os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Reduce redundant markup and word and other minor problems reported by

Browse source 
igor.  Limited additional checking was done of the surrounding content.

Approved by:	jkois (mentor, before merge conflict resolution)
This commit is contained in:
Eitan Adler 2012-11-11 22:29:01 +00:00
parent a77e6637c3
commit 61606d36dd
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=39981
1 changed files with 41 additions and 42 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

83
en_US.ISO8859-1/books/faq/book.xml
View file

@ -923,7 +923,7 @@
<para>Where the format is <para>Where the format is
<literal>html-split</literal>, the files are bundled <literal>html-split</literal>, the files are bundled
up using &man.tar.1;. The resulting up using &man.tar.1;. The resulting
<filename>.tar</filename> file is then compressed <filename>.tar</filename> is then compressed
using the compression schemes detailed in the next using the compression schemes detailed in the next
point.</para> point.</para>
</listitem> </listitem>
@ -986,9 +986,9 @@
appropriate documents into place.</para> appropriate documents into place.</para>
<para>For example, the split HTML version of the FAQ, <para>For example, the split HTML version of the FAQ,
compressed using &man.bzip2.1;, can be found in the compressed using &man.bzip2.1;, can be found in
<filename>doc/en_US.ISO8859-1/books/faq/book.html-split.tar.bz2</filename> <filename>doc/en_US.ISO8859-1/books/faq/book.html-split.tar.bz2</filename>
file. To download and uncompress that file you would have To download and uncompress that file you would have
to do this.</para> to do this.</para>
<screen>&prompt.root; <userinput>fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/en_US.ISO8859-1/books/faq/book.html-split.tar.bz2</userinput> <screen>&prompt.root; <userinput>fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/en_US.ISO8859-1/books/faq/book.html-split.tar.bz2</userinput>
@ -2241,7 +2241,7 @@
drive. See &man.burncd.8; for details.</para> drive. See &man.burncd.8; for details.</para>
<para>&os; also supports any SCSI CD-R or CD-RW drives. <para>&os; also supports any SCSI CD-R or CD-RW drives.
Install and use the <command>cdrecord</command> command Install and use <command>cdrecord</command>
from the ports or packages system, and make sure that you from the ports or packages system, and make sure that you
have the <devicename>pass</devicename> device compiled in have the <devicename>pass</devicename> device compiled in
your kernel.</para> your kernel.</para>
@ -2766,8 +2766,8 @@ quit</programlisting>
<answer> <answer>
<para>This is usually caused by an interrupt conflict (e.g., <para>This is usually caused by an interrupt conflict (e.g.,
two boards using the same IRQ). Boot with the two boards using the same IRQ). Boot with
<option>-c</option> option and change the <option>-c</option> and change the
<devicename>ed0</devicename>/<devicename>de0</devicename>/... <devicename>ed0</devicename>/<devicename>de0</devicename>/...
entry to match your board.</para> entry to match your board.</para>
@ -3420,9 +3420,9 @@ chip1@pci0:31:5: class=0x040100 card=0x00931028 chip=0x24158086 rev=0x02
<filename>/etc/resolv.conf</filename>. This will often <filename>/etc/resolv.conf</filename>. This will often
cause a delay in <application>SSH</application>, as the cause a delay in <application>SSH</application>, as the
option <literal>UseDNS</literal> is set to option <literal>UseDNS</literal> is set to
<literal>yes</literal> by default in the <literal>yes</literal> by default in
<filename>sshd_config</filename> file in <filename>/etc/ssh/sshd_config</filename>.
<filename class="directory">/etc/ssh</filename>. If this is causing the If this is causing the
problem, you will either need to fill in the missing problem, you will either need to fill in the missing
information in <filename>/etc/resolv.conf</filename> or set information in <filename>/etc/resolv.conf</filename> or set
<literal>UseDNS</literal> to <literal>no</literal> in <literal>UseDNS</literal> to <literal>no</literal> in
@ -3455,7 +3455,7 @@ chip1@pci0:31:5: class=0x040100 card=0x00931028 chip=0x24158086 rev=0x02
<varname>MAX_STRAY_LOG</varname> from <varname>MAX_STRAY_LOG</varname> from
<literal>5</literal> to <literal>0</literal> in your <literal>5</literal> to <literal>0</literal> in your
platform's (e.g., &i386;) platform's (e.g., &i386;)
<filename>intr_machdep.c</filename> file and rebuild the <filename>intr_machdep.c</filename> and rebuild the
new kernel and all the warnings will be new kernel and all the warnings will be
suppressed.</para> suppressed.</para>
</listitem> </listitem>
@ -3643,7 +3643,7 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
<para>Enter &man.sysinstall.8; and choose <para>Enter &man.sysinstall.8; and choose
<guimenuitem>Configure</guimenuitem>, then <guimenuitem>Configure</guimenuitem>, then
<guimenuitem>Fdisk</guimenuitem>. Select the disk the Boot <guimenuitem>Fdisk</guimenuitem>. Select the disk the Boot
Manager resided on with the <keycap>Space</keycap> key. Manager resided on with <keycap>Space</keycap>.
Press <keycap>W</keycap> to write changes to the drive. A Press <keycap>W</keycap> to write changes to the drive. A
prompt will appear asking which boot loader to install. prompt will appear asking which boot loader to install.
Select this, and it will be restored.</para> Select this, and it will be restored.</para>
@ -4439,8 +4439,8 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr</programlisting>
used to build the currently running system (e.g., you used to build the currently running system (e.g., you
are compiling &rel.current;-RELEASE on a are compiling &rel.current;-RELEASE on a
&rel2.current;-RELEASE system). If you are attempting &rel2.current;-RELEASE system). If you are attempting
an upgrade, please read the an upgrade, please read
<filename>/usr/src/UPDATING</filename> file, paying <filename>/usr/src/UPDATING</filename>, paying
particular attention to the <quote>COMMON ITEMS</quote> particular attention to the <quote>COMMON ITEMS</quote>
section at the end.</para> section at the end.</para>
</listitem> </listitem>
@ -4697,8 +4697,8 @@ kern.sched.name: ULE</screen>
<para>When you are slicing up your disk, check that the disk <para>When you are slicing up your disk, check that the disk
geometry displayed in the FDISK screen is correct (i.e., it geometry displayed in the FDISK screen is correct (i.e., it
matches the BIOS numbers); if it is wrong, use the matches the BIOS numbers); if it is wrong, use
<keycap>G</keycap> key to fix it. You may have to do this <keycap>G</keycap> to fix it. You may have to do this
if there is absolutely nothing on the disk, or if the disk if there is absolutely nothing on the disk, or if the disk
has been moved from another system. Note that this is only has been moved from another system. Note that this is only
an issue with the disk that you are going to boot from; &os; an issue with the disk that you are going to boot from; &os;
@ -4965,7 +4965,7 @@ use "disklabel -r" to install initial label</screen>
DOS/&windowsnt; partition. Assuming you name that file DOS/&windowsnt; partition. Assuming you name that file
something like <filename>c:\bootsect.bsd</filename> something like <filename>c:\bootsect.bsd</filename>
(inspired by <filename>c:\bootsect.dos</filename>), you can (inspired by <filename>c:\bootsect.dos</filename>), you can
then edit the <filename>c:\boot.ini</filename> file to come then edit <filename>c:\boot.ini</filename> to come
up with something like this:</para> up with something like this:</para>
<programlisting>[boot loader] <programlisting>[boot loader]
@ -5461,7 +5461,7 @@ C:\="DOS"</programlisting>
<literal>Avail</literal> columns, usually by a factor of <literal>Avail</literal> columns, usually by a factor of
8%.</para> 8%.</para>
<para>For more details, look up the <option>-m</option> option <para>For more details, look up <option>-m</option>
in &man.tunefs.8;.</para> in &man.tunefs.8;.</para>
</answer> </answer>
</qandaentry> </qandaentry>
@ -5520,8 +5520,8 @@ C:\="DOS"</programlisting>
<qandaentry> <qandaentry>
<question id="root-not-found-cron-errors"> <question id="root-not-found-cron-errors">
<para>Why do I keep getting messages like <errorname>root: not <para>Why do I keep getting messages like <errorname>root: not
found</errorname> after editing my found</errorname> after editing
<filename>crontab</filename> file?</para> <filename>/etc/crontab</filename></para>
</question> </question>
<answer> <answer>
@ -5933,7 +5933,8 @@ options SYSVMSG # enable for messaging</programlisting>
<para>The error comes from the <para>The error comes from the
<application>Kerberos</application> distributed authentication <application>Kerberos</application> distributed authentication
system. The problem is not fatal but annoying. You can system. The problem is not fatal but annoying. You can
either run su with the <option>-K</option> option, or either run <command>su</command> with <option>-K</option>,
or
uninstall <application>Kerberos</application> as described uninstall <application>Kerberos</application> as described
in the next question.</para> in the next question.</para>
</answer> </answer>
@ -6529,8 +6530,8 @@ EndSection</programlisting>
are running or to read your mail while waiting for an FTP are running or to read your mail while waiting for an FTP
transfer to finish. Just do <keycombo transfer to finish. Just do <keycombo
action="simul"><keycap>Alt</keycap><keycap>F2</keycap></keycombo> action="simul"><keycap>Alt</keycap><keycap>F2</keycap></keycombo>
(hold down the <keycap>Alt</keycap> key and press the (hold down <keycap>Alt</keycap> and press
<keycap>F2</keycap> key), and you will find a login prompt <keycap>F2</keycap>), and you will find a login prompt
waiting for you on the second <quote>virtual waiting for you on the second <quote>virtual
console</quote>! When you want to go back to the original console</quote>! When you want to go back to the original
session, do <keycombo session, do <keycombo
@ -6605,7 +6606,7 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure</programlisting>
<para>It is imperative that you completely shut down X Window <para>It is imperative that you completely shut down X Window
if it is running, before running this command. If you do not, if it is running, before running this command. If you do not,
your system will probably appear to hang or lock up after your system will probably appear to hang or lock up after
executing the <command>kill</command> command.</para> executing <command>kill</command>.</para>
</answer> </answer>
</qandaentry> </qandaentry>
@ -6665,8 +6666,8 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure</programlisting>
server.</para> server.</para>
<para>If loaded from &man.rc.8;, <command>xdm</command> should <para>If loaded from &man.rc.8;, <command>xdm</command> should
be started without any arguments (i.e., as a daemon). The be started without any arguments (i.e., as a daemon).
<command>xdm</command> command must start <command>xdm</command> must start
<emphasis>after</emphasis> &man.getty.8; runs, or else <emphasis>after</emphasis> &man.getty.8; runs, or else
<command>getty</command> and <command>xdm</command> will <command>getty</command> and <command>xdm</command> will
conflict, locking out the console. The best way around this conflict, locking out the console. The best way around this
@ -6677,9 +6678,8 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure</programlisting>
<filename>/etc/ttys</filename>, there still is a chance of <filename>/etc/ttys</filename>, there still is a chance of
conflict between <command>xdm</command> and &man.getty.8;. conflict between <command>xdm</command> and &man.getty.8;.
One way to avoid this is to add the <literal>vt</literal> One way to avoid this is to add the <literal>vt</literal>
number in the number in
<filename>/usr/local/lib/X11/xdm/Xservers</filename> <filename>/usr/local/lib/X11/xdm/Xservers</filename></para>
file:</para>
<programlisting>:0 local /usr/local/bin/X vt4</programlisting> <programlisting>:0 local /usr/local/bin/X vt4</programlisting>
@ -7878,11 +7878,11 @@ default 10.0.0.2 UGSc 0 0 tun0
10.0.0.2 10.0.0.1 UH 0 0 tun0</programlisting> 10.0.0.2 10.0.0.1 UH 0 0 tun0</programlisting>
<para>This is assuming that you have used the addresses from <para>This is assuming that you have used the addresses from
the handbook, the manual page, or from the the handbook, the manual page, or from
<filename>ppp.conf.sample</filename> file. If you do not <filename>ppp.conf.sample</filename>. If you do not
have a default route, it may be because you forgot to add have a default route, it may be because you forgot to add
the <literal>HISADDR</literal> line to the the <literal>HISADDR</literal> line to
<filename>ppp.conf</filename> file.</para> <filename>ppp.conf</filename>.</para>
<para>Another reason for the default route line being missing <para>Another reason for the default route line being missing
is that you have mistakenly set up a default router in your is that you have mistakenly set up a default router in your
@ -7906,8 +7906,7 @@ default 10.0.0.2 UGSc 0 0 tun0
<answer> <answer>
<para>This error is usually due that the following section is <para>This error is usually due that the following section is
missing in your <filename>/etc/ppp/ppp.linkup</filename> missing in your <filename>/etc/ppp/ppp.linkup</filename>:</para>
file:</para>
<programlisting>MYADDR: <programlisting>MYADDR:
delete ALL delete ALL
@ -8386,7 +8385,7 @@ set dfilter 3 permit 0/0 0/0</programlisting>
invoked with <option>-bd -q30m</option>, telling it to run invoked with <option>-bd -q30m</option>, telling it to run
the queue every 30 minutes) or until a <command>sendmail the queue every 30 minutes) or until a <command>sendmail
<option>-q</option></command> is done (perhaps from your <option>-q</option></command> is done (perhaps from your
<filename>ppp.linkup</filename> file).</para> <filename>ppp.linkup</filename>).</para>
</answer> </answer>
</qandaentry> </qandaentry>
@ -8741,8 +8740,8 @@ ATDT1234567</programlisting>
if the incoming data is actually a login or shell prompt. if the incoming data is actually a login or shell prompt.
If you have a shell prompt at the remote end, it is possible If you have a shell prompt at the remote end, it is possible
to terminate &man.ppp.8; without dropping the line by using to terminate &man.ppp.8; without dropping the line by using
the <command>close lcp</command> command (a following <command>close lcp</command> (a following
<command>term</command> command) will reconnect you to the <command>term</command>) will reconnect you to the
shell on the remote machine.</para> shell on the remote machine.</para>
<para>If nothing in your log file indicates why the link might <para>If nothing in your log file indicates why the link might
@ -8762,7 +8761,7 @@ ATDT1234567</programlisting>
<para>If all else fails, send as much information as you can, <para>If all else fails, send as much information as you can,
including your config files, how you are starting including your config files, how you are starting
&man.ppp.8;, the relevant parts of your log file and the &man.ppp.8;, the relevant parts of your log file and the
output of the <command>netstat -rn</command> command (before output of <command>netstat -rn</command> (before
and after connecting) to the &a.questions; or the <ulink and after connecting) to the &a.questions; or the <ulink
url="news:comp.unix.bsd.freebsd.misc">comp.unix.bsd.freebsd.misc</ulink> url="news:comp.unix.bsd.freebsd.misc">comp.unix.bsd.freebsd.misc</ulink>
news group, and someone should point you in the right news group, and someone should point you in the right
@ -9054,12 +9053,12 @@ hint.sio.7.irq="12"</programlisting>
<para>When changing modes of the file hierarchies rooted in the <para>When changing modes of the file hierarchies rooted in the
files instead of the files themselves, files instead of the files themselves,
you have to use either <option>-H</option> or you have to use either <option>-H</option> or
<option>-L</option> together with the <option>-R</option> <option>-L</option> together with <option>-R</option>
option to make this work. See the &man.chmod.1; and to make this work. See &man.chmod.1; and
&man.symlink.7; manual pages for more info.</para> &man.symlink.7; for more information.</para>
<warning> <warning>
<para>The <option>-R</option> option does a <para><option>-R</option> does a
<emphasis>recursive</emphasis> &man.chmod.1;. Be careful <emphasis>recursive</emphasis> &man.chmod.1;. Be careful
about specifying directories or symlinks to directories to about specifying directories or symlinks to directories to
&man.chmod.1;. If you want to change the permissions of a &man.chmod.1;. If you want to change the permissions of a