From owner-svn-doc-all@freebsd.org Sat Aug 1 15:47:46 2015 Return-Path: Delivered-To: svn-doc-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 336D99AF885; Sat, 1 Aug 2015 15:47:46 +0000 (UTC) (envelope-from bhd@FreeBSD.org) Received: from repo.freebsd.org (repo.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 228B997; Sat, 1 Aug 2015 15:47:46 +0000 (UTC) (envelope-from bhd@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.70]) by repo.freebsd.org (8.14.9/8.14.9) with ESMTP id t71Flkux009755; Sat, 1 Aug 2015 15:47:46 GMT (envelope-from bhd@FreeBSD.org) Received: (from bhd@localhost) by repo.freebsd.org (8.14.9/8.14.9/Submit) id t71FlkOg009754; Sat, 1 Aug 2015 15:47:46 GMT (envelope-from bhd@FreeBSD.org) Message-Id: <201508011547.t71FlkOg009754@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: bhd set sender to bhd@FreeBSD.org using -f From: Bjoern Heidotting Date: Sat, 1 Aug 2015 15:47:46 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r47142 - 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.20 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: Sat, 01 Aug 2015 15:47:46 -0000 Author: bhd Date: Sat Aug 1 15:47:45 2015 New Revision: 47142 URL: https://svnweb.freebsd.org/changeset/doc/47142 Log: Fix typos and various other things found by igor. Translators can ignore. Approved by: bcr (mentor) 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 Sat Aug 1 09:28:08 2015 (r47141) +++ head/en_US.ISO8859-1/books/faq/book.xml Sat Aug 1 15:47:45 2015 (r47142) @@ -20,8 +20,9 @@ ]> - Frequently Asked Questions for &os; - &rel3.relx;, &rel2.relx; and &rel.relx; + + Frequently Asked Questions for &os; + &rel3.relx;, &rel2.relx; and &rel.relx; The &os; Documentation Project @@ -72,11 +73,11 @@ This is the Frequently Asked Questions - FAQ for &os; versions &rel3.relx;, &rel2.relx; - and &rel.relx;. Every effort has been made to make this FAQ - as informative as possible; if you have any suggestions as to - how it may be improved, send them to the - &a.doc;. + FAQ for &os; versions &rel3.relx;, + &rel2.relx; and &rel.relx;. Every effort has been made to + make this FAQ as informative as possible; + if you have any suggestions as to how it may be improved, send + them to the &a.doc;. The latest version of this document is always available from the - Yes. Those restrictions do not control how - the code is used, but how to treat the &os; Project itself. + Yes. Those restrictions do not control how the code + is used, but how to treat the &os; Project itself. The license itself is available at license - and can be summarized like - this: + and can be summarized like this: @@ -211,15 +211,15 @@ xlink:href="http://www.FreeBSD.org/ports/">Ports Collection. - If an application is only - available on one operating system, - that operating system cannot just be replaced. Chances are, there is a - very similar application on &os;, however. As a - solid office or Internet server or a reliable workstation, - &os; will almost certainly do everything you need. Many - computer users across the world, including both novices - and experienced &unix; administrators, use &os; as their - only desktop operating system. + If an application is only available on one operating + system, that operating system cannot just be replaced. + Chances are, there is a very similar application on &os;, + however. As a solid office or Internet server or a + reliable workstation, &os; will almost certainly do + everything you need. Many computer users across the + world, including both novices and experienced &unix; + administrators, use &os; as their only desktop operating + system. Users migrating to &os; from another &unix;-like environment will find &os; to be similar. @@ -228,7 +228,8 @@ xlink:href="http://www.pcbsd.org/">PC-BSD, a &os;-based desktop distribution. Non-&unix; users should expect to invest some additional time learning the - &unix; way of doing things. This FAQ and the FAQ + and the &os; Handbook are excellent places to start. @@ -356,7 +357,8 @@ -CURRENT snapshot. Releases can come from either branch, but -CURRENT is meant for users who are prepared for its increased - volatility, relative to -STABLE. + volatility, relative to + -STABLE. Releases are made every few months. While many people stay more @@ -923,8 +925,9 @@ compressed files, uncompress them, and then copy the appropriate documents into place. - For example, the split HTML version of the FAQ, - compressed using &man.bzip2.1;, can be found in + For example, the split HTML version of the + FAQ, compressed using &man.bzip2.1;, + can be found in doc/en_US.ISO8859-1/books/faq/book.html-split.tar.bz2 To download and uncompress that file, type: @@ -983,12 +986,11 @@ questions. Other users can help with the basics, referring to the Handbook whenever possible and providing links for learning more about - a particular topic. This is primarily an - English speaking channel, though it does have users from - all over the world. Non-native English speakers should - try to ask the question in - English first and then relocate to - ##freebsd-lang as + a particular topic. This is primarily an English + speaking channel, though it does have users from all + over the world. Non-native English speakers should + try to ask the question in English first and then + relocate to ##freebsd-lang as appropriate. @@ -1080,11 +1082,19 @@ - Installation + Installation - NikClayton -
nik@FreeBSD.org
- + + + Nik + Clayton + + +
+ nik@FreeBSD.org +
+ + @@ -1100,8 +1110,8 @@ &arch.amd64; is the term &os; uses for 64-bit compatible x86 architectures (also known as "x86-64" or "x64"). Most modern computers should use &arch.amd64;. - Older hardware should use &arch.i386;. When - installing on a non-x86-compatible architecture, select the + Older hardware should use &arch.i386;. When installing + on a non-x86-compatible architecture, select the platform which best matches the hardware. @@ -1114,8 +1124,8 @@ On the Getting - &os; page, select [iso] next to - the architecture that matches the hardware. + &os; page, select [iso] next + to the architecture that matches the hardware. Any of the following can be used: @@ -1175,27 +1185,28 @@ - What do I do if the install image does not boot? + What do I do if the install image does not + boot? This can be caused by not downloading the image in - binary mode when using - FTP. + binary mode when using + FTP. - Some FTP clients default their transfer mode to - ascii and attempt to change any - end-of-line characters received to match the - conventions used by the client's system. This will - almost invariably corrupt the boot image. Check the - SHA-256 checksum of the downloaded boot image: if it is not - exactly that on the server, then - the download process is suspect. - - When using a command line FTP client, type binary at - the FTP command prompt after getting connected to the - server and before starting the download of the - image. + Some FTP clients default their transfer mode to + ascii and attempt to change any + end-of-line characters received to match the + conventions used by the client's system. This will + almost invariably corrupt the boot image. Check the + SHA-256 checksum of the downloaded boot image: if it + is not exactly that on the + server, then the download process is suspect. + + When using a command line FTP client, type + binary at the FTP command prompt + after getting connected to the server and before + starting the download of the image. @@ -1403,8 +1414,8 @@ buildworld and make buildkernel to update the kernel. - Boot the system by specifying the kernel directly at the - second stage, pressing any key when the + Boot the system by specifying the kernel directly at + the second stage, pressing any key when the | shows up before loader is started. @@ -1439,8 +1450,8 @@ This is discussed continually on the &os; mailing - lists but is to be expected since hardware changes so quickly. - Read through the Hardware Notes + lists but is to be expected since hardware changes so + quickly. Read through the Hardware Notes for &os; &rel.current; or + platforms support up to 4 TB of physical + memory. @@ -1522,7 +1534,8 @@ thumb is that if the driver is usable on 64-bit architectures (like AMD64), it is also usable with PAE. When creating a custom kernel configuration - file, PAE can be enabled by adding the following line: + file, PAE can be enabled by adding the following + line: options PAE @@ -1663,12 +1676,12 @@ &man.chio.1;. While - AMANDA and some other products - already understands changers, other applications - only know how to move a tape from one point to another/ - In this case, keep track of which slot a tape is in - and which slot the tape currently in the drive needs to - go back to. + AMANDA and some other + products already understands changers, other + applications only know how to move a tape from one point + to another. In this case, keep track of which slot a + tape is in and which slot the tape currently in the + drive needs to go back to. @@ -1687,8 +1700,8 @@ drive. See &man.burncd.8; for details. &os; also supports any SCSI CD-R or CD-RW drives. - Install the sysutils/cdrtools - port or package, then use cdrecord. + Install the sysutils/cdrtools port or + package, then use cdrecord. @@ -1706,10 +1719,10 @@ The default console driver, - &man.syscons.4;, provides the ability to use a mouse pointer in text - consoles to cut & paste text. Run the mouse daemon, - &man.moused.8;, and turn on the mouse pointer in the - virtual console: + &man.syscons.4;, provides the ability to use a mouse + pointer in text consoles to cut & paste text. Run + the mouse daemon, &man.moused.8;, and turn on the mouse + pointer in the virtual console: &prompt.root; moused -p /dev/xxxx -t yyyy &prompt.root; vidcontrol -m on @@ -1735,7 +1748,8 @@ When the mouse daemon is running, access to the mouse must be coordinated between the mouse daemon and - other programs such as X Windows. Refer to the FAQ + other programs such as X Windows. Refer to the + FAQ Why does my mouse not work with X? for more details on this issue. @@ -1749,9 +1763,8 @@ It is not possible to remove data using the mouse. - However, it is possible to copy and - paste. - Once the mouse daemon is running as described in the previous question, hold down button 1 (left button) and move the mouse to select a region of text. Then, press button 2 (middle button) to @@ -1759,9 +1772,9 @@ button) will extend the selected region of text. - If the mouse does not have a middle button, it is possible - to emulate one or remap buttons using mouse daemon - options. See the &man.moused.8; manual page for + If the mouse does not have a middle button, it is + possible to emulate one or remap buttons using mouse + daemon options. See the &man.moused.8; manual page for details. @@ -1883,8 +1896,8 @@ bindkey ^[[3~ delete-char # for xterm

On a 32-bit version of &os;, the memory appears lost, since it will be remapped above 4 GB, which a 32-bit kernel is unable to access. In this case, the solution is - to build a PAE enabled kernel. See - the entry on memory limits for more information. + to build a PAE enabled kernel. See the entry on memory + limits for more information. On a 64-bit version of &os;, or when running a PAE-enabled kernel, &os; will correctly detect and remap @@ -1923,8 +1936,9 @@ bindkey ^[[3~ delete-char # for xterm

If it is a problem with part of the base &os; system, it may also be buggy code, but more often than not these problems are found and fixed long before us - general FAQ readers get to use these bits of code - (that is what -CURRENT is for). + general FAQ readers get to use + these bits of code (that is what -CURRENT is + for). @@ -1937,8 +1951,8 @@ bindkey ^[[3~ delete-char # for xterm

For example, if make buildworld fails while trying to compile ls.c into - ls.o and, when run again, it fails in the - same place, this is a broken build. Try + ls.o and, when run again, it fails + in the same place, this is a broken build. Try updating source and try again. If the compile fails elsewhere, it is almost certainly due to hardware. @@ -1954,8 +1968,8 @@ bindkey ^[[3~ delete-char # for xterm

- The hard disks might be overheating: Check that the - fans are still working, as the disk and + The hard disks might be overheating: Check that + the fans are still working, as the disk and other hardware might be overheating. @@ -2008,10 +2022,11 @@ bindkey ^[[3~ delete-char # for xterm

- Read the section on Signal 11 - for a further explanation and a discussion on how - memory testing software or hardware can still pass faulty - memory. There is an extensive FAQ on this at Read the section on + Signal 11 for a further + explanation and a discussion on how memory testing + software or hardware can still pass faulty memory. There + is an extensive FAQ on this at the SIG11 problem FAQ. @@ -2037,16 +2052,16 @@ bindkey ^[[3~ delete-char # for xterm

FAQ section on kernel panics, build a debugging kernel, and get a - backtrace. This might sound difficult, but does not require - any programming skills. Just follow the + backtrace. This might sound difficult, but does not + require any programming skills. Just follow the instructions. - What is the meaning of the error maxproc limit - exceeded by uid %i, please see tuning(7) and + What is the meaning of the error maxproc + limit exceeded by uid %i, please see tuning(7) and login.conf(5)? @@ -2068,9 +2083,9 @@ bindkey ^[[3~ delete-char # for xterm

- If the machine is lightly loaded but - running a very large number of processes, adjust - the kern.maxproc tunable by defining it in + If the machine is lightly loaded but running a very + large number of processes, adjust the + kern.maxproc tunable by defining it in /boot/loader.conf. The tunable will not get adjusted until the system is rebooted. For more information about tuning tunables, see @@ -2091,18 +2106,18 @@ bindkey ^[[3~ delete-char # for xterm

The remote machine may be setting the terminal type to - something other than xterm which is - required by the &os; console. Alternatively the kernel - may have the wrong values for the width and height of the - terminal. + something other than xterm which is + required by the &os; console. Alternatively the kernel + may have the wrong values for the width and height of the + terminal. Check the value of the TERM - enviroment variable is xterm. If the + environment variable is xterm. If the remote machine does not support that try vt100. Run stty -a to check what the - kernel thinks the terminal dimensions are. If they are + kernel thinks the terminal dimensions are. If they are incorrect, they can be changed by running stty rows RR cols CC. @@ -2182,9 +2197,9 @@ bindkey ^[[3~ delete-char # for xterm

- This error message indicates that the - number of available file descriptors have been exhausted on the system. - Refer to the This error message indicates that the number of + available file descriptors have been exhausted on the + system. Refer to the kern.maxfiles section of the Tuning @@ -2302,8 +2317,7 @@ kern.timecounter.hardware: TSC -> i82 &man.witness.4; is conservative. A true positive report does not mean that a system is dead-locked; instead it should be understood as a warning - that a deadlock could - have happened here. + that a deadlock could have happened here. Problematic LORs tend to get @@ -2420,10 +2434,10 @@ kern.timecounter.hardware: TSC -> i82 Use SVN if custom patches to the ports tree are needed. Refer to Using - Subversion for details. + Subversion for details. - Use CTM, as described in Use CTM, as described in Using CTM to receive patches by email over an unreliable Internet connection. @@ -2457,10 +2471,10 @@ kern.timecounter.hardware: TSC -> i82 -STABLE, update the Ports Collection using the instructions in Using - the Ports Collection. If the system is up-to-date, - someone might have committed a change to the port - which works for -CURRENT but which - broke the port for -STABLE. + the Ports Collection. If the system is + up-to-date, someone might have committed a change to the + port which works for -CURRENT but + which broke the port for -STABLE. Submit a bug report, since the Ports Collection is supposed to work @@ -2476,8 +2490,8 @@ kern.timecounter.hardware: TSC -> i82 - First, make sure that the - Ports Collection is up-to-date. Errors that affect building + First, make sure that the Ports Collection is + up-to-date. Errors that affect building INDEX from an up-to-date copy of the Ports Collection are high-visibility and are thus almost always fixed immediately. @@ -2701,8 +2715,8 @@ kern.timecounter.hardware: TSC -> i82 to further reduce the size. See for more information. - To put any of these options into effect, follow the instructions - to To put any of these options into effect, follow the + instructions to build and install the new kernel. @@ -2735,7 +2749,7 @@ kern.timecounter.hardware: TSC -> i82 The make buildkernel command did not complete - successfuly. The make + successfully. The make buildkernel target relies on files generated by the make buildworld target to complete its job correctly. @@ -2749,9 +2763,10 @@ kern.timecounter.hardware: TSC -> i82 Only releases are guaranteed to be buildable, although &os;-STABLE builds fine the - majority of the time. Try re-fetching the source tree and see if the - problem goes away. Try using a different mirror in - case the previous one is having problems. + majority of the time. Try re-fetching the source tree + and see if the problem goes away. Try using a + different mirror in case the previous one is having + problems. @@ -2811,37 +2826,36 @@ kern.sched.name: ULE - The best way is to reinstall the operating system on the new disk, - then move the user data over. This is highly recommended - when tracking -STABLE for - more than one release or when updating a release instead - of installing a new one. Install booteasy on both - disks with &man.boot0cfg.8; and dual boot until you - are happy with the new configuration. Skip the next - paragraph to find out how to move the data after doing - this. + The best way is to reinstall the operating system on + the new disk, then move the user data over. This is + highly recommended when tracking + -STABLE for more than one release or + when updating a release instead of installing a new one. + Install booteasy on both disks with &man.boot0cfg.8; and + dual boot until you are happy with the new configuration. + Skip the next paragraph to find out how to move the data + after doing this. Alternatively, partition and label the new disk with either &man.sade.8; or &man.gpart.8;. If the disks are MBR-formatted, booteasy can be installed on both disks - with &man.boot0cfg.8; so that the computer can dual boot to the - old or new system after the copying is done. + with &man.boot0cfg.8; so that the computer can dual boot + to the old or new system after the copying is done. Once the new disk set up, the data cannot just be copied. Instead, use tools that - understand device files and syste flags, such as + understand device files and system flags, such as &man.dump.8;. Although it is recommended to move the data while in single-user mode, it is not required. When the disks are formatted with - UFS, never use anything but &man.dump.8; and - &man.restore.8; to move the root file system. These - commands should also be used when - moving a single partition to another empty - partition. The sequence of steps to use - dump to move the data from one - UFS partitions to a new + UFS, never use anything but + &man.dump.8; and &man.restore.8; to move the root file + system. These commands should also be used when moving a + single partition to another empty partition. The sequence + of steps to use dump to move the data + from one UFS partitions to a new partition is: @@ -2866,7 +2880,8 @@ kern.sched.name: ULE For example, to move /dev/ada1s1a with - /mnt as the temporary mount point, type: + /mnt as the temporary mount point, + type: &prompt.root; newfs /dev/ada1s1a &prompt.root; mount /dev/ada1s1a /mnt @@ -2902,9 +2917,9 @@ kern.sched.name: ULE &prompt.root; cd /mnt &prompt.root; dump 0af - / | restore rf - - The &man.cpio.1; and &man.pax.1; utilities are also available - for moving user data. These are known to lose file flag - information, so use them with caution. + The &man.cpio.1; and &man.pax.1; utilities are also + available for moving user data. These are known to lose + file flag information, so use them with caution. @@ -2931,14 +2946,14 @@ kern.sched.name: ULE When a large file is deleted the file still resides on disk until the kernel actually performs the deletion. This can cause a very simple race condition. Suppose - one large file is deleted and another large file is immediately created. - The first large file is not yet actually removed - from the physical disk, so the disk might not have enough - room for the second large file. This will produce an error that the - partition does not have enough space, even though - a large chunk of - space has just been released. A few seconds later, the file - creation works as expected. + one large file is deleted and another large file is + immediately created. The first large file is not yet + actually removed from the physical disk, so the disk might + not have enough room for the second large file. This will + produce an error that the partition does not have enough + space, even though a large chunk of space has just been + released. A few seconds later, the file creation works as + expected. If a system should crash after the kernel accepts a chunk of data for writing to disk, but before that data is @@ -3034,9 +3049,9 @@ kern.sched.name: ULE - &os; includes the Network File System NFS and - the &os; Ports Collection provides several FUSE applications - to support many other + &os; includes the Network File System + NFS and the &os; Ports Collection + provides several FUSE applications to support many other file systems. @@ -3052,7 +3067,7 @@ kern.sched.name: ULE example, if E is the second DOS partition on the second SCSI drive, there will be a device file for slice 5 in - /dev. To mount it: + /dev. To mount it: &prompt.root; mount -t msdosfs /dev/da1s5 /dos/e @@ -3079,8 +3094,8 @@ kern.sched.name: ULE - To boot &os; using GRUB, add the - following to either + To boot &os; using GRUB, + add the following to either /boot/grub/menu.lst or /boot/grub/grub.conf, depending upon which is used by the &linux; distribution. @@ -3111,9 +3126,9 @@ kern.sched.name: ULE then boot LILO from BootEasy. - This is recommended when running &windows; and &linux; as it - makes it simpler to get &linux; - booting again if &windows; is reinstalled. + This is recommended when running &windows; and &linux; + as it makes it simpler to get &linux; booting again if + &windows; is reinstalled. @@ -3125,10 +3140,10 @@ kern.sched.name: ULE - This cannot be accomplished with the standard boot manager - without rewriting it. There are a number of other boot - managers in the sysutils category of the Ports - Collection. + This cannot be accomplished with the standard boot + manager without rewriting it. There are a number of other + boot managers in the sysutils + category of the Ports Collection. @@ -3145,8 +3160,8 @@ kern.sched.name: ULE If the drive will only be used with &os; systems, partition it with UFS or - ZFS. This will provide long filename support, - improvement in performance, and stability. If + ZFS. This will provide long filename + support, improvement in performance, and stability. If the drive will be used by other operating systems, a more portable choice, such as msdosfs, is better. @@ -3178,9 +3193,8 @@ kern.sched.name: ULE - The type of device - to mount must be specified. This is described in the Handbook - section on The type of device to mount must be specified. This + is described in the Handbook section on Using Data CDs. @@ -3342,26 +3356,27 @@ kern.sched.name: ULE - This is due to how these commands actually work. du - goes through the directory tree, measures how large each - file is, and presents the totals. df - just asks the file system how much space it has left. - They seem to be the same thing, but a file without a - directory entry will affect df but not + This is due to how these commands actually work. + du goes through the directory tree, + measures how large each file is, and presents the totals. + df just asks the file system how much + space it has left. They seem to be the same thing, but a + file without a directory entry will affect + df but not du. - When a program is using a file, and the file is deleted, - the file is not really removed from the file system - until the program stops using it. The file is immediately - deleted from the directory listing, however. As an example, - consider a file that is large - enough that its presence affects the output of - du and df. If this file is deleted - while using more on it, + When a program is using a file, and the file is + deleted, the file is not really removed from the file + system until the program stops using it. The file is + immediately deleted from the directory listing, however. + As an example, consider a file that is large enough that + its presence affects the output of + du and df. If this + file is deleted while using more on it, more does not immediately choke and complain that it cannot view the file. The entry is - removed from the directory so no other program or - user can access it. However, du shows that it + removed from the directory so no other program or user can + access it. However, du shows that it is gone as it has walked the directory tree and the file is not listed. df shows that it is still there, as the file system knows that @@ -3391,7 +3406,7 @@ kern.sched.name: ULE - This sectionThis section of the Handbook describes how to do this. @@ -3625,14 +3640,14 @@ kern.sched.name: ULE The primary configuration file is - /etc/defaults/rc.conf which is described in - &man.rc.conf.5;. System startup scripts such as - /etc/rc and - /etc/rc.d, which are described in &man.rc.8;, - include this file. Do not edit this + /etc/defaults/rc.conf which is + described in &man.rc.conf.5;. System startup scripts + such as /etc/rc and + /etc/rc.d, which are described in + &man.rc.8;, include this file. Do not edit this file! Instead, to edit an entry in - /etc/defaults/rc.conf, copy the line into - /etc/rc.conf and change it + /etc/defaults/rc.conf, copy the line + into /etc/rc.conf and change it there. For example, if to start &man.named.8;, the @@ -3693,11 +3708,13 @@ kern.sched.name: ULE - This is a security feature. In order to su - to root, or any - other account with superuser privileges, the user account must be a member of - the wheel - group. If this feature were not there, anybody with an + This is a security feature. In order to + su to + root, or any + other account with superuser privileges, the user account + must be a member of the + wheel group. + If this feature were not there, anybody with an account on a system who also found out root's password would be able to gain superuser level access to the system. @@ -3761,7 +3778,8 @@ kern.sched.name: ULE See the Handbook - entry on printing for troubleshooting tips. + entry on printing for troubleshooting + tips. @@ -3915,15 +3933,16 @@ options SYSVMSG # enable for class="username">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 + /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. Mount the specific partition in this - case and then chroot to it. For example, replace mount - -urw / with mount /dev/ada0p1 /mnt; - chroot /mnt for a system on + case and then chroot to it. For example, replace + mount -urw / with + mount /dev/ada0p1 /mnt; chroot /mnt + for a system on ada0p1. @@ -4089,10 +4108,11 @@ options SYSVMSG # enable for &prompt.root; sysctl kern.securelevel - The security level cannot be lowered in multi-user mode, so boot - to single-user 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 + The security level cannot be lowered in multi-user + mode, so boot to single-user 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 @@ -4117,10 +4137,11 @@ options SYSVMSG # enable for &prompt.root; sysctl kern.securelevel - The security level cannot be lowered in multi-user mode. Either boot - to single-user mode to change the date or change the - security level in /etc/rc.conf and - reboot. See the &man.init.8; manual page for details on + The security level cannot be lowered in multi-user + mode. Either boot to single-user mode to change the date + or change the security level in + /etc/rc.conf and 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 @@ -4389,9 +4410,10 @@ options SYSVMSG # enable for information, see at the &man.init.8; manual page. There are two solutions to the problem: set the - securelevel back down to zero or run &man.xdm.1; - (or an alternative display manager) at boot time before - the securelevel is raised. + securelevel back down to zero or run + &man.xdm.1; (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. @@ -4464,7 +4486,7 @@ options SYSVMSG # enable for /etc/X11/xorg.conf, as seen in this example: - Section "InputDevice" + Section "InputDevice" Identifier "Mouse1" Driver "mouse" Option "Protocol" "auto" @@ -4590,23 +4612,24 @@ ttyvb "/usr/libexec/getty Pc" The more virtual terminals, the more resources that are used. This can be - problematic on systems with 8 MB RAM or less. Consider - changing secure to + problematic on systems with 8 MB RAM or less. + Consider changing secure to insecure. Versions of &os; prior to 9.0 used the cons25 terminal type, and not xterm. Use the format of existing entries in - when adding entries to /etc/ttys. + when adding entries to + /etc/ttys. In order to run an X server, at least one virtual - terminal must be left to off for it to use. This - means that only eleven of the Alt-function keys can be - used as virtual consoles so that one is left for the - X server. + terminal must be left to off for it + to use. This means that only eleven of the Alt-function + keys can be used as virtual consoles so that one is left + for the X server. For example, to run X and eleven virtual consoles, the @@ -4738,9 +4761,9 @@ ttyvb "/usr/libexec/getty Pc" - The mouse and the mouse driver may have - become out of synchronization. In rare cases, the driver may also erroneously report - synchronization errors: + The mouse and the mouse driver may have become out of + synchronization. In rare cases, the driver may also + erroneously report synchronization errors: psmintr: out of sync (xxxx != yyyy) @@ -4760,8 +4783,8 @@ ttyvb "/usr/libexec/getty Pc" Type - xmodmap -e "pointer = 3 2 1". Add this command to - ~/.xinitrc or + xmodmap -e "pointer = 3 2 1". Add this + command to ~/.xinitrc or ~/.xsession to make it happen automatically. @@ -4846,8 +4869,8 @@ ttyvb "/usr/libexec/getty Pc" keycode 116 = F14 keycode 117 = F15 - For the x11-wm/fvwm2 desktop manager, - one could map the keys so that + For the x11-wm/fvwm2 desktop + manager, one could map the keys so that F13 iconifies or de-iconifies the window the cursor is in, F14 brings the window the cursor is in to the front or, if it is already @@ -4960,9 +4983,8 @@ Key F15 A A Menu Wo xlink:href="&url.books.handbook;/userppp.html">Handbook entry on user PPP. - If the - connection to the Internet is over Ethernet, use &man.natd.8;. - A tutorial can be found in the If the connection to the Internet is over Ethernet, + use &man.natd.8;. A tutorial can be found in the natd section of the Handbook. @@ -5009,7 +5031,8 @@ Key F15 A A Menu Wo *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***