From owner-svn-doc-all@FreeBSD.ORG Tue May 13 03:34:53 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 05CF27E2; Tue, 13 May 2014 03:34:53 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E615D24DC; Tue, 13 May 2014 03:34:52 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s4D3Yqjb028154; Tue, 13 May 2014 03:34:52 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s4D3YqK1028153; Tue, 13 May 2014 03:34:52 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201405130334.s4D3YqK1028153@svn.freebsd.org> From: Dru Lavigne Date: Tue, 13 May 2014 03:34:52 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44818 - head/en_US.ISO8859-1/books/faq X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2014 03:34:53 -0000 Author: dru Date: Tue May 13 03:34:52 2014 New Revision: 44818 URL: http://svnweb.freebsd.org/changeset/doc/44818 Log: White space fix only. Translators can ignore. Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/faq/book.xml Modified: head/en_US.ISO8859-1/books/faq/book.xml ============================================================================== --- head/en_US.ISO8859-1/books/faq/book.xml Mon May 12 18:42:03 2014 (r44817) +++ head/en_US.ISO8859-1/books/faq/book.xml Tue May 13 03:34:52 2014 (r44818) @@ -4247,32 +4247,36 @@ options SYSVMSG # enable for - The sendmail - server is the default mail-server software for &os;, but you - can easily replace it with one of the other MTA (for + The sendmail + server is the default mail-server software for &os;, but + you can easily replace it with one of the other MTA (for instance, an MTA installed from the ports). There are various alternative MTAs in the ports tree already, with mail/exim, - mail/postfix, mail/qmail, and mail/zmailer being some of the - most popular choices. + mail/postfix, + mail/qmail, and + mail/zmailer being some of the most + popular choices. Diversity is nice, and the fact that you have many different mail-servers to chose from is considered a good thing; therefore try to avoid asking questions like Is sendmail better than qmail? in the mailing - lists. If you do feel like asking, first check the mailing - list archives. The advantages and disadvantages of each and - every one of the available MTAs have already been discussed - a few times. + lists. If you do feel like asking, first check the + mailing list archives. The advantages and disadvantages + of each and every one of the available MTAs have already + been discussed a few times. - I have forgotten the root password! - What do I do? + I have forgotten the root password! What do I + do? @@ -4281,27 +4285,29 @@ options SYSVMSG # enable for Boot: prompt to enter Single User mode. At the question about the shell to use, hit Enter. You will be dropped to a - &prompt.root; prompt. Enter mount -urw / - to remount your root file system read/write, then run - mount -a to remount all the file systems. - Run passwd root to change the - root password then run &man.exit.1; to - continue booting. + &prompt.root; prompt. Enter mount + -urw / to remount your root file system + read/write, then run mount -a to + remount all the file systems. Run passwd + root to change the root password then run + &man.exit.1; to continue booting. - If you are still prompted to give the - root password when entering the - Single User mode, it means that the console has been - marked as insecure in + If you are still prompted to give the root password when + entering the Single User mode, it means that the console + has been marked as insecure in /etc/ttys. In this case it will be required to boot from a &os; installation disk, choose the Live CD or - Shell at the beginning of the install - process and issue the commands mentioned above. You will need to - mount the specific partition in this case and then chroot to it, - i.e., replace mount -urw / by - mount /dev/ada0p1 /mnt; chroot /mnt for - a system on ada0p1. + Shell at the beginning of the + install process and issue the commands mentioned above. + You will need to mount the specific partition in this + case and then chroot to it, i.e., replace mount + -urw / by mount /dev/ada0p1 /mnt; + chroot /mnt for a system on + ada0p1. @@ -4310,21 +4316,23 @@ options SYSVMSG # enable for encrypted and it is impossible to mount them without the access keys. Your chances depend on the chosen implementation. For more information see the section - about encrypted disks in the &os; Handbook. + about encrypted disks in the &os; Handbook. - How do I keep ControlAltDelete + How do I keep ControlAltDelete from rebooting the system? If you are using &man.syscons.4; (the default console - driver) build and install a new kernel with the line in the - configuration file: + driver) build and install a new kernel with the line in + the configuration file: options SC_DISABLE_REBOOT @@ -4335,16 +4343,18 @@ options SYSVMSG # enable for &prompt.root; sysctl hw.syscons.kbd_reboot=0 - The above two methods are exclusive: The &man.sysctl.8; - does not exist if you compile your kernel with the - SC_DISABLE_REBOOT option. + The above two methods are exclusive: The + &man.sysctl.8; does not exist if you compile your kernel + with the SC_DISABLE_REBOOT + option. - How do I reformat DOS text files to &unix; ones? + How do I reformat DOS text files to &unix; + ones? @@ -4352,25 +4362,26 @@ options SYSVMSG # enable for &prompt.user; perl -i.bak -npe 's/\r\n/\n/g' file(s) - where file(s) is one or more - files to process. The modification is done in-place, with the - original file stored with a .bak - extension. + where file(s) is one or + more files to process. The modification is done in-place, + with the original file stored with a + .bak extension. - Alternatively you can use the &man.tr.1; command: + Alternatively you can use the &man.tr.1; + command: &prompt.user; tr -d '\r' < dos-text-file > unix-file dos-text-file is the file containing DOS text while unix-file will contain the - converted output. This can be quite a bit faster than using - perl. + converted output. This can be quite a bit faster than + using perl. - Yet another way to reformat DOS text files is to use the - converters/dosunix port - from the Ports Collection. Consult its documentation about - the details. + Yet another way to reformat DOS text files is to use + the converters/dosunix port from the + Ports Collection. Consult its documentation about the + details. @@ -4411,73 +4422,77 @@ options SYSVMSG # enable for -STABLE, but got -BETAx, -RC or - -PRERELEASE! What is going on? + -PRERELEASE! What is going + on? Short answer: it is just a name. RC stands for Release - Candidate. It signifies that a release is imminent. - In &os;, -PRERELEASE is typically - synonymous with the code freeze before a release. (For some - releases, the -BETA label was used in - the same way as -PRERELEASE.) + Candidate. It signifies that a release is + imminent. In &os;, -PRERELEASE is + typically synonymous with the code freeze before a + release. (For some releases, the + -BETA label was used in the same way + as -PRERELEASE.) Long answer: &os; derives its releases from one of two places. Major, dot-zero, releases, such as 9.0-RELEASE - are branched from the head of the development - stream, commonly referred to as -CURRENT. Minor releases, such as - 6.3-RELEASE or 5.2-RELEASE, have been snapshots of the + are branched from the head of the development stream, + commonly referred to as -CURRENT. Minor releases, such + as 6.3-RELEASE or 5.2-RELEASE, have been snapshots of the active -STABLE branch. - Starting with 4.3-RELEASE, each release also now has its own - branch which can be tracked by people requiring an extremely - conservative rate of development (typically only security - advisories). + Starting with 4.3-RELEASE, each release also now has its + own branch which can be tracked by people requiring an + extremely conservative rate of development (typically only + security advisories). When a release is about to be made, the branch from which it will be derived from has to undergo a certain process. Part of this process is a code freeze. When a - code freeze is initiated, the name of the branch is changed - to reflect that it is about to become a release. For - example, if the branch used to be called 6.2-STABLE, its - name will be changed to 6.3-PRERELEASE to signify the code - freeze and signify that extra pre-release testing should be - happening. Bug fixes can still be committed to be part of - the release. When the source code is in shape for the - release the name will be changed to 6.3-RC to signify that a - release is about to be made from it. Once in the RC stage, - only the most critical bugs found can be fixed. Once the - release (6.3-RELEASE in this example) and release branch - have been made, the branch will be renamed to - 6.3-STABLE. - - For more information on version numbers and the various - Subversion branches, refer to the Release Engineering - article. + code freeze is initiated, the name of the branch is + changed to reflect that it is about to become a release. + For example, if the branch used to be called 6.2-STABLE, + its name will be changed to 6.3-PRERELEASE to signify the + code freeze and signify that extra pre-release testing + should be happening. Bug fixes can still be committed to + be part of the release. When the source code is in shape + for the release the name will be changed to 6.3-RC to + signify that a release is about to be made from it. Once + in the RC stage, only the most critical bugs found can be + fixed. Once the release (6.3-RELEASE in this example) and + release branch have been made, the branch will be renamed + to 6.3-STABLE. + + For more information on version numbers and the + various Subversion branches, refer to the Release + Engineering article. - I tried to install a new kernel, and the &man.chflags.1; - failed. How do I get around this? + I tried to install a new kernel, and the + &man.chflags.1; failed. How do I get around this? - Short answer: You are probably at security level greater - than 0. Reboot directly to Single User mode to install the - kernel. + Short answer: You are probably at security level + greater than 0. Reboot directly to Single User mode to + install the kernel. Long answer: &os; disallows changing system flags at - security levels greater than 0. You can check your security - level with the command: + security levels greater than 0. You can check your + security level with the command: &prompt.root; sysctl kern.securelevel - You cannot lower the security level; you have to boot to - Single Mode to install the kernel, or change the security - level in /etc/rc.conf then reboot. See - the &man.init.8; manual page for details on + You cannot lower the security level; you have to boot + to Single Mode to install the kernel, or change the + security level in /etc/rc.conf then + reboot. See the &man.init.8; manual page for details on securelevel, and see /etc/defaults/rc.conf and the &man.rc.conf.5; manual page for more information on @@ -4492,20 +4507,20 @@ options SYSVMSG # enable for - Short answer: You are probably at security level greater - than 1. Reboot directly to Single User mode to change the - date. + Short answer: You are probably at security level + greater than 1. Reboot directly to Single User mode to + change the date. Long answer: &os; disallows changing the time by more - that one second at security levels greater than 1. You can - check your security level with the command: + that one second at security levels greater than 1. You + can check your security level with the command: &prompt.root; sysctl kern.securelevel - You cannot lower the security level; you have to boot to - Single User mode to change the date, or change the security - level in /etc/rc.conf then reboot. See - the &man.init.8; manual page for details on + You cannot lower the security level; you have to boot + to Single User mode to change the date, or change the + security level in /etc/rc.conf then + reboot. See the &man.init.8; manual page for details on securelevel, and see /etc/defaults/rc.conf and the &man.rc.conf.5; manual page for more information on @@ -4515,8 +4530,8 @@ options SYSVMSG # enable for - Why is rpc.statd using 256 MB of - memory? + Why is rpc.statd using 256 MB + of memory? @@ -4524,17 +4539,17 @@ options SYSVMSG # enable for 256 MB of memory. For convenience, rpc.statd maps an obscene amount of memory into its address space. There is nothing terribly - wrong with this from a technical standpoint; it just throws - off things like &man.top.1; and &man.ps.1;. + wrong with this from a technical standpoint; it just + throws off things like &man.top.1; and &man.ps.1;. &man.rpc.statd.8; maps its status file (resident on /var) into its address space; to save - worrying about remapping it later when it needs to grow, it - maps it with a generous size. This is very evident from the - source code, where one can see that the length argument to - &man.mmap.2; is 0x10000000, or one - sixteenth of the address space on an IA32, or exactly - 256 MB. + worrying about remapping it later when it needs to grow, + it maps it with a generous size. This is very evident + from the source code, where one can see that the length + argument to &man.mmap.2; is 0x10000000, + or one sixteenth of the address space on an IA32, or + exactly 256 MB. @@ -4546,9 +4561,9 @@ options SYSVMSG # enable for You are running at an elevated (i.e., greater than 0) - securelevel. Lower the securelevel and try again. For more - information, see the FAQ entry - on securelevel and the &man.init.8; manual + securelevel. Lower the securelevel and try again. For + more information, see the FAQ + entry on securelevel and the &man.init.8; manual page. @@ -4556,17 +4571,17 @@ options SYSVMSG # enable for Why does SSH authentication - through .shosts not work by default in - recent versions of &os;? + through .shosts not work by default + in recent versions of &os;? The reason why .shosts authentication does not work by default in more recent versions of &os; is because &man.ssh.1; is not installed - suid root by default. To - fix this, you can do one of the - following: + suid root by + default. To fix this, you can do one of + the following: @@ -4580,9 +4595,9 @@ options SYSVMSG # enable for As a temporary fix, change the mode on /usr/bin/ssh to - 4555 by running - chmod 4555 /usr/bin/ssh as - root. + 4555 by running chmod 4555 + /usr/bin/ssh as root. @@ -4595,10 +4610,10 @@ options SYSVMSG # enable for vnlru flushes and frees vnodes when - the system hits the kern.maxvnodes limit. - This kernel thread sits mostly idle, and only activates if - you have a huge amount of RAM and are accessing tens of - thousands of tiny files. + the system hits the kern.maxvnodes + limit. This kernel thread sits mostly idle, and only + activates if you have a huge amount of RAM and are + accessing tens of thousands of tiny files. @@ -4624,49 +4639,51 @@ options SYSVMSG # enable for Cache: (most often) pages that have percolated from inactive to a status where they - maintain their data, but can often be immediately reused - (either with their old association, or reused with a new - association). There can be certain immediate transitions - from active to - cache state if the page is known to - be clean (unmodified), but that transition is a matter - of policy, depending upon the algorithm choice of the VM - system maintainer. + maintain their data, but can often be immediately + reused (either with their old association, or reused + with a new association). There can be certain + immediate transitions from active + to cache state if the page is known + to be clean (unmodified), but that transition is a + matter of policy, depending upon the algorithm choice + of the VM system maintainer. - Free: pages without data content, - and can be immediately used in certain circumstances - where cache pages might be ineligible. Free pages can - be reused at interrupt or process + Free: pages without data + content, and can be immediately used in certain + circumstances where cache pages might be ineligible. + Free pages can be reused at interrupt or process state. - Wired: pages that are fixed into - memory, usually for kernel purposes, but also sometimes - for special use in processes. + Wired: pages that are fixed + into memory, usually for kernel purposes, but also + sometimes for special use in processes. - Pages are most often written to disk (sort of a VM sync) - when they are in the inactive state, but active pages can - also be synced. This depends upon the CPU tracking of the - modified bit being available, and in certain situations - there can be an advantage for a block of VM pages to be - synced, whether they are active or inactive. In most common - cases, it is best to think of the inactive queue to be a - queue of relatively unused pages that might or might not be - in the process of being written to disk. Cached pages are - already synced, not mapped, but available for immediate - process use with their old association or with a new - association. Free pages are available at interrupt level, - but cached or free pages can be used at process state for - reuse. Cache pages are not adequately locked to be - available at interrupt level. + Pages are most often written to disk (sort of a VM + sync) when they are in the inactive state, but active + pages can also be synced. This depends upon the CPU + tracking of the modified bit being available, and in + certain situations there can be an advantage for a block + of VM pages to be synced, whether they are active or + inactive. In most common cases, it is best to think of + the inactive queue to be a queue of relatively unused + pages that might or might not be in the process of being + written to disk. Cached pages are already synced, not + mapped, but available for immediate process use with their + old association or with a new association. Free pages are + available at interrupt level, but cached or free pages can + be used at process state for reuse. Cache pages are not + adequately locked to be available at interrupt + level. There are some other flags (e.g., busy flag or busy - count) that might modify some of the described rules. + count) that might modify some of the described + rules. @@ -4680,16 +4697,16 @@ options SYSVMSG # enable for There are a couple of kinds of free memory. One kind is the amount of memory immediately available without paging anything else out. - That is approximately the size of cache queue + size of free - queue (with a derating factor, depending upon system - tuning). Another kind of free memory is the - total amount of VM space. That can be - complex, but is dependent upon the amount of swap space and - memory. Other kinds of free memory - descriptions are also possible, but it is relatively useless - to define these, but rather it is important to make sure - that the paging rate is kept low, and to avoid running out - of swap space. + That is approximately the size of cache queue + size of + free queue (with a derating factor, depending upon system + tuning). Another kind of free memory is + the total amount of VM space. That can + be complex, but is dependent upon the amount of swap space + and memory. Other kinds of free memory + descriptions are also possible, but it is relatively + useless to define these, but rather it is important to + make sure that the paging rate is kept low, and to avoid + running out of swap space. @@ -4700,24 +4717,26 @@ options SYSVMSG # enable for - /var/empty is a directory that the - &man.sshd.8; program uses when performing privilege separation. - The /var/empty directory is empty, owned by - root and has the schg - flag set. - - Although it is not recommended to delete this directory, to - do so you will need to unset the schg flag - first. See the &man.chflags.1; manual page for more information - (and bear in mind the answer to - the question on unsetting the schg flag). + /var/empty is a directory that + the &man.sshd.8; program uses when performing privilege + separation. The /var/empty + directory is empty, owned by root and has the + schg flag set. + + Although it is not recommended to delete this + directory, to do so you will need to unset the + schg flag first. See the + &man.chflags.1; manual page for more information (and bear + in mind the answer to the + question on unsetting the schg flag). I just changed - /etc/newsyslog.conf. How can I check + /etc/newsyslog.conf. How can I check if it does what I expect? @@ -4752,14 +4771,16 @@ options SYSVMSG # enable for - The X Window System (commonly X11) is - the most widely available windowing system capable of running - on &unix; or &unix; like systems, including &os;. - The X.Org Foundation - administers the X protocol standards, - with the current reference implementation, version 11 - release &xorg.version;, so you will often see references - shortened to X11. + The X Window System (commonly X11) + is the most widely available windowing system capable of + running on &unix; or &unix; like systems, including + &os;. The X.Org + Foundation administers the X + protocol standards, with the current reference + implementation, version 11 release &xorg.version;, so you + will often see references shortened to + X11. Many implementations are available for different architectures and operating systems. An implementation of @@ -4787,13 +4808,16 @@ options SYSVMSG # enable for &prompt.root; pkg_add -r xorg - or on systems using pkg: + or on systems using + pkg: &prompt.root; pkg install xorg - After the installation of &xorg;, follow - the instructions from the X11 Configuration section of - the &os; Handbook. + After the installation of &xorg;, follow the + instructions from the X11 + Configuration section of the &os; + Handbook. @@ -4801,27 +4825,24 @@ options SYSVMSG # enable for I tried to run X, but I get a No devices detected. error when I - type - startx. What do I do now? + type startx. What do I do now? Your system is probably running at a raised - securelevel. It is not possible to start X - at a raised securelevel because X - requires write access to &man.io.4;. For more information, - see at the &man.init.8; manual page. + securelevel. It is not possible to + start X at a raised securelevel because + X requires write access to &man.io.4;. For more + information, see at the &man.init.8; manual page. - There are two solutions to the problem: - Set your + There are two solutions to the problem: Set your securelevel back down to zero (usually in /etc/rc.conf), or run &man.xdm.1; - (or an alternative display manager) - at boot time (before the securelevel is - raised). + (or an alternative display manager) at boot time (before + the securelevel is raised). - See for more information about - running &man.xdm.1; at boot time. + See for more information + about running &man.xdm.1; at boot time. @@ -4832,14 +4853,15 @@ options SYSVMSG # enable for If you are using &man.syscons.4; (the default console - driver), you can configure &os; to support a mouse pointer on - each virtual screen. To avoid conflicting with X, + driver), you can configure &os; to support a mouse pointer + on each virtual screen. To avoid conflicting with X, &man.syscons.4; supports a virtual device called /dev/sysmouse. All mouse events received from the real mouse device are written to the &man.sysmouse.4; device via &man.moused.8;. To use your mouse on one or more virtual consoles, - and use X, see and set up + and use X, see and set up &man.moused.8;. Then edit /etc/X11/xorg.conf and @@ -4853,9 +4875,9 @@ options SYSVMSG # enable for Starting with &xorg; version 7.4, the InputDevice sections in xorg.conf are ignored in favor of - autodetected devices. To restore the old behavior, add the - following line to the ServerLayout or - ServerFlags section: + autodetected devices. To restore the old behavior, add + the following line to the ServerLayout + or ServerFlags section: Option "AutoAddDevices" "false" @@ -4870,8 +4892,8 @@ options SYSVMSG # enable for link sysmouse mouse This link can be created by restarting &man.devfs.5; - with the following command (as - root): + with the following command (as root): &prompt.root; service devfs restart @@ -4890,12 +4912,12 @@ options SYSVMSG # enable for and ZAxisMapping 4 5 to the InputDevice section of /etc/X11/xorg.conf. For example, you - might have the following InputDevice section - in /etc/X11/xorg.conf. + might have the following InputDevice + section in /etc/X11/xorg.conf. - <quote>InputDevice</quote> Section for Wheeled Mouse - in &xorg; Configuration File + <quote>InputDevice</quote> Section for Wheeled + Mouse in &xorg; Configuration File Section "InputDevice" Identifier "Mouse1" @@ -4920,18 +4942,18 @@ EndSection - My laptop has a Synaptics touchpad. Can I use - it in X? + My laptop has a Synaptics touchpad. Can I use it in + X? - Yes, you will have to configure a few things to - make it work. + Yes, you will have to configure a few things to make + it work. If you plan to use the Xorg synaptics driver you must remove moused_enable from - rc.conf. Xorg can not use - the synaptics mouse if the moused already sits on + rc.conf. Xorg can not use the + synaptics mouse if the moused already sits on /dev/psm0. To enable synaptics in the &man.psm.4; driver you need @@ -4976,35 +4998,43 @@ EndSection - What is a virtual console and how do I make more? + What is a virtual console and how do I make + more? - Virtual consoles, put simply, enable you to have several - simultaneous sessions on the same machine without doing - anything complicated like setting up a network or running - X. + Virtual consoles, put simply, enable you to have + several simultaneous sessions on the same machine without + doing anything complicated like setting up a network or + running X. When the system starts, it will display a login prompt - on the monitor after displaying all the boot messages. You - can then type in your login name and password and start - working (or playing!) on the first virtual console. + on the monitor after displaying all the boot messages. + You can then type in your login name and password and + start working (or playing!) on the first virtual + console. At some point, you will probably wish to start another - session, perhaps to look at documentation for a program you - are running or to read your mail while waiting for an FTP - transfer to finish. Just do AltF2 + session, perhaps to look at documentation for a program + you are running or to read your mail while waiting for an + FTP transfer to finish. Just do AltF2 (hold down Alt and press F2), and you will find a login prompt waiting for you on the second virtual - console! When you want to go back to the original - session, do AltF1. - - The default &os; installation has eight virtual consoles - enabled. AltF1, - AltF2, - AltF3, - and so on will switch between these virtual consoles. + console! When you want to go back to the + original session, do AltF1. + + The default &os; installation has eight virtual + consoles enabled. AltF1, + AltF2, + AltF3, + and so on will switch between these virtual + consoles. To enable more of them, edit /etc/ttys (see &man.ttys.5;) and add @@ -5021,8 +5051,8 @@ ttyvb "/usr/libexec/getty Pc" Use as many or as few as you want. The more virtual terminals you have, the more resources that are used; this - can be important if you have 8 MB RAM or less. You may - also want to change the secure to + can be important if you have 8 MB RAM or less. You + may also want to change the secure to insecure. @@ -5036,11 +5066,12 @@ ttyvb "/usr/libexec/getty Pc" If you want to run an X server you must leave at least one virtual - terminal unused (or turned off) for it to use. That is to - say that if you want to have a login prompt pop up for all - twelve of your Alt-function keys, you are out of luck - — you can only do this for eleven of them if you - also want to run an X server on the same machine. + terminal unused (or turned off) for it to use. That is + to say that if you want to have a login prompt pop up + for all twelve of your Alt-function keys, you are out of + luck — you can only do this for eleven of them if + you also want to run an X server on the same + machine. The easiest way to disable a console is by turning it @@ -5066,14 +5097,15 @@ ttyvb "/usr/libexec/getty Pc" Next, the easiest (and cleanest) way to activate the virtual consoles is to reboot. However, if you really do not want to reboot, you can just shut down the X Window - system and execute (as root): + system and execute (as root): &prompt.root; kill -HUP 1 - It is imperative that you completely shut down X Window - if it is running, before running this command. If you do not, - your system will probably appear to hang or lock up after - executing kill. + It is imperative that you completely shut down X + Window if it is running, before running this command. If + you do not, your system will probably appear to hang or + lock up after executing kill. @@ -5083,21 +5115,25 @@ ttyvb "/usr/libexec/getty Pc" - Use CtrlAltFn - to switch back to a virtual console. CtrlAltF1 + Use CtrlAltFn + to switch back to a virtual console. CtrlAltF1 would return you to the first virtual console. Once you are back to a text console, you can then use - AltFn + AltFn as normal to move between them. To return to the X session, you must switch to the virtual console running X. If you invoked X from the command line, (e.g., using startx) then the X session will attach to the next unused virtual - console, not the text console from which it was invoked. If - you have eight active virtual terminals then X will be - running on the ninth, and you would use AltF9 + console, not the text console from which it was invoked. + If you have eight active virtual terminals then X will be + running on the ninth, and you would use AltF9 to return. @@ -5110,32 +5146,32 @@ ttyvb "/usr/libexec/getty Pc" There are two schools of thought on how to start - &man.xdm.1;. One school starts xdm from - /etc/ttys (see &man.ttys.5;) using the - supplied example, while the other simply runs + &man.xdm.1;. One school starts xdm + from /etc/ttys (see &man.ttys.5;) + using the supplied example, while the other simply runs xdm from rc.local (see &man.rc.8;) or from an X script in - /usr/local/etc/rc.d. Both are equally - valid, and one may work in situations where the other does - not. In both cases the result is the same: X will pop up a - graphical login prompt. - - The &man.ttys.5; method has the advantage of documenting - which vty X will start on and passing the responsibility of - restarting the X server on logout to &man.init.8;. The - &man.rc.8; method makes it easy to kill - xdm if there is a problem starting the X - server. - - If loaded from &man.rc.8;, xdm should - be started without any arguments (i.e., as a daemon). - xdm must start + /usr/local/etc/rc.d. Both are + equally valid, and one may work in situations where the + other does not. In both cases the result is the same: X + will pop up a graphical login prompt. + + The &man.ttys.5; method has the advantage of + documenting which vty X will start on and passing the + responsibility of restarting the X server on logout to + &man.init.8;. The &man.rc.8; method makes it easy to + kill xdm if there is + a problem starting the X server. + + If loaded from &man.rc.8;, xdm + should be started without any arguments (i.e., as a + daemon). xdm must start after &man.getty.8; runs, or else getty and xdm will - conflict, locking out the console. The best way around this - is to have the script sleep 10 seconds or so then launch - xdm. + conflict, locking out the console. The best way around + this is to have the script sleep 10 seconds or so then + launch xdm. If you are to start xdm from /etc/ttys, there still is a chance of @@ -5175,8 +5211,8 @@ ttyvb "/usr/libexec/getty Pc" machine with a VTY, the &man.fbtab.5; file exists to solve such problems. - In a nutshell, make sure an uncommented line of the form - is in /etc/fbtab (see + In a nutshell, make sure an uncommented line of the + form is in /etc/fbtab (see &man.fbtab.5;): /dev/ttyv0 0600 /dev/console @@ -5193,8 +5229,8 @@ ttyvb "/usr/libexec/getty Pc" - Your mouse and the mouse driver may have somewhat become - out of synchronization. + Your mouse and the mouse driver may have somewhat + become out of synchronization. In rare cases the driver may erroneously report synchronization problem and you may see the kernel @@ -5205,15 +5241,16 @@ ttyvb "/usr/libexec/getty Pc" and notice that your mouse does not work properly. - If this happens, disable the synchronization check code - by setting the driver flags for the PS/2 mouse driver to - 0x100. This can be easiest achieved + If this happens, disable the synchronization check + code by setting the driver flags for the PS/2 mouse driver + to 0x100. This can be easiest achieved by adding hint.psm.0.flags="0x100" to - /boot/loader.conf and rebooting. + /boot/loader.conf and + rebooting. @@ -5240,8 +5277,10 @@ ttyvb "/usr/libexec/getty Pc" The detailed answer for this question can be found in - the Boot Time Splash Screens *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***