diff --git a/en_US.ISO8859-1/books/faq/book.sgml b/en_US.ISO8859-1/books/faq/book.sgml index 82f63a3316..f1bbd05a9e 100644 --- a/en_US.ISO8859-1/books/faq/book.sgml +++ b/en_US.ISO8859-1/books/faq/book.sgml @@ -14,7 +14,7 @@ The FreeBSD Documentation Project - $FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.173 2001/04/13 03:30:09 murray Exp $ + $FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.174 2001/04/15 19:17:27 jim Exp $ 1995 @@ -2675,9 +2675,10 @@ Filesystem 1024-blocks Used Avail Capacity Mounted on FreeBSD supports the SCSI ZIP drive out of the box, of course. The ZIP drive can only be set to run at SCSI target IDs 5 or 6, but if your SCSI host adapter's BIOS supports it you - can even boot from it. I don't know which host adapters let you - boot from targets other than 0 or 1... look at your docs (and - let me know if it works out for you). + can even boot from it. It is not clear which host + adapters support booting from targets other than 0 or 1, + so you will have to consult your adapter's documentation + if you'd like to use this feature. ATAPI (IDE) Zip drives are supported in FreeBSD 2.2.6 and later releases. @@ -5183,15 +5184,15 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx - I recommend making a dated snapshot of your kernel + It is recommended that you make a dated snapshot + of your kernel in kernel.YYMMDD after you get it all working, that way if you do something dire the next time you play with your configuration you can boot that kernel instead of having to go all the way back to kernel.GENERIC. This is particularly important if you're now booting off a controller that isn't - supported in the GENERIC kernel (yes, personal - experience). + supported in the GENERIC kernel. @@ -5655,10 +5656,10 @@ C:\="DOS" For 2.2.x systems this procedure assumes that DOS, NT, FreeBSD, or whatever have been installed into their respective fdisk partitions on the same - disk. In my case DOS & NT are in the first fdisk partition - and FreeBSD is in the second. I also installed FreeBSD to boot - from its native partition, not - the disk MBR. + disk. This example was tested on a system where DOS & NT + were on the first fdisk partition, and FreeBSD on the second. + FreeBSD was also set up to boot from its native partition, not + the disk's MBR. Mount a DOS-formatted floppy (if you've converted to NTFS) or the FAT partition, under, say, @@ -5923,9 +5924,10 @@ C:\="DOS" IDE drives are not able to allow access to both drives on the same channel at the same time (FreeBSD doesn't support mode - 4, so all IDE disk I/O is programmed). I would - still suggest putting your swap on a separate drive however. - The drives are so cheap, it is not worth worrying about. + 4, so all IDE disk I/O is programmed). + It is still suggested that you put your swap partition on a + separate driver, however: the drives are so cheap, it is not + worth worrying about. Swapping over NFS is only recommended if you do not have a local disk to swap to. Swapping over NFS is slow and @@ -7043,8 +7045,8 @@ define(`confDELIVERY_MODE',`deferred')dnl /dev) and symbolic links tend to screw that up. You need to use tools that understand these things, which means &man.dump.8; and &man.tar.1;. - I recommend doing the data moves in single user mode, - but it's not required. + Although it is suggested that you move the data in single user + mode, it is not required. You should never use anything but &man.dump.8; and &man.restore.8; to move the root file system. The @@ -8124,9 +8126,10 @@ bitmap_name="/boot/splash.pcx" to your ~/.xinitrc. - For example, I have mapped the 3 keys to be F13, F14, and - F15 respectively. This makes it easy to map them to useful - functions within applications or your window manager. + For example, you could map the 3 keys top be F13, F14, and + F15, respectively. This would make it easy to map them to + useful functions within applications or your window + manager, as demonstrated further down. To do this put the following in ~/.xmodmaprc. @@ -8135,7 +8138,8 @@ bitmap_name="/boot/splash.pcx" keycode 116 = F14 keycode 117 = F15 - I use fvwm2 and have mapped the keys + If you use fvwm2, for example, you + could map the keys so that F13 iconifies (or de-iconifies) the window the cursor is in, F14 brings the window the cursor is in to the front or, if it is already at the front, pushes it to the back, and F15 @@ -8144,8 +8148,9 @@ keycode 117 = F15 any part of the desktop visible (and the logo on the key matches its functionality). - The entries in my ~/.fvwmrc which map - the keys this way are: + The following entries in + ~/.fvwmrc implement the + aforementioned setup: Key F13 FTIWS A Iconify Key F14 FTIWS A RaiseLower @@ -11078,11 +11083,11 @@ raisechar=^^ blindfolded volunteers who have also had 250 micrograms of LSD-25 administered beforehand. 35% of the volunteers said that FreeBSD tasted sort of orange, whereas Linux tasted like purple - haze. Neither group mentioned any particular variances in - temperature that I can remember. We eventually had to throw the + haze. Neither group mentioned any significant variances in + temperature. We eventually had to throw the results of this survey out entirely anyway when we found that too many volunteers were wandering out of the room during the - tests, thus skewing the results. I think most of the volunteers + tests, thus skewing the results. We think most of the volunteers are at Apple now, working on their new scratch and sniff GUI. It's a funny old business we're in! @@ -11124,9 +11129,9 @@ raisechar=^^ take off running and don't ever look back! Freed from the counterbalancing influence of the BSD daemons, the twin demons of DOS and Windows are often able to re-assert total control - over your machine to the eternal damnation of your soul. Given - a choice, I think I'd prefer to get used to the scratchy - noises, myself! + over your machine to the eternal damnation of your soul. + Now that you know, given a choice you'd probably prefer to get + used to the scratchy noises, no? diff --git a/en_US.ISO_8859-1/books/faq/book.sgml b/en_US.ISO_8859-1/books/faq/book.sgml index 82f63a3316..f1bbd05a9e 100644 --- a/en_US.ISO_8859-1/books/faq/book.sgml +++ b/en_US.ISO_8859-1/books/faq/book.sgml @@ -14,7 +14,7 @@ The FreeBSD Documentation Project - $FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.173 2001/04/13 03:30:09 murray Exp $ + $FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.174 2001/04/15 19:17:27 jim Exp $ 1995 @@ -2675,9 +2675,10 @@ Filesystem 1024-blocks Used Avail Capacity Mounted on FreeBSD supports the SCSI ZIP drive out of the box, of course. The ZIP drive can only be set to run at SCSI target IDs 5 or 6, but if your SCSI host adapter's BIOS supports it you - can even boot from it. I don't know which host adapters let you - boot from targets other than 0 or 1... look at your docs (and - let me know if it works out for you). + can even boot from it. It is not clear which host + adapters support booting from targets other than 0 or 1, + so you will have to consult your adapter's documentation + if you'd like to use this feature. ATAPI (IDE) Zip drives are supported in FreeBSD 2.2.6 and later releases. @@ -5183,15 +5184,15 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx - I recommend making a dated snapshot of your kernel + It is recommended that you make a dated snapshot + of your kernel in kernel.YYMMDD after you get it all working, that way if you do something dire the next time you play with your configuration you can boot that kernel instead of having to go all the way back to kernel.GENERIC. This is particularly important if you're now booting off a controller that isn't - supported in the GENERIC kernel (yes, personal - experience). + supported in the GENERIC kernel. @@ -5655,10 +5656,10 @@ C:\="DOS" For 2.2.x systems this procedure assumes that DOS, NT, FreeBSD, or whatever have been installed into their respective fdisk partitions on the same - disk. In my case DOS & NT are in the first fdisk partition - and FreeBSD is in the second. I also installed FreeBSD to boot - from its native partition, not - the disk MBR. + disk. This example was tested on a system where DOS & NT + were on the first fdisk partition, and FreeBSD on the second. + FreeBSD was also set up to boot from its native partition, not + the disk's MBR. Mount a DOS-formatted floppy (if you've converted to NTFS) or the FAT partition, under, say, @@ -5923,9 +5924,10 @@ C:\="DOS" IDE drives are not able to allow access to both drives on the same channel at the same time (FreeBSD doesn't support mode - 4, so all IDE disk I/O is programmed). I would - still suggest putting your swap on a separate drive however. - The drives are so cheap, it is not worth worrying about. + 4, so all IDE disk I/O is programmed). + It is still suggested that you put your swap partition on a + separate driver, however: the drives are so cheap, it is not + worth worrying about. Swapping over NFS is only recommended if you do not have a local disk to swap to. Swapping over NFS is slow and @@ -7043,8 +7045,8 @@ define(`confDELIVERY_MODE',`deferred')dnl /dev) and symbolic links tend to screw that up. You need to use tools that understand these things, which means &man.dump.8; and &man.tar.1;. - I recommend doing the data moves in single user mode, - but it's not required. + Although it is suggested that you move the data in single user + mode, it is not required. You should never use anything but &man.dump.8; and &man.restore.8; to move the root file system. The @@ -8124,9 +8126,10 @@ bitmap_name="/boot/splash.pcx" to your ~/.xinitrc. - For example, I have mapped the 3 keys to be F13, F14, and - F15 respectively. This makes it easy to map them to useful - functions within applications or your window manager. + For example, you could map the 3 keys top be F13, F14, and + F15, respectively. This would make it easy to map them to + useful functions within applications or your window + manager, as demonstrated further down. To do this put the following in ~/.xmodmaprc. @@ -8135,7 +8138,8 @@ bitmap_name="/boot/splash.pcx" keycode 116 = F14 keycode 117 = F15 - I use fvwm2 and have mapped the keys + If you use fvwm2, for example, you + could map the keys so that F13 iconifies (or de-iconifies) the window the cursor is in, F14 brings the window the cursor is in to the front or, if it is already at the front, pushes it to the back, and F15 @@ -8144,8 +8148,9 @@ keycode 117 = F15 any part of the desktop visible (and the logo on the key matches its functionality). - The entries in my ~/.fvwmrc which map - the keys this way are: + The following entries in + ~/.fvwmrc implement the + aforementioned setup: Key F13 FTIWS A Iconify Key F14 FTIWS A RaiseLower @@ -11078,11 +11083,11 @@ raisechar=^^ blindfolded volunteers who have also had 250 micrograms of LSD-25 administered beforehand. 35% of the volunteers said that FreeBSD tasted sort of orange, whereas Linux tasted like purple - haze. Neither group mentioned any particular variances in - temperature that I can remember. We eventually had to throw the + haze. Neither group mentioned any significant variances in + temperature. We eventually had to throw the results of this survey out entirely anyway when we found that too many volunteers were wandering out of the room during the - tests, thus skewing the results. I think most of the volunteers + tests, thus skewing the results. We think most of the volunteers are at Apple now, working on their new scratch and sniff GUI. It's a funny old business we're in! @@ -11124,9 +11129,9 @@ raisechar=^^ take off running and don't ever look back! Freed from the counterbalancing influence of the BSD daemons, the twin demons of DOS and Windows are often able to re-assert total control - over your machine to the eternal damnation of your soul. Given - a choice, I think I'd prefer to get used to the scratchy - noises, myself! + over your machine to the eternal damnation of your soul. + Now that you know, given a choice you'd probably prefer to get + used to the scratchy noises, no?