svn commit: r40906 - head/en_US.ISO8859-1/books/handbook/disks

Dru Lavigne dru at FreeBSD.org
Thu Feb 7 15:53:27 UTC 2013


Author: dru
Date: Thu Feb  7 15:53:27 2013
New Revision: 40906
URL: http://svnweb.freebsd.org/changeset/doc/40906

Log:
  This patch addresses the following:
  
  - fix &os;, <xref>, incorrect directory, varname, and devicename tags
  
  - general rewording/tightening to address "you" and redundancy
  
  - one comment was weirdly tagged and I couldn't figure out how to fix it so it was removed
  
  - a newfs example was modified as UFS2 is now the default
  
  Approved by:  bcr (mentor)

Modified:
  head/en_US.ISO8859-1/books/handbook/disks/chapter.xml

Modified: head/en_US.ISO8859-1/books/handbook/disks/chapter.xml
==============================================================================
--- head/en_US.ISO8859-1/books/handbook/disks/chapter.xml	Thu Feb  7 15:09:55 2013	(r40905)
+++ head/en_US.ISO8859-1/books/handbook/disks/chapter.xml	Thu Feb  7 15:53:27 2013	(r40906)
@@ -11,7 +11,7 @@
   <sect1 id="disks-synopsis">
     <title>Synopsis</title>
 
-    <para>This chapter covers the use of disks in FreeBSD.  This
+    <para>This chapter covers the use of disks in &os;.  This
       includes memory-backed disks, network-attached disks,
       standard SCSI/IDE storage devices, and devices using the USB
       interface.</para>
@@ -20,13 +20,13 @@
 
     <itemizedlist>
       <listitem>
-	<para>The terminology FreeBSD uses to describe the
-	  organization of data on a physical disk (partitions and
-	  slices).</para>
+	<para>The terminology &os; uses to describe the organization
+	  of data on a physical disk.</para>
       </listitem>
 
       <listitem>
-	<para>How to add additional hard disks to your system.</para>
+	<para>How to add additional hard disks to a &os;
+	  system.</para>
       </listitem>
 
       <listitem>
@@ -48,7 +48,7 @@
       </listitem>
 
       <listitem>
-	<para>How to create and burn CDs and DVDs on FreeBSD.</para>
+	<para>How to create and burn CDs and DVDs on &os;.</para>
       </listitem>
 
       <listitem>
@@ -56,8 +56,8 @@
       </listitem>
 
       <listitem>
-	<para>How to use backup programs available under
-	  FreeBSD.</para>
+	<para>How to use the backup programs available under
+	  &os;.</para>
       </listitem>
 
       <listitem>
@@ -74,8 +74,8 @@
 
     <itemizedlist>
       <listitem>
-	<para>Know how to configure and install a new FreeBSD kernel
-	  (<xref linkend="kernelconfig"/>).</para>
+	<para>Know how to <link linkend="kernelconfig">configure and
+	    install a new &os; kernel</link>.</para>
       </listitem>
     </itemizedlist>
   </sect1>
@@ -84,8 +84,7 @@
     <title>Device Names</title>
 
     <para>The following is a list of physical storage devices
-      supported in FreeBSD, and the device names associated with
-      them.</para>
+      supported in &os;, and their associated device names.</para>
 
     <table id="disk-naming-physical-table" frame="none">
       <title>Physical Disk Naming Conventions</title>
@@ -180,21 +179,16 @@
       <secondary>adding</secondary>
     </indexterm>
 
-    <para>The following section will describe how to add a new
+    <para>This section describes how to add a new
       <acronym>SCSI</acronym> disk to a machine that currently only
-      has a single drive.  First turn off the computer and install the
-      drive in the computer following the instructions of the
-      computer, controller, and drive manufacturer.  Due to the wide
-      variations of procedures to do this, the details are beyond the
-      scope of this document.</para>
-
-    <para>Login as user <username>root</username>.  After you have
-      installed the drive, inspect
-      <filename>/var/run/dmesg.boot</filename> to ensure the new disk
-      was found.  Continuing with our example, the newly added drive
-      will be <devicename>da1</devicename> and we want to mount it on
-      <filename>/1</filename> (if you are adding an IDE drive, the
-      device name will be <devicename>ad1</devicename>).</para>
+      has a single drive.  First, turn off the computer and install
+      the drive in the computer following the instructions of the
+      computer, controller, and drive manufacturers.  Reboot
+      the system and become <username>root</username>.</para>
+
+    <para>Inspect <filename>/var/run/dmesg.boot</filename> to ensure
+      the new disk was found.  In this example, the newly added SCSI
+      drive should appear as <devicename>da1</devicename>.</para>
 
     <indexterm><primary>partitions</primary></indexterm>
     <indexterm><primary>slices</primary></indexterm>
@@ -202,36 +196,35 @@
       <primary><command>fdisk</command></primary>
     </indexterm>
 
-    <para>FreeBSD runs on IBM-PC compatible computers, therefore it
-      must take into account the PC BIOS partitions.  These are
+    <para>&os; runs on IBM-PC compatible computers, therefore it
+      must take into account the PC BIOS partitions which are
       different from the traditional BSD partitions.  A PC disk has up
       to four BIOS partition entries.  If the disk is going to be
-      truly dedicated to FreeBSD, you can use the
-      <emphasis>dedicated</emphasis> mode.  Otherwise, FreeBSD will
-      have to live within one of the PC BIOS partitions.  FreeBSD
-      calls the PC BIOS 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 a good way to avoid confusing the
-      <command>fdisk</command> utility of other, non-FreeBSD operating
-      systems.</para>
+      truly dedicated to &os;, use <emphasis>dedicated</emphasis>
+      mode.  Otherwise, &os; will have to live within one of the PC
+      BIOS partitions.  &os; calls the PC BIOS partitions
+      <emphasis>slices</emphasis> so as not to confuse them with
+      traditional BSD partitions.  Slices may also be used on a disk
+      that is dedicated to &os;, but used in a computer that also has
+      another operating system installed.  This is a good way to avoid
+      confusing the <command>fdisk</command> utility of non-&os;
+      operating systems.</para>
 
