Assorted spelling and grammar cleanups.
This commit is contained in:
Daniel Harris
parent
5c75be36bd
commit
74a066fbfc
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=9623
1 changed files with 35 additions and 35 deletions
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/disks/chapter.sgml,v 1.26 2001/04/09 00:33:49 dd Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/disks/chapter.sgml,v 1.27 2001/04/21 23:14:53 dd Exp $
|
||||
-->
|
||||
|
||||
<chapter id="disks">
|
||||
|
|
@ -220,7 +220,7 @@
|
|||
have their own branches, such as
|
||||
<filename>/usr/local</filename>, and so on.</para>
|
||||
|
||||
<para>There are various reasons to house certain of these
|
||||
<para>There are various reasons to house some of these
|
||||
directories on separate filesystems. <filename>/var</filename>
|
||||
contains log, spool, and various types of temporary files, and
|
||||
as such, may get filled up. Filling up the root filesystem
|
||||
|
|
@ -439,7 +439,7 @@
|
|||
disk is going to be truly dedicated to FreeBSD, you can use the
|
||||
<emphasis>dedicated</emphasis> mode. Otherwise, FreeBSD will have to live
|
||||
with in one of the PC BIOS partitions. FreeBSD calls the PC BIOS
|
||||
partitions, <emphasis>slices</emphasis> so as not to confuse them with
|
||||
partitions <emphasis>slices</emphasis> so as not to confuse them with
|
||||
traditional BSD partitions. You may also use slices on a disk that is
|
||||
dedicated to FreeBSD, but used in a computer that also has another
|
||||
operating system installed. This is to not confuse the
|
||||
|
|
@ -566,8 +566,8 @@
|
|||
<sect1 id="disks-virtual">
|
||||
<title>Virtual Disks: Network, Memory, and File-Based Filesystems</title>
|
||||
|
||||
<para>Besides the disks you physically insert into your computer;
|
||||
floppies, CDs, hard drives, and so forth, other forms of disks
|
||||
<para>Aside from the disks you physically insert into your computer:
|
||||
floppies, CDs, hard drives, and so forth; other forms of disks
|
||||
are understood by FreeBSD - the <firstterm>virtual
|
||||
disks</firstterm>.</para>
|
||||
|
||||
|
|
@ -761,17 +761,17 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
|
|||
combination of both. Each of these limits are further broken down
|
||||
into two categories; hard and soft limits.</para>
|
||||
|
||||
<para>A hard limit may not be exceeded. Once a user reaches their
|
||||
hard limit they may not make any further allocations on the file
|
||||
<para>A hard limit may not be exceeded. Once a user reaches his
|
||||
hard limit he may not make any further allocations on the file
|
||||
system in question. For example, if the user has a hard limit of
|
||||
500 blocks on a file system and is currently using 490 blocks, the
|
||||
user can only allocate an additional 10 blocks. Attempting to
|
||||
allocate an additional 11 blocks will fail.</para>
|
||||
allocate an additional 11 blocks will fail.</para>
|
||||
|
||||
<para>Soft limits on the other hand can be exceeded for a limited
|
||||
<para>Soft limits, on the other hand, can be exceeded for a limited
|
||||
amount of time. This period of time is known as the grace period,
|
||||
which is one week by default. If a user stays over his or her
|
||||
soft limit longer than their grace period, the soft limit will
|
||||
soft limit longer than the grace period, the soft limit will
|
||||
turn into a hard limit and no further allocations will be allowed.
|
||||
When the user drops back below the soft limit, the grace period
|
||||
will be reset.</para>
|
||||
|
|
@ -846,14 +846,14 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
|
|||
/usr/var 0 50 75 0 50 60</programlisting>
|
||||
|
||||
<para>On the <filename>/usr</filename> file system in the above
|
||||
example this user is currently 15 blocks over their soft limit of
|
||||
50 blocks and has 5 days of their grace period left. Note the
|
||||
example this user is currently 15 blocks over the soft limit of
|
||||
50 blocks and has 5 days of the grace period left. Note the
|
||||
asterisk <literal>*</literal> which indicates that the user is
|
||||
currently over their quota limit.</para>
|
||||
currently over his quota limit.</para>
|
||||
|
||||
<para>Normally file systems that the user is not using any disk
|
||||
space on will not show up in the output from the
|
||||
<command>quota</command> command, even if they have a quota limit
|
||||
<command>quota</command> command, even if he has a quota limit
|
||||
assigned for that file system. The <option>-v</option> option
|
||||
will display those file systems, such as the
|
||||
<filename>/usr/var</filename> file system in the above
|
||||
|
|
@ -889,14 +889,14 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
|
|||
<title>Introduction</title>
|
||||
|
||||
<para>CDs have a number of features that differentiate them from
|
||||
convential disks. Initially, they weren't writable by the
|
||||
user. They are designed so they can be read continuously without
|
||||
conventional disks. Initially, they weren't writable by the
|
||||
user. They are designed so that they can be read continuously without
|
||||
delays to move the head between tracks. They are also much easier
|
||||
to transport between system than similar sized media was at the
|
||||
to transport between systems than similarly sized media were at the
|
||||
time.</para>
|
||||
|
||||
<para>CDs do have tracks, but by this they mean a section of data to
|
||||
be read continuously, not a physical property of the disk. To
|
||||
<para>CDs do have tracks, but this refers to a section of data to
|
||||
be read continuously and not a physical property of the disk. To
|
||||
produce a CD on FreeBSD, you prepare the data files that are going
|
||||
to make up the tracks on the CD, then write the tracks to the
|
||||
CD.</para>
|
||||
|
|
@ -913,7 +913,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
|
|||
described below. You can install it with the <filename>
|
||||
/usr/ports/sysutils/mkisofs</filename> port.</para>
|
||||
|
||||
<para>The tool to use to burn the CD depend on whether your CD burner
|
||||
<para>Which tool to use to burn the CD depends on whether your CD burner
|
||||
is ATAPI or something else. ATAPI CD burners use the <command><link
|
||||
linkend="burncd">burncd</link></command> program that is part of
|
||||
the base system. SCSI and USB CD burners should use the
|
||||
|
|
@ -940,24 +940,24 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
|
|||
control it.</para>
|
||||
|
||||
<para>A number of options are available to overcome those
|
||||
restrictions. In particular, <option>-R</option> will enable the
|
||||
restrictions. In particular, <option>-R</option> enables the
|
||||
Rock Ridge extensions common to Unix systems, <option>-J</option>
|
||||
causes Joliet extenions used by Microsoft systems, and
|
||||
enables Joliet extensions used by Microsoft systems, and
|
||||
<option>-hfs</option> can be used to create HFS file systems used
|
||||
by Macs. Read &man.mkisofs.8; for more information on the last
|
||||
two.</para>
|
||||
|
||||
<para>For CD's that are going to be used only on FreeBSD systems,
|
||||
<para>For CDs that are going to be used only on FreeBSD systems,
|
||||
<option>-U</option> can be used to disable all filename
|
||||
restrictions. When used with <option>-R</option>, it produced a
|
||||
restrictions. When used with <option>-R</option>, it produces a
|
||||
file system image that is identical to the FreeBSD tree you started
|
||||
from, though it may violate the ISO 9660 standard in a number of
|
||||
ways.</para>
|
||||
|
||||
<para>The last option of general use is <option>-b</option>. This is
|
||||
used to specify the location of the boot image in producing a
|
||||
used to specify the location of the boot image for use in producing an
|
||||
<quote>El Torito</quote> bootable CD. This option takes an
|
||||
argument, which is the path to a boot image from the top of the
|
||||
argument which is the path to a boot image from the top of the
|
||||
tree being written to the CD. So, given that
|
||||
<filename>/tmp/myboot</filename> holds a bootable FreeBSD system
|
||||
with the boot image in
|
||||
|
|
@ -968,7 +968,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
|
|||
<screen>&prompt.root; <userinput>mkisofs <option>-U</option> <option>-R</option> <option>-b</option> <filename>boot/cdboot</filename> <option>-o</option> <filename>/tmp/bootable.iso</filename> <filename>/tmp/myboot</filename></userinput></screen>
|
||||
|
||||
<para>Having done that, if you have vn configured in your kernel, you
|
||||
can mount the file system by doing:</para>
|
||||
can mount the file system with:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>vnconfig <option>-e</option> <filename>vn0c</filename> <filename>/tmp/bootable.iso</filename></userinput>
|
||||
&prompt.root; <userinput>mount <option>-t</option> cd9660 <filename>/dev/vn0c</filename> <filename>/mnt</filename></userinput></screen>
|
||||
|
|
@ -976,8 +976,8 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
|
|||
<para>At which point you can verify that <filename>/mnt</filename>
|
||||
and <filename>/tmp/myboot</filename> are identical.</para>
|
||||
|
||||
<para>There are a large number of other options you can use with
|
||||
<command>mkisofs</command> to fine tune its behavior. See
|
||||
<para>There are many other options you can use with
|
||||
<command>mkisofs</command> to fine-tune its behavior. See
|
||||
&man.mkisofs.8; for details.</para>
|
||||
</sect2>
|
||||
|
||||
|
|
@ -988,14 +988,14 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
|
|||
<command>burncd</command> command to burn an ISO image onto a
|
||||
CD. <command>burncd</command> is part of the base system, installed
|
||||
as <filename>/usr/sbin/burncd</filename>. Usage is very simple, as
|
||||
it does not have a lot of options:</para>
|
||||
it has few options:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>burncd <option>-f</option> <replaceable>cddevice</replaceable> data <replaceable>imagefile.iso</replaceable> fixate</userinput></screen>
|
||||
|
||||
<para>Will burn a copy of <replaceable>imagefile.iso</replaceable> on
|
||||
<replaceable>cddevice</replaceable>. The default device is
|
||||
<filename>/dev/acd0</filename>. See &man.burncd.8; for options like
|
||||
setting the write speed, ejecting the floppy, and writing audio
|
||||
<filename>/dev/acd0</filename>. See &man.burncd.8; for options to
|
||||
set the write speed, eject the CD after burning, and write audio
|
||||
data.</para>
|
||||
</sect2>
|
||||
|
||||
|
|
@ -1016,7 +1016,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
|
|||
|
||||
<para>While <command>cdrecord</command> has many options, basic usage
|
||||
is even simpler than <command>burncd</command>. Burning an ISO 9660
|
||||
image is done by:</para>
|
||||
image is done with:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>cdrecord <option>dev=</option><replaceable>device</replaceable> <replaceable>imagefile.iso</replaceable></userinput></screen>
|
||||
|
||||
|
|
@ -1048,13 +1048,13 @@ scsibus1:
|
|||
1,7,0 107) *
|
||||
</screen>
|
||||
|
||||
<para>This lists the approriate <option>dev</option> value for the
|
||||
<para>This lists the appropriate <option>dev</option> value for the
|
||||
devices on the list. Locate your CD burner, and use the three
|
||||
numbers separated by commas as the value for
|
||||
<option>dev</option>. In this case, the CRW device is 1,5,0, so the
|
||||
appriate input would be
|
||||
<userinput><option>dev</option>=1,5,0</userinput>. There are easier
|
||||
ways to specify this value; see the &man.cdrecord.1; for
|
||||
ways to specify this value; see &man.cdrecord.1; for
|
||||
details. That is also the place to look for information on writing
|
||||
audio tracks, controlling the speed, and other things.</para>
|
||||
</sect2>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue