Index: en_US.ISO8859-1/books/handbook/disks/chapter.sgml =================================================================== RCS file: /home/hiten/ncvs/doc/en_US.ISO8859-1/books/handbook/disks/chapter.sgml,v retrieving revision 1.129 diff -u -r1.129 chapter.sgml --- en_US.ISO8859-1/books/handbook/disks/chapter.sgml 15 Dec 2002 16:51:52 -0000 1.129 +++ en_US.ISO8859-1/books/handbook/disks/chapter.sgml 5 Jan 2003 23:12:47 -0000 @@ -70,7 +70,7 @@ ad - IDE CDROM drives + IDE CD-ROM drives acd @@ -78,11 +78,11 @@ da - SCSI CDROM drives + SCSI CD-ROM drives cd - Assorted non-standard CDROM drives + Assorted non-standard CD-ROM drives mcd for Mitsumi CD-ROM, scd for Sony CD-ROM, matcd for Matsushita/Panasonic CD-ROM @@ -371,7 +371,7 @@ To sum it up, I need something that will give me the most amount of storage space for my money. The cost of large IDE disks are cheap these days. I found a place that was selling Western - Digital 30.7gb 5400 RPM IDE disks for about one-hundred and thirty + Digital 30.7GB 5400 RPM IDE disks for about one-hundred and thirty US dollars. I bought three of them, giving me approximately ninety gigabytes of online storage. @@ -383,7 +383,7 @@ would be for each IDE disk to have its own IDE controller and cable, but without fronting more costs to acquire a dual IDE controller this would not be a possibility. So, I - jumpered two disks as slaves, and one as master. One went + jumper ed two disks as slaves, and one as master. One went on the first IDE controller as a slave to the system disk, and the other two where slave/master on the secondary IDE controller. @@ -398,7 +398,7 @@ ad3: 29333MB <WDC WD307AA> [59598/16/63] at ata1-slave UDMA33 At this point, if FreeBSD does not detect the disks, be - sure that you have jumpered them correctly. I have heard + sure that you have jumper-ed them correctly. I have heard numerous reports with problems using cable select instead of true slave/master configuration. @@ -434,7 +434,7 @@ later. To set up ccd, first I need - to disklabel the disks. Here is how I disklabeled + to disklabel the disks. Here is how I disklabel-ed them: disklabel -r -w ad1 auto @@ -685,7 +685,7 @@ Creating and Using Optical Media (CDs & DVDs) - CDROMs + CD-ROMs creating @@ -768,12 +768,12 @@ file systems - Joliet + JOLIET A number of options are available to overcome those restrictions. In particular, enables the Rock Ridge extensions common to Unix systems, - enables Joliet extensions used by Microsoft systems, and + enables JOLIET extensions used by Microsoft systems, and can be used to create HFS file systems used by MacOS. @@ -785,7 +785,7 @@ ways. - CDROMs + CD-ROMs creating bootable The last option of general use is . This is @@ -819,14 +819,14 @@ There are many other options you can use with sysutils/mkisofs to fine-tune its behavior. In particular: - modifications to an ISO 9660 layout and the creation of Joilet + modifications to an ISO 9660 layout and the creation of JOLIET and HFS discs. See the &man.mkisofs.8; manual page for details. burncd - CDROMs + CD-ROMs burning If you have an ATAPI CD burner, you can use the @@ -870,7 +870,7 @@ the flag of cdrecord, which might produce results like this: - CDROMs + CD-ROMs burning &prompt.root; cdrecord -scanbus @@ -959,7 +959,7 @@ Extract each track using &man.dd.1;. You must also use a - specific blocksize when extracting the files. + specific block size when extracting the files. &prompt.root; dd if=/dev/acd0t1 of=track1.cdr bs=2352 &prompt.root; dd if=/dev/acd0t2 of=track2.cdr bs=2352 @@ -984,11 +984,11 @@ You can copy a data CD to a image file that is functionally equivalent to the image file created with sysutils/mkisofs, and you can use it to duplicate - any data CD. The example given here assumes that your CDROM + any data CD. The example given here assumes that your CD-ROM device is acd0. Substitute your - correct CDROM device. A c must be appended + correct CD-ROM device. A c must be appended to the end of the device name to indicate the entire partition - or, in the case of CDROMs, the entire disc. + or, in the case of CD-ROMs, the entire disc. &prompt.root; dd if=/dev/acd0c of=file.iso bs=2048 @@ -999,21 +999,21 @@ Using Data CDs - Now that you have created a standard data CDROM, you + Now that you have created a standard data CD-ROM, you probably want to mount it and read the data on it. By default, &man.mount.8; assumes that a file system is of type - ufs. If you try something like: + UFS. If you try something like: &prompt.root; mount /dev/cd0c /mnt you will get a complaint about Incorrect super - block, and no mount. The CDROM is not a + block, and no mount. The CD-ROM is not a UFS file system, so attempts to mount it as such will fail. You just need to tell &man.mount.8; that the file system is of type ISO9660, and everything will work. You do this by specifying the option &man.mount.8;. For - example, if you want to mount the CDROM device, + example, if you want to mount the CD-ROM device, /dev/cd0c, under /mnt, you would execute: @@ -1021,16 +1021,16 @@ Note that your device name (/dev/cd0c in this example) could be - different, depending on the interface your CDROM uses. Also, + different, depending on the interface your CD-ROM uses. Also, the option just executes &man.mount.cd9660.8;. The above example could be shortened to: &prompt.root; mount_cd9660 /dev/cd0c /mnt - You can generally use data CDROMs from any vendor in this + You can generally use data CD-ROMs from any vendor in this way. Disks with certain ISO 9660 extensions might behave - oddly, however. For example, Joliet disks store all filenames + oddly, however. For example, JOLIET disks store all filenames in two-byte Unicode characters. The FreeBSD kernel does not speak Unicode (yet!), so non-English characters show up as question marks. (If you are running FreeBSD 4.3 or later, the @@ -1040,21 +1040,21 @@ sysutils/cd9660_unicode port.) Occasionally, you might get Device not - configured when trying to mount a CDROM. This - usually means that the CDROM drive thinks that there is no + configured when trying to mount a CD-ROM. This + usually means that the CD-ROM 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 CDROM drive to realize + It can take a couple of seconds for a CD-ROM drive to realize that it has been fed, so be patient. - Sometimes, a SCSI CDROM may be missed because it didn't + Sometimes, a SCSI CD-ROM may be missed because it didn't have enough time to answer the bus reset. If you have a SCSI - CDROM please add the following option to your kernel + CD-ROM please add the following option to your kernel configuration and rebuild your kernel. options SCSI_DELAY=15000 This tells your SCSI bus to pause 15 seconds during boot, - to give your CDROM drive every possible chance to answer the + to give your CD-ROM drive every possible chance to answer the bus reset. @@ -1073,8 +1073,8 @@ &prompt.root; tar xzvf /dev/acd1c - You cannot mount this disk as you would a normal CDROM. - Such a CDROM cannot be read under any operating system + You cannot mount this disk as you would a normal CD-ROM. + Such a CD-ROM cannot be read under any operating system except FreeBSD. If you want to be able to mount the CD, or share data with another operating system, you must use sysutils/mkisofs as described above. @@ -1159,10 +1159,10 @@ &prompt.root; /usr/sbin/fdformat /dev/fd0.1720 It will take some more time than before (forced disks are - slower). When it finishes, you will have a 1720kb floppy disk, + slower). When it finishes, you will have a 1720kB floppy disk, but for the moment you will not notice any difference. You may use other disk sizes that you can find in /dev, but the most - stable/compatible is the 1720kb for 3.5inch disks. + stable/compatible is the 1720kB for 3.5inch disks. @@ -2024,7 +2024,7 @@ fixit.flp floppies, keep reading. Insert the boot.flp floppy in the first floppy drive and boot the computer. The original install menu will be displayed on - the screen. Select the Fixit--Repair mode with CDROM or + the screen. Select the Fixit--Repair mode with CD-ROM or floppy. option. Insert the fixit.flp when prompted. restore and the other programs that you need are @@ -2639,13 +2639,13 @@ editor. Sometimes it is desirable to set quota limits on a range of - uids. This can be done by use of the option + UIDs. This can be done by use of the option on the edquota command. First, assign the desired quota limit to a user, and then run edquota -p protouser startuid-enduid. For example, if user test has the desired quota limits, the following command can be used to duplicate those quota - limits for uids 10,000 through 19,999: + limits for UIDs 10,000 through 19,999: &prompt.root; edquota -p test 10000-19999