-    <para>In the slice case the drive will be added as
+    <para>In the slice case, the drive will be added as
       <filename>/dev/da1s1e</filename>.  This is read as: SCSI disk,
       unit number 1 (second SCSI disk), slice 1 (PC BIOS partition 1),
       and <filename>e</filename> BSD partition.  In the dedicated
-      case, the drive will be added simply as
+      case, the drive will be added as
       <filename>/dev/da1e</filename>.</para>
 
     <para>Due to the use of 32-bit integers to store the number of
-      sectors, &man.bsdlabel.8; is limited to 2^32-1 sectors per disk
+      sectors, &man.bsdlabel.8; is limited to 2^32-1 sectors per disk,
       or 2TB in most cases.  The &man.fdisk.8; format allows a
       starting sector of no more than 2^32-1 and a length of no more
-      than 2^32-1, limiting partitions to 2TB and disks to 4TB in most
-      cases.  The &man.sunlabel.8; format is limited to 2^32-1 sectors
-      per partition and 8 partitions for a total of 16TB.  For larger
-      disks, &man.gpart.8; may be used to create
+      than 2^32-1, limiting partitions to 2TB and disks to 4TB, in
+      most cases.  The &man.sunlabel.8; format is limited to 2^32-1
+      sectors per partition and 8 partitions for a total of 16TB.  For
+      larger disks, &man.gpart.8; may be used to create
       <acronym>GPT</acronym> partitions.  <acronym>GPT</acronym> has
       the added benefit of not being limited to 4 slices.</para>
 
@@ -249,15 +242,14 @@
       <procedure>
 	<step>
 	  <title>Navigating
-	    <application>Sysinstall</application></title>
+	    <application>sysinstall</application></title>
 
-	  <para>You may use <command>sysinstall</command> to partition
-	    and label a new disk using its easy to use menus.  Either
-	    login as user <username>root</username> or use the
-	    <command>su</command> command.  Run
+	  <para><command>sysinstall</command> can be used to partition
+	    and label a new disk using its easy-to-use menus.  As
+	    <username>root</username>, run
 	    <command>sysinstall</command> and enter the
 	    <literal>Configure</literal> menu.  Within the
-	    <literal>FreeBSD Configuration Menu</literal>, scroll down
+	    <literal>&os; Configuration Menu</literal>, scroll down
 	    and select the <literal>Fdisk</literal> option.</para>
 	</step>
 
@@ -266,14 +258,14 @@
 	    Editor</title>
 
 	  <para>Once inside <application>fdisk</application>, pressing
-	    <keycap>A</keycap> will use the entire disk for FreeBSD.
-	    When asked if you want to <quote>remain cooperative with
+	    <keycap>A</keycap> will use the entire disk for &os;.
+	    When asked whether to <quote>remain cooperative with
 	      any future possible operating systems</quote>, answer
 	    <literal>YES</literal>.  Write the changes to the disk
-	    using <keycap>W</keycap>.  Now exit the FDISK editor by
-	    pressing <keycap>Q</keycap>.  Next you will be asked about
-	    the <quote>Master Boot Record</quote>.  Since you are
-	    adding a disk to an already running system, choose
+	    using <keycap>W</keycap>.  Exit the fdisk editor by
+	    pressing <keycap>Q</keycap> which will prompt about
+	    the <quote>Master Boot Record</quote>.  Since the disk is
+	    being added to an already running system, choose
 	    <literal>None</literal>.</para>
 	</step>
 
@@ -282,43 +274,43 @@
 
 	  <indexterm><primary>BSD partitions</primary></indexterm>
 
-	  <para>Next, you need to exit
-	    <application>sysinstall</application> and start it again.
-	    Follow the directions above, although this time choose the
-	    <literal>Label</literal> option.  This will enter the
-	    <literal>Disk Label Editor</literal>.  This is where you
-	    will create the traditional BSD partitions.  A disk can
-	    have up to eight partitions, labeled
+	  <para>Next, exit <application>sysinstall</application> and
+	    start it again.  Follow the directions above, except this
+	    time choose the <literal>Label</literal> option.  This
+	    will enter the <literal>Disk Label Editor</literal>.  This
+	    editor is used to create traditional BSD partitions.  A
+	    disk can have up to eight partitions, labeled
 	    <literal>a-h</literal>.  A few of the partition labels
 	    have special uses.  The <literal>a</literal> partition is
-	    used for the root partition (<filename>/</filename>).
-	    Thus only your system disk (e.g., the disk you boot from)
-	    should have an <literal>a</literal> partition.  The
-	    <literal>b</literal> partition is used for swap
-	    partitions, and you may have many disks with swap
+	    used for the root partition (<filename
+	      class="directory">/</filename>).  Only the disk the
+	    system boots from should have an <literal>a</literal>
+	    partition.  The <literal>b</literal> partition is used for
+	    swap partitions, and there can be many disks with swap
 	    partitions.  The <literal>c</literal> partition addresses
-	    the entire disk in dedicated mode, or the entire FreeBSD
+	    the entire disk in dedicated mode, or the entire &os;
 	    slice in slice mode.  The other partitions are for general
 	    use.</para>
 
