Date: Fri, 21 Mar 2014 21:54:51 +0000 (UTC) From: Dru Lavigne <dru@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44327 - head/en_US.ISO8859-1/books/handbook/disks Message-ID: <201403212154.s2LLspGx030277@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: dru Date: Fri Mar 21 21:54:51 2014 New Revision: 44327 URL: http://svnweb.freebsd.org/changeset/doc/44327 Log: White space fix only. Translators can ignore. 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 Fri Mar 21 21:37:42 2014 (r44326) +++ head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Fri Mar 21 21:54:51 2014 (r44327) @@ -16,7 +16,8 @@ <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 <acronym>USB</acronym> interface.</para> + storage devices, and devices using the <acronym>USB</acronym> + interface.</para> <para>After reading this chapter, you will know:</para> @@ -32,7 +33,8 @@ </listitem> <listitem> - <para>How to configure &os; to use <acronym>USB</acronym> storage devices.</para> + <para>How to configure &os; to use <acronym>USB</acronym> + storage devices.</para> </listitem> <listitem> @@ -50,7 +52,8 @@ </listitem> <listitem> - <para>How to create and burn <acronym>CD</acronym>s and <acronym>DVD</acronym>s on &os;.</para> + <para>How to create and burn <acronym>CD</acronym>s and + <acronym>DVD</acronym>s on &os;.</para> </listitem> <listitem> @@ -99,7 +102,8 @@ </row> <row> - <entry><acronym>IDE</acronym> <acronym>CD-ROM</acronym> drives</entry> + <entry><acronym>IDE</acronym> <acronym>CD-ROM</acronym> + drives</entry> <entry><literal>acd</literal> or <literal>cd</literal></entry> </row> @@ -111,26 +115,32 @@ </row> <row> - <entry><acronym>SATA</acronym> <acronym>CD-ROM</acronym> drives</entry> + <entry><acronym>SATA</acronym> <acronym>CD-ROM</acronym> + drives</entry> <entry><literal>acd</literal> or <literal>cd</literal></entry> </row> <row> - <entry><acronym>SCSI</acronym> hard drives and <acronym>USB</acronym> Mass storage + <entry><acronym>SCSI</acronym> hard drives and + <acronym>USB</acronym> Mass storage devices</entry> <entry><literal>da</literal></entry> </row> <row> - <entry><acronym>SCSI</acronym> <acronym>CD-ROM</acronym> drives</entry> + <entry><acronym>SCSI</acronym> <acronym>CD-ROM</acronym> + drives</entry> <entry><literal>cd</literal></entry> </row> <row> - <entry>Assorted non-standard <acronym>CD-ROM</acronym> drives</entry> - <entry><literal>mcd</literal> for Mitsumi <acronym>CD-ROM</acronym> and - <literal>scd</literal> for Sony <acronym>CD-ROM</acronym> devices</entry> + <entry>Assorted non-standard <acronym>CD-ROM</acronym> + drives</entry> + <entry><literal>mcd</literal> for Mitsumi + <acronym>CD-ROM</acronym> and + <literal>scd</literal> for Sony + <acronym>CD-ROM</acronym> devices</entry> </row> <row> @@ -420,18 +430,19 @@ super-block backups (for fsck -b #) at: <secondary>disks</secondary> </indexterm> - <para>Many external storage solutions, such as hard drives, <acronym>USB</acronym> - thumbdrives, and CD/DVD burners, use the Universal Serial Bus - (<acronym>USB</acronym>). &os; provides support for these devices.</para> + <para>Many external storage solutions, such as hard drives, + <acronym>USB</acronym> thumbdrives, and CD/DVD burners, use the + Universal Serial Bus (<acronym>USB</acronym>). &os; provides + support for these devices.</para> <sect2> <title>Configuration</title> - <para>The <acronym>USB</acronym> mass storage devices driver, &man.umass.4;, is - built into the <filename>GENERIC</filename> kernel and - provides support for <acronym>USB</acronym> storage devices. For a custom - kernel, be sure that the following lines are present in the - kernel configuration file:</para> + <para>The <acronym>USB</acronym> mass storage devices driver, + &man.umass.4;, is built into the <filename>GENERIC</filename> + kernel and provides support for <acronym>USB</acronym> 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 @@ -442,32 +453,38 @@ device ehci device usb device umass</programlisting> - <para>Since the &man.umass.4; driver uses the <acronym>SCSI</acronym> subsystem to - access the <acronym>USB</acronym> storage devices, any <acronym>USB</acronym> device will be seen as - a <acronym>SCSI</acronym> device by the system. Depending on the <acronym>USB</acronym> chipset on - the motherboard, <literal>device uhci</literal> or - <literal>device ohci</literal> is used to provide <acronym>USB</acronym> 1.X - support. Support for <acronym>USB</acronym> 2.0 controllers is provided by + <para>Since the &man.umass.4; driver uses the + <acronym>SCSI</acronym> subsystem to access the + <acronym>USB</acronym> storage devices, any + <acronym>USB</acronym> device will be seen as a + <acronym>SCSI</acronym> device by the system. Depending on + the <acronym>USB</acronym> chipset on the motherboard, + <literal>device uhci</literal> or + <literal>device ohci</literal> is used to provide + <acronym>USB</acronym> 1.X support. Support for + <acronym>USB</acronym> 2.0 controllers is provided by <literal>device ehci</literal>.</para> <note> - <para>If the <acronym>USB</acronym> device is a <acronym>CD</acronym> or <acronym>DVD</acronym> burner, &man.cd.4;, - must be added to the kernel via the line:</para> + <para>If the <acronym>USB</acronym> device is a + <acronym>CD</acronym> or <acronym>DVD</acronym> burner, + &man.cd.4;, must be added to the kernel via the line:</para> <programlisting>device cd</programlisting> - <para>Since the burner is seen as a <acronym>SCSI</acronym> drive, the driver - &man.atapicam.4; should not be used in the kernel - configuration.</para> + <para>Since the burner is seen as a <acronym>SCSI</acronym> + drive, the driver &man.atapicam.4; should not be used in the + kernel configuration.</para> </note> </sect2> <sect2> <title>Testing the Configuration</title> - <para>To test the <acronym>USB</acronym> configuration, plug in the <acronym>USB</acronym> device. In - the system message buffer, &man.dmesg.8;, the drive should - appear as something like:</para> + <para>To test the <acronym>USB</acronym> configuration, plug in + the <acronym>USB</acronym> 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 @@ -479,17 +496,18 @@ da0: 126MB (258048 512 byte sectors: 64H <para>The brand, device node (<filename>da0</filename>), and other details will differ according to the device.</para> - <para>Since the <acronym>USB</acronym> device is seen as a <acronym>SCSI</acronym> one, - <command>camcontrol</command> can be used to list the <acronym>USB</acronym> - storage devices attached to the system:</para> + <para>Since the <acronym>USB</acronym> device is seen as a + <acronym>SCSI</acronym> one, <command>camcontrol</command> can + be used to list the <acronym>USB</acronym> 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, it can be mounted. - Refer to <xref linkend="disks-adding"/> for - instructions on how to format and create partitions on the <acronym>USB</acronym> - drive.</para> + Refer to <xref linkend="disks-adding"/> for instructions on + how to format and create partitions on the + <acronym>USB</acronym> drive.</para> <warning> <para>Allowing untrusted users to mount arbitrary media, by @@ -502,25 +520,24 @@ da0: 126MB (258048 512 byte sectors: 64H <para>To make the device mountable as a normal user, one solution is to make all users of the device a member of the <systemitem class="groupname">operator</systemitem> group - using &man.pw.8;. Next, ensure that the - <systemitem class="groupname">operator</systemitem> group is - able to read and write the device by adding these lines to + using &man.pw.8;. Next, ensure that the <systemitem + class="groupname">operator</systemitem> 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 <acronym>SCSI</acronym> disks are installed in the system, change - the second line as follows:</para> + <para>If <acronym>SCSI</acronym> 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 first three <acronym>SCSI</acronym> disks - (<filename>da0</filename> to - <filename>da2</filename>)from belonging to the - <systemitem class="groupname">operator</systemitem> - group.</para> + <para>This will exclude the first three + <acronym>SCSI</acronym> disks (<filename>da0</filename> to + <filename>da2</filename>)from belonging to the <systemitem + class="groupname">operator</systemitem> group.</para> </note> <para>Next, enable the &man.devfs.rules.5; ruleset in @@ -551,10 +568,10 @@ add path 'da*' mode 0660 group operator< <screen>&prompt.root; <userinput>mkdir /mnt/username</userinput> &prompt.root; <userinput>chown username:usergroup /mnt/username</userinput></screen> - <para>Suppose a <acronym>USB</acronym> thumbdrive is plugged in, and a device - <filename>/dev/da0s1</filename> appears. If the device is - preformatted with a FAT file system, it can be mounted - using:</para> + <para>Suppose a <acronym>USB</acronym> thumbdrive is plugged in, + and a device <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/username</userinput></screen> @@ -602,64 +619,70 @@ umass0: detached</screen> <secondary>creating</secondary> </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 they can be - read continuously without delays to move the head between - tracks. They are also much easier to transport between - systems.</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> + <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 + they can be read continuously without delays to move the head + between tracks. They are also much easier to transport + between systems.</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>file systems</primary> - <secondary>ISO 9660</secondary> - </indexterm> + <indexterm><primary>ISO 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> + <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> + <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> + <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> + <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>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> <sect2 xml:id="mkisofs"> <title><application>mkisofs</application></title> @@ -699,27 +722,29 @@ umass0: detached</screen> Microsoft systems, and <option>-hfs</option> can be used to create HFS file systems used by &macos;.</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> + <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> <indexterm> <primary><acronym>CD-ROM</acronym>s</primary> <secondary>creating bootable</secondary> </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 - 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 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, + 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 + 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>/tmp/myboot</filename> holds a bootable &os; system with the boot image in @@ -751,8 +776,9 @@ umass0: detached</screen> <primary><acronym>CD-ROM</acronym>s</primary> <secondary>burning</secondary> </indexterm> - <para>For an <acronym>ATAPI</acronym> <acronym>CD</acronym> burner, <command>burncd</command> can be - used to burn an ISO image onto a <acronym>CD</acronym>. + <para>For an <acronym>ATAPI</acronym> <acronym>CD</acronym> + burner, <command>burncd</command> can be used to burn an ISO + image onto a <acronym>CD</acronym>. <command>burncd</command> is part of the base system, installed as <filename>/usr/sbin/burncd</filename>. Usage is very simple, as it has few options:</para> @@ -763,24 +789,26 @@ umass0: detached</screen> <replaceable>imagefile.iso</replaceable> on <replaceable>cddevice</replaceable>. The default device is <filename>/dev/acd0</filename>. See &man.burncd.8; for - options to set the write speed, eject the <acronym>CD</acronym> after burning, - and write audio data.</para> + options to set the write speed, eject the + <acronym>CD</acronym> after burning, and write audio + data.</para> </sect2> <sect2 xml:id="cdrecord"> <title><application>cdrecord</application></title> - <para>For systems without an <acronym>ATAPI</acronym> <acronym>CD</acronym> burner, - <command>cdrecord</command> can be used to burn <acronym>CD</acronym>s. + <para>For systems without an <acronym>ATAPI</acronym> + <acronym>CD</acronym> burner, <command>cdrecord</command> can + be used to burn <acronym>CD</acronym>s. <command>cdrecord</command> is not part of the base system and must be installed from either the <package>sysutils/cdrtools</package> package or port. Changes to the base system can cause binary versions of this program to fail, possibly resulting in a <quote>coaster</quote>. It is recommended to either upgrade the port when the system is - upgraded, or for users - <link linkend="stable">tracking -STABLE</link>, to upgrade the - port when a new version becomes available.</para> + upgraded, or for users <link linkend="stable">tracking + -STABLE</link>, to upgrade the port when a new version + becomes available.</para> <para>While <command>cdrecord</command> has many options, basic usage is simple. Burning an ISO 9660 image is done @@ -820,21 +848,23 @@ scsibus1: 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 writing audio tracks and - controlling the write speed.</para> + 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 + writing audio tracks and controlling the write speed.</para> </sect2> <sect2 xml:id="duplicating-audiocds"> <title>Duplicating Audio <acronym>CD</acronym>s</title> - <para>To duplicate an audio <acronym>CD</acronym>, extract the audio data from the - <acronym>CD</acronym> to a series of files, then write these files to a blank <acronym>CD</acronym>. - The process is slightly different for <acronym>ATAPI</acronym> and <acronym>SCSI</acronym> + <para>To duplicate an audio <acronym>CD</acronym>, extract the + audio data from the <acronym>CD</acronym> to a series of + files, then write these files to a blank + <acronym>CD</acronym>. The process is slightly different for + <acronym>ATAPI</acronym> and <acronym>SCSI</acronym> drives.</para> <procedure> @@ -854,8 +884,8 @@ scsibus1: <screen>&prompt.user; <userinput>cdrecord -v dev=2,0 -dao -useinfo *.wav</userinput></screen> <para>Make sure that <replaceable>2,0</replaceable> is set - appropriately, as described in - <xref linkend="cdrecord"/>.</para> + appropriately, as described in <xref + linkend="cdrecord"/>.</para> </step> </procedure> @@ -865,19 +895,21 @@ scsibus1: <note> <para>With the help of the <link linkend="atapicam">ATAPI/CAM module</link>, - <command>cdda2wav</command> can also be used on <acronym>ATAPI</acronym> - drives. This tool is usually a better choice for most of - users, as it supports jitter correction and endianness, - than the method proposed below.</para> + <command>cdda2wav</command> can also be used on + <acronym>ATAPI</acronym> drives. This tool is usually a + better choice for most of users, as it supports jitter + correction and endianness, than the method proposed + below.</para> </note> <step> - <para>The <acronym>ATAPI</acronym> <acronym>CD</acronym> driver makes each track available as - <filename>/dev/acddtnn</filename>, - where <replaceable>d</replaceable> is the drive number, - and <replaceable>nn</replaceable> is the track number - written with two decimal digits, prefixed with zero as - needed. So the first track on the first disk is + <para>The <acronym>ATAPI</acronym> <acronym>CD</acronym> + driver makes each track available as + <filename>/dev/acddtnn</filename>, where + <replaceable>d</replaceable> is the drive number, and + <replaceable>nn</replaceable> is the track number written + with two decimal digits, prefixed with zero as needed. So + the first track on the first disk is <filename>/dev/acd0t01</filename>, the second is <filename>/dev/acd0t02</filename>, the third is <filename>/dev/acd0t03</filename>, and so on.</para> @@ -912,58 +944,59 @@ scsibus1: <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> + <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> + <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> <para>It is possible to mount and read the data on a standard - data <acronym>CD</acronym>. By default, &man.mount.8; assumes that a file system - is of type <literal>ufs</literal>. Running this - command:</para> + data <acronym>CD</acronym>. By default, &man.mount.8; assumes + that a file system is of type <literal>ufs</literal>. Running + this command:</para> <screen>&prompt.root; <userinput>mount /dev/cd0 /mnt</userinput></screen> <para>will generate an error about <errorname>Incorrect super - block</errorname>, and will fail to mount the <acronym>CD</acronym>. The <acronym>CD</acronym> - does not use the <literal>UFS</literal> file system, so - attempts to mount it as such will fail. Instead, tell - &man.mount.8; that the file system is of type - <literal>ISO9660</literal> by specifying - <option>-t cd9660</option> to &man.mount.8;. For example, - to mount the <acronym>CD-ROM</acronym> device, <filename>/dev/cd0</filename>, - under <filename>/mnt</filename>, - use:</para> + block</errorname>, and will fail to mount the + <acronym>CD</acronym>. The <acronym>CD</acronym> does not use + the <literal>UFS</literal> file system, so attempts to mount + it as such will fail. Instead, tell &man.mount.8; that the + file system is of type <literal>ISO9660</literal> by + specifying <option>-t cd9660</option> to &man.mount.8;. For + example, to mount the <acronym>CD-ROM</acronym> device, + <filename>/dev/cd0</filename>, under + <filename>/mnt</filename>, use:</para> <screen>&prompt.root; <userinput>mount -t cd9660 /dev/cd0 /mnt</userinput></screen> <para>Replace <filename>/dev/cd0</filename> with the device - name for the <acronym>CD</acronym> device. Also, <option>-t cd9660</option> - executes &man.mount.cd9660.8;, meaning the above command is - equivalent to:</para> + name for the <acronym>CD</acronym> device. Also, + <option>-t cd9660</option> executes &man.mount.cd9660.8;, + meaning the above command is equivalent to:</para> <screen>&prompt.root; <userinput>mount_cd9660 /dev/cd0 /mnt</userinput></screen> - <para>While data <acronym>CD-ROM</acronym>s from any vendor can be mounted this - way, disks with certain ISO 9660 extensions might behave - oddly. For example, Joliet disks store all filenames in - two-byte Unicode characters. The &os; kernel does not speak - Unicode, but the &os; CD9660 driver is able to convert Unicode - characters on the fly. If some non-English characters show up - as question marks, specify the local charset with - <option>-C</option>. For more information, refer to - &man.mount.cd9660.8;.</para> + <para>While data <acronym>CD-ROM</acronym>s from any vendor can + be mounted this way, disks with certain ISO 9660 extensions + might behave oddly. For example, Joliet disks store all + filenames in two-byte Unicode characters. The &os; kernel + does not speak Unicode, but the &os; CD9660 driver is able to + convert Unicode characters on the fly. If some non-English + characters show up as question marks, specify the local + charset with <option>-C</option>. For more information, refer + to &man.mount.cd9660.8;.</para> <note> <para>In order to do this character conversion with the help @@ -979,13 +1012,16 @@ scsibus1: </note> <para>Occasionally, <errorname>Device not configured</errorname> - will be displayed when trying to mount a <acronym>CD-ROM</acronym>. This - usually means that the <acronym>CD-ROM</acronym> drive thinks that there is no - disk in the tray, or that the drive is not visible on the bus. - It can take a couple of seconds for a <acronym>CD-ROM</acronym> drive to realize - that a media is present, so be patient.</para> + will be displayed when trying to mount a + <acronym>CD-ROM</acronym>. This usually means that the + <acronym>CD-ROM</acronym> drive thinks that there is no disk + in the tray, or that the drive is not visible on the bus. It + can take a couple of seconds for a <acronym>CD-ROM</acronym> + drive to realize that a media is present, so be + patient.</para> - <para>Sometimes, a <acronym>SCSI</acronym> <acronym>CD-ROM</acronym> may be missed because it did not + <para>Sometimes, a <acronym>SCSI</acronym> + <acronym>CD-ROM</acronym> may be missed because it did not have enough time to answer the bus reset. To resolve this, add the following option to the kernel configuration and <link linkend="kernelconfig-building">rebuild the @@ -993,31 +1029,34 @@ scsibus1: <programlisting>options SCSI_DELAY=15000</programlisting> - <para>This tells the <acronym>SCSI</acronym> bus to pause 15 seconds during boot, - to give the <acronym>CD-ROM</acronym> drive every possible chance to answer the - bus reset.</para> + <para>This tells the <acronym>SCSI</acronym> bus to pause 15 + seconds during boot, to give the <acronym>CD-ROM</acronym> + drive every possible chance to answer the bus reset.</para> </sect2> <sect2 xml:id="rawdata-cd"> <title>Burning Raw Data CDs</title> - <para>It is possible to burn a file directly to <acronym>CD</acronym>, without - creating an ISO 9660 file system. Some people do this for - backup purposes. This command runs more quickly than burning - a standard <acronym>CD</acronym>:</para> + <para>It is possible to burn a file directly to + <acronym>CD</acronym>, without creating an ISO 9660 file + system. Some people do this for backup purposes. This + command runs more quickly than burning a standard + <acronym>CD</acronym>:</para> <screen>&prompt.root; <userinput>burncd -f /dev/acd1 -s 12 data archive.tar.gz fixate</userinput></screen> - <para>In order to retrieve the data burned to such a <acronym>CD</acronym>, the - data must be read from the raw device node:</para> + <para>In order to retrieve the data burned to such a + <acronym>CD</acronym>, the data must be read from the raw + device node:</para> <screen>&prompt.root; <userinput>tar xzvf /dev/acd1</userinput></screen> - <para>This type of disk can not be mounted as a normal <acronym>CD-ROM</acronym> - and the data cannot be read under any operating system except - &os;. In order to mount the <acronym>CD</acronym>, or to share the data with - another operating system, &man.mkisofs.8; must be used as - described above.</para> + <para>This type of disk can not be mounted as a normal + <acronym>CD-ROM</acronym> and the data cannot be read under + any operating system except &os;. In order to mount the + <acronym>CD</acronym>, or to share the data with another + operating system, &man.mkisofs.8; must be used as described + above.</para> </sect2> <sect2 xml:id="atapicam"> @@ -1040,9 +1079,10 @@ scsibus1: <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 + <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 @@ -1082,24 +1122,25 @@ cd0: Attempt to query device size failed <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> + mount a <acronym>CD-ROM</acronym> on + <filename>/mnt</filename>, type the following:</para> <screen>&prompt.root; <userinput>mount -t cd9660 /dev/cd0 /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> + 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> + <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> @@ -1132,41 +1173,48 @@ cd0: Attempt to query device size failed <secondary>burning</secondary> </indexterm> - <para>Compared to the <acronym>CD</acronym>, the <acronym>DVD</acronym> is the next generation of - optical media storage technology. The <acronym>DVD</acronym> can hold more data - than any <acronym>CD</acronym> and is the standard for video publishing.</para> + <para>Compared to the <acronym>CD</acronym>, the + <acronym>DVD</acronym> is the next generation of optical media + storage technology. The <acronym>DVD</acronym> can hold more + data than any <acronym>CD</acronym> and is the standard for + video publishing.</para> <para>Five physical recordable formats can be defined for a recordable <acronym>DVD</acronym>:</para> <itemizedlist> <listitem> - <para>DVD-R: This was the first <acronym>DVD</acronym> recordable format - available. The DVD-R standard is defined by the - <link xlink:href="http://www.dvdforum.com/forum.shtml"><acronym>DVD</acronym>; + <para>DVD-R: This was the first <acronym>DVD</acronym> + recordable format available. The DVD-R standard is + defined by the <link + xlink:href="http://www.dvdforum.com/forum.shtml"><acronym>DVD</acronym>; Forum</link>. This format is write once.</para> </listitem> <listitem> - <para><acronym>DVD-RW</acronym>: This is the rewritable version of the - DVD-R standard. A <acronym>DVD-RW</acronym> can be rewritten about 1000 + <para><acronym>DVD-RW</acronym>: This is the rewritable + version of the DVD-R standard. A + <acronym>DVD-RW</acronym> can be rewritten about 1000 times.</para> </listitem> <listitem> - <para><acronym>DVD-RAM</acronym>: This is a rewritable format which can be seen - as a removable hard drive. However, this media is not - compatible with most <acronym>DVD-ROM</acronym> drives and DVD-Video players - as only a few <acronym>DVD</acronym> writers support the <acronym>DVD-RAM</acronym> format. - Refer to <xref linkend="creating-dvd-ram"/> for more - information on <acronym>DVD-RAM</acronym> use.</para> + <para><acronym>DVD-RAM</acronym>: This is a rewritable + format which can be seen as a removable hard drive. + However, this media is not compatible with most + <acronym>DVD-ROM</acronym> drives and DVD-Video players + as only a few <acronym>DVD</acronym> writers support the + <acronym>DVD-RAM</acronym> format. Refer to <xref + linkend="creating-dvd-ram"/> for more information on + <acronym>DVD-RAM</acronym> use.</para> </listitem> <listitem> - <para><acronym>DVD+RW</acronym>: This is a rewritable format defined by - the <link xlink:href="http://www.dvdrw.com/"><acronym>DVD+RW</acronym>; - Alliance</link>. A <acronym>DVD+RW</acronym> can be rewritten about 1000 - times.</para> + <para><acronym>DVD+RW</acronym>: This is a rewritable format + defined by the <link + xlink:href="http://www.dvdrw.com/"><acronym>DVD+RW</acronym>; + Alliance</link>. A <acronym>DVD+RW</acronym> can be + rewritten about 1000 times.</para> </listitem> <listitem> @@ -1175,38 +1223,39 @@ cd0: Attempt to query device size failed </listitem> </itemizedlist> - <para>A single layer recordable <acronym>DVD</acronym> can hold up to - 4,700,000,000 bytes which is actually 4.38 GB or - 4485 MB as 1 kilobyte is 1024 bytes.</para> + <para>A single layer recordable <acronym>DVD</acronym> can hold + up to 4,700,000,000 bytes which is actually 4.38 GB + or 4485 MB as 1 kilobyte is 1024 bytes.</para> <note> <para>A distinction must be made between the physical media and the application. For example, a DVD-Video is a specific - file layout that can be written on any recordable <acronym>DVD</acronym> - physical media such as DVD-R, DVD+R, or <acronym>DVD-RW</acronym>. Before - choosing the type of media, ensure that both the burner and - the DVD-Video player are compatible with the media under - consideration.</para> + file layout that can be written on any recordable + <acronym>DVD</acronym> physical media such as DVD-R, DVD+R, + or <acronym>DVD-RW</acronym>. Before choosing the type of + media, ensure that both the burner and the DVD-Video player + are compatible with the media under consideration.</para> </note> <sect2> <title>Configuration</title> - <para>To perform <acronym>DVD</acronym> recording, use &man.growisofs.1;. This - command is part of the + <para>To perform <acronym>DVD</acronym> recording, use + &man.growisofs.1;. This command is part of the <package>sysutils/dvd+rw-tools</package> utilities which support all <acronym>DVD</acronym> media types.</para> - <para>These tools use the <acronym>SCSI</acronym> subsystem to access the devices, - therefore <link linkend="atapicam">ATAPI/CAM support</link> - must be loaded or statically compiled into the kernel. This - support is not needed if the burner uses the <acronym>USB</acronym> interface. - Refer to <xref linkend="usb-disks"/> for more details - on <acronym>USB</acronym> device configuration.</para> - - <para>DMA access must also be enabled for <acronym>ATAPI</acronym> devices, by - adding the following line to - <filename>/boot/loader.conf</filename>:</para> + <para>These tools use the <acronym>SCSI</acronym> subsystem to + access the devices, therefore <link + linkend="atapicam">ATAPI/CAM support</link> must be loaded + or statically compiled into the kernel. This support is not + needed if the burner uses the <acronym>USB</acronym> + interface. Refer to <xref linkend="usb-disks"/> for more + details on <acronym>USB</acronym> device configuration.</para> + + <para>DMA access must also be enabled for + <acronym>ATAPI</acronym> devices, by adding the following line + to <filename>/boot/loader.conf</filename>:</para> <programlisting>hw.ata.atapi_dma="1"</programlisting> @@ -1226,15 +1275,16 @@ cd0: Attempt to query device size failed <sect2> <title>Burning Data <acronym>DVD</acronym>s</title> - <para>Since &man.growisofs.1; is a front-end to - <link linkend="mkisofs">mkisofs</link>, it will invoke + <para>Since &man.growisofs.1; is a front-end to <link + linkend="mkisofs">mkisofs</link>, it will invoke &man.mkisofs.8; to create the file system layout and perform - the write on the <acronym>DVD</acronym>. This means that an image of the data - does not need to be created before the burning process.</para> + the write on the <acronym>DVD</acronym>. This means that an + image of the data does not need to be created before the + burning process.</para> <para>To burn to a DVD+R or a DVD-R the data in - <filename>/path/to/data</filename>, - use the following command:</para> + <filename>/path/to/data</filename>, use the following + command:</para> <screen>&prompt.root; <userinput>growisofs -dvd-compat -Z /dev/cd0 -J -R /path/to/data</userinput></screen> @@ -1245,11 +1295,12 @@ cd0: Attempt to query device size failed <para>For the initial session recording, <option>-Z</option> is used for both single and multiple sessions. Replace - <replaceable>/dev/cd0</replaceable>, with the name of the <acronym>DVD</acronym> - device. Using <option>-dvd-compat</option> indicates that the - disk will be closed and that the recording will be - unappendable. This should also provide better media - compatibility with <acronym>DVD-ROM</acronym> drives.</para> + <replaceable>/dev/cd0</replaceable>, with the name of the + <acronym>DVD</acronym> device. Using + <option>-dvd-compat</option> indicates that the disk will be + closed and that the recording will be unappendable. This + should also provide better media compatibility with + <acronym>DVD-ROM</acronym> drives.</para> <para>To burn a pre-mastered image, such as <replaceable>imagefile.iso</replaceable>, use:</para> @@ -1310,9 +1361,10 @@ cd0: Attempt to query device size failed <para>If an image of the DVD-Video file system already exists, it can be burned in the same way as any other image. If - <command>dvdauthor</command> was used to make the <acronym>DVD</acronym> and the - result is in <filename>/path/to/video</filename>, the - following command should be used to burn the DVD-Video:</para> + <command>dvdauthor</command> was used to make the + <acronym>DVD</acronym> and the result is in + <filename>/path/to/video</filename>, the following command + should be used to burn the DVD-Video:</para> <screen>&prompt.root; <userinput>growisofs -Z /dev/cd0 -dvd-video /path/to/video</userinput></screen> @@ -1330,34 +1382,36 @@ cd0: Attempt to query device size failed <secondary><acronym>DVD+RW</acronym></secondary> </indexterm> - <para>Unlike CD-RW, a virgin <acronym>DVD+RW</acronym> needs to be formatted before - first use. It is <emphasis>recommended</emphasis> to let - &man.growisofs.1; take care of this automatically whenever - appropriate. However, it is possible to use - <command>dvd+rw-format</command> to format the <acronym>DVD+RW</acronym>:</para> + <para>Unlike CD-RW, a virgin <acronym>DVD+RW</acronym> needs to + be formatted before first use. It is + <emphasis>recommended</emphasis> to let &man.growisofs.1; take + care of this automatically whenever appropriate. However, it + is possible to use <command>dvd+rw-format</command> to format + the <acronym>DVD+RW</acronym>:</para> <screen>&prompt.root; <userinput>dvd+rw-format /dev/cd0</userinput></screen> <para>Only perform this operation once and keep in mind that - only virgin <acronym>DVD+RW</acronym> medias need to be formatted. Once - formatted, the <acronym>DVD+RW</acronym> can be burned as usual.</para> + only virgin <acronym>DVD+RW</acronym> medias need to be + formatted. Once formatted, the <acronym>DVD+RW</acronym> can + be burned as usual.</para> <para>To burn a totally new file system and not just append some - data onto a <acronym>DVD+RW</acronym>, the media does not need to be blanked - first. Instead, write over the previous recording like - this:</para> + data onto a <acronym>DVD+RW</acronym>, the media does not need + to be blanked first. Instead, write over the previous + recording like this:</para> <screen>&prompt.root; <userinput>growisofs -Z /dev/cd0 -J -R /path/to/newdata</userinput></screen> - <para>The <acronym>DVD+RW</acronym> format supports appending data to a previous - recording. This operation consists of merging a new session - to the existing one as it is not considered to be - multi-session writing. &man.growisofs.1; will - <emphasis>grow</emphasis> the ISO 9660 file system present on - the media.</para> + <para>The <acronym>DVD+RW</acronym> format supports appending + data to a previous recording. This operation consists of + merging a new session to the existing one as it is not + considered to be multi-session writing. &man.growisofs.1; + will <emphasis>grow</emphasis> the ISO 9660 file system + present on the media.</para> - <para>For example, to append data to a <acronym>DVD+RW</acronym>, use the - following:</para> + <para>For example, to append data to a + <acronym>DVD+RW</acronym>, use the following:</para> <screen>&prompt.root; <userinput>growisofs -M /dev/cd0 -J -R /path/to/nextdata</userinput></screen> @@ -1366,8 +1420,9 @@ cd0: Attempt to query device size failed <note> <para>Use <option>-dvd-compat</option> for better media - compatibility with <acronym>DVD-ROM</acronym> drives. When using <acronym>DVD+RW</acronym>, this - option will not prevent the addition of data.</para> + compatibility with <acronym>DVD-ROM</acronym> drives. When + using <acronym>DVD+RW</acronym>, this option will not + prevent the addition of data.</para> </note> <para>To blank the media, use:</para> @@ -1383,25 +1438,28 @@ cd0: Attempt to query device size failed <secondary><acronym>DVD-RW</acronym></secondary> </indexterm> - <para>A <acronym>DVD-RW</acronym> accepts two disc formats: incremental sequential - and restricted overwrite. By default, <acronym>DVD-RW</acronym> discs are in - sequential format.</para> - - <para>A virgin <acronym>DVD-RW</acronym> can be directly written without being - formatted. However, a non-virgin <acronym>DVD-RW</acronym> in sequential format *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201403212154.s2LLspGx030277>