From 2de880b5f1dde9b506f83031de8fcc6bf606f45c Mon Sep 17 00:00:00 2001 From: Chern Lee Date: Sat, 28 Jul 2001 01:44:52 +0000 Subject: [PATCH] man fstab -> &man.fstab.5; Minor grammar/markup changes. Placed two groups of paragraphs into and Make use of tag Reviewed by: murray --- .../books/handbook/disks/chapter.sgml | 266 +++++++++++------- 1 file changed, 158 insertions(+), 108 deletions(-) diff --git a/en_US.ISO8859-1/books/handbook/disks/chapter.sgml b/en_US.ISO8859-1/books/handbook/disks/chapter.sgml index d7b1cb3d70..863e8786a5 100644 --- a/en_US.ISO8859-1/books/handbook/disks/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/disks/chapter.sgml @@ -1,7 +1,7 @@ @@ -18,7 +18,7 @@ BIOS Drive Numbering Before you install and configure FreeBSD on your system, there is an - important subject that you should be aware of if, especially if you have + important subject that you should be aware of, especially if you have multiple hard drives. DOS @@ -235,11 +235,12 @@ root filesystem There are various reasons to house some of these directories on separate filesystems. /var - contains log/, spool/, + contains the directories log/, + spool/, and various types of temporary files, and as such, may get filled up. Filling up the root filesystem isn't a good idea, so splitting /var from - / is often a good idea. + / is often favorable. Another common reason to contain certain directory trees on other filesystems is if they are to be housed on separate @@ -248,7 +249,7 @@ drives. - The fstab File + The <filename>fstab</filename> File filesystems mounted with fstab @@ -264,28 +265,55 @@ device /mount-point fstype options dumpfreq passno - device is a device name (which should - exist), as explained in the Disk - naming conventions above. + + + device + + A device name (which should exist), as explained in + the Disk naming + conventions above. + + - mount-point is a directory (which - should exist), on which to mount the filesystem. + + mount-point - fstype is the filesystem type to pass - to &man.mount.8;. The default FreeBSD filesystem is - ufs. + A directory (which should exist), on which + to mount the filesystem. + + - options is either - for read-write filesystems, or for - read-only filesystems, followed by any other options that may - be needed. A common option is for - filesystems not normally mounted during the boot sequence. - Other options in the &man.mount.8; manual page. + + fstype - dumpfreq is the number of days the - filesystem should be dumped, and passno is - the pass number during which the filesystem is checked during - the boot sequence. + The filesystem type to pass to + &man.mount.8;. The default FreeBSD filesystem is + ufs. + + + + + options + + Either for read-write + filesystems, or for read-only + filesystems, followed by any other options that may be + needed. A common option is for + filesystems not normally mounted during the boot sequence. + Other options in the &man.mount.8; manual page. + + + + + dumpfreq + + The number of days the filesystem should be + dumped, and passno is the pass number + during which the filesystem is checked during the boot + sequence. + + + @@ -308,7 +336,7 @@ &man.mount.8; manual page, but the most common are: - mount options + Mount Options @@ -459,9 +487,9 @@ Login as user root. After you've 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, it will - be wd1 in pre-4.0 systems, or + be da1 and we want to mount it on + /1 (if you are adding an IDE drive, the device name + will be wd1 in pre-4.0 systems, or ad1 in most 4.X systems). partitions @@ -498,68 +526,86 @@ adding disks - You may use /stand/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 - /stand/sysinstall and enter the - Configure menu. Within the - FreeBSD Configuration Menu, scroll down and - select the Partition item. Next you should - be presented with a list of hard drives installed in your - system. If you do not see da1 listed, you - need to recheck your physical installation and - dmesg output in the file - /var/run/dmesg.boot. - - Select da1 to enter the FDISK - Partition Editor. Type A to - 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 typing q. Next you will be - asked about the Master Boot Record. Since you are adding a - disk to an already running system, choose - None. + + + Navigating <application>Sysinstall</application> - BSD partitions - Next, Sysinstall 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. + You may use /stand/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 + /stand/sysinstall and enter the + Configure menu. Within the + FreeBSD Configuration Menu, scroll down and + select the Partition item. Next you should + be presented with a list of hard drives installed in your + system. If you do not see da1 listed, you + need to recheck your physical installation and + dmesg output in the file + /var/run/dmesg.boot. + - Sysinstall's Label editor - favors the e - partition for non-root, non-swap partitions. Within the - Label editor, create a single file system by typing - 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 isn't important. + + FDISK Partition Editor + Select da1 to enter the FDISK + Partition Editor. Type A to + 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 typing q. Next you will be + asked about the Master Boot Record. Since you are adding a + disk to an already running system, choose + None. + - You are now ready to write the new label to the disk and - create a file system on it. Do this by typing - W. Ignore any errors from - Sysinstall that - it could not mount the new partition. Exit the Label Editor - and Sysinstall completely. + + Disk Label Editor + BSD partitions - The last step is to edit /etc/fstab - to add an entry for your new disk. + Next, Sysinstall 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 typing + 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 isn't important. + + You are now ready to write the new label to the disk and + create a file system on it. Do this by typing + W. Ignore any errors from + 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. + + @@ -579,11 +625,11 @@ &prompt.root; dd if=/dev/zero of=/dev/rda1 bs=1k count=1 &prompt.root; fdisk -BI da1 #Initialize your new disk &prompt.root; disklabel -B -w -r da1s1 auto #Label it. -&prompt.root; disklabel -e da1s1 # Now edit the disklabel you just created and add any partitions. +&prompt.root; disklabel -e da1s1 # Edit the disklabel just created and add any partitions. &prompt.root; mkdir -p /1 &prompt.root; newfs /dev/da1s1e # Repeat this for every partition you created. &prompt.root; mount -t ufs /dev/da1s1e /1 # Mount the partition(s) -&prompt.root; vi /etc/fstab # When satisfied, add the appropriate entry/entries to your /etc/fstab. +&prompt.root; vi /etc/fstab # Add the appropriate entry/entries to your /etc/fstab. If you have an IDE disk, substitute ad for da. On pre-4.X systems use @@ -647,13 +693,13 @@ linkend="disks-vnconfig">vnconfig. - vnconfig: file-backed filesystem + vnconfig: File-Backed Filesystem disks file-backed - &man.vnconfig.8; configures and enables vnode pseudo disk + &man.vnconfig.8; configures and enables vnode pseudo-disk devices. A vnode is a representation of a file, and is the focus of file activity. This means that &man.vnconfig.8; uses files to create and operate a @@ -770,8 +816,8 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on the quota database properly reflects the data on the file system. This is a very time consuming process that will significantly affect the time your system takes to boot. If you would like to - skip this step, a variable is made available for the - purpose: + skip this step, a variable in /etc/rc.conf + is made available for the purpose: check_quotas=NO @@ -803,8 +849,9 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on By default the quota files are stored in the root directory of the file system with the names quota.user and quota.group for user and group quotas - respectively. See man fstab for more - information. Even though that man page says that you can specify + respectively. See &man.fstab.5; for more + information. Even though the &man.fstab.5; man page says that + you can specify an alternate location for the quota files, this is not recommended because the various quota utilities do not seem to handle this properly. @@ -910,7 +957,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on &prompt.root; edquota -p test 10000-19999 - See man edquota for more detailed + See the &man.edquota.8; for more detailed information. @@ -1019,8 +1066,8 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on The mkisofs program is used to produce a data file containing an ISO 9660 file system. It has options that support various extensions, and is - described below. You can install it with the - /usr/ports/sysutils/mkisofs port. + described below. You can install it with the + sysutils/mkisofs port. CD burner @@ -1031,7 +1078,12 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on linkend="burncd">burncd program that is part of the base system. SCSI and USB CD burners should use the cdrecord from - the /usr/ports/sysutils/cdrecord port. + the sysutils/cdrecord port. + + burncd has a limited number of + supported drives. To find out if a drive is supported, see + CD-R/RW supported + drives. @@ -1052,9 +1104,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on /path/to/tree. In the process, it will map the file names to names that fit the limitations of the standard ISO 9660 file system, and will exclude files that have - names uncharacteristic of ISO file systems. Read &man.mkisofs.8; - for details of this process, and options that can be used to - control it. + names uncharacteristic of ISO file systems. filesystems @@ -1069,9 +1119,8 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on Rock Ridge extensions common to Unix systems, enables Joliet extensions used by Microsoft systems, and can be used to create HFS file systems used - by Macs. Read &man.mkisofs.8; for more information on the last - two. - + by MacOS. + For CDs that are going to be used only on FreeBSD systems, can be used to disable all filename restrictions. When used with , it produces a @@ -1106,8 +1155,9 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on and /tmp/myboot are identical. There are many other options you can use with - mkisofs to fine-tune its behavior. See - &man.mkisofs.8; for details. + mkisofs to fine-tune its behavior. In particular: + modifications to an ISO 9660 layout and the creation of Joilet + and HFS discs. See the &man.mkisofs.8; man page for details. @@ -1137,13 +1187,13 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on If you do not have an ATAPI CD burner, you will have to use cdrecord to burn your CDs. cdrecord is not part of the base system; - you must install it from either the port at - /usr/ports/sysutils/cdrecord or the appropriate + you must install it from either the port at sysutils/cdrecord + or the appropriate package. Changes to the base system can cause binary versions of this program to fail, possibly resulting in a coaster. You should therefore either upgrade the port when you upgrade your system, or if you are tracking -stable, upgrade the port when a + linkend="stable">tracking -STABLE, upgrade the port when a new version becomes available. While cdrecord has many options, basic usage