-	  <para><application>sysinstall</application>'s Label editor
-	    favors the <literal>e</literal> partition for non-root,
-	    non-swap partitions.  Within the Label editor, create a
-	    single file system by pressing <keycap>C</keycap>.  When
-	    prompted if this will be a FS (file system) or swap,
-	    choose <literal>FS</literal> and type in a mount point
-	    (e.g., <filename>/mnt</filename>).  When adding a disk in
-	    post-install mode, <application>sysinstall</application>
-	    will not create entries in <filename>/etc/fstab</filename>
-	    for you, so the mount point you specify is not
-	    important.</para>
-
-	  <para>You are now ready to write the new label to the disk
-	    and create a file system on it.  Do this by pressing
-	    <keycap>W</keycap>.  Ignore any errors from
-	    <application>sysinstall</application> that it could not
-	    mount the new partition.  Exit the Label Editor and
-	    <application>sysinstall</application> completely.</para>
+	  <para>The label editor in
+	    <application>sysinstall</application> favors the
+	    <literal>e</literal> partition for non-root, non-swap
+	    partitions.  Within the label editor, create a single file
+	    system by pressing <keycap>C</keycap>.  When prompted if
+	    this will be a FS (file system) or swap, choose
+	    <literal>FS</literal> and type in a mount point such as
+	    <filename class="directory">/mnt</filename>).  When adding
+	    a disk in post-install mode,
+	    <application>sysinstall</application> will not create
+	    entries in <filename>/etc/fstab</filename>, so the mount
+	    point you specify is not important.</para>
+
+	  <para>Press <keycap>W</keycap> to write the new label to the
+	    disk and create a file system on it.  Ignore any errors
+	    from <application>sysinstall</application> indicating that
+	    it could not mount the new partition.  Exit the label
+	    editor then <application>sysinstall</application>
+	    completely.</para>
 	</step>
 
 	<step>
@@ -337,12 +329,12 @@
       <sect3>
 	<title>Using Slices</title>
 
-	<para>This setup will allow your disk to work correctly with
-	  other operating systems that might be installed on your
-	  computer and will not confuse other operating systems'
-	  <command>fdisk</command> utilities.  It is recommended
-	  to use this method for new disk installs.  Only use
-	  <literal>dedicated</literal> mode if you have a good reason
+	<para>The setup in the following example allows the new disk
+	  to work correctly with other operating systems that might be
+	  installed on the computer without confusing other operating
+	  systems' <command>fdisk</command> utilities.  This method is
+	  recommended for new disk installs.  Only use
+	  <literal>dedicated</literal> mode if there is a good reason
 	  to do so!</para>
 
 	<screen>&prompt.root; <userinput>dd if=/dev/zero of=/dev/da1 bs=1k count=1</userinput>
@@ -354,7 +346,7 @@
 &prompt.root; <userinput>mount /dev/da1s1e /1</userinput> # Mount the partition(s)
 &prompt.root; <userinput>vi /etc/fstab</userinput> # Add the appropriate entry/entries to your <filename>/etc/fstab</filename>.</screen>
 
-	<para>If you have an IDE disk, substitute
+	<para>For an IDE disk, substitute
 	  <filename>ad</filename> for <filename>da</filename>.</para>
       </sect3>
 
@@ -363,13 +355,11 @@
 
 	<indexterm><primary>OS/2</primary></indexterm>
 
-	<para>If you will not be sharing the new drive with another
-	  operating system, you may use the
-	  <literal>dedicated</literal> mode.  Remember this mode can
-	  confuse Microsoft operating systems; however, no damage will
-	  be done by them.  IBM's &os2; however, will
-	  <quote>appropriate</quote> any partition it finds which it
-	  does not understand.</para>
+	<para>If the new drive will not be shared with another
+	  operating system, <literal>dedicated</literal> mode can be
+	  used.  This mode can confuse Microsoft operating systems;
+	  however, no damage will be done by them.  To configure a
+	  disk in dedicated mode:</para>
 
 	<screen>&prompt.root; <userinput>dd if=/dev/zero of=/dev/da1 bs=1k count=1</userinput>
 &prompt.root; <userinput>bsdlabel -Bw da1 auto</userinput>
@@ -422,89 +412,78 @@
 	<indexterm><primary>RAID</primary><secondary>software</secondary></indexterm>
 	<indexterm><primary>RAID</primary><secondary>CCD</secondary></indexterm>
 
-	<para>When choosing a mass storage solution the most important
-	  factors to consider are speed, reliability, and cost.  It is
-	  rare to have all three in balance; normally a fast, reliable
-	  mass storage device is expensive, and to cut back on cost
-	  either speed or reliability must be sacrificed.</para>
+	<para>When choosing a mass storage solution, the most
+	  important factors to consider are speed, reliability, and
+	  cost.  It is rare to have all three in balance.  Normally a
+	  fast, reliable mass storage device is expensive, and to cut
+	  back on cost either speed or reliability must be
+	  sacrificed.</para>
 
 	<para>In designing the system described below, cost was
 	  chosen as the most important factor, followed by speed,
 	  then reliability.  Data transfer speed for this system is
-	  ultimately constrained by the network.  And while
-	  reliability is very important, the CCD drive described
-	  below serves online data that is already fully backed up
-	  on CD-R's and can easily be replaced.</para>
-
-	<para>Defining your own requirements is the first step in
-	  choosing a mass storage solution.  If your requirements
-	  prefer speed or reliability over cost, your solution will
-	  differ from the system described in this section.</para>
+	  ultimately constrained by the network.  While reliability is
+	  very important, the CCD drive described below serves online
+	  data that is already fully backed up and which can easily be
+	  replaced.</para>
+
+	<para>Defining the requirements is the first step in choosing
+	  a mass storage solution.  If the requirements prefer speed
+	  or reliability over cost, the solution will differ from the
+	  system described in this section.</para>
 
 	<sect4 id="ccd-installhw">
 	  <title>Installing the Hardware</title>
 
 	  <para>In addition to the IDE system disk, three Western
 	    Digital 30GB, 5400 RPM IDE disks form the core of the CCD
