svn commit: r44830 - head/en_US.ISO8859-1/books/faq
Dru Lavigne
dru at FreeBSD.org
Wed May 14 15:19:15 UTC 2014
Author: dru
Date: Wed May 14 15:19:14 2014
New Revision: 44830
URL: http://svnweb.freebsd.org/changeset/doc/44830
Log:
More rewording around "you" usage.
Remove question about shosts.
Sponsored by: iXsystems
Modified:
head/en_US.ISO8859-1/books/faq/book.xml
Modified: head/en_US.ISO8859-1/books/faq/book.xml
==============================================================================
--- head/en_US.ISO8859-1/books/faq/book.xml Wed May 14 14:16:00 2014 (r44829)
+++ head/en_US.ISO8859-1/books/faq/book.xml Wed May 14 15:19:14 2014 (r44830)
@@ -933,13 +933,12 @@
<para>If the file is compressed,
<application>tar</application> will automatically
- detect the appropriate format and decompress it correctly.
- You will be left with a collection of
+ detect the appropriate format and decompress it correctly,
+ resulting in a collection of
<filename>.html</filename> files. The main one is called
<filename>index.html</filename>, which will contain the
table of contents, introductory material, and links to the
- other parts of the document. You can then copy or move
- these to their final location as necessary.</para>
+ other parts of the document.</para>
</answer>
</qandaentry>
@@ -950,7 +949,7 @@
</question>
<answer>
- <para>You can find full information in the <link
+ <para>Refer to the <link
xlink:href="&url.books.handbook;/eresources.html#eresources-mail">Handbook
entry on mailing-lists</link> and the <link
xlink:href="&url.books.handbook;/eresources-news.html">Handbook
@@ -986,7 +985,7 @@
questions. Other users can help with
the basics, referring to the Handbook whenever
possible and providing links for learning more about
- the topic you need help with. This is primarily an
+ a particular topic. This is primarily an
English speaking channel, though it does have users from
all over the world. Non-native English speakers should
try to ask the question in
@@ -1208,18 +1207,18 @@
</listitem>
<listitem>
- <para>Using the DOS <command>copy</command> command (or
- equivalent GUI tool) to transfer the boot image to
+ <para>Using the DOS <command>copy</command> command or
+ equivalent GUI tool to transfer the boot image to
floppy.</para>
<para>Programs like <command>copy</command> will not
work as the boot image has been created to be booted
into directly. The image has the complete content of
the floppy, track for track, and is not meant to be
- placed on the floppy as a regular file. You have to
- transfer it to the floppy <quote>raw</quote>, using
- the low-level tools (e.g., <command>fdimage</command>
- or <command>rawrite</command>) described in the <link
+ placed on the floppy as a regular file.
+ Transfer it to the floppy <quote>raw</quote>, using
+ <command>fdimage</command>
+ or <command>rawrite</command> as described in the <link
xlink:href="&url.books.handbook;/install.html">installation
guide to &os;</link>.</para>
</listitem>
@@ -2195,7 +2194,7 @@ to /etc/mail/sendmail.cf.</programlistin
<itemizedlist>
<listitem>
- <para>After logging on to the remote machine, set your
+ <para>After logging on to the remote machine, set the
<envar>TERM</envar> shell variable to
<literal>ansi</literal> or <literal>sco</literal> if
the remote machine knows about these terminal
@@ -2321,7 +2320,7 @@ to /etc/mail/sendmail.cf.</programlistin
</question>
<answer>
- <para>Your computer has two or more clocks, and &os; has
+ <para>The computer has two or more clocks, and &os; has
chosen to use the wrong one.</para>
<para>Run &man.dmesg.8;, and check for lines that contain
@@ -2334,7 +2333,7 @@ Timecounter "ACPI-fast" frequency 357954
Timecounter "TSC" frequency 2998570050 Hz quality 800
Timecounters tick every 1.000 msec</screen>
- <para>You can confirm this by checking the
+ <para>Confirm this by checking the
<varname>kern.timecounter.hardware</varname>
&man.sysctl.3;.</para>
@@ -2361,7 +2360,7 @@ kern.timecounter.hardware: ACPI-fast</sc
<screen>&prompt.root; <userinput>sysctl kern.timecounter.hardware=i8254</userinput>
kern.timecounter.hardware: TSC -> i8254</screen>
- <para>Your computer should now start keeping more accurate
+ <para>The computer should now start keeping more accurate
time.</para>
<para>To have this change automatically run at boot time,
@@ -2624,8 +2623,8 @@ kern.timecounter.hardware: TSC -> i82
<answer>
<para>&os; does not include a port upgrading tool, but it
does have some tools to make the upgrade process somewhat
- easier. You can also install additional tools to simplify
- port handling, see the <link
+ easier. Additional tools are available to simplify
+ port handling and are described the <link
xlink:href="&url.books.handbook;/ports-using.html">Upgrading
Ports</link> section in the &os; Handbook.</para>
</answer>
@@ -2698,7 +2697,7 @@ kern.timecounter.hardware: TSC -> i82
shells have. That is why other more featureful shells
like <command>bash</command>, <command>scsh</command>,
&man.tcsh.1;, and <command>zsh</command> are available.
- You can compare the memory utilization of
+ Compare the memory utilization of
these shells by looking at the <quote>VSZ</quote> and
<quote>RSS</quote> columns in a <command>ps -u</command>
listing.</para>
@@ -3059,9 +3058,8 @@ kern.sched.name: ULE</screen>
&prompt.root; <userinput>cd /mnt</userinput>
&prompt.root; <userinput>dump 0af - / | restore rf -</userinput></screen>
- <para>You might prefer &man.cpio.1;, &man.pax.1;,
- &man.tar.1; to &man.dump.8; for user data. At the time of
- this writing, these are known to lose file flag
+ <para>The &man.cpio.1; and &man.pax.1; utilities are also available
+ for moving user data. These are known to lose file flag
information, so use them with caution.</para>
</answer>
</qandaentry>
@@ -3232,26 +3230,28 @@ kern.sched.name: ULE</screen>
<qandaentry>
<question xml:id="grub-loader">
- <para>How do I boot &os; and &linux; using GRUB?</para>
+ <para>How do I boot &os; and &linux; using
+ <application>GRUB</application>?</para>
</question>
<answer>
- <para>Booting &os; using GRUB is very simple. Just add the
- following to your configuration file
- <filename>/boot/grub/menu.lst</filename> (or
- <filename>/boot/grub/grub.conf</filename> in some systems,
- e.g., Red Hat Linux and its derivatives).</para>
+ <para>To boot &os; using <application>GRUB</application>, add the
+ following to either
+ <filename>/boot/grub/menu.lst</filename> or
+ <filename>/boot/grub/grub.conf</filename>, depending upon
+ which is used by the &linux; distribution.</para>
- <programlisting>title &os; 6.1
+ <programlisting>title &os; 9.1
root <replaceable>(hd0,a)</replaceable>
kernel /boot/loader</programlisting>
- <para>Where <replaceable>hd0,a</replaceable> points to your
- root partition on the first disk. If you need to specify
- which slice number should be used, use something like this
+ <para>Where <replaceable>hd0,a</replaceable> points to the
+ root partition on the first disk. To specify
+ the slice number, use something like this
<replaceable>(hd0,2,a)</replaceable>. By default, if the
- slice number is omitted, GRUB searches the first slice
- which has <literal>a</literal> partition.</para>
+ slice number is omitted, <application>GRUB</application>
+ searches the first slice
+ which has the <literal>a</literal> partition.</para>
</answer>
</qandaentry>
@@ -3267,11 +3267,9 @@ kern.sched.name: ULE</screen>
then boot LILO from
<application>BootEasy</application>.</para>
- <para>If you are running &windows; and &linux; this is
- recommended anyway, to make it simpler to get &linux;
- booting again if you should need to reinstall &windows;
- (which is a Jealous Operating System, and will bear no
- other Operating Systems in the Master Boot Record).</para>
+ <para>This is recommended when running &windows; and &linux; as it
+ makes it simpler to get &linux;
+ booting again if &windows; is reinstalled.</para>
</answer>
</qandaentry>
@@ -3283,29 +3281,29 @@ kern.sched.name: ULE</screen>
</question>
<answer>
- <para>You can not do that with the standard boot manager
+ <para>This can not be accomplished with the standard boot manager
without rewriting it. There are a number of other boot
- managers in the <filename>sysutils</filename> ports
- category that provide this functionality.</para>
+ managers in the <filename>sysutils</filename> category of the Ports
+ Collection.</para>
</answer>
</qandaentry>
<qandaentry>
<question xml:id="removable-drives">
- <para>I have a new removable drive, how do I use it?</para>
+ <para>How do I use a new removable drive?</para>
</question>
<answer>
- <para>If the drive already has a file system on it, you can
+ <para>If the drive already has a file system on it,
use a command like this:</para>
<screen>&prompt.root; <userinput>mount -t msdosfs /dev/da0s1 /mnt</userinput></screen>
- <para>If the drive will only be used with &os; systems it is
- better idea to stick a BSD file system on it, like UFS or
- ZFS. You will get long filename support, at least a 2X
- improvement in performance, and a lot more stability. If
- the drive will be used by other operating systems a more
+ <para>If the drive will only be used with &os; systems,
+ partition it with <acronym>UFS</acronym> or
+ <acronym>ZFS</acronym>. This will provide long filename support,
+ improvement in performance, and stability. If
+ the drive will be used by other operating systems, a more
portable choice, such as msdosfs, is better.</para>
<screen>&prompt.root; <userinput>dd if=/dev/zero of=/dev/da0 count=2</userinput>
@@ -3332,15 +3330,13 @@ kern.sched.name: ULE</screen>
<qandaentry>
<question xml:id="mount-cd-superblock">
<para>Why do I get <errorname>Incorrect super
- block</errorname> when mounting a CD-ROM?</para>
+ block</errorname> when mounting a CD?</para>
</question>
<answer>
- <para>You have to tell &man.mount.8; the type of the device
- that you want to mount. This is described in the <link
- xlink:href="&url.books.handbook;/creating-cds.html">Handbook
- section on optical media</link>, specifically the
- section <link
+ <para>The type of device
+ to mount must be specified. This is described in the Handbook
+ section on <link
xlink:href="&url.books.handbook;/creating-cds.html#mounting-cd">Using
Data CDs</link>.</para>
</answer>
@@ -3349,12 +3345,12 @@ kern.sched.name: ULE</screen>
<qandaentry>
<question xml:id="cdrom-not-configured">
<para>Why do I get <errorname>Device not
- configured</errorname> when mounting a CD-ROM?</para>
+ configured</errorname> when mounting a CD?</para>
</question>
<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.
+ <para>This generally means that there is no CD in the
+ drive, or the drive is not visible on the bus.
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
@@ -3369,12 +3365,9 @@ kern.sched.name: ULE</screen>
</question>
<answer>
- <para>Your CD-ROM probably uses the <quote>Joliet</quote>
+ <para>The CD probably uses the <quote>Joliet</quote>
extension for storing information about files and
- directories. This is discussed in the Handbook chapter on
- <link
- xlink:href="&url.books.handbook;/creating-cds.html">creating
- and using CD-ROMs</link>, specifically the section on
+ directories. This is discussed in the Handbook section on
<link
xlink:href="&url.books.handbook;/creating-cds.html#mounting-cd">Using
Data CD-ROMs</link>.</para>
@@ -3383,17 +3376,14 @@ kern.sched.name: ULE</screen>
<qandaentry>
<question xml:id="burncd-isofs">
- <para>I burned a CD under &os; and now I can not read it
+ <para>A CD burned under &os; can not be read
under any other operating system. Why?</para>
</question>
<answer>
- <para>You most likely burned a raw file to your CD, rather
+ <para>This means a raw file was burned to the CD, rather
than creating an ISO 9660 file system. Take a look
- at the <link
- xlink:href="&url.books.handbook;/creating-cds.html">Handbook
- chapter on creating CD-ROMs</link>, particularly the
- section on <link
+ at the Handbook section on <link
xlink:href="&url.books.handbook;/creating-cds.html#mounting-cd">Using
Data <acronym>CD</acronym>s</link>.</para>
</answer>
@@ -3422,13 +3412,13 @@ kern.sched.name: ULE</screen>
</question>
<answer>
- <para>If you try to mount an audio CD, you will get an error
+ <para>Trying to mount an audio CD will produce an error
like <errorname>cd9660: /dev/acd0c: Invalid
argument</errorname>. This is because
<command>mount</command> only works on file systems.
Audio CDs do not have file systems; they just have data.
- You need a program that reads audio CDs, such as the
- <package>audio/xmcd</package> port.</para>
+ Instead, use a program that reads audio CDs, such as the
+ <package>audio/xmcd</package> package or port.</para>
</answer>
</qandaentry>
@@ -3440,8 +3430,8 @@ kern.sched.name: ULE</screen>
<answer>
<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
+ last data track (session) of a CD. To
+ load an earlier session, use the
<option>-s</option> command line argument. Refer to
&man.mount.cd9660.8; for specific examples.</para>
</answer>
@@ -3495,7 +3485,7 @@ kern.sched.name: ULE</screen>
<note>
<para>The device name used in the previous examples must
- be changed according to your configuration.</para>
+ be changed according to the configuration.</para>
</note>
</answer>
</qandaentry>
@@ -3508,8 +3498,7 @@ kern.sched.name: ULE</screen>
</question>
<answer>
- <para>You need to understand what <command>du</command> and
- <command>df</command> really do. <command>du</command>
+ <para>This is due to how these commands actually work. <command>du</command>
goes through the directory tree, measures how large each
file is, and presents the totals. <command>df</command>
just asks the file system how much space it has left.
@@ -3517,26 +3506,23 @@ kern.sched.name: ULE</screen>
directory entry will affect <command>df</command> but not
<command>du</command>.</para>
- <para>When a program is using a file, and you delete the
- file, the file is not really removed from the file system
+ <para>When a program is using a file, and the file is deleted,
+ the file is not really removed from the file system
until the program stops using it. The file is immediately
- deleted from the directory listing, however. You can see
- this easily enough with a program such as
- <command>more</command>. Assume you have a file large
+ deleted from the directory listing, however. As an example,
+ consider a file that is large
enough that its presence affects the output of
- <command>du</command> and <command>df</command>. (Since
- disks can be so large today, this might be a
- <emphasis>very</emphasis> large file!) If you delete this
- file while using <command>more</command> on it,
+ <command>du</command> and <command>df</command>. If this file is deleted
+ 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
removed from the directory so no other program or
- user can access it. <command>du</command> shows that it
- is gone — it has walked the directory tree and the
+ user can access it. However, <command>du</command> shows that it
+ is gone as it has walked the directory tree and the
file is not listed. <command>df</command> shows that it
is still there, as the file system knows that
<command>more</command> is still using that space. Once
- you end the <command>more</command> session,
+ the <command>more</command> session ends,
<command>du</command> and <command>df</command> will
agree.</para>
@@ -3550,8 +3536,8 @@ kern.sched.name: ULE</screen>
this from happening, set up &man.newsyslog.8;.</para>
<para>Note that Soft Updates can delay the freeing of disk
- space; you might need to wait up to 30 seconds for the
- change to be visible!</para>
+ space and it can take up to 30 seconds for the
+ change to be visible.</para>
</answer>
</qandaentry>
@@ -3561,12 +3547,9 @@ kern.sched.name: ULE</screen>
</question>
<answer>
- <para>In the <link
- xlink:href="&url.books.handbook;/config-tuning.html">Configuration
- and Tuning</link> section of the Handbook, you will find
- a <link
- xlink:href="&url.books.handbook;/adding-swap-space.html">section</link>
- describing how to do this.</para>
+ <para>This section<link
+ xlink:href="&url.books.handbook;/adding-swap-space.html">of the Handbook</link>
+ describes how to do this.</para>
</answer>
</qandaentry>
@@ -3602,7 +3585,7 @@ kern.sched.name: ULE</screen>
<systemitem class="username">root</systemitem> user.
&man.df.1; does not count that space when calculating the
<literal>Capacity</literal> column, so it can exceed 100%.
- Also, you will notice that the <literal>Blocks</literal>
+ Notice that the <literal>Blocks</literal>
column is always greater than the sum of the
<literal>Used</literal> and <literal>Avail</literal>
columns, usually by a factor of 8%.</para>
@@ -3677,7 +3660,7 @@ kern.sched.name: ULE</screen>
<answer>
<para>By default, ZFS stores the ZIL in the pool with all
- the data. If your application has a heavy write load,
+ the data. If an application has a heavy write load,
storing the ZIL in a separate device that has very fast
synchronous, sequential write performance can improve
overall system. For other workloads, a SSD is unlikely
@@ -3741,7 +3724,7 @@ kern.sched.name: ULE</screen>
<para>This could happen because the pool is 100% full.
ZFS requires space on the disk to write transaction
metadata. To restore the pool to a usable state,
- truncate a file you want to delete.</para>
+ truncate the file to delete:</para>
<screen>&prompt.user; <userinput>truncate -s 0 unimportant-file</userinput></screen>
@@ -3798,19 +3781,18 @@ kern.sched.name: ULE</screen>
<answer>
<para>The primary configuration file is
- <filename>/etc/defaults/rc.conf</filename> (see
- &man.rc.conf.5;). System startup scripts such as
+ <filename>/etc/defaults/rc.conf</filename> which is described in
+ &man.rc.conf.5;. System startup scripts such as
<filename>/etc/rc</filename> and
- <filename>/etc/rc.d</filename> (see &man.rc.8;) just
+ <filename>/etc/rc.d</filename>, which are described in &man.rc.8;,
include this file. <emphasis>Do not edit this
- file!</emphasis> Instead, if there is any entry in
- <filename>/etc/defaults/rc.conf</filename> that you want
- to change, you should copy the line into
+ file!</emphasis> Instead, to edit an entry in
+ <filename>/etc/defaults/rc.conf</filename>, copy the line into
<filename>/etc/rc.conf</filename> and change it
there.</para>
- <para>For example, if you wish to start &man.named.8;, the
- included DNS server, all you need to do is:</para>
+ <para>For example, if to start &man.named.8;, the
+ included DNS server:</para>
<screen>&prompt.root; <userinput>echo 'named_enable="YES"' >> /etc/rc.conf</userinput></screen>
@@ -3843,46 +3825,18 @@ kern.sched.name: ULE</screen>
</question>
<answer>
- <para>This is normally caused by editing the system crontab
- (<filename>/etc/crontab</filename>) and then using
- &man.crontab.1; to install it:</para>
-
- <screen>&prompt.root; <userinput>crontab /etc/crontab</userinput></screen>
-
- <para>This is not the correct way to do things. The system
- crontab has a different format to the per-user crontabs
- 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 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>This is normally caused by editing the system crontab.
+ This is not the correct way to do things as the system
+ crontab has a different format to the per-user crontabs.
+ The system
+ crontab has an extra field, specifying which user to run
+ the command as. &man.cron.8; assumes this user is the
+ first word of the command to execute. Since no such
+ command exists, this error message is displayed.</para>
- <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 is probably better to add shell scripts
- <filename>/usr/local/etc/periodic</filename>, and let the
- &man.periodic.8; command run from the system
- <command>cron</command> schedule it with the other
- periodic system tasks.</para>
+ <para>To delete the extra, incorrect crontab:</para>
- <para>The actual reason for the error is that the system
- crontab has an extra field, specifying which user to run
- the command as. In the default system crontab provided
- with &os;, this is <systemitem
- class="username">root</systemitem> for all entries.
- When this crontab is used as the <systemitem
- class="username">root</systemitem> user's crontab (which
- is <emphasis>not</emphasis> the same as the system
- crontab), &man.cron.8; assumes the string
- <literal>root</literal> is the first word of the command
- to execute, but no such command exists.</para>
+ <screen>&prompt.root; <userinput>crontab -r</userinput></screen>
</answer>
</qandaentry>
@@ -3895,18 +3849,14 @@ kern.sched.name: ULE</screen>
</question>
<answer>
- <para>This is a security feature. To <command>su</command>
- to <systemitem class="username">root</systemitem> (or any
- other account with superuser privileges), you must be in
+ <para>This is a security feature. In order to <command>su</command>
+ to <systemitem class="username">root</systemitem>, or any
+ other account with superuser privileges, the user account must be a member of
the <systemitem class="groupname">wheel</systemitem>
group. If this feature were not there, anybody with an
account on a system who also found out <systemitem
class="username">root</systemitem>'s password would be
- able to gain superuser level access to the system. With
- this feature, this is not strictly true; &man.su.1; will
- prevent them from even trying to enter the password if
- they are not in <systemitem
- class="groupname">wheel</systemitem>.</para>
+ able to gain superuser level access to the system.</para>
<para>To allow someone to <command>su</command> to
<systemitem class="username">root</systemitem>, put
@@ -3937,23 +3887,23 @@ kern.sched.name: ULE</screen>
-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
- favorite editor is defined. If your favorite editor is on
- a network file system, you will need to either configure
- the network manually before you can mount network file
+ favorite editor is defined. If that editor is on
+ a network file system, either configure
+ the network manually before you mounting the network file
systems, or use an editor which resides on a local file
system, such as &man.ed.1;.</para>
- <para>If you intend to use a full screen editor such as
- &man.vi.1; or &man.emacs.1;, you may also need to run
+ <para>In order to use a full screen editor such as
+ &man.vi.1; or &man.emacs.1;, run
<command>export TERM=xterm</command> on &os; 9.0+, or
<command>export TERM=cons25</command> on &os; 8.X so that
these editors can load the correct data from the
&man.termcap.5; database.</para>
- <para>Once you have performed these steps, you can edit
- <filename>/etc/rc.conf</filename> as you usually would to
+ <para>After performing these steps, edit
+ <filename>/etc/rc.conf</filename> to
fix the syntax error. The error message displayed
- immediately after the kernel boot messages should tell you
+ immediately after the kernel boot messages should indicate
the number of the line in the file which is at
fault.</para>
</answer>
@@ -3967,16 +3917,7 @@ kern.sched.name: ULE</screen>
<answer>
<para>See the <link
xlink:href="&url.books.handbook;/printing.html">Handbook
- entry on printing</link>. It should cover most of your
- problem.</para>
-
- <para>Some printers require a host-based driver to do any
- kind of printing. These so-called
- <quote>WinPrinters</quote> are not natively supported by
- &os;. If your printer does not work in DOS or &windows;,
- it is probably a WinPrinter. Your only hope of getting
- one of these to work is to check if the
- <package>print/pnm2ppa</package> port supports it.</para>
+ entry on printing</link> for troubleshooting tips.</para>
</answer>
</qandaentry>
@@ -4003,10 +3944,10 @@ kern.sched.name: ULE</screen>
<answer>
<orderedlist>
<listitem>
- <para>It is possible that your kernel is not configured
- to use quotas. If this is the case, you will need to
- add the following line to your kernel configuration
- file and recompile:</para>
+ <para>It is possible that the kernel is not configured
+ to use quotas. In this case,
+ add the following line to the kernel configuration
+ file and recompile the kernel:</para>
<programlisting>options QUOTA</programlisting>
@@ -4074,13 +4015,13 @@ kern.sched.name: ULE</screen>
<filename>sysvsem.ko</filename> and
<filename>sysvmsg.ko</filename> kernel modules, or
enabled in the custom kernel by adding the following lines
- to your kernel config:</para>
+ to the kernel configuration file:</para>
<programlisting>options SYSVSHM # enable shared memory
options SYSVSEM # enable for semaphores
options SYSVMSG # enable for messaging</programlisting>
- <para>Recompile and install your kernel.</para>
+ <para>Recompile and install the kernel.</para>
</answer>
</qandaentry>
@@ -4094,25 +4035,13 @@ options SYSVMSG # enable for
<para>The <link
xlink:href="http://www.sendmail.org/"><application>sendmail</application></link>
server is the default mail-server software for &os;, but
- you can easily replace it with one of the other MTA (for
- instance, an MTA installed from the ports).</para>
-
- <para>There are various alternative MTAs in the ports tree
- already, with <package>mail/exim</package>,
- <package>mail/postfix</package>,
- <package>mail/qmail</package>, and
- <package>mail/zmailer</package> being some of the most
- popular choices.</para>
-
- <para>Diversity is nice, and the fact that you have many
- different mail-servers to chose from is considered a good
- thing; therefore try to avoid asking questions like
- <quote>Is <application>sendmail</application> better than
- <application>qmail</application>?</quote> in the mailing
- lists. If you do feel like asking, first check the
- mailing list archives. The advantages and disadvantages
- of each and every one of the available MTAs have already
- been discussed a few times.</para>
+ it can be replaced with another
+ MTA installed from the Ports Collection. Available ports
+ include <package>mail/exim</package>,
+ <package>mail/postfix</package>, and
+ <package>mail/qmail</package>. Search the mailing lists
+ for discussions regarding the advantages and disadvantages
+ of the available MTAs.</para>
</answer>
</qandaentry>
@@ -4128,9 +4057,9 @@ options SYSVMSG # enable for
<userinput>boot -s</userinput> at the
<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
+ <keycap>Enter</keycap> which will display a
&prompt.root; prompt. Enter <command>mount
- -urw /</command> to remount your root file system
+ -urw /</command> to remount the root file system
read/write, then run <command>mount -a</command> to
remount all the file systems. Run <command>passwd
root</command> to change the <systemitem
@@ -4142,12 +4071,12 @@ options SYSVMSG # enable for
class="username">root</systemitem> password when
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
+ <filename>/etc/ttys</filename>. In this case, it will be
required to boot from a &os; installation disk, choose
the <guimenuitem>Live CD</guimenuitem> or
<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
+ Mount the specific partition in this
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
@@ -4155,11 +4084,10 @@ options SYSVMSG # enable for
</note>
<note>
- <para>If you cannot mount your root partition from
+ <para>If the root partition can not be mounted 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
+ access keys. For more information see the section
about encrypted disks in the &os; <link
xlink:href="&url.books.handbook;/disks-encrypting.html">Handbook</link>.</para>
</note>
@@ -4174,8 +4102,8 @@ options SYSVMSG # enable for
</question>
<answer>
- <para>If you are using &man.syscons.4; (the default console
- driver) build and install a new kernel with the line in
+ <para>When using &man.syscons.4;, the default console
+ driver, build and install a new kernel with this line in
the configuration file:</para>
<programlisting>options SC_DISABLE_REBOOT</programlisting>
@@ -4188,9 +4116,8 @@ options SYSVMSG # enable for
<note>
<para>The above two methods are exclusive: The
- &man.sysctl.8; does not exist if you compile your kernel
- with the <literal>SC_DISABLE_REBOOT</literal>
- option.</para>
+ &man.sysctl.8; does not exist if the kernel is compiled
+ with <literal>SC_DISABLE_REBOOT</literal>.</para>
</note>
</answer>
</qandaentry>
@@ -4211,8 +4138,7 @@ options SYSVMSG # enable for
with the original file stored with a
<filename>.bak</filename> extension.</para>
- <para>Alternatively you can use the &man.tr.1;
- command:</para>
+ <para>Alternatively, use &man.tr.1;:</para>
<screen>&prompt.user; <userinput>tr -d '\r' < dos-text-file > unix-file</userinput></screen>
@@ -4319,17 +4245,17 @@ options SYSVMSG # enable for
</question>
<answer>
- <para>Short answer: You are probably at security level
+ <para>Short answer: the security level is
greater than 0. Reboot directly to single-user mode to
install the kernel.</para>
<para>Long answer: &os; disallows changing system flags at
- security levels greater than 0. You can check your
- security level with the command:</para>
+ security levels greater than 0. To check the current
+ security level:</para>
<screen>&prompt.root; <userinput>sysctl kern.securelevel</userinput></screen>
- <para>You cannot lower the security level; you have to boot
+ <para>The security level can not be lowered in multi-user mode, so boot
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
@@ -4347,19 +4273,19 @@ options SYSVMSG # enable for
</question>
<answer>
- <para>Short answer: You are probably at security level
+ <para>Short answer: the system is at a security level
greater than 1. Reboot directly to single-user mode to
change the date.</para>
<para>Long answer: &os; 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>
+ that one second at security levels greater than 1. To
+ check the security level:</para>
<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
- security level in <filename>/etc/rc.conf</filename> then
+ <para>The security level can not be lowered in multi-user mode. Either boot
+ to single-user mode to change the date or change the
+ security level in <filename>/etc/rc.conf</filename> and
reboot. See the &man.init.8; manual page for details on
<literal>securelevel</literal>, and see
<filename>/etc/defaults/rc.conf</filename> and the
@@ -4400,7 +4326,7 @@ options SYSVMSG # enable for
</question>
<answer>
- <para>You are running a securelevel greater than 0.
+ <para>The system is running a securelevel greater than 0.
Lower the securelevel and try again. For
more information, see <link linkend="securelevel">the <acronym>FAQ</acronym>
entry on securelevel</link> and the &man.init.8; manual
@@ -4409,41 +4335,6 @@ options SYSVMSG # enable for
</qandaentry>
<qandaentry>
- <question xml:id="ssh-shosts">
- <para>Why does <application>SSH</application> authentication
- through <filename>.shosts</filename> not work by default
- in recent versions of &os;?</para>
- </question>
-
- <answer>
- <para>The reason why <filename>.shosts</filename>
- authentication does not work by default in more recent
- versions of &os; is because &man.ssh.1; is not installed
- suid <systemitem class="username">root</systemitem> by
- default. To <quote>fix</quote> this, you can do one of
- the following:</para>
-
- <itemizedlist>
- <listitem>
- <para>As a permanent fix, set
- <varname>ENABLE_SUID_SSH</varname> to
- <literal>true</literal> in
- <filename>/etc/make.conf</filename> then rebuild and
- reinstall &man.ssh.1;.</para>
- </listitem>
-
- <listitem>
- <para>As a temporary fix, change the mode on
- <filename>/usr/bin/ssh</filename> to
- <literal>4555</literal> by running <command>chmod 4555
- /usr/bin/ssh</command> as <systemitem
- class="username">root</systemitem>.</para>
- </listitem>
- </itemizedlist>
- </answer>
- </qandaentry>
-
- <qandaentry>
<question xml:id="vnlru">
<para>What is <literal>vnlru</literal>?</para>
</question>
More information about the svn-doc-all
mailing list