From owner-svn-doc-all@FreeBSD.ORG Fri Mar 21 20:55:43 2014 Return-Path: Delivered-To: svn-doc-all@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 D583EE18; Fri, 21 Mar 2014 20:55:43 +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 C11F18F; Fri, 21 Mar 2014 20:55:43 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s2LKthMo005528; Fri, 21 Mar 2014 20:55:43 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s2LKthWH005527; Fri, 21 Mar 2014 20:55:43 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201403212055.s2LKthWH005527@svn.freebsd.org> From: Dru Lavigne Date: Fri, 21 Mar 2014 20:55:43 +0000 (UTC) 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 X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Mar 2014 20:55:43 -0000 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 @@ 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 +32,7 @@ - How to configure &os; to use USB storage devices. + How to configure &os; to use USB storage devices. @@ -50,7 +50,7 @@ - How to create and burn CDs and DVDs on &os;. + How to create and burn CDs and DVDs on &os;. @@ -93,44 +93,44 @@ - IDE hard drives + IDE hard drives ad or ada - IDE CD-ROM drives + IDE CD-ROM drives acd or cd - SATA hard drives + SATA hard drives ad or ada - 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 @@ -139,12 +139,12 @@ - SCSI tape drives + SCSI tape drives sa - IDE tape drives + IDE tape drives ast @@ -402,7 +402,7 @@ super-block backups (for fsck -b #) at: - USB Storage Devices + <acronym>USB</acronym> Storage Devices @@ -420,16 +420,16 @@ super-block backups (for fsck -b #) at: disks - Many external storage solutions, such as hard drives, USB + 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. + (USB). &os; provides support for these devices. Configuration - The USB mass storage devices driver, &man.umass.4;, is + 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 + provides support for USB storage devices. For a custom kernel, be sure that the following lines are present in the kernel configuration file: @@ -442,21 +442,21 @@ 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 + 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 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;, + 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 + Since the burner is seen as a SCSI drive, the driver &man.atapicam.4; should not be used in the kernel configuration. @@ -465,7 +465,7 @@ device umass Testing the Configuration - To test the USB configuration, plug in the USB device. In + 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: @@ -479,8 +479,8 @@ 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 + 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 @@ -488,7 +488,7 @@ da0: 126MB (258048 512 byte sectors: 64H 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 + instructions on how to format and create partitions on the USB drive. @@ -511,12 +511,12 @@ da0: 126MB (258048 512 byte sectors: 64H add path 'da*' mode 0660 group operator - If SCSI disks are installed in the system, change + 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 + This will exclude the first three SCSI disks (da0 to da2)from belonging to the operator @@ -551,7 +551,7 @@ 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 + 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: @@ -584,7 +584,7 @@ umass0: detached - Creating and Using CD Media + Creating and Using <acronym>CD</acronym> Media @@ -598,22 +598,22 @@ umass0: detached - CD-ROMs + CD-ROMs creating - CD media provide a number of features that differentiate + 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 + 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. + 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 @@ -624,7 +624,7 @@ umass0: detached 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 + CDs to exceed those limits while still working with systems that do not support those extensions. @@ -638,27 +638,27 @@ umass0: detached 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 + 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 + 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 + tools for SCSI drives on ATAPI hardware with the ATAPI/CAM module. - For CD burning software with a graphical user + 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 + ATAPI/CAM module with ATAPI hardware. @@ -699,7 +699,7 @@ 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, + 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; @@ -707,14 +707,14 @@ umass0: detached of ways. - CD-ROMs + 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 + 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, + 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 @@ -748,11 +748,11 @@ umass0: detached <application>burncd</application> - CD-ROMs + 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,15 +763,15 @@ 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, + 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 @@ -794,7 +794,7 @@ umass0: detached results like this: - CD-ROMs + CD-ROMs burning &prompt.root; cdrecord -scanbus @@ -820,7 +820,7 @@ scsibus1: 1,7,0 107) * This lists the appropriate value for - the devices on the list. Locate the CD burner, and use the + 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 . @@ -830,15 +830,15 @@ scsibus1: - Duplicating Audio CDs + 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. - SCSI Drives + <acronym>SCSI</acronym> Drives Use cdda2wav to extract the @@ -860,19 +860,19 @@ scsibus1: - ATAPI Drives + <acronym>ATAPI</acronym> Drives With the help of the ATAPI/CAM module, - cdda2wav can also be used on ATAPI + 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 + The ATAPI CD driver makes each track available as /dev/acddtnn, where d is the drive number, and nn is the track number @@ -910,52 +910,52 @@ scsibus1: - Duplicating Data CDs + Duplicating Data <acronym>CD</acronym>s - It is possible to copy a data CD to an image file that is + 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 + &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 + Now that there is an image, it can be burned to CD as described above. - Using Data CDs + 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 + 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 + 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, + 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, + 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 + 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 @@ -979,13 +979,13 @@ 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 + 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 + 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,29 +993,29 @@ 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 + 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 + 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: + 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 + 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 + 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 + &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. @@ -1036,12 +1036,12 @@ scsibus1: - CD burner + CD burner ATAPI/CAM driver - This driver allows ATAPI devices, such as CD/DVD drives, - to be accessed through the SCSI subsystem, and so allows the + 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;. @@ -1082,30 +1082,30 @@ 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, + 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 + 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 + 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, + For more information about ATAPI/CAM and SCSI system, refer to &man.atapicam.4; and &man.cam.4;. - Creating and Using DVD Media + Creating and Using <acronym>DVD</acronym> Media @@ -1128,62 +1128,62 @@ cd0: Attempt to query device size failed - DVD + DVD 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: + recordable DVD: - DVD-R: This was the first DVD recordable format + DVD-R: This was the first DVD recordable format available. The DVD-R standard is defined by the - DVD + 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 + 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. + 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. + 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 + DVD+RW: This is a rewritable format defined by + the DVD+RW + Alliance. A DVD+RW can be rewritten about 1000 times. DVD+R: This format is the write once variation - of the DVD+RW format. + of the DVD+RW format. - A single layer recordable DVD can hold up to + 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 + 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. @@ -1192,19 +1192,19 @@ cd0: Attempt to query device size failed Configuration - To perform DVD recording, use &man.growisofs.1;. This + 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. + support all DVD media types. - These tools use the SCSI subsystem to access the devices, + 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. + support is not needed if the burner uses the USB interface. Refer to for more details - on USB device configuration. + on USB device configuration. - DMA access must also be enabled for ATAPI devices, by + DMA access must also be enabled for ATAPI devices, by adding the following line to /boot/loader.conf: @@ -1224,12 +1224,12 @@ cd0: Attempt to query device size failed - Burning Data DVDs + Burning Data <acronym>DVD</acronym>s 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 + 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 @@ -1245,11 +1245,11 @@ 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 + /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. + compatibility with DVD-ROM drives. To burn a pre-mastered image, such as imagefile.iso, use: @@ -1295,10 +1295,10 @@ cd0: Attempt to query device size failed - Burning a DVD-Video + Burning a <acronym>DVD</acronym>-Video - DVD + DVD DVD-Video @@ -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 multimedia/dvdauthor is - needed to author the DVD. + needed to author the DVD. 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 + 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: @@ -1323,40 +1323,40 @@ cd0: Attempt to query device size failed - Using a DVD+RW + Using a <acronym>DVD+RW</acronym> - DVD - DVD+RW + DVD + DVD+RW - Unlike CD-RW, a virgin DVD+RW needs to be formatted before + 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: + 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 + 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 + 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 + For example, to append data to a DVD+RW, use the following: &prompt.root; growisofs -M /dev/cd0 -J -R /path/to/nextdata @@ -1366,7 +1366,7 @@ cd0: Attempt to query device size failed Use for better media - compatibility with DVD-ROM drives. When using DVD+RW, this + compatibility with DVD-ROM drives. When using DVD+RW, this option will not prevent the addition of data. @@ -1376,31 +1376,31 @@ cd0: Attempt to query device size failed - Using a DVD-RW + Using a <acronym>DVD-RW</acronym> - DVD - DVD-RW + DVD + DVD-RW - A DVD-RW accepts two disc formats: incremental sequential - and restricted overwrite. By default, DVD-RW discs are in + 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 + A virgin DVD-RW can be directly written without being + formatted. However, a non-virgin DVD-RW in sequential format needs to be blanked before writing a new initial session. - To blank a DVD-RW in sequential mode: + To blank a DVD-RW in sequential mode: &prompt.root; dvd+rw-format -blank=full /dev/cd0 A full blanking using will take about one hour on a 1x media. A fast blanking can be - performed using , if the DVD-RW will - be recorded in Disk-At-Once (DAO) mode. To burn the DVD-RW + performed using , if the DVD-RW will + be recorded in Disk-At-Once (DAO) mode. To burn the DVD-RW in DAO mode, use the command: &prompt.root; growisofs -use-the-force-luke=dao -Z /dev/cd0=imagefile.iso @@ -1411,29 +1411,29 @@ cd0: Attempt to query device size failed required. One should instead use restricted overwrite mode with - any DVD-RW as this format is more flexible than the default + any DVD-RW as this format is more flexible than the default of incremental sequential. - To write data on a sequential DVD-RW, use the same - instructions as for the other DVD formats: + To write data on a sequential DVD-RW, use the same + instructions as for the other DVD formats: &prompt.root; growisofs -Z /dev/cd0 -J -R /path/to/data To append some data to a previous recording, use with &man.growisofs.1;. However, if data - is appended on a DVD-RW in incremental sequential mode, a new + is appended on a DVD-RW in incremental sequential mode, a new session will be created on the disc and the result will be a multi-session disc. - A DVD-RW in restricted overwrite format does not need to + A DVD-RW in restricted overwrite format does not need to be blanked before a new initial session. Instead, overwrite the disc with . It is also possible to grow an existing ISO 9660 file system written on the disc with . The result will be a one-session - DVD. + DVD. - To put a DVD-RW in restricted overwrite format, the + To put a DVD-RW in restricted overwrite format, the following command must be used: &prompt.root; dvd+rw-format /dev/cd0 @@ -1446,19 +1446,19 @@ cd0: Attempt to query device size failed Multi-Session - 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 + 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 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. + of multiple sessions does not exist for the DVD+RW and the + DVD-RW restricted overwrite formats. 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 DVD-RW in sequential format, will add a new session to the disc: &prompt.root; growisofs -M /dev/cd0 -J -R /path/to/nextdata - Using this command with a DVD+RW or a DVD-RW in restricted + Using this command with a DVD+RW or a DVD-RW 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 For More Information - To obtain more information about a DVD, use + To obtain more information about a DVD, use dvd+rw-mediainfo /dev/cd0 while the disc in the specified drive. @@ -1498,22 +1498,22 @@ cd0: Attempt to query device size failed - Using a DVD-RAM + Using a <acronym>DVD-RAM</acronym> - DVD - DVD-RAM + DVD + DVD-RAM - DVD-RAM writers can use either a SCSI or ATAPI - interface. For ATAPI devices, DMA access has to be + DVD-RAM writers can use either a SCSI or ATAPI + interface. For ATAPI devices, DMA access has to be enabled by adding the following line to /boot/loader.conf: hw.ata.atapi_dma="1" - A DVD-RAM can be seen as a removable hard drive. Like - any other hard drive, the DVD-RAM must be formatted before + A DVD-RAM can be seen as a removable hard drive. Like + any other hard drive, the DVD-RAM must be formatted before it can be used. In this example, the whole disk space will be formatted with a standard UFS2 file system: @@ -1521,15 +1521,15 @@ cd0: Attempt to query device size failed &prompt.root; bsdlabel -Bw acd0 &prompt.root; newfs /dev/acd0 - The DVD device, acd0, must be + The DVD device, acd0, must be changed according to the configuration. - Once the DVD-RAM has been formatted, it can be mounted + Once the DVD-RAM has been formatted, it can be mounted as a normal hard drive: &prompt.root; mount /dev/acd0 /mnt - Once mounted, the DVD-RAM will be both readable and + Once mounted, the DVD-RAM will be both readable and writeable. @@ -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. + uses SCSI, such as LTO and older devices such as DAT. There is + limited support for SATA and USB tape drives. Serial Access with &man.sa.4; @@ -2002,7 +2002,7 @@ cd0: Attempt to query device size failed - livefs CD + livefs CD 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 The installation media for &os;/&arch.i386; &rel2.current;-RELEASE does not *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***