diff --git a/en_US.ISO8859-1/books/handbook/disks/chapter.xml b/en_US.ISO8859-1/books/handbook/disks/chapter.xml index 36835d4313..062a8e6440 100644 --- a/en_US.ISO8859-1/books/handbook/disks/chapter.xml +++ b/en_US.ISO8859-1/books/handbook/disks/chapter.xml @@ -432,24 +432,24 @@ super-block backups (for fsck -b #) at: Many external storage solutions, such as hard drives, USB thumbdrives, and CD - and DVD burners, use the - Universal Serial Bus (USB). &os; provides - support for USB 1.x, 2.0, and 3.0 devices. + and DVD burners, use the Universal Serial Bus + (USB). &os; provides support for + USB 1.x, 2.0, and 3.0 devices. USB 3.0 support is not compatible with - some hardware, including Haswell (Lynx point) chipsets. If + some hardware, including Haswell (Lynx point) chipsets. If &os; boots with a failed with error 19 message, disable xHCI/USB3 in the system BIOS. - - Support for USB storage devices - is built into the GENERIC - kernel. For a custom kernel, be sure that the following - lines are present in the kernel configuration file: - device scbus # SCSI bus (required for ATA/SCSI) + Support for USB storage devices is built + into the GENERIC kernel. For a custom + kernel, be sure that the following lines are present in the + kernel configuration file: + + device scbus # SCSI bus (required for ATA/SCSI) device da # Direct Access (disks) device pass # Passthrough device (direct ATA/SCSI access) device uhci # provides USB 1.x support @@ -460,15 +460,15 @@ device usb # USB Bus (required) device umass # Disks/Mass storage - Requires scbus and da device cd # needed for CD and DVD burners - &os; uses the &man.umass.4; driver which uses the - SCSI subsystem to access - USB storage devices. Since any - USB device will be seen as a - SCSI device by the system, - if the USB device is a - CD or DVD burner, do - not include - in a custom kernel configuration file. + &os; uses the &man.umass.4; driver which uses the + SCSI subsystem to access + USB storage devices. Since any + USB device will be seen as a + SCSI device by the system, if the + USB device is a CD or + DVD burner, do not + include in a custom kernel + configuration file. The rest of this section demonstrates how to verify that a USB storage device is recognized by &os; and @@ -480,15 +480,15 @@ device cd # needed for CD and DVD burners To test the USB configuration, plug in the USB device. Use dmesg to confirm that the drive appears in - the system message buffer. It should look something - like this: + the system message buffer. It should look something like + this: umass0: <STECH Simple Drive, class 0/0, rev 2.00/1.04, addr 3> on usbus0 umass0: SCSI over Bulk-Only; quirks = 0x0100 umass0:4:0:-1: Attached to scbus4 da0 at umass-sim0 bus 0 scbus4 target 0 lun 0 -da0: <STECH Simple Drive 1.04> Fixed Direct Access SCSI-4 device -da0: Serial Number WD-WXE508CAN263 +da0: <STECH Simple Drive 1.04> Fixed Direct Access SCSI-4 device +da0: Serial Number WD-WXE508CAN263 da0: 40.000MB/s transfers da0: 152627MB (312581808 512 byte sectors: 255H 63S/T 19457C) da0: quirks=0x2<NO_6_BYTE> @@ -511,36 +511,36 @@ da0: quirks=0x2<NO_6_BYTE> &prompt.root; usbconfig ugen0.3: <Simple Drive STECH> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (2mA) - If the device has not been formatted, - refer to for instructions on - how to format and create partitions on the - USB drive. If the drive comes with a file - system, it can be mounted by root using the + If the device has not been formatted, refer to for instructions on how to format + and create partitions on the USB drive. If + the drive comes with a file system, it can be mounted by + root using the instructions in . Allowing untrusted users to mount arbitrary media, by - enabling vfs.usermount as - described below, should not be considered safe from a - security point of view. Most file systems were not - built to safeguard against malicious devices. + enabling vfs.usermount as described + below, should not be considered safe from a security point + of view. Most file systems were not built to safeguard + against malicious devices. To make the device mountable as a normal user, one solution is to make all users of the device a member of the operator group using &man.pw.8;. Next, ensure that operator is able to - read and write the device by adding these lines to + class="groupname">operator is able to read and + write the device by adding these lines to /etc/devfs.rules: [localrules=5] add path 'da*' mode 0660 group operator - If internal SCSI disks are also installed in the - system, change the second line as follows: + If internal SCSI disks are also + installed in the system, change the second line as + follows: add path 'da[3-9]*' mode 0660 group operator @@ -558,9 +558,8 @@ add path 'da*' mode 0660 group operator devfs_system_ruleset="localrules" - Then, instruct the system to allow regular users - to mount file systems by adding the - following line to + Then, instruct the system to allow regular users to mount + file systems by adding the following line to /etc/sysctl.conf: vfs.usermount=1 @@ -568,7 +567,7 @@ add path 'da*' mode 0660 group operator Since this only takes effect after the next reboot, use sysctl to set this variable now: - &prompt.root; sysctl vfs.usermount=1 + &prompt.root; sysctl vfs.usermount=1 vfs.usermount: 0 -> 1 The final step is to create a directory where the file @@ -587,19 +586,18 @@ vfs.usermount: 0 -> 1 Suppose a USB thumbdrive is plugged in, and a device /dev/da0s1 appears. If the - device is formatted with a FAT file system, the user can - mount it using: + device is formatted with a FAT file system, + the user can mount it using: &prompt.user; mount -t msdosfs -o -m=644,-M=755 /dev/da0s1 /mnt/username Before the device can be unplugged, it - must be unmounted first: + must be unmounted first: &prompt.user; umount /mnt/username - - After device - removal, the system message buffer will show messages similar - to the following: + + After device removal, the system message buffer will show + messages similar to the following: umass0: at uhub3, port 2, addr 3 (disconnected) da0 at umass-sim0 bus 0 scbus4 target 0 lun 0 @@ -629,14 +627,16 @@ da0: <STECH Simple Drive 1.04> s/n WD-WXE508CAN263 detached 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. + 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 + ISO + 9660 file systems ISO 9660 @@ -652,10 +652,10 @@ da0: <STECH Simple Drive 1.04> s/n WD-WXE508CAN263 detached 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 + 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. @@ -713,23 +713,23 @@ device umass # Disks/Mass storage - Requires scbus and da device ata # Legacy ATA/SATA controllers device scbus # SCSI bus (required for ATA/SCSI) device pass # Passthrough device (direct ATA/SCSI access) -device cd # needed for CD and DVD burners - +device cd # needed for CD and DVD burners On &os; versions prior to 10.x, this line is also - needed in the kernel configuration file if the burner is an - ATAPI device: + needed in the kernel configuration file if the burner is an + ATAPI device: device atapicam - Alternately, this driver can be loaded at boot time by adding the following line to - /boot/loader.conf: + Alternately, this driver can be loaded at boot time by + adding the following line to + /boot/loader.conf: - atapicam_load="YES" + atapicam_load="YES" - This will require a reboot of the system as this driver - can only be loaded at boot time. + This will require a reboot of the system as this driver + can only be loaded at boot time. To verify that &os; recognizes the device, run @@ -740,27 +740,25 @@ device cd # needed for CD and DVD burners &prompt.user; dmesg | grep cd cd0 at ahcich1 bus 0 scbus1 target 0 lun 0 -cd0: <HL-DT-ST DVDRAM GU70N LT20> Removable CD-ROM SCSI-0 device +cd0: <HL-DT-ST DVDRAM GU70N LT20> Removable CD-ROM SCSI-0 device cd0: Serial Number M3OD3S34152 cd0: 150.000MB/s transfers (SATA 1.x, UDMA6, ATAPI 12bytes, PIO 8192bytes) -cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed - +cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed Burning a <acronym>CD</acronym> - In &os;, cdrecord can - be used to burn CDs. This command is - installed with the + In &os;, cdrecord can be used to burn + CDs. This command is installed with the sysutils/cdrtools package or port. &os; 8.x includes the built-in - burncd utility for burning - CDs using an ATAPI - CD burner. Refer to the manual page for - burncd for usage examples. + burncd utility for burning + CDs using an ATAPI + CD burner. Refer to the manual page for + burncd for usage examples. While cdrecord has many options, basic @@ -809,9 +807,10 @@ scsibus1: easier 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 burner: + Alternately, 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) @@ -824,12 +823,14 @@ scsibus1: Creating 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: + 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: &prompt.root; mkisofs -o imagefile.iso /path/to/tree @@ -2027,7 +2028,7 @@ Update example for cdrecord include a rescue shell. For this version, instead download and burn a Livefs CD image from ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/&arch.i386;/ISO-IMAGES/&rel2.current;/&os;-&rel2.current;-RELEASE-&arch.i386;-livefs.iso. + xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/&arch.i386;/ISO-IMAGES/&rel2.current;/&os;-&rel2.current;-RELEASE-&arch.i386;-livefs.iso">ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/&arch.i386;/ISO-IMAGES/&rel2.current;/&os;-&rel2.current;-RELEASE-&arch.i386;-livefs.iso. Next, test the rescue shell and the backups. Make notes