From owner-svn-doc-all@FreeBSD.ORG Wed Apr 23 18:16:35 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 8A0858BA; Wed, 23 Apr 2014 18:16:35 +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 755DE165F; Wed, 23 Apr 2014 18:16:35 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s3NIGZ85070230; Wed, 23 Apr 2014 18:16:35 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s3NIGZQE070229; Wed, 23 Apr 2014 18:16:35 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201404231816.s3NIGZQE070229@svn.freebsd.org> From: Dru Lavigne Date: Wed, 23 Apr 2014 18:16:35 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44636 - 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: Wed, 23 Apr 2014 18:16:35 -0000 Author: dru Date: Wed Apr 23 18:16:34 2014 New Revision: 44636 URL: http://svnweb.freebsd.org/changeset/doc/44636 Log: Initial prep work for CD chapter. Move ATAPI section to beginning. This section will be reworked to describe what is needed for supported devices, including the changes for 10.x. Rename some headings to indicate the type of device it applies to. More commits to come. 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 Wed Apr 23 17:04:02 2014 (r44635) +++ head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Wed Apr 23 18:16:34 2014 (r44636) @@ -629,75 +629,126 @@ da0: <STECH Simple Drive 1.04> s/n 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 + that differentiate them from conventional disks. 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. + between tracks. While CD media do have tracks, these refer + to a section of data to be read continuously, and not a physical + property of the disk. The ISO 9660 file system was designed to deal with these + differences. - 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 + 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. - - - 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. - 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. + The &os; Ports Collection provides several utilities for + burning and duplicating audio and data CDs. + Which tool to use to burn a CD depends + on whether the CD burner is an + ATAPI, SCSI, or + USB device. This chapter demonstrates the use + of several command line utilities. For CD + burning software with a graphical, consider installing the + sysutils/xcdroast or + sysutils/k3b packages or ports. + + + + Supported Devices + + + + + Marc + Fonvieille + + Contributed by + + + + + + 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 use of + applications like sysutils/cdrdao or + &man.cdrecord.1;. + + To use this driver, add the following line to + /boot/loader.conf: + + atapicam_load="YES" + + then, reboot the system. + + + Users who prefer to statically compile &man.atapicam.4; + support into the kernel, should add this line to the + kernel configuration file: + + device atapicam + + Ensure the following lines are still in the kernel + configuration file: + + device ata +device scbus +device cd +device pass + + Then rebuild, install the new kernel, and reboot the + machine. + + + During the boot process, the burner should show up, like + so: + + acd0: CD-RW <MATSHITA CD-RW/DVD-ROM UJDA740> at ata1-master PIO4 +cd0 at ata1 bus 0 target 0 lun 0 +cd0: <MATSHITA CDRW/DVD UJDA740 1.00> Removable CD-ROM SCSI-0 device +cd0: 16.000MB/s transfers +cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed + + 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 + + As root, run 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 applications. + + For more information about ATAPI/CAM and + SCSI system, refer to &man.atapicam.4; and + &man.cam.4;. + - <application>mkisofs</application> + Creating an <acronym>ISO</acronym> File System - The sysutils/cdrtools - port also installs &man.mkisofs.8;, which produces an ISO 9660 + 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: @@ -779,7 +830,7 @@ da0: <STECH Simple Drive 1.04> s/n - <application>burncd</application> + Using an <acronym>ATAPI</acronym> Burner CD-ROMs @@ -804,7 +855,7 @@ da0: <STECH Simple Drive 1.04> s/n - <application>cdrecord</application> + Using a <acronym>USB</acronym> or <acronym>SCSI</acronym> Burner For systems without an ATAPI CD burner, cdrecord can @@ -1067,90 +1118,6 @@ scsibus1: operating system, &man.mkisofs.8; must be used as described above. - - - - Using the ATAPI/CAM Driver - - - - - Marc - Fonvieille - - Contributed by - - - - - - 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 use of - applications like sysutils/cdrdao or - &man.cdrecord.1;. - - To use this driver, add the following line to - /boot/loader.conf: - - atapicam_load="YES" - - then, reboot the system. - - - Users who prefer to statically compile &man.atapicam.4; - support into the kernel, should add this line to the - kernel configuration file: - - device atapicam - - Ensure the following lines are still in the kernel - configuration file: - - device ata -device scbus -device cd -device pass - - Then rebuild, install the new kernel, and reboot the - machine. - - - During the boot process, the burner should show up, like - so: - - acd0: CD-RW <MATSHITA CD-RW/DVD-ROM UJDA740> at ata1-master PIO4 -cd0 at ata1 bus 0 target 0 lun 0 -cd0: <MATSHITA CDRW/DVD UJDA740 1.00> Removable CD-ROM SCSI-0 device -cd0: 16.000MB/s transfers -cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed - - 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 - - As root, run 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 applications. - - For more information about ATAPI/CAM and - SCSI system, refer to &man.atapicam.4; and - &man.cam.4;. -