-	    disk described below providing approximately 90GB of
+	    disk described below, providing approximately 90GB of
 	    online storage.  Ideally, each IDE disk would have its own
 	    IDE controller and cable, but to minimize cost, additional
-	    IDE controllers were not used.  Instead the disks were
+	    IDE controllers were not used.  Instead, the disks were
 	    configured with jumpers so that each IDE controller has
 	    one master, and one slave.</para>
 
 	  <para>Upon reboot, the system BIOS was configured to
 	    automatically detect the disks attached.  More
-	    importantly, FreeBSD detected them on reboot:</para>
+	    importantly, &os; detected them on reboot:</para>
 
 	  <programlisting>ad0: 19574MB <WDC WD205BA> [39770/16/63] at ata0-master UDMA33
 ad1: 29333MB <WDC WD307AA> [59598/16/63] at ata0-slave UDMA33
 ad2: 29333MB <WDC WD307AA> [59598/16/63] at ata1-master UDMA33
 ad3: 29333MB <WDC WD307AA> [59598/16/63] at ata1-slave UDMA33</programlisting>
 
-	  <note><para>If FreeBSD does not detect all the disks, ensure
-	    that you have jumpered them correctly.  Most IDE drives
-	    also have a <quote>Cable Select</quote> jumper.  This is
-	    <emphasis>not</emphasis> the jumper for the master/slave
-	    relationship.  Consult the drive documentation for help in
-	    identifying the correct jumper.</para></note>
-
-	  <para>Next, consider how to attach them as part of the file
-	    system.  You should research both &man.vinum.4; (<xref
-	      linkend="vinum-vinum"/>) and &man.ccd.4;.  In this
-	    particular configuration, &man.ccd.4; was chosen.</para>
+	  <note><para>If &os; does not detect all the disks, consult
+	    the drive documentation for proper setup and verify
+	    that the controller is supported by &os;.</para></note>
 	</sect4>
 
 	<sect4 id="ccd-setup">
 	  <title>Setting Up the CCD</title>
 
-	  <para>The &man.ccd.4; driver allows you to take several
-	    identical disks and concatenate them into one logical file
-	    system.  In order to use &man.ccd.4;, you need a kernel
-	    with &man.ccd.4; support built in.  Add this line to your
-	    kernel configuration file, rebuild, and reinstall the
-	    kernel:</para>
+	  <para>The &man.ccd.4; driver takes several identical disks
+	    and concatenates them into one logical file system.  In
+	    order to use &man.ccd.4;, its kernel module must be
+	    loaded using &man.ccd.4;.  When using a custom kernel,
+	    ensure that this line is compiled in:</para>
 
 	  <programlisting>device   ccd</programlisting>
 
-	  <para>The &man.ccd.4; support can also be loaded as a kernel
-	    loadable module.</para>
-
-	  <para>To set up &man.ccd.4;, you must first use
-	    &man.bsdlabel.8; to label the disks:</para>
+	  <para>Before configuring &man.ccd.4;, use &man.bsdlabel.8;
+	    to label the disks:</para>
 
 	  <programlisting>bsdlabel -w ad1 auto
 bsdlabel -w ad2 auto
 bsdlabel -w ad3 auto</programlisting>
 
-	  <para>This creates a bsdlabel for
+	  <para>This example creates a bsdlabel for
 	    <devicename>ad1c</devicename>,
 	    <devicename>ad2c</devicename> and
 	    <devicename>ad3c</devicename> that spans the entire
 	    disk.</para>
 
-	  <para>The next step is to change the disk label type.  You
-	    can use &man.bsdlabel.8; to edit the disks:</para>
+	  <para>The next step is to change the disk label type.  Use
+	    &man.bsdlabel.8; to edit the disks:</para>
 
 	  <programlisting>bsdlabel -e ad1
 bsdlabel -e ad2
@@ -537,46 +516,46 @@ bsdlabel -e ad3</programlisting>
 	<sect4 id="ccd-buildingfs">
 	  <title>Building the File System</title>
 
-	  <para>Now that you have all the disks labeled, you must
-	    build the &man.ccd.4;.  To do that, use &man.ccdconfig.8;,
-	    with options similar to the following:</para>
+	  <para>Now that all the disks are labeled, build the
+	    &man.ccd.4; using &man.ccdconfig.8;, with options similar
+	    to the following:</para>
 
 	  <programlisting>ccdconfig ccd0<co id="co-ccd-dev"/> 32<co id="co-ccd-interleave"/> 0<co id="co-ccd-flags"/> /dev/ad1e<co id="co-ccd-devs"/> /dev/ad2e /dev/ad3e</programlisting>
 
-	  <para>The use and meaning of each option is shown
+	  <para>The use and meaning of each option is described
 	    below:</para>
 
 	  <calloutlist>
 	    <callout arearefs="co-ccd-dev">
 	      <para>The first argument is the device to configure, in
 		this case, <filename>/dev/ccd0c</filename>.  The
-		<filename>/dev/</filename> portion is optional.</para>
+		<literal>/dev/</literal> portion is optional.</para>
 	    </callout>
 
 	    <callout arearefs="co-ccd-interleave">
-	      <para>The interleave for the file system.  The
-		interleave defines the size of a stripe in disk
-		blocks, each normally 512 bytes.  So, an interleave of
-		32 would be 16,384 bytes.</para>
+	      <para>The interleave for the file system, which defines
+		the size of a stripe in disk blocks, each normally 512
+		bytes.  So, an interleave of 32 would be 16,384
+		bytes.</para>
 	    </callout>
 
 	    <callout arearefs="co-ccd-flags">
