Date: Fri, 21 Mar 2014 20:55:43 +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: r44324 - head/en_US.ISO8859-1/books/handbook/disks Message-ID: <201403212055.s2LKthWH005527@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: dru Date: Fri Mar 21 20:55:43 2014 New Revision: 44324 URL: http://svnweb.freebsd.org/changeset/doc/44324 Log: Add acronym tags to Storage chapter. 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 20:34:38 2014 (r44323) +++ head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Fri Mar 21 20:55:43 2014 (r44324) @@ -16,7 +16,7 @@ <para>This chapter covers the use of disks in &os;. This includes memory-backed disks, network-attached disks, standard SCSI/IDE - storage devices, and devices using the USB interface.</para> + storage devices, and devices using the <acronym>USB</acronym> interface.</para> <para>After reading this chapter, you will know:</para> @@ -32,7 +32,7 @@ </listitem> <listitem> - <para>How to configure &os; to use USB storage devices.</para> + <para>How to configure &os; to use <acronym>USB</acronym> storage devices.</para> </listitem> <listitem> @@ -50,7 +50,7 @@ </listitem> <listitem> - <para>How to create and burn CDs and DVDs on &os;.</para> + <para>How to create and burn <acronym>CD</acronym>s and <acronym>DVD</acronym>s on &os;.</para> </listitem> <listitem> @@ -93,44 +93,44 @@ <tbody> <row> - <entry>IDE hard drives</entry> + <entry><acronym>IDE</acronym> hard drives</entry> <entry><literal>ad</literal> or <literal>ada</literal></entry> </row> <row> - <entry>IDE CD-ROM drives</entry> + <entry><acronym>IDE</acronym> <acronym>CD-ROM</acronym> drives</entry> <entry><literal>acd</literal> or <literal>cd</literal></entry> </row> <row> - <entry>SATA hard drives</entry> + <entry><acronym>SATA</acronym> hard drives</entry> <entry><literal>ad</literal> or <literal>ada</literal></entry> </row> <row> - <entry>SATA CD-ROM drives</entry> + <entry><acronym>SATA</acronym> <acronym>CD-ROM</acronym> drives</entry> <entry><literal>acd</literal> or <literal>cd</literal></entry> </row> <row> - <entry>SCSI hard drives and USB Mass storage + <entry><acronym>SCSI</acronym> hard drives and <acronym>USB</acronym> Mass storage devices</entry> <entry><literal>da</literal></entry> </row> <row> - <entry>SCSI CD-ROM drives</entry> + <entry><acronym>SCSI</acronym> <acronym>CD-ROM</acronym> drives</entry> <entry><literal>cd</literal></entry> </row> <row> - <entry>Assorted non-standard CD-ROM drives</entry> - <entry><literal>mcd</literal> for Mitsumi CD-ROM and - <literal>scd</literal> for Sony CD-ROM 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> @@ -139,12 +139,12 @@ </row> <row> - <entry>SCSI tape drives</entry> + <entry><acronym>SCSI</acronym> tape drives</entry> <entry><literal>sa</literal></entry> </row> <row> - <entry>IDE tape drives</entry> + <entry><acronym>IDE</acronym> tape drives</entry> <entry><literal>ast</literal></entry> </row> @@ -402,7 +402,7 @@ super-block backups (for fsck -b #) at: <sect1 xml:id="usb-disks"> <info> - <title>USB Storage Devices</title> + <title><acronym>USB</acronym> Storage Devices</title> <authorgroup> <author> @@ -420,16 +420,16 @@ super-block backups (for fsck -b #) at: <secondary>disks</secondary> </indexterm> - <para>Many external storage solutions, such as hard drives, USB + <para>Many external storage solutions, such as hard drives, <acronym>USB</acronym> thumbdrives, and CD/DVD burners, use the Universal Serial Bus - (USB). &os; provides support for these devices.</para> + (<acronym>USB</acronym>). &os; provides support for these devices.</para> <sect2> <title>Configuration</title> - <para>The USB mass storage devices driver, &man.umass.4;, is + <para>The <acronym>USB</acronym> mass storage devices driver, &man.umass.4;, is built into the <filename>GENERIC</filename> kernel and - provides support for USB storage devices. For a custom + 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> @@ -442,21 +442,21 @@ device ehci device usb device umass</programlisting> - <para>Since the &man.umass.4; driver uses the SCSI subsystem to - access the USB storage devices, any USB device will be seen as - a SCSI device by the system. Depending on the USB chipset on + <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 USB 1.X - support. Support for USB 2.0 controllers is provided by + <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 USB device is a CD or DVD burner, &man.cd.4;, + <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 SCSI drive, the driver + <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> @@ -465,7 +465,7 @@ device umass</programlisting> <sect2> <title>Testing the Configuration</title> - <para>To test the USB configuration, plug in the USB device. In + <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> @@ -479,8 +479,8 @@ 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 USB device is seen as a SCSI one, - <command>camcontrol</command> can be used to list the USB + <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> @@ -488,7 +488,7 @@ da0: 126MB (258048 512 byte sectors: 64H <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 USB + instructions on how to format and create partitions on the <acronym>USB</acronym> drive.</para> <warning> @@ -511,12 +511,12 @@ da0: 126MB (258048 512 byte sectors: 64H add path 'da*' mode 0660 group operator</programlisting> <note> - <para>If SCSI disks are installed in the system, change + <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 SCSI disks + <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> @@ -551,7 +551,7 @@ 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 USB thumbdrive is plugged in, and a device + <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> @@ -584,7 +584,7 @@ umass0: detached</screen> <sect1 xml:id="creating-cds"> <info> - <title>Creating and Using CD Media</title> + <title>Creating and Using <acronym>CD</acronym> Media</title> <authorgroup> <author> @@ -598,22 +598,22 @@ umass0: detached</screen> </info> <indexterm> - <primary>CD-ROMs</primary> + <primary><acronym>CD-ROM</acronym>s</primary> <secondary>creating</secondary> </indexterm> - <para>CD media provide a number of features that differentiate + <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>CD media do have tracks, but this refers to a section of + <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 CD on &os;, prepare the - data files that are going to make up the tracks on the CD, - then write the tracks to the CD.</para> + 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> @@ -624,7 +624,7 @@ umass0: detached</screen> <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 - CDs to exceed those limits while still working with systems + <acronym>CD</acronym>s to exceed those limits while still working with systems that do not support those extensions.</para> <indexterm> @@ -638,27 +638,27 @@ umass0: detached</screen> below.</para> <indexterm> - <primary>CD burner</primary> - <secondary>ATAPI</secondary> + <primary><acronym>CD</acronym> burner</primary> + <secondary><acronym>ATAPI</acronym></secondary> </indexterm> - <para>Which tool to use to burn the CD depends on whether the - CD burner is ATAPI or something else. ATAPI CD burners use + <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. - SCSI and USB CD burners should use <command>cdrecord</command> + <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 SCSI drives on ATAPI hardware with the + tools for <acronym>SCSI</acronym> drives on <acronym>ATAPI</acronym> hardware with the <link linkend="atapicam">ATAPI/CAM module</link>.</para> - <para>For CD burning software with a graphical user + <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 ATAPI + <link linkend="atapicam">ATAPI/CAM module</link> with <acronym>ATAPI</acronym> hardware.</para> <sect2 xml:id="mkisofs"> @@ -699,7 +699,7 @@ umass0: detached</screen> Microsoft systems, and <option>-hfs</option> can be used to create HFS file systems used by &macos;.</para> - <para>For CDs that are going to be used only on &os; systems, + <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; @@ -707,14 +707,14 @@ umass0: detached</screen> of ways.</para> <indexterm> - <primary>CD-ROMs</primary> + <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 CD. This + 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 CD. By default, + 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 @@ -748,11 +748,11 @@ umass0: detached</screen> <title><application>burncd</application></title> <indexterm> - <primary>CD-ROMs</primary> + <primary><acronym>CD-ROM</acronym>s</primary> <secondary>burning</secondary> </indexterm> - <para>For an ATAPI CD burner, <command>burncd</command> can be - used to burn an ISO image onto a CD. + <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,15 +763,15 @@ 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 CD after burning, + 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 ATAPI CD burner, - <command>cdrecord</command> can be used to burn CDs. + <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 @@ -794,7 +794,7 @@ umass0: detached</screen> results like this:</para> <indexterm> - <primary>CD-ROMs</primary> + <primary><acronym>CD-ROM</acronym>s</primary> <secondary>burning</secondary> </indexterm> <screen>&prompt.root; <userinput>cdrecord -scanbus</userinput> @@ -820,7 +820,7 @@ scsibus1: 1,7,0 107) *</screen> <para>This lists the appropriate <option>dev</option> value for - the devices on the list. Locate the CD burner, and use the + 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>. @@ -830,15 +830,15 @@ scsibus1: </sect2> <sect2 xml:id="duplicating-audiocds"> - <title>Duplicating Audio CDs</title> + <title>Duplicating Audio <acronym>CD</acronym>s</title> - <para>To duplicate an audio CD, extract the audio data from the - CD to a series of files, then write these files to a blank CD. - The process is slightly different for ATAPI and SCSI + <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> - <title>SCSI Drives</title> + <title><acronym>SCSI</acronym> Drives</title> <step> <para>Use <command>cdda2wav</command> to extract the @@ -860,19 +860,19 @@ scsibus1: </procedure> <procedure> - <title>ATAPI Drives</title> + <title><acronym>ATAPI</acronym> Drives</title> <note> <para>With the help of the <link linkend="atapicam">ATAPI/CAM module</link>, - <command>cdda2wav</command> can also be used on ATAPI + <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 ATAPI CD driver makes each track available as + <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 @@ -910,52 +910,52 @@ scsibus1: </sect2> <sect2 xml:id="imaging-cd"> - <title>Duplicating Data CDs</title> + <title>Duplicating Data <acronym>CD</acronym>s</title> - <para>It is possible to copy a data CD to an image file that is + <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 CD. - The example given here assumes that the CD-ROM device is - <filename>acd0</filename>. Substitute the correct CD-ROM + &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 CD as + <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 CDs</title> + <title>Using Data <acronym>CD</acronym>s</title> <para>It is possible to mount and read the data on a standard - data CD. By default, &man.mount.8; assumes that a file system + 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 CD. The CD + 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 CD-ROM device, <filename>/dev/cd0</filename>, + 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 CD device. Also, <option>-t cd9660</option> + 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 CD-ROMs from any vendor can be mounted this + <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 @@ -979,13 +979,13 @@ scsibus1: </note> <para>Occasionally, <errorname>Device not configured</errorname> - will be displayed when trying to mount a CD-ROM. This - usually means that the CD-ROM drive thinks that there is no + 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 CD-ROM drive to realize + 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 SCSI CD-ROM 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,29 +993,29 @@ scsibus1: <programlisting>options SCSI_DELAY=15000</programlisting> - <para>This tells the SCSI bus to pause 15 seconds during boot, - to give the CD-ROM drive every possible chance to answer the + <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 CD, without + <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 CD:</para> + 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 CD, the + <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 CD-ROM + <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 CD, or to share the data with + &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> @@ -1036,12 +1036,12 @@ scsibus1: </info> <indexterm> - <primary>CD burner</primary> + <primary><acronym>CD</acronym> burner</primary> <secondary>ATAPI/CAM driver</secondary> </indexterm> - <para>This driver allows ATAPI devices, such as CD/DVD drives, - to be accessed through the SCSI subsystem, and so allows the + <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> @@ -1082,30 +1082,30 @@ 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 CD-ROM on <filename>/mnt</filename>, + 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 SCSI address of 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 SCSI - address to use with &man.cdrecord.1; and other SCSI + <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 SCSI system, + <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"> <info> - <title>Creating and Using DVD Media</title> + <title>Creating and Using <acronym>DVD</acronym> Media</title> <authorgroup> <author> @@ -1128,62 +1128,62 @@ cd0: Attempt to query device size failed </info> <indexterm> - <primary>DVD</primary> + <primary><acronym>DVD</acronym></primary> <secondary>burning</secondary> </indexterm> - <para>Compared to the CD, the DVD is the next generation of - optical media storage technology. The DVD can hold more data - than any CD 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 DVD:</para> + recordable <acronym>DVD</acronym>:</para> <itemizedlist> <listitem> - <para>DVD-R: This was the first DVD recordable format + <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">DVD + <link xlink:href="http://www.dvdforum.com/forum.shtml"><acronym>DVD</acronym>; Forum</link>. This format is write once.</para> </listitem> <listitem> - <para>DVD-RW: This is the rewritable version of the - DVD-R standard. A DVD-RW 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>DVD-RAM: This is a rewritable format which can be seen + <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 DVD-ROM drives and DVD-Video players - as only a few DVD writers support the DVD-RAM format. + 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 DVD-RAM use.</para> + information on <acronym>DVD-RAM</acronym> use.</para> </listitem> <listitem> - <para>DVD+RW: This is a rewritable format defined by - the <link xlink:href="http://www.dvdrw.com/">DVD+RW - Alliance</link>. A DVD+RW can be rewritten about 1000 + <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> <para>DVD+R: This format is the write once variation - of the DVD+RW format.</para> + of the <acronym>DVD+RW</acronym> format.</para> </listitem> </itemizedlist> - <para>A single layer recordable DVD can hold up to + <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 DVD - physical media such as DVD-R, DVD+R, or DVD-RW. Before + 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> @@ -1192,19 +1192,19 @@ cd0: Attempt to query device size failed <sect2> <title>Configuration</title> - <para>To perform DVD recording, use &man.growisofs.1;. This + <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 DVD media types.</para> + support all <acronym>DVD</acronym> media types.</para> - <para>These tools use the SCSI subsystem to access the devices, + <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 USB interface. + support is not needed if the burner uses the <acronym>USB</acronym> interface. Refer to <xref linkend="usb-disks"/> for more details - on USB device configuration.</para> + on <acronym>USB</acronym> device configuration.</para> - <para>DMA access must also be enabled for ATAPI devices, by + <para>DMA access must also be enabled for <acronym>ATAPI</acronym> devices, by adding the following line to <filename>/boot/loader.conf</filename>:</para> @@ -1224,12 +1224,12 @@ cd0: Attempt to query device size failed </sect2> <sect2> - <title>Burning Data DVDs</title> + <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 &man.mkisofs.8; to create the file system layout and perform - the write on the DVD. This means that an image of the data + 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 @@ -1245,11 +1245,11 @@ 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 DVD + <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 DVD-ROM drives.</para> + compatibility with <acronym>DVD-ROM</acronym> drives.</para> <para>To burn a pre-mastered image, such as <replaceable>imagefile.iso</replaceable>, use:</para> @@ -1295,10 +1295,10 @@ cd0: Attempt to query device size failed </sect2> <sect2> - <title>Burning a DVD-Video</title> + <title>Burning a <acronym>DVD</acronym>-Video</title> <indexterm> - <primary>DVD</primary> + <primary><acronym>DVD</acronym></primary> <secondary>DVD-Video</secondary> </indexterm> @@ -1306,11 +1306,11 @@ cd0: Attempt to query device size failed 9660 and micro-UDF (M-UDF) specifications. Since DVD-Video presents a specific data structure hierarchy, a particular program such as <package>multimedia/dvdauthor</package> is - needed to author the DVD.</para> + needed to author the <acronym>DVD</acronym>.</para> <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 DVD and the + <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> @@ -1323,40 +1323,40 @@ cd0: Attempt to query device size failed </sect2> <sect2> - <title>Using a DVD+RW</title> + <title>Using a <acronym>DVD+RW</acronym></title> <indexterm> - <primary>DVD</primary> - <secondary>DVD+RW</secondary> + <primary><acronym>DVD</acronym></primary> + <secondary><acronym>DVD+RW</acronym></secondary> </indexterm> - <para>Unlike CD-RW, a virgin DVD+RW needs to be formatted before + <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 DVD+RW:</para> + <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 DVD+RW medias need to be formatted. Once - formatted, the DVD+RW 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 DVD+RW, the media does not need to be blanked + 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 DVD+RW format supports appending data to a previous + <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 DVD+RW, use the + <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,7 +1366,7 @@ cd0: Attempt to query device size failed <note> <para>Use <option>-dvd-compat</option> for better media - compatibility with DVD-ROM drives. When using DVD+RW, this + compatibility with <acronym>DVD-ROM</acronym> drives. When using <acronym>DVD+RW</acronym>, this option will not prevent the addition of data.</para> </note> @@ -1376,31 +1376,31 @@ cd0: Attempt to query device size failed </sect2> <sect2> - <title>Using a DVD-RW</title> + <title>Using a <acronym>DVD-RW</acronym></title> <indexterm> - <primary>DVD</primary> - <secondary>DVD-RW</secondary> + <primary><acronym>DVD</acronym></primary> + <secondary><acronym>DVD-RW</acronym></secondary> </indexterm> - <para>A DVD-RW accepts two disc formats: incremental sequential - and restricted overwrite. By default, DVD-RW discs are in + <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 DVD-RW can be directly written without being - formatted. However, a non-virgin DVD-RW in sequential format + <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 needs to be blanked before writing a new initial session.</para> - <para>To blank a DVD-RW in sequential mode:</para> + <para>To blank a <acronym>DVD-RW</acronym> in sequential mode:</para> <screen>&prompt.root; <userinput>dvd+rw-format -blank=full /dev/cd0</userinput></screen> <note> <para>A full blanking using <option>-blank=full</option> will take about one hour on a 1x media. A fast blanking can be - performed using <option>-blank</option>, if the DVD-RW will - be recorded in Disk-At-Once (DAO) mode. To burn the DVD-RW + performed using <option>-blank</option>, if the <acronym>DVD-RW</acronym> will + be recorded in Disk-At-Once (DAO) mode. To burn the <acronym>DVD-RW</acronym> in DAO mode, use the command:</para> <screen>&prompt.root; <userinput>growisofs -use-the-force-luke=dao -Z /dev/cd0=imagefile.iso</userinput></screen> @@ -1411,29 +1411,29 @@ cd0: Attempt to query device size failed required.</para> <para>One should instead use restricted overwrite mode with - any DVD-RW as this format is more flexible than the default + any <acronym>DVD-RW</acronym> as this format is more flexible than the default of incremental sequential.</para> </note> - <para>To write data on a sequential DVD-RW, use the same - instructions as for the other DVD formats:</para> + <para>To write data on a sequential <acronym>DVD-RW</acronym>, use the same + instructions as for the other <acronym>DVD</acronym> formats:</para> <screen>&prompt.root; <userinput>growisofs -Z /dev/cd0 -J -R /path/to/data</userinput></screen> <para>To append some data to a previous recording, use <option>-M</option> with &man.growisofs.1;. However, if data - is appended on a DVD-RW in incremental sequential mode, a new + is appended on a <acronym>DVD-RW</acronym> in incremental sequential mode, a new session will be created on the disc and the result will be a multi-session disc.</para> - <para>A DVD-RW in restricted overwrite format does not need to + <para>A <acronym>DVD-RW</acronym> in restricted overwrite format does not need to be blanked before a new initial session. Instead, overwrite the disc with <option>-Z</option>. It is also possible to grow an existing ISO 9660 file system written on the disc with <option>-M</option>. The result will be a one-session - DVD.</para> + <acronym>DVD</acronym>.</para> - <para>To put a DVD-RW in restricted overwrite format, the + <para>To put a <acronym>DVD-RW</acronym> in restricted overwrite format, the following command must be used:</para> <screen>&prompt.root; <userinput>dvd+rw-format /dev/cd0</userinput></screen> @@ -1446,19 +1446,19 @@ cd0: Attempt to query device size failed <sect2> <title>Multi-Session</title> - <para>Few DVD-ROM drives support multi-session DVDs and most of - the time only read the first session. DVD+R, DVD-R and DVD-RW + <para>Few <acronym>DVD-ROM</acronym> drives support multi-session DVDs and most of + the time only read the first session. DVD+R, DVD-R and <acronym>DVD-RW</acronym> in sequential format can accept multiple sessions. The notion - of multiple sessions does not exist for the DVD+RW and the - DVD-RW restricted overwrite formats.</para> + of multiple sessions does not exist for the <acronym>DVD+RW</acronym> and the + <acronym>DVD-RW</acronym> restricted overwrite formats.</para> <para>Using the following command after an initial non-closed - session on a DVD+R, DVD-R, or DVD-RW in sequential format, + session on a DVD+R, DVD-R, or <acronym>DVD-RW</acronym> in sequential format, will add a new session to the disc:</para> <screen>&prompt.root; <userinput>growisofs -M /dev/cd0 -J -R /path/to/nextdata</userinput></screen> - <para>Using this command with a DVD+RW or a DVD-RW in restricted + <para>Using this command with a <acronym>DVD+RW</acronym> or a <acronym>DVD-RW</acronym> in restricted overwrite mode will append data while merging the new session to the existing one. The result will be a single-session disc. Use this method to add data after an initial write on @@ -1477,7 +1477,7 @@ cd0: Attempt to query device size failed <sect2> <title>For More Information</title> - <para>To obtain more information about a DVD, use + <para>To obtain more information about a <acronym>DVD</acronym>, use <command>dvd+rw-mediainfo /dev/cd0</command> while the disc in the specified drive.</para> @@ -1498,22 +1498,22 @@ cd0: Attempt to query device size failed </sect2> <sect2 xml:id="creating-dvd-ram"> - <title>Using a DVD-RAM</title> + <title>Using a <acronym>DVD-RAM</acronym></title> <indexterm> - <primary>DVD</primary> - <secondary>DVD-RAM</secondary> + <primary><acronym>DVD</acronym></primary> + <secondary><acronym>DVD-RAM</acronym></secondary> </indexterm> - <para>DVD-RAM writers can use either a SCSI or ATAPI - interface. For ATAPI devices, DMA access has to be + <para><acronym>DVD-RAM</acronym> writers can use either a <acronym>SCSI</acronym> or <acronym>ATAPI</acronym> + interface. For <acronym>ATAPI</acronym> devices, DMA access has to be enabled by adding the following line to <filename>/boot/loader.conf</filename>:</para> <programlisting>hw.ata.atapi_dma="1"</programlisting> - <para>A DVD-RAM can be seen as a removable hard drive. Like - any other hard drive, the DVD-RAM must be formatted before + <para>A <acronym>DVD-RAM</acronym> can be seen as a removable hard drive. Like + any other hard drive, the <acronym>DVD-RAM</acronym> must be formatted before it can be used. In this example, the whole disk space will be formatted with a standard UFS2 file system:</para> @@ -1521,15 +1521,15 @@ cd0: Attempt to query device size failed &prompt.root; <userinput>bsdlabel -Bw acd0</userinput> &prompt.root; <userinput>newfs /dev/acd0</userinput></screen> - <para>The DVD device, <filename>acd0</filename>, must be + <para>The <acronym>DVD</acronym> device, <filename>acd0</filename>, must be changed according to the configuration.</para> - <para>Once the DVD-RAM has been formatted, it can be mounted + <para>Once the <acronym>DVD-RAM</acronym> has been formatted, it can be mounted as a normal hard drive:</para> <screen>&prompt.root; <userinput>mount /dev/acd0 /mnt</userinput></screen> - <para>Once mounted, the DVD-RAM will be both readable and + <para>Once mounted, the <acronym>DVD-RAM</acronym> will be both readable and writeable.</para> </sect2> </sect1> @@ -1618,8 +1618,8 @@ cd0: Attempt to query device size failed to be used in a modern system. Modern backup systems tend to use off site combined with local removable disk drive technologies. Still, &os; will support any tape drive that - uses SCSI, such as LTO and older devices such as DAT. There is - limited support for SATA and USB tape drives.</para> + uses <acronym>SCSI</acronym>, such as LTO and older devices such as DAT. There is + limited support for <acronym>SATA</acronym> and <acronym>USB</acronym> tape drives.</para> <sect2 xml:id="tapes-sa0"> <title>Serial Access with &man.sa.4;</title> @@ -2002,7 +2002,7 @@ cd0: Attempt to query device size failed </listitem> </itemizedlist> - <indexterm><primary>livefs CD</primary></indexterm> + <indexterm><primary>livefs <acronym>CD</acronym></primary></indexterm> <para>Store this printout and a copy of the installation media in a secure location. Should an emergency restore be needed, boot into the installation media and select @@ -2015,7 +2015,7 @@ cd0: Attempt to query device size failed <para>The installation media for &os;/&arch.i386; &rel2.current;-RELEASE does not *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201403212055.s2LKthWH005527>