svn commit: r44642 - in head/en_US.ISO8859-1/books: faq handbook/disks
Dru Lavigne
dru at FreeBSD.org
Thu Apr 24 13:16:40 UTC 2014
Author: dru
Date: Thu Apr 24 13:16:39 2014
New Revision: 44642
URL: http://svnweb.freebsd.org/changeset/doc/44642
Log:
Editorial review of Burning CDs and Creating ISO File sections.
Add data CDs as a note and modify reference to new location in FAQ.
Sponsored by: iXsystems
Modified:
head/en_US.ISO8859-1/books/faq/book.xml
head/en_US.ISO8859-1/books/handbook/disks/chapter.xml
Modified: head/en_US.ISO8859-1/books/faq/book.xml
==============================================================================
--- head/en_US.ISO8859-1/books/faq/book.xml Thu Apr 24 11:36:42 2014 (r44641)
+++ head/en_US.ISO8859-1/books/faq/book.xml Thu Apr 24 13:16:39 2014 (r44642)
@@ -3383,7 +3383,7 @@ C:\="DOS"</programlisting>
</question>
<answer>
- <para>This is discussed in the Handbook section on <link xlink:href="&url.books.handbook;/creating-cds.html#imaging-cd">duplicating data CDs</link>.
+ <para>This is discussed in the Handbook section on <link xlink:href="&url.books.handbook;/creating-cds.html#mkisofs">duplicating data CDs</link>.
For more on working with CD-ROMs, see the <link xlink:href="&url.books.handbook;/creating-cds.html">Creating CDs Section</link>
in the Storage chapter in the Handbook.</para>
</answer>
Modified: head/en_US.ISO8859-1/books/handbook/disks/chapter.xml
==============================================================================
--- head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Thu Apr 24 11:36:42 2014 (r44641)
+++ head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Thu Apr 24 13:16:39 2014 (r44642)
@@ -759,14 +759,15 @@ cd0: Attempt to query device size failed
</note>
<para>While <command>cdrecord</command> has many options, basic
- usage is simple. Burning an ISO 9660 image is done
- with:</para>
+ usage is simple. Specify the name of the
+ <acronym>ISO</acronym> file to burn and, if the system has
+ multiple burner devices, specify the name of the device to
+ use:</para>
- <screen>&prompt.root; <userinput>cdrecord dev=<replaceable>device</replaceable> <replaceable>imagefile.iso</replaceable></userinput></screen>
+ <screen>&prompt.root; <userinput>cdrecord <replaceable>dev=device</replaceable> <replaceable>imagefile.iso</replaceable></userinput></screen>
- <para>The tricky part of using <command>cdrecord</command> is
- finding the <option>dev</option> to use. To find the proper
- setting, use <option>-scanbus</option> which might produce
+ <para>To determine the device name of the burner,
+ use <option>-scanbus</option> which might produce
results like this:</para>
<indexterm>
@@ -774,8 +775,8 @@ cd0: Attempt to query device size failed
<secondary>burning</secondary>
</indexterm>
<screen>&prompt.root; <userinput>cdrecord -scanbus</userinput>
-Cdrecord-Clone 2.01 (i386-unknown-freebsd7.0) Copyright (C) 1995-2004 Jörg Schilling
-Using libscg version 'schily-0.1'
+ProDVD-ProBD-Clone 3.00 (amd64-unknown-freebsd10.0) Copyright (C) 1995-2010 Jörg Schilling
+Using libscg version 'schily-0.9'
scsibus0:
0,0,0 0) 'SEAGATE ' 'ST39236LW ' '0004' Disk
0,1,0 1) 'SEAGATE ' 'ST39173W ' '5958' Disk
@@ -795,39 +796,40 @@ scsibus1:
1,6,0 106) 'ARTEC ' 'AM12S ' '1.06' Scanner
1,7,0 107) *</screen>
- <para>This lists the appropriate <option>dev</option> value for
- the devices on the list. Locate the <acronym>CD</acronym>
- burner, and use the three numbers separated by commas as the
- value for <option>dev</option>. In this case, the CRW device
- is 1,5,0, so the appropriate input is
- <option>dev=1,5,0</option>. Refer to &man.cdrecord.1; for
- easier ways to specify this value and for information on
+ <para>Locate the entry for the <acronym>CD</acronym>
+ burner and use the three numbers separated by commas as the
+ value for <option>dev</option>. In this case, the Yamaha burner device
+ is <literal>1,5,0</literal>, so the appropriate input to specify that device is
+ <option>dev=1,5,0</option>. Refer to the manual page for <command>cdrecord</command> for
+ other ways to specify this value and for information on
writing audio tracks and controlling the write speed.</para>
- <para>Alternately, as <systemitem
- class="username">root</systemitem>, run the following
- command to get the <acronym>SCSI</acronym> address of the
+ <para>Alternately, run the following
+ command to get the device 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>
+<MATSHITA CDRW/DVD UJDA740 1.00> at scbus1 target 0 lun 0 (cd0,pass0)</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>Use the numeric values for <literal>scbus</literal>,
+ <literal>target</literal>, and <literal>lun</literal>. For
+ this example, <literal>1,0,0</literal> is the
+ device name to use.</para>
</sect2>
<sect2 xml:id="mkisofs">
- <title>Creating an <acronym>ISO</acronym> File System</title>
+ <title>Writing Data to an <acronym>ISO</acronym> File System</title>
<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>
+ <acronym>CD</acronym> must be prepared before they can be burned to the
+ <acronym>CD</acronym>. In &os;,
+ <package>sysutils/cdrtools</package> installs
+ <command>mkisofs</command>, which can be used to produce an <acronym>ISO</acronym> 9660 file
+ system that is an image of a directory tree within a &unix; file
+ system. The simplest usage is to specify the name of the
+ <acronym>ISO</acronym> file to create and the path to the files
+ to place into the <acronym>ISO</acronym> 9660 file system:</para>
<screen>&prompt.root; <userinput>mkisofs -o <replaceable>imagefile.iso</replaceable> <replaceable>/path/to/tree</replaceable></userinput></screen>
@@ -836,35 +838,27 @@ scsibus1:
<secondary>ISO 9660</secondary>
</indexterm>
- <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
- 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>
+ <para>This command
+ maps the file names in the specified path to names that fit the limitations of
+ the standard <acronym>ISO</acronym> 9660 file system, and will exclude files that
+ do not meet the standard for <acronym>ISO</acronym> file systems.</para>
<indexterm>
<primary>file systems</primary>
- <secondary>HFS</secondary>
- </indexterm>
- <indexterm>
- <primary>file systems</primary>
<secondary>Joliet</secondary>
</indexterm>
- <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,
+ <para>A number of options are available to overcome the
+ restrictions imposed by the standard. In particular, <option>-R</option> enables the
+ Rock Ridge extensions common to &unix; systems and
<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>
+ Microsoft systems.</para>
<para>For <acronym>CD</acronym>s 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 specified &os; tree, though it may violate
- the ISO 9660 standard in a number of ways.</para>
+ identical to the specified &os; tree, even if it violates
+ the <acronym>ISO</acronym> 9660 standard.</para>
<indexterm>
<primary><acronym>CD-ROM</acronym>s</primary>
@@ -872,27 +866,26 @@ scsibus1:
</indexterm>
<para>The last option of general use is <option>-b</option>.
- This is used to specify the location of the boot image for use
+ This is used to specify the location of a boot image for use
in producing an <quote>El Torito</quote> bootable
<acronym>CD</acronym>. This option takes an argument which is
the path to a boot image from the top of the tree being
written to the <acronym>CD</acronym>. By default,
- &man.mkisofs.8; creates an ISO image in <quote>floppy disk
+ <command>mkisofs</command> creates an <acronym>ISO</acronym> 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
+ loaders, like the one used by the &os; distribution media, do
not use emulation mode. In this case,
<option>-no-emul-boot</option> should be used. So, if
<filename>/tmp/myboot</filename> holds a bootable &os; system
with the boot image in
<filename>/tmp/myboot/boot/cdboot</filename>, this command
- would produce the image of an ISO 9660 file system as
+ would produce
<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>
- <para>If <filename>md</filename> is configured in the
- kernel, the file system can be mounted as a memory disk
+ <para>The resulting <acronym>ISO</acronym> image can be mounted as a memory disk
with:</para>
<screen>&prompt.root; <userinput>mdconfig -a -t vnode -f /tmp/bootable.iso -u 0</userinput>
@@ -902,8 +895,23 @@ scsibus1:
<filename>/tmp/myboot</filename> are identical.</para>
<para>There are many other options available for
- &man.mkisofs.8; to fine-tune its behavior. Refer to
+ <command>mkisofs</command> to fine-tune its behavior. Refer to
&man.mkisofs.8; for details.</para>
+
+ <note>
+ <para>It is possible to copy a data <acronym>CD</acronym> to an
+ image file that is functionally equivalent to the image file
+ created with <command>mkisofs</command>. To do so, use
+ <filename>dd</filename> with the device name as the input file
+ and the name of the <acronym>ISO</acronym> to create as the
+ output file:</para>
+
+ <screen>&prompt.root; <userinput>dd if=/dev/<replaceable>cd0</replaceable> of=<replaceable>file.iso</replaceable> bs=2048</userinput></screen>
+
+ <para>The resulting image file can be burned to
+ <acronym>CD</acronym> as described in <xref
+ linkend="cdrecord"/>.</para>
+ </note>
</sect2>
<sect2 xml:id="duplicating-audiocds">
@@ -992,23 +1000,6 @@ Update example for cdrecord
</procedure>
</sect2>
- <sect2 xml:id="imaging-cd">
- <title>Duplicating Data <acronym>CD</acronym>s</title>
-
- <para>It is possible to copy a data <acronym>CD</acronym> to an
- image file that is functionally equivalent to the image file
- created with &man.mkisofs.8;, and then use it to duplicate any
- data <acronym>CD</acronym>. The example given here assumes
- that the <acronym>CD-ROM</acronym> device is
- <filename>acd0</filename>. Substitute the correct
- <acronym>CD-ROM</acronym> device.</para>
-
- <screen>&prompt.root; <userinput>dd if=/dev/acd0 of=file.iso bs=2048</userinput></screen>
-
- <para>Now that there is an image, it can be burned to
- <acronym>CD</acronym> as described above.</para>
- </sect2>
-
<sect2 xml:id="mounting-cd">
<title>Using Data <acronym>CD</acronym>s</title>
More information about the svn-doc-all
mailing list