Add missing words to make complete sentences.

Clarify the descriptions of the different mount options.
Clean up a couple of man page references.
This commit is contained in:
Murray Stokely 2001-08-10 01:18:34 +00:00
parent 126c118090
commit 91bb5c5671
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=10282

View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/disks/chapter.sgml,v 1.44 2001/08/08 17:27:03 dd Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/disks/chapter.sgml,v 1.45 2001/08/09 23:42:30 chern Exp $
-->
<chapter id="disks">
@ -213,7 +213,7 @@
<para>Slices, <quote>dangerously dedicated</quote> physical
drives, and other drives contain
<firstterm>partitions</firstterm>, which represented as
<firstterm>partitions</firstterm>, which are represented as
letters from <literal>a</literal> to <literal>h</literal>.
<literal>b</literal> is reserved for swap partitions, and
<literal>c</literal> is an unused partition the size of the
@ -300,7 +300,7 @@
filesystems, followed by any other options that may be
needed. A common option is <option>noauto</option> for
filesystems not normally mounted during the boot sequence.
Other options in the &man.mount.8; manual page.</para>
Other options are listed in the &man.mount.8; manual page.</para>
</listitem>
</varlistentry>
@ -342,9 +342,11 @@
<term><option>-a</option></term>
<listitem>
<para>Mount all filesystems in
<filename>/etc/fstab</filename>, as modified by
<option>-t</option>, if given.</para>
<para>Mount all the filesystems listed in
<filename>/etc/fstab</filename>. Exceptions are those
marked as <quote>noauto</quote>, excluded by the
<option>-t</option> flag, or those that are already
mounted.</para>
</listitem>
</varlistentry>
@ -352,8 +354,10 @@
<term><option>-d</option></term>
<listitem>
<para>Do everything but actually mount the
filesystem.</para>
<para>Do everything except for the actual system call.
This option is useful in conjunction with the
<option>-v</option> flag to determine what the
<command>mount</command> is actually trying to do.</para>
</listitem>
</varlistentry>
@ -361,7 +365,10 @@
<term><option>-f</option></term>
<listitem>
<para>Force the mounting the filesystem.</para>
<para>Force the mount of an unclean filesystem
(dangerous), or forces the revocation of write access
when downgrading a filesystem's mount status from
read-write to read-only.</para>
</listitem>
</varlistentry>
@ -369,7 +376,9 @@
<term><option>-r</option></term>
<listitem>
<para>Mount the filesystem read-only.</para>
<para>Mount the filesystem read-only. This is identical
to using the <option>rdonly</option> argument to the
<option>-o</option> option.</para>
</listitem>
</varlistentry>
@ -412,7 +421,7 @@
</varlistentry>
</variablelist>
<para>The <option>-o</option> takes a comma-separated list of
<para>The <option>-o</option> option takes a comma-separated list of
the options, including the following:</para>
<variablelist>
@ -421,7 +430,7 @@
<listitem>
<para>Do not interpret special devices on the
filesystem. Useful security option.</para>
filesystem. This is a useful security option.</para>
</listitem>
</varlistentry>
@ -430,7 +439,7 @@
<listitem>
<para>Do not allow execution of binaries on this
filesystem. Useful security option.</para>
filesystem. This is also a useful security option.</para>
</listitem>
</varlistentry>
@ -439,14 +448,14 @@
<listitem>
<para>Do not interpret setuid or setgid flags on the
filesystem. Useful security option.</para>
filesystem. This is also a useful security option.</para>
</listitem>
</varlistentry>
</variablelist>
</sect2>
<sect2 id="disks-umount">
<title>The umount Command</title>
<title>The <command>umount</command> Command</title>
<indexterm>
<primary>filesystems</primary>
<secondary>unmounting</secondary>
@ -534,7 +543,9 @@
<primary><application>sysinstall</application></primary>
<secondary>adding disks</secondary>
</indexterm>
<indexterm>
<primary>su</primary>
</indexterm>
<procedure>
<step>
<title>Navigating <application>Sysinstall</application></title>
@ -699,7 +710,7 @@
linkend="nfs">Network Filesystem</link> and Coda, memory-based
filesystems such as <link linkend="disks-md">md</link> and
file-backed filesystems created by <link
linkend="disks-vnconfig">vnconfig</link>.</para>
linkend="disks-vnconfig">vnconfig</link> or mdconfig.</para>
<sect2 id="disks-vnconfig">
<title>vnconfig: File-Backed Filesystem</title>
@ -755,7 +766,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
<secondary>memory filesystem</secondary>
</indexterm>
<para><devicename>md</devicename> is a simple, efficient means to do memory
<para><devicename>md</devicename> is a simple, efficient means to create memory
filesystems.</para>
<para>Simply take a filesystem you've prepared with, for
@ -804,8 +815,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
<para>The stock <filename>GENERIC</filename> kernel does not have
this enabled by default, so you will have to configure, build and
install a custom kernel in order to use disk quotas. Please refer
to the <link linkend="kernelconfig">Configuring the FreeBSD
Kernel</link> section for more information on kernel
to <xref linkend="kernelconfig"> for more information on kernel
configuration.</para>
<para>Next you will need to enable disk quotas in
@ -966,8 +976,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
<screen>&prompt.root; <userinput>edquota -p test 10000-19999</userinput></screen>
<para>See the &man.edquota.8; for more detailed
information.</para>
<para>For more information see &man.edquota.8;.</para>
</sect2>
<sect2>