-	      <para>Flags for &man.ccdconfig.8;.  If you want to
-		enable drive mirroring, you can specify a flag here.
-		This configuration does not provide mirroring for
+	      <para>Flags for &man.ccdconfig.8;.  For example, to
+		enable drive mirroring, specify a flag.  This
+		configuration does not provide mirroring for
 		&man.ccd.4;, so it is set at 0 (zero).</para>
 	    </callout>
 
 	    <callout arearefs="co-ccd-devs">
 	      <para>The final arguments to &man.ccdconfig.8; are the
 		devices to place into the array.  Use the complete
-		pathname for each device.</para>
+		path name for each device.</para>
 	    </callout>
 	  </calloutlist>
 
 	  <para>After running &man.ccdconfig.8; the &man.ccd.4; is
-	    configured.  A file system can be installed.  Refer to
-	    &man.newfs.8; for options, or simply run: </para>
+	    configured and a file system can be installed.  Refer to
+	    &man.newfs.8; for options, or run: </para>
 
 	  <programlisting>newfs /dev/ccd0c</programlisting>
 	</sect4>
@@ -584,9 +563,9 @@ bsdlabel -e ad3</programlisting>
 	<sect4 id="ccd-auto">
 	  <title>Making it All Automatic</title>
 
-	  <para>Generally, you will want to mount the &man.ccd.4; upon
-	    each reboot.  To do this, you must configure it first.
-	    Write out your current configuration to
+	  <para>Generally, &man.ccd.4; should be configured to
+	    automount upon each reboot.  To do this, write out the
+	    current configuration to
 	    <filename>/etc/ccd.conf</filename> using the following
 	    command:</para>
 
@@ -599,9 +578,9 @@ bsdlabel -e ad3</programlisting>
 	    mounted.</para>
 
 	  <note>
-	    <para>If you are booting into single user mode, before you
-	      can &man.mount.8; the &man.ccd.4;, you need to issue the
-	      following command to configure the array:</para>
+	    <para>When booting into single user mode, the following
+	      command must be issued to configure the array before
+	      the &man.ccd.4; can be mounted:</para>
 
 	    <programlisting>ccdconfig -C</programlisting>
 	  </note>
@@ -634,7 +613,7 @@ bsdlabel -e ad3</programlisting>
 	  storage.  &man.vinum.4; implements the RAID-0, RAID-1 and
 	  RAID-5 models, both individually and in combination.</para>
 
-	<para>See <xref linkend="vinum-vinum"/> for more
+	<para>Refer to <link linkend="vinum-vinum"></link> for more
 	  information about &man.vinum.4;.</para>
       </sect3>
     </sect2>
@@ -647,32 +626,31 @@ bsdlabel -e ad3</programlisting>
 	<secondary>hardware</secondary>
       </indexterm>
 
-      <para>FreeBSD also supports a variety of hardware
+      <para>&os; also supports a variety of hardware
 	<acronym>RAID</acronym> controllers.  These devices control a
-	<acronym>RAID</acronym> subsystem without the need for FreeBSD
+	<acronym>RAID</acronym> subsystem without the need for &os;
 	specific software to manage the array.</para>
 
       <para>Using an on-card <acronym>BIOS</acronym>, the card
-	controls most of the disk operations itself.  The following is
-	a brief setup description using a Promise
+	controls most of the disk operations.  The following is a
+	brief setup description using a Promise
 	<acronym>IDE</acronym> <acronym>RAID</acronym> controller.
 	When this card is installed and the system is started up, it
 	displays a prompt requesting information.  Follow the
-	instructions to enter the card's setup screen.  From here, you
-	have the ability to combine all the attached drives.  After
-	doing so, the disk(s) will look like a single drive to
-	FreeBSD.  Other <acronym>RAID</acronym> levels can be set up
+	instructions to enter the card's setup screen and to combine
+	all the attached drives.  After doing so, the disks will
+	look like a single drive to &os;.  Other
+	<acronym>RAID</acronym> levels can be set up
 	accordingly.</para>
     </sect2>
 
     <sect2>
       <title>Rebuilding ATA RAID1 Arrays</title>
 
-      <para>FreeBSD allows you to hot-replace a failed disk in an
-	array.  This requires that you catch it before you
-	reboot.</para>
+      <para>&os; supports the ability to hot-replace a failed disk in
+	an array.</para>
 
-      <para>You will probably see something like the following in
+      <para>An error indicating a failed disk will appear in
 	<filename>/var/log/messages</filename> or in the &man.dmesg.8;
 	output:</para>
 
@@ -684,7 +662,7 @@ ad6: hard error reading fsbn 1116119 of 
 status=59 error=40
 ar0: WARNING - mirror lost</programlisting>
 
-      <para>Using &man.atacontrol.8;, check for further
+      <para>Use &man.atacontrol.8; to check for further
 	information:</para>
 
       <screen>&prompt.root; <userinput>atacontrol list</userinput>
@@ -709,8 +687,8 @@ ar0: ATA RAID1 subdisks: ad4 ad6 status:
 
       <procedure>
 	<step>
-	  <para>You will first need to detach the ata channel with the
-	    failed disk so you can safely remove it:</para>
+	  <para>First, detach the ata channel with the failed disk
+	    so that it can be safely removed:</para>
 
 	  <screen>&prompt.root; <userinput>atacontrol detach ata3</userinput></screen>
 	</step>
@@ -779,19 +757,18 @@ ar0: ATA RAID1 subdisks: ad4 ad6 status:
       <secondary>disks</secondary>
     </indexterm>
 
