From owner-p4-projects@FreeBSD.ORG Sat Feb 4 10:02:48 2012 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id ED1D91065670; Sat, 4 Feb 2012 10:02:47 +0000 (UTC) Delivered-To: perforce@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A4A4F106564A for ; Sat, 4 Feb 2012 10:02:47 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from skunkworks.freebsd.org (skunkworks.freebsd.org [IPv6:2001:4f8:fff6::2d]) by mx1.freebsd.org (Postfix) with ESMTP id 901F88FC0C for ; Sat, 4 Feb 2012 10:02:47 +0000 (UTC) Received: from skunkworks.freebsd.org (localhost [127.0.0.1]) by skunkworks.freebsd.org (8.14.4/8.14.4) with ESMTP id q14A2lhF026950 for ; Sat, 4 Feb 2012 10:02:47 GMT (envelope-from rene@FreeBSD.org) Received: (from perforce@localhost) by skunkworks.freebsd.org (8.14.4/8.14.4/Submit) id q14A2kB7026947 for perforce@freebsd.org; Sat, 4 Feb 2012 10:02:46 GMT (envelope-from rene@FreeBSD.org) Date: Sat, 4 Feb 2012 10:02:46 GMT Message-Id: <201202041002.q14A2kB7026947@skunkworks.freebsd.org> X-Authentication-Warning: skunkworks.freebsd.org: perforce set sender to rene@FreeBSD.org using -f From: Rene Ladan To: Perforce Change Reviews Precedence: bulk Cc: Subject: PERFORCE change 205673 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.5 List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Feb 2012 10:02:48 -0000 http://p4web.freebsd.org/@@205673?ac=10 Change 205673 by rene@rene_acer on 2012/02/04 10:01:41 IFC Affected files ... .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.committers.sgml#74 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/desktop/chapter.sgml#32 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/disks/chapter.sgml#23 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/filesystems/chapter.sgml#9 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml#32 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/porters-handbook/book.sgml#127 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/share/sgml/authors.ent#67 integrate .. //depot/projects/docproj_nl/share/pgpkeys/davide.key#1 branch .. //depot/projects/docproj_nl/share/pgpkeys/pgpkeys-developers.sgml#68 integrate .. //depot/projects/docproj_nl/share/pgpkeys/pgpkeys.ent#65 integrate Differences ... ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.committers.sgml#74 (text+ko) ==== @@ -1,4 +1,4 @@ - + @@ -189,7 +189,7 @@ &prompt.root; pkg_add -r firefox - This will install Firefox 9.0, + This will install Firefox 10.0, if you want to run Firefox 3.6, use instead: ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/disks/chapter.sgml#23 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -10,44 +10,62 @@ Synopsis - This chapter covers the use of disks in FreeBSD. This includes memory-backed disks, network-attached disks, standard SCSI/IDE storage devices, and devices using the USB interface. After reading this chapter, you will know: + - The terminology FreeBSD uses to describe the - organization of data on a physical disk (partitions and slices). + + The terminology FreeBSD uses to describe the + organization of data on a physical disk (partitions and + slices). - How to add additional hard disks to your system. + + + How to add additional hard disks to your system. + How to configure &os; to use USB storage devices. - How to set up virtual file systems, such as memory - disks. + + + How to set up virtual file systems, such as memory + disks. + + How to use quotas to limit disk space usage. + - How to encrypt disks to secure them against attackers. + How to encrypt disks to secure them against + attackers. + How to create and burn CDs and DVDs on FreeBSD. + - The various storage media options for backups. + The various storage media options for backups. + - How to use backup programs available under FreeBSD. + How to use backup programs available under + FreeBSD. + - How to backup to floppy disks. + How to backup to floppy disks. + - What file system snapshots are and how to use them efficiently. + What file system snapshots are and how to use them + efficiently. @@ -55,11 +73,10 @@ - Know how to configure and install a new FreeBSD kernel - (). + Know how to configure and install a new FreeBSD kernel + (). - @@ -79,45 +96,56 @@ Drive device name + IDE hard drives ad + IDE CDROM drives acd + - SCSI hard drives and USB Mass storage devices + SCSI hard drives and USB Mass storage + devices da + SCSI CDROM drives cd + Assorted non-standard CDROM drives mcd for Mitsumi CD-ROM and - scd for Sony CD-ROM devices - + scd for Sony CD-ROM devices + Floppy drives fd + SCSI tape drives sa - + + IDE tape drives ast + Flash drives - fla for &diskonchip; Flash device + fla for &diskonchip; Flash + device + RAID drives aacd for &adaptec; AdvancedRAID, @@ -152,19 +180,20 @@ The following section will describe how to add a new - SCSI disk to a machine that - currently only has a single drive. First turn off the computer - and install the drive in the computer following the instructions - of the computer, controller, and drive manufacturer. Due to the - wide variations of procedures to do this, the details are beyond - the scope of this document. + SCSI disk to a machine that currently only + has a single drive. First turn off the computer and install the + drive in the computer following the instructions of the + computer, controller, and drive manufacturer. Due to the wide + variations of procedures to do this, the details are beyond the + scope of this document. - Login as user root. After you have installed the - drive, inspect /var/run/dmesg.boot to ensure the new - disk was found. Continuing with our example, the newly added drive will - be da1 and we want to mount it on - /1 (if you are adding an IDE drive, the device name - will be ad1). + Login as user root. After you have + installed the drive, inspect + /var/run/dmesg.boot to ensure the new disk + was found. Continuing with our example, the newly added drive + will be da1 and we want to mount it on + /1 (if you are adding an IDE drive, the + device name will be ad1). partitions slices @@ -172,19 +201,20 @@ fdisk - FreeBSD runs on IBM-PC compatible computers, therefore it must - take into account the PC BIOS partitions. These are different - from the traditional BSD partitions. A PC disk has up to four - BIOS partition entries. If the disk is going to be truly - dedicated to FreeBSD, you can use the + FreeBSD runs on IBM-PC compatible computers, therefore it + must take into account the PC BIOS partitions. These are + different from the traditional BSD partitions. A PC disk has up + to four BIOS partition entries. If the disk is going to be + truly dedicated to FreeBSD, you can use the dedicated mode. Otherwise, FreeBSD will have to live within one of the PC BIOS partitions. FreeBSD calls the PC BIOS partitions slices so as not to confuse them with traditional BSD partitions. You may also use slices on a disk that is dedicated to FreeBSD, but used in a computer that also has another operating system installed. - This is a good way to avoid confusing the fdisk utility of - other, non-FreeBSD operating systems. + This is a good way to avoid confusing the + fdisk utility of other, non-FreeBSD operating + systems. In the slice case the drive will be added as /dev/da1s1e. This is read as: SCSI disk, @@ -193,50 +223,55 @@ case, the drive will be added simply as /dev/da1e. - Due to the use of 32-bit integers to store the number of sectors, - &man.bsdlabel.8; is - limited to 2^32-1 sectors per disk or 2TB in most cases. The - &man.fdisk.8; format allows a starting sector of no more than - 2^32-1 and a length of no more than 2^32-1, limiting partitions to - 2TB and disks to 4TB in most cases. The &man.sunlabel.8; format - is limited to 2^32-1 sectors per partition and 8 partitions for - a total of 16TB. For larger disks, &man.gpart.8; may be used to - create GPT partitions. GPT - has the added benefit of not being limited to 4 slices. + Due to the use of 32-bit integers to store the number of + sectors, &man.bsdlabel.8; is limited to 2^32-1 sectors per disk + or 2TB in most cases. The &man.fdisk.8; format allows a + starting sector of no more than 2^32-1 and a length of no more + than 2^32-1, limiting partitions to 2TB and disks to 4TB in most + cases. The &man.sunlabel.8; format is limited to 2^32-1 sectors + per partition and 8 partitions for a total of 16TB. For larger + disks, &man.gpart.8; may be used to create + GPT partitions. GPT has + the added benefit of not being limited to 4 slices. Using &man.sysinstall.8; - sysinstall - adding disks + sysinstall + adding disks su + - Navigating <application>Sysinstall</application> + Navigating + <application>Sysinstall</application> - You may use sysinstall to - partition and label a new disk using its easy to use menus. - Either login as user root or use the + You may use sysinstall to partition + and label a new disk using its easy to use menus. Either + login as user root or use the su command. Run sysinstall and enter the Configure menu. Within the - FreeBSD Configuration Menu, scroll down and - select the Fdisk option. + FreeBSD Configuration Menu, scroll down + and select the Fdisk option. - <application>fdisk</application> Partition Editor - Once inside fdisk, pressing A will - use the entire disk for FreeBSD. When asked if you want to - remain cooperative with any future possible operating - systems, answer YES. Write the - changes to the disk using W. Now exit the - FDISK editor by pressing Q. Next you will be - asked about the Master Boot Record. Since you are adding a - disk to an already running system, choose + <application>fdisk</application> Partition + Editor + + Once inside fdisk, pressing + A will use the entire disk for FreeBSD. + When asked if you want to remain cooperative with + any future possible operating systems, answer + YES. Write the changes to the disk + using W. Now exit the FDISK editor by + pressing Q. Next you will be asked about + the Master Boot Record. Since you are + adding a disk to an already running system, choose None. @@ -244,48 +279,51 @@ Disk Label Editor BSD partitions - Next, you need to exit sysinstall - and start it again. Follow the directions above, although this - time choose the Label option. This will - enter the Disk Label Editor. This - is where you will create the traditional BSD partitions. A - disk can have up to eight partitions, labeled - a-h. - A few of the partition labels have special uses. The - a partition is used for the root partition - (/). Thus only your system disk (e.g, - the disk you boot from) should have an a - partition. The b partition is used for - swap partitions, and you may have many disks with swap - partitions. The c partition addresses the - entire disk in dedicated mode, or the entire FreeBSD slice in - slice mode. The other partitions are for general use. + Next, you need to exit + sysinstall and start it again. + Follow the directions above, although this time choose the + Label option. This will enter the + Disk Label Editor. This is where you + will create the traditional BSD partitions. A disk can + have up to eight partitions, labeled + a-h. A few of the partition labels + have special uses. The a partition is + used for the root partition (/). + Thus only your system disk (e.g, the disk you boot from) + should have an a partition. The + b partition is used for swap + partitions, and you may have many disks with swap + partitions. The c partition addresses + the entire disk in dedicated mode, or the entire FreeBSD + slice in slice mode. The other partitions are for general + use. sysinstall's Label editor - favors the e - partition for non-root, non-swap partitions. Within the - Label editor, create a single file system by pressing - C. When prompted if this will be a FS - (file system) or swap, choose FS and type in a - mount point (e.g, /mnt). When adding a - disk in post-install mode, sysinstall - will not create entries - in /etc/fstab for you, so the mount point - you specify is not important. + favors the e partition for non-root, + non-swap partitions. Within the Label editor, create a + single file system by pressing C. When + prompted if this will be a FS (file system) or swap, + choose FS and type in a mount point + (e.g, /mnt). When adding a disk in + post-install mode, sysinstall + will not create entries in /etc/fstab + for you, so the mount point you specify is not + important. - You are now ready to write the new label to the disk and - create a file system on it. Do this by pressing + You are now ready to write the new label to the disk + and create a file system on it. Do this by pressing W. Ignore any errors from - sysinstall that - it could not mount the new partition. Exit the Label Editor - and sysinstall completely. + sysinstall that it could not + mount the new partition. Exit the Label Editor and + sysinstall completely. Finish - The last step is to edit /etc/fstab - to add an entry for your new disk. + The last step is to edit + /etc/fstab to add an entry for your + new disk. @@ -313,20 +351,21 @@ &prompt.root; mount /dev/da1s1e /1 # Mount the partition(s) &prompt.root; vi /etc/fstab # Add the appropriate entry/entries to your /etc/fstab. - If you have an IDE disk, substitute ad - for da. + If you have an IDE disk, substitute + ad for da. Dedicated OS/2 - If you will not be sharing the new drive with another operating - system, you may use the dedicated mode. Remember - this mode can confuse Microsoft operating systems; however, no damage - will be done by them. IBM's &os2; however, will - appropriate any partition it finds which it does not - understand. + If you will not be sharing the new drive with another + operating system, you may use the + dedicated mode. Remember this mode can + confuse Microsoft operating systems; however, no damage will + be done by them. IBM's &os2; however, will + appropriate any partition it finds which it + does not understand. &prompt.root; dd if=/dev/zero of=/dev/da1 bs=1k count=1 &prompt.root; bsdlabel -Bw da1 auto @@ -364,6 +403,7 @@ Original work by + Jim @@ -373,103 +413,102 @@ -RAIDsoftware - - RAIDCCD - + RAIDsoftware + RAIDCCD Concatenated Disk Driver (CCD) Configuration + When choosing a mass storage solution the most important factors to consider are speed, reliability, and cost. It is - rare to have all three in balance; normally a fast, reliable mass - storage device is expensive, and to cut back on cost either speed - or reliability must be sacrificed. + rare to have all three in balance; normally a fast, reliable + mass storage device is expensive, and to cut back on cost + either speed or reliability must be sacrificed. - In designing the system described below, cost was chosen - as the most important factor, followed by speed, then reliability. - Data transfer speed for this system is ultimately - constrained by the network. And while reliability is very important, - the CCD drive described below serves online data that is already - fully backed up on CD-R's and can easily be replaced. + In designing the system described below, cost was + chosen as the most important factor, followed by speed, + then reliability. Data transfer speed for this system is + ultimately constrained by the network. And while + reliability is very important, the CCD drive described + below serves online data that is already fully backed up + on CD-R's and can easily be replaced. - Defining your own requirements is the first step - in choosing a mass storage solution. If your requirements prefer - speed or reliability over cost, your solution will differ from - the system described in this section. - + Defining your own requirements is the first step in + choosing a mass storage solution. If your requirements + prefer speed or reliability over cost, your solution will + differ from the system described in this section. Installing the Hardware In addition to the IDE system disk, three Western - Digital 30GB, 5400 RPM IDE disks form the core - of the CCD disk described below providing approximately - 90GB of online storage. Ideally, - each IDE disk would have its own IDE controller - and cable, but to minimize cost, additional + Digital 30GB, 5400 RPM IDE disks form the core of the CCD + disk described below providing approximately 90GB of + online storage. Ideally, each IDE disk would have its own + IDE controller and cable, but to minimize cost, additional IDE controllers were not used. Instead the disks were configured with jumpers so that each IDE controller has - one master, and one slave. + one master, and one slave. Upon reboot, the system BIOS was configured to - automatically detect the disks attached. More importantly, - FreeBSD detected them on reboot: + automatically detect the disks attached. More + importantly, FreeBSD detected them on reboot: ad0: 19574MB <WDC WD205BA> [39770/16/63] at ata0-master UDMA33 ad1: 29333MB <WDC WD307AA> [59598/16/63] at ata0-slave UDMA33 ad2: 29333MB <WDC WD307AA> [59598/16/63] at ata1-master UDMA33 ad3: 29333MB <WDC WD307AA> [59598/16/63] at ata1-slave UDMA33 - If FreeBSD does not detect all the disks, ensure - that you have jumpered them correctly. Most IDE drives - also have a Cable Select jumper. This is - not the jumper for the master/slave - relationship. Consult the drive documentation for help in - identifying the correct jumper. + If FreeBSD does not detect all the disks, ensure + that you have jumpered them correctly. Most IDE drives + also have a Cable Select jumper. This is + not the jumper for the master/slave + relationship. Consult the drive documentation for help in + identifying the correct jumper. - Next, consider how to attach them as part of the file - system. You should research both &man.vinum.4; () and &man.ccd.4;. In this - particular configuration, &man.ccd.4; was chosen. + Next, consider how to attach them as part of the file + system. You should research both &man.vinum.4; () and &man.ccd.4;. In this + particular configuration, &man.ccd.4; was chosen. Setting Up the CCD - The &man.ccd.4; driver allows you to take - several identical disks and concatenate them into one - logical file system. In order to use - &man.ccd.4;, you need a kernel with - &man.ccd.4; support built in. - Add this line to your kernel configuration file, rebuild, and - reinstall the kernel: + The &man.ccd.4; driver allows you to take several + identical disks and concatenate them into one logical file + system. In order to use &man.ccd.4;, you need a kernel + with &man.ccd.4; support built in. Add this line to your + kernel configuration file, rebuild, and reinstall the + kernel: device ccd - The &man.ccd.4; support can also be - loaded as a kernel loadable module. + The &man.ccd.4; support can also be loaded as a kernel + loadable module. - To set up &man.ccd.4;, you must first use - &man.bsdlabel.8; to label the disks: + To set up &man.ccd.4;, you must first use + &man.bsdlabel.8; to label the disks: bsdlabel -w ad1 auto bsdlabel -w ad2 auto bsdlabel -w ad3 auto - This creates a bsdlabel for ad1c, ad2c and ad3c that - spans the entire disk. + This creates a bsdlabel for + ad1c, + ad2c and + ad3c that spans the entire + disk. - The next step is to change the disk label type. You - can use &man.bsdlabel.8; to edit the - disks: + The next step is to change the disk label type. You + can use &man.bsdlabel.8; to edit the disks: bsdlabel -e ad1 bsdlabel -e ad2 bsdlabel -e ad3 - This opens up the current disk label on each disk with - the editor specified by the EDITOR - environment variable, typically &man.vi.1;. + This opens up the current disk label on each disk with + the editor specified by the EDITOR + environment variable, typically &man.vi.1;. An unmodified disk label will look something like this: @@ -478,95 +517,94 @@ # size offset fstype [fsize bsize bps/cpg] c: 60074784 0 unused 0 0 0 # (Cyl. 0 - 59597) - Add a new e partition for &man.ccd.4; to use. This - can usually be copied from the c partition, - but the must - be 4.2BSD. The disk label should - now look something like this: + Add a new e partition for + &man.ccd.4; to use. This can usually be copied from the + c partition, but the + must be + 4.2BSD. The disk label should now + look something like this: 8 partitions: # size offset fstype [fsize bsize bps/cpg] c: 60074784 0 unused 0 0 0 # (Cyl. 0 - 59597) e: 60074784 0 4.2BSD 0 0 0 # (Cyl. 0 - 59597) - Building the File System Now that you have all the disks labeled, you must - build the &man.ccd.4;. To do that, - use &man.ccdconfig.8;, with options similar to the following: + build the &man.ccd.4;. To do that, use &man.ccdconfig.8;, + with options similar to the following: - ccdconfig ccd0 32 0 /dev/ad1e /dev/ad2e /dev/ad3e + ccdconfig ccd0 32 0 /dev/ad1e /dev/ad2e /dev/ad3e - The use and meaning of each option is shown below: + The use and meaning of each option is shown + below: - - - The first argument is the device to configure, in this case, - /dev/ccd0c. The /dev/ - portion is optional. - + + + The first argument is the device to configure, in + this case, /dev/ccd0c. The + /dev/ portion is optional. + - + + The interleave for the file system. The + interleave defines the size of a stripe in disk + blocks, each normally 512 bytes. So, an interleave of + 32 would be 16,384 bytes. + - The interleave for the file system. The interleave - defines the size of a stripe in disk blocks, each normally 512 bytes. - So, an interleave of 32 would be 16,384 bytes. - + + Flags for &man.ccdconfig.8;. If you want to + enable drive mirroring, you can specify a flag here. + This configuration does not provide mirroring for + &man.ccd.4;, so it is set at 0 (zero). + - - Flags for &man.ccdconfig.8;. If you want to enable drive - mirroring, you can specify a flag here. This - configuration does not provide mirroring for - &man.ccd.4;, so it is set at 0 (zero). - + + The final arguments to &man.ccdconfig.8; are the + devices to place into the array. Use the complete + pathname for each device. + + - - The final arguments to &man.ccdconfig.8; - are the devices to place into the array. Use the complete pathname - for each device. - - - - - After running &man.ccdconfig.8; the &man.ccd.4; - is configured. A file system can be installed. Refer to &man.newfs.8; - for options, or simply run: + After running &man.ccdconfig.8; the &man.ccd.4; is + configured. A file system can be installed. Refer to + &man.newfs.8; for options, or simply run: newfs /dev/ccd0c - - Making it All Automatic - Generally, you will want to mount the - &man.ccd.4; upon each reboot. To do this, you must - configure it first. Write out your current configuration to - /etc/ccd.conf using the following command: + Generally, you will want to mount the &man.ccd.4; upon + each reboot. To do this, you must configure it first. + Write out your current configuration to + /etc/ccd.conf using the following + command: ccdconfig -g > /etc/ccd.conf During reboot, the script /etc/rc - runs ccdconfig -C if /etc/ccd.conf - exists. This automatically configures the - &man.ccd.4; so it can be mounted. + runs ccdconfig -C if + /etc/ccd.conf exists. This + automatically configures the &man.ccd.4; so it can be + mounted. - If you are booting into single user mode, before you can - &man.mount.8; the &man.ccd.4;, you - need to issue the following command to configure the - array: + + If you are booting into single user mode, before you + can &man.mount.8; the &man.ccd.4;, you need to issue the + following command to configure the array: - ccdconfig -C - + ccdconfig -C + - To automatically mount the &man.ccd.4;, - place an entry for the &man.ccd.4; in - /etc/fstab so it will be mounted at - boot time: + To automatically mount the &man.ccd.4;, place an entry + for the &man.ccd.4; in /etc/fstab so + it will be mounted at boot time: /dev/ccd0c /media ufs rw 2 2 @@ -575,11 +613,14 @@ The Vinum Volume Manager -RAIDsoftware - - RAID - Vinum - + + RAID + software + + + RAID + Vinum + The Vinum Volume Manager is a block device driver which implements virtual disk drives. It isolates disk hardware @@ -602,29 +643,33 @@ hardware - FreeBSD also supports a variety of hardware RAID - controllers. These devices control a RAID subsystem - without the need for FreeBSD specific software to manage the - array. + FreeBSD also supports a variety of hardware + RAID controllers. These devices control a + RAID subsystem without the need for FreeBSD + specific software to manage the array. - Using an on-card BIOS, the card controls most of the disk operations - itself. The following is a brief setup description using a Promise IDE RAID - controller. When this card is installed and the system is started up, it - displays a prompt requesting information. Follow the instructions - to enter the card's setup screen. From here, you have the ability to - combine all the attached drives. After doing so, the disk(s) will look like - a single drive to FreeBSD. Other RAID levels can be set up - accordingly. - + Using an on-card BIOS, the card + controls most of the disk operations itself. The following is + a brief setup description using a Promise + IDE RAID controller. + When this card is installed and the system is started up, it + displays a prompt requesting information. Follow the + instructions to enter the card's setup screen. From here, you + have the ability to combine all the attached drives. After + doing so, the disk(s) will look like a single drive to + FreeBSD. Other RAID levels can be set up + accordingly. Rebuilding ATA RAID1 Arrays - FreeBSD allows you to hot-replace a failed disk in an array. This requires - that you catch it before you reboot. + FreeBSD allows you to hot-replace a failed disk in an + array. This requires that you catch it before you + reboot. - You will probably see something like the following in /var/log/messages or in the &man.dmesg.8; + You will probably see something like the following in + /var/log/messages or in the &man.dmesg.8; output: ad6 on monster1 suffered a hard error. @@ -635,7 +680,8 @@ status=59 error=40 ar0: WARNING - mirror lost - Using &man.atacontrol.8;, check for further information: + Using &man.atacontrol.8;, check for further + information: &prompt.root; atacontrol list ATA channel 0: @@ -659,8 +705,8 @@ - You will first need to detach the ata channel with the failed - disk so you can safely remove it: + You will first need to detach the ata channel with the + failed disk so you can safely remove it: &prompt.root; atacontrol detach ata3 @@ -755,17 +801,17 @@ to the USB storage devices, your USB device will be seen as a SCSI device by the system. Depending on the USB chipset on your motherboard, you only need either device - uhci or device ohci for USB 1.X support, however - having both in the kernel configuration file is harmless. - Support for USB 2.0 controllers is provided by the - &man.ehci.4; driver (the device ehci line). Do - not forget to compile and install the new kernel if you added - any lines. + uhci or device ohci for USB 1.X + support, however having both in the kernel configuration file + is harmless. Support for USB 2.0 controllers is provided by + the &man.ehci.4; driver (the device ehci + line). Do not forget to compile and install the new kernel if + you added any lines. - If your USB device is a CD-R or DVD burner, the SCSI CD-ROM - driver, &man.cd.4;, must be added to the kernel via the - line: + If your USB device is a CD-R or DVD burner, the SCSI + CD-ROM driver, &man.cd.4;, must be added to the kernel via + the line: device cd @@ -863,9 +909,9 @@ is for root to create a subdirectory owned by that user as /mnt/username - (replace username by the login name of - the actual user and usergroup by the - user's primary group): + (replace username by the login name + of the actual user and usergroup by + the user's primary group): &prompt.root; mkdir /mnt/username &prompt.root; chown username:usergroup /mnt/username @@ -892,10 +938,11 @@ Further Reading Beside the Adding - Disks and Mounting and + Disks and Mounting and Unmounting File Systems sections, reading various manual pages may be also useful: &man.umass.4;, - &man.camcontrol.8;, and &man.usbconfig.8; under &os;  8.X or &man.usbdevs.8; under earlier versions of &os;. + &man.camcontrol.8;, and &man.usbconfig.8; under &os;  8.X + or &man.usbdevs.8; under earlier versions of &os;. @@ -922,63 +969,69 @@ Introduction CDs have a number of features that differentiate them from - conventional disks. Initially, they were not writable by the - user. 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 than similarly sized media were at the - time. + conventional disks. Initially, they were not writable by the + user. 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 than similarly sized + media were at the time. - CDs do have tracks, but this refers to a section of data to - be read continuously and not a physical property of the disk. To - produce a CD on FreeBSD, you prepare the data files that are going - to make up the tracks on the CD, then write the tracks to the - CD. + CDs do have tracks, but this refers to a section of data + to be read continuously and not a physical property of the + disk. To produce a CD on FreeBSD, you prepare the data files + that are going to make up the tracks on the CD, then write the + tracks to the CD. ISO 9660 - file systems - ISO 9660 + file systems + ISO 9660 + The ISO 9660 file system was designed to deal with these - differences. It unfortunately codifies file system limits that were - common then. Fortunately, 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. + differences. It unfortunately codifies file system limits + that were common then. Fortunately, 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 + sysutils/cdrtools + The sysutils/cdrtools port includes &man.mkisofs.8;, a program that you can use to produce a data file containing an ISO 9660 file - system. It has options that support various extensions, and is - described below. + system. It has options that support various extensions, and + is described below. >>> TRUNCATED FOR MAIL (1000 lines) <<<