From owner-svn-doc-all@FreeBSD.ORG Thu Apr 24 15:32:08 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 A7249E35; Thu, 24 Apr 2014 15:32:08 +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)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 879E91970; Thu, 24 Apr 2014 15:32:08 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s3OFW85g097894; Thu, 24 Apr 2014 15:32:08 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s3OFW8GD097893; Thu, 24 Apr 2014 15:32:08 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201404241532.s3OFW8GD097893@svn.freebsd.org> From: Dru Lavigne Date: Thu, 24 Apr 2014 15:32:08 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44644 - 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: Thu, 24 Apr 2014 15:32:08 -0000 Author: dru Date: Thu Apr 24 15:32:08 2014 New Revision: 44644 URL: http://svnweb.freebsd.org/changeset/doc/44644 Log: Finish editorial review of CD 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 Thu Apr 24 13:49:22 2014 (r44643) +++ head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Thu Apr 24 15:32:08 2014 (r44644) @@ -917,46 +917,23 @@ scsibus1: Using Data <acronym>CD</acronym>s - The drive can now be accessed via the - /dev/cd0 device name. For example, to - mount a CD-ROM on - /mnt, type the following: - - &prompt.root; mount -t cd9660 /dev/cd0 /mnt - - 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: - - &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: - - &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: + Once an ISO has been burned to a + CD, it can be mounted by specifying the + file system type, the name of the device containing the + CD, and an existing mount point: + + &prompt.root; mount -t cd9660 /dev/cd0 /mnt + + Since mount assumes + that a file system is of type ufs, a + Incorrect super block error will occur + if -t cd9660 is not included when mounting + a data CD. - &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 + While any data CD 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 + filenames in two-byte Unicode characters. If some non-English characters show up as question marks, specify the local charset with . For more information, refer to &man.mount.cd9660.8;. @@ -971,54 +948,51 @@ scsibus1: cd9660_iconv_load="YES" and then rebooting the machine, or by directly loading - the module with &man.kldload.8;. + the module with kldload. 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 + will be displayed when trying to mount a data + CD. This usually means that the + CD 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 + can take a couple of seconds for a CD drive to realize that a media is present, so be patient. Sometimes, a SCSI - CD-ROM may be missed because it did not + CD drive 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 - kernel. + a custom kernel can be created which increases the default + SCSI delay. Add the following option to + the custom kernel configuration file and rebuild the kernel + using the instructions in : options SCSI_DELAY=15000 This tells the SCSI bus to pause 15 - seconds during boot, to give the CD-ROM + seconds during boot, to give the CD drive every possible chance to answer the bus reset. It is possible to burn a file directly to - CD, without creating an ISO 9660 file + CD, without creating an ISO 9660 file system. This is known as burning a raw data - CD. Some people do this for backup purposes. This - command runs more quickly than burning a standard - CD. - - In order to retrieve the data burned to such a - CD, the data must be read from the raw - device node: + CD and some people do this for backup purposes. - &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 data + CD. In order to retrieve the data burned to such a + CD, the data must be read from the raw + device node. For example, this command will extract a + compressed tar file located on the second CD + device into the current working directory: + + &prompt.root; tar xzvf /dev/cd1 + + In order to mount a data + CD, the data must be written using + mkisofs. @@ -1027,18 +1001,32 @@ Update example for cdrecord 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. + CD. - - <acronym>SCSI</acronym> Drives + describes how to + duplicate and burn an audio CD. If the + &os; version is less than 10.0 and the device is + ATAPI, the module + must be first loaded using the instructions in . - - Use cdda2wav to extract the - audio: + + Duplicating an Audio <acronym>CD</acronym> - &prompt.user; cdda2wav -vall -D2,0 -B -Owav + + The sysutils/cdrecord package or + port installs cdda2wav. This command + can be used to extract all of the audio tracks, with each + track written to a separate WAV + file in the current working directory: + + &prompt.user; cdda2wav -vall -B -Owav + + A device name does not need to be specified if there + is only one CD device on the system. + Refer to the cdda2wav manual page for + instructions on how to specify a device and to learn more + about the other options available for this command. @@ -1052,59 +1040,6 @@ Update example for cdrecord linkend="cdrecord"/>. - - - <acronym>ATAPI</acronym> Drives - - - 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. - - - - 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. - - Make sure the appropriate files exist in - /dev. If the entries are missing, - force the system to retaste the media: - - &prompt.root; dd if=/dev/acd0 of=/dev/null count=1 - - - - Extract each track using &man.dd.1;, making sure to - specify a block size when extracting the files: - - &prompt.root; dd if=/dev/acd0t01 of=track1.cdr bs=2352 -&prompt.root; dd if=/dev/acd0t02 of=track2.cdr bs=2352 -... - - - - Burn the extracted files to disk using - cdrecord. Specify that these are audio - files, and that cdrecord should fixate - the disk when finished: - - -