-    <para>A lot of external storage solutions, nowadays, use the
-      Universal Serial Bus (USB): hard drives, USB thumbdrives, CD-R
-      burners, etc.  &os; provides support for these devices.</para>
+    <para>Many external storage solutions, such as hard drives, USB
+      thumbdrives, and CD/DVD burners, use the Universal Serial Bus
+      (USB).  &os; provides support for these devices.</para>
 
     <sect2>
       <title>Configuration</title>
 
       <para>The USB mass storage devices driver, &man.umass.4;,
-	provides the support for USB storage devices.  If you use the
-	<filename>GENERIC</filename> kernel, you do not have to change
-	anything in your configuration.  If you use a custom kernel,
-	be sure that the following lines are present in your kernel
-	configuration file:</para>
+	is built into the <filename>GENERIC</filename> kernel
+	and provides support for USB storage devices.  For a custom
+	kernel, be sure that the following lines are present in the
+	kernel configuration file:</para>
 
       <programlisting>device scbus
 device da
@@ -802,21 +779,17 @@ device ehci
 device usb
 device umass</programlisting>
 
-      <para>The &man.umass.4; driver uses the SCSI subsystem to access
-	to the USB storage devices, your USB device will be seen as a
-	SCSI device by the system.  Depending on the USB chipset on
-	your motherboard, you only need either <literal>device
-	  uhci</literal> or <literal>device ohci</literal> for USB 1.X
-	support, however having both in the kernel configuration file
-	is harmless.  Support for USB 2.0 controllers is provided by
-	the &man.ehci.4; driver (the <literal>device ehci</literal>
-	line).  Do not forget to compile and install the new kernel if
-	you added any lines.</para>
+      <para>Since the &man.umass.4; driver uses the SCSI subsystem to
+	access the USB storage devices, any USB device will be seen as
+	a SCSI device by the system.  Depending on the USB chipset on
+	the motherboard, <literal>device uhci</literal> or
+	<literal>device ohci</literal> is used to provide USB 1.X
+	support.  Support for USB 2.0 controllers is provided by
+	<literal>device ehci</literal>.</para>
 
       <note>
-	<para>If your USB device is a CD-R or DVD burner, the SCSI
-	  CD-ROM driver, &man.cd.4;, must be added to the kernel via
-	  the line:</para>
+	<para>If the USB device is a CD or DVD burner, &man.cd.4;,
+	  must be added to the kernel via the line:</para>
 
 	<programlisting>device cd</programlisting>
 
@@ -829,9 +802,9 @@ device umass</programlisting>
     <sect2>
       <title>Testing the Configuration</title>
 
-      <para>The configuration is ready to be tested: plug in your USB
-	device, and in the system message buffer (&man.dmesg.8;), the
-	drive should appear as something like:</para>
+      <para>To test the USB configuration, plug in the USB device.  In
+	the system message buffer, &man.dmesg.8;, the drive should
+	appear as something like:</para>
 
       <screen>umass0: USB Solid state disk, rev 1.10/1.00, addr 2
 GEOM: create disk da0 dp=0xc2d74850
@@ -840,97 +813,91 @@ da0: <Generic Traveling Disk 1.11>
 da0: 1.000MB/s transfers
 da0: 126MB (258048 512 byte sectors: 64H 32S/T 126C)</screen>
 
-      <para>Of course, the brand, the device node
-	(<devicename>da0</devicename>) and other details can differ
-	according to your configuration.</para>
-
-      <para>Since the USB device is seen as a SCSI one, the
-	<command>camcontrol</command> command can be used to list the
-	USB storage devices attached to the system:</para>
+      <para>The brand, device node (<devicename>da0</devicename>), and
+	other details will differ according to the device.</para>
+
+      <para>Since the USB device is seen as a SCSI one,
+	<command>camcontrol</command> can be used to list the USB
+	storage devices attached to the system:</para>
 
       <screen>&prompt.root; <userinput>camcontrol devlist</userinput>
 <Generic Traveling Disk 1.11>      at scbus0 target 0 lun 0 (da0,pass0)</screen>
 
-      <para>If the drive comes with a file system, you should be able
-	to mount it.  The <xref linkend="disks-adding"/> will help you
-	to format and create partitions on the USB drive if
-	needed.</para>
+      <para>If the drive comes with a file system, it can be mounted.
+	Refer to <link linkend="disks-adding"></link> for
+	instructions on how to format and create partitions on the USB
+	drive.</para>
 
       <warning>
-	<para>Allowing untrusted users to mount arbitrary media,
-	  e.g., by enabling <literal>vfs.usermount</literal> as
+	<para>Allowing untrusted users to mount arbitrary media, by
+	  enabling <varname>vfs.usermount</varname> as
 	  described below, should not be considered safe from a
 	  security point of view.  Most file systems in &os; were not
 	  built to safeguard against malicious devices.</para>
       </warning>
 
-      <para>To make this device mountable as a normal user, certain
-	steps have to be taken.  First, the devices that are created
-	when a USB storage device is connected need to be accessible
-	by the user.  A solution is to make all users of these devices
-	a member of the <groupname>operator</groupname> group.  This
-	is done with &man.pw.8;.  Second, when the devices are
-	created, the <groupname>operator</groupname> group should be
-	able to read and write them.  This is accomplished by adding
-	these lines to
+      <para>To make the device mountable as a normal user, one
+	solution is to make all users of the device a member of the
+	<groupname>operator</groupname> group using &man.pw.8;.
+	Next, ensure that the <groupname>operator</groupname> group is
+	able to read and write the device by adding these lines to
 	<filename>/etc/devfs.rules</filename>:</para>
 
       <programlisting>[localrules=5]
 add path 'da*' mode 0660 group operator</programlisting>
 
       <note>
