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

Fix formatting -- people this thing is <space> not <tab> indented.

Browse source
This commit is contained in:
David E. O'Brien 2001-03-08 11:01:25 +00:00
parent 0d86d09533
commit cf1b475fc2
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=8917
2 changed files with 606 additions and 604 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -11,7 +11,7 @@
<corpauthor>The FreeBSD Documentation Project</corpauthor>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.148 2001/03/07 20:00:49 hrs Exp $</pubdate>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.149 2001/03/08 10:55:14 obrien Exp $</pubdate>
<abstract>
<para>This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X.
@ -428,41 +428,41 @@
place(s):</para>
<address>BSDi
<street>4041 Pike Lane, Suite F</street>
<city>Concord</city>, <state>CA</state>
<postcode>94520</postcode>
<country>USA</country>
<street>4041 Pike Lane, Suite F</street>
<city>Concord</city>, <state>CA</state>
<postcode>94520</postcode>
<country>USA</country>
<phone>Orders: +1 800 786-9907</phone>
<phone>Questions: +1 925 674-0783</phone>
<fax>FAX: +1 925 674-0821</fax>
<otheraddr>email: <ulink URL="mailto:orders@osd.bsdi.com">BSDi Orders address</ulink></otheraddr>
<otheraddr>WWW: <ulink URL="http://www.osd.bsdi.com/">BSDi Home page</ulink></otheraddr></address>
<phone>Orders: +1 800 786-9907</phone>
<phone>Questions: +1 925 674-0783</phone>
<fax>FAX: +1 925 674-0821</fax>
<otheraddr>email: <ulink URL="mailto:orders@osd.bsdi.com">BSDi Orders address</ulink></otheraddr>
<otheraddr>WWW: <ulink URL="http://www.osd.bsdi.com/">BSDi Home page</ulink></otheraddr></address>
<para>In Australia, you may find it at:</para>
<address>Advanced Multimedia Distributors
<street>Factory 1/1 Ovata Drive</street>
<city>Tullamarine, Melbourne</city>
<state>Victoria</state>
<country>Australia</country>
<phone>Voice: +61 3 9338 6777</phone>
<street>Factory 1/1 Ovata Drive</street>
<city>Tullamarine, Melbourne</city>
<state>Victoria</state>
<country>Australia</country>
<phone>Voice: +61 3 9338 6777</phone>
<otheraddr>CDROM Support BBS</otheraddr>
<street>17 Irvine St</street>
<city>Peppermint Grove</city>, <state>WA</state>
<postcode>6011</postcode>
<phone>Voice: +61 9 385-3793</phone>
<fax>Fax: +61 9 385-2360</fax></address>
<otheraddr>CDROM Support BBS</otheraddr>
<street>17 Irvine St</street>
<city>Peppermint Grove</city>, <state>WA</state>
<postcode>6011</postcode>
<phone>Voice: +61 9 385-3793</phone>
<fax>Fax: +61 9 385-2360</fax></address>
<para>And in the UK:</para>
<address>The Public Domain &amp; Shareware Library
<street>Winscombe House, Beacon Rd</street>
<city>Crowborough</city>
<state>Sussex. TN6 1UL</state>
<phone>Voice: +44 1892 663-298</phone>
<fax>Fax: +44 1892 667-473</fax></address>
<street>Winscombe House, Beacon Rd</street>
<city>Crowborough</city>
<state>Sussex. TN6 1UL</state>
<phone>Voice: +44 1892 663-298</phone>
<fax>Fax: +44 1892 667-473</fax></address>
</answer>
</qandaentry>
@ -585,7 +585,8 @@
<para>The definitive printed guide on FreeBSD is
<quote>The Complete FreeBSD</quote>, written by Greg Lehey and
published by BSDi (formerly Walnut Creek CDROM) Books. Now in its second
published by BSDi (formerly Walnut Creek CDROM) Books.
Now in its second
edition, the book contains 1,750 pages of install &amp; system
administration guidance, program setup help, and manual pages.
The book (and current FreeBSD release) can be ordered from
@ -813,7 +814,7 @@
<entry><literal>html-split</literal></entry>
<entry>A collection of small, linked, HTML
files.</entry>
files.</entry>
</row>
<row>
@ -1422,146 +1423,146 @@ File: +DESC (ignored)</screen>
</qandaentry>
<qandaentry>
<question id="boot-on-thinkpad">
<para>I have an IBM Thinkpad in the A, T, or X series that FreeBSD
installs on, but then the machine locks up on next boot. How can I
solve this?</para>
</question>
<question id="boot-on-thinkpad">
<para>I have an IBM Thinkpad in the A, T, or X series that FreeBSD
installs on, but then the machine locks up on next boot. How can I
solve this?</para>
</question>
<answer>
<para>A bug in early revisions of IBM's BIOS on these machines
mistakenly identifies the FreeBSD partition as a potential FAT
suspend-to-disk partition. When the BIOS tries to parse the
FreeBSD partition it hangs.</para>
<answer>
<para>A bug in early revisions of IBM's BIOS on these machines
mistakenly identifies the FreeBSD partition as a potential FAT
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
Frechette
<email>kfrechet@us.ibm.com</email>.</para></footnote>, the
following model/BIOS release numbers incorporate the fix.</para>
<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>
<informaltable frame="none">
<tgroup cols="2">
<thead>
<row>
<entry>Model</entry>
<entry>BIOS revision</entry>
</row>
</thead>
<tbody>
<row>
<entry>T20</entry>
<entry>IYET49WW or later</entry>
</row>
<informaltable frame="none">
<tgroup cols="2">
<thead>
<row>
<entry>Model</entry>
<entry>BIOS revision</entry>
</row>
</thead>
<tbody>
<row>
<entry>T20</entry>
<entry>IYET49WW or later</entry>
</row>
<row>
<entry>T21</entry>
<entry>KZET22WW or later</entry>
</row>
<row>
<entry>T21</entry>
<entry>KZET22WW or later</entry>
</row>
<row>
<entry>A20p</entry>
<entry>IVET62WW or later</entry>
</row>
<row>
<entry>A20p</entry>
<entry>IVET62WW or later</entry>
</row>
<row>
<entry>A20m</entry>
<entry>IWET54WW or later</entry>
</row>
<row>
<entry>A20m</entry>
<entry>IWET54WW or later</entry>
</row>
<row>
<entry>A21p</entry>
<entry>KYET27WW or later</entry>
</row>
<row>
<entry>A21p</entry>
<entry>KYET27WW or later</entry>
</row>
<row>
<entry>A21m</entry>
<entry>KXET24WW or later</entry>
</row>
<row>
<entry>A21m</entry>
<entry>KXET24WW or later</entry>
</row>
<row>
<entry>A21e</entry>
<entry>KUET30WW</entry>
</row>
</tbody>
</tgroup>
</informaltable>
<row>
<entry>A21e</entry>
<entry>KUET30WW</entry>
</row>
</tbody>
</tgroup>
</informaltable>
<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
partition ID.</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
partition ID.</para>
<para>First, you'll need to to restore the machine to a state where
it can get through its self-test screen. Doing this requires
powering up the machine without letting it find a FreeBSD
partition on its primary disk. One way is to remove the hard disk
and temporarily move it to an older ThinkPad (such as a ThinkPad
600) or a desktop PC with an appropriate conversion cable. Once
it's there, you can delete the FreeBSD partition and move the hard
disk back. The ThinkPad should now be in a bootable state
again.</para>
<para>First, you'll need to to restore the machine to a state where
it can get through its self-test screen. Doing this requires
powering up the machine without letting it find a FreeBSD
partition on its primary disk. One way is to remove the hard disk
and temporarily move it to an older ThinkPad (such as a ThinkPad
600) or a desktop PC with an appropriate conversion cable. Once
it's there, you can delete the FreeBSD partition and move the hard
disk back. The ThinkPad should now be in a bootable state
again.</para>
<para>With the machine functional again, you can use the workaround
procedure described here to get a working FreeBSD
installation.</para>
<para>With the machine functional again, you can use the workaround
procedure described here to get a working FreeBSD
installation.</para>
<procedure>
<step>
<para>Download <filename>boot1</filename> and
<filename>boot2</filename> from <ulink
<procedure>
<step>
<para>Download <filename>boot1</filename> and
<filename>boot2</filename> from <ulink
url="http://people.freebsd.org/~bmah/ThinkPad/">http://people.freebsd.org/~bmah/ThinkPad/</ulink>.
Put these files somewhere you will be able to retrieve them
later.</para>
</step>
Put these files somewhere you will be able to retrieve them
later.</para>
</step>
<step>
<para>Install FreeBSD as normal on to the ThinkPad.
<emphasis>Do not</emphasis> use <literal>Dangerously
Dedicated</literal> mode. <emphasis>Do not</emphasis>
reboot when the install has finished.</para>
</step>
<step>
<para>Install FreeBSD as normal on to the ThinkPad.
<emphasis>Do not</emphasis> use <literal>Dangerously
Dedicated</literal> mode. <emphasis>Do not</emphasis>
reboot when the install has finished.</para>
</step>
<step>
<para>Either switch to the <quote>Emergency Holographic
Shell</quote> (<keycombo><keycap>ALT</keycap>
<keycap>F4</keycap></keycombo>) or start a
<quote>fixit</quote> shell.</para>
</step>
<step>
<para>Either switch to the <quote>Emergency Holographic
Shell</quote> (<keycombo><keycap>ALT</keycap>
<keycap>F4</keycap></keycombo>) or start a
<quote>fixit</quote> shell.</para>
</step>
<step>
<para>Use &man.fdisk.8; to change the FreeBSD partition ID from
<literal>165</literal> to <literal>166</literal> (this is the
type used by OpenBSD).</para>
</step>
<step>
<para>Use &man.fdisk.8; to change the FreeBSD partition ID from
<literal>165</literal> to <literal>166</literal> (this is the
type used by OpenBSD).</para>
</step>
<step>
<para>Bring the <filename>boot1</filename> and
<filename>boot2</filename> files to the local
filesystem.</para>
</step>
<step>
<para>Bring the <filename>boot1</filename> and
<filename>boot2</filename> files to the local
filesystem.</para>
</step>
<step>
<para>Use &man.disklabel.8; to write <filename>boot1</filename>
and <filename>boot2</filename> to your FreeBSD slice.</para>
<step>
<para>Use &man.disklabel.8; to write <filename>boot1</filename>
and <filename>boot2</filename> to your FreeBSD slice.</para>
<screen>&prompt.root; <userinput>disklabel -B -b boot1 -s boot2 ad0s<replaceable>n</replaceable></userinput></screen>
<screen>&prompt.root; <userinput>disklabel -B -b boot1 -s boot2 ad0s<replaceable>n</replaceable></userinput></screen>
<para><replaceable>n</replaceable> is the number of the slice
where you installed FreeBSD.</para>
</step>
<para><replaceable>n</replaceable> is the number of the slice
where you installed FreeBSD.</para>
</step>
<step>
<para>Reboot. At the boot prompt you will be given the option
of booting <literal>OpenBSD</literal>. This will actually
boot FreeBSD.</para>
</step>
</procedure>
<step>
<para>Reboot. At the boot prompt you will be given the option
of booting <literal>OpenBSD</literal>. This will actually
boot FreeBSD.</para>
</step>
</procedure>
<para>Getting this to work in the case where you want to dual boot
OpenBSD and FreeBSD on the same laptop is left as an exercise for
the reader.</para>
</answer>
<para>Getting this to work in the case where you want to dual boot
OpenBSD and FreeBSD on the same laptop is left as an exercise for
the reader.</para>
</answer>
</qandaentry>
<qandaentry>
@ -1879,13 +1880,13 @@ BUSY</literallayout></entry>
<answer>
<para>
<note>
<para>By the <quote>geometry</quote> of a disk, we mean the
number of cylinders, heads and sectors/track on a disk - I'll
refer to this as C/H/S for convenience. This is how the PC's
BIOS works out which area on a disk to read/write from.</para>
</note>
</para>
<note>
<para>By the <quote>geometry</quote> of a disk, we mean the
number of cylinders, heads and sectors/track on a disk - I'll
refer to this as C/H/S for convenience. This is how the PC's
BIOS works out which area on a disk to read/write from.</para>
</note>
</para>
<para>This seems to cause a lot of confusion for some reason.
First of all, the <emphasis>physical</emphasis> geometry of a
@ -2373,7 +2374,7 @@ Filesystem 1024-blocks Used Avail Capacity Mounted on
1+0 records out
1 bytes transferred in 0.000187 secs (5346 bytes/sec)
-rw-r--r-- 1 bde bin 8796093022207 Sep 7 16:04 z
32 z
32 z
Filesystem 1024-blocks Used Avail Capacity Mounted on
/dev/da0a 64479 27734 31587 47% /</screen>
@ -4226,7 +4227,7 @@ IO range check 0x00 activate 0x01</screen>
<qandaentry>
<question id="nlist-failed">
<para>I get the error <errorname>nlist failed</errorname> when
running, for example, <command>top</command> or
running, for example, <command>top</command> or
<command>systat</command>.</para>
</question>
@ -4238,13 +4239,13 @@ IO range check 0x00 activate 0x01</screen>
<itemizedlist>
<listitem>
<para>Your kernel and userland are not synchronized (i.e., you
built a new kernel but did not do an
<maketarget>installworld</maketarget>, or vice versa), and
thus the symbol table is different from what the user
application thinks it is. If this is the case, simply
complete the upgrade process (see
<filename>/usr/src/UPDATING</filename> for the correct
sequence).</para>
built a new kernel but did not do an
<maketarget>installworld</maketarget>, or vice versa), and
thus the symbol table is different from what the user
application thinks it is. If this is the case, simply
complete the upgrade process (see
<filename>/usr/src/UPDATING</filename> for the correct
sequence).</para>
</listitem>
<listitem>
@ -5013,7 +5014,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>
@ -5249,19 +5250,19 @@ 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
will notice them automatically.</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
will notice them automatically.</para>
<para>If you want something to be run once per day, week, or
month, it's probably better to add shell scripts
<filename>/usr/local/etc/periodic</filename>, and let the
&man.periodic.8; command run from the system cron schedule
it with the other periodic system tasks.</para>
<para>If you want something to be run once per day, week, or
month, it's probably better to add shell scripts
<filename>/usr/local/etc/periodic</filename>, and let the
&man.periodic.8; command run from the system cron schedule
it with the other periodic system tasks.</para>
<para>The actual reason for the error is that the system
crontab has an extra field, specifying which user to run the
@ -5278,7 +5279,7 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr</programlisting>
<qandaentry>
<question id="rcconf-readonly">
<para>I made a mistake in <filename>rc.conf</filename>,
or another startup file, and
or another startup file, and
now I can't edit it because the filesystem is read-only.
What should I do?</para>
</question>
@ -5884,16 +5885,16 @@ C:\="DOS"</programlisting>
<qandaentry>
<question id="pnp-resources">
<para>I get messages like: <errorname>unknown: &lt;PNP0303> can't
assign resources</errorname> on boot</para>
assign resources</errorname> on boot</para>
</question>
<answer>
<para>These indicate Plug-and-Play devices that the current
kernel doesn't have drivers for. They're harmless.</para>
kernel doesn't have drivers for. They're harmless.</para>
<para>If you dislike these messages, the FreeBSD Project
will happily accept driver contributions via send-pr.</para>
</answer>
<para>If you dislike these messages, the FreeBSD Project
will happily accept driver contributions via send-pr.</para>
</answer>
</qandaentry>
<qandaentry>
@ -5913,34 +5914,34 @@ C:\="DOS"</programlisting>
<para>Put the quota file on the file system that the quotas
are to be enforced on. ie:</para>
<informaltable frame="none">
<tgroup cols="2">
<thead>
<row>
<entry>Filesystem</entry>
<entry>Quota file</entry>
</row>
</thead>
<informaltable frame="none">
<tgroup cols="2">
<thead>
<row>
<entry>Filesystem</entry>
<entry>Quota file</entry>
</row>
</thead>
<tbody>
<row>
<entry><filename>/usr</filename></entry>
<entry><filename>/usr/admin/quotas</filename></entry>
</row>
<tbody>
<row>
<entry><filename>/usr</filename></entry>
<entry><filename>/usr/admin/quotas</filename></entry>
</row>
<row>
<entry><filename>/home</filename></entry>
<entry><filename>/home/admin/quotas</filename></entry>
</row>
<row>
<entry><filename>/home</filename></entry>
<entry><filename>/home/admin/quotas</filename></entry>
</row>
<row>
<entry>&hellip;</entry>
<entry>&hellip;</entry>
</row>
</tbody>
</tgroup>
</informaltable>
</listitem>
<row>
<entry>&hellip;</entry>
<entry>&hellip;</entry>
</row>
</tbody>
</tgroup>
</informaltable>
</listitem>
</orderedlist></para>
</answer>
@ -6384,8 +6385,8 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
&prompt.root; <userinput>./install.sh</userinput></screen>
<para>Alternately, you can remove all "MAKE_KERBEROS"
options from <filename>/etc/make.conf</filename> and rebuild
world.</para>
options from <filename>/etc/make.conf</filename> and rebuild
world.</para>
</answer>
</qandaentry>
@ -6604,12 +6605,12 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
&prompt.root; <userinput>chmod 640 /dev/cd0c</userinput></screen>
</step>
<step>
<para>Finally, add the line
<literal>vfs.usermount=1</literal> to the file
<filename>/etc/sysctl.conf</filename> so that it is reset
at system boot time.</para>
</step>
<step>
<para>Finally, add the line
<literal>vfs.usermount=1</literal> to the file
<filename>/etc/sysctl.conf</filename> so that it is reset
at system boot time.</para>
</step>
</procedure>
<para>All users can now mount the floppy
@ -6633,7 +6634,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>
@ -6776,52 +6777,52 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
<qandaentry>
<question id="kernel-chflag-failure">
<para>I tried to install a new kernel, and the chflags failed.
How do I get around this?</para>
How do I get around this?</para>
</question>
<answer>
<para>Short answer: You're probably at security level
greater than 0. Reboot directly to single user mode to
install the kernel.</para>
greater than 0. Reboot directly to single user mode to
install the kernel.</para>
<para>Long answer: FreeBSD disallows changing system flags
at security levels greater than 0. You can check your
security level with the command:</para>
at security levels greater than 0. You can check your
security level with the command:</para>
<screen>&prompt.root; <userinput>sysctl kern.securelevel</userinput></screen>
<screen>&prompt.root; <userinput>sysctl kern.securelevel</userinput></screen>
<para>You cannot lower the security level; you have to boot
to single mode to install the kernel, or change the
security in <filename>/etc/rc.conf</filename> then reboot. See
the &man.init.8; man page for details on securelevel, and
see <filename>/etc/defaults/rc.conf</filename> and the
&man.rc.conf.5; man page for more information on rc.conf.</para>
<para>You cannot lower the security level; you have to boot
to single mode to install the kernel, or change the
security in <filename>/etc/rc.conf</filename> then reboot. See
the &man.init.8; man page for details on securelevel, and
see <filename>/etc/defaults/rc.conf</filename> and the
&man.rc.conf.5; man page for more information on rc.conf.</para>
</answer>
</qandaentry>
<qandaentry>
<question id="kernel-securelevel-time">
<para>I can't change the time on my system by more than one second!
How do I get around this?</para>
How do I get around this?</para>
</question>
<answer>
<para>Short answer: You're probably at security level
greater than 1. Reboot directly to single user mode to
change the date.</para>
greater than 1. Reboot directly to single user mode to
change the date.</para>
<para>Long answer: FreeBSD disallows changing the time by
more that one second at security levels greater than 1. You
can check your security level with the command:</para>
<screen>&prompt.root; <userinput>sysctl kern.securelevel</userinput></screen>
<screen>&prompt.root; <userinput>sysctl kern.securelevel</userinput></screen>
<para>You cannot lower the security level; you have to boot
to single mode to change the date, or change the security
level in <filename>/etc/rc.conf</filename> then reboot. See
the &man.init.8; man page for details on securelevel, and
see <filename>/etc/defaults/rc.conf</filename> and the
&man.rc.conf.5; man page for more information on rc.conf.</para>
<para>You cannot lower the security level; you have to boot
to single mode to change the date, or change the security
level in <filename>/etc/rc.conf</filename> then reboot. See
the &man.init.8; man page for details on securelevel, and
see <filename>/etc/defaults/rc.conf</filename> and the
&man.rc.conf.5; man page for more information on rc.conf.</para>
</answer>
</qandaentry>
@ -6880,24 +6881,24 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
<qandaentry>
<question id="running-X-securelevels">
<para>I <emphasis>tried</emphasis> to run X, but I get an
<errorname>KDENABIO failed (Operation not permitted)</errorname>
error when I type <command>startx</command>. What do I do
now?</para>
<errorname>KDENABIO failed (Operation not permitted)</errorname>
error when I type <command>startx</command>. What do I do
now?</para>
</question>
<answer>
<para>Your system is running at a raised securelevel, isn't
it? It is, indeed, impossible to start X at a raised
securelevel. To see why, look at the &man.init.8; man
page.</para>
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>),
or run &man.xdm.1; at boot time (before the securelevel is
raised).</para>
<para>See <xref linkend="xdm-boot"> for more information about
<para>See <xref linkend="xdm-boot"> for more information about
running &man.xdm.1; at boot time.</para>
</answer>
</qandaentry>
@ -7226,7 +7227,7 @@ ttyvb "/usr/libexec/getty Pc" cons25 on secure</programlisting>
want to change the <literal>secure</literal>
to <literal>insecure</literal>.</para>
<para>
<para>
<important>
<para>If you want to run an X server you
<emphasis>must</emphasis> leave at least one virtual
@ -7236,8 +7237,8 @@ ttyvb "/usr/libexec/getty Pc" cons25 on secure</programlisting>
can only do this for eleven of them if you also want to run
an X server on the same machine.</para>
</important>
</para>
</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
@ -7287,34 +7288,34 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure</programlisting>
<para>How do I access the virtual consoles from X?</para>
</question>
<answer>
<para>Use <keycombo action="simul">
<keycap>Ctrl</keycap>
<keycap>Alt</keycap>
<keycap>F<replaceable>n</replaceable></keycap>
</keycombo> to switch back to a virtual console.
<keycombo action="simul">
<keycap>Ctrl</keycap>
<keycap>Alt</keycap>
<keycap>F1</keycap>
</keycombo> would return you to the first virtual console.</para>
<answer>
<para>Use <keycombo action="simul">
<keycap>Ctrl</keycap>
<keycap>Alt</keycap>
<keycap>F<replaceable>n</replaceable></keycap>
</keycombo> to switch back to a virtual console.
<keycombo action="simul">
<keycap>Ctrl</keycap>
<keycap>Alt</keycap>
<keycap>F1</keycap>
</keycombo> would return you to the first virtual console.</para>
<para>Once you are back to a text console, you can then use
<keycombo action="simul">
<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
the next unused virtual console, not the text console from which
it was invoked. If you have eight active virtual terminals then X
will be running on the ninth, and you would use
<keycombo action="simul">
<keycap>Alt</keycap>
<keycap>F9</keycap>
</keycombo> to return.</para>
<para>Once you are back to a text console, you can then use
<keycombo action="simul">
<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
the next unused virtual console, not the text console from which
it was invoked. If you have eight active virtual terminals then X
will be running on the ninth, and you would use
<keycombo action="simul">
<keycap>Alt</keycap>
<keycap>F9</keycap>
</keycombo> to return.</para>
</answer>
</qandaentry>
@ -7536,8 +7537,8 @@ UserConfig&gt; <userinput>quit</userinput></screen>
+ set_mouse_resolution(sc-&gt;kbdc, PSMD_RES_HIGH);
+
#if 0
set_mouse_scaling(sc-&gt;kbdc); /* 1:1 scaling */
set_mouse_mode(sc-&gt;kbdc); /* stream mode */</programlisting>
set_mouse_scaling(sc-&gt;kbdc); /* 1:1 scaling */
set_mouse_mode(sc-&gt;kbdc); /* stream mode */</programlisting>
<para>In versions 2.2.6 or later, specify the flags 0x04 to
the PS/2 mouse driver to put the mouse into the high
@ -8061,15 +8062,15 @@ Key F15 A A Menu Workplace Nop</programlisting>
passage from the &man.exports.5 manual page
correctly:</para>
<blockquote>
<para>Each line in the file (other than comment
lines that begin with a #) specifies the mount point(s)
and export flags within one local server filesystem for
one or more hosts. A host may be specified only once
for each local filesystem on the server and there may be
only one default entry for each server filesystem that
applies to all other hosts.</para>
</blockquote>
<blockquote>
<para>Each line in the file (other than comment
lines that begin with a #) specifies the mount point(s)
and export flags within one local server filesystem for
one or more hosts. A host may be specified only once
for each local filesystem on the server and there may be
only one default entry for each server filesystem that
applies to all other hosts.</para>
</blockquote>
<para>This is made more clear by an example of a common
mistake. If everything above <filename>/usr</filename> is
@ -8402,7 +8403,7 @@ Znyx (2.2.x) ZX312, ZX314, ZX342, ZX345, ZX346, ZX348
utilize it. Add this to your kernel config file and build
a new kernel:</para>
<programlisting>pseudo-device bpfilter # Berkeley Packet Filter</programlisting>
<programlisting>pseudo-device bpfilter # Berkeley Packet Filter</programlisting>
<para>Secondly, after rebooting you will have to create the
device node. This can be accomplished by a change to the
@ -8523,7 +8524,7 @@ Znyx (2.2.x) ZX312, ZX314, ZX342, ZX345, ZX346, ZX348
/etc/syslog.conf</ulink> contains the lines</para>
<programlisting>!ppp
*.* /var/log/ppp.log</programlisting>
*.* /var/log/ppp.log</programlisting>
<para>and that the file <filename>/var/log/ppp.log</filename>
exists. You can now find out a lot about what's going on
@ -9570,8 +9571,8 @@ ATDT1234567</programlisting>
fragment</quote> bit set (default of TCP) and the Telco router
is not sending ICMP <quote>must fragment</quote> back to the
www site you are trying to load. (Alternatively, the router is
sending the ICMP packet correctly, but the firewall at the www
site is dropping it.) When the www server is sending
sending the ICMP packet correctly, but the firewall at the www
site is dropping it.) When the www server is sending
you frames that don't fit into the PPPoE pipe the Telco router
drops them on the floor and your page doesn't load (some
pages/graphics do as they are smaller than a MSS.) This seems
@ -9590,13 +9591,13 @@ ATDT1234567</programlisting>
packets into a PPPoE frame perfectly but the
<quote>1450</quote> gives you a margin of error for other IP
protocols you may encounter). This registry key is reported to
have moved to
<literal>Tcpip\Parameters\Interfaces\<replaceable>ID for adapter</replaceable>\MTU</literal>
in Windows 2000.</para>
have moved to
<literal>Tcpip\Parameters\Interfaces\<replaceable>ID for adapter</replaceable>\MTU</literal>
in Windows 2000.</para>
<para>Refer to <ulink
URL="http://search.support.microsoft.com/kb">Microsoft Knowledge
Base</ulink> documents <quote>Q158474 - Windows TCPIP Registry
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
changing Windoze MTU to work with a FreeBSD/NAT/PPPoE
@ -10098,9 +10099,9 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr</programlist
/etc/remote</ulink> file. For example:</para>
<programlisting>tip115200|Dial any phone number at 115200 bps:\
:dv=/dev/cuaa0:br#115200:at=hayes:pa=none:du:
:dv=/dev/cuaa0:br#115200:at=hayes:pa=none:du:
tip57600|Dial any phone number at 57600 bps:\
:dv=/dev/cuaa0:br#57600:at=hayes:pa=none:du:</programlisting>
:dv=/dev/cuaa0:br#57600:at=hayes:pa=none:du:</programlisting>
<para>Then you can do something like <command>tip -115200
5551234</command>. If you prefer <ulink
@ -10148,11 +10149,11 @@ tip57600|Dial any phone number at 57600 bps:\
/etc/remote</ulink>:</para>
<programlisting>pain|pain.deep13.com|Forrester's machine:\
:cm=CONNECT pain\n:tc=deep13:
:cm=CONNECT pain\n:tc=deep13:
muffin|muffin.deep13.com|Frank's machine:\
:cm=CONNECT muffin\n:tc=deep13:
:cm=CONNECT muffin\n:tc=deep13:
deep13:Gizmonics Institute terminal server:\
:dv=/dev/cuaa2:br#38400:at=hayes:du:pa=none:pn=5551234:</programlisting>
:dv=/dev/cuaa2:br#38400:at=hayes:du:pa=none:pn=5551234:</programlisting>
<para>will let you type <command>tip pain</command> or
<command>tip muffin</command> to connect to the hosts
@ -10179,9 +10180,9 @@ deep13:Gizmonics Institute terminal server:\
the <literal>pn</literal> capability:</para>
<programlisting>big-university:\
:pn=\@:tc=dialout
:pn=\@:tc=dialout
dialout:\
:dv=/dev/cuaa3:br#9600:at=courier:du:pa=none:</programlisting>
:dv=/dev/cuaa3:br#9600:at=courier:du:pa=none:</programlisting>
<para>Then, list the phone numbers for the university in
<ulink URL="http://www.FreeBSD.org/cgi/man.cgi?phones">
@ -11388,8 +11389,8 @@ ${RELEASEDIR}/tarballs/bindist/bin_tgz.)</programlisting>
mailing list</link> if you are interested in joining that
project. Most recent additions to the list of upcoming plaforms
are IA-64 and PowerPC, join the
<email>freebsd-ia64@FreeBSD.org</email> or/and
<email>freebsd-ppc@FreeBSD.org</email> <link
<email>freebsd-ia64@FreeBSD.org</email> or/and
<email>freebsd-ppc@FreeBSD.org</email> <link
linkend="mailing">mailing lists</link> for more information.
For general discussion on new architectures, join
the <email>freebsd-platforms@FreeBSD.org</email>

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

