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

And the next round of markup fixes:

Browse source 
- use errorname for error message
- use &man.foo instead of <command>foo</command> where possible
- don't use &man.foo in anything that will become a link
- add some more <devicename>s
This commit is contained in:
Udo Erdelhoff 2001-05-24 15:51:13 +00:00
parent c389868349
commit 6afca4e331
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=9489
2 changed files with 104 additions and 104 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

104
en_US.ISO8859-1/books/faq/book.sgml
View file

@ -14,7 +14,7 @@
<corpauthor>The FreeBSD Documentation Project</corpauthor> <corpauthor>The FreeBSD Documentation Project</corpauthor>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.204 2001/05/22 17:33:26 bmah Exp $</pubdate> <pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.205 2001/05/24 14:08:40 jim Exp $</pubdate>
<copyright> <copyright>
<year>1995</year> <year>1995</year>
@ -2085,7 +2085,7 @@ BUSY</literallayout></entry>
<qandaentry> <qandaentry>
<question id="panic-on-install-reboot"> <question id="panic-on-install-reboot">
<para>I get a <literal>panic: cant mount root</literal> <para>I get a <errorname>panic: cant mount root</errorname>
error when rebooting the system after installation.</para> error when rebooting the system after installation.</para>
</question> </question>
@ -2344,7 +2344,7 @@ Filesystem 1024-blocks Used Avail Capacity Mounted on
<qandaentry> <qandaentry>
<question id="archsw-readin-failed-error"> <question id="archsw-readin-failed-error">
<para>I compiled a new kernel and now I get the error message <para>I compiled a new kernel and now I get the error message
<literal>archsw.readin.failed</literal> when booting.</para> <errorname>archsw.readin.failed</errorname> when booting.</para>
</question> </question>
<answer> <answer>
@ -3698,7 +3698,7 @@ quit</programlisting>
<para>Note that your device name (<devicename>/dev/cd0c</devicename> <para>Note that your device name (<devicename>/dev/cd0c</devicename>
in this example) could be different, depending on the CDROM in this example) could be different, depending on the CDROM
interface. Note that the <option>-t cd9660</option> option just interface. Note that the <option>-t cd9660</option> option just
causes the <command>mount_cd9660</command> command to be causes the &man.mount.cd9660.8; command to be
executed, and so the above example could be shortened executed, and so the above example could be shortened
to:</para> to:</para>
@ -3773,7 +3773,7 @@ quit</programlisting>
<qandaentry> <qandaentry>
<question id="signal11"> <question id="signal11">
<para>My programs occasionally die with <para>My programs occasionally die with
<literal>Signal 11</literal> errors.</para> <errorname>Signal 11</errorname> errors.</para>
</question> </question>
<answer> <answer>
@ -4167,29 +4167,29 @@ quit</programlisting>
<qandaentry> <qandaentry>
<question id="pcm0-not-found"> <question id="pcm0-not-found">
<para>I see <literal>pcm0 not found</literal> or my sound card is <para>I see <errorname>pcm0 not found</errorname> or my sound card is
found as <literal>pcm1</literal> but I have found as <devicename>pcm1</devicename> but I have
<literal>device pcm0</literal> in my kernel config file</para> <literal>device pcm0</literal> in my kernel config file</para>
</question> </question>
<answer> <answer>
<para>This occurs in FreeBSD 3.x with PCI sound cards. The <para>This occurs in FreeBSD 3.x with PCI sound cards. The
<literal>pcm0</literal> device is reserved exclusively for <devicename>pcm0</devicename> device is reserved exclusively for
ISA-based cards so, if you have a PCI card, then you will see ISA-based cards so, if you have a PCI card, then you will see
this error, and your card will appear as <literal>pcm1</literal>. this error, and your card will appear as <devicename>pcm1</devicename>.
<note> <note>
<para>You cannot remove the warning by simply changing the <para>You cannot remove the warning by simply changing the
line in the kernel config file to <literal>device line in the kernel config file to <literal>device
pcm1</literal> as this will result in pcm1</literal> as this will result in
<literal>pcm1</literal> being reserved for ISA cards and <devicename>pcm1</devicename> being reserved for ISA cards and
your PCI card being found as <literal>pcm2</literal> (along your PCI card being found as <devicename>pcm2</devicename> (along
with the warning <literal>pcm1 not found</literal>).</para> with the warning <errorname>pcm1 not found</errorname>).</para>
</note> </note>
If you have a PCI sound card you will also have to make the If you have a PCI sound card you will also have to make the
<literal>snd1</literal> device rather than <devicename>snd1</devicename> device rather than
<literal>snd0</literal>:</para> <devicename>snd0</devicename>:</para>
<screen>&prompt.root; <userinput>cd /dev</userinput> <screen>&prompt.root; <userinput>cd /dev</userinput>
&prompt.root; <userinput>./MAKEDEV snd1</userinput></screen> &prompt.root; <userinput>./MAKEDEV snd1</userinput></screen>
@ -4197,7 +4197,7 @@ quit</programlisting>
<para>This situation does not arise in FreeBSD 4.x as has a lot <para>This situation does not arise in FreeBSD 4.x as has a lot
of work has been done to make the it more of work has been done to make the it more
<emphasis>PnP-centric</emphasis> and the <emphasis>PnP-centric</emphasis> and the
<literal>pcm0</literal> device is no longer reserved <devicename>pcm0</devicename> device is no longer reserved
exclusively fo ISA cards</para> exclusively fo ISA cards</para>
</answer> </answer>
</qandaentry> </qandaentry>
@ -4348,7 +4348,7 @@ IO range check 0x00 activate 0x01</screen>
<qandaentry> <qandaentry>
<question id="connection-delay"> <question id="connection-delay">
<para>Why does it take so long to connect to my computer via <para>Why does it take so long to connect to my computer via
&man.ssh.1; or &man.telnet.1;?</para> <command>ssh</command> or <command>telnet</command>?</para>
</question> </question>
<answer> <answer>
@ -5162,7 +5162,7 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx</screen>
<answer> <answer>
<para>Unfortunately, there is no easy way to update installed <para>Unfortunately, there is no easy way to update installed
ports. The <command>pkg_version</command> command can be used ports. The &man.pkg.version.1; command can be used
to generate a script that will update the installed ports with to generate a script that will update the installed ports with
a newer version in the ports tree:</para> a newer version in the ports tree:</para>
@ -5170,8 +5170,8 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx</screen>
<para>The output script <emphasis>must</emphasis> be edited by <para>The output script <emphasis>must</emphasis> be edited by
hand before you use it. Current versions of hand before you use it. Current versions of
<command>pkg_version</command> force this by inserting an &man.pkg.version.1; force this by inserting an
<command>exit</command> at the beginning of the script.</para> &man.exit.1; at the beginning of the script.</para>
<para>You should save the output of the script, as it will note <para>You should save the output of the script, as it will note
packages that depend on the one that has been udpated. These packages that depend on the one that has been udpated. These
@ -5264,7 +5264,7 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx</screen>
</listitem> </listitem>
<listitem> <listitem>
<para>You are not running <command>config</command> with <para>You are not running &man.config.8; with
the <option>-g</option> option.</para> the <option>-g</option> option.</para>
</listitem> </listitem>
</itemizedlist> </itemizedlist>
@ -5471,8 +5471,8 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr</programlisting>
<para>for a ZIP disk with the factory configuration.</para> <para>for a ZIP disk with the factory configuration.</para>
<para>For other disks, see how they're laid out using <para>For other disks, see how they're laid out using
<command>fdisk</command> or &man.fdisk.8; or
<filename>/stand/sysinstall</filename>.</para> &man.sysinstall.8;.</para>
<para>The rest of the examples will be for a ZIP drive on da2, <para>The rest of the examples will be for a ZIP drive on da2,
the third SCSI disk.</para> the third SCSI disk.</para>
@ -5563,7 +5563,7 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr</programlisting>
<qandaentry> <qandaentry>
<question id="su-wheel-group"> <question id="su-wheel-group">
<para>&man.su.1; says <errorname>you are not in the correct group <para><command>su</command> says <errorname>you are not in the correct group
to su root</errorname> when I try to su to to su root</errorname> when I try to su to
<username>root</username>.</para> <username>root</username>.</para>
</question> </question>
@ -5855,8 +5855,8 @@ C:\="DOS"</programlisting>
AWARD (eg. as found in HP Netserver and Micronics systems as AWARD (eg. as found in HP Netserver and Micronics systems as
well as many others) and Symbios/NCR (for the popular 53C8xx well as many others) and Symbios/NCR (for the popular 53C8xx
range of SCSI controllers). This isn't a complete list, there range of SCSI controllers). This isn't a complete list, there
are more. Symptoms of this confusion include the <quote>read are more. Symptoms of this confusion include the <errorname>read
error</quote> message printed by the FreeBSD bootstrap when it error</errorname> message printed by the FreeBSD bootstrap when it
can't find itself, as well as system lockups when can't find itself, as well as system lockups when
booting.</para> booting.</para>
@ -5905,8 +5905,8 @@ C:\="DOS"</programlisting>
<para>Once you've got the BIOS and FreeBSD agreeing about the <para>Once you've got the BIOS and FreeBSD agreeing about the
geometry of the disk, your problems are almost guaranteed to be geometry of the disk, your problems are almost guaranteed to be
over, and with no need for <quote>DD</quote> mode at all. If, over, and with no need for <quote>DD</quote> mode at all. If,
however, you are still greeted with the dreaded <quote>read however, you are still greeted with the dreaded <errorname>read
error</quote> message when you try to boot, it's time to cross error</errorname> message when you try to boot, it's time to cross
your fingers and go for it - there's nothing left to your fingers and go for it - there's nothing left to
lose.</para> lose.</para>
@ -6621,7 +6621,7 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
<command>mount -u /</command> to remount your root filesystem <command>mount -u /</command> to remount your root filesystem
read/write, then run <command>mount -a</command> to remount all read/write, then run <command>mount -a</command> to remount all
the filesystems. Run <command>passwd root</command> to change the filesystems. Run <command>passwd root</command> to change
the root password then run <command>exit</command> to continue the root password then run &man.exit.1; to continue
booting.</para> booting.</para>
</answer> </answer>
</qandaentry> </qandaentry>
@ -7255,7 +7255,7 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
<qandaentry> <qandaentry>
<question id="statd-mem-leak"> <question id="statd-mem-leak">
<para>There is a memory leak in &man.rpc.statd.8;! It is using <para>There is a memory leak in <command>rpc.statd</command>! It is using
256 Mbytes of memory!</para> 256 Mbytes of memory!</para>
</question> </question>
@ -7842,7 +7842,7 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure</programlisting>
<para>If you are to start <command>xdm</command> from <para>If you are to start <command>xdm</command> from
<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 conflict between <command>xdm</command> and
<command>getty</command>. One way to avoid this is to add the &man.getty.8;. One way to avoid this is to add the
<literal>vt</literal> number in the <literal>vt</literal> number in the
<filename>/usr/X11R6/lib/X11/xdm/Xservers</filename> <filename>/usr/X11R6/lib/X11/xdm/Xservers</filename>
file.</para> file.</para>
@ -7916,7 +7916,7 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure</programlisting>
logins. It is usually started at boot time, and is responsible logins. It is usually started at boot time, and is responsible
for authenticating users and starting their sessions; it is for authenticating users and starting their sessions; it is
essentially the graphical counterpart of essentially the graphical counterpart of
<command>getty</command> and <command>login</command>. For &man.getty.8; and &man.login.1;. For
more information on <command>xdm</command> see more information on <command>xdm</command> see
<ulink url="http://www.xfree86.org/support.html">the XFree86 <ulink url="http://www.xfree86.org/support.html">the XFree86
documentation</ulink>, and the <link linkend="xdm-boot">the FAQ documentation</ulink>, and the <link linkend="xdm-boot">the FAQ
@ -8321,7 +8321,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
<para>If you are using kernel-mode ppp, or have an Ethernet <para>If you are using kernel-mode ppp, or have an Ethernet
connection to the Internet, you will have to use connection to the Internet, you will have to use
<command>natd</command>. Please look at the &man.natd.8;. Please look at the
<link linkend="natd">natd</link> section of this FAQ.</para> <link linkend="natd">natd</link> section of this FAQ.</para>
</answer> </answer>
</qandaentry> </qandaentry>
@ -8375,7 +8375,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
but have been allocated only a single IP number from your but have been allocated only a single IP number from your
Internet provider (or even if you receive a dynamic IP number), Internet provider (or even if you receive a dynamic IP number),
you may want to look at the &man.natd.8; you may want to look at the &man.natd.8;
program. <command>natd</command> allows you to connect an program. &man.natd.8; allows you to connect an
entire subnet to the internet using only a single IP entire subnet to the internet using only a single IP
number.</para> number.</para>
@ -8480,8 +8480,8 @@ Key F15 A A Menu Workplace Nop</programlisting>
<qandaentry> <qandaentry>
<question id="exports-errors"> <question id="exports-errors">
<para>Why does <command>mountd</command> keep telling me it <para>Why does <command>mountd</command> keep telling me it
<quote>can't change attributes</quote> and that I have a <errorname>can't change attributes</errorname> and that I have a
<quote>bad exports list</quote> on my FreeBSD NFS <errorname>bad exports list</errorname> on my FreeBSD NFS
server?</para> server?</para>
</question> </question>
@ -8569,8 +8569,8 @@ Key F15 A A Menu Workplace Nop</programlisting>
2.0 and later by default. If you want your box to run as a 2.0 and later by default. If you want your box to run as a
multicast router, you will need to recompile your kernel with multicast router, you will need to recompile your kernel with
the <literal>MROUTING</literal> option and run the <literal>MROUTING</literal> option and run
<command>mrouted</command>. FreeBSD 2.2 and later will start &man.mrouted.8;. FreeBSD 2.2 and later will start
<command>mrouted</command> at boot time if the flag &man.mrouted.8; at boot time if the flag
<literal>mrouted_enable</literal> is set to <literal>mrouted_enable</literal> is set to
<literal>"YES"</literal> in <literal>"YES"</literal> in
<filename>/etc/rc.conf</filename>.</para> <filename>/etc/rc.conf</filename>.</para>
@ -8772,7 +8772,7 @@ Znyx (2.2.x) ZX312, ZX314, ZX342, ZX345, ZX346, ZX348
<qandaentry> <qandaentry>
<question id="ipfw-fwd"> <question id="ipfw-fwd">
<para>Why is my &man.ipfw.8; <quote>fwd</quote> rule to redirect a <para>Why is my <command>ipfw</command> <quote>fwd</quote> rule to redirect a
service to another machine not working?</para> service to another machine not working?</para>
</question> </question>
@ -8862,7 +8862,7 @@ Znyx (2.2.x) ZX312, ZX314, ZX342, ZX345, ZX346, ZX348
address if you want to tighten things further.</para> address if you want to tighten things further.</para>
<para>Congratulations, by the way. It is good practice to read <para>Congratulations, by the way. It is good practice to read
your <command>sockstat</command> output and notice odd your &man.sockstat.1; output and notice odd
things!</para> things!</para>
</answer> </answer>
</qandaentry> </qandaentry>
@ -9084,7 +9084,7 @@ default 10.0.0.2 UGSc 0 0 tun0
<qandaentry> <qandaentry>
<question id="no-route-to-host"> <question id="no-route-to-host">
<para>What does <literal>No route to host</literal> mean</para> <para>What does <errorname>No route to host</errorname> mean</para>
</question> </question>
<answer> <answer>
@ -9188,7 +9188,7 @@ add 0 0 HISADDR</programlisting>
the link is hung.</para> the link is hung.</para>
<para>If you are using an external modem, you can simply try <para>If you are using an external modem, you can simply try
using <command>ping</command> to see if the using &man.ping.8; to see if the
<acronym>TD</acronym> light is flashing when you transmit data. <acronym>TD</acronym> light is flashing when you transmit data.
If it flashes (and the <acronym>RD</acronym> light doesn't), If it flashes (and the <acronym>RD</acronym> light doesn't),
the problem is with the remote end. If <acronym>TD</acronym> the problem is with the remote end. If <acronym>TD</acronym>
@ -9201,7 +9201,7 @@ add 0 0 HISADDR</programlisting>
<literal>set socket</literal> command succeeded at startup <literal>set socket</literal> command succeeded at startup
time), the problem is local. If you can connect and things are time), the problem is local. If you can connect and things are
still hung, enable local async logging with <literal>set log still hung, enable local async logging with <literal>set log
local async</literal> and use <command>ping</command> from local async</literal> and use &man.ping.8; from
another window or terminal to make use of the link. The async another window or terminal to make use of the link. The async
logging will show you the data being transmitted and received logging will show you the data being transmitted and received
on the link. If data is going out and not coming back, the on the link. If data is going out and not coming back, the
@ -10347,7 +10347,7 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr</programlist
<filename>.login</filename> files a prompt for the actual terminal type if the <filename>.login</filename> files a prompt for the actual terminal type if the
starting type is dialup. The example shows the port as starting type is dialup. The example shows the port as
insecure. To become root on this port, you have to login as a insecure. To become root on this port, you have to login as a
regular user, then <command>su</command> to become regular user, then &man.su.1; to become
<username>root</username>. If you use <literal>secure</literal> <username>root</username>. If you use <literal>secure</literal>
then <username>root</username> can login in directly.</para> then <username>root</username> can login in directly.</para>
@ -10358,7 +10358,7 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr</programlist
<screen>&prompt.root; <userinput>kill -HUP 1</userinput></screen> <screen>&prompt.root; <userinput>kill -HUP 1</userinput></screen>
<para>This forces the <command>init</command> process to reread <para>This forces the &man.init.8; process to reread
<filename>/etc/ttys</filename>. The init process will then start getty <filename>/etc/ttys</filename>. The init process will then start getty
processes on all <literal>on</literal> ports. You can find processes on all <literal>on</literal> ports. You can find
out if logins are available for your port by typing</para> out if logins are available for your port by typing</para>
@ -10416,7 +10416,7 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr</programlist
dialer.</para> dialer.</para>
<para>Alternatively, you can let everyone on your system <para>Alternatively, you can let everyone on your system
run <command>tip</command> and <command>cu</command> by run &man.tip.1; and &man.cu.1; by
typing:</para> typing:</para>
<screen>&prompt.root; <userinput>chmod 4511 /usr/bin/cu</userinput> <screen>&prompt.root; <userinput>chmod 4511 /usr/bin/cu</userinput>
@ -10443,12 +10443,12 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr</programlist
should turn those messages off when you use &man.tip.1; should turn those messages off when you use &man.tip.1;
(using <literal>ATX0&amp;W</literal>).</para> (using <literal>ATX0&amp;W</literal>).</para>
<para>Also, the dial timeout for <command>tip</command> is 60 <para>Also, the dial timeout for &man.tip.1; is 60
seconds. Your modem should use something less, or else tip seconds. Your modem should use something less, or else tip
will think there's a communication problem. Try will think there's a communication problem. Try
<literal>ATS7=45&amp;W</literal>.</para> <literal>ATS7=45&amp;W</literal>.</para>
<para>Actually, as shipped <command>tip</command> doesn't yet <para>Actually, as shipped &man.tip.1; doesn't yet
support it fully. The solution is to edit the file support it fully. The solution is to edit the file
<filename>tipconf.h</filename> in the directory <filename>tipconf.h</filename> in the directory
<filename>/usr/src/usr.bin/tip/tip</filename>. Obviously you <filename>/usr/src/usr.bin/tip/tip</filename>. Obviously you
@ -10611,7 +10611,7 @@ big-university 5551114</programlisting>
<para>&man.tip.1; <para>&man.tip.1;
will try each one in the listed order, then give will try each one in the listed order, then give
up. If you want to keep retrying, run <command>tip</command> up. If you want to keep retrying, run &man.tip.1;
in a while loop.</para> in a while loop.</para>
</answer> </answer>
</qandaentry> </qandaentry>
@ -10764,7 +10764,7 @@ raisechar=^^</programlisting>
<qandaentry> <qandaentry>
<question id="top-freemem"> <question id="top-freemem">
<para>Why does &man.top.1; show very little free memory even <para>Why does <command>top</command> show very little free memory even
when I have very few programs running?</para> when I have very few programs running?</para>
</question> </question>
@ -10991,7 +10991,7 @@ raisechar=^^</programlisting>
<acronym>RECURSIVE</acronym> <acronym>RECURSIVE</acronym>
&man.chmod.1;. Be careful about &man.chmod.1;. Be careful about
specifying directories or symlinks to directories to specifying directories or symlinks to directories to
<command>chmod</command>. If you want to &man.chmod.1;. If you want to
change the permissions of a directory referenced by a change the permissions of a directory referenced by a
symlink, use &man.chmod.1; symlink, use &man.chmod.1;
without any options and follow the symlink without any options and follow the symlink
@ -11240,7 +11240,7 @@ raisechar=^^</programlisting>
this history very useful, a repository copy is often used this history very useful, a repository copy is often used
instead. This is a process where one of the repository meisters instead. This is a process where one of the repository meisters
will copy the files directly within the repository, rather than will copy the files directly within the repository, rather than
using the <command>cvs</command> program.</para> using the &man.cvs.1; program.</para>
</answer> </answer>
</qandaentry> </qandaentry>
@ -12126,7 +12126,7 @@ SECTIONS
&man.top.1; and the like; <command>make &man.top.1; and the like; <command>make
world</command> should take care of it (or a manual rebuild of world</command> should take care of it (or a manual rebuild of
<filename>libkvm</filename>, <filename>libkvm</filename>,
<command>ps</command> and <command>top</command> &man.ps.1; and &man.top.1;
after copying the patched <filename>pmap.h</filename> to after copying the patched <filename>pmap.h</filename> to
<filename>/usr/include/vm/</filename>.</para> <filename>/usr/include/vm/</filename>.</para>

104
en_US.ISO_8859-1/books/faq/book.sgml
View file

@ -14,7 +14,7 @@
<corpauthor>The FreeBSD Documentation Project</corpauthor> <corpauthor>The FreeBSD Documentation Project</corpauthor>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.204 2001/05/22 17:33:26 bmah Exp $</pubdate> <pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.205 2001/05/24 14:08:40 jim Exp $</pubdate>
<copyright> <copyright>
<year>1995</year> <year>1995</year>
@ -2085,7 +2085,7 @@ BUSY</literallayout></entry>
<qandaentry> <qandaentry>
<question id="panic-on-install-reboot"> <question id="panic-on-install-reboot">
<para>I get a <literal>panic: cant mount root</literal> <para>I get a <errorname>panic: cant mount root</errorname>
error when rebooting the system after installation.</para> error when rebooting the system after installation.</para>
</question> </question>
@ -2344,7 +2344,7 @@ Filesystem 1024-blocks Used Avail Capacity Mounted on
<qandaentry> <qandaentry>
<question id="archsw-readin-failed-error"> <question id="archsw-readin-failed-error">
<para>I compiled a new kernel and now I get the error message <para>I compiled a new kernel and now I get the error message
<literal>archsw.readin.failed</literal> when booting.</para> <errorname>archsw.readin.failed</errorname> when booting.</para>
</question> </question>
<answer> <answer>
@ -3698,7 +3698,7 @@ quit</programlisting>
<para>Note that your device name (<devicename>/dev/cd0c</devicename> <para>Note that your device name (<devicename>/dev/cd0c</devicename>
in this example) could be different, depending on the CDROM in this example) could be different, depending on the CDROM
interface. Note that the <option>-t cd9660</option> option just interface. Note that the <option>-t cd9660</option> option just
causes the <command>mount_cd9660</command> command to be causes the &man.mount.cd9660.8; command to be
executed, and so the above example could be shortened executed, and so the above example could be shortened
to:</para> to:</para>
@ -3773,7 +3773,7 @@ quit</programlisting>
<qandaentry> <qandaentry>
<question id="signal11"> <question id="signal11">
<para>My programs occasionally die with <para>My programs occasionally die with
<literal>Signal 11</literal> errors.</para> <errorname>Signal 11</errorname> errors.</para>
</question> </question>
<answer> <answer>
@ -4167,29 +4167,29 @@ quit</programlisting>
<qandaentry> <qandaentry>
<question id="pcm0-not-found"> <question id="pcm0-not-found">
<para>I see <literal>pcm0 not found</literal> or my sound card is <para>I see <errorname>pcm0 not found</errorname> or my sound card is
found as <literal>pcm1</literal> but I have found as <devicename>pcm1</devicename> but I have
<literal>device pcm0</literal> in my kernel config file</para> <literal>device pcm0</literal> in my kernel config file</para>
</question> </question>
<answer> <answer>
<para>This occurs in FreeBSD 3.x with PCI sound cards. The <para>This occurs in FreeBSD 3.x with PCI sound cards. The
<literal>pcm0</literal> device is reserved exclusively for <devicename>pcm0</devicename> device is reserved exclusively for
ISA-based cards so, if you have a PCI card, then you will see ISA-based cards so, if you have a PCI card, then you will see
this error, and your card will appear as <literal>pcm1</literal>. this error, and your card will appear as <devicename>pcm1</devicename>.
<note> <note>
<para>You cannot remove the warning by simply changing the <para>You cannot remove the warning by simply changing the
line in the kernel config file to <literal>device line in the kernel config file to <literal>device
pcm1</literal> as this will result in pcm1</literal> as this will result in
<literal>pcm1</literal> being reserved for ISA cards and <devicename>pcm1</devicename> being reserved for ISA cards and
your PCI card being found as <literal>pcm2</literal> (along your PCI card being found as <devicename>pcm2</devicename> (along
with the warning <literal>pcm1 not found</literal>).</para> with the warning <errorname>pcm1 not found</errorname>).</para>
</note> </note>
If you have a PCI sound card you will also have to make the If you have a PCI sound card you will also have to make the
<literal>snd1</literal> device rather than <devicename>snd1</devicename> device rather than
<literal>snd0</literal>:</para> <devicename>snd0</devicename>:</para>
<screen>&prompt.root; <userinput>cd /dev</userinput> <screen>&prompt.root; <userinput>cd /dev</userinput>
&prompt.root; <userinput>./MAKEDEV snd1</userinput></screen> &prompt.root; <userinput>./MAKEDEV snd1</userinput></screen>
@ -4197,7 +4197,7 @@ quit</programlisting>
<para>This situation does not arise in FreeBSD 4.x as has a lot <para>This situation does not arise in FreeBSD 4.x as has a lot
of work has been done to make the it more of work has been done to make the it more
<emphasis>PnP-centric</emphasis> and the <emphasis>PnP-centric</emphasis> and the
<literal>pcm0</literal> device is no longer reserved <devicename>pcm0</devicename> device is no longer reserved
exclusively fo ISA cards</para> exclusively fo ISA cards</para>
</answer> </answer>
</qandaentry> </qandaentry>
@ -4348,7 +4348,7 @@ IO range check 0x00 activate 0x01</screen>
<qandaentry> <qandaentry>
<question id="connection-delay"> <question id="connection-delay">
<para>Why does it take so long to connect to my computer via <para>Why does it take so long to connect to my computer via
&man.ssh.1; or &man.telnet.1;?</para> <command>ssh</command> or <command>telnet</command>?</para>
</question> </question>
<answer> <answer>
@ -5162,7 +5162,7 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx</screen>
<answer> <answer>
<para>Unfortunately, there is no easy way to update installed <para>Unfortunately, there is no easy way to update installed
ports. The <command>pkg_version</command> command can be used ports. The &man.pkg.version.1; command can be used
to generate a script that will update the installed ports with to generate a script that will update the installed ports with
a newer version in the ports tree:</para> a newer version in the ports tree:</para>
@ -5170,8 +5170,8 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx</screen>
<para>The output script <emphasis>must</emphasis> be edited by <para>The output script <emphasis>must</emphasis> be edited by
hand before you use it. Current versions of hand before you use it. Current versions of
<command>pkg_version</command> force this by inserting an &man.pkg.version.1; force this by inserting an
<command>exit</command> at the beginning of the script.</para> &man.exit.1; at the beginning of the script.</para>
<para>You should save the output of the script, as it will note <para>You should save the output of the script, as it will note
packages that depend on the one that has been udpated. These packages that depend on the one that has been udpated. These
@ -5264,7 +5264,7 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx</screen>
</listitem> </listitem>
<listitem> <listitem>
<para>You are not running <command>config</command> with <para>You are not running &man.config.8; with
the <option>-g</option> option.</para> the <option>-g</option> option.</para>
</listitem> </listitem>
</itemizedlist> </itemizedlist>
@ -5471,8 +5471,8 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr</programlisting>
<para>for a ZIP disk with the factory configuration.</para> <para>for a ZIP disk with the factory configuration.</para>
<para>For other disks, see how they're laid out using <para>For other disks, see how they're laid out using
<command>fdisk</command> or &man.fdisk.8; or
<filename>/stand/sysinstall</filename>.</para> &man.sysinstall.8;.</para>
<para>The rest of the examples will be for a ZIP drive on da2, <para>The rest of the examples will be for a ZIP drive on da2,
the third SCSI disk.</para> the third SCSI disk.</para>
@ -5563,7 +5563,7 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr</programlisting>
<qandaentry> <qandaentry>
<question id="su-wheel-group"> <question id="su-wheel-group">
<para>&man.su.1; says <errorname>you are not in the correct group <para><command>su</command> says <errorname>you are not in the correct group
to su root</errorname> when I try to su to to su root</errorname> when I try to su to
<username>root</username>.</para> <username>root</username>.</para>
</question> </question>
@ -5855,8 +5855,8 @@ C:\="DOS"</programlisting>
AWARD (eg. as found in HP Netserver and Micronics systems as AWARD (eg. as found in HP Netserver and Micronics systems as
well as many others) and Symbios/NCR (for the popular 53C8xx well as many others) and Symbios/NCR (for the popular 53C8xx
range of SCSI controllers). This isn't a complete list, there range of SCSI controllers). This isn't a complete list, there
are more. Symptoms of this confusion include the <quote>read are more. Symptoms of this confusion include the <errorname>read
error</quote> message printed by the FreeBSD bootstrap when it error</errorname> message printed by the FreeBSD bootstrap when it
can't find itself, as well as system lockups when can't find itself, as well as system lockups when
booting.</para> booting.</para>
@ -5905,8 +5905,8 @@ C:\="DOS"</programlisting>
<para>Once you've got the BIOS and FreeBSD agreeing about the <para>Once you've got the BIOS and FreeBSD agreeing about the
geometry of the disk, your problems are almost guaranteed to be geometry of the disk, your problems are almost guaranteed to be
over, and with no need for <quote>DD</quote> mode at all. If, over, and with no need for <quote>DD</quote> mode at all. If,
however, you are still greeted with the dreaded <quote>read however, you are still greeted with the dreaded <errorname>read
error</quote> message when you try to boot, it's time to cross error</errorname> message when you try to boot, it's time to cross
your fingers and go for it - there's nothing left to your fingers and go for it - there's nothing left to
lose.</para> lose.</para>
@ -6621,7 +6621,7 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
<command>mount -u /</command> to remount your root filesystem <command>mount -u /</command> to remount your root filesystem
read/write, then run <command>mount -a</command> to remount all read/write, then run <command>mount -a</command> to remount all
the filesystems. Run <command>passwd root</command> to change the filesystems. Run <command>passwd root</command> to change
the root password then run <command>exit</command> to continue the root password then run &man.exit.1; to continue
booting.</para> booting.</para>
</answer> </answer>
</qandaentry> </qandaentry>
@ -7255,7 +7255,7 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
<qandaentry> <qandaentry>
<question id="statd-mem-leak"> <question id="statd-mem-leak">
<para>There is a memory leak in &man.rpc.statd.8;! It is using <para>There is a memory leak in <command>rpc.statd</command>! It is using
256 Mbytes of memory!</para> 256 Mbytes of memory!</para>
</question> </question>
@ -7842,7 +7842,7 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure</programlisting>
<para>If you are to start <command>xdm</command> from <para>If you are to start <command>xdm</command> from
<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 conflict between <command>xdm</command> and
<command>getty</command>. One way to avoid this is to add the &man.getty.8;. One way to avoid this is to add the
<literal>vt</literal> number in the <literal>vt</literal> number in the
<filename>/usr/X11R6/lib/X11/xdm/Xservers</filename> <filename>/usr/X11R6/lib/X11/xdm/Xservers</filename>
file.</para> file.</para>
@ -7916,7 +7916,7 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure</programlisting>
logins. It is usually started at boot time, and is responsible logins. It is usually started at boot time, and is responsible
for authenticating users and starting their sessions; it is for authenticating users and starting their sessions; it is
essentially the graphical counterpart of essentially the graphical counterpart of
<command>getty</command> and <command>login</command>. For &man.getty.8; and &man.login.1;. For
more information on <command>xdm</command> see more information on <command>xdm</command> see
<ulink url="http://www.xfree86.org/support.html">the XFree86 <ulink url="http://www.xfree86.org/support.html">the XFree86
documentation</ulink>, and the <link linkend="xdm-boot">the FAQ documentation</ulink>, and the <link linkend="xdm-boot">the FAQ
@ -8321,7 +8321,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
<para>If you are using kernel-mode ppp, or have an Ethernet <para>If you are using kernel-mode ppp, or have an Ethernet
connection to the Internet, you will have to use connection to the Internet, you will have to use
<command>natd</command>. Please look at the &man.natd.8;. Please look at the
<link linkend="natd">natd</link> section of this FAQ.</para> <link linkend="natd">natd</link> section of this FAQ.</para>
</answer> </answer>
</qandaentry> </qandaentry>
@ -8375,7 +8375,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
but have been allocated only a single IP number from your but have been allocated only a single IP number from your
Internet provider (or even if you receive a dynamic IP number), Internet provider (or even if you receive a dynamic IP number),
you may want to look at the &man.natd.8; you may want to look at the &man.natd.8;
program. <command>natd</command> allows you to connect an program. &man.natd.8; allows you to connect an
entire subnet to the internet using only a single IP entire subnet to the internet using only a single IP
number.</para> number.</para>
@ -8480,8 +8480,8 @@ Key F15 A A Menu Workplace Nop</programlisting>
<qandaentry> <qandaentry>
<question id="exports-errors"> <question id="exports-errors">
<para>Why does <command>mountd</command> keep telling me it <para>Why does <command>mountd</command> keep telling me it
<quote>can't change attributes</quote> and that I have a <errorname>can't change attributes</errorname> and that I have a
<quote>bad exports list</quote> on my FreeBSD NFS <errorname>bad exports list</errorname> on my FreeBSD NFS
server?</para> server?</para>
</question> </question>
@ -8569,8 +8569,8 @@ Key F15 A A Menu Workplace Nop</programlisting>
2.0 and later by default. If you want your box to run as a 2.0 and later by default. If you want your box to run as a
multicast router, you will need to recompile your kernel with multicast router, you will need to recompile your kernel with
the <literal>MROUTING</literal> option and run the <literal>MROUTING</literal> option and run
<command>mrouted</command>. FreeBSD 2.2 and later will start &man.mrouted.8;. FreeBSD 2.2 and later will start
<command>mrouted</command> at boot time if the flag &man.mrouted.8; at boot time if the flag
<literal>mrouted_enable</literal> is set to <literal>mrouted_enable</literal> is set to
<literal>"YES"</literal> in <literal>"YES"</literal> in
<filename>/etc/rc.conf</filename>.</para> <filename>/etc/rc.conf</filename>.</para>
@ -8772,7 +8772,7 @@ Znyx (2.2.x) ZX312, ZX314, ZX342, ZX345, ZX346, ZX348
<qandaentry> <qandaentry>
<question id="ipfw-fwd"> <question id="ipfw-fwd">
<para>Why is my &man.ipfw.8; <quote>fwd</quote> rule to redirect a <para>Why is my <command>ipfw</command> <quote>fwd</quote> rule to redirect a
service to another machine not working?</para> service to another machine not working?</para>
</question> </question>
@ -8862,7 +8862,7 @@ Znyx (2.2.x) ZX312, ZX314, ZX342, ZX345, ZX346, ZX348
address if you want to tighten things further.</para> address if you want to tighten things further.</para>
<para>Congratulations, by the way. It is good practice to read <para>Congratulations, by the way. It is good practice to read
your <command>sockstat</command> output and notice odd your &man.sockstat.1; output and notice odd
things!</para> things!</para>
</answer> </answer>
</qandaentry> </qandaentry>
@ -9084,7 +9084,7 @@ default 10.0.0.2 UGSc 0 0 tun0
<qandaentry> <qandaentry>
<question id="no-route-to-host"> <question id="no-route-to-host">
<para>What does <literal>No route to host</literal> mean</para> <para>What does <errorname>No route to host</errorname> mean</para>
</question> </question>
<answer> <answer>
@ -9188,7 +9188,7 @@ add 0 0 HISADDR</programlisting>
the link is hung.</para> the link is hung.</para>
<para>If you are using an external modem, you can simply try <para>If you are using an external modem, you can simply try
using <command>ping</command> to see if the using &man.ping.8; to see if the
<acronym>TD</acronym> light is flashing when you transmit data. <acronym>TD</acronym> light is flashing when you transmit data.
If it flashes (and the <acronym>RD</acronym> light doesn't), If it flashes (and the <acronym>RD</acronym> light doesn't),
the problem is with the remote end. If <acronym>TD</acronym> the problem is with the remote end. If <acronym>TD</acronym>
@ -9201,7 +9201,7 @@ add 0 0 HISADDR</programlisting>
<literal>set socket</literal> command succeeded at startup <literal>set socket</literal> command succeeded at startup
time), the problem is local. If you can connect and things are time), the problem is local. If you can connect and things are
still hung, enable local async logging with <literal>set log still hung, enable local async logging with <literal>set log
local async</literal> and use <command>ping</command> from local async</literal> and use &man.ping.8; from
another window or terminal to make use of the link. The async another window or terminal to make use of the link. The async
logging will show you the data being transmitted and received logging will show you the data being transmitted and received
on the link. If data is going out and not coming back, the on the link. If data is going out and not coming back, the
@ -10347,7 +10347,7 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr</programlist
<filename>.login</filename> files a prompt for the actual terminal type if the <filename>.login</filename> files a prompt for the actual terminal type if the
starting type is dialup. The example shows the port as starting type is dialup. The example shows the port as
insecure. To become root on this port, you have to login as a insecure. To become root on this port, you have to login as a
regular user, then <command>su</command> to become regular user, then &man.su.1; to become
<username>root</username>. If you use <literal>secure</literal> <username>root</username>. If you use <literal>secure</literal>
then <username>root</username> can login in directly.</para> then <username>root</username> can login in directly.</para>
@ -10358,7 +10358,7 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr</programlist
<screen>&prompt.root; <userinput>kill -HUP 1</userinput></screen> <screen>&prompt.root; <userinput>kill -HUP 1</userinput></screen>
<para>This forces the <command>init</command> process to reread <para>This forces the &man.init.8; process to reread
<filename>/etc/ttys</filename>. The init process will then start getty <filename>/etc/ttys</filename>. The init process will then start getty
processes on all <literal>on</literal> ports. You can find processes on all <literal>on</literal> ports. You can find
out if logins are available for your port by typing</para> out if logins are available for your port by typing</para>
@ -10416,7 +10416,7 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr</programlist
dialer.</para> dialer.</para>
<para>Alternatively, you can let everyone on your system <para>Alternatively, you can let everyone on your system
run <command>tip</command> and <command>cu</command> by run &man.tip.1; and &man.cu.1; by
typing:</para> typing:</para>
<screen>&prompt.root; <userinput>chmod 4511 /usr/bin/cu</userinput> <screen>&prompt.root; <userinput>chmod 4511 /usr/bin/cu</userinput>
@ -10443,12 +10443,12 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr</programlist
should turn those messages off when you use &man.tip.1; should turn those messages off when you use &man.tip.1;
(using <literal>ATX0&amp;W</literal>).</para> (using <literal>ATX0&amp;W</literal>).</para>
<para>Also, the dial timeout for <command>tip</command> is 60 <para>Also, the dial timeout for &man.tip.1; is 60
seconds. Your modem should use something less, or else tip seconds. Your modem should use something less, or else tip
will think there's a communication problem. Try will think there's a communication problem. Try
<literal>ATS7=45&amp;W</literal>.</para> <literal>ATS7=45&amp;W</literal>.</para>
<para>Actually, as shipped <command>tip</command> doesn't yet <para>Actually, as shipped &man.tip.1; doesn't yet
support it fully. The solution is to edit the file support it fully. The solution is to edit the file
<filename>tipconf.h</filename> in the directory <filename>tipconf.h</filename> in the directory
<filename>/usr/src/usr.bin/tip/tip</filename>. Obviously you <filename>/usr/src/usr.bin/tip/tip</filename>. Obviously you
@ -10611,7 +10611,7 @@ big-university 5551114</programlisting>
<para>&man.tip.1; <para>&man.tip.1;
will try each one in the listed order, then give will try each one in the listed order, then give
up. If you want to keep retrying, run <command>tip</command> up. If you want to keep retrying, run &man.tip.1;
in a while loop.</para> in a while loop.</para>
</answer> </answer>
</qandaentry> </qandaentry>
@ -10764,7 +10764,7 @@ raisechar=^^</programlisting>
<qandaentry> <qandaentry>
<question id="top-freemem"> <question id="top-freemem">
<para>Why does &man.top.1; show very little free memory even <para>Why does <command>top</command> show very little free memory even
when I have very few programs running?</para> when I have very few programs running?</para>
</question> </question>
@ -10991,7 +10991,7 @@ raisechar=^^</programlisting>
<acronym>RECURSIVE</acronym> <acronym>RECURSIVE</acronym>
&man.chmod.1;. Be careful about &man.chmod.1;. Be careful about
specifying directories or symlinks to directories to specifying directories or symlinks to directories to
<command>chmod</command>. If you want to &man.chmod.1;. If you want to
change the permissions of a directory referenced by a change the permissions of a directory referenced by a
symlink, use &man.chmod.1; symlink, use &man.chmod.1;
without any options and follow the symlink without any options and follow the symlink
@ -11240,7 +11240,7 @@ raisechar=^^</programlisting>
this history very useful, a repository copy is often used this history very useful, a repository copy is often used
instead. This is a process where one of the repository meisters instead. This is a process where one of the repository meisters
will copy the files directly within the repository, rather than will copy the files directly within the repository, rather than
using the <command>cvs</command> program.</para> using the &man.cvs.1; program.</para>
</answer> </answer>
</qandaentry> </qandaentry>
@ -12126,7 +12126,7 @@ SECTIONS
&man.top.1; and the like; <command>make &man.top.1; and the like; <command>make
world</command> should take care of it (or a manual rebuild of world</command> should take care of it (or a manual rebuild of
<filename>libkvm</filename>, <filename>libkvm</filename>,
<command>ps</command> and <command>top</command> &man.ps.1; and &man.top.1;
after copying the patched <filename>pmap.h</filename> to after copying the patched <filename>pmap.h</filename> to
<filename>/usr/include/vm/</filename>.</para> <filename>/usr/include/vm/</filename>.</para>