From owner-svn-doc-all@FreeBSD.ORG Thu Apr 24 20:14:15 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 754EDD1F; Thu, 24 Apr 2014 20:14:15 +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 606EA1917; Thu, 24 Apr 2014 20:14:15 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s3OKEF6x017190; Thu, 24 Apr 2014 20:14:15 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s3OKEF7m017189; Thu, 24 Apr 2014 20:14:15 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201404242014.s3OKEF7m017189@svn.freebsd.org> From: Dru Lavigne Date: Thu, 24 Apr 2014 20:14:15 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44649 - 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 20:14:15 -0000 Author: dru Date: Thu Apr 24 20:14:14 2014 New Revision: 44649 URL: http://svnweb.freebsd.org/changeset/doc/44649 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 Thu Apr 24 19:51:56 2014 (r44648) +++ head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Thu Apr 24 20:14:14 2014 (r44649) @@ -34,7 +34,8 @@ - How to grow the size of a disk's partition on &os;. + How to grow the size of a disk's partition on + &os;. @@ -53,8 +54,7 @@ - How to set up memory - disks. + How to set up memory disks. @@ -72,7 +72,8 @@ - How to configure a highly available storage network. + How to configure a highly available storage + network. @@ -635,14 +636,14 @@ da0: <STECH Simple Drive 1.04> s/n creating - Compact Disc (CD) media provide a number of features - that differentiate them from conventional disks. They are - designed so that they can be read continuously without delays to - move the head 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. + Compact Disc (CD) media provide a number + of features that differentiate them from conventional disks. + They are designed so that they can be read continuously without + delays to move the head 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. ISO 9660 @@ -658,10 +659,10 @@ da0: <STECH Simple Drive 1.04> s/n The &os; Ports Collection provides several utilities for burning and duplicating audio and data CDs. - This chapter demonstrates the - use of several command line utilities. For - CD burning software with a graphical utility, - consider installing the sysutils/xcdroast or + This chapter demonstrates the use of several command line + utilities. For CD burning software with a + graphical utility, consider installing the + sysutils/xcdroast or sysutils/k3b packages or ports. @@ -775,9 +776,9 @@ cd0: Attempt to query device size failed &prompt.root; cdrecord dev=device imagefile.iso - To determine the device name of the burner, - use which might produce - results like this: + To determine the device name of the burner, use + which might produce results like + this: CD-ROMs @@ -805,40 +806,42 @@ scsibus1: 1,6,0 106) 'ARTEC ' 'AM12S ' '1.06' Scanner 1,7,0 107) * - 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, run the following - command to get the device address of the - burner: + 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, 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 (cd0,pass0) Use the numeric values for scbus, target, and lun. For - this example, 1,0,0 is the - device name to use. + this example, 1,0,0 is the device name to + use. - Writing Data to 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 before they can be burned to the - CD. In &os;, + 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: + 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 @@ -847,27 +850,29 @@ scsibus1: ISO 9660 - 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. + 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 Joliet + 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. + restrictions imposed by the standard. In particular, + enables the Rock Ridge extensions common + to &unix; systems and enables Joliet + extensions used by 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, even if it violates - the ISO 9660 standard. + identical to the specified &os; tree, even if it violates the + ISO 9660 standard. CD-ROMs @@ -880,22 +885,22 @@ scsibus1: 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, - 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 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 + 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 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 /tmp/bootable.iso: &prompt.root; mkisofs -R -no-emul-boot -b boot/cdboot -o /tmp/bootable.iso /tmp/myboot - The resulting ISO image can be mounted as a memory disk - with: + The resulting ISO image can be mounted + as a memory disk with: &prompt.root; mdconfig -a -t vnode -f /tmp/bootable.iso -u 0 &prompt.root; mount -t cd9660 /dev/md0 /mnt @@ -904,23 +909,23 @@ scsibus1: /tmp/myboot are identical. There are many other options available for - mkisofs to fine-tune its behavior. Refer to - &man.mkisofs.8; for details. + 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: + 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 . - + The resulting image file can be burned to + CD as described in . + @@ -933,14 +938,14 @@ scsibus1: &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. + 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. - While any data CD 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. If some non-English characters show up as question marks, specify the local @@ -963,8 +968,8 @@ scsibus1: Occasionally, Device not configured 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 + 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 drive to realize that a media is present, so be patient. @@ -985,32 +990,35 @@ scsibus1: 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 - system. This is known as burning a raw data - CD and some people do this for backup purposes. - - 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. - + It is possible to burn a file directly to + CD, without creating an + ISO 9660 file system. This is known as + burning a raw data CD and some people do + this for backup purposes. + + 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. + 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. + CD. describes how to duplicate and burn an audio CD. If the @@ -1026,11 +1034,11 @@ scsibus1: 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: + 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 @@ -1049,7 +1057,7 @@ scsibus1: linkend="cdrecord"/>. - + @@ -1988,19 +1996,19 @@ scsibus1: - In addition to physical disks, &os; also supports - the creation and use of memory disks. One possible use for a + In addition to physical disks, &os; also supports the + creation and use of memory disks. One possible use for a memory disk is to access the contents of an ISO file system without the overhead of first burning it to a CD or DVD, then mounting the CD/DVD media. - - In &os;, the &man.md.4; driver is used to provide support - for memory disks. The GENERIC kernel - includes this driver. When using a custom kernel - configuration file, ensure it includes this line: - device md + In &os;, the &man.md.4; driver is used to provide support + for memory disks. The GENERIC kernel + includes this driver. When using a custom kernel configuration + file, ensure it includes this line: + + device md Attaching and Detaching Existing Images @@ -2020,26 +2028,26 @@ scsibus1: /dev/md0 then mounts that memory device on /mnt: - &prompt.root; mdconfig -f diskimage.iso -u 0 + &prompt.root; mdconfig -f diskimage.iso -u 0 &prompt.root; mount /dev/md0 /mnt If a unit number is not specified with , mdconfig will automatically allocate an unused memory device and output - the name of the allocated unit, such - as md4. Refer to &man.mdconfig.8; - for more details about this command and its options. + the name of the allocated unit, such as + md4. Refer to &man.mdconfig.8; for more + details about this command and its options. disks detaching a memory disk - When a memory disk is no - longer in use, its resources should be released back to - the system. First, unmount the file system, then use - mdconfig to detach the disk from the system and - release its resources. To continue this example: + When a memory disk is no longer in use, its resources + should be released back to the system. First, unmount the + file system, then use mdconfig to detach + the disk from the system and release its resources. To + continue this example: &prompt.root; umount /mnt &prompt.root; mdconfig -d -u 0 @@ -2070,7 +2078,7 @@ scsibus1: the UFS file system before it is mounted: - &prompt.root; mdconfig -a -t swap -s 5m -u 1 + &prompt.root; mdconfig -a -t swap -s 5m -u 1 &prompt.root; newfs -U md1 /dev/md1: 5.0MB (10240 sectors) block size 16384, fragment size 2048 using 4 cylinder groups of 1.27MB, 81 blks, 192 inodes. @@ -2082,12 +2090,11 @@ super-block backups (for fsck -b #) at: Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/md1 4718 4 4338 0% /mnt - - To create a new file-backed memory disk, first allocate an + To create a new file-backed memory disk, first allocate an area of disk to use. This example creates an empty 5K file named newimage: - &prompt.root; dd if=/dev/zero of=newimage bs=1k count=5k + &prompt.root; dd if=/dev/zero of=newimage bs=1k count=5k 5120+0 records in 5120+0 records out @@ -2095,7 +2102,7 @@ Filesystem 1K-blocks Used Avail Capacity disk and format it with the UFS file system, mount the memory disk, and verify the size of the file-backed disk: - + &prompt.root; mdconfig -f newimage -u 0 &prompt.root; bsdlabel -w md0 auto &prompt.root; newfs md0a @@ -2108,28 +2115,28 @@ super-block backups (for fsck -b #) at: Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/md0a 4710 4 4330 0% /mnt - It takes several commands to create a file- or memory-backed file - system using mdconfig. &os; also - comes with mdmfs which automatically configures a - memory disk, formats it with the UFS file system, - and mounts it. For example, after creating - newimage with - dd, this one command is equivalent to + It takes several commands to create a file- or + memory-backed file system using mdconfig. + &os; also comes with mdmfs which + automatically configures a memory disk, formats it with the + UFS file system, and mounts it. For + example, after creating newimage + with dd, this one command is equivalent to running the bsdlabel, newfs, and mount commands shown above: - &prompt.root; mdmfs -F newimage -s 5m md0 /mnt + &prompt.root; mdmfs -F newimage -s 5m md0 /mnt To instead create a new memory-based memory disk with - mdmfs, use this one command: + mdmfs, use this one command: + + &prompt.root; mdmfs -s 5m md1 /mnt - &prompt.root; mdmfs -s 5m md1 /mnt - - If the unit number is not specified, - mdmfs will - automatically select an unused memory device. For more details - about mdmfs, refer to &man.mdmfs.8;. + If the unit number is not specified, + mdmfs will automatically select an unused + memory device. For more details about + mdmfs, refer to &man.mdmfs.8;.