From owner-svn-doc-head@FreeBSD.ORG Fri Mar 21 21:54:51 2014 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A6B82230; Fri, 21 Mar 2014 21:54:51 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 92BE8861; Fri, 21 Mar 2014 21:54:51 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s2LLsp1s030278; Fri, 21 Mar 2014 21:54:51 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s2LLspGx030277; Fri, 21 Mar 2014 21:54:51 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201403212154.s2LLspGx030277@svn.freebsd.org> From: Dru Lavigne Date: Fri, 21 Mar 2014 21:54:51 +0000 (UTC) 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 X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Mar 2014 21:54:51 -0000 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 @@ 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. + storage devices, and devices using the USB + interface. After reading this chapter, you will know: @@ -32,7 +33,8 @@ - How to configure &os; to use USB storage devices. + How to configure &os; to use USB + storage devices. @@ -50,7 +52,8 @@ - How to create and burn CDs and DVDs on &os;. + How to create and burn CDs and + DVDs on &os;. @@ -99,7 +102,8 @@ - IDE CD-ROM drives + IDE CD-ROM + drives acd or cd @@ -111,26 +115,32 @@ - SATA CD-ROM drives + SATA CD-ROM + drives acd or cd - SCSI hard drives and USB Mass storage + SCSI hard drives and + USB Mass storage devices da - SCSI CD-ROM drives + SCSI CD-ROM + drives cd - Assorted non-standard CD-ROM drives - mcd for Mitsumi CD-ROM and - scd for Sony CD-ROM devices + Assorted non-standard CD-ROM + drives + mcd for Mitsumi + CD-ROM and + scd for Sony + CD-ROM devices @@ -420,18 +430,19 @@ super-block backups (for fsck -b #) at: disks - Many external storage solutions, such as hard drives, USB - thumbdrives, and CD/DVD burners, use the Universal Serial Bus - (USB). &os; provides support for these devices. + Many external storage solutions, such as hard drives, + USB thumbdrives, and CD/DVD burners, use the + Universal Serial Bus (USB). &os; provides + support for these devices. Configuration - The USB mass storage devices driver, &man.umass.4;, is - built into the GENERIC kernel and - provides support for USB storage devices. For a custom - kernel, be sure that the following lines are present in the - kernel configuration file: + The USB mass storage devices driver, + &man.umass.4;, is built into the GENERIC + kernel and provides support for USB storage + devices. For a custom kernel, be sure that the following + lines are present in the kernel configuration file: device scbus device da @@ -442,32 +453,38 @@ device ehci device usb device umass - 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 - the motherboard, device uhci or - device ohci is used to provide USB 1.X - support. Support for USB 2.0 controllers is provided by + 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 the motherboard, + device uhci or + device ohci is used to provide + USB 1.X support. Support for + USB 2.0 controllers is provided by device ehci. - If the USB device is a CD or DVD burner, &man.cd.4;, - must be added to the kernel via the line: + If the USB device is a + CD or DVD burner, + &man.cd.4;, must be added to the kernel via the line: device cd - Since the burner is seen as a SCSI drive, the driver - &man.atapicam.4; should not be used in the kernel - configuration. + Since the burner is seen as a SCSI + drive, the driver &man.atapicam.4; should not be used in the + kernel configuration. Testing the Configuration - To test the USB configuration, plug in the USB device. In - the system message buffer, &man.dmesg.8;, the drive should - appear as something like: + To test the USB configuration, plug in + the USB device. In the system message + buffer, &man.dmesg.8;, the drive should appear as something + like: 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 The brand, device node (da0), and other details will differ according to the device. - Since the USB device is seen as a SCSI one, - camcontrol can be used to list the USB - storage devices attached to the system: + Since the USB device is seen as a + SCSI one, camcontrol can + be used to list the USB storage devices + attached to the system: &prompt.root; camcontrol devlist <Generic Traveling Disk 1.11> at scbus0 target 0 lun 0 (da0,pass0) If the drive comes with a file system, it can be mounted. - Refer to for - instructions on how to format and create partitions on the USB - drive. + Refer to for instructions on + how to format and create partitions on the + USB drive. Allowing untrusted users to mount arbitrary media, by @@ -502,25 +520,24 @@ da0: 126MB (258048 512 byte sectors: 64H To make the device mountable as a normal user, one solution is to make all users of the device a member of the operator group - using &man.pw.8;. Next, ensure that the - operator group is - able to read and write the device by adding these lines to + using &man.pw.8;. Next, ensure that the operator group is able to + read and write the device by adding these lines to /etc/devfs.rules: [localrules=5] add path 'da*' mode 0660 group operator - If SCSI disks are installed in the system, change - the second line as follows: + If SCSI disks are installed in the + system, change the second line as follows: add path 'da[3-9]*' mode 0660 group operator - This will exclude the first three SCSI disks - (da0 to - da2)from belonging to the - operator - group. + This will exclude the first three + SCSI disks (da0 to + da2)from belonging to the operator group. Next, enable the &man.devfs.rules.5; ruleset in @@ -551,10 +568,10 @@ add path 'da*' mode 0660 group operator< &prompt.root; mkdir /mnt/username &prompt.root; chown username:usergroup /mnt/username - Suppose a USB thumbdrive is plugged in, and a device - /dev/da0s1 appears. If the device is - preformatted with a FAT file system, it can be mounted - using: + Suppose a USB thumbdrive is plugged in, + and a device /dev/da0s1 appears. If the + device is preformatted with a FAT file system, it can be + mounted using: &prompt.user; mount -t msdosfs -o -m=644,-M=755 /dev/da0s1 /mnt/username @@ -602,64 +619,70 @@ umass0: detached creating - CD 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. - - CD 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. + CD 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. + + CD 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. - ISO 9660 - - file systems - ISO 9660 - + ISO 9660 + + file systems + ISO 9660 + - 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 - that do not support those extensions. + 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 that do not support those + extensions. - - sysutils/cdrtools - + + sysutils/cdrtools + - The sysutils/cdrtools - 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. + The sysutils/cdrtools 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. - - CD burner - ATAPI - + + CD burner + ATAPI + - Which tool to use to burn the CD depends on whether the - CD burner is ATAPI or something else. ATAPI CD burners use - burncd which is part of the base system. - SCSI and USB CD burners should use cdrecord - from the sysutils/cdrtools port. It is - also possible to use cdrecord and other - tools for SCSI drives on ATAPI hardware with the - ATAPI/CAM module. - - For CD burning software with a graphical user - interface, consider X-CD-Roast or - K3b. These tools are available as - packages or from the sysutils/xcdroast and - sysutils/k3b ports. - X-CD-Roast and - K3b require the - ATAPI/CAM module with ATAPI - hardware. + Which tool to use to burn the CD depends + on whether the CD burner is + ATAPI or something else. + ATAPI CD burners use + burncd which is part of the base system. + SCSI and USB + CD burners should use + cdrecord from the + sysutils/cdrtools port. It is also possible + to use cdrecord and other tools for + SCSI drives on ATAPI + hardware with the ATAPI/CAM + module. + + For CD burning software with a graphical + user interface, consider X-CD-Roast + or K3b. These tools are available as + packages or from the sysutils/xcdroast and + sysutils/k3b ports. + X-CD-Roast and + K3b require the ATAPI/CAM module with + ATAPI hardware. <application>mkisofs</application> @@ -699,27 +722,29 @@ umass0: detached Microsoft systems, and can be used to create HFS file systems used by &macos;. - For CDs that are going to be used only on &os; systems, - can be used to disable all filename - restrictions. When used with , 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. + For CDs that are going to be used only + on &os; systems, can be used to disable + all filename restrictions. When used with + , 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. CD-ROMs creating bootable + The last option of general use is . This is used to specify the location of the boot image for use - in producing an El Torito bootable CD. 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, - &man.mkisofs.8; creates an ISO image in - floppy disk emulation 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 El Torito bootable + CD. 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, + &man.mkisofs.8; creates an ISO image in floppy disk + emulation 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, should be used. So, if /tmp/myboot holds a bootable &os; system with the boot image in @@ -751,8 +776,9 @@ umass0: detached CD-ROMs burning - For an ATAPI CD burner, burncd can be - used to burn an ISO image onto a CD. + For an ATAPI CD + burner, burncd can be used to burn an ISO + image onto a CD. burncd is part of the base system, installed as /usr/sbin/burncd. Usage is very simple, as it has few options: @@ -763,24 +789,26 @@ umass0: detached imagefile.iso on cddevice. The default device is /dev/acd0. See &man.burncd.8; for - options to set the write speed, eject the CD after burning, - and write audio data. + options to set the write speed, eject the + CD after burning, and write audio + data. <application>cdrecord</application> - For systems without an ATAPI CD burner, - cdrecord can be used to burn CDs. + For systems without an ATAPI + CD burner, cdrecord can + be used to burn CDs. cdrecord is not part of the base system and must be installed from either the sysutils/cdrtools package or port. Changes to the base system can cause binary versions of this program to fail, possibly resulting in a coaster. It is recommended to either upgrade the port when the system is - upgraded, or for users - tracking -STABLE, to upgrade the - port when a new version becomes available. + upgraded, or for users tracking + -STABLE, to upgrade the port when a new version + becomes available. While cdrecord has many options, basic usage is simple. Burning an ISO 9660 image is done @@ -820,21 +848,23 @@ scsibus1: 1,7,0 107) * This lists the appropriate value for - the devices on the list. Locate the CD burner, and use the - three numbers separated by commas as the value for - . In this case, the CRW device is 1,5,0, - so the appropriate input is . - Refer to &man.cdrecord.1; for easier ways to specify this - value and for information on writing audio tracks and - controlling the write speed. + the devices on the list. Locate the CD + burner, and use the three numbers separated by commas as the + value for . In this case, the CRW device + is 1,5,0, so the appropriate input is + . Refer to &man.cdrecord.1; for + easier ways to specify this value and for information on + writing audio tracks and controlling the write speed. Duplicating Audio <acronym>CD</acronym>s - 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 + 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 drives. @@ -854,8 +884,8 @@ scsibus1: &prompt.user; cdrecord -v dev=2,0 -dao -useinfo *.wav Make sure that 2,0 is set - appropriately, as described in - . + appropriately, as described in . @@ -865,19 +895,21 @@ scsibus1: With the help of the ATAPI/CAM module, - cdda2wav can also be used on ATAPI - drives. This tool is usually a better choice for most of - users, as it supports jitter correction and endianness, - than the method proposed below. + cdda2wav can also be used on + ATAPI drives. This tool is usually a + better choice for most of users, as it supports jitter + correction and endianness, than the method proposed + below. - The ATAPI CD driver makes each track available as - /dev/acddtnn, - where d is the drive number, - and nn is the track number - written with two decimal digits, prefixed with zero as - needed. So the first track on the first disk is + The ATAPI CD + driver makes each track available as + /dev/acddtnn, where + d is the drive number, and + nn is the track number written + with two decimal digits, prefixed with zero as needed. So + the first track on the first disk is /dev/acd0t01, the second is /dev/acd0t02, the third is /dev/acd0t03, and so on. @@ -912,58 +944,59 @@ scsibus1: Duplicating Data <acronym>CD</acronym>s - It is possible to copy a data CD 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 - acd0. Substitute the correct CD-ROM - device. + It is possible to copy a data CD 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 + acd0. Substitute the correct + CD-ROM device. &prompt.root; dd if=/dev/acd0 of=file.iso bs=2048 - Now that there is an image, it can be burned to CD as - described above. + Now that there is an image, it can be burned to + CD as described above. Using Data <acronym>CD</acronym>s It is possible to mount and read the data on a standard - data CD. By default, &man.mount.8; assumes that a file system - is of type ufs. Running this - command: + data CD. By default, &man.mount.8; assumes + that a file system is of type ufs. Running + this command: &prompt.root; mount /dev/cd0 /mnt will generate an error about Incorrect super - block, and will fail to mount the CD. The CD - does not use the UFS file system, so - attempts to mount it as such will fail. Instead, tell - &man.mount.8; that the file system is of type - ISO9660 by specifying - to &man.mount.8;. For example, - to mount the CD-ROM device, /dev/cd0, - under /mnt, - use: + block, and will fail to mount the + CD. The CD does not use + the UFS file system, so attempts to mount + it as such will fail. Instead, tell &man.mount.8; that the + file system is of type ISO9660 by + specifying to &man.mount.8;. For + example, to mount the CD-ROM device, + /dev/cd0, under + /mnt, use: &prompt.root; mount -t cd9660 /dev/cd0 /mnt Replace /dev/cd0 with the device - name for the CD device. Also, - executes &man.mount.cd9660.8;, meaning the above command is - equivalent to: + name for the CD device. Also, + executes &man.mount.cd9660.8;, + meaning the above command is equivalent to: &prompt.root; mount_cd9660 /dev/cd0 /mnt - While data CD-ROMs 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 - . For more information, refer to - &man.mount.cd9660.8;. + While data CD-ROMs 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 . For more information, refer + to &man.mount.cd9660.8;. In order to do this character conversion with the help @@ -979,13 +1012,16 @@ scsibus1: Occasionally, Device not configured - will be displayed when trying to mount a CD-ROM. This - usually means that the CD-ROM 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 - that a media is present, so be patient. + will be displayed when trying to mount a + CD-ROM. This usually means that the + CD-ROM 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 that a media is present, so be + patient. - Sometimes, a SCSI CD-ROM may be missed because it did not + Sometimes, a SCSI + CD-ROM 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 rebuild the @@ -993,31 +1029,34 @@ scsibus1: options SCSI_DELAY=15000 - This tells the SCSI bus to pause 15 seconds during boot, - to give the CD-ROM drive every possible chance to answer the - bus reset. + This tells the SCSI bus to pause 15 + seconds during boot, to give the CD-ROM + drive every possible chance to answer the bus reset. Burning Raw Data CDs - It is possible to burn a file directly to CD, without - creating an ISO 9660 file system. Some people do this for - backup purposes. This command runs more quickly than burning - a standard CD: + It is possible to burn a file directly to + CD, without creating an ISO 9660 file + system. Some people do this for backup purposes. This + command runs more quickly than burning a standard + CD: &prompt.root; burncd -f /dev/acd1 -s 12 data archive.tar.gz fixate - In order to retrieve the data burned to such a CD, the - data must be read from the raw device node: + In order to retrieve the data burned to such a + CD, the data must be read from the raw + device node: &prompt.root; tar xzvf /dev/acd1 - This type of disk can not be mounted as a normal CD-ROM - and the data cannot be read under any operating system except - &os;. In order to mount the CD, or to share the data with - another operating system, &man.mkisofs.8; must be used as - described above. + This type of disk can not be mounted as a normal + CD-ROM and the data cannot be read under + any operating system except &os;. In order to mount the + CD, or to share the data with another + operating system, &man.mkisofs.8; must be used as described + above. @@ -1040,9 +1079,10 @@ scsibus1: ATAPI/CAM driver - This driver allows ATAPI devices, such as CD/DVD drives, - to be accessed through the SCSI subsystem, and so allows the - use of applications like sysutils/cdrdao or + This driver allows ATAPI devices, such + as CD/DVD drives, to be accessed through the + SCSI subsystem, and so allows the use of + applications like sysutils/cdrdao or &man.cdrecord.1;. To use this driver, add the following line to @@ -1082,24 +1122,25 @@ cd0: Attempt to query device size failed The drive can now be accessed via the /dev/cd0 device name. For example, to - mount a CD-ROM on /mnt, - type the following: + mount a CD-ROM on + /mnt, type the following: &prompt.root; mount -t cd9660 /dev/cd0 /mnt As root, run the - following command to get the SCSI address of the - burner: + following command to get the SCSI address + of the burner: &prompt.root; camcontrol devlist <MATSHITA CDRW/DVD UJDA740 1.00> at scbus1 target 0 lun 0 (pass0,cd0) - In this example, 1,0,0 is the SCSI - address to use with &man.cdrecord.1; and other SCSI - applications. - - For more information about ATAPI/CAM and SCSI system, - refer to &man.atapicam.4; and &man.cam.4;. + In this example, 1,0,0 is the + SCSI address to use with &man.cdrecord.1; + and other SCSI applications. + + For more information about ATAPI/CAM and + SCSI system, refer to &man.atapicam.4; and + &man.cam.4;. @@ -1132,41 +1173,48 @@ cd0: Attempt to query device size failed burning - 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. + 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. Five physical recordable formats can be defined for a recordable DVD: - DVD-R: This was the first DVD recordable format - available. The DVD-R standard is defined by the - DVD + DVD-R: This was the first DVD + recordable format available. The DVD-R standard is + defined by the DVD Forum. This format is write once. - DVD-RW: This is the rewritable version of the - DVD-R standard. A DVD-RW can be rewritten about 1000 + DVD-RW: This is the rewritable + version of the DVD-R standard. A + DVD-RW can be rewritten about 1000 times. - DVD-RAM: 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. - Refer to for more - information on DVD-RAM use. + DVD-RAM: 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. Refer to for more information on + DVD-RAM use. - DVD+RW: This is a rewritable format defined by - the DVD+RW - Alliance. A DVD+RW can be rewritten about 1000 - times. + DVD+RW: This is a rewritable format + defined by the DVD+RW + Alliance. A DVD+RW can be + rewritten about 1000 times. @@ -1175,38 +1223,39 @@ cd0: Attempt to query device size failed - A single layer recordable DVD can hold up to - 4,700,000,000 bytes which is actually 4.38 GB or - 4485 MB as 1 kilobyte is 1024 bytes. + A single layer recordable DVD can hold + up to 4,700,000,000 bytes which is actually 4.38 GB + or 4485 MB as 1 kilobyte is 1024 bytes. 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 - choosing the type of media, ensure that both the burner and - the DVD-Video player are compatible with the media under - consideration. + file layout that can be written on any recordable + DVD physical media such as DVD-R, DVD+R, + or DVD-RW. Before choosing the type of + media, ensure that both the burner and the DVD-Video player + are compatible with the media under consideration. Configuration - To perform DVD recording, use &man.growisofs.1;. This - command is part of the + To perform DVD recording, use + &man.growisofs.1;. This command is part of the sysutils/dvd+rw-tools utilities which support all DVD media types. - These tools use the SCSI subsystem to access the devices, - therefore ATAPI/CAM support - must be loaded or statically compiled into the kernel. This - support is not needed if the burner uses the USB interface. - Refer to for more details - on USB device configuration. - - DMA access must also be enabled for ATAPI devices, by - adding the following line to - /boot/loader.conf: + These tools use the SCSI subsystem to + access the devices, therefore ATAPI/CAM support must be loaded + or statically compiled into the kernel. This support is not + needed if the burner uses the USB + interface. Refer to for more + details on USB device configuration. + + DMA access must also be enabled for + ATAPI devices, by adding the following line + to /boot/loader.conf: hw.ata.atapi_dma="1" @@ -1226,15 +1275,16 @@ cd0: Attempt to query device size failed Burning Data <acronym>DVD</acronym>s - Since &man.growisofs.1; is a front-end to - mkisofs, it will invoke + Since &man.growisofs.1; is a front-end to mkisofs, 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 - does not need to be created before the burning process. + the write on the DVD. This means that an + image of the data does not need to be created before the + burning process. To burn to a DVD+R or a DVD-R the data in - /path/to/data, - use the following command: + /path/to/data, use the following + command: &prompt.root; growisofs -dvd-compat -Z /dev/cd0 -J -R /path/to/data @@ -1245,11 +1295,12 @@ cd0: Attempt to query device size failed For the initial session recording, is used for both single and multiple sessions. Replace - /dev/cd0, with the name of the DVD - device. Using 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. + /dev/cd0, with the name of the + DVD device. Using + 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. To burn a pre-mastered image, such as imagefile.iso, use: @@ -1310,9 +1361,10 @@ cd0: Attempt to query device size failed If an image of the DVD-Video file system already exists, it can be burned in the same way as any other image. If - dvdauthor was used to make the DVD and the - result is in /path/to/video, the - following command should be used to burn the DVD-Video: + dvdauthor was used to make the + DVD and the result is in + /path/to/video, the following command + should be used to burn the DVD-Video: &prompt.root; growisofs -Z /dev/cd0 -dvd-video /path/to/video @@ -1330,34 +1382,36 @@ cd0: Attempt to query device size failed DVD+RW - Unlike CD-RW, a virgin DVD+RW needs to be formatted before - first use. It is recommended to let - &man.growisofs.1; take care of this automatically whenever - appropriate. However, it is possible to use - dvd+rw-format to format the DVD+RW: + Unlike CD-RW, a virgin DVD+RW needs to + be formatted before first use. It is + recommended to let &man.growisofs.1; take + care of this automatically whenever appropriate. However, it + is possible to use dvd+rw-format to format + the DVD+RW: &prompt.root; dvd+rw-format /dev/cd0 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. + only virgin DVD+RW medias need to be + formatted. Once formatted, the DVD+RW can + be burned as usual. 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 - first. Instead, write over the previous recording like - this: + data onto a DVD+RW, the media does not need + to be blanked first. Instead, write over the previous + recording like this: &prompt.root; growisofs -Z /dev/cd0 -J -R /path/to/newdata - The DVD+RW 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 - grow the ISO 9660 file system present on - the media. + The DVD+RW 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 grow the ISO 9660 file system + present on the media. - For example, to append data to a DVD+RW, use the - following: + For example, to append data to a + DVD+RW, use the following: &prompt.root; growisofs -M /dev/cd0 -J -R /path/to/nextdata @@ -1366,8 +1420,9 @@ cd0: Attempt to query device size failed Use for better media - compatibility with DVD-ROM drives. When using DVD+RW, this - option will not prevent the addition of data. + compatibility with DVD-ROM drives. When + using DVD+RW, this option will not + prevent the addition of data. To blank the media, use: @@ -1383,25 +1438,28 @@ cd0: Attempt to query device size failed DVD-RW - A DVD-RW accepts two disc formats: incremental sequential - and restricted overwrite. By default, DVD-RW discs are in - sequential format. - - A virgin DVD-RW can be directly written without being - formatted. However, a non-virgin DVD-RW in sequential format *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***