@ -11,7 +11,7 @@
<corpauthor>The FreeBSD Documentation Project</corpauthor>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.148 2001/03/07 20:00:49 hrs Exp $</pubdate>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.149 2001/03/08 10:55:14 obrien Exp $</pubdate>
<abstract>
<para>This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X.
@ -428,41 +428,41 @@
place(s):</para>
<address>BSDi
<street>4041 Pike Lane, Suite F</street>
<city>Concord</city>, <state>CA</state>
<postcode>94520</postcode>
<country>USA</country>
<street>4041 Pike Lane, Suite F</street>
<city>Concord</city>, <state>CA</state>
<postcode>94520</postcode>
<country>USA</country>
<phone>Orders: +1 800 786-9907</phone>
<phone>Questions: +1 925 674-0783</phone>
<fax>FAX: +1 925 674-0821</fax>
<otheraddr>email: <ulink URL="mailto:orders@osd.bsdi.com">BSDi Orders address</ulink></otheraddr>
<otheraddr>WWW: <ulink URL="http://www.osd.bsdi.com/">BSDi Home page</ulink></otheraddr></address>
<phone>Orders: +1 800 786-9907</phone>
<phone>Questions: +1 925 674-0783</phone>
<fax>FAX: +1 925 674-0821</fax>
<otheraddr>email: <ulink URL="mailto:orders@osd.bsdi.com">BSDi Orders address</ulink></otheraddr>
<otheraddr>WWW: <ulink URL="http://www.osd.bsdi.com/">BSDi Home page</ulink></otheraddr></address>
<para>In Australia, you may find it at:</para>
<address>Advanced Multimedia Distributors
<street>Factory 1/1 Ovata Drive</street>
<city>Tullamarine, Melbourne</city>
<state>Victoria</state>
<country>Australia</country>
<phone>Voice: +61 3 9338 6777</phone>
<street>Factory 1/1 Ovata Drive</street>
<city>Tullamarine, Melbourne</city>
<state>Victoria</state>
<country>Australia</country>
<phone>Voice: +61 3 9338 6777</phone>
<otheraddr>CDROM Support BBS</otheraddr>
<street>17 Irvine St</street>
<city>Peppermint Grove</city>, <state>WA</state>
<postcode>6011</postcode>
<phone>Voice: +61 9 385-3793</phone>
<fax>Fax: +61 9 385-2360</fax></address>
<otheraddr>CDROM Support BBS</otheraddr>
<street>17 Irvine St</street>
<city>Peppermint Grove</city>, <state>WA</state>
<postcode>6011</postcode>
<phone>Voice: +61 9 385-3793</phone>
<fax>Fax: +61 9 385-2360</fax></address>
<para>And in the UK:</para>
<address>The Public Domain &amp; Shareware Library
<street>Winscombe House, Beacon Rd</street>
<city>Crowborough</city>
<state>Sussex. TN6 1UL</state>
<phone>Voice: +44 1892 663-298</phone>
<fax>Fax: +44 1892 667-473</fax></address>
<street>Winscombe House, Beacon Rd</street>
<city>Crowborough</city>
<state>Sussex. TN6 1UL</state>
<phone>Voice: +44 1892 663-298</phone>
<fax>Fax: +44 1892 667-473</fax></address>
</answer>
</qandaentry>
@ -585,7 +585,8 @@
<para>The definitive printed guide on FreeBSD is
<quote>The Complete FreeBSD</quote>, written by Greg Lehey and
published by BSDi (formerly Walnut Creek CDROM) Books. Now in its second
published by BSDi (formerly Walnut Creek CDROM) Books.
Now in its second
edition, the book contains 1,750 pages of install &amp; system
administration guidance, program setup help, and manual pages.
The book (and current FreeBSD release) can be ordered from
@ -813,7 +814,7 @@
<entry><literal>html-split</literal></entry>
<entry>A collection of small, linked, HTML
files.</entry>
files.</entry>
</row>
<row>
@ -1422,146 +1423,146 @@ File: +DESC (ignored)</screen>
</qandaentry>
<qandaentry>
<question id="boot-on-thinkpad">
<para>I have an IBM Thinkpad in the A, T, or X series that FreeBSD
installs on, but then the machine locks up on next boot. How can I
solve this?</para>
</question>
<question id="boot-on-thinkpad">
<para>I have an IBM Thinkpad in the A, T, or X series that FreeBSD
installs on, but then the machine locks up on next boot. How can I
solve this?</para>
</question>
<answer>
<para>A bug in early revisions of IBM's BIOS on these machines
mistakenly identifies the FreeBSD partition as a potential FAT
suspend-to-disk partition. When the BIOS tries to parse the
FreeBSD partition it hangs.</para>
<answer>
<para>A bug in early revisions of IBM's BIOS on these machines
mistakenly identifies the FreeBSD partition as a potential FAT
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
Frechette
<email>kfrechet@us.ibm.com</email>.</para></footnote>, the
following model/BIOS release numbers incorporate the fix.</para>
<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>
<informaltable frame="none">
<tgroup cols="2">
<thead>
<row>
<entry>Model</entry>
<entry>BIOS revision</entry>
</row>
</thead>
<tbody>
<row>
<entry>T20</entry>
<entry>IYET49WW or later</entry>
</row>
<informaltable frame="none">
<tgroup cols="2">
<thead>
<row>
<entry>Model</entry>
<entry>BIOS revision</entry>
</row>
</thead>
<tbody>
<row>
<entry>T20</entry>
<entry>IYET49WW or later</entry>
</row>
<row>
<entry>T21</entry>
<entry>KZET22WW or later</entry>
</row>
<row>
<entry>T21</entry>
<entry>KZET22WW or later</entry>
</row>
<row>
<entry>A20p</entry>
<entry>IVET62WW or later</entry>
</row>
<row>
<entry>A20p</entry>
<entry>IVET62WW or later</entry>
</row>
<row>
<entry>A20m</entry>
<entry>IWET54WW or later</entry>
</row>
<row>
<entry>A20m</entry>
<entry>IWET54WW or later</entry>
</row>
<row>
<entry>A21p</entry>
<entry>KYET27WW or later</entry>
</row>
<row>
<entry>A21p</entry>
<entry>KYET27WW or later</entry>
</row>
<row>
<entry>A21m</entry>
<entry>KXET24WW or later</entry>
</row>
<row>
<entry>A21m</entry>
<entry>KXET24WW or later</entry>
</row>
<row>
<entry>A21e</entry>
<entry>KUET30WW</entry>
</row>
</tbody>
</tgroup>
</informaltable>
<row>
<entry>A21e</entry>
<entry>KUET30WW</entry>
</row>
</tbody>
</tgroup>
</informaltable>
<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
partition ID.</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
partition ID.</para>
<para>First, you'll need to to restore the machine to a state where
it can get through its self-test screen. Doing this requires
powering up the machine without letting it find a FreeBSD
partition on its primary disk. One way is to remove the hard disk
and temporarily move it to an older ThinkPad (such as a ThinkPad
600) or a desktop PC with an appropriate conversion cable. Once
it's there, you can delete the FreeBSD partition and move the hard
disk back. The ThinkPad should now be in a bootable state
again.</para>
<para>First, you'll need to to restore the machine to a state where
it can get through its self-test screen. Doing this requires
powering up the machine without letting it find a FreeBSD
partition on its primary disk. One way is to remove the hard disk
and temporarily move it to an older ThinkPad (such as a ThinkPad
600) or a desktop PC with an appropriate conversion cable. Once
it's there, you can delete the FreeBSD partition and move the hard
disk back. The ThinkPad should now be in a bootable state
again.</para>
<para>With the machine functional again, you can use the workaround
procedure described here to get a working FreeBSD
installation.</para>
<para>With the machine functional again, you can use the workaround
procedure described here to get a working FreeBSD
installation.</para>
<procedure>
<step>
<para>Download <filename>boot1</filename> and
<filename>boot2</filename> from <ulink
<procedure>
<step>
<para>Download <filename>boot1</filename> and
<filename>boot2</filename> from <ulink
url="http://people.freebsd.org/~bmah/ThinkPad/">http://people.freebsd.org/~bmah/ThinkPad/</ulink>.
Put these files somewhere you will be able to retrieve them
later.</para>
</step>
Put these files somewhere you will be able to retrieve them
later.</para>
</step>
<step>
<para>Install FreeBSD as normal on to the ThinkPad.
<emphasis>Do not</emphasis> use <literal>Dangerously
Dedicated</literal> mode. <emphasis>Do not</emphasis>
reboot when the install has finished.</para>
</step>
<step>
<para>Install FreeBSD as normal on to the ThinkPad.
<emphasis>Do not</emphasis> use <literal>Dangerously
Dedicated</literal> mode. <emphasis>Do not</emphasis>
reboot when the install has finished.</para>
</step>
<step>
<para>Either switch to the <quote>Emergency Holographic
Shell</quote> (<keycombo><keycap>ALT</keycap>
<keycap>F4</keycap></keycombo>) or start a
<quote>fixit</quote> shell.</para>
</step>
<step>
<para>Either switch to the <quote>Emergency Holographic
Shell</quote> (<keycombo><keycap>ALT</keycap>
<keycap>F4</keycap></keycombo>) or start a
<quote>fixit</quote> shell.</para>
</step>
<step>
<para>Use &man.fdisk.8; to change the FreeBSD partition ID from
<literal>165</literal> to <literal>166</literal> (this is the
type used by OpenBSD).</para>
</step>
<step>
<para>Use &man.fdisk.8; to change the FreeBSD partition ID from
<literal>165</literal> to <literal>166</literal> (this is the
type used by OpenBSD).</para>
</step>
<step>
<para>Bring the <filename>boot1</filename> and
<filename>boot2</filename> files to the local
filesystem.</para>
</step>
<step>
<para>Bring the <filename>boot1</filename> and
<filename>boot2</filename> files to the local
filesystem.</para>
</step>
<step>
<para>Use &man.disklabel.8; to write <filename>boot1</filename>
and <filename>boot2</filename> to your FreeBSD slice.</para>
<step>
<para>Use &man.disklabel.8; to write <filename>boot1</filename>
and <filename>boot2</filename> to your FreeBSD slice.</para>
<screen>&prompt.root; <userinput>disklabel -B -b boot1 -s boot2 ad0s<replaceable>n</replaceable></userinput></screen>
<screen>&prompt.root; <userinput>disklabel -B -b boot1 -s boot2 ad0s<replaceable>n</replaceable></userinput></screen>
<para><replaceable>n</replaceable> is the number of the slice
where you installed FreeBSD.</para>
</step>
<para><replaceable>n</replaceable> is the number of the slice
where you installed FreeBSD.</para>
</step>
<step>
<para>Reboot. At the boot prompt you will be given the option
of booting <literal>OpenBSD</literal>. This will actually
boot FreeBSD.</para>
</step>
</procedure>
<step>
<para>Reboot. At the boot prompt you will be given the option
of booting <literal>OpenBSD</literal>. This will actually
boot FreeBSD.</para>
</step>
</procedure>
<para>Getting this to work in the case where you want to dual boot
OpenBSD and FreeBSD on the same laptop is left as an exercise for
the reader.</para>
</answer>
<para>Getting this to work in the case where you want to dual boot
OpenBSD and FreeBSD on the same laptop is left as an exercise for
the reader.</para>
</answer>
</qandaentry>
<qandaentry>
@ -1879,13 +1880,13 @@ BUSY</literallayout></entry>
<answer>
<para>
<note>
<para>By the <quote>geometry</quote> of a disk, we mean the
number of cylinders, heads and sectors/track on a disk - I'll
refer to this as C/H/S for convenience. This is how the PC's
BIOS works out which area on a disk to read/write from.</para>
</note>
</para>
<note>
<para>By the <quote>geometry</quote> of a disk, we mean the
number of cylinders, heads and sectors/track on a disk - I'll
refer to this as C/H/S for convenience. This is how the PC's
BIOS works out which area on a disk to read/write from.</para>
</note>
</para>
<para>This seems to cause a lot of confusion for some reason.
First of all, the <emphasis>physical</emphasis> geometry of a
@ -2373,7 +2374,7 @@ Filesystem 1024-blocks Used Avail Capacity Mounted on
1+0 records out
1 bytes transferred in 0.000187 secs (5346 bytes/sec)
-rw-r--r-- 1 bde bin 8796093022207 Sep 7 16:04 z
32 z
32 z
Filesystem 1024-blocks Used Avail Capacity Mounted on
/dev/da0a 64479 27734 31587 47% /</screen>
@ -4226,7 +4227,7 @@ IO range check 0x00 activate 0x01</screen>
<qandaentry>
<question id="nlist-failed">
<para>I get the error <errorname>nlist failed</errorname> when
running, for example, <command>top</command> or
running, for example, <command>top</command> or
<command>systat</command>.</para>
</question>
@ -4238,13 +4239,13 @@ IO range check 0x00 activate 0x01</screen>
<itemizedlist>
<listitem>
<para>Your kernel and userland are not synchronized (i.e., you
built a new kernel but did not do an
<maketarget>installworld</maketarget>, or vice versa), and
thus the symbol table is different from what the user
application thinks it is. If this is the case, simply
complete the upgrade process (see
<filename>/usr/src/UPDATING</filename> for the correct
sequence).</para>
built a new kernel but did not do an
<maketarget>installworld</maketarget>, or vice versa), and
thus the symbol table is different from what the user
application thinks it is. If this is the case, simply
complete the upgrade process (see
<filename>/usr/src/UPDATING</filename> for the correct
sequence).</para>
</listitem>
<listitem>
@ -5013,7 +5014,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>
@ -5249,19 +5250,19 @@ 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
will notice them automatically.</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
will notice them automatically.</para>
<para>If you want something to be run once per day, week, or
month, it's probably better to add shell scripts
<filename>/usr/local/etc/periodic</filename>, and let the
&man.periodic.8; command run from the system cron schedule
it with the other periodic system tasks.</para>
<para>If you want something to be run once per day, week, or
month, it's probably better to add shell scripts
<filename>/usr/local/etc/periodic</filename>, and let the
&man.periodic.8; command run from the system cron schedule
it with the other periodic system tasks.</para>
<para>The actual reason for the error is that the system
crontab has an extra field, specifying which user to run the
@ -5278,7 +5279,7 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr</programlisting>
<qandaentry>
<question id="rcconf-readonly">
<para>I made a mistake in <filename>rc.conf</filename>,
or another startup file, and
or another startup file, and
now I can't edit it because the filesystem is read-only.
What should I do?</para>
</question>
@ -5884,16 +5885,16 @@ C:\="DOS"</programlisting>
<qandaentry>
<question id="pnp-resources">
<para>I get messages like: <errorname>unknown: &lt;PNP0303> can't
assign resources</errorname> on boot</para>
assign resources</errorname> on boot</para>
</question>
<answer>
<para>These indicate Plug-and-Play devices that the current
kernel doesn't have drivers for. They're harmless.</para>
kernel doesn't have drivers for. They're harmless.</para>
<para>If you dislike these messages, the FreeBSD Project
will happily accept driver contributions via send-pr.</para>
</answer>
<para>If you dislike these messages, the FreeBSD Project
will happily accept driver contributions via send-pr.</para>
</answer>
</qandaentry>
<qandaentry>
@ -5913,34 +5914,34 @@ C:\="DOS"</programlisting>
<para>Put the quota file on the file system that the quotas
are to be enforced on. ie:</para>
<informaltable frame="none">
<tgroup cols="2">
<thead>
<row>
<entry>Filesystem</entry>
<entry>Quota file</entry>
</row>
</thead>
<informaltable frame="none">
<tgroup cols="2">
<thead>
<row>
<entry>Filesystem</entry>
<entry>Quota file</entry>
</row>
</thead>
<tbody>
<row>
<entry><filename>/usr</filename></entry>
<entry><filename>/usr/admin/quotas</filename></entry>
</row>
<tbody>
<row>
<entry><filename>/usr</filename></entry>
<entry><filename>/usr/admin/quotas</filename></entry>
</row>
<row>
<entry><filename>/home</filename></entry>
<entry><filename>/home/admin/quotas</filename></entry>
</row>
<row>
<entry><filename>/home</filename></entry>
<entry><filename>/home/admin/quotas</filename></entry>
</row>
<row>
<entry>&hellip;</entry>
<entry>&hellip;</entry>
</row>
</tbody>
</tgroup>
</informaltable>
</listitem>
<row>
<entry>&hellip;</entry>
<entry>&hellip;</entry>
</row>
</tbody>
</tgroup>
</informaltable>
</listitem>
</orderedlist></para>
</answer>
@ -6384,8 +6385,8 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
&prompt.root; <userinput>./install.sh</userinput></screen>
<para>Alternately, you can remove all "MAKE_KERBEROS"
options from <filename>/etc/make.conf</filename> and rebuild
world.</para>
options from <filename>/etc/make.conf</filename> and rebuild
world.</para>
</answer>
</qandaentry>
@ -6604,12 +6605,12 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
&prompt.root; <userinput>chmod 640 /dev/cd0c</userinput></screen>
</step>
<step>
<para>Finally, add the line
<literal>vfs.usermount=1</literal> to the file
<filename>/etc/sysctl.conf</filename> so that it is reset
at system boot time.</para>
</step>
<step>
<para>Finally, add the line
<literal>vfs.usermount=1</literal> to the file
<filename>/etc/sysctl.conf</filename> so that it is reset
at system boot time.</para>
</step>
</procedure>
<para>All users can now mount the floppy
@ -6633,7 +6634,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>
@ -6776,52 +6777,52 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
<qandaentry>
<question id="kernel-chflag-failure">
<para>I tried to install a new kernel, and the chflags failed.
How do I get around this?</para>
How do I get around this?</para>
</question>
<answer>
<para>Short answer: You're probably at security level
greater than 0. Reboot directly to single user mode to
install the kernel.</para>
greater than 0. Reboot directly to single user mode to
install the kernel.</para>
<para>Long answer: FreeBSD disallows changing system flags
at security levels greater than 0. You can check your
security level with the command:</para>
at security levels greater than 0. You can check your
security level with the command:</para>
<screen>&prompt.root; <userinput>sysctl kern.securelevel</userinput></screen>
<screen>&prompt.root; <userinput>sysctl kern.securelevel</userinput></screen>
<para>You cannot lower the security level; you have to boot
to single mode to install the kernel, or change the
security in <filename>/etc/rc.conf</filename> then reboot. See
the &man.init.8; man page for details on securelevel, and
see <filename>/etc/defaults/rc.conf</filename> and the
&man.rc.conf.5; man page for more information on rc.conf.</para>
<para>You cannot lower the security level; you have to boot
to single mode to install the kernel, or change the
security in <filename>/etc/rc.conf</filename> then reboot. See
the &man.init.8; man page for details on securelevel, and
see <filename>/etc/defaults/rc.conf</filename> and the
&man.rc.conf.5; man page for more information on rc.conf.</para>
</answer>
</qandaentry>
<qandaentry>
<question id="kernel-securelevel-time">
<para>I can't change the time on my system by more than one second!
How do I get around this?</para>
How do I get around this?</para>
</question>
<answer>
<para>Short answer: You're probably at security level
greater than 1. Reboot directly to single user mode to
change the date.</para>
greater than 1. Reboot directly to single user mode to
change the date.</para>
<para>Long answer: FreeBSD disallows changing the time by
more that one second at security levels greater than 1. You
can check your security level with the command:</para>
<screen>&prompt.root; <userinput>sysctl kern.securelevel</userinput></screen>
<screen>&prompt.root; <userinput>sysctl kern.securelevel</userinput></screen>
<para>You cannot lower the security level; you have to boot
to single mode to change the date, or change the security
level in <filename>/etc/rc.conf</filename> then reboot. See
the &man.init.8; man page for details on securelevel, and
see <filename>/etc/defaults/rc.conf</filename> and the
&man.rc.conf.5; man page for more information on rc.conf.</para>
<para>You cannot lower the security level; you have to boot
to single mode to change the date, or change the security
level in <filename>/etc/rc.conf</filename> then reboot. See
the &man.init.8; man page for details on securelevel, and
see <filename>/etc/defaults/rc.conf</filename> and the
&man.rc.conf.5; man page for more information on rc.conf.</para>
</answer>
</qandaentry>
@ -6880,24 +6881,24 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
<qandaentry>
<question id="running-X-securelevels">
<para>I <emphasis>tried</emphasis> to run X, but I get an
<errorname>KDENABIO failed (Operation not permitted)</errorname>
error when I type <command>startx</command>. What do I do
now?</para>
<errorname>KDENABIO failed (Operation not permitted)</errorname>
error when I type <command>startx</command>. What do I do
now?</para>
</question>
<answer>
<para>Your system is running at a raised securelevel, isn't
it? It is, indeed, impossible to start X at a raised
securelevel. To see why, look at the &man.init.8; man
page.</para>
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>),
or run &man.xdm.1; at boot time (before the securelevel is
raised).</para>
<para>See <xref linkend="xdm-boot"> for more information about
<para>See <xref linkend="xdm-boot"> for more information about
running &man.xdm.1; at boot time.</para>
</answer>
</qandaentry>
@ -7226,7 +7227,7 @@ ttyvb "/usr/libexec/getty Pc" cons25 on secure</programlisting>
want to change the <literal>secure</literal>
to <literal>insecure</literal>.</para>
<para>
<para>
<important>
<para>If you want to run an X server you
<emphasis>must</emphasis> leave at least one virtual
@ -7236,8 +7237,8 @@ ttyvb "/usr/libexec/getty Pc" cons25 on secure</programlisting>
can only do this for eleven of them if you also want to run
an X server on the same machine.</para>
</important>
</para>
</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
@ -7287,34 +7288,34 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure</programlisting>
<para>How do I access the virtual consoles from X?</para>
</question>
<answer>
<para>Use <keycombo action="simul">
<keycap>Ctrl</keycap>
<keycap>Alt</keycap>
<keycap>F<replaceable>n</replaceable></keycap>
</keycombo> to switch back to a virtual console.
<keycombo action="simul">
<keycap>Ctrl</keycap>
<keycap>Alt</keycap>
<keycap>F1</keycap>
</keycombo> would return you to the first virtual console.</para>
<answer>
<para>Use <keycombo action="simul">
<keycap>Ctrl</keycap>
<keycap>Alt</keycap>
<keycap>F<replaceable>n</replaceable></keycap>
</keycombo> to switch back to a virtual console.
<keycombo action="simul">
<keycap>Ctrl</keycap>
<keycap>Alt</keycap>
<keycap>F1</keycap>
</keycombo> would return you to the first virtual console.</para>
<para>Once you are back to a text console, you can then use
<keycombo action="simul">
<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
the next unused virtual console, not the text console from which
it was invoked. If you have eight active virtual terminals then X
will be running on the ninth, and you would use
<keycombo action="simul">
<keycap>Alt</keycap>
<keycap>F9</keycap>
</keycombo> to return.</para>
<para>Once you are back to a text console, you can then use
<keycombo action="simul">
<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
the next unused virtual console, not the text console from which
it was invoked. If you have eight active virtual terminals then X
will be running on the ninth, and you would use
<keycombo action="simul">
<keycap>Alt</keycap>
<keycap>F9</keycap>
</keycombo> to return.</para>
</answer>
</qandaentry>
@ -7536,8 +7537,8 @@ UserConfig&gt; <userinput>quit</userinput></screen>
+ set_mouse_resolution(sc-&gt;kbdc, PSMD_RES_HIGH);
+
#if 0
set_mouse_scaling(sc-&gt;kbdc); /* 1:1 scaling */
set_mouse_mode(sc-&gt;kbdc); /* stream mode */</programlisting>
set_mouse_scaling(sc-&gt;kbdc); /* 1:1 scaling */
set_mouse_mode(sc-&gt;kbdc); /* stream mode */</programlisting>
<para>In versions 2.2.6 or later, specify the flags 0x04 to
the PS/2 mouse driver to put the mouse into the high
@ -8061,15 +8062,15 @@ Key F15 A A Menu Workplace Nop</programlisting>
passage from the &man.exports.5 manual page
correctly:</para>
<blockquote>
<para>Each line in the file (other than comment
lines that begin with a #) specifies the mount point(s)
and export flags within one local server filesystem for
one or more hosts. A host may be specified only once
for each local filesystem on the server and there may be
only one default entry for each server filesystem that
applies to all other hosts.</para>
</blockquote>
<blockquote>
<para>Each line in the file (other than comment
lines that begin with a #) specifies the mount point(s)
and export flags within one local server filesystem for
one or more hosts. A host may be specified only once
for each local filesystem on the server and there may be
only one default entry for each server filesystem that
applies to all other hosts.</para>
</blockquote>
<para>This is made more clear by an example of a common
mistake. If everything above <filename>/usr</filename> is
@ -8402,7 +8403,7 @@ Znyx (2.2.x) ZX312, ZX314, ZX342, ZX345, ZX346, ZX348
utilize it. Add this to your kernel config file and build
a new kernel:</para>
<programlisting>pseudo-device bpfilter # Berkeley Packet Filter</programlisting>
<programlisting>pseudo-device bpfilter # Berkeley Packet Filter</programlisting>
<para>Secondly, after rebooting you will have to create the
device node. This can be accomplished by a change to the
@ -8523,7 +8524,7 @@ Znyx (2.2.x) ZX312, ZX314, ZX342, ZX345, ZX346, ZX348
/etc/syslog.conf</ulink> contains the lines</para>
<programlisting>!ppp
*.* /var/log/ppp.log</programlisting>
*.* /var/log/ppp.log</programlisting>
<para>and that the file <filename>/var/log/ppp.log</filename>
exists. You can now find out a lot about what's going on
@ -9570,8 +9571,8 @@ ATDT1234567</programlisting>
fragment</quote> bit set (default of TCP) and the Telco router
is not sending ICMP <quote>must fragment</quote> back to the
www site you are trying to load. (Alternatively, the router is
sending the ICMP packet correctly, but the firewall at the www
site is dropping it.) When the www server is sending
sending the ICMP packet correctly, but the firewall at the www
site is dropping it.) When the www server is sending
you frames that don't fit into the PPPoE pipe the Telco router
drops them on the floor and your page doesn't load (some
pages/graphics do as they are smaller than a MSS.) This seems
@ -9590,13 +9591,13 @@ ATDT1234567</programlisting>
packets into a PPPoE frame perfectly but the
<quote>1450</quote> gives you a margin of error for other IP
protocols you may encounter). This registry key is reported to
have moved to
<literal>Tcpip\Parameters\Interfaces\<replaceable>ID for adapter</replaceable>\MTU</literal>
in Windows 2000.</para>
have moved to
<literal>Tcpip\Parameters\Interfaces\<replaceable>ID for adapter</replaceable>\MTU</literal>
in Windows 2000.</para>
<para>Refer to <ulink
URL="http://search.support.microsoft.com/kb">Microsoft Knowledge
Base</ulink> documents <quote>Q158474 - Windows TCPIP Registry
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
changing Windoze MTU to work with a FreeBSD/NAT/PPPoE
@ -10098,9 +10099,9 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr</programlist
/etc/remote</ulink> file. For example:</para>
<programlisting>tip115200|Dial any phone number at 115200 bps:\
:dv=/dev/cuaa0:br#115200:at=hayes:pa=none:du:
:dv=/dev/cuaa0:br#115200:at=hayes:pa=none:du:
tip57600|Dial any phone number at 57600 bps:\
:dv=/dev/cuaa0:br#57600:at=hayes:pa=none:du:</programlisting>
:dv=/dev/cuaa0:br#57600:at=hayes:pa=none:du:</programlisting>
<para>Then you can do something like <command>tip -115200
5551234</command>. If you prefer <ulink
@ -10148,11 +10149,11 @@ tip57600|Dial any phone number at 57600 bps:\
/etc/remote</ulink>:</para>
<programlisting>pain|pain.deep13.com|Forrester's machine:\
:cm=CONNECT pain\n:tc=deep13:
:cm=CONNECT pain\n:tc=deep13:
muffin|muffin.deep13.com|Frank's machine:\
:cm=CONNECT muffin\n:tc=deep13:
:cm=CONNECT muffin\n:tc=deep13:
deep13:Gizmonics Institute terminal server:\
:dv=/dev/cuaa2:br#38400:at=hayes:du:pa=none:pn=5551234:</programlisting>
:dv=/dev/cuaa2:br#38400:at=hayes:du:pa=none:pn=5551234:</programlisting>
<para>will let you type <command>tip pain</command> or
<command>tip muffin</command> to connect to the hosts
@ -10179,9 +10180,9 @@ deep13:Gizmonics Institute terminal server:\
the <literal>pn</literal> capability:</para>
<programlisting>big-university:\
:pn=\@:tc=dialout
:pn=\@:tc=dialout
dialout:\
:dv=/dev/cuaa3:br#9600:at=courier:du:pa=none:</programlisting>
:dv=/dev/cuaa3:br#9600:at=courier:du:pa=none:</programlisting>
<para>Then, list the phone numbers for the university in
<ulink URL="http://www.FreeBSD.org/cgi/man.cgi?phones">
@ -11388,8 +11389,8 @@ ${RELEASEDIR}/tarballs/bindist/bin_tgz.)</programlisting>
mailing list</link> if you are interested in joining that
project. Most recent additions to the list of upcoming plaforms
are IA-64 and PowerPC, join the
<email>freebsd-ia64@FreeBSD.org</email> or/and
<email>freebsd-ppc@FreeBSD.org</email> <link
<email>freebsd-ia64@FreeBSD.org</email> or/and
<email>freebsd-ppc@FreeBSD.org</email> <link
linkend="mailing">mailing lists</link> for more information.
For general discussion on new architectures, join
the <email>freebsd-platforms@FreeBSD.org</email>