svn commit: r44636 - head/en_US.ISO8859-1/books/handbook/disks
Dru Lavigne
dru at FreeBSD.org
Wed Apr 23 18:16:35 UTC 2014
Author: dru
Date: Wed Apr 23 18:16:34 2014
New Revision: 44636
URL: http://svnweb.freebsd.org/changeset/doc/44636
Log:
Initial prep work for CD chapter.
Move ATAPI section to beginning. This section will be reworked to describe
what is needed for supported devices, including the changes for 10.x.
Rename some headings to indicate the type of device it applies to.
More commits to come.
Sponsored by: iXsystems
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 Wed Apr 23 17:04:02 2014 (r44635)
+++ head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Wed Apr 23 18:16:34 2014 (r44636)
@@ -629,75 +629,126 @@ da0: <STECH Simple Drive 1.04> s/n
</indexterm>
<para><acronym>CD</acronym> 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
+ that differentiate them from conventional disks. 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>
+ between tracks. While <acronym>CD</acronym> media do have tracks, these refer
+ to a section of data to be read continuously, and not a physical
+ property of the disk. The <acronym>ISO</acronym> 9660 file system was designed to deal with these
+ differences.</para>
- <para><acronym>CD</acronym> 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
- <acronym>CD</acronym> on &os;, prepare the data files that are
- going to make up the tracks on the <acronym>CD</acronym>, then
- write the tracks to the <acronym>CD</acronym>.</para>
-
- <indexterm><primary>ISO 9660</primary></indexterm>
+ <indexterm><primary><acronym>ISO</acronym> 9660</primary></indexterm>
<indexterm>
<primary>file systems</primary>
<secondary>ISO 9660</secondary>
</indexterm>
- <para>The ISO 9660 file system was designed to deal with these
- differences. To overcome the original file system limits, it
- provides an extension mechanism that allows properly written
- <acronym>CD</acronym>s to exceed those limits while still
- working with systems that do not support those
- extensions.</para>
-
- <indexterm>
- <primary><package>sysutils/cdrtools</package></primary>
- </indexterm>
-
- <para>The <package>sysutils/cdrtools</package> 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><acronym>CD</acronym> burner</primary>
<secondary><acronym>ATAPI</acronym></secondary>
</indexterm>
- <para>Which tool to use to burn the <acronym>CD</acronym> depends
- on whether the <acronym>CD</acronym> burner is
- <acronym>ATAPI</acronym> or something else.
- <acronym>ATAPI</acronym> <acronym>CD</acronym> burners use
- <command>burncd</command> which is part of the base system.
- <acronym>SCSI</acronym> and <acronym>USB</acronym>
- <acronym>CD</acronym> burners should use
- <command>cdrecord</command> from the
- <package>sysutils/cdrtools</package> port. It is also possible
- to use <command>cdrecord</command> and other tools for
- <acronym>SCSI</acronym> drives on <acronym>ATAPI</acronym>
- hardware with the <link linkend="atapicam">ATAPI/CAM
- module</link>.</para>
-
- <para>For <acronym>CD</acronym> 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 <package>sysutils/xcdroast</package> and
- <package>sysutils/k3b</package> ports.
- <application>X-CD-Roast</application> and
- <application>K3b</application> require the <link
- linkend="atapicam">ATAPI/CAM module</link> with
- <acronym>ATAPI</acronym> hardware.</para>
+ <para>The &os; Ports Collection provides several utilities for
+ burning and duplicating audio and data <acronym>CD</acronym>s.
+ Which tool to use to burn a <acronym>CD</acronym> depends
+ on whether the <acronym>CD</acronym> burner is an
+ <acronym>ATAPI</acronym>, <acronym>SCSI</acronym>, or
+ <acronym>USB</acronym> device. This chapter demonstrates the use
+ of several command line utilities. For <acronym>CD</acronym>
+ burning software with a graphical, consider installing the
+ <package>sysutils/xcdroast</package> or
+ <package>sysutils/k3b</package> packages or ports.</para>
+
+ <sect2 xml:id="atapicam">
+ <info>
+ <title>Supported Devices</title>
+
+ <authorgroup>
+ <author>
+ <personname>
+ <firstname>Marc</firstname>
+ <surname>Fonvieille</surname>
+ </personname>
+ <contrib>Contributed by </contrib>
+ </author>
+ </authorgroup>
+ </info>
+
+ <indexterm>
+ <primary><acronym>CD</acronym> burner</primary>
+ <secondary>ATAPI/CAM driver</secondary>
+ </indexterm>
+
+ <para>This driver allows <acronym>ATAPI</acronym> devices, such
+ as CD/DVD drives, to be accessed through the
+ <acronym>SCSI</acronym> subsystem, and so allows the use of
+ applications like <package>sysutils/cdrdao</package> or
+ &man.cdrecord.1;.</para>
+
+ <para>To use this driver, add the following line to
+ <filename>/boot/loader.conf</filename>:</para>
+
+ <programlisting>atapicam_load="YES"</programlisting>
+
+ <para>then, reboot the system.</para>
+
+ <note>
+ <para>Users who prefer to statically compile &man.atapicam.4;
+ support into the kernel, should add this line to the
+ kernel configuration file:</para>
+
+ <programlisting>device atapicam</programlisting>
+
+ <para>Ensure the following lines are still in the kernel
+ configuration file:</para>
+
+ <programlisting>device ata
+device scbus
+device cd
+device pass</programlisting>
+
+ <para>Then rebuild, install the new kernel, and reboot the
+ machine.</para>
+ </note>
+
+ <para>During the boot process, the burner should show up, like
+ so:</para>
+
+ <screen>acd0: CD-RW <MATSHITA CD-RW/DVD-ROM UJDA740> at ata1-master PIO4
+cd0 at ata1 bus 0 target 0 lun 0
+cd0: <MATSHITA CDRW/DVD UJDA740 1.00> Removable CD-ROM SCSI-0 device
+cd0: 16.000MB/s transfers
+cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed</screen>
+
+ <para>The drive can now be accessed via the
+ <filename>/dev/cd0</filename> device name. For example, to
+ mount a <acronym>CD-ROM</acronym> on
+ <filename>/mnt</filename>, type the following:</para>
+
+ <screen>&prompt.root; <userinput>mount -t cd9660 <replaceable>/dev/cd0</replaceable> /mnt</userinput></screen>
+
+ <para>As <systemitem class="username">root</systemitem>, run the
+ following command to get the <acronym>SCSI</acronym> address
+ of the burner:</para>
+
+ <screen>&prompt.root; <userinput>camcontrol devlist</userinput>
+<MATSHITA CDRW/DVD UJDA740 1.00> at scbus1 target 0 lun 0 (pass0,cd0)</screen>
+
+ <para>In this example, <literal>1,0,0</literal> is the
+ <acronym>SCSI</acronym> address to use with &man.cdrecord.1;
+ and other <acronym>SCSI</acronym> applications.</para>
+
+ <para>For more information about ATAPI/CAM and
+ <acronym>SCSI</acronym> system, refer to &man.atapicam.4; and
+ &man.cam.4;.</para>
+ </sect2>
<sect2 xml:id="mkisofs">
- <title><application>mkisofs</application></title>
+ <title>Creating an <acronym>ISO</acronym> File System</title>
- <para>The <package>sysutils/cdrtools</package>
- port also installs &man.mkisofs.8;, which produces an ISO 9660
+ <para>In order to produce a data <acronym>CD</acronym>, the data files that are
+ going to make up the tracks on the <acronym>CD</acronym> must be prepared then
+ written to the <acronym>CD</acronym>. In &os;, the <package>sysutils/cdrtools</package>
+ package or port installs <command>mkisofs</command>, 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>
@@ -779,7 +830,7 @@ da0: <STECH Simple Drive 1.04> s/n
</sect2>
<sect2 xml:id="burncd">
- <title><application>burncd</application></title>
+ <title>Using an <acronym>ATAPI</acronym> Burner</title>
<indexterm>
<primary><acronym>CD-ROM</acronym>s</primary>
@@ -804,7 +855,7 @@ da0: <STECH Simple Drive 1.04> s/n
</sect2>
<sect2 xml:id="cdrecord">
- <title><application>cdrecord</application></title>
+ <title>Using a <acronym>USB</acronym> or <acronym>SCSI</acronym> Burner</title>
<para>For systems without an <acronym>ATAPI</acronym>
<acronym>CD</acronym> burner, <command>cdrecord</command> can
@@ -1067,90 +1118,6 @@ scsibus1:
operating system, &man.mkisofs.8; must be used as described
above.</para>
</sect2>
-
- <sect2 xml:id="atapicam">
- <info>
- <title>Using the ATAPI/CAM Driver</title>
-
- <authorgroup>
- <author>
- <personname>
- <firstname>Marc</firstname>
- <surname>Fonvieille</surname>
- </personname>
- <contrib>Contributed by </contrib>
- </author>
- </authorgroup>
- </info>
-
- <indexterm>
- <primary><acronym>CD</acronym> burner</primary>
- <secondary>ATAPI/CAM driver</secondary>
- </indexterm>
-
- <para>This driver allows <acronym>ATAPI</acronym> devices, such
- as CD/DVD drives, to be accessed through the
- <acronym>SCSI</acronym> subsystem, and so allows the use of
- applications like <package>sysutils/cdrdao</package> or
- &man.cdrecord.1;.</para>
-
- <para>To use this driver, add the following line to
- <filename>/boot/loader.conf</filename>:</para>
-
- <programlisting>atapicam_load="YES"</programlisting>
-
- <para>then, reboot the system.</para>
-
- <note>
- <para>Users who prefer to statically compile &man.atapicam.4;
- support into the kernel, should add this line to the
- kernel configuration file:</para>
-
- <programlisting>device atapicam</programlisting>
-
- <para>Ensure the following lines are still in the kernel
- configuration file:</para>
-
- <programlisting>device ata
-device scbus
-device cd
-device pass</programlisting>
-
- <para>Then rebuild, install the new kernel, and reboot the
- machine.</para>
- </note>
-
- <para>During the boot process, the burner should show up, like
- so:</para>
-
- <screen>acd0: CD-RW <MATSHITA CD-RW/DVD-ROM UJDA740> at ata1-master PIO4
-cd0 at ata1 bus 0 target 0 lun 0
-cd0: <MATSHITA CDRW/DVD UJDA740 1.00> Removable CD-ROM SCSI-0 device
-cd0: 16.000MB/s transfers
-cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed</screen>
-
- <para>The drive can now be accessed via the
- <filename>/dev/cd0</filename> device name. For example, to
- mount a <acronym>CD-ROM</acronym> on
- <filename>/mnt</filename>, type the following:</para>
-
- <screen>&prompt.root; <userinput>mount -t cd9660 <replaceable>/dev/cd0</replaceable> /mnt</userinput></screen>
-
- <para>As <systemitem class="username">root</systemitem>, run the
- following command to get the <acronym>SCSI</acronym> address
- of the burner:</para>
-
- <screen>&prompt.root; <userinput>camcontrol devlist</userinput>
-<MATSHITA CDRW/DVD UJDA740 1.00> at scbus1 target 0 lun 0 (pass0,cd0)</screen>
-
- <para>In this example, <literal>1,0,0</literal> is the
- <acronym>SCSI</acronym> address to use with &man.cdrecord.1;
- and other <acronym>SCSI</acronym> applications.</para>
-
- <para>For more information about ATAPI/CAM and
- <acronym>SCSI</acronym> system, refer to &man.atapicam.4; and
- &man.cam.4;.</para>
- </sect2>
</sect1>
<sect1 xml:id="creating-dvds">
More information about the svn-doc-all
mailing list