PERFORCE change 205673 for review
Rene Ladan
rene at FreeBSD.org
Sat Feb 4 10:02:48 UTC 2012
http://p4web.freebsd.org/@@205673?ac=10
Change 205673 by rene at rene_acer on 2012/02/04 10:01:41
IFC
Affected files ...
.. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.committers.sgml#74 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/desktop/chapter.sgml#32 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/disks/chapter.sgml#23 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/filesystems/chapter.sgml#9 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml#32 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/books/porters-handbook/book.sgml#127 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/share/sgml/authors.ent#67 integrate
.. //depot/projects/docproj_nl/share/pgpkeys/davide.key#1 branch
.. //depot/projects/docproj_nl/share/pgpkeys/pgpkeys-developers.sgml#68 integrate
.. //depot/projects/docproj_nl/share/pgpkeys/pgpkeys.ent#65 integrate
Differences ...
==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.committers.sgml#74 (text+ko) ====
@@ -1,4 +1,4 @@
-<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/contributors/contrib.committers.sgml,v 1.347 2011/12/19 21:01:20 jgh Exp $ -->
+<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/contributors/contrib.committers.sgml,v 1.348 2012/01/31 22:54:32 davide Exp $ -->
<!--
NOTE TO NEW COMMITTERS: Core and committers lists are sorted in
alphabetical order by last name. Please keep in mind that fact while
@@ -554,6 +554,10 @@
<para>&a.chinsan;</para>
</listitem>
+ <listitem>
+ <para>&a.davide;</para>
+ </listitem>
+
<listitem>
<para>&a.iwasaki;</para>
</listitem>
==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/desktop/chapter.sgml#32 (text+ko) ====
@@ -1,6 +1,6 @@
<!--
The FreeBSD Documentation Project
- $FreeBSD: doc/en_US.ISO8859-1/books/handbook/desktop/chapter.sgml,v 1.120 2011/12/22 13:14:00 ryusuke Exp $
+ $FreeBSD: doc/en_US.ISO8859-1/books/handbook/desktop/chapter.sgml,v 1.121 2012/02/03 22:45:15 ryusuke Exp $
-->
<chapter id="desktop">
@@ -189,7 +189,7 @@
<screen>&prompt.root; <userinput>pkg_add -r firefox</userinput></screen>
- <para>This will install <application>Firefox</application> 9.0,
+ <para>This will install <application>Firefox</application> 10.0,
if you want to run <application>Firefox</application> 3.6,
use instead:</para>
==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/disks/chapter.sgml#23 (text+ko) ====
@@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
- $FreeBSD: doc/en_US.ISO8859-1/books/handbook/disks/chapter.sgml,v 1.310 2011/12/05 23:46:43 wblock Exp $
+ $FreeBSD: doc/en_US.ISO8859-1/books/handbook/disks/chapter.sgml,v 1.312 2012/02/03 02:14:27 wblock Exp $
-->
<chapter id="disks">
@@ -10,44 +10,62 @@
<sect1 id="disks-synopsis">
<title>Synopsis</title>
-
<para>This chapter covers the use of disks in FreeBSD. This
includes memory-backed disks, network-attached disks,
standard SCSI/IDE storage devices, and devices using the USB
interface.</para>
<para>After reading this chapter, you will know:</para>
+
<itemizedlist>
- <listitem><para>The terminology FreeBSD uses to describe the
- organization of data on a physical disk (partitions and slices).</para>
+ <listitem>
+ <para>The terminology FreeBSD uses to describe the
+ organization of data on a physical disk (partitions and
+ slices).</para>
</listitem>
- <listitem><para>How to add additional hard disks to your system.</para>
+
+ <listitem>
+ <para>How to add additional hard disks to your system.</para>
</listitem>
+
<listitem>
<para>How to configure &os; to use USB storage devices.</para>
</listitem>
- <listitem><para>How to set up virtual file systems, such as memory
- disks.</para></listitem>
+
+ <listitem>
+ <para>How to set up virtual file systems, such as memory
+ disks.</para>
+ </listitem>
+
<listitem>
<para>How to use quotas to limit disk space usage.</para>
</listitem>
+
<listitem>
- <para>How to encrypt disks to secure them against attackers.</para>
+ <para>How to encrypt disks to secure them against
+ attackers.</para>
</listitem>
+
<listitem>
<para>How to create and burn CDs and DVDs on FreeBSD.</para>
</listitem>
+
<listitem>
- <para>The various storage media options for backups.</para>
+ <para>The various storage media options for backups.</para>
</listitem>
+
<listitem>
- <para>How to use backup programs available under FreeBSD.</para>
+ <para>How to use backup programs available under
+ FreeBSD.</para>
</listitem>
+
<listitem>
- <para>How to backup to floppy disks.</para>
+ <para>How to backup to floppy disks.</para>
</listitem>
+
<listitem>
- <para>What file system snapshots are and how to use them efficiently.</para>
+ <para>What file system snapshots are and how to use them
+ efficiently.</para>
</listitem>
</itemizedlist>
@@ -55,11 +73,10 @@
<itemizedlist>
<listitem>
- <para>Know how to configure and install a new FreeBSD kernel
- (<xref linkend="kernelconfig">).</para>
+ <para>Know how to configure and install a new FreeBSD kernel
+ (<xref linkend="kernelconfig">).</para>
</listitem>
</itemizedlist>
-
</sect1>
<sect1 id="disks-naming">
@@ -79,45 +96,56 @@
<entry>Drive device name</entry>
</row>
</thead>
+
<tbody>
<row>
<entry>IDE hard drives</entry>
<entry><literal>ad</literal></entry>
</row>
+
<row>
<entry>IDE CDROM drives</entry>
<entry><literal>acd</literal></entry>
</row>
+
<row>
- <entry>SCSI hard drives and USB Mass storage devices</entry>
+ <entry>SCSI hard drives and USB Mass storage
+ devices</entry>
<entry><literal>da</literal></entry>
</row>
+
<row>
<entry>SCSI CDROM drives</entry>
<entry><literal>cd</literal></entry>
</row>
+
<row>
<entry>Assorted non-standard CDROM drives</entry>
<entry><literal>mcd</literal> for Mitsumi CD-ROM and
- <literal>scd</literal> for Sony CD-ROM devices
- </entry>
+ <literal>scd</literal> for Sony CD-ROM devices</entry>
</row>
+
<row>
<entry>Floppy drives</entry>
<entry><literal>fd</literal></entry>
</row>
+
<row>
<entry>SCSI tape drives</entry>
<entry><literal>sa</literal></entry>
- </row>
+ </row>
+
<row>
<entry>IDE tape drives</entry>
<entry><literal>ast</literal></entry>
</row>
+
<row>
<entry>Flash drives</entry>
- <entry><literal>fla</literal> for &diskonchip; Flash device</entry>
+ <entry><literal>fla</literal> for &diskonchip; Flash
+ device</entry>
</row>
+
<row>
<entry>RAID drives</entry>
<entry><literal>aacd</literal> for &adaptec; AdvancedRAID,
@@ -152,19 +180,20 @@
</indexterm>
<para>The following section will describe 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>
+ <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>
+ <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>
<indexterm><primary>partitions</primary></indexterm>
<indexterm><primary>slices</primary></indexterm>
@@ -172,19 +201,20 @@
<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 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
+ <para>FreeBSD runs on IBM-PC compatible computers, therefore it
+ must take into account the PC BIOS partitions. These 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>
+ This is a good way to avoid confusing the
+ <command>fdisk</command> utility of other, non-FreeBSD operating
+ systems.</para>
<para>In the slice case the drive will be added as
<filename>/dev/da1s1e</filename>. This is read as: SCSI disk,
@@ -193,50 +223,55 @@
case, the drive will be added simply 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 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 <acronym>GPT</acronym> partitions. <acronym>GPT</acronym>
- has the added benefit of not being limited to 4 slices.</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
+ 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
+ <acronym>GPT</acronym> partitions. <acronym>GPT</acronym> has
+ the added benefit of not being limited to 4 slices.</para>
<sect2>
<title>Using &man.sysinstall.8;</title>
<indexterm>
- <primary><application>sysinstall</application></primary>
- <secondary>adding disks</secondary>
+ <primary><application>sysinstall</application></primary>
+ <secondary>adding disks</secondary>
</indexterm>
<indexterm>
<primary>su</primary>
</indexterm>
+
<procedure>
<step>
- <title>Navigating <application>Sysinstall</application></title>
+ <title>Navigating
+ <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
+ <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
<command>sysinstall</command> and enter the
<literal>Configure</literal> menu. Within the
- <literal>FreeBSD Configuration Menu</literal>, scroll down and
- select the <literal>Fdisk</literal> option.</para>
+ <literal>FreeBSD Configuration Menu</literal>, scroll down
+ and select the <literal>Fdisk</literal> option.</para>
</step>
<step>
- <title><application>fdisk</application> Partition 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 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
+ <title><application>fdisk</application> Partition
+ 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
+ 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
<literal>None</literal>.</para>
</step>
@@ -244,48 +279,51 @@
<title>Disk Label Editor</title>
<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
- <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
- partitions. The <literal>c</literal> partition addresses the
- entire disk in dedicated mode, or the entire FreeBSD slice in
- slice mode. The other partitions are for general use.</para>
+ <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
+ <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
+ partitions. The <literal>c</literal> partition addresses
+ the entire disk in dedicated mode, or the entire FreeBSD
+ 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>
+ 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
+ <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>
+ <application>sysinstall</application> that it could not
+ mount the new partition. Exit the Label Editor and
+ <application>sysinstall</application> completely.</para>
</step>
<step>
<title>Finish</title>
- <para>The last step is to edit <filename>/etc/fstab</filename>
- to add an entry for your new disk.</para>
+ <para>The last step is to edit
+ <filename>/etc/fstab</filename> to add an entry for your
+ new disk.</para>
</step>
</procedure>
</sect2>
@@ -313,20 +351,21 @@
&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 <filename>ad</filename>
- for <filename>da</filename>.</para>
+ <para>If you have an IDE disk, substitute
+ <filename>ad</filename> for <filename>da</filename>.</para>
</sect3>
<sect3>
<title>Dedicated</title>
<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 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>
<screen>&prompt.root; <userinput>dd if=/dev/zero of=/dev/da1 bs=1k count=1</userinput>
&prompt.root; <userinput>bsdlabel -Bw da1 auto</userinput>
@@ -364,6 +403,7 @@
<contrib>Original work by </contrib>
</author>
</authorgroup>
+
<authorgroup>
<author>
<firstname>Jim</firstname>
@@ -373,103 +413,102 @@
</authorgroup>
</sect3info>
-<indexterm><primary>RAID</primary><secondary>software</secondary></indexterm>
-<indexterm>
- <primary>RAID</primary><secondary>CCD</secondary>
-</indexterm>
+ <indexterm><primary>RAID</primary><secondary>software</secondary></indexterm>
+ <indexterm><primary>RAID</primary><secondary>CCD</secondary></indexterm>
<title>Concatenated Disk Driver (CCD) Configuration</title>
+
<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>
+ 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>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>
-
+ <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>
<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 online storage. Ideally,
- each IDE disk would have its own IDE controller
- and cable, but to minimize cost, additional
+ Digital 30GB, 5400 RPM IDE disks form the core of the CCD
+ 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
configured with jumpers so that each IDE controller has
- one master, and one slave.</para>
+ 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>
+ automatically detect the disks attached. More
+ importantly, FreeBSD 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>
+ <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>
+ <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>
</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 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>
<programlisting>device ccd</programlisting>
- <para>The &man.ccd.4; support can also be
- loaded as a kernel loadable module.</para>
+ <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>To set up &man.ccd.4;, you must first 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 <devicename>ad1c</devicename>, <devicename>ad2c</devicename> and <devicename>ad3c</devicename> that
- spans the entire disk.</para>
+ <para>This 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. You
+ can use &man.bsdlabel.8; to edit the disks:</para>
<programlisting>bsdlabel -e ad1
bsdlabel -e ad2
bsdlabel -e ad3</programlisting>
- <para>This opens up the current disk label on each disk with
- the editor specified by the <envar>EDITOR</envar>
- environment variable, typically &man.vi.1;.</para>
+ <para>This opens up the current disk label on each disk with
+ the editor specified by the <envar>EDITOR</envar>
+ environment variable, typically &man.vi.1;.</para>
<para>An unmodified disk label will look something like
this:</para>
@@ -478,95 +517,94 @@
# size offset fstype [fsize bsize bps/cpg]
c: 60074784 0 unused 0 0 0 # (Cyl. 0 - 59597)</programlisting>
- <para>Add a new <literal>e</literal> partition for &man.ccd.4; to use. This
- can usually be copied from the <literal>c</literal> partition,
- but the <option>fstype</option> <emphasis>must</emphasis>
- be <userinput>4.2BSD</userinput>. The disk label should
- now look something like this:</para>
+ <para>Add a new <literal>e</literal> partition for
+ &man.ccd.4; to use. This can usually be copied from the
+ <literal>c</literal> partition, but the
+ <option>fstype</option> <emphasis>must</emphasis> be
+ <userinput>4.2BSD</userinput>. The disk label should now
+ look something like this:</para>
<programlisting>8 partitions:
# size offset fstype [fsize bsize bps/cpg]
c: 60074784 0 unused 0 0 0 # (Cyl. 0 - 59597)
e: 60074784 0 4.2BSD 0 0 0 # (Cyl. 0 - 59597)</programlisting>
-
</sect4>
<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>
+ build the &man.ccd.4;. To do that, use &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>
+ <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 below:</para>
+ <para>The use and meaning of each option is shown
+ 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>
- </callout>
+ <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>
+ </callout>
- <callout arearefs="co-ccd-interleave">
+ <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>
+ </callout>
- <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>
- </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
+ &man.ccd.4;, so it is set at 0 (zero).</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
- &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>
+ </callout>
+ </calloutlist>
- <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>
- </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>
+ <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>
<programlisting>newfs /dev/ccd0c</programlisting>
-
-
</sect4>
<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
- <filename>/etc/ccd.conf</filename> using the following command:</para>
+ <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
+ <filename>/etc/ccd.conf</filename> using the following
+ command:</para>
<programlisting>ccdconfig -g > /etc/ccd.conf</programlisting>
<para>During reboot, the script <command>/etc/rc</command>
- runs <command>ccdconfig -C</command> if <filename>/etc/ccd.conf</filename>
- exists. This automatically configures the
- &man.ccd.4; so it can be mounted.</para>
+ runs <command>ccdconfig -C</command> if
+ <filename>/etc/ccd.conf</filename> exists. This
+ automatically configures the &man.ccd.4; so it can be
+ 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>
+ <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>
- <programlisting>ccdconfig -C</programlisting>
- </note>
+ <programlisting>ccdconfig -C</programlisting>
+ </note>
- <para>To automatically mount the &man.ccd.4;,
- place an entry for the &man.ccd.4; in
- <filename>/etc/fstab</filename> so it will be mounted at
- boot time:</para>
+ <para>To automatically mount the &man.ccd.4;, place an entry
+ for the &man.ccd.4; in <filename>/etc/fstab</filename> so
+ it will be mounted at boot time:</para>
<programlisting>/dev/ccd0c /media ufs rw 2 2</programlisting>
</sect4>
@@ -575,11 +613,14 @@
<sect3 id="vinum">
<title>The Vinum Volume Manager</title>
-<indexterm><primary>RAID</primary><secondary>software</secondary></indexterm>
-<indexterm>
- <primary>RAID</primary>
- <secondary>Vinum</secondary>
-</indexterm>
+ <indexterm>
+ <primary>RAID</primary>
+ <secondary>software</secondary>
+ </indexterm>
+ <indexterm>
+ <primary>RAID</primary>
+ <secondary>Vinum</secondary>
+ </indexterm>
<para>The Vinum Volume Manager is a block device driver which
implements virtual disk drives. It isolates disk hardware
@@ -602,29 +643,33 @@
<secondary>hardware</secondary>
</indexterm>
- <para>FreeBSD also supports a variety of hardware <acronym>RAID</acronym>
- controllers. These devices control a <acronym>RAID</acronym> subsystem
- without the need for FreeBSD specific software to manage the
- array.</para>
+ <para>FreeBSD also supports a variety of hardware
+ <acronym>RAID</acronym> controllers. These devices control a
+ <acronym>RAID</acronym> subsystem without the need for FreeBSD
+ 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 <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
- accordingly.
- </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
+ <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
+ 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>FreeBSD allows you to hot-replace a failed disk in an
+ array. This requires that you catch it before you
+ reboot.</para>
- <para>You will probably see something like the following in <filename>/var/log/messages</filename> or in the &man.dmesg.8;
+ <para>You will probably see something like the following in
+ <filename>/var/log/messages</filename> or in the &man.dmesg.8;
output:</para>
<programlisting>ad6 on monster1 suffered a hard error.
@@ -635,7 +680,8 @@
status=59 error=40
ar0: WARNING - mirror lost</programlisting>
- <para>Using &man.atacontrol.8;, check for further information:</para>
+ <para>Using &man.atacontrol.8;, check for further
+ information:</para>
<screen>&prompt.root; <userinput>atacontrol list</userinput>
ATA channel 0:
@@ -659,8 +705,8 @@
<procedure>
<step>
- <para>You will first need to detach the ata channel with the failed
- disk so you can safely remove it:</para>
+ <para>You will first need to detach the ata channel with the
+ failed disk so you can safely remove it:</para>
<screen>&prompt.root; <userinput>atacontrol detach ata3</userinput></screen>
</step>
@@ -755,17 +801,17 @@
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>
+ 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>
<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 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>
<programlisting>device cd</programlisting>
@@ -863,9 +909,9 @@
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>
+ (replace <replaceable>username</replaceable> by the login name
+ of the actual user and <replaceable>usergroup</replaceable> by
+ 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>
@@ -892,10 +938,11 @@
<title>Further Reading</title>
<para>Beside the <link linkend="disks-adding">Adding
- Disks</link> and <link linkend="mount-unmount">Mounting and
+ Disks</link> and <link linkend="mount-unmount">Mounting and
Unmounting File Systems</link> sections, reading various
manual pages may be also useful: &man.umass.4;,
- &man.camcontrol.8;, and &man.usbconfig.8; under &os; 8.X or &man.usbdevs.8; under earlier versions of &os;.</para>
+ &man.camcontrol.8;, and &man.usbconfig.8; under &os; 8.X
+ or &man.usbdevs.8; under earlier versions of &os;.</para>
</sect2>
</sect1>
@@ -922,63 +969,69 @@
<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>
+ 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>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>
<indexterm><primary>ISO 9660</primary></indexterm>
<indexterm>
- <primary>file systems</primary>
- <secondary>ISO 9660</secondary>
+ <primary>file systems</primary>
+ <secondary>ISO 9660</secondary>
</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. 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>
<indexterm>
- <primary><filename role="package">sysutils/cdrtools</filename></primary>
+ <primary><filename
+ role="package">sysutils/cdrtools</filename></primary>
</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>
+ system. It has options that support various extensions, and
+ is described below.</para>
>>> TRUNCATED FOR MAIL (1000 lines) <<<
More information about the p4-projects
mailing list