Date: Sat, 1 Aug 2015 15:47:46 +0000 (UTC) From: Bjoern Heidotting <bhd@FreeBSD.org> 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 Message-ID: <201508011547.t71FlkOg009754@repo.freebsd.org>
next in thread | raw e-mail | index | archive | help
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 @@ <!ENTITY rel3.relengdate "August 2009"> ]> <book xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en"> - <info><title>Frequently Asked Questions for &os; - &rel3.relx;, &rel2.relx; and &rel.relx;</title> + <info> + <title>Frequently Asked Questions for &os; + &rel3.relx;, &rel2.relx; and &rel.relx;</title> <author><orgname>The &os; Documentation Project</orgname></author> @@ -72,11 +73,11 @@ <abstract> <para>This is the Frequently Asked Questions - <acronym>FAQ</acronym> for &os; versions &rel3.relx;, &rel2.relx; - and &rel.relx;. Every effort has been made to make this <acronym>FAQ</acronym> - as informative as possible; if you have any suggestions as to - how it may be improved, send them to the - &a.doc;.</para> + <acronym>FAQ</acronym> for &os; versions &rel3.relx;, + &rel2.relx; and &rel.relx;. Every effort has been made to + make this <acronym>FAQ</acronym> as informative as possible; + if you have any suggestions as to how it may be improved, send + them to the &a.doc;.</para> <para>The latest version of this document is always available from the <link @@ -141,13 +142,12 @@ </question> <answer> - <para>Yes. Those restrictions do not control how - the code is used, but how to treat the &os; Project itself. + <para>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 <link xlink:href="http://www.FreeBSD.org/copyright/freebsd-license.html">license</link>; - and can be summarized like - this:</para> + and can be summarized like this:</para> <itemizedlist> <listitem> @@ -211,15 +211,15 @@ xlink:href="http://www.FreeBSD.org/ports/">Ports Collection</link>.</para> - <para>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.</para> + <para>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.</para> <para>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</link>, a &os;-based desktop distribution. Non-&unix; users should expect to invest some additional time learning the - &unix; way of doing things. This <acronym>FAQ</acronym> and the <link + &unix; way of doing things. This <acronym>FAQ</acronym> + and the <link xlink:href="&url.books.handbook;/index.html">&os; Handbook</link> are excellent places to start.</para> </answer> @@ -356,7 +357,8 @@ <emphasis>-CURRENT</emphasis> snapshot. Releases can come from either branch, but <emphasis>-CURRENT</emphasis> is meant for users who are prepared for its increased - volatility, relative to <emphasis>-STABLE</emphasis>.</para> + volatility, relative to + <emphasis>-STABLE</emphasis>.</para> <para>Releases are made <link linkend="release-freq">every few months</link>. While many people stay more @@ -923,8 +925,9 @@ compressed files, uncompress them, and then copy the appropriate documents into place.</para> - <para>For example, the split HTML version of the <acronym>FAQ</acronym>, - compressed using &man.bzip2.1;, can be found in + <para>For example, the split HTML version of the + <acronym>FAQ</acronym>, compressed using &man.bzip2.1;, + can be found in <filename>doc/en_US.ISO8859-1/books/faq/book.html-split.tar.bz2</filename> To download and uncompress that file, type:</para> @@ -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 - <literal>##freebsd-lang</literal> 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 <literal>##freebsd-lang</literal> as appropriate.</para> </listitem> @@ -1080,11 +1082,19 @@ <chapter xml:id="install"> <info> - <title>Installation</title> + <title>Installation</title> - <author><personname><firstname>Nik</firstname><surname>Clayton</surname></personname><affiliation> - <address><email>nik@FreeBSD.org</email></address> - </affiliation></author> + <author> + <personname> + <firstname>Nik</firstname> + <surname>Clayton</surname> + </personname> + <affiliation> + <address> + <email>nik@FreeBSD.org</email> + </address> + </affiliation> + </author> </info> <qandaset> @@ -1100,8 +1110,8 @@ <para>&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.</para> </answer> </qandaentry> @@ -1114,8 +1124,8 @@ <answer> <para>On the <link xlink:href="http://www.freebsd.org/where.html">Getting - &os;</link> page, select <literal>[iso]</literal> next to - the architecture that matches the hardware.</para> + &os;</link> page, select <literal>[iso]</literal> next + to the architecture that matches the hardware.</para> <para>Any of the following can be used:</para> @@ -1175,27 +1185,28 @@ <qandaentry> <question xml:id="floppy-image-too-large"> - <para>What do I do if the install image does not boot?</para> + <para>What do I do if the install image does not + boot?</para> </question> <answer> <para>This can be caused by not downloading the image in - <emphasis>binary</emphasis> mode when using - <acronym>FTP</acronym>.</para> + <emphasis>binary</emphasis> mode when using + <acronym>FTP</acronym>.</para> - <para>Some FTP clients default their transfer mode to - <emphasis>ascii</emphasis> 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 - <emphasis>exactly</emphasis> that on the server, then - the download process is suspect.</para> - - <para>When using a command line FTP client, type <emphasis>binary</emphasis> at - the FTP command prompt after getting connected to the - server and before starting the download of the - image.</para> + <para>Some FTP clients default their transfer mode to + <emphasis>ascii</emphasis> 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 <emphasis>exactly</emphasis> that on the + server, then the download process is suspect.</para> + + <para>When using a command line FTP client, type + <emphasis>binary</emphasis> at the FTP command prompt + after getting connected to the server and before + starting the download of the image.</para> </answer> </qandaentry> @@ -1403,8 +1414,8 @@ buildworld</command> and <command>make buildkernel</command> to update the kernel.</para> - <para>Boot the system by specifying the kernel directly at the - second stage, pressing any key when the + <para>Boot the system by specifying the kernel directly at + the second stage, pressing any key when the <literal>|</literal> shows up before loader is started.</para> </answer> @@ -1439,8 +1450,8 @@ <answer> <para>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; <link xlink:href="&rel.current.hardware;">&rel.current;</link> or <link @@ -1474,7 +1485,8 @@ 4 GB of memory (and usually less than that because of PCI address space) and &i386; with PAE supports at most 64 GB memory. As of &os; 10, AMD64 - platforms support up to 4 TB of physical memory.</para> + platforms support up to 4 TB of physical + memory.</para> </answer> </qandaentry> @@ -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:</para> + file, PAE can be enabled by adding the following + line:</para> <programlisting>options PAE</programlisting> @@ -1663,12 +1676,12 @@ &man.chio.1;.</para> <para>While - <application>AMANDA</application> 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.</para> + <application>AMANDA</application> 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.</para> </answer> </qandaentry> @@ -1687,8 +1700,8 @@ drive. See &man.burncd.8; for details.</para> <para>&os; also supports any SCSI CD-R or CD-RW drives. - Install the <package>sysutils/cdrtools</package> - port or package, then use <command>cdrecord</command>.</para> + Install the <package>sysutils/cdrtools</package> port or + package, then use <command>cdrecord</command>.</para> </answer> </qandaentry> </qandaset> @@ -1706,10 +1719,10 @@ <answer> <para>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:</para> + &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:</para> <screen>&prompt.root; <userinput>moused -p /dev/xxxx -t yyyy</userinput> &prompt.root; <userinput>vidcontrol -m on</userinput></screen> @@ -1735,7 +1748,8 @@ <para>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 <acronym>FAQ</acronym> + other programs such as X Windows. Refer to the + <acronym>FAQ</acronym> <link linkend="x-and-moused">Why does my mouse not work with X?</link> for more details on this issue.</para> </answer> @@ -1749,9 +1763,8 @@ <answer> <para>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 <link + However, it is possible to copy and paste. Once the + mouse daemon is running as described in the <link linkend="moused">previous question</link>, 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 <quote>extend</quote> the selected region of text.</para> - <para>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 + <para>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.</para> </answer> </qandaentry> @@ -1883,8 +1896,8 @@ bindkey ^[[3~ delete-char # for xterm</p <para>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.</para> + to build a PAE enabled kernel. See the entry on memory + limits for more information.</para> <para>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</p <para>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 <acronym>FAQ</acronym> readers get to use these bits of code - (that is what -CURRENT is for).</para> + general <acronym>FAQ</acronym> readers get to use + these bits of code (that is what -CURRENT is + for).</para> </listitem> </orderedlist> @@ -1937,8 +1951,8 @@ bindkey ^[[3~ delete-char # for xterm</p <para>For example, if <command>make buildworld</command> fails while trying to compile <filename>ls.c</filename> into - <filename>ls.o</filename> and, when run again, it fails in the - same place, this is a broken build. Try + <filename>ls.o</filename> 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.</para> @@ -1954,8 +1968,8 @@ bindkey ^[[3~ delete-char # for xterm</p <orderedlist> <listitem> - <para>The hard disks might be overheating: Check that the - fans are still working, as the disk and + <para>The hard disks might be overheating: Check that + the fans are still working, as the disk and other hardware might be overheating.</para> </listitem> @@ -2008,10 +2022,11 @@ bindkey ^[[3~ delete-char # for xterm</p </listitem> </orderedlist> - <para>Read the section on <link linkend="signal11">Signal 11</link> - for a further explanation and a discussion on how - memory testing software or hardware can still pass faulty - memory. There is an extensive <acronym>FAQ</acronym> on this at <link + <para>Read the section on + <link linkend="signal11">Signal 11</link> for a further + explanation and a discussion on how memory testing + software or hardware can still pass faulty memory. There + is an extensive <acronym>FAQ</acronym> on this at <link xlink:href="http://www.bitwizard.nl/sig11/">the SIG11 problem <acronym>FAQ</acronym></link>.</para> @@ -2037,16 +2052,16 @@ bindkey ^[[3~ delete-char # for xterm</p <acronym>FAQ</acronym> section on <link linkend="kernel-panic-troubleshooting">kernel panics</link>, 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.</para> </answer> </qandaentry> <qandaentry> <question xml:id="proc-table-full"> - <para>What is the meaning of the error <errorname>maxproc limit - exceeded by uid %i, please see tuning(7) and + <para>What is the meaning of the error <errorname>maxproc + limit exceeded by uid %i, please see tuning(7) and login.conf(5)</errorname>?</para> </question> @@ -2068,9 +2083,9 @@ bindkey ^[[3~ delete-char # for xterm</p section refers to open files, the same limits apply to processes.</para> - <para>If the machine is lightly loaded but - running a very large number of processes, adjust - the <varname>kern.maxproc</varname> tunable by defining it in + <para>If the machine is lightly loaded but running a very + large number of processes, adjust the + <varname>kern.maxproc</varname> tunable by defining it in <filename>/boot/loader.conf</filename>. 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</p <answer> <para>The remote machine may be setting the terminal type to - something other than <literal>xterm</literal> which is - required by the &os; console. Alternatively the kernel - may have the wrong values for the width and height of the - terminal.</para> + something other than <literal>xterm</literal> which is + required by the &os; console. Alternatively the kernel + may have the wrong values for the width and height of the + terminal.</para> <para>Check the value of the <envar>TERM</envar> - enviroment variable is <literal>xterm</literal>. If the + environment variable is <literal>xterm</literal>. If the remote machine does not support that try <literal>vt100</literal>.</para> <para>Run <command>stty -a</command> 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 <command>stty rows <replaceable>RR</replaceable> cols <replaceable>CC</replaceable></command>.</para> @@ -2182,9 +2197,9 @@ bindkey ^[[3~ delete-char # for xterm</p </question> <answer> - <para>This error message indicates that the - number of available file descriptors have been exhausted on the system. - Refer to the <link + <para>This error message indicates that the number of + available file descriptors have been exhausted on the + system. Refer to the <link xlink:href="&url.books.handbook;/configtuning-kernel-limits.html#kern-maxfiles">kern.maxfiles</link> section of the <link xlink:href="&url.books.handbook;/configtuning-kernel-limits.html">Tuning @@ -2302,8 +2317,7 @@ kern.timecounter.hardware: TSC -> i82 &man.witness.4; is conservative. A true positive report <emphasis>does not</emphasis> mean that a system is dead-locked; instead it should be understood as a warning - that a deadlock could - have happened here.</para> + that a deadlock could have happened here.</para> <note> <para>Problematic <acronym>LOR</acronym>s tend to get @@ -2420,10 +2434,10 @@ kern.timecounter.hardware: TSC -> i82 <para>Use SVN if custom patches to the ports tree are needed. Refer to <link xlink:href="&url.books.handbook;/svn.html">Using - Subversion</link> for details.</para> + Subversion</link> for details.</para> </listitem> <listitem> - <para>Use <acronym>CTM</acronym>, as described in <link + <para>Use <acronym>CTM</acronym>, as described in <link xlink:href="&url.books.handbook;/ctm.html">Using <acronym>CTM</acronym></link> to receive patches by email over an unreliable Internet connection.</para> @@ -2457,10 +2471,10 @@ kern.timecounter.hardware: TSC -> i82 <emphasis>-STABLE</emphasis>, update the Ports Collection using the instructions in <link xlink:href="&url.books.handbook;/ports-using.html">Using - the Ports Collection</link>. If the system is up-to-date, - someone might have committed a change to the port - which works for <emphasis>-CURRENT</emphasis> but which - broke the port for <emphasis>-STABLE</emphasis>. + the Ports Collection</link>. If the system is + up-to-date, someone might have committed a change to the + port which works for <emphasis>-CURRENT</emphasis> but + which broke the port for <emphasis>-STABLE</emphasis>. <link xlink:href="https://bugs.FreeBSD.org/submit/">Submit</link>; a bug report, since the Ports Collection is supposed to work @@ -2476,8 +2490,8 @@ kern.timecounter.hardware: TSC -> i82 </question> <answer> - <para>First, make sure that the - Ports Collection is up-to-date. Errors that affect building + <para>First, make sure that the Ports Collection is + up-to-date. Errors that affect building <filename>INDEX</filename> from an up-to-date copy of the Ports Collection are high-visibility and are thus almost always fixed immediately.</para> @@ -2701,8 +2715,8 @@ kern.timecounter.hardware: TSC -> i82 to further reduce the size. See <xref linkend="make-kernel"/> for more information.</para> - <para>To put any of these options into effect, follow the instructions - to <link + <para>To put any of these options into effect, follow the + instructions to <link xlink:href="&url.books.handbook;/kernelconfig-building.html">build and install</link> the new kernel.</para> @@ -2735,7 +2749,7 @@ kern.timecounter.hardware: TSC -> i82 <listitem> <para>The <command>make buildkernel</command> command did not complete - successfuly. The <command>make + successfully. The <command>make buildkernel</command> target relies on files generated by the <command>make buildworld</command> target to complete its job correctly.</para> @@ -2749,9 +2763,10 @@ kern.timecounter.hardware: TSC -> i82 Only releases are guaranteed to be buildable, although <link linkend="stable">&os;-STABLE</link> 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.</para> + 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.</para> </listitem> </itemizedlist> </answer> @@ -2811,37 +2826,36 @@ kern.sched.name: ULE</screen> </question> <answer> - <para>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 <emphasis>-STABLE</emphasis> 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.</para> + <para>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 + <emphasis>-STABLE</emphasis> 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.</para> <para>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.</para> + with &man.boot0cfg.8; so that the computer can dual boot + to the old or new system after the copying is done.</para> <para>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.</para> <para>When the disks are formatted with - <acronym>UFS</acronym>, 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 - <command>dump</command> to move the data from one - <acronym>UFS</acronym> partitions to a new + <acronym>UFS</acronym>, 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 <command>dump</command> to move the data + from one <acronym>UFS</acronym> partitions to a new partition is:</para> <procedure> @@ -2866,7 +2880,8 @@ kern.sched.name: ULE</screen> <para>For example, to move <filename>/dev/ada1s1a</filename> with - <filename>/mnt</filename> as the temporary mount point, type:</para> + <filename>/mnt</filename> as the temporary mount point, + type:</para> <screen>&prompt.root; <userinput>newfs /dev/ada1s1a</userinput> &prompt.root; <userinput>mount /dev/ada1s1a /mnt</userinput> @@ -2902,9 +2917,9 @@ kern.sched.name: ULE</screen> &prompt.root; <userinput>cd /mnt</userinput> &prompt.root; <userinput>dump 0af - / | restore rf -</userinput></screen> - <para>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.</para> + <para>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.</para> </answer> </qandaentry> @@ -2931,14 +2946,14 @@ kern.sched.name: ULE</screen> 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.</para> + 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.</para> <para>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</screen> </varlistentry> </variablelist> - <para>&os; includes the Network File System <acronym>NFS</acronym> and - the &os; Ports Collection provides several FUSE applications - to support many other + <para>&os; includes the Network File System + <acronym>NFS</acronym> and the &os; Ports Collection + provides several FUSE applications to support many other file systems.</para> </answer> </qandaentry> @@ -3052,7 +3067,7 @@ kern.sched.name: ULE</screen> example, if <literal>E</literal> is the second DOS partition on the second SCSI drive, there will be a device file for <quote>slice 5</quote> in - <filename>/dev</filename>. To mount it:</para> + <filename>/dev</filename>. To mount it:</para> <screen>&prompt.root; <userinput>mount -t msdosfs /dev/da1s5 /dos/e</userinput></screen> </answer> @@ -3079,8 +3094,8 @@ kern.sched.name: ULE</screen> </question> <answer> - <para>To boot &os; using <application>GRUB</application>, add the - following to either + <para>To boot &os; using <application>GRUB</application>, + add the following to either <filename>/boot/grub/menu.lst</filename> or <filename>/boot/grub/grub.conf</filename>, depending upon which is used by the &linux; distribution.</para> @@ -3111,9 +3126,9 @@ kern.sched.name: ULE</screen> then boot LILO from <application>BootEasy</application>.</para> - <para>This is recommended when running &windows; and &linux; as it - makes it simpler to get &linux; - booting again if &windows; is reinstalled.</para> + <para>This is recommended when running &windows; and &linux; + as it makes it simpler to get &linux; booting again if + &windows; is reinstalled.</para> </answer> </qandaentry> @@ -3125,10 +3140,10 @@ kern.sched.name: ULE</screen> </question> <answer> - <para>This cannot be accomplished with the standard boot manager - without rewriting it. There are a number of other boot - managers in the <filename>sysutils</filename> category of the Ports - Collection.</para> + <para>This cannot be accomplished with the standard boot + manager without rewriting it. There are a number of other + boot managers in the <filename>sysutils</filename> + category of the Ports Collection.</para> </answer> </qandaentry> @@ -3145,8 +3160,8 @@ kern.sched.name: ULE</screen> <para>If the drive will only be used with &os; systems, partition it with <acronym>UFS</acronym> or - <acronym>ZFS</acronym>. This will provide long filename support, - improvement in performance, and stability. If + <acronym>ZFS</acronym>. 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.</para> @@ -3178,9 +3193,8 @@ kern.sched.name: ULE</screen> </question> <answer> - <para>The type of device - to mount must be specified. This is described in the Handbook - section on <link + <para>The type of device to mount must be specified. This + is described in the Handbook section on <link xlink:href="&url.books.handbook;/creating-cds.html#mounting-cd">Using Data CDs</link>.</para> </answer> @@ -3342,26 +3356,27 @@ kern.sched.name: ULE</screen> </question> <answer> - <para>This is due to how these commands actually work. <command>du</command> - goes through the directory tree, measures how large each - file is, and presents the totals. <command>df</command> - 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 <command>df</command> but not + <para>This is due to how these commands actually work. + <command>du</command> goes through the directory tree, + measures how large each file is, and presents the totals. + <command>df</command> 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 + <command>df</command> but not <command>du</command>.</para> - <para>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 - <command>du</command> and <command>df</command>. If this file is deleted - while using <command>more</command> on it, + <para>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 + <command>du</command> and <command>df</command>. If this + file is deleted while using <command>more</command> on it, <command>more</command> 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, <command>du</command> shows that it + removed from the directory so no other program or user can + access it. However, <command>du</command> shows that it is gone as it has walked the directory tree and the file is not listed. <command>df</command> shows that it is still there, as the file system knows that @@ -3391,7 +3406,7 @@ kern.sched.name: ULE</screen> </question> <answer> - <para>This section<link + <para>This section <link xlink:href="&url.books.handbook;/adding-swap-space.html">of the Handbook</link> describes how to do this.</para> </answer> @@ -3625,14 +3640,14 @@ kern.sched.name: ULE</screen> <answer> <para>The primary configuration file is - <filename>/etc/defaults/rc.conf</filename> which is described in - &man.rc.conf.5;. System startup scripts such as - <filename>/etc/rc</filename> and - <filename>/etc/rc.d</filename>, which are described in &man.rc.8;, - include this file. <emphasis>Do not edit this + <filename>/etc/defaults/rc.conf</filename> which is + described in &man.rc.conf.5;. System startup scripts + such as <filename>/etc/rc</filename> and + <filename>/etc/rc.d</filename>, which are described in + &man.rc.8;, include this file. <emphasis>Do not edit this file!</emphasis> Instead, to edit an entry in - <filename>/etc/defaults/rc.conf</filename>, copy the line into - <filename>/etc/rc.conf</filename> and change it + <filename>/etc/defaults/rc.conf</filename>, copy the line + into <filename>/etc/rc.conf</filename> and change it there.</para> <para>For example, if to start &man.named.8;, the @@ -3693,11 +3708,13 @@ kern.sched.name: ULE</screen> </question> <answer> - <para>This is a security feature. In order to <command>su</command> - to <systemitem class="username">root</systemitem>, or any - other account with superuser privileges, the user account must be a member of - the <systemitem class="groupname">wheel</systemitem> - group. If this feature were not there, anybody with an + <para>This is a security feature. In order to + <command>su</command> to + <systemitem class="username">root</systemitem>, or any + other account with superuser privileges, the user account + must be a member of the + <systemitem class="groupname">wheel</systemitem> group. + If this feature were not there, anybody with an account on a system who also found out <systemitem class="username">root</systemitem>'s password would be able to gain superuser level access to the system.</para> @@ -3761,7 +3778,8 @@ kern.sched.name: ULE</screen> <answer> <para>See the <link xlink:href="&url.books.handbook;/printing.html">Handbook - entry on printing</link> for troubleshooting tips.</para> + entry on printing</link> for troubleshooting + tips.</para> </answer> </qandaentry> @@ -3915,15 +3933,16 @@ options SYSVMSG # enable for class="username">root</systemitem> password when entering the single-user mode, it means that the console has been marked as <literal>insecure</literal> in - <filename>/etc/ttys</filename>. In this case, it will be - required to boot from a &os; installation disk, choose - the <guimenuitem>Live CD</guimenuitem> or + <filename>/etc/ttys</filename>. In this case, it will + be required to boot from a &os; installation disk, + choose the <guimenuitem>Live CD</guimenuitem> or <guimenuitem>Shell</guimenuitem> 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 <command>mount - -urw /</command> with <command>mount /dev/ada0p1 /mnt; - chroot /mnt</command> for a system on + case and then chroot to it. For example, replace + <command>mount -urw /</command> with + <command>mount /dev/ada0p1 /mnt; chroot /mnt</command> + for a system on <replaceable>ada0p1</replaceable>.</para> </note> @@ -4089,10 +4108,11 @@ options SYSVMSG # enable for <screen>&prompt.root; <userinput>sysctl kern.securelevel</userinput></screen> - <para>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 <filename>/etc/rc.conf</filename> then - reboot. See the &man.init.8; manual page for details on + <para>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 + <filename>/etc/rc.conf</filename> then reboot. See the + &man.init.8; manual page for details on <literal>securelevel</literal>, and see <filename>/etc/defaults/rc.conf</filename> and the &man.rc.conf.5; manual page for more information on @@ -4117,10 +4137,11 @@ options SYSVMSG # enable for <screen>&prompt.root; <userinput>sysctl kern.securelevel</userinput></screen> - <para>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 <filename>/etc/rc.conf</filename> and - reboot. See the &man.init.8; manual page for details on + <para>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 + <filename>/etc/rc.conf</filename> and reboot. See the + &man.init.8; manual page for details on <literal>securelevel</literal>, and see <filename>/etc/defaults/rc.conf</filename> 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.</para> <para>There are two solutions to the problem: set the - <literal>securelevel</literal> back down to zero or run &man.xdm.1; - (or an alternative display manager) at boot time before - the <literal>securelevel</literal> is raised.</para> + <literal>securelevel</literal> back down to zero or run + &man.xdm.1; (or an alternative display manager) at boot + time before the <literal>securelevel</literal> is + raised.</para> <para>See <xref linkend="xdm-boot"/> for more information about running &man.xdm.1; at boot time.</para> @@ -4464,7 +4486,7 @@ options SYSVMSG # enable for <filename>/etc/X11/xorg.conf</filename>, as seen in this example:</para> - <programlisting>Section "InputDevice" + <programlisting>Section "InputDevice" Identifier "Mouse1" Driver "mouse" Option "Protocol" "auto" @@ -4590,23 +4612,24 @@ ttyvb "/usr/libexec/getty Pc" <para>The more virtual terminals, the more resources that are used. This can be - problematic on systems with 8 MB RAM or less. Consider - changing <literal>secure</literal> to + problematic on systems with 8 MB RAM or less. + Consider changing <literal>secure</literal> to <literal>insecure</literal>.</para> <note> <para>Versions of &os; prior to 9.0 used the <quote> cons25</quote> terminal type, and not <quote> xterm</quote>. Use the format of existing entries in - when adding entries to <filename>/etc/ttys</filename>.</para> + when adding entries to + <filename>/etc/ttys</filename>.</para> </note> <important> <para>In order to run an X server, at least one virtual - terminal must be left to <literal>off</literal> 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.</para> + terminal must be left to <literal>off</literal> 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.</para> </important> <para>For example, to run X and eleven virtual consoles, the @@ -4738,9 +4761,9 @@ ttyvb "/usr/libexec/getty Pc" </question> <answer> - <para>The mouse and the mouse driver may have - become out of synchronization. In rare cases, the driver may also erroneously report - synchronization errors:</para> + <para>The mouse and the mouse driver may have become out of + synchronization. In rare cases, the driver may also + erroneously report synchronization errors:</para> <programlisting>psmintr: out of sync (xxxx != yyyy)</programlisting> @@ -4760,8 +4783,8 @@ ttyvb "/usr/libexec/getty Pc" <answer> <para>Type - <command>xmodmap -e "pointer = 3 2 1"</command>. Add this command to - <filename>~/.xinitrc</filename> or + <command>xmodmap -e "pointer = 3 2 1"</command>. Add this + command to <filename>~/.xinitrc</filename> or <filename>~/.xsession</filename> to make it happen automatically.</para> </answer> @@ -4846,8 +4869,8 @@ ttyvb "/usr/libexec/getty Pc" keycode 116 = F14 keycode 117 = F15</programlisting> - <para>For the <package>x11-wm/fvwm2</package> desktop manager, - one could map the keys so that + <para>For the <package>x11-wm/fvwm2</package> desktop + manager, one could map the keys so that <keycap>F13</keycap> iconifies or de-iconifies the window the cursor is in, <keycap>F14</keycap> 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</link>.</para> - <para>If the - connection to the Internet is over Ethernet, use &man.natd.8;. - A tutorial can be found in the <link + <para>If the connection to the Internet is over Ethernet, + use &man.natd.8;. A tutorial can be found in the <link xlink:href="&url.books.handbook;/firewalls-ipfw.html#network-natd">natd</link> section of the Handbook.</para> </answer> @@ -5009,7 +5031,8 @@ Key F15 A A Menu Wo *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201508011547.t71FlkOg009754>