From owner-svn-doc-all@FreeBSD.ORG Thu Apr 24 13:16:40 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DF2E2CCB; Thu, 24 Apr 2014 13:16:39 +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 CA2E3174A; Thu, 24 Apr 2014 13:16:39 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s3ODGdJi040322; Thu, 24 Apr 2014 13:16:39 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s3ODGd3h040320; Thu, 24 Apr 2014 13:16:39 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201404241316.s3ODGd3h040320@svn.freebsd.org> From: Dru Lavigne Date: Thu, 24 Apr 2014 13:16:39 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44642 - in head/en_US.ISO8859-1/books: faq 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 13:16:40 -0000 Author: dru Date: Thu Apr 24 13:16:39 2014 New Revision: 44642 URL: http://svnweb.freebsd.org/changeset/doc/44642 Log: Editorial review of Burning CDs and Creating ISO File sections. Add data CDs as a note and modify reference to new location in FAQ. Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/faq/book.xml head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Modified: head/en_US.ISO8859-1/books/faq/book.xml ============================================================================== --- head/en_US.ISO8859-1/books/faq/book.xml Thu Apr 24 11:36:42 2014 (r44641) +++ head/en_US.ISO8859-1/books/faq/book.xml Thu Apr 24 13:16:39 2014 (r44642) @@ -3383,7 +3383,7 @@ C:\="DOS" - This is discussed in the Handbook section on duplicating data CDs. + This is discussed in the Handbook section on duplicating data CDs. For more on working with CD-ROMs, see the Creating CDs Section in the Storage chapter in the Handbook. Modified: head/en_US.ISO8859-1/books/handbook/disks/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Thu Apr 24 11:36:42 2014 (r44641) +++ head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Thu Apr 24 13:16:39 2014 (r44642) @@ -759,14 +759,15 @@ cd0: Attempt to query device size failed While cdrecord has many options, basic - usage is simple. Burning an ISO 9660 image is done - with: + usage is simple. Specify the name of the + ISO file to burn and, if the system has + multiple burner devices, specify the name of the device to + use: - &prompt.root; cdrecord dev=device imagefile.iso + &prompt.root; cdrecord dev=device imagefile.iso - The tricky part of using cdrecord is - finding the to use. To find the proper - setting, use which might produce + To determine the device name of the burner, + use which might produce results like this: @@ -774,8 +775,8 @@ cd0: Attempt to query device size failed burning &prompt.root; cdrecord -scanbus -Cdrecord-Clone 2.01 (i386-unknown-freebsd7.0) Copyright (C) 1995-2004 Jörg Schilling -Using libscg version 'schily-0.1' +ProDVD-ProBD-Clone 3.00 (amd64-unknown-freebsd10.0) Copyright (C) 1995-2010 Jörg Schilling +Using libscg version 'schily-0.9' scsibus0: 0,0,0 0) 'SEAGATE ' 'ST39236LW ' '0004' Disk 0,1,0 1) 'SEAGATE ' 'ST39173W ' '5958' Disk @@ -795,39 +796,40 @@ scsibus1: 1,6,0 106) 'ARTEC ' 'AM12S ' '1.06' Scanner 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 + Locate the entry for the CD + burner and use the three numbers separated by commas as the + value for . In this case, the Yamaha burner device + is 1,5,0, so the appropriate input to specify that device is + . Refer to the manual page for cdrecord for + other ways to specify this value and for information on writing audio tracks and controlling the write speed. - Alternately, as root, run the following - command to get the SCSI address of the + Alternately, run the following + command to get the device address of the burner: &prompt.root; camcontrol devlist -<MATSHITA CDRW/DVD UJDA740 1.00> at scbus1 target 0 lun 0 (pass0,cd0) +<MATSHITA CDRW/DVD UJDA740 1.00> at scbus1 target 0 lun 0 (cd0,pass0) - In this example, 1,0,0 is the - SCSI address to use with &man.cdrecord.1; - and other SCSI applications. + Use the numeric values for scbus, + target, and lun. For + this example, 1,0,0 is the + device name to use. - Creating an <acronym>ISO</acronym> File System + Writing Data to an <acronym>ISO</acronym> File System In order to produce a data CD, the data files that are going to make up the tracks on the - CD must be prepared then written to the - CD. In &os;, the - sysutils/cdrtools package or port installs - mkisofs, which produces an ISO 9660 file - system that is an image of a directory tree in the &unix; file - system name space. The simplest usage is: + CD must be prepared before they can be burned to the + CD. In &os;, + sysutils/cdrtools installs + mkisofs, which can be used to produce an ISO 9660 file + system that is an image of a directory tree within a &unix; file + system. The simplest usage is to specify the name of the + ISO file to create and the path to the files + to place into the ISO 9660 file system: &prompt.root; mkisofs -o imagefile.iso /path/to/tree @@ -836,35 +838,27 @@ scsibus1: ISO 9660 - This command creates an - imagefile.iso containing an ISO - 9660 file system that is a copy of the tree at - /path/to/tree. In the process, it - maps the file names to names that fit the limitations of - the standard ISO 9660 file system, and will exclude files that - have names uncharacteristic of ISO file systems. + This command + maps the file names in the specified path to names that fit the limitations of + the standard ISO 9660 file system, and will exclude files that + do not meet the standard for ISO file systems. file systems - HFS - - - file systems Joliet - A number of options are available to overcome these - restrictions. In particular, enables the - Rock Ridge extensions common to &unix; systems, + A number of options are available to overcome the + restrictions imposed by the standard. In particular, enables the + Rock Ridge extensions common to &unix; systems and enables Joliet extensions used by - Microsoft systems, and can be used to - create HFS file systems used by &macos;. + Microsoft 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; tree, though it may violate - the ISO 9660 standard in a number of ways. + identical to the specified &os; tree, even if it violates + the ISO 9660 standard. CD-ROMs @@ -872,27 +866,26 @@ scsibus1: The last option of general use is . - This is used to specify the location of the boot image for use + This is used to specify the location of a 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 + mkisofs 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 + loaders, like the one used by the &os; distribution media, 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 /tmp/myboot/boot/cdboot, this command - would produce the image of an ISO 9660 file system as + would produce /tmp/bootable.iso: &prompt.root; mkisofs -R -no-emul-boot -b boot/cdboot -o /tmp/bootable.iso /tmp/myboot - If md is configured in the - kernel, the file system can be mounted as a memory disk + The resulting ISO image can be mounted as a memory disk with: &prompt.root; mdconfig -a -t vnode -f /tmp/bootable.iso -u 0 @@ -902,8 +895,23 @@ scsibus1: /tmp/myboot are identical. There are many other options available for - &man.mkisofs.8; to fine-tune its behavior. Refer to + mkisofs to fine-tune its behavior. Refer to &man.mkisofs.8; for details. + + + It is possible to copy a data CD to an + image file that is functionally equivalent to the image file + created with mkisofs. To do so, use + dd with the device name as the input file + and the name of the ISO to create as the + output file: + + &prompt.root; dd if=/dev/cd0 of=file.iso bs=2048 + + The resulting image file can be burned to + CD as described in . + @@ -992,23 +1000,6 @@ Update example for cdrecord - - 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. - - &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. - - Using Data <acronym>CD</acronym>s