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

Fix some grammos noticed in previous whitespace fixes.

Browse source 
Reword to remove i.e., simply, and please.
This whole document needs a thorough editorial review and a tech review
to remove outdated material.
Much of this material belongs in, or is already in, the Handbook.
Many more commits to come.

Sponsored by:	iXsystems
This commit is contained in:
Dru Lavigne 2014-05-14 02:50:11 +00:00
parent ad73e2ef39
commit 6c12105ee5
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=44824
1 changed files with 120 additions and 131 deletions

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

@ -72,7 +72,7 @@
<para>This is the FAQ for &os; versions &rel3.relx;, &rel2.relx;
and &rel.relx;. Every effort has been made to make this FAQ
as informative as possible; if you have any suggestions as to
how it may be improved, please feel free to mail them to the
how it may be improved, send them to the
&a.doc;.</para>
<para>The latest version of this document is always available
@ -114,7 +114,7 @@
users all over the world in their work, education and
recreation.</para>
<para>For more detailed information on &os;, please see the
<para>For more detailed information on &os;, refer to the
<link xlink:href="&url.books.handbook;/index.html">&os;
Handbook</link>.</para>
</answer>
@ -143,8 +143,8 @@
If you have serious license concerns, read the actual
<link
xlink:href="http://www.FreeBSD.org/copyright/freebsd-license.html">license</link>.
For the simply curious, the license can be summarized like
this.</para>
The license can be summarized like
this:</para>
<itemizedlist>
<listitem>
@ -605,7 +605,7 @@
problem report submission interface</link> can be used
to submit problem reports through a web browser.</para>
<para>Before submitting a problem report, please read <link
<para>Before submitting a problem report, read <link
xlink:href="&url.articles.problem-reports;/article.html">Writing
&os; Problem Reports</link>, an article on how to write
good problem reports.</para>
@ -899,10 +899,10 @@
</listitem>
<listitem>
<para>All the other formats generate one file,
called <filename>type.format</filename> (i.e.,
<para>All the other formats generate one file. For
example,
<filename>article.pdf</filename>,
<filename>book.html</filename>, and so on).</para>
<filename>book.html</filename>, and so on.</para>
<para>These files are then compressed using either
the <literal>zip</literal> or
@ -1019,7 +1019,7 @@
<listitem>
<para>Channel <literal>#FreeBSD</literal> on <link
xlink:href="http://www.rusnet.org.ru/">RUSNET</link>
is a russian-language oriented channel dedicated to
is a Russian language channel dedicated to
helping &os; users. This is also good place for
non-technical discussions.</para>
</listitem>
@ -1027,8 +1027,8 @@
<listitem>
<para>Channel <literal>#bsdchat</literal> on <link
xlink:href="http://freenode.net/">Freenode</link> is
a Traditional-Chinese (UTF-8 encoding) language
oriented channel dedicated to helping &os; users.
a Traditional Chinese (UTF-8 encoding) language
channel dedicated to helping &os; users.
This is also good place for non-technical
discussions.</para>
</listitem>
@ -1077,7 +1077,7 @@
<para>BSD Certification Group, Inc. provides system
administration certifications for DragonFly&nbsp;BSD,
&os;, NetBSD, OpenBSD. If you are interested in them,
&os;, NetBSD, and OpenBSD. If you are interested in them,
visit <link
xlink:href="http://www.BSDCertification.org">their
site</link>.</para>
@ -1827,8 +1827,8 @@
<para>It is not possible to remove data using the mouse.
However, it is possible to <quote>copy and
paste</quote>.
Once you get the mouse daemon running (see the <link
linkend="moused">previous question</link>) hold down
Once you get the mouse daemon running as described in the <link
linkend="moused">previous question</link>, hold down
button 1 (left button) and move the mouse to select a
region of text. Then, press button 2 (middle button) to
paste it at the text cursor. Pressing button 3 (right
@ -2154,7 +2154,7 @@ bindkey ^[[3~ delete-char # for xterm</programlisting>
section refers to open files, the same limits apply to
processes.)</para>
<para>If your machine is lightly loaded, and you are simply
<para>If the machine is lightly loaded and you are
running a very large number of processes, you can adjust
this with the <varname>kern.maxproc</varname> tunable. If
this tunable needs adjustment it needs to be defined in
@ -2327,7 +2327,7 @@ to /etc/mail/sendmail.cf.</programlisting>
<answer>
<para>This error message indicates you have exhausted the
number of available file descriptors on your system.
Please see the <link
Refer to the <link
xlink:href="&url.books.handbook;/configtuning-kernel-limits.html#kern-maxfiles">kern.maxfiles</link>
section of the <link
xlink:href="&url.books.handbook;/configtuning-kernel-limits.html">Tuning
@ -2504,9 +2504,9 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
<para>This error does not mean that the &man.touch.1;
utility is missing. The error is instead probably due to
the dates of the files being set sometime in the future.
If your CMOS-clock is set to local time you need to run
the command <command>adjkerntz&nbsp;-i</command> to adjust
the kernel clock when booting into single user
If your CMOS-clock is set to local time, run
<command>adjkerntz&nbsp;-i</command> to adjust
the kernel clock when booting into single-user
mode.</para>
</answer>
</qandaentry>
@ -2523,7 +2523,7 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
</question>
<answer>
<para>Please take a look at <link
<para>Refer to <link
xlink:href="&url.base;/ports/index.html">the ports
page</link> for info on software packages ported to
&os;. The list currently tops &os.numports; and is
@ -2589,8 +2589,9 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
</question>
<answer>
<para>Yes. Please see <link
xlink:href="&url.base;/java/index.html">http://www.FreeBSD.org/java/</link>.</para>
<para>Yes. Refer to <link
xlink:href="&url.base;/java/index.html">http://www.FreeBSD.org/java/</link>
for more information.</para>
</answer>
</qandaentry>
@ -2611,8 +2612,8 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
information on how to do this. If you are up to date,
then someone might have committed a change to the port
which works for <emphasis>-CURRENT</emphasis> but which
broke the port for <emphasis>-STABLE</emphasis>. Please
submit a bug report on this with the &man.send-pr.1;
broke the port for <emphasis>-STABLE</emphasis>.
Submit a bug report with the &man.send-pr.1;
command, since the Ports Collection is supposed to work
for both the <emphasis>-CURRENT</emphasis> and
<emphasis>-STABLE</emphasis> branches.</para>
@ -2637,7 +2638,7 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
<varname>WITH_<replaceable>*</replaceable></varname> or
<varname>WITHOUT_<replaceable>*</replaceable></varname>
variables being set in <filename>make.conf</filename>. If
you suspect that this is the case, please try to make
you suspect that this is the case, try to make
<filename>INDEX</filename> with those make variables
turned off before reporting it to &a.ports;.</para>
</answer>
@ -2764,7 +2765,7 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
</question>
<answer>
<para>The open-source <application>Apache
<para>The open source <application>Apache
OpenOffice</application> and
<application>LibreOffice</application> office suites work
natively on &os;.</para>
@ -2919,7 +2920,7 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
tree is different from the one used to build the
currently running system (e.g., you are compiling
&rel.current;-RELEASE on a &rel2.current;-RELEASE
system). If you are attempting an upgrade, please
system). If you are attempting an upgrade,
read <filename>/usr/src/UPDATING</filename>, paying
particular attention to the <quote>COMMON
ITEMS</quote> section at the end.</para>
@ -3029,7 +3030,7 @@ kern.sched.name: ULE</screen>
<filename>/dev</filename>), flags, and links tend to screw
that up. You need to use tools that understand these
things, which means &man.dump.8;. Although it is
suggested that you move the data in single user mode, it
suggested that you move the data in single-user mode, it
is not required.</para>
<para>You should never use anything but &man.dump.8; and
@ -3121,8 +3122,8 @@ kern.sched.name: ULE</screen>
<para>Long answer: Soft Updates has two characteristics
that may be undesirable on certain partitions. First, a
Soft Updates partition has a small chance of losing data
during a system crash. (The partition will not be
corrupted; the data will simply be lost.) Second, Soft
during a system crash. The partition will not be
corrupted as the data will simply be lost. Second, Soft
Updates can cause temporary space shortages.</para>
<para>When using Soft Updates, the kernel can take up to
@ -3236,11 +3237,9 @@ kern.sched.name: ULE</screen>
</varlistentry>
</variablelist>
<para>&os; also supports network file systems such as NFS
(see &man.mount.nfs.8;), NetWare (see &man.mount.nwfs.8;),
and Microsoft-style SMB file systems (see
&man.mount.smbfs.8;). You can find ports based on FUSE
(<package>sysutils/fusefs-kmod</package>) for many other
<para>&os; includes the Network File System <acronym>NFS</acronym> and
the &os; Ports Collection provides several FUSE applications
to support many other
file systems.</para>
</answer>
</qandaentry>
@ -3256,7 +3255,7 @@ kern.sched.name: ULE</screen>
example, if you have an <quote>E</quote> partition as the
second DOS partition on the second SCSI drive, there will
be a device file for <quote>slice 5</quote> in
<filename>/dev</filename>, so simply mount it:</para>
<filename>/dev</filename>, so mount it:</para>
<screen>&prompt.root; <userinput>mount -t msdosfs /dev/da1s5 /dos/e</userinput></screen>
</answer>
@ -3300,7 +3299,7 @@ C:\BOOTSECT.BSD="&os;"
C:\="DOS"</programlisting>
<para>If &os; is installed on the same disk as the
&windowsnt; boot partition simply copy
&windowsnt; boot partition, copy
<filename>/boot/boot1</filename> to
<filename>C:\BOOTSECT.BSD</filename>. However, if &os; is
installed on a different disk
@ -3317,11 +3316,11 @@ C:\="DOS"</programlisting>
MBR.</para>
<warning>
<para><emphasis>Do not simply copy
<para><emphasis>Do not copy
<filename>/boot/boot0</filename> instead of
<filename>/boot/boot1</filename>; you will overwrite
your partition table and render your computer
un-bootable!</emphasis></para>
<filename>/boot/boot1</filename> as this will overwrite
the partition table and render the computer
unbootable!</emphasis></para>
</warning>
<para>When the &os; boot manager runs it records the last OS
@ -3511,7 +3510,7 @@ C:\="DOS"</programlisting>
<answer>
<para>This generally means that there is no CD-ROM in the
CD-ROM drive, or the drive is not visible on the bus.
Please see the <link
Refer to the <link
xlink:href="&url.books.handbook;/creating-cds.html#mounting-cd">Using
Data CDs</link> section of the Handbook for a detailed
discussion of this issue.</para>
@ -3598,7 +3597,7 @@ C:\="DOS"</programlisting>
<para>By default, &man.mount.8; will attempt to mount the
last data track (session) of a CD. If you would like to
load an earlier session, you must use the
<option>-s</option> command line argument. Please see
<option>-s</option> command line argument. Refer to
&man.mount.cd9660.8; for specific examples.</para>
</answer>
</qandaentry>
@ -3686,7 +3685,7 @@ C:\="DOS"</programlisting>
file while using <command>more</command> on it,
<command>more</command> does not immediately choke and
complain that it cannot view the file. The entry is
simply removed from the directory so no other program or
removed from the directory so no other program or
user can access it. <command>du</command> shows that it
is gone &mdash; it has walked the directory tree and the
file is not listed. <command>df</command> shows that it
@ -3873,8 +3872,8 @@ C:\="DOS"</programlisting>
<para>Deduplication takes up a significant amount of RAM
and may slow down read and write disk access times.
Unless one is storing data that is very heavily
duplicated (such as virtual machine images, or user
backups) it is possible that deduplication will do more
duplicated, such as virtual machine images or user
backups, it is possible that deduplication will do more
harm than good. Another consideration is the inability
to revert deduplication status. If data is written when
deduplication is enabled, disabling dedup will not cause
@ -3882,7 +3881,7 @@ C:\="DOS"</programlisting>
until they are next modified.</para>
<para>Deduplication can also lead to some unexpected
situations. In particular deleting files may become
situations. In particular, deleting files may become
much slower.</para>
</answer>
</qandaentry>
@ -3995,7 +3994,7 @@ C:\="DOS"</programlisting>
<question xml:id="root-not-found-cron-errors">
<para>Why do I keep getting messages like <errorname>root:
not found</errorname> after editing
<filename>/etc/crontab</filename></para>
<filename>/etc/crontab</filename>?</para>
</question>
<answer>
@ -4010,7 +4009,7 @@ C:\="DOS"</programlisting>
which &man.crontab.1; updates (the &man.crontab.5; manual
page explains the differences in more detail).</para>
<para>If this is what you did, the extra crontab is simply a
<para>If this is what you did, the extra crontab is a
copy of <filename>/etc/crontab</filename> in the wrong
format it. Delete it with the command:</para>
@ -4065,10 +4064,10 @@ C:\="DOS"</programlisting>
class="groupname">wheel</systemitem>.</para>
<para>To allow someone to <command>su</command> to
<systemitem class="username">root</systemitem>, simply put
<systemitem class="username">root</systemitem>, put
them in the <systemitem
class="groupname">wheel</systemitem> group. Use
&man.pw.8; for this purpose.</para>
class="groupname">wheel</systemitem> group using
<command>pw</command>:</para>
<screen>&prompt.root; <userinput>pw groupmod wheel -m lisa</userinput></screen>
@ -4087,9 +4086,9 @@ C:\="DOS"</programlisting>
<answer>
<para>Restart the system using <userinput>boot
-s</userinput> at the loader prompt to enter Single User
mode. When prompted for a shell pathname, simply press
<keycap>Enter</keycap>, and run <command>mount
-s</userinput> at the loader prompt to enter single-user
mode. When prompted for a shell pathname, press
<keycap>Enter</keycap> and run <command>mount
-urw /</command> to re-mount the root file system in
read/write mode. You may also need to run <command>mount
-a -t ufs</command> to mount the file system where your
@ -4143,7 +4142,7 @@ C:\="DOS"</programlisting>
</question>
<answer>
<para>Please see the Handbook section on <link
<para>Refer to the Handbook section on <link
xlink:href="&url.books.handbook;/using-localization.html">using
localization</link>, specifically the section on <link
xlink:href="&url.books.handbook;/using-localization.html#setting-console">console
@ -4166,7 +4165,7 @@ C:\="DOS"</programlisting>
<programlisting>options QUOTA</programlisting>
<para>Please read the <link
<para>Refer to the <link
xlink:href="&url.books.handbook;/quotas.html">Handbook
entry on quotas</link> for full details.</para>
</listitem>
@ -4178,7 +4177,7 @@ C:\="DOS"</programlisting>
<listitem>
<para>Put the quota file on the file system that the
quotas are to be enforced on, i.e.:</para>
quotas are to be enforced on:</para>
<informaltable frame="none" pgwide="1">
<tgroup cols="2">
@ -4282,7 +4281,7 @@ options SYSVMSG # enable for messaging</programlisting>
<answer>
<para>Do not panic! Restart the system, type
<userinput>boot -s</userinput> at the
<literal>Boot:</literal> prompt to enter Single User mode.
<literal>Boot:</literal> prompt to enter single-user mode.
At the question about the shell to use, hit
<keycap>Enter</keycap>. You will be dropped to a
&prompt.root; prompt. Enter <command>mount
@ -4296,7 +4295,7 @@ options SYSVMSG # enable for messaging</programlisting>
<note>
<para>If you are still prompted to give the <systemitem
class="username">root</systemitem> password when
entering the Single User mode, it means that the console
entering the single-user mode, it means that the console
has been marked as <literal>insecure</literal> in
<filename>/etc/ttys</filename>. In this case it will be
required to boot from a &os; installation disk, choose
@ -4304,15 +4303,15 @@ options SYSVMSG # enable for messaging</programlisting>
<guimenuitem>Shell</guimenuitem> at the beginning of the
install process and issue the commands mentioned above.
You will need to mount the specific partition in this
case and then chroot to it, i.e., replace <command>mount
-urw /</command> by <command>mount /dev/ada0p1 /mnt;
case and then chroot to it. For example, replace <command>mount
-urw /</command> with <command>mount /dev/ada0p1 /mnt;
chroot /mnt</command> for a system on
<replaceable>ada0p1</replaceable>.</para>
</note>
<note>
<para>If you cannot mount your root partition from Single
User mode, it is possible that the partitions are
<para>If you cannot mount your root partition from
single-user mode, it is possible that the partitions are
encrypted and it is impossible to mount them without the
access keys. Your chances depend on the chosen
implementation. For more information see the section
@ -4403,14 +4402,10 @@ options SYSVMSG # enable for messaging</programlisting>
</question>
<answer>
<para>Go into single user mode and then back to multi user
mode.</para>
<para>On the console do:</para>
<para>Go into single-user mode and then back to multi-user
mode:</para>
<screen>&prompt.root; <userinput>shutdown now</userinput>
(Note: without -r or -h)
&prompt.root; <userinput>return</userinput>
&prompt.root; <userinput>exit</userinput></screen>
</answer>
@ -4480,7 +4475,7 @@ options SYSVMSG # enable for messaging</programlisting>
<answer>
<para>Short answer: You are probably at security level
greater than 0. Reboot directly to Single User mode to
greater than 0. Reboot directly to single-user mode to
install the kernel.</para>
<para>Long answer: &os; disallows changing system flags at
@ -4490,7 +4485,7 @@ options SYSVMSG # enable for messaging</programlisting>
<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
to single-user mode to install the kernel, or change the
security level in <filename>/etc/rc.conf</filename> then
reboot. See the &man.init.8; manual page for details on
<literal>securelevel</literal>, and see
@ -4508,7 +4503,7 @@ options SYSVMSG # enable for messaging</programlisting>
<answer>
<para>Short answer: You are probably at security level
greater than 1. Reboot directly to Single User mode to
greater than 1. Reboot directly to single-user mode to
change the date.</para>
<para>Long answer: &os; disallows changing the time by more
@ -4518,7 +4513,7 @@ options SYSVMSG # enable for messaging</programlisting>
<screen>&prompt.root; <userinput>sysctl kern.securelevel</userinput></screen>
<para>You cannot lower the security level; you have to boot
to Single User mode to change the date, or change the
to single-user mode to change the date, or change the
security level in <filename>/etc/rc.conf</filename> then
reboot. See the &man.init.8; manual page for details on
<literal>securelevel</literal>, and see
@ -4560,8 +4555,8 @@ options SYSVMSG # enable for messaging</programlisting>
</question>
<answer>
<para>You are running at an elevated (i.e., greater than 0)
securelevel. Lower the securelevel and try again. For
<para>You are running a securelevel greater than 0.
Lower the securelevel and try again. For
more information, see <link linkend="securelevel">the FAQ
entry on securelevel</link> and the &man.init.8; manual
page.</para>
@ -4835,11 +4830,10 @@ options SYSVMSG # enable for messaging</programlisting>
X requires write access to &man.io.4;. For more
information, see at the &man.init.8; manual page.</para>
<para>There are two solutions to the problem: Set your
<literal>securelevel</literal> back down to zero (usually
in <filename>/etc/rc.conf</filename>), or run &man.xdm.1;
(or an alternative display manager) at boot time (before
the <literal>securelevel</literal> is raised).</para>
<para>There are two solutions to the problem: set the
<literal>securelevel</literal> back down to zero or run &man.xdm.1;
(or an alternative display manager) at boot time before
the <literal>securelevel</literal> is raised.</para>
<para>See <xref linkend="xdm-boot"/> for more information
about running &man.xdm.1; at boot time.</para>
@ -4908,7 +4902,7 @@ options SYSVMSG # enable for messaging</programlisting>
<para>Yes.</para>
<para>You need to tell X that you have a 5 button mouse. To
do this, simply add the lines <literal>Buttons 5</literal>
do this, add the lines <literal>Buttons 5</literal>
and <literal>ZAxisMapping 4 5</literal> to the
<quote>InputDevice</quote> section of
<filename>/etc/X11/xorg.conf</filename>. For example, you
@ -4988,7 +4982,7 @@ EndSection</programlisting>
<para>For security reasons, the default setting is to not
allow a machine to remotely open a window.</para>
<para>To enable this feature, simply start
<para>To enable this feature, start
<application>X</application> with the optional
<option>-listen_tcp</option> argument:</para>
@ -5003,7 +4997,7 @@ EndSection</programlisting>
</question>
<answer>
<para>Virtual consoles, put simply, enable you to have
<para>Virtual consoles enable you to have
several simultaneous sessions on the same machine without
doing anything complicated like setting up a network or
running X.</para>
@ -5148,7 +5142,7 @@ ttyvb "/usr/libexec/getty Pc" xterm off secure</programlisting>
<para>There are two schools of thought on how to start
&man.xdm.1;. One school starts <command>xdm</command>
from <filename>/etc/ttys</filename> (see &man.ttys.5;)
using the supplied example, while the other simply runs
using the supplied example, while the other runs
<command>xdm</command> from
<filename>rc.local</filename> (see &man.rc.8;) or from an
<filename>X</filename> script in
@ -5165,8 +5159,8 @@ ttyvb "/usr/libexec/getty Pc" xterm off secure</programlisting>
a problem starting the X server.</para>
<para>If loaded from &man.rc.8;, <command>xdm</command>
should be started without any arguments (i.e., as a
daemon). <command>xdm</command> must start
should be started without any arguments.
<command>xdm</command> must start
<emphasis>after</emphasis> &man.getty.8; runs, or else
<command>getty</command> and <command>xdm</command> will
conflict, locking out the console. The best way around
@ -5244,11 +5238,7 @@ ttyvb "/usr/libexec/getty Pc" xterm off secure</programlisting>
<para>If this happens, disable the synchronization check
code by setting the driver flags for the PS/2 mouse driver
to <literal>0x100</literal>. This can be easiest achieved
by adding
<screen>hint.psm.0.flags="0x100"</screen>
to
by adding <literal>hint.psm.0.flags="0x100"</literal> to
<filename>/boot/loader.conf</filename> and
rebooting.</para>
</answer>
@ -5435,7 +5425,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
<para><quote>Diskless booting</quote> means that the &os;
box is booted over a network, and reads the necessary
files from a server instead of its hard disk. For full
details, please read <link
details, see <link
xlink:href="&url.books.handbook;/network-diskless.html">the
Handbook entry on diskless booting</link>.</para>
</answer>
@ -5448,7 +5438,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
</question>
<answer>
<para>Yes. Please see the Handbook entry on <link
<para>Yes. Refer to the Handbook entry on <link
xlink:href="&url.books.handbook;/advanced-networking.html">advanced
networking</link>, specifically the section on <link
xlink:href="&url.books.handbook;/network-routing.html">routing
@ -5475,15 +5465,15 @@ Key F15 A A Menu Workplace Nop</programlisting>
and set <literal>gateway_enable</literal> to
<emphasis>YES</emphasis> in
<filename>/etc/rc.conf</filename>. For more information,
please see the &man.ppp.8; manual page or the <link
refer to &man.ppp.8; or the <link
xlink:href="&url.books.handbook;/userppp.html">Handbook
entry on user PPP</link>.</para>
<para>If you are using kernel-mode PPP or have an Ethernet
connection to the Internet, you need to use &man.natd.8;.
Please look at the <link
A tutorial can be found in the <link
xlink:href="&url.books.handbook;/network-natd.html">natd</link>
section of the Handbook for a tutorial.</para>
section of the Handbook.</para>
</answer>
</qandaentry>
@ -5496,7 +5486,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
<para>Yes. &man.ppp.8; provides support for both incoming
and outgoing connections.</para>
<para>For more information on how to use this, please see
<para>For more information on how to use this, refer to
the <link
xlink:href="&url.books.handbook;/ppp-and-slip.html">Handbook
chapter on PPP</link>.</para>
@ -5510,10 +5500,10 @@ Key F15 A A Menu Workplace Nop</programlisting>
<answer>
<para>Yes. If you want to use NAT over a user PPP
connection, please see the <link
connection, see the <link
xlink:href="&url.books.handbook;/userppp.html">Handbook
entry on user PPP</link>. If you want to use NAT over
some other sort of network connection, please look at the
some other sort of network connection, look at the
<link
xlink:href="&url.books.handbook;/network-natd.html">natd</link>
section of the Handbook.</para>
@ -5568,7 +5558,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
<answer>
<para>The most frequent problem is not understanding the
correct format of <filename>/etc/exports</filename>.
Please review &man.exports.5; and the <link
Review &man.exports.5; and the <link
xlink:href="&url.books.handbook;/network-nfs.html">NFS</link>
entry in the Handbook, especially the section on <link
xlink:href="&url.books.handbook;/network-nfs.html#configuring-nfs">configuring
@ -5691,8 +5681,8 @@ Key F15 A A Menu Workplace Nop</programlisting>
<answer>
<para>You can redirect FTP (and other service) request with
the <package>sysutils/socket</package> port. Simply
replace the service's command line to call
the <package>sysutils/socket</package> port.
Replace the service's command line to call
<command>socket</command> instead, like so:</para>
<programlisting>ftp stream tcp nowait nobody /usr/local/bin/socket socket <replaceable>ftp.example.com</replaceable> <replaceable>ftp</replaceable></programlisting>
@ -5896,7 +5886,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
<para>The most common way to accomplish this is to build
a simulated environment in a subdirectory and then run
the processes in that directory chrooted (i.e.,
the processes in that directory chrooted so that
<filename>/</filename> for that process is this
directory, not the real <filename>/</filename> of the
system).</para>
@ -5940,7 +5930,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
<para><literal>securelevel</literal> is a security
mechanism implemented in the kernel. When the securelevel
is positive, the kernel restricts certain tasks; not even
the superuser (i.e., <systemitem
the superuser (<systemitem
class="username">root</systemitem>) is allowed to do
them. The securelevel mechanism limits the ability
to:</para>
@ -5968,12 +5958,12 @@ Key F15 A A Menu Workplace Nop</programlisting>
</itemizedlist>
<para>To check the status of the securelevel on a running
system, simply execute the following command:</para>
system:</para>
<screen>&prompt.root; <userinput>sysctl -n kern.securelevel</userinput></screen>
<para>The output contains the current value of the
securelevel. If it is positive (i.e., greater than 0), at
securelevel. If it is greater than 0, at
least some of the securelevel's protections are
enabled.</para>
@ -5989,8 +5979,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
reboot.</para>
<para>For more information on securelevel and the specific
things all the levels do, please consult the &man.init.8;
manual page.</para>
things all the levels do, consult &man.init.8;.</para>
<warning>
<para>Securelevel is not a silver bullet; it has many
@ -6013,8 +6002,8 @@ Key F15 A A Menu Workplace Nop</programlisting>
file.</para>
<para>This point and others are often discussed on the
mailing lists, particularly the &a.security;. Please
search the archives <link
mailing lists, particularly the &a.security;.
Search the archives <link
xlink:href="&url.base;/search/index.html">here</link>
for an extensive discussion. A more fine-grained
mechanism is preferred.</para>
@ -6099,7 +6088,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
mounted for some reason, <systemitem
class="username">root</systemitem> will not be able to
log in to fix a problem (although if you reboot into
single user mode you will be prompted for the path to a
single-user mode you will be prompted for the path to a
shell).</para>
<para>Some people use <systemitem
@ -6107,7 +6096,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
<systemitem class="username">root</systemitem> tasks with
a non-standard shell, leaving <systemitem
class="username">root</systemitem>, with a standard
shell, for single user mode or emergencies. By default
shell, for single-user mode or emergencies. By default
you cannot log in using <systemitem
class="username">toor</systemitem> as it does not have a
password, so log in as <systemitem
@ -6133,7 +6122,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
<para>You should first read the &man.ppp.8; manual page and
the <link
xlink:href="&url.books.handbook;/ppp-and-slip.html#userppp">PPP
section of the handbook</link>. Enable logging with the
section of the Handbook</link>. Enable logging with the
following command:</para>
<programlisting>set log Phase Chat Connect Carrier lcp ipcp ccp command</programlisting>
@ -6168,14 +6157,14 @@ Key F15 A A Menu Workplace Nop</programlisting>
<filename>/etc/hosts</filename> is consulted by your
resolver first by editing
<filename>/etc/host.conf</filename> and putting the
<literal>hosts</literal> line first. Then, simply put an
<literal>hosts</literal> line first. Then, put an
entry in <filename>/etc/hosts</filename> for your local
machine. If you have no local network, change your
<systemitem>localhost</systemitem> line:</para>
<programlisting>127.0.0.1 foo.example.com foo localhost</programlisting>
<para>Otherwise, simply add another entry for your host.
<para>Otherwise, add another entry for your host.
Consult the relevant manual pages for more details.</para>
<para>You should be able to successfully <command>ping -c1
@ -6200,7 +6189,7 @@ default 10.0.0.2 UGSc 0 0 tun0
10.0.0.2 10.0.0.1 UH 0 0 tun0</programlisting>
<para>This is assuming that you have used the addresses from
the handbook, the manual page, or from
the Handbook, the manual page, or from
<filename>ppp.conf.sample</filename>. If you do not have
a default route, it may be because you forgot to add the
<literal>HISADDR</literal> line to
@ -6217,7 +6206,7 @@ default 10.0.0.2 UGSc 0 0 tun0
<para>If this is the case, go back to the <link
xlink:href="&url.books.handbook;/userppp.html#userppp-final">Final
System Configuration</link> section of the
handbook.</para>
Handbook.</para>
</answer>
</qandaentry>
@ -6248,7 +6237,7 @@ add 0 0 HISADDR</programlisting>
<para>Refer to the <link
xlink:href="&url.books.handbook;/userppp.html#userppp-dynamicip">PPP
and Dynamic IP addresses</link> section of the handbook
and Dynamic IP addresses</link> section of the Handbook
for further details.</para>
</answer>
</qandaentry>
@ -6323,7 +6312,7 @@ add 0 0 HISADDR</programlisting>
apparent explanation. The first thing to establish is
which side of the link is hung.</para>
<para>If you are using an external modem, you can simply try
<para>If you are using an external modem, try
using &man.ping.8; to see if the <acronym>TD</acronym>
light is flashing when you transmit data. If it flashes
(and the <acronym>RD</acronym> light does not), the
@ -7092,7 +7081,7 @@ ATDT1234567</programlisting>
<answer>
<para>There is a list of these in the <link
xlink:href="&url.books.handbook;/serial.html">Serial
Communications</link> chapter of the handbook.</para>
Communications</link> chapter of the Handbook.</para>
<para>Most multi-port PCI cards that are based on 16550 or
clones are supported with no extra effort.</para>
@ -7114,7 +7103,7 @@ ATDT1234567</programlisting>
<answer>
<para>See <link
xlink:href="&url.books.handbook;/serialconsole-setup.html">this
section of the handbook</link>.</para>
section of the Handbook</link>.</para>
</answer>
</qandaentry>
@ -7259,7 +7248,7 @@ hint.sio.7.irq="12"</programlisting>
</question>
<answer>
<para>Please read the section about <link
<para>Refer to the section about <link
xlink:href="&url.books.handbook;/dialup.html">Dial-in
Services</link> in the &os; Handbook.</para>
</answer>
@ -7584,7 +7573,7 @@ hint.sio.7.irq="12"</programlisting>
</question>
<answer>
<para>Please see the <link
<para>Refer to the <link
xlink:href="&url.books.handbook;/freebsd-glossary.html">&os;
Glossary</link>.</para>
</answer>
@ -7964,7 +7953,7 @@ hint.sio.7.irq="12"</programlisting>
</question>
<answer>
<para>Please see the article on <link
<para>See the article on <link
xlink:href="&url.articles.contributing;/article.html">Contributing
to &os;</link> for specific advice on how to do this.
Assistance is more than welcome!</para>
@ -8007,10 +7996,10 @@ hint.sio.7.irq="12"</programlisting>
</listitem>
</itemizedlist>
<para><literal>HEAD</literal> is not an actual branch tag,
like the others; it is simply a symbolic constant for
<quote><emphasis>the current, non-branched development
stream</emphasis></quote> which we simply refer to as
<para><literal>HEAD</literal> is not an actual branch tag.
It is a symbolic constant for
the current, non-branched development
stream known as
<emphasis>-CURRENT</emphasis>.</para>
<para>Right now, <emphasis>-CURRENT</emphasis> is the
@ -8043,7 +8032,7 @@ hint.sio.7.irq="12"</programlisting>
</question>
<answer>
<para>Please take a look at the article on <link
<para>Take a look at the article on <link
xlink:href="&url.articles.contributing;/article.html">Contributing
to &os;</link> to learn how to submit code.</para>
@ -8109,7 +8098,7 @@ panic: page fault</programlisting>
the instruction pointer address will be somewhere
inside a function, not at the start. If you do not
get an exact match, omit the last digit from the
instruction pointer value and try again, i.e.:</para>
instruction pointer value and try again:</para>
<screen>&prompt.user; <userinput>nm -n kernel.that.caused.the.panic | grep f0xxxxx</userinput></screen>