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

274
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>
@ -47,7 +47,7 @@
FAQ</ulink>.</para>
</abstract>
</bookinfo>
<preface id="preface">
<title>Preface</title>
@ -266,7 +266,7 @@
and <ulink URL="ftp://releng4.FreeBSD.org/pub/FreeBSD">
releng4.FreeBSD.org</ulink> for 4-STABLE snapshots.
3-STABLE snapshots are not being produced at the time of
this writing (May 2000).</para>
this writing (May 2000).</para>
<para>Snapshots are generated, on the average, once a day for
all actively developed branches.</para>
@ -380,7 +380,7 @@
<qandaentry>
<question id="responsible">
<para> Who is responsible for FreeBSD?</para>
<para>Who is responsible for FreeBSD?</para>
</question>
<answer>
@ -727,14 +727,14 @@
<qandaentry>
<question id="doc-formats">
<para>Is the documentation available in other formats, such as plain
<para>Is the documentation available in other formats, such as plain
text (ASCII), or Postscript?</para>
</question>
<answer>
<para>Yes. The documentation is available in a number of different
formats and compression schemes on the FreeBSD FTP site, in the
<ulink
<ulink
URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/">/pub/FreeBSD/doc/</ulink> directory.</para>
<para>The documentation is categorised in a number of different
@ -750,7 +750,7 @@
<para>The document's language and encoding. These are based on
the locale names you will find under
<filename>/usr/share/locale</filename> on your FreeBSD
system. The current languages and encodings that we have for
system. The current languages and encodings that we have for
documentation are as follows:</para>
<informaltable frame="none">
@ -819,35 +819,35 @@
<para>The document's format. We produce the documentation in a
number of different output formats to try and make it as
flexible as possible. The current formats are;</para>
<informaltable frame="none">
<tgroup cols="2">
<thead>
<row>
<entry>Format</entry>
<entry>Meaning</entry>
</row>
</thead>
<tbody>
<row>
<entry><literal>html-split</literal></entry>
<entry>A collection of small, linked, HTML
files.</entry>
</row>
<row>
<entry><literal>html</literal></entry>
<entry>One large HTML file containing the entire
document</entry>
</row>
<row>
<entry><literal>pdb</literal></entry>
<entry>Palm Pilot database format, for use with the
<ulink URL="http://www.iSilo.com/">iSilo</ulink>
reader.</entry>
@ -855,19 +855,19 @@
<row>
<entry><literal>pdf</literal></entry>
<entry>Adobe's Portable Document Format</entry>
</row>
<row>
<entry><literal>ps</literal></entry>
<entry>Postscript</entry>
</row>
<row>
<entry><literal>rtf</literal></entry>
<entry>Microsoft's Rich Text Format<footnote>
<para>Page numbers are not automatically updated
when loading this format in to Word. Press
@ -878,10 +878,10 @@
</footnote>
</entry>
</row>
<row>
<entry><literal>txt</literal></entry>
<entry>Plain text</entry>
</row>
</tbody>
@ -895,7 +895,7 @@
<orderedlist>
<listitem>
<para>Where the format is <literal>html-split</literal>, the
<para>Where the format is <literal>html-split</literal>, the
files are bundled up using &man.tar.1;. The resulting
<filename>.tar</filename> file is then compressed using
the compression schemes detailed in the next point.</para>
@ -919,7 +919,7 @@
<entry>Description</entry>
</row>
</thead>
<tbody>
<row>
<entry><literal>zip</literal></entry>
@ -975,7 +975,7 @@
&man.pkg.delete.1;.</para>
<para>If you decide to download and install the package then you
must know the filename to download. The documentation-as-packages
must know the filename to download. The documentation-as-packages
files are stored in a directory called
<filename>packages</filename>. Each package file looks like
<filename><replaceable>document-name</replaceable>.<replaceable>lang</replaceable>.<replaceable>encoding</replaceable>.<replaceable>format</replaceable>.tgz</filename>.</para>
@ -984,11 +984,11 @@
package called
<filename>faq.en_US.ISO_8859-1.pdf.tgz</filename>.</para>
<para>Knowing this, you can use the following command to install the
<para>Knowing this, you can use the following command to install the
English PDF FAQ package.</para>
<screen>&prompt.root; <userinput>pkg_add ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/packages/faq.en_US.ISO_8859-1.pdf.tgz</userinput></screen>
<para>Having done that, you can use &man.pkg.info.1; to determine
where the file has been installed.</para>
@ -1014,7 +1014,7 @@ File: +DESC (ignored)</screen>
<para>For example, the split HTML version of the FAQ, compressed
using &man.gzip.1;, can be found in the
<filename>en_US.ISO_8859-1/books/faq/book.html-split.tar.gz</filename>
<filename>en_US.ISO_8859-1/books/faq/book.html-split.tar.gz</filename>
file. To download and uncompress that file you would have to do
this.</para>
@ -1040,7 +1040,7 @@ File: +DESC (ignored)</screen>
<para>Certainly! There are multiple ways to mirror the Web
pages.</para>
<itemizedlist>
<listitem>
@ -1053,7 +1053,7 @@ File: +DESC (ignored)</screen>
supfile, which can be found in
<filename>/usr/share/examples/cvsup/www-supfile</filename>.
</para>
</listitem>
<listitem>
@ -1095,7 +1095,7 @@ File: +DESC (ignored)</screen>
<para>The following newsgroups contain pertinent discussion for
FreeBSD users:</para>
<itemizedlist>
<listitem>
@ -1117,7 +1117,7 @@ File: +DESC (ignored)</screen>
<para>Web resources:</para>
<itemizedlist>
<listitem>
@ -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>
@ -1380,7 +1380,7 @@ File: +DESC (ignored)</screen>
<qandaentry>
<question id="win95-damaged-boot-manager">
<para>Windows 95/98 killed my boot manager!
<para>Windows 95/98 killed my boot manager!
How do I get it back?</para>
</question>
@ -1415,7 +1415,7 @@ File: +DESC (ignored)</screen>
</listitem>
<listitem>
<para>Boot the FreeBSD boot floppy (or CD-ROM) and choose the
<para>Boot the FreeBSD boot floppy (or CD-ROM) and choose the
<quote>Fixit</quote> menu item. Select either the Fixit
floppy or CD-ROM #2 (the <quote>live</quote> file system
option) as appropriate and enter the fixit shell. Then
@ -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>
@ -1460,7 +1460,7 @@ File: +DESC (ignored)</screen>
<entry>BIOS revision</entry>
</row>
</thead>
<tbody>
<row>
<entry>T20</entry>
@ -1507,7 +1507,7 @@ File: +DESC (ignored)</screen>
mailing list describes a procedure which may work if your newer
IBM laptop does not boot FreeBSD properly, and you can upgrade or
downgrade the BIOS..</para>
<para>If you have an earlier BIOS, and upgrading is not an option a
workaround is to install FreeBSD, change the partition ID FreeBSD
uses, and install new boot blocks that can handle the different
@ -1584,7 +1584,7 @@ File: +DESC (ignored)</screen>
the reader.</para>
</answer>
</qandaentry>
<qandaentry>
<question id="install-bad-blocks">
<para>Can I install on a disk with bad blocks?</para>
@ -1652,7 +1652,7 @@ File: +DESC (ignored)</screen>
<qandaentry>
<question id="no-install-cdrom">
<para>I booted from my ATAPI CD-ROM, but the install program says no
<para>I booted from my ATAPI CD-ROM, but the install program says no
CD-ROM is found. Where did it go?</para>
</question>
@ -1672,7 +1672,7 @@ File: +DESC (ignored)</screen>
master device.</para>
</answer>
</qandaentry>
<qandaentry>
<question id="cannot-install-tape">
<para>Help! I can't install from tape!</para>
@ -1720,7 +1720,7 @@ IP Address 10.0.0.1 10.0.0.2</programlisting>
<screen>&prompt.root; <userinput>ifconfig lp0 10.0.0.2 10.0.0.1</userinput></screen>
<para>Thats all! Please read also the manpages
<para>Thats all! Please read also the manpages
&man.lp.4; and &man.lpt.4; .</para>
<para>You should also add the hosts to
@ -1755,7 +1755,7 @@ PING moritz (10.0.0.2): 56 data bytes
--- moritz ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms</screen>
</answer>
</qandaentry>
@ -1786,7 +1786,7 @@ round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms</screen>
<entry>Post/Bit</entry>
</row>
</thead>
<tbody>
<row>
<entry><literallayout>DATA0
@ -1835,7 +1835,7 @@ round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms</screen>
<entry><literallayout>0/0x04
1/0x20</literallayout></entry>
</row>
<row>
<entry><literallayout>DATA3
-ACK</literallayout></entry>
@ -1867,7 +1867,7 @@ BUSY</literallayout></entry>
<entry><literallayout>0/0x10
1/0x80</literallayout></entry>
</row>
<row>
<entry>GND</entry>
@ -2061,7 +2061,7 @@ BUSY</literallayout></entry>
<para>To actually select a subset of the sources, use the Custom
menu item when you are in the Distributions menu of the
system installation tool.</para>
system installation tool.</para>
</answer>
</qandaentry>
@ -2089,7 +2089,7 @@ BUSY</literallayout></entry>
<qandaentry>
<question id="password-encryption">
<para>Should I use DES passwords, or MD5, and how do I specify
<para>Should I use DES passwords, or MD5, and how do I specify
which form my users receive?</para>
</question>
@ -2262,7 +2262,7 @@ disk wd2 at wdc1 drive 1 # change from wd3 to wd2</programlisting
<entry>should work</entry>
</row>
</thead>
<tbody>
<row>
<entry>4K</entry>
@ -2410,7 +2410,7 @@ Filesystem 1024-blocks Used Avail Capacity Mounted on
<answer>
<para>We <emphasis>strongly</emphasis> recommend that you use
binary snapshots to do this. 4-STABLE snapshots are available at
<ulink
<ulink
URL="ftp://releng4.FreeBSD.org/">releng4.FreeBSD.org</ulink>.</para>
<para>If you wish to upgrade using source, please see the <ulink
@ -2496,7 +2496,7 @@ Filesystem 1024-blocks Used Avail Capacity Mounted on
<row>
<entry>&man.sshd.8;</entry>
<entry>NO</entry>
<entry>YES</entry>
@ -2568,7 +2568,7 @@ Filesystem 1024-blocks Used Avail Capacity Mounted on
sets up the desired security to convenience ration out of
the box.</para>
</warning>
<note>
<para>The security profile mechanism is meant to be used
when you first install FreeBSD. If you already have
@ -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>
@ -2963,7 +2963,7 @@ moused_flags=""</programlisting>
<para>In 3.1 and later, assuming you have a PS/2 mouse, all you
need to is add <literal>moused_enable="YES"</literal> to
<filename>/etc/rc.conf</filename>.</para>
<filename>/etc/rc.conf</filename>.</para>
<para>In addition, if you would like to be able to use the mouse
daemon on all virtual terminals instead of just console at
@ -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>
@ -3888,7 +3888,7 @@ quit</programlisting>
ensure that you have hardware running at what it's
specified to run at, at least while trying to solve this
problem. i.e. Clock it back to the default settings.</para>
<para>If you are overclocking then note that it's far cheaper
to have a slow system than a fried system that needs
replacing! Also the wider community is not often
@ -3914,7 +3914,7 @@ quit</programlisting>
possible idea is to set to BIOS defaults, but it might be
worth noting down your settings first!</para>
</listitem>
<listitem>
<para>Unclean or insufficient power to the motherboard. If you
have any unused I/O boards, hard disks, or CDROMs in your
@ -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
@ -4505,7 +4505,7 @@ Timecounter "TSC" frequency 595573479 Hz</screen>
<screen>&prompt.root; <userinput>sysctl kern.timecounter.hardware</userinput>
kern.timecounter.hardware: TSC</screen>
<para>The BIOS may modify the TSC clock&mdash;perhaps to change the
speed of the processor when running from batteries, or going in to
a power saving mode, but FreeBSD is unaware of these adjustments,
@ -4557,9 +4557,9 @@ 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
Office Suite for FreeBSD containing a word processor,
spreadsheet, presentation program, vector drawing
@ -5177,7 +5177,7 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx</screen>
hand before you use it. Current versions of
<command>pkg_version</command> force this by inserting an
<command>exit</command> at the beginning of the script.</para>
<para>You should save the output of the script, as it will note
packages that depend on the one that has been udpated. These
may or may not need to be updated as well. The usual case where
@ -5281,7 +5281,7 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx</screen>
should notice a fairly large size decrease; most kernels
tend to be around 1.5MB to 2MB.</para>
</answer>
</qandaentry>
</qandaentry>
<qandaentry>
<question id="multiport-serial-interrupts">
@ -5315,7 +5315,7 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr</programlisting>
<para>Every kernel I try to build fails to compile; even
GENERIC.</para>
</question>
<answer>
<para>There are a number of possible causes for this problem.
They are, in no particular order:</para>
@ -5455,7 +5455,7 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr</programlisting>
<answer>
<para>Whether it's a removable drive like a ZIP or an EZ drive
<para>Whether it's a removable drive like a ZIP or an EZ drive
(or even a floppy, if you want to use it that way), or a new
hard disk, once it's installed and recognized by the system,
and you have your cartridge/floppy/whatever slotted in, things
@ -5541,9 +5541,9 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr</programlisting>
<para>If this is what you did, the extra crontab is simply a
copy of <filename>/etc/crontab</filename> in the wrong
format it. Delete it with the command:</para>
<screen>&prompt.root; <userinput>crontab -r</userinput></screen>
<para>Next time, when you edit
<filename>/etc/crontab</filename>, you should not do
anything to inform &man.cron.8; of the changes, since it
@ -6093,112 +6093,112 @@ 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>
</qandaentry>
<qandaentry>
<question id="pnp-resources">
<para>I get messages like: <errorname>unknown: &lt;PNP0303&gt;
@ -6330,7 +6330,7 @@ use "disklabel -r" to install initial label</screen>
following lines to your kernel config to enable them.</para>
<programlisting>options SYSVSHM
options SYSVSHM # enable shared memory
options SYSVSHM # enable shared memory
options SYSVSEM # enable for semaphores
options SYSVMSG # enable for messaging</programlisting>
@ -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>
@ -7068,7 +7068,7 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
<para>Enabling <varname>vfs.usermount</varname>, however, has
negative security implications. A better way to access MSDOS
formatted media is to use the <ulink
URL="http://www.freebsd.org/cgi/ports.cgi?query=%5Emtools-&amp;stype=name">mtools</ulink> package in the ports collection.</para>
URL="http://www.freebsd.org/cgi/ports.cgi?query=%5Emtools-&amp;stype=name">mtools</ulink> package in the ports collection.</para>
</answer>
</qandaentry>
@ -7340,7 +7340,7 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
it? It is, indeed, impossible to start X at a raised
securelevel. To see why, look at the &man.init.8; man
page.</para>
<para>So the question is what else you should do instead,
and you basically have two choices: set your securelevel
back down to zero (usually from <filename>/etc/rc.conf</filename>),
@ -7449,7 +7449,7 @@ Device "/dev/sysmouse"
<example>
<title><quote>Pointer</quote> Section for Wheeled
Mouse in XFree86 3.3.x series XF86Config with moused
Mouse in XFree86 3.3.x series XF86Config with moused
Translation</title>
<programlisting>Section "Pointer"
@ -7482,7 +7482,7 @@ EndSection</programlisting>
(global-set-key [mouse-4] 'scroll-down)
(global-set-key [mouse-5] 'scroll-up)</programlisting>
</example>
</listitem>
<listitem>
@ -7705,7 +7705,7 @@ ttyvb "/usr/libexec/getty Pc" cons25 on secure</programlisting>
an X server on the same machine.</para>
</important>
</para>
<para>The easiest way to disable a console is by turning it off.
For example, if you had the full 12 terminal allocation
mentioned above and you wanted to run X, you would change
@ -7770,7 +7770,7 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure</programlisting>
<keycap>Alt</keycap>
<keycap>F<replaceable>n</replaceable></keycap>
</keycombo> as normal to move between them.</para>
<para>To return to the X session, you must switch to the virtual
console running X. If you invoked X from the command line, (e.g.,
using <command>startx</command>) then the X session will attach to
@ -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
@ -8296,7 +8296,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
<para>More detailed information about setting this up can be
found in the <ulink
URL="http://www.FreeBSD.org/tutorials/ppp/index.html">
Pedantic PPP Primer</ulink> by Steve Sims.</para>
Pedantic PPP Primer</ulink> by Steve Sims.</para>
<para>If you are using kernel-mode ppp, or have an Ethernet
connection to the Internet, you will have to use
@ -8513,7 +8513,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
/usr/src /usr/ports -maproot=0 client01
/usr/src /usr/ports client02
# The "client" machines have root and can mount anywhere
# up /exports. The world can mount /exports/obj read-only
# up /exports. The world can mount /exports/obj read-only
/exports -alldirs -maproot=0 client01 client02
/exports/obj -ro</programlisting>
</answer>
@ -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>
@ -9841,7 +9841,7 @@ ATDT1234567</programlisting>
<para>This is the most difficult solution, but it is the best
and will make the software work with multiple machines.</para>
</listitem>
<listitem>
<para>Use a proxy. The
application may support socks5 for example, or (as in the
@ -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>
@ -10785,7 +10785,7 @@ raisechar=^^</programlisting>
formats for UNIX:</para>
<para>
<note>
<note>
<para>Prior to FreeBSD 3.x, FreeBSD used the a.out
format.</para>
</note></para>
@ -11010,7 +11010,7 @@ raisechar=^^</programlisting>
<answer>
<para>You'd think it'd be easy enough to change
<para>You'd think it'd be easy enough to change
<literal>UT_NAMESIZE</literal> and rebuild the whole world,
and everything would just work. Unfortunately there are often
scads of applications and utilities (including system tools)
@ -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

274
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>
@ -47,7 +47,7 @@
FAQ</ulink>.</para>
</abstract>
</bookinfo>
<preface id="preface">
<title>Preface</title>
@ -266,7 +266,7 @@
and <ulink URL="ftp://releng4.FreeBSD.org/pub/FreeBSD">
releng4.FreeBSD.org</ulink> for 4-STABLE snapshots.
3-STABLE snapshots are not being produced at the time of
this writing (May 2000).</para>
this writing (May 2000).</para>
<para>Snapshots are generated, on the average, once a day for
all actively developed branches.</para>
@ -380,7 +380,7 @@
<qandaentry>
<question id="responsible">
<para> Who is responsible for FreeBSD?</para>
<para>Who is responsible for FreeBSD?</para>
</question>
<answer>
@ -727,14 +727,14 @@
<qandaentry>
<question id="doc-formats">
<para>Is the documentation available in other formats, such as plain
<para>Is the documentation available in other formats, such as plain
text (ASCII), or Postscript?</para>
</question>
<answer>
<para>Yes. The documentation is available in a number of different
formats and compression schemes on the FreeBSD FTP site, in the
<ulink
<ulink
URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/">/pub/FreeBSD/doc/</ulink> directory.</para>
<para>The documentation is categorised in a number of different
@ -750,7 +750,7 @@
<para>The document's language and encoding. These are based on
the locale names you will find under
<filename>/usr/share/locale</filename> on your FreeBSD
system. The current languages and encodings that we have for
system. The current languages and encodings that we have for
documentation are as follows:</para>
<informaltable frame="none">
@ -819,35 +819,35 @@
<para>The document's format. We produce the documentation in a
number of different output formats to try and make it as
flexible as possible. The current formats are;</para>
<informaltable frame="none">
<tgroup cols="2">
<thead>
<row>
<entry>Format</entry>
<entry>Meaning</entry>
</row>
</thead>
<tbody>
<row>
<entry><literal>html-split</literal></entry>
<entry>A collection of small, linked, HTML
files.</entry>
</row>
<row>
<entry><literal>html</literal></entry>
<entry>One large HTML file containing the entire
document</entry>
</row>
<row>
<entry><literal>pdb</literal></entry>
<entry>Palm Pilot database format, for use with the
<ulink URL="http://www.iSilo.com/">iSilo</ulink>
reader.</entry>
@ -855,19 +855,19 @@
<row>
<entry><literal>pdf</literal></entry>
<entry>Adobe's Portable Document Format</entry>
</row>
<row>
<entry><literal>ps</literal></entry>
<entry>Postscript</entry>
</row>
<row>
<entry><literal>rtf</literal></entry>
<entry>Microsoft's Rich Text Format<footnote>
<para>Page numbers are not automatically updated
when loading this format in to Word. Press
@ -878,10 +878,10 @@
</footnote>
</entry>
</row>
<row>
<entry><literal>txt</literal></entry>
<entry>Plain text</entry>
</row>
</tbody>
@ -895,7 +895,7 @@
<orderedlist>
<listitem>
<para>Where the format is <literal>html-split</literal>, the
<para>Where the format is <literal>html-split</literal>, the
files are bundled up using &man.tar.1;. The resulting
<filename>.tar</filename> file is then compressed using
the compression schemes detailed in the next point.</para>
@ -919,7 +919,7 @@
<entry>Description</entry>
</row>
</thead>
<tbody>
<row>
<entry><literal>zip</literal></entry>
@ -975,7 +975,7 @@
&man.pkg.delete.1;.</para>
<para>If you decide to download and install the package then you
must know the filename to download. The documentation-as-packages
must know the filename to download. The documentation-as-packages
files are stored in a directory called
<filename>packages</filename>. Each package file looks like
<filename><replaceable>document-name</replaceable>.<replaceable>lang</replaceable>.<replaceable>encoding</replaceable>.<replaceable>format</replaceable>.tgz</filename>.</para>
@ -984,11 +984,11 @@
package called
<filename>faq.en_US.ISO_8859-1.pdf.tgz</filename>.</para>
<para>Knowing this, you can use the following command to install the
<para>Knowing this, you can use the following command to install the
English PDF FAQ package.</para>
<screen>&prompt.root; <userinput>pkg_add ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/packages/faq.en_US.ISO_8859-1.pdf.tgz</userinput></screen>
<para>Having done that, you can use &man.pkg.info.1; to determine
where the file has been installed.</para>
@ -1014,7 +1014,7 @@ File: +DESC (ignored)</screen>
<para>For example, the split HTML version of the FAQ, compressed
using &man.gzip.1;, can be found in the
<filename>en_US.ISO_8859-1/books/faq/book.html-split.tar.gz</filename>
<filename>en_US.ISO_8859-1/books/faq/book.html-split.tar.gz</filename>
file. To download and uncompress that file you would have to do
this.</para>
@ -1040,7 +1040,7 @@ File: +DESC (ignored)</screen>
<para>Certainly! There are multiple ways to mirror the Web
pages.</para>
<itemizedlist>
<listitem>
@ -1053,7 +1053,7 @@ File: +DESC (ignored)</screen>
supfile, which can be found in
<filename>/usr/share/examples/cvsup/www-supfile</filename>.
</para>
</listitem>
<listitem>
@ -1095,7 +1095,7 @@ File: +DESC (ignored)</screen>
<para>The following newsgroups contain pertinent discussion for
FreeBSD users:</para>
<itemizedlist>
<listitem>
@ -1117,7 +1117,7 @@ File: +DESC (ignored)</screen>
<para>Web resources:</para>
<itemizedlist>
<listitem>
@ -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>
@ -1380,7 +1380,7 @@ File: +DESC (ignored)</screen>
<qandaentry>
<question id="win95-damaged-boot-manager">
<para>Windows 95/98 killed my boot manager!
<para>Windows 95/98 killed my boot manager!
How do I get it back?</para>
</question>
@ -1415,7 +1415,7 @@ File: +DESC (ignored)</screen>
</listitem>
<listitem>
<para>Boot the FreeBSD boot floppy (or CD-ROM) and choose the
<para>Boot the FreeBSD boot floppy (or CD-ROM) and choose the
<quote>Fixit</quote> menu item. Select either the Fixit
floppy or CD-ROM #2 (the <quote>live</quote> file system
option) as appropriate and enter the fixit shell. Then
@ -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>
@ -1460,7 +1460,7 @@ File: +DESC (ignored)</screen>
<entry>BIOS revision</entry>
</row>
</thead>
<tbody>
<row>
<entry>T20</entry>
@ -1507,7 +1507,7 @@ File: +DESC (ignored)</screen>
mailing list describes a procedure which may work if your newer
IBM laptop does not boot FreeBSD properly, and you can upgrade or
downgrade the BIOS..</para>
<para>If you have an earlier BIOS, and upgrading is not an option a
workaround is to install FreeBSD, change the partition ID FreeBSD
uses, and install new boot blocks that can handle the different
@ -1584,7 +1584,7 @@ File: +DESC (ignored)</screen>
the reader.</para>
</answer>
</qandaentry>
<qandaentry>
<question id="install-bad-blocks">
<para>Can I install on a disk with bad blocks?</para>
@ -1652,7 +1652,7 @@ File: +DESC (ignored)</screen>
<qandaentry>
<question id="no-install-cdrom">
<para>I booted from my ATAPI CD-ROM, but the install program says no
<para>I booted from my ATAPI CD-ROM, but the install program says no
CD-ROM is found. Where did it go?</para>
</question>
@ -1672,7 +1672,7 @@ File: +DESC (ignored)</screen>
master device.</para>
</answer>
</qandaentry>
<qandaentry>
<question id="cannot-install-tape">
<para>Help! I can't install from tape!</para>
@ -1720,7 +1720,7 @@ IP Address 10.0.0.1 10.0.0.2</programlisting>
<screen>&prompt.root; <userinput>ifconfig lp0 10.0.0.2 10.0.0.1</userinput></screen>
<para>Thats all! Please read also the manpages
<para>Thats all! Please read also the manpages
&man.lp.4; and &man.lpt.4; .</para>
<para>You should also add the hosts to
@ -1755,7 +1755,7 @@ PING moritz (10.0.0.2): 56 data bytes
--- moritz ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms</screen>
</answer>
</qandaentry>
@ -1786,7 +1786,7 @@ round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms</screen>
<entry>Post/Bit</entry>
</row>
</thead>
<tbody>
<row>
<entry><literallayout>DATA0
@ -1835,7 +1835,7 @@ round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms</screen>
<entry><literallayout>0/0x04
1/0x20</literallayout></entry>
</row>
<row>
<entry><literallayout>DATA3
-ACK</literallayout></entry>
@ -1867,7 +1867,7 @@ BUSY</literallayout></entry>
<entry><literallayout>0/0x10
1/0x80</literallayout></entry>
</row>
<row>
<entry>GND</entry>
@ -2061,7 +2061,7 @@ BUSY</literallayout></entry>
<para>To actually select a subset of the sources, use the Custom
menu item when you are in the Distributions menu of the
system installation tool.</para>
system installation tool.</para>
</answer>
</qandaentry>
@ -2089,7 +2089,7 @@ BUSY</literallayout></entry>
<qandaentry>
<question id="password-encryption">
<para>Should I use DES passwords, or MD5, and how do I specify
<para>Should I use DES passwords, or MD5, and how do I specify
which form my users receive?</para>
</question>
@ -2262,7 +2262,7 @@ disk wd2 at wdc1 drive 1 # change from wd3 to wd2</programlisting
<entry>should work</entry>
</row>
</thead>
<tbody>
<row>
<entry>4K</entry>
@ -2410,7 +2410,7 @@ Filesystem 1024-blocks Used Avail Capacity Mounted on
<answer>
<para>We <emphasis>strongly</emphasis> recommend that you use
binary snapshots to do this. 4-STABLE snapshots are available at
<ulink
<ulink
URL="ftp://releng4.FreeBSD.org/">releng4.FreeBSD.org</ulink>.</para>
<para>If you wish to upgrade using source, please see the <ulink
@ -2496,7 +2496,7 @@ Filesystem 1024-blocks Used Avail Capacity Mounted on
<row>
<entry>&man.sshd.8;</entry>
<entry>NO</entry>
<entry>YES</entry>
@ -2568,7 +2568,7 @@ Filesystem 1024-blocks Used Avail Capacity Mounted on
sets up the desired security to convenience ration out of
the box.</para>
</warning>
<note>
<para>The security profile mechanism is meant to be used
when you first install FreeBSD. If you already have
@ -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>
@ -2963,7 +2963,7 @@ moused_flags=""</programlisting>
<para>In 3.1 and later, assuming you have a PS/2 mouse, all you
need to is add <literal>moused_enable="YES"</literal> to
<filename>/etc/rc.conf</filename>.</para>
<filename>/etc/rc.conf</filename>.</para>
<para>In addition, if you would like to be able to use the mouse
daemon on all virtual terminals instead of just console at
@ -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>
@ -3888,7 +3888,7 @@ quit</programlisting>
ensure that you have hardware running at what it's
specified to run at, at least while trying to solve this
problem. i.e. Clock it back to the default settings.</para>
<para>If you are overclocking then note that it's far cheaper
to have a slow system than a fried system that needs
replacing! Also the wider community is not often
@ -3914,7 +3914,7 @@ quit</programlisting>
possible idea is to set to BIOS defaults, but it might be
worth noting down your settings first!</para>
</listitem>
<listitem>
<para>Unclean or insufficient power to the motherboard. If you
have any unused I/O boards, hard disks, or CDROMs in your
@ -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
@ -4505,7 +4505,7 @@ Timecounter "TSC" frequency 595573479 Hz</screen>
<screen>&prompt.root; <userinput>sysctl kern.timecounter.hardware</userinput>
kern.timecounter.hardware: TSC</screen>
<para>The BIOS may modify the TSC clock&mdash;perhaps to change the
speed of the processor when running from batteries, or going in to
a power saving mode, but FreeBSD is unaware of these adjustments,
@ -4557,9 +4557,9 @@ 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
Office Suite for FreeBSD containing a word processor,
spreadsheet, presentation program, vector drawing
@ -5177,7 +5177,7 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx</screen>
hand before you use it. Current versions of
<command>pkg_version</command> force this by inserting an
<command>exit</command> at the beginning of the script.</para>
<para>You should save the output of the script, as it will note
packages that depend on the one that has been udpated. These
may or may not need to be updated as well. The usual case where
@ -5281,7 +5281,7 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx</screen>
should notice a fairly large size decrease; most kernels
tend to be around 1.5MB to 2MB.</para>
</answer>
</qandaentry>
</qandaentry>
<qandaentry>
<question id="multiport-serial-interrupts">
@ -5315,7 +5315,7 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr</programlisting>
<para>Every kernel I try to build fails to compile; even
GENERIC.</para>
</question>
<answer>
<para>There are a number of possible causes for this problem.
They are, in no particular order:</para>
@ -5455,7 +5455,7 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr</programlisting>
<answer>
<para>Whether it's a removable drive like a ZIP or an EZ drive
<para>Whether it's a removable drive like a ZIP or an EZ drive
(or even a floppy, if you want to use it that way), or a new
hard disk, once it's installed and recognized by the system,
and you have your cartridge/floppy/whatever slotted in, things
@ -5541,9 +5541,9 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr</programlisting>
<para>If this is what you did, the extra crontab is simply a
copy of <filename>/etc/crontab</filename> in the wrong
format it. Delete it with the command:</para>
<screen>&prompt.root; <userinput>crontab -r</userinput></screen>
<para>Next time, when you edit
<filename>/etc/crontab</filename>, you should not do
anything to inform &man.cron.8; of the changes, since it
@ -6093,112 +6093,112 @@ 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>
</qandaentry>
<qandaentry>
<question id="pnp-resources">
<para>I get messages like: <errorname>unknown: &lt;PNP0303&gt;
@ -6330,7 +6330,7 @@ use "disklabel -r" to install initial label</screen>
following lines to your kernel config to enable them.</para>
<programlisting>options SYSVSHM
options SYSVSHM # enable shared memory
options SYSVSHM # enable shared memory
options SYSVSEM # enable for semaphores
options SYSVMSG # enable for messaging</programlisting>
@ -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>
@ -7068,7 +7068,7 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
<para>Enabling <varname>vfs.usermount</varname>, however, has
negative security implications. A better way to access MSDOS
formatted media is to use the <ulink
URL="http://www.freebsd.org/cgi/ports.cgi?query=%5Emtools-&amp;stype=name">mtools</ulink> package in the ports collection.</para>
URL="http://www.freebsd.org/cgi/ports.cgi?query=%5Emtools-&amp;stype=name">mtools</ulink> package in the ports collection.</para>
</answer>
</qandaentry>
@ -7340,7 +7340,7 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
it? It is, indeed, impossible to start X at a raised
securelevel. To see why, look at the &man.init.8; man
page.</para>
<para>So the question is what else you should do instead,
and you basically have two choices: set your securelevel
back down to zero (usually from <filename>/etc/rc.conf</filename>),
@ -7449,7 +7449,7 @@ Device "/dev/sysmouse"
<example>
<title><quote>Pointer</quote> Section for Wheeled
Mouse in XFree86 3.3.x series XF86Config with moused
Mouse in XFree86 3.3.x series XF86Config with moused
Translation</title>
<programlisting>Section "Pointer"
@ -7482,7 +7482,7 @@ EndSection</programlisting>
(global-set-key [mouse-4] 'scroll-down)
(global-set-key [mouse-5] 'scroll-up)</programlisting>
</example>
</listitem>
<listitem>
@ -7705,7 +7705,7 @@ ttyvb "/usr/libexec/getty Pc" cons25 on secure</programlisting>
an X server on the same machine.</para>
</important>
</para>
<para>The easiest way to disable a console is by turning it off.
For example, if you had the full 12 terminal allocation
mentioned above and you wanted to run X, you would change
@ -7770,7 +7770,7 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure</programlisting>
<keycap>Alt</keycap>
<keycap>F<replaceable>n</replaceable></keycap>
</keycombo> as normal to move between them.</para>
<para>To return to the X session, you must switch to the virtual
console running X. If you invoked X from the command line, (e.g.,
using <command>startx</command>) then the X session will attach to
@ -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
@ -8296,7 +8296,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
<para>More detailed information about setting this up can be
found in the <ulink
URL="http://www.FreeBSD.org/tutorials/ppp/index.html">
Pedantic PPP Primer</ulink> by Steve Sims.</para>
Pedantic PPP Primer</ulink> by Steve Sims.</para>
<para>If you are using kernel-mode ppp, or have an Ethernet
connection to the Internet, you will have to use
@ -8513,7 +8513,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
/usr/src /usr/ports -maproot=0 client01
/usr/src /usr/ports client02
# The "client" machines have root and can mount anywhere
# up /exports. The world can mount /exports/obj read-only
# up /exports. The world can mount /exports/obj read-only
/exports -alldirs -maproot=0 client01 client02
/exports/obj -ro</programlisting>
</answer>
@ -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>
@ -9841,7 +9841,7 @@ ATDT1234567</programlisting>
<para>This is the most difficult solution, but it is the best
and will make the software work with multiple machines.</para>
</listitem>
<listitem>
<para>Use a proxy. The
application may support socks5 for example, or (as in the
@ -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>
@ -10785,7 +10785,7 @@ raisechar=^^</programlisting>
formats for UNIX:</para>
<para>
<note>
<note>
<para>Prior to FreeBSD 3.x, FreeBSD used the a.out
format.</para>
</note></para>
@ -11010,7 +11010,7 @@ raisechar=^^</programlisting>
<answer>
<para>You'd think it'd be easy enough to change
<para>You'd think it'd be easy enough to change
<literal>UT_NAMESIZE</literal> and rebuild the whole world,
and everything would just work. Unfortunately there are often
scads of applications and utilities (including system tools)
@ -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