diff --git a/en/handbook/README b/en/handbook/README index 47ff1ff455..cf002e533d 100644 --- a/en/handbook/README +++ b/en/handbook/README @@ -261,4 +261,5 @@ for example, Changed the declaration at the top of the handbook to use this new DTD. + 18. Yet more things that should be filenames marked up as such. diff --git a/en/handbook/handbook.sgml b/en/handbook/handbook.sgml index fa7bef4a17..43c2c91dce 100644 --- a/en/handbook/handbook.sgml +++ b/en/handbook/handbook.sgml @@ -1861,8 +1861,7 @@ If your machine is already running MS-DOS and has little or no free space available for FreeBSD's installation, all is not lost! - You may find the FIPS utility, provided in the tools directory on the FreeBSD CDROM or on the + You may find the FIPS utility, provided in the tools directory on the FreeBSD CDROM or on the various FreeBSD ftp sites, to be quite useful. FIPS allows you to split an existing MS-DOS partition into two @@ -1894,10 +1893,10 @@ partitions? Yes. DOS extended partitions are mapped in at the end of the - other slices in FreeBSD, e.g. your D: drive might be /dev/sd0s5, - your E: drive /dev/sd0s6, and so on. This example assumes, of + other slices in FreeBSD, e.g. your D: drive might be /dev/sd0s5, + your E: drive /dev/sd0s6, and so on. This example assumes, of course, that your extended partition is on SCSI drive 0. For IDE - drives, substitute ``wd'' for ``sd'' appropriately. You otherwise + drives, substitute wd for sd appropriately. You otherwise mount extended partitions exactly like you would mount any other DOS drive, e.g.: @@ -2501,7 +2500,7 @@ This is probably not the place to go into a detailed examination of how Makefiles work; suffice it to say that the line - starting with ``MAN3'' ensures that the ElectricFence man page is + starting with MAN3 ensures that the ElectricFence man page is compressed after installation, to help conserve your precious disk space. The original port did not provide an ``install'' target, so the three lines from ``do-install'' ensure that the files @@ -3735,8 +3734,8 @@ Floppy drive controller: fd0 is the A: floppy drive, and - fd1 is the B: drive. + remap=tt>fd0 is the A: floppy drive, and + fd1 is the B: drive. ft0 is a QIC-80 tape drive attached to the floppy controller. Comment out any lines corresponding to devices you do not have. @@ -4709,7 +4708,7 @@ controller wcd0 This means that you should look for some entries - that start with wcd0 in the + that start with wcd0 in the /dev directory, possibly followed by a letter, such as c, or preceded by the letter r, which means a raw device. It turns out that those files are not there, so I must @@ -4717,8 +4716,7 @@ # sh MAKEDEV wcd0 When this script finishes, you will find that - there are now wcd0c and rwcd0c entries in /dev so + there are now wcd0c and rwcd0c entries in /dev so you know that it executed correctly. For sound cards, the command: @@ -8785,7 +8783,7 @@ Replace the job name on the header page with text. The job name is normally the name of the first file of the job, or - ``stdin'' if you are printing standard input. + stdin if you are printing standard input. @@ -18806,13 +18804,13 @@ Each nx= entry matches another - gettytab capability name + gettytab capability name Each tc= entry matches another - gettytab capability name + gettytab capability name @@ -22576,8 +22574,7 @@ Get pop software from the Ports collection that - can be found in /usr/ports or packages + can be found in /usr/ports or packages collection. This handbook section has a complete reference on the system. @@ -22780,8 +22777,7 @@ Do not panic, this is only a few hundred kilobytes in size. - The file README in the cf directory can serve as a basic + The file README in the cf directory can serve as a basic introduction to m4 configuration. For UUCP delivery, you are best advised to use the @@ -23555,15 +23551,15 @@ into a CTM supported tree. You can recognize these transition deltas by the - X appended to the number + X appended to the number (src-cur.3210XEmpty.gz for instance). The - designation following the X - corresponds to the origin of your initial seed. ``Empty'' is - an empty directory, ``R225'' would designate the 2.2.5 release, - etc. As a rule a base transition from ``Empty'' is producted + designation following the X + corresponds to the origin of your initial seed. Empty is + an empty directory, R225 would designate the 2.2.5 release, + etc. As a rule a base transition from Empty is producted every 100 deltas. By the way, they are large! 25 to 30 Megabytes of gzip'ed data is - common for the ``XEmpty'' deltas. + common for the XEmpty deltas. Once you've picked a base delta to start from, you will also need all deltas with higher numbers following it. diff --git a/en_US.ISO8859-1/books/handbook/book.sgml b/en_US.ISO8859-1/books/handbook/book.sgml index fa7bef4a17..43c2c91dce 100644 --- a/en_US.ISO8859-1/books/handbook/book.sgml +++ b/en_US.ISO8859-1/books/handbook/book.sgml @@ -1861,8 +1861,7 @@ If your machine is already running MS-DOS and has little or no free space available for FreeBSD's installation, all is not lost! - You may find the FIPS utility, provided in the tools directory on the FreeBSD CDROM or on the + You may find the FIPS utility, provided in the tools directory on the FreeBSD CDROM or on the various FreeBSD ftp sites, to be quite useful. FIPS allows you to split an existing MS-DOS partition into two @@ -1894,10 +1893,10 @@ partitions? Yes. DOS extended partitions are mapped in at the end of the - other slices in FreeBSD, e.g. your D: drive might be /dev/sd0s5, - your E: drive /dev/sd0s6, and so on. This example assumes, of + other slices in FreeBSD, e.g. your D: drive might be /dev/sd0s5, + your E: drive /dev/sd0s6, and so on. This example assumes, of course, that your extended partition is on SCSI drive 0. For IDE - drives, substitute ``wd'' for ``sd'' appropriately. You otherwise + drives, substitute wd for sd appropriately. You otherwise mount extended partitions exactly like you would mount any other DOS drive, e.g.: @@ -2501,7 +2500,7 @@ This is probably not the place to go into a detailed examination of how Makefiles work; suffice it to say that the line - starting with ``MAN3'' ensures that the ElectricFence man page is + starting with MAN3 ensures that the ElectricFence man page is compressed after installation, to help conserve your precious disk space. The original port did not provide an ``install'' target, so the three lines from ``do-install'' ensure that the files @@ -3735,8 +3734,8 @@ Floppy drive controller: fd0 is the A: floppy drive, and - fd1 is the B: drive. + remap=tt>fd0 is the A: floppy drive, and + fd1 is the B: drive. ft0 is a QIC-80 tape drive attached to the floppy controller. Comment out any lines corresponding to devices you do not have. @@ -4709,7 +4708,7 @@ controller wcd0 This means that you should look for some entries - that start with wcd0 in the + that start with wcd0 in the /dev directory, possibly followed by a letter, such as c, or preceded by the letter r, which means a raw device. It turns out that those files are not there, so I must @@ -4717,8 +4716,7 @@ # sh MAKEDEV wcd0 When this script finishes, you will find that - there are now wcd0c and rwcd0c entries in /dev so + there are now wcd0c and rwcd0c entries in /dev so you know that it executed correctly. For sound cards, the command: @@ -8785,7 +8783,7 @@ Replace the job name on the header page with text. The job name is normally the name of the first file of the job, or - ``stdin'' if you are printing standard input. + stdin if you are printing standard input. @@ -18806,13 +18804,13 @@ Each nx= entry matches another - gettytab capability name + gettytab capability name Each tc= entry matches another - gettytab capability name + gettytab capability name @@ -22576,8 +22574,7 @@ Get pop software from the Ports collection that - can be found in /usr/ports or packages + can be found in /usr/ports or packages collection. This handbook section has a complete reference on the system. @@ -22780,8 +22777,7 @@ Do not panic, this is only a few hundred kilobytes in size. - The file README in the cf directory can serve as a basic + The file README in the cf directory can serve as a basic introduction to m4 configuration. For UUCP delivery, you are best advised to use the @@ -23555,15 +23551,15 @@ into a CTM supported tree. You can recognize these transition deltas by the - X appended to the number + X appended to the number (src-cur.3210XEmpty.gz for instance). The - designation following the X - corresponds to the origin of your initial seed. ``Empty'' is - an empty directory, ``R225'' would designate the 2.2.5 release, - etc. As a rule a base transition from ``Empty'' is producted + designation following the X + corresponds to the origin of your initial seed. Empty is + an empty directory, R225 would designate the 2.2.5 release, + etc. As a rule a base transition from Empty is producted every 100 deltas. By the way, they are large! 25 to 30 Megabytes of gzip'ed data is - common for the ``XEmpty'' deltas. + common for the XEmpty deltas. Once you've picked a base delta to start from, you will also need all deltas with higher numbers following it. diff --git a/en_US.ISO_8859-1/books/handbook/book.sgml b/en_US.ISO_8859-1/books/handbook/book.sgml index fa7bef4a17..43c2c91dce 100644 --- a/en_US.ISO_8859-1/books/handbook/book.sgml +++ b/en_US.ISO_8859-1/books/handbook/book.sgml @@ -1861,8 +1861,7 @@ If your machine is already running MS-DOS and has little or no free space available for FreeBSD's installation, all is not lost! - You may find the FIPS utility, provided in the tools directory on the FreeBSD CDROM or on the + You may find the FIPS utility, provided in the tools directory on the FreeBSD CDROM or on the various FreeBSD ftp sites, to be quite useful. FIPS allows you to split an existing MS-DOS partition into two @@ -1894,10 +1893,10 @@ partitions? Yes. DOS extended partitions are mapped in at the end of the - other slices in FreeBSD, e.g. your D: drive might be /dev/sd0s5, - your E: drive /dev/sd0s6, and so on. This example assumes, of + other slices in FreeBSD, e.g. your D: drive might be /dev/sd0s5, + your E: drive /dev/sd0s6, and so on. This example assumes, of course, that your extended partition is on SCSI drive 0. For IDE - drives, substitute ``wd'' for ``sd'' appropriately. You otherwise + drives, substitute wd for sd appropriately. You otherwise mount extended partitions exactly like you would mount any other DOS drive, e.g.: @@ -2501,7 +2500,7 @@ This is probably not the place to go into a detailed examination of how Makefiles work; suffice it to say that the line - starting with ``MAN3'' ensures that the ElectricFence man page is + starting with MAN3 ensures that the ElectricFence man page is compressed after installation, to help conserve your precious disk space. The original port did not provide an ``install'' target, so the three lines from ``do-install'' ensure that the files @@ -3735,8 +3734,8 @@ Floppy drive controller: fd0 is the A: floppy drive, and - fd1 is the B: drive. + remap=tt>fd0 is the A: floppy drive, and + fd1 is the B: drive. ft0 is a QIC-80 tape drive attached to the floppy controller. Comment out any lines corresponding to devices you do not have. @@ -4709,7 +4708,7 @@ controller wcd0 This means that you should look for some entries - that start with wcd0 in the + that start with wcd0 in the /dev directory, possibly followed by a letter, such as c, or preceded by the letter r, which means a raw device. It turns out that those files are not there, so I must @@ -4717,8 +4716,7 @@ # sh MAKEDEV wcd0 When this script finishes, you will find that - there are now wcd0c and rwcd0c entries in /dev so + there are now wcd0c and rwcd0c entries in /dev so you know that it executed correctly. For sound cards, the command: @@ -8785,7 +8783,7 @@ Replace the job name on the header page with text. The job name is normally the name of the first file of the job, or - ``stdin'' if you are printing standard input. + stdin if you are printing standard input. @@ -18806,13 +18804,13 @@ Each nx= entry matches another - gettytab capability name + gettytab capability name Each tc= entry matches another - gettytab capability name + gettytab capability name @@ -22576,8 +22574,7 @@ Get pop software from the Ports collection that - can be found in /usr/ports or packages + can be found in /usr/ports or packages collection. This handbook section has a complete reference on the system. @@ -22780,8 +22777,7 @@ Do not panic, this is only a few hundred kilobytes in size. - The file README in the cf directory can serve as a basic + The file README in the cf directory can serve as a basic introduction to m4 configuration. For UUCP delivery, you are best advised to use the @@ -23555,15 +23551,15 @@ into a CTM supported tree. You can recognize these transition deltas by the - X appended to the number + X appended to the number (src-cur.3210XEmpty.gz for instance). The - designation following the X - corresponds to the origin of your initial seed. ``Empty'' is - an empty directory, ``R225'' would designate the 2.2.5 release, - etc. As a rule a base transition from ``Empty'' is producted + designation following the X + corresponds to the origin of your initial seed. Empty is + an empty directory, R225 would designate the 2.2.5 release, + etc. As a rule a base transition from Empty is producted every 100 deltas. By the way, they are large! 25 to 30 Megabytes of gzip'ed data is - common for the ``XEmpty'' deltas. + common for the XEmpty deltas. Once you've picked a base delta to start from, you will also need all deltas with higher numbers following it.