-	<para>If there already are SCSI disks in the system, it must
-	  be done a bit different.  E.g., if the system already
-	  contains disks <devicename>da0</devicename> through
-	  <devicename>da2</devicename> attached to the system, change
+	<para>If SCSI disks are installed in the system, change
 	  the second line as follows:</para>
 
 	<programlisting>add path 'da[3-9]*' mode 0660 group operator</programlisting>
 
-	<para>This will exclude the already existing disks from
-	  belonging to the <groupname>operator</groupname>
-	  group.</para>
+	<para>This will exclude the first three SCSI disks
+	  (<devicename>da0</devicename> to
+	  <devicename>da2</devicename>)from belonging to the
+	  <groupname>operator</groupname> group.</para>
       </note>
 
-      <para>You also have to enable your &man.devfs.rules.5; ruleset
-	in your <filename>/etc/rc.conf</filename> file:</para>
+      <para>Next, enable the &man.devfs.rules.5; ruleset in
+	<filename>/etc/rc.conf</filename>:</para>
 
       <programlisting>devfs_system_ruleset="localrules"</programlisting>
 
-      <para>Next, the kernel has to be configured to allow regular
-	users to mount file systems.  The easiest way is to add the
+      <para>Next, instruct the running kernel to allow regular users
+	to mount file systems.  The easiest way is to add the
 	following line to
 	<filename>/etc/sysctl.conf</filename>:</para>
 
       <programlisting>vfs.usermount=1</programlisting>
 
-      <para>Note that this only takes effect after the next reboot.
-	Alternatively, one can also use &man.sysctl.8; to set this
-	variable.</para>
+      <para>Since this only takes effect after the next reboot use
+	&man.sysctl.8; to set this variable now.</para>
 
       <para>The final step is to create a directory where the file
 	system is to be mounted.  This directory needs to be owned by
 	the user that is to mount the file system.  One way to do that
 	is for <username>root</username> to create a subdirectory
