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

Minor whitespace cleanup: Nuke all spaces at EOL and fix inline

Browse source 
entities of the form <foo> bar </foo> to be <foo>bar</foo>.

No content or markup changes in this commit.

Reviewed by:	alex
Inspired by:	German translation, rev. 1.79
This commit is contained in:
Udo Erdelhoff 2001-05-16 16:59:53 +00:00
parent 76bd774fd3
commit 6fed51db98
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=9448
2 changed files with 274 additions and 274 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -14,7 +14,7 @@
<corpauthor>The FreeBSD Documentation Project</corpauthor>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.194 2001/05/15 00:24:18 dd Exp $</pubdate>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.195 2001/05/15 21:00:11 ue Exp $</pubdate>
<copyright>
<year>1995</year>
@ -380,7 +380,7 @@
<qandaentry>
<question id="responsible">
<para> Who is responsible for FreeBSD?</para>
<para>Who is responsible for FreeBSD?</para>
</question>
<answer>
@ -1185,23 +1185,23 @@ File: +DESC (ignored)</screen>
<itemizedlist>
<listitem>
<para> bin/<!-- <br> --></para>
<para>bin/<!-- <br> --></para>
</listitem>
<listitem>
<para> manpages/<!-- <br> --></para>
<para>manpages/<!-- <br> --></para>
</listitem>
<listitem>
<para> compat*/<!-- <br> --></para>
<para>compat*/<!-- <br> --></para>
</listitem>
<listitem>
<para> doc/ <!-- <br> --></para>
<para>doc/ <!-- <br> --></para>
</listitem>
<listitem>
<para> src/ssys.* <!-- <br> --></para>
<para>src/ssys.* <!-- <br> --></para>
</listitem>
</itemizedlist>
@ -1447,7 +1447,7 @@ File: +DESC (ignored)</screen>
suspend-to-disk partition. When the BIOS tries to parse the
FreeBSD partition it hangs.</para>
<para>According to IBM<footnote> <para>In an e-mail from Keith
<para>According to IBM<footnote><para>In an e-mail from Keith
Frechette
<email>kfrechet@us.ibm.com</email>.</para></footnote>, the
following model/BIOS release numbers incorporate the fix.</para>
@ -2584,7 +2584,7 @@ Filesystem 1024-blocks Used Avail Capacity Mounted on
<chapter
id="hardware">
<title>Hardware compatibility </title>
<title>Hardware compatibility</title>
<qandaset>
<qandaentry>
@ -3270,7 +3270,7 @@ diff -u -r1.60.2.1 -r1.60.2.2
<para>See the <ulink
URL="../handbook/install-hw.html#INSTALL-NICS">
Ethernet cards</ulink> section of the handbook for a more
complete list. </para>
complete list.</para>
</answer>
</qandaentry>
@ -3364,7 +3364,7 @@ diff -u -r1.60.2.1 -r1.60.2.2
A CAM-enhanced boot floppy is available at <ulink
URL="http://people.FreeBSD.org/~abial/cam-boot/">
http://people.FreeBSD.org/~abial/cam-boot/</ulink>.
In both cases read the README before beginning. </para>
In both cases read the README before beginning.</para>
</answer>
</qandaentry>
@ -3714,7 +3714,7 @@ quit</programlisting>
<para>If you're using the BNC connector on your network card,
you may also see device timeouts because of bad termination. To
check this, attach a terminator directly to the NIC (with no
cable) and see if the error messages go away. </para>
cable) and see if the error messages go away.</para>
<para>Some NE2000 compatible cards will give this error if there
is no link on the UTP port or if the cable is disconnected.</para>
@ -3872,7 +3872,7 @@ quit</programlisting>
<para>In the second case you need to verify that it's not your
hardware at fault.</para>
<para> Common causes of this include :</para>
<para>Common causes of this include:</para>
<orderedlist>
<listitem>
@ -4207,7 +4207,7 @@ quit</programlisting>
<screen>&prompt.root; <userinput>sysctl -w kern.timecounter.method=1</userinput></screen>
<para> This means a performance impact, but considering the cause
<para>This means a performance impact, but considering the cause
of this problem, you probably will not notice. If the problem
persists, keep the sysctl set to one and set the
<literal>NTIMECOUNTER</literal> option in your kernel to
@ -4557,7 +4557,7 @@ kern.timecounter.hardware: TSC -> i8254</screen>
<listitem>
<para><ulink url="http://www.wccdrom.com">BSDi</ulink>
offers a FreeBSD native version of <ulink
url="http://www.vistasource.com">VistaSource </ulink>
url="http://www.vistasource.com">VistaSource</ulink>
ApplixWare 5.</para>
<para>ApplixWare is a rich full-featured, commercial
@ -6093,107 +6093,107 @@ C:\="DOS"</programlisting>
<itemizedlist>
<listitem>
<para>Belgian ISO-8859-1 </para>
<para>Belgian ISO-8859-1</para>
</listitem>
<listitem>
<para>Brazilian 275 keyboard Codepage 850 </para>
<para>Brazilian 275 keyboard Codepage 850</para>
</listitem>
<listitem>
<para>Brazilian 275 keyboard ISO-8859-1 </para>
<para>Brazilian 275 keyboard ISO-8859-1</para>
</listitem>
<listitem>
<para>Danish Codepage 865 </para>
<para>Danish Codepage 865</para>
</listitem>
<listitem>
<para>Danish ISO-8859-1 </para>
<para>Danish ISO-8859-1</para>
</listitem>
<listitem>
<para>French ISO-8859-1 </para>
<para>French ISO-8859-1</para>
</listitem>
<listitem>
<para>German Codepage 850 </para>
<para>German Codepage 850</para>
</listitem>
<listitem>
<para>German ISO-8859-1 </para>
<para>German ISO-8859-1</para>
</listitem>
<listitem>
<para>Italian ISO-8859-1 </para>
<para>Italian ISO-8859-1</para>
</listitem>
<listitem>
<para>Japanese 106 </para>
<para>Japanese 106</para>
</listitem>
<listitem>
<para>Japanese 106x </para>
<para>Japanese 106x</para>
</listitem>
<listitem>
<para>Latin American </para>
<para>Latin American</para>
</listitem>
<listitem>
<para>Norwegian ISO-8859-1 </para>
<para>Norwegian ISO-8859-1</para>
</listitem>
<listitem>
<para>Polish ISO-8859-2 (programmer's) </para>
<para>Polish ISO-8859-2 (programmer's)</para>
</listitem>
<listitem>
<para>Russian Codepage 866 (alternative) </para>
<para>Russian Codepage 866 (alternative)</para>
</listitem>
<listitem>
<para>Russian koi8-r (shift) </para>
<para>Russian koi8-r (shift)</para>
</listitem>
<listitem>
<para>Russian koi8-r </para>
<para>Russian koi8-r</para>
</listitem>
<listitem>
<para>Spanish ISO-8859-1 </para>
<para>Spanish ISO-8859-1</para>
</listitem>
<listitem>
<para>Swedish Codepage 850 </para>
<para>Swedish Codepage 850</para>
</listitem>
<listitem>
<para>Swedish ISO-8859-1 </para>
<para>Swedish ISO-8859-1</para>
</listitem>
<listitem>
<para>Swiss-German ISO-8859-1 </para>
<para>Swiss-German ISO-8859-1</para>
</listitem>
<listitem>
<para>United Kingdom Codepage 850 </para>
<para>United Kingdom Codepage 850</para>
</listitem>
<listitem>
<para>United Kingdom ISO-8859-1 </para>
<para>United Kingdom ISO-8859-1</para>
</listitem>
<listitem>
<para>United States of America ISO-8859-1 </para>
<para>United States of America ISO-8859-1</para>
</listitem>
<listitem>
<para>United States of America dvorak </para>
<para>United States of America dvorak</para>
</listitem>
<listitem>
<para>United States of America dvorakx </para>
<para>United States of America dvorakx</para>
</listitem>
</itemizedlist>
</answer>
@ -6471,7 +6471,7 @@ if-bus.UUCP uucp-dom:if-bus
<para>Final hint: if you are uncertain whether some particular
mail routing would work, remember the <option>-bt</option>
option to sendmail. It starts sendmail in <emphasis>address
test mode</emphasis>; simply enter <literal>0 </literal>,
test mode</emphasis>; simply enter <literal>0</literal>,
followed by the address you wish to test for the mail routing.
The last line tells you the used internal mail agent, the
destination host this agent will be called with, and the
@ -6630,7 +6630,7 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
read/write, then run <command>mount -a</command> to remount all
the filesystems. Run <command>passwd root</command> to change
the root password then run <command>exit</command> to continue
booting. </para>
booting.</para>
</answer>
</qandaentry>
@ -7051,15 +7051,15 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
<filename>/dev/fd0</filename> onto a directory that they
own:</para>
<screen>&prompt.user; <userinput> mkdir ~/my-mount-point</userinput>
&prompt.user; <userinput> mount -t msdos /dev/fd0 ~/my-mount-point</userinput></screen>
<screen>&prompt.user; <userinput>mkdir ~/my-mount-point</userinput>
&prompt.user; <userinput>mount -t msdos /dev/fd0 ~/my-mount-point</userinput></screen>
<para>Users in group <username>operator</username> can now
mount the cdrom <filename>/dev/cd0c</filename> onto a
directory that they own:</para>
<screen>&prompt.user; <userinput> mkdir ~/my-mount-point</userinput>
&prompt.user; <userinput> mount -t msdos /dev/cd0c ~/my-mount-point</userinput></screen>
<screen>&prompt.user; <userinput>mkdir ~/my-mount-point</userinput>
&prompt.user; <userinput>mount -t msdos /dev/cd0c ~/my-mount-point</userinput></screen>
<para>Unmounting the device is simple:</para>
@ -7800,13 +7800,13 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure</programlisting>
<filename>/usr/local/etc/rc.d</filename>. Both are equally
valid, and one may work in situations where the other doesn't.
In both cases the result is the same: X will popup a graphical
login: prompt. </para>
login: prompt.</para>
<para>The ttys method has the advantage of documenting which
vty X will start on and passing the responsibility of
restarting the X server on logout to init. The rc.local
method makes it easy to kill xdm if there is a problem
starting the X server. </para>
starting the X server.</para>
<para>If loaded from rc.local, <command>xdm</command> should
be started without any arguments (i.e., as a daemon). xdm must
@ -8030,7 +8030,7 @@ UserConfig&gt; <userinput>quit</userinput></screen>
application building tool. Imake.tmpl, as well as several
header files that are required to build X apps, is contained
in the X prog distribution. You can install this from sysinstall
or manually from the X distribution files. </para>
or manually from the X distribution files.</para>
</answer>
</qandaentry>
@ -8263,7 +8263,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
&man.routed.8;
or for more complex situations you may want to try
<emphasis>GaTeD</emphasis> (available from <ulink
URL="http://www.gated.org/"> http://www.gated.org/ </ulink>)
URL="http://www.gated.org/">http://www.gated.org/</ulink>)
which supports FreeBSD as of 3_5Alpha7.</para>
<para>It is our duty to warn you that, even when FreeBSD is
@ -8285,7 +8285,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
use the FreeBSD box to connect to the Internet and then be able
to access the Internet from the Windows95 box through the
FreeBSD box. This is really just a special case of the previous
question.</para> <para> ... and the answer is yes! In FreeBSD
question.</para> <para>... and the answer is yes! In FreeBSD
3.x, user-mode ppp contains a <option>-nat</option> option. If
you run <command>ppp</command> with the <option>-nat</option>,
set <literal>gateway_enable</literal> to
@ -8816,7 +8816,7 @@ Znyx (2.2.x) ZX312, ZX314, ZX342, ZX345, ZX346, ZX348
URL="http://www.csl.sony.co.jp/person/kjc/programs.html">
ALTQ</ulink> is available for free; Bandwidth Manager from
<ulink URL="http://www.etinc.com/">Emerging Technologies</ulink>
is a commercial product. </para>
is a commercial product.</para>
</answer>
</qandaentry>
@ -10034,7 +10034,7 @@ ATDT1234567</programlisting>
URL="http://search.support.microsoft.com/kb">Microsoft Knowledge
Base</ulink> documents <quote>Q158474 - Windows TCPIP Registry
Entries</quote> and <quote>Q120642 - TCPIP & NBT Configuration
Parameters for Windows NT </quote> for more information on
Parameters for Windows NT</quote> for more information on
changing Windoze MTU to work with a FreeBSD/NAT/PPPoE
router.</para>
@ -10740,7 +10740,7 @@ raisechar=^^</programlisting>
to make more main memory available for active use. Linux tends
to only move pages to swap as a last resort. The perceived
heavier use of swap is balanced by the more efficient use of
main memory. </para>
main memory.</para>
<para>Note that while FreeBSD is proactive in this regard, it
does not arbitrarily decide to swap pages when the system is
@ -10775,7 +10775,7 @@ raisechar=^^</programlisting>
<qandaentry>
<question id="aout-elf">
<para>Why use (what are) a.out and ELF executable
formats? </para>
formats?</para>
</question>
<answer>
@ -11884,7 +11884,7 @@ Cc: current@FreeBSD.org</programlisting>
only <emphasis>you</emphasis> can tell us where the fault
occured.</para>
<para> What you should do is this:</para>
<para>What you should do is this:</para>
<itemizedlist>
<listitem>
@ -11919,12 +11919,12 @@ Cc: current@FreeBSD.org</programlisting>
</listitem>
</itemizedlist>
<para> I see people constantly show panic messages like this
<para>I see people constantly show panic messages like this
but rarely do I see someone take the time to match up the
instruction pointer with a function in the kernel symbol
table.</para>
<para> The best way to track down the cause of a panic is by
<para>The best way to track down the cause of a panic is by
capturing a crash dump, then using
<command>gdb(1)</command> to generate a stack trace on the
crash dump.</para>
@ -11972,7 +11972,7 @@ Cc: current@FreeBSD.org</programlisting>
<filename>kernel.debug</filename> can be used as the source of
debugging symbols for gdb(1).</para>
<para> To make sure you capture a crash dump, you need edit
<para>To make sure you capture a crash dump, you need edit
<filename>/etc/rc.conf</filename> and set
<literal>dumpdev</literal> to point to your swap
partition. This will cause the <command>rc(8)</command> scripts
@ -12004,13 +12004,13 @@ Cc: current@FreeBSD.org</programlisting>
will be 16MB instead of 128MB.</para>
</note></para>
<para> Once you have recovered the crash dump, you can get a
<para>Once you have recovered the crash dump, you can get a
stack trace with <command>gdb(1)</command> as follows:</para>
<screen>&prompt.user; <userinput>gdb -k /sys/compile/KERNELCONFIG/kernel.debug /var/crash/vmcore.0</userinput>
<prompt>(gdb)</prompt> <userinput>where</userinput></screen>
<para> Note that there may be several screens worth of
<para>Note that there may be several screens worth of
information; ideally you should use
<command>script(1)</command> to capture all of them. Using the
unstripped kernel image with all the debug symbols should show
@ -12021,7 +12021,7 @@ Cc: current@FreeBSD.org</programlisting>
the contents of various variables or structures in order to
examine the system state at the time of the crash.</para>
<para> Now, if you're really insane and have a second computer,
<para>Now, if you're really insane and have a second computer,
you can also configure <command>gdb(1)</command> to do remote
debugging such that you can use <command>gdb(1)</command> on
one system to debug the kernel on another system, including
@ -12030,7 +12030,7 @@ Cc: current@FreeBSD.org</programlisting>
played with this yet as I don't often have the chance to set up
two machines side by side for debugging purposes.</para>
<para> <emphasis>[Bill adds: "I forgot to mention one thing: if
<para><emphasis>[Bill adds: "I forgot to mention one thing: if
you have DDB enabled and the kernel drops into the debugger,
you can force a panic (and a crash dump) just by typing 'panic'
at the ddb prompt. It may stop in the debugger again during the
@ -12127,7 +12127,7 @@ SECTIONS
<para>NOTE: the size of the kernel address space must be a
multiple of four megabytes.</para>
<para>[&a.dg; adds: <emphasis> I think the kernel address space
<para>[&a.dg; adds: <emphasis>I think the kernel address space
needs to be a power of two, but I'm not certain about that. The
old(er) boot code used to monkey with the high order address bits
and I think expected at least 256MB

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

@ -14,7 +14,7 @@
<corpauthor>The FreeBSD Documentation Project</corpauthor>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.194 2001/05/15 00:24:18 dd Exp $</pubdate>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.195 2001/05/15 21:00:11 ue Exp $</pubdate>
<copyright>
<year>1995</year>
@ -380,7 +380,7 @@
<qandaentry>
<question id="responsible">
<para> Who is responsible for FreeBSD?</para>
<para>Who is responsible for FreeBSD?</para>
</question>
<answer>
@ -1185,23 +1185,23 @@ File: +DESC (ignored)</screen>
<itemizedlist>
<listitem>
<para> bin/<!-- <br> --></para>
<para>bin/<!-- <br> --></para>
</listitem>
<listitem>
<para> manpages/<!-- <br> --></para>
<para>manpages/<!-- <br> --></para>
</listitem>
<listitem>
<para> compat*/<!-- <br> --></para>
<para>compat*/<!-- <br> --></para>
</listitem>
<listitem>
<para> doc/ <!-- <br> --></para>
<para>doc/ <!-- <br> --></para>
</listitem>
<listitem>
<para> src/ssys.* <!-- <br> --></para>
<para>src/ssys.* <!-- <br> --></para>
</listitem>
</itemizedlist>
@ -1447,7 +1447,7 @@ File: +DESC (ignored)</screen>
suspend-to-disk partition. When the BIOS tries to parse the
FreeBSD partition it hangs.</para>
<para>According to IBM<footnote> <para>In an e-mail from Keith
<para>According to IBM<footnote><para>In an e-mail from Keith
Frechette
<email>kfrechet@us.ibm.com</email>.</para></footnote>, the
following model/BIOS release numbers incorporate the fix.</para>
@ -2584,7 +2584,7 @@ Filesystem 1024-blocks Used Avail Capacity Mounted on
<chapter
id="hardware">
<title>Hardware compatibility </title>
<title>Hardware compatibility</title>
<qandaset>
<qandaentry>
@ -3270,7 +3270,7 @@ diff -u -r1.60.2.1 -r1.60.2.2
<para>See the <ulink
URL="../handbook/install-hw.html#INSTALL-NICS">
Ethernet cards</ulink> section of the handbook for a more
complete list. </para>
complete list.</para>
</answer>
</qandaentry>
@ -3364,7 +3364,7 @@ diff -u -r1.60.2.1 -r1.60.2.2
A CAM-enhanced boot floppy is available at <ulink
URL="http://people.FreeBSD.org/~abial/cam-boot/">
http://people.FreeBSD.org/~abial/cam-boot/</ulink>.
In both cases read the README before beginning. </para>
In both cases read the README before beginning.</para>
</answer>
</qandaentry>
@ -3714,7 +3714,7 @@ quit</programlisting>
<para>If you're using the BNC connector on your network card,
you may also see device timeouts because of bad termination. To
check this, attach a terminator directly to the NIC (with no
cable) and see if the error messages go away. </para>
cable) and see if the error messages go away.</para>
<para>Some NE2000 compatible cards will give this error if there
is no link on the UTP port or if the cable is disconnected.</para>
@ -3872,7 +3872,7 @@ quit</programlisting>
<para>In the second case you need to verify that it's not your
hardware at fault.</para>
<para> Common causes of this include :</para>
<para>Common causes of this include:</para>
<orderedlist>
<listitem>
@ -4207,7 +4207,7 @@ quit</programlisting>
<screen>&prompt.root; <userinput>sysctl -w kern.timecounter.method=1</userinput></screen>
<para> This means a performance impact, but considering the cause
<para>This means a performance impact, but considering the cause
of this problem, you probably will not notice. If the problem
persists, keep the sysctl set to one and set the
<literal>NTIMECOUNTER</literal> option in your kernel to
@ -4557,7 +4557,7 @@ kern.timecounter.hardware: TSC -> i8254</screen>
<listitem>
<para><ulink url="http://www.wccdrom.com">BSDi</ulink>
offers a FreeBSD native version of <ulink
url="http://www.vistasource.com">VistaSource </ulink>
url="http://www.vistasource.com">VistaSource</ulink>
ApplixWare 5.</para>
<para>ApplixWare is a rich full-featured, commercial
@ -6093,107 +6093,107 @@ C:\="DOS"</programlisting>
<itemizedlist>
<listitem>
<para>Belgian ISO-8859-1 </para>
<para>Belgian ISO-8859-1</para>
</listitem>
<listitem>
<para>Brazilian 275 keyboard Codepage 850 </para>
<para>Brazilian 275 keyboard Codepage 850</para>
</listitem>
<listitem>
<para>Brazilian 275 keyboard ISO-8859-1 </para>
<para>Brazilian 275 keyboard ISO-8859-1</para>
</listitem>
<listitem>
<para>Danish Codepage 865 </para>
<para>Danish Codepage 865</para>
</listitem>
<listitem>
<para>Danish ISO-8859-1 </para>
<para>Danish ISO-8859-1</para>
</listitem>
<listitem>
<para>French ISO-8859-1 </para>
<para>French ISO-8859-1</para>
</listitem>
<listitem>
<para>German Codepage 850 </para>
<para>German Codepage 850</para>
</listitem>
<listitem>
<para>German ISO-8859-1 </para>
<para>German ISO-8859-1</para>
</listitem>
<listitem>
<para>Italian ISO-8859-1 </para>
<para>Italian ISO-8859-1</para>
</listitem>
<listitem>
<para>Japanese 106 </para>
<para>Japanese 106</para>
</listitem>
<listitem>
<para>Japanese 106x </para>
<para>Japanese 106x</para>
</listitem>
<listitem>
<para>Latin American </para>
<para>Latin American</para>
</listitem>
<listitem>
<para>Norwegian ISO-8859-1 </para>
<para>Norwegian ISO-8859-1</para>
</listitem>
<listitem>
<para>Polish ISO-8859-2 (programmer's) </para>
<para>Polish ISO-8859-2 (programmer's)</para>
</listitem>
<listitem>
<para>Russian Codepage 866 (alternative) </para>
<para>Russian Codepage 866 (alternative)</para>
</listitem>
<listitem>
<para>Russian koi8-r (shift) </para>
<para>Russian koi8-r (shift)</para>
</listitem>
<listitem>
<para>Russian koi8-r </para>
<para>Russian koi8-r</para>
</listitem>
<listitem>
<para>Spanish ISO-8859-1 </para>
<para>Spanish ISO-8859-1</para>
</listitem>
<listitem>
<para>Swedish Codepage 850 </para>
<para>Swedish Codepage 850</para>
</listitem>
<listitem>
<para>Swedish ISO-8859-1 </para>
<para>Swedish ISO-8859-1</para>
</listitem>
<listitem>
<para>Swiss-German ISO-8859-1 </para>
<para>Swiss-German ISO-8859-1</para>
</listitem>
<listitem>
<para>United Kingdom Codepage 850 </para>
<para>United Kingdom Codepage 850</para>
</listitem>
<listitem>
<para>United Kingdom ISO-8859-1 </para>
<para>United Kingdom ISO-8859-1</para>
</listitem>
<listitem>
<para>United States of America ISO-8859-1 </para>
<para>United States of America ISO-8859-1</para>
</listitem>
<listitem>
<para>United States of America dvorak </para>
<para>United States of America dvorak</para>
</listitem>
<listitem>
<para>United States of America dvorakx </para>
<para>United States of America dvorakx</para>
</listitem>
</itemizedlist>
</answer>
@ -6471,7 +6471,7 @@ if-bus.UUCP uucp-dom:if-bus
<para>Final hint: if you are uncertain whether some particular
mail routing would work, remember the <option>-bt</option>
option to sendmail. It starts sendmail in <emphasis>address
test mode</emphasis>; simply enter <literal>0 </literal>,
test mode</emphasis>; simply enter <literal>0</literal>,
followed by the address you wish to test for the mail routing.
The last line tells you the used internal mail agent, the
destination host this agent will be called with, and the
@ -6630,7 +6630,7 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
read/write, then run <command>mount -a</command> to remount all
the filesystems. Run <command>passwd root</command> to change
the root password then run <command>exit</command> to continue
booting. </para>
booting.</para>
</answer>
</qandaentry>
@ -7051,15 +7051,15 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
<filename>/dev/fd0</filename> onto a directory that they
own:</para>
<screen>&prompt.user; <userinput> mkdir ~/my-mount-point</userinput>
&prompt.user; <userinput> mount -t msdos /dev/fd0 ~/my-mount-point</userinput></screen>
<screen>&prompt.user; <userinput>mkdir ~/my-mount-point</userinput>
&prompt.user; <userinput>mount -t msdos /dev/fd0 ~/my-mount-point</userinput></screen>
<para>Users in group <username>operator</username> can now
mount the cdrom <filename>/dev/cd0c</filename> onto a
directory that they own:</para>
<screen>&prompt.user; <userinput> mkdir ~/my-mount-point</userinput>
&prompt.user; <userinput> mount -t msdos /dev/cd0c ~/my-mount-point</userinput></screen>
<screen>&prompt.user; <userinput>mkdir ~/my-mount-point</userinput>
&prompt.user; <userinput>mount -t msdos /dev/cd0c ~/my-mount-point</userinput></screen>
<para>Unmounting the device is simple:</para>
@ -7800,13 +7800,13 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure</programlisting>
<filename>/usr/local/etc/rc.d</filename>. Both are equally
valid, and one may work in situations where the other doesn't.
In both cases the result is the same: X will popup a graphical
login: prompt. </para>
login: prompt.</para>
<para>The ttys method has the advantage of documenting which
vty X will start on and passing the responsibility of
restarting the X server on logout to init. The rc.local
method makes it easy to kill xdm if there is a problem
starting the X server. </para>
starting the X server.</para>
<para>If loaded from rc.local, <command>xdm</command> should
be started without any arguments (i.e., as a daemon). xdm must
@ -8030,7 +8030,7 @@ UserConfig&gt; <userinput>quit</userinput></screen>
application building tool. Imake.tmpl, as well as several
header files that are required to build X apps, is contained
in the X prog distribution. You can install this from sysinstall
or manually from the X distribution files. </para>
or manually from the X distribution files.</para>
</answer>
</qandaentry>
@ -8263,7 +8263,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
&man.routed.8;
or for more complex situations you may want to try
<emphasis>GaTeD</emphasis> (available from <ulink
URL="http://www.gated.org/"> http://www.gated.org/ </ulink>)
URL="http://www.gated.org/">http://www.gated.org/</ulink>)
which supports FreeBSD as of 3_5Alpha7.</para>
<para>It is our duty to warn you that, even when FreeBSD is
@ -8285,7 +8285,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
use the FreeBSD box to connect to the Internet and then be able
to access the Internet from the Windows95 box through the
FreeBSD box. This is really just a special case of the previous
question.</para> <para> ... and the answer is yes! In FreeBSD
question.</para> <para>... and the answer is yes! In FreeBSD
3.x, user-mode ppp contains a <option>-nat</option> option. If
you run <command>ppp</command> with the <option>-nat</option>,
set <literal>gateway_enable</literal> to
@ -8816,7 +8816,7 @@ Znyx (2.2.x) ZX312, ZX314, ZX342, ZX345, ZX346, ZX348
URL="http://www.csl.sony.co.jp/person/kjc/programs.html">
ALTQ</ulink> is available for free; Bandwidth Manager from
<ulink URL="http://www.etinc.com/">Emerging Technologies</ulink>
is a commercial product. </para>
is a commercial product.</para>
</answer>
</qandaentry>
@ -10034,7 +10034,7 @@ ATDT1234567</programlisting>
URL="http://search.support.microsoft.com/kb">Microsoft Knowledge
Base</ulink> documents <quote>Q158474 - Windows TCPIP Registry
Entries</quote> and <quote>Q120642 - TCPIP & NBT Configuration
Parameters for Windows NT </quote> for more information on
Parameters for Windows NT</quote> for more information on
changing Windoze MTU to work with a FreeBSD/NAT/PPPoE
router.</para>
@ -10740,7 +10740,7 @@ raisechar=^^</programlisting>
to make more main memory available for active use. Linux tends
to only move pages to swap as a last resort. The perceived
heavier use of swap is balanced by the more efficient use of
main memory. </para>
main memory.</para>
<para>Note that while FreeBSD is proactive in this regard, it
does not arbitrarily decide to swap pages when the system is
@ -10775,7 +10775,7 @@ raisechar=^^</programlisting>
<qandaentry>
<question id="aout-elf">
<para>Why use (what are) a.out and ELF executable
formats? </para>
formats?</para>
</question>
<answer>
@ -11884,7 +11884,7 @@ Cc: current@FreeBSD.org</programlisting>
only <emphasis>you</emphasis> can tell us where the fault
occured.</para>
<para> What you should do is this:</para>
<para>What you should do is this:</para>
<itemizedlist>
<listitem>
@ -11919,12 +11919,12 @@ Cc: current@FreeBSD.org</programlisting>
</listitem>
</itemizedlist>
<para> I see people constantly show panic messages like this
<para>I see people constantly show panic messages like this
but rarely do I see someone take the time to match up the
instruction pointer with a function in the kernel symbol
table.</para>
<para> The best way to track down the cause of a panic is by
<para>The best way to track down the cause of a panic is by
capturing a crash dump, then using
<command>gdb(1)</command> to generate a stack trace on the
crash dump.</para>
@ -11972,7 +11972,7 @@ Cc: current@FreeBSD.org</programlisting>
<filename>kernel.debug</filename> can be used as the source of
debugging symbols for gdb(1).</para>
<para> To make sure you capture a crash dump, you need edit
<para>To make sure you capture a crash dump, you need edit
<filename>/etc/rc.conf</filename> and set
<literal>dumpdev</literal> to point to your swap
partition. This will cause the <command>rc(8)</command> scripts
@ -12004,13 +12004,13 @@ Cc: current@FreeBSD.org</programlisting>
will be 16MB instead of 128MB.</para>
</note></para>
<para> Once you have recovered the crash dump, you can get a
<para>Once you have recovered the crash dump, you can get a
stack trace with <command>gdb(1)</command> as follows:</para>
<screen>&prompt.user; <userinput>gdb -k /sys/compile/KERNELCONFIG/kernel.debug /var/crash/vmcore.0</userinput>
<prompt>(gdb)</prompt> <userinput>where</userinput></screen>
<para> Note that there may be several screens worth of
<para>Note that there may be several screens worth of
information; ideally you should use
<command>script(1)</command> to capture all of them. Using the
unstripped kernel image with all the debug symbols should show
@ -12021,7 +12021,7 @@ Cc: current@FreeBSD.org</programlisting>
the contents of various variables or structures in order to
examine the system state at the time of the crash.</para>
<para> Now, if you're really insane and have a second computer,
<para>Now, if you're really insane and have a second computer,
you can also configure <command>gdb(1)</command> to do remote
debugging such that you can use <command>gdb(1)</command> on
one system to debug the kernel on another system, including
@ -12030,7 +12030,7 @@ Cc: current@FreeBSD.org</programlisting>
played with this yet as I don't often have the chance to set up
two machines side by side for debugging purposes.</para>
<para> <emphasis>[Bill adds: "I forgot to mention one thing: if
<para><emphasis>[Bill adds: "I forgot to mention one thing: if
you have DDB enabled and the kernel drops into the debugger,
you can force a panic (and a crash dump) just by typing 'panic'
at the ddb prompt. It may stop in the debugger again during the
@ -12127,7 +12127,7 @@ SECTIONS
<para>NOTE: the size of the kernel address space must be a
multiple of four megabytes.</para>
<para>[&a.dg; adds: <emphasis> I think the kernel address space
<para>[&a.dg; adds: <emphasis>I think the kernel address space
needs to be a power of two, but I'm not certain about that. The
old(er) boot code used to monkey with the high order address bits
and I think expected at least 256MB