-	owned by that user as
-	<filename>/mnt/<replaceable>username</replaceable></filename>
-	(replace <replaceable>username</replaceable> by the login name
-	of the actual user and <replaceable>usergroup</replaceable> by
-	the user's primary group):</para>
+	owned by that user as <filename
+	class="directory">/mnt/<replaceable>username</replaceable></filename>.
+	In the following example, replace
+	<replaceable>username</replaceable> with the login name of the
+	user and <replaceable>usergroup</replaceable> with the user's
+	primary group:</para>
 
       <screen>&prompt.root; <userinput>mkdir /mnt/<replaceable>username</replaceable></userinput>
 &prompt.root; <userinput>chown <replaceable>username</replaceable>:<replaceable>usergroup</replaceable> /mnt/<replaceable>username</replaceable></userinput></screen>
 
       <para>Suppose a USB thumbdrive is plugged in, and a device
-	<filename>/dev/da0s1</filename> appears.  Since these devices
-	usually come preformatted with a FAT file system, one can
-	mount them like this:</para>
+	<filename>/dev/da0s1</filename> appears.  If the device is
+	preformatted with a FAT file system, it can be mounted
+	using:</para>
 
       <screen>&prompt.user; <userinput>mount -t msdosfs -o -m=644,-M=755 /dev/da0s1 /mnt/<replaceable>username</replaceable></userinput></screen>
 
-      <para>If you unplug the device (the disk must be unmounted
-	before), you should see, in the system message buffer,
-	something like the following:</para>
+      <para>Before the device can be unplugged, it
+	<emphasis>must</emphasis> be unmounted first.  After device
+	removal, the system message buffer will show messages similar
+	to the following:</para>
 
       <screen>umass0: at uhub0 port 1 (addr 2) disconnected
 (da0:umass-sim0:0:0:0): lost device
@@ -964,7 +931,7 @@ umass0: detached</screen>
       <!-- Apr 2001 -->
     </sect1info>
 
-    <title>Creating and Using Optical Media (CDs)</title>
+    <title>Creating and Using CD Media</title>
 
     <indexterm>
       <primary>CDROMs</primary>
@@ -974,18 +941,18 @@ umass0: detached</screen>
     <sect2>
       <title>Introduction</title>
 
-      <para>CDs have a number of features that differentiate them from
-	conventional disks.  Initially, they were not 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 systems than similarly sized
-	media were at the time.</para>
-
-      <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>
+      <para>CD media provide a number of features that differentiate
+	them from conventional disks.  Initially, they were not
+	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
+	systems.</para>
+
+      <para>CD media do have tracks, but this refers to a section of
+	data to be read continuously and not a physical property of
+	the disk.  For example, to produce a CD on &os;, prepare the
+	data files that are going to make up the tracks on the CD,
+	then write the tracks to the CD.</para>
 
       <indexterm><primary>ISO 9660</primary></indexterm>
       <indexterm>
@@ -994,11 +961,10 @@ umass0: detached</screen>
       </indexterm>
 
       <para>The ISO 9660 file system was designed to deal with these
-	differences.  It unfortunately codifies file system limits
-	that were common then.  Fortunately, it provides an extension
-	mechanism that allows properly written CDs to exceed those
-	limits while still working with systems that do not support
-	those extensions.</para>
+	differences.  To overcome the original file system limits, it
+	provides an extension mechanism that allows properly written
+	CDs to exceed those limits while still working with systems
+	that do not support those extensions.</para>
 
       <indexterm>
 	<primary><filename
@@ -1006,31 +972,30 @@ umass0: detached</screen>
       </indexterm>
 
       <para>The <filename role="package">sysutils/cdrtools</filename>
-	port includes &man.mkisofs.8;, a program that you can use to
-	produce a data file containing an ISO 9660 file
-	system.  It has options that support various extensions, and
-	is described below.</para>
+	port includes &man.mkisofs.8;, a program that can be used to
+	produce a data file containing an ISO 9660 file system.  It
+	has options that support various extensions, and is described
+	below.</para>
 
       <indexterm>
 	<primary>CD burner</primary>
 	<secondary>ATAPI</secondary>
       </indexterm>
 
-      <para>Which tool to use to burn the CD depends on whether your
+      <para>Which tool to use to burn the CD depends on whether the
 	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
-	<command><link linkend="cdrecord">cdrecord</link></command>
-	from the <filename role="package">sysutils/cdrtools</filename>
-	port.  It is also possible to use
-	<command><link linkend="cdrecord">cdrecord</link></command>
-	and other tools for SCSI drives on ATAPI hardware with the
-	<link linkend="atapicam">ATAPI/CAM module</link>.</para>
-
-      <para>If you want CD burning software with a graphical user
-	interface, you may wish to take a look at either
-	<application>X-CD-Roast</application> or
+	<command><link linkend="burncd">burncd</link></command>
+	which is part of the base system.  SCSI and USB CD burners
+	should use <command><link
+	  linkend="cdrecord">cdrecord</link></command> from the
+	<filename role="package">sysutils/cdrtools</filename> port.
+	It is also possible to use <command><link
+	  linkend="cdrecord">cdrecord</link></command> and other tools
+	for SCSI drives on ATAPI hardware with the <link
+	  linkend="atapicam">ATAPI/CAM module</link>.</para>
+
+      <para>For CD burning software with a graphical user
+	interface, consider <application>X-CD-Roast</application> or
 	<application>K3b</application>.  These tools are available as
 	packages or from the
 	<filename role="package">sysutils/xcdroast</filename> and
@@ -1044,11 +1009,10 @@ umass0: detached</screen>
     <sect2 id="mkisofs">
       <title><application>mkisofs</application></title>
 
-      <para>The &man.mkisofs.8; program, which is part of the
-	<filename role="package">sysutils/cdrtools</filename> port,
-	produces an ISO 9660 file system that is an image of a
-	directory tree in the &unix; file system name space.  The
-	simplest usage is:</para>
+      <para>The <filename role="package">sysutils/cdrtools</filename>
+	port also installs &man.mkisofs.8;, which produces an ISO 9660
+	file system that is an image of a directory tree in the &unix;
+	file system name space.  The simplest usage is:</para>
 
       <screen>&prompt.root; <userinput>mkisofs -o <replaceable>imagefile.iso</replaceable> <replaceable>/path/to/tree</replaceable></userinput></screen>
 
@@ -1057,11 +1021,11 @@ umass0: detached</screen>
 	<secondary>ISO 9660</secondary>
       </indexterm>
 
-      <para>This command will create an
+      <para>This command creates an
 	<replaceable>imagefile.iso</replaceable> containing an ISO
 	9660 file system that is a copy of the tree at
 	<replaceable>/path/to/tree</replaceable>.  In the process, it
-	will map the file names to names that fit the limitations of
+	maps the file names to names that fit the limitations of
 	the standard ISO 9660 file system, and will exclude files that
 	have names uncharacteristic of ISO file systems.</para>
 
@@ -1073,19 +1037,19 @@ umass0: detached</screen>
 	<primary>file systems</primary>
 	<secondary>Joliet</secondary>
       </indexterm>
-      <para>A number of options are available to overcome those
+      <para>A number of options are available to overcome these
 	restrictions.  In particular, <option>-R</option> enables the
 	Rock Ridge extensions common to &unix; systems,
 	<option>-J</option> enables Joliet extensions used by
 	Microsoft systems, and <option>-hfs</option> can be used to
 	create HFS file systems used by &macos;.</para>
 
-      <para>For CDs that are going to be used only on FreeBSD systems,
+      <para>For CDs that are going to be used only on &os; systems,
 	<option>-U</option> can be used to disable all filename
 	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>
+	a file system image that is identical to the specified &os;
+	tree, though it may violate the ISO 9660 standard in a number
+	of ways.</para>
 
       <indexterm>
 	<primary>CDROMs</primary>
@@ -1096,36 +1060,35 @@ umass0: detached</screen>
 	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 tree being written to the CD.  By default,
-	&man.mkisofs.8; creates an ISO image in the so-called
-	<quote>floppy disk emulation</quote> mode, and thus expects
-	the boot image to be exactly 1200, 1440 or 2880 KB in
-	size.  Some boot loaders, like the one used by the FreeBSD
-	distribution disks, do not use emulation mode; in this case,
-	the <option>-no-emul-boot</option> option should be used.  So,
-	if <filename>/tmp/myboot</filename> holds a bootable FreeBSD
-	system with the boot image in
-	<filename>/tmp/myboot/boot/cdboot</filename>, you could
-	produce the image of an ISO 9660 file system in
-	<filename>/tmp/bootable.iso</filename> like so:</para>
+	&man.mkisofs.8; creates an ISO image in <quote>floppy disk
+	  emulation</quote> mode, and thus expects the boot image to
+	be exactly 1200, 1440 or 2880 KB in size.  Some boot
+	loaders, like the one used by the &os; distribution disks, do
+	not use emulation mode.  In this case,
+	<option>-no-emul-boot</option> should be used.  So, if
+	<filename class="directory">/tmp/myboot</filename> holds a
+	bootable &os; system with the boot image in <filename
+	  class="directory">/tmp/myboot/boot/cdboot</filename>, this
+	command would produce the image of an ISO 9660 file system as
+	<filename>/tmp/bootable.iso</filename>:</para>
 
       <screen>&prompt.root; <userinput>mkisofs -R -no-emul-boot -b boot/cdboot -o /tmp/bootable.iso /tmp/myboot</userinput></screen>

*** DIFF OUTPUT TRUNCATED AT 1000 LINES ***


More information about the svn-doc-all mailing list