diff --git a/en_US.ISO8859-1/books/faq/book.sgml b/en_US.ISO8859-1/books/faq/book.sgml index 7b03e9cb8f..4f2681ca13 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.ISO8859-1/books/faq/book.sgml,v 1.210 2001/06/11 01:16:41 ache Exp $ + $FreeBSD: doc/en_US.ISO8859-1/books/faq/book.sgml,v 1.211 2001/06/13 11:36:18 tom Exp $ 1995 @@ -104,7 +104,7 @@ that may be used for any purpose and without strings attached. Many of us have a significant investment in the code (and project) and would certainly not mind a little financial - compensation now and then, but we're definitely not prepared + compensation now and then, but we are definitely not prepared to insist on it. We believe that our first and foremost mission is to provide code to any and all comers, and for whatever purpose, so that the code gets the @@ -177,7 +177,7 @@ low change count over the wizzy new features of the latest -CURRENT snapshot. Releases can come from either branch, but you should only use - -CURRENT if you're sure that you're + -CURRENT if you are sure that you are prepared for its increased volatility (relative to -STABLE, that is). @@ -235,7 +235,7 @@ To give people who would like to run -CURRENT or - -STABLE but who don't have the time and/or bandwidth to + -STABLE but who do not have the time and/or bandwidth to follow it on a day-to-day basis an easy way of bootstrapping it onto their systems. @@ -531,7 +531,7 @@ Channel #FreeBSD on - EFNet is a FreeBSD forum, but don't go there for tech + EFNet is a FreeBSD forum, but do not go there for tech support or to try and get folks there to help you avoid the pain of reading man pages or doing your own research. It is a chat channel, first and foremost, and topics there @@ -573,9 +573,9 @@ Each of these channels are distinct and are not connected to each other. Their chat styles also differ, so you may need to try each to find one suited to your chat style. As with - *all* types of IRC traffic, if you're easily offended or can't + *all* types of IRC traffic, if you are easily offended or cannot deal with lots of young people (and more than a few older - ones) doing the verbal equivalent of jello wrestling, don't + ones) doing the verbal equivalent of jello wrestling, do not even bother with it. @@ -646,7 +646,7 @@ manuals may be hard to get a hold of. For a more in-depth look at the 4.4BSD kernel - organization, you can't go wrong with . A good book on system administration is This book covers the basics, as well as TCP/IP, DNS, NFS, - SLIP/PPP, sendmail, INN/NNTP, printing, etc. It's expensive + SLIP/PPP, sendmail, INN/NNTP, printing, etc. It is expensive but worth it. The third edition covers Solaris, HP/UX, FreeBSD, and Linux. @@ -1032,14 +1032,14 @@ File: +DESC (ignored) - Well, we can't pay, but we might arrange a free CD or + Well, we cannot pay, but we might arrange a free CD or T-shirt and a Contributor's Handbook entry if you submit a translation of the documentation. Before you begin translating please contact the freebsd-doc mailing list at freebsd-doc@FreeBSD.org; you may find somebody to help with the translation effort. You may also find out there is already a team translating the docs into your - chosen language, who surely wouldn't turn down your help. + chosen language, who surely would not turn down your help. @@ -1099,7 +1099,7 @@ File: +DESC (ignored) For information on FreeBSD multimedia applications, please see the multimedia - page. If you're interested specifically in the Bt848 video capture chip, then follow that link. @@ -1107,7 +1107,7 @@ File: +DESC (ignored) The FreeBSD handbook also has a fairly complete bibliography - section which is worth reading if you're looking for actual + section which is worth reading if you are looking for actual books to buy. @@ -1241,7 +1241,7 @@ File: +DESC (ignored) - You'll need a 386 or better PC, with 5 MB or more of RAM + You will need a 386 or better PC, with 5 MB or more of RAM and at least 60 MB of hard disk space. It can run with a low end MDA graphics card but to run X11R6, a VGA or better video card is needed. @@ -1263,7 +1263,7 @@ File: +DESC (ignored) 2.2, need at least 5MB to install on a new system. All versions of FreeBSD, including 3.0, will - run in 4MB of RAM, they just can't run the + run in 4MB of RAM, they just can not run the installation program in 4MB. You can add extra memory for the install process, if you like, and then after the system is up and running, go back to 4MB. Or you could always just swap your @@ -1301,7 +1301,7 @@ File: +DESC (ignored) - Currently there's no way to just + Currently there is no way to just make a custom install floppy. You have to cut a whole new release, which will include your install floppy. @@ -1470,13 +1470,13 @@ File: +DESC (ignored) uses, and install new boot blocks that can handle the different partition ID. - First, you'll need to restore the machine to a state where + First, you will need to restore the machine to a state where it can get through its self-test screen. Doing this requires powering up the machine without letting it find a FreeBSD partition on its primary disk. One way is to remove the hard disk and temporarily move it to an older ThinkPad (such as a ThinkPad 600) or a desktop PC with an appropriate conversion cable. Once - it's there, you can delete the FreeBSD partition and move the hard + it is there, you can delete the FreeBSD partition and move the hard disk back. The ThinkPad should now be in a bootable state again. @@ -1573,7 +1573,7 @@ File: +DESC (ignored) - If you're seeing things like the machine grinding to a halt + If you are seeing things like the machine grinding to a halt or spontaneously rebooting when you try to boot the install floppy, here are three questions to ask yourself:- @@ -1581,19 +1581,19 @@ File: +DESC (ignored) Did you use a new, freshly-formatted, error-free floppy (preferably a brand-new one straight out of the box, as - opposed to the magazine coverdisk that's been lying under + opposed to the magazine coverdisk that has been lying under the bed for the last three years)? Did you download the floppy image in binary (or image) - mode? (don't be embarrassed, even the best of us have + mode? (do not be embarrassed, even the best of us have accidentally downloaded a binary file in ASCII mode at least once!) - If you're using Windows95 or Win98 did you run + If you are using Windows95 or Win98 did you run fdimage or rawrite in pure DOS mode? These OS's can interfere with programs that write directly to hardware, which the disk creation program @@ -1603,7 +1603,7 @@ File: +DESC (ignored) There have also been reports of Netscape causing problems - when downloading the boot floppy, so it's probably best to use + when downloading the boot floppy, so it is probably best to use a different FTP client if you can. @@ -1855,7 +1855,7 @@ BUSY By the geometry of a disk, we mean the - number of cylinders, heads and sectors/track on a disk - I'll + number of cylinders, heads and sectors/track on a disk - I will refer to this as C/H/S for convenience. This is how the PC's BIOS works out which area on a disk to read/write from. @@ -1867,7 +1867,7 @@ BUSY the physical geometry, as the sector density varies across the disk - what manufacturers claim is the quote physical geometry is usually the - geometry that they've worked out results in the least wasted + geometry that they have worked out results in the least wasted space. For IDE disks, FreeBSD does work in terms of C/H/S, but all modern drives will convert this into block references internally as well. @@ -1875,7 +1875,7 @@ BUSY All that matters is the logical geometry - the answer that the BIOS gets when it asks what is your geometry? and then uses to access - the disk. As FreeBSD uses the BIOS when booting, it's very + the disk. As FreeBSD uses the BIOS when booting, it is very important to get this right. In particular, if you have more than one operating system on a disk, they must all agree on the geometry, otherwise you will have serious problems @@ -1884,14 +1884,14 @@ BUSY For SCSI disks, the geometry to use depends on whether extended translation support is turned on in your controller (this is often referred to as support for DOS disks - >1GB or something similar). If it's turned off, then + >1GB or something similar). If it is turned off, then use N cylinders, 64 heads and 32 sectors/track, where N is the capacity of the disk in MB. For example, a 2GB disk should pretend to have 2048 cylinders, 64 heads and 32 sectors/track. - If it is turned on (it's often supplied + If it is turned on (it is often supplied this way to get around certain limitations in MSDOS) and the disk capacity is more than 1GB, use M cylinders, 63 sectors per track (*not* 64), and 255 heads, where 'M' is the disk capacity @@ -1903,7 +1903,7 @@ BUSY around this is usually to create a small DOS partition on the disk. The correct geometry should then be detected (and you can always remove the DOS partition in the partition editor if you - don't want to keep it, or leave it around for programming + do not want to keep it, or leave it around for programming network cards and the like). Alternatively, there is a freely available utility @@ -1943,10 +1943,10 @@ BUSY FreeBSD recognizes the Ontrack Disk Manager and makes allowances for it. Other disk managers are not supported. - If you just want to use the disk with FreeBSD you don't + If you just want to use the disk with FreeBSD you do not need a disk manager. Just configure the disk for as much space as the BIOS can deal with (usually 504 megabytes), and FreeBSD - should figure out how much space you really have. If you're + should figure out how much space you really have. If you are using an old disk with an MFM controller, you may need to explicitly tell FreeBSD how many cylinders to use. @@ -1954,7 +1954,7 @@ BUSY operating system, you may be able to do without a disk manager: just make sure the FreeBSD boot partition and the slice for the other operating system are in the first 1024 cylinders. If - you're reasonably careful, a 20 megabyte boot partition should + you are reasonably careful, a 20 megabyte boot partition should be plenty. @@ -2036,9 +2036,9 @@ BUSY visual configuration screen which allows you to configure the kernel's settings for most common ISA cards. - It's still recommended that you eventually build a new + It is still recommended that you eventually build a new kernel containing just the drivers that you need, just to save a - bit of RAM, but it's no longer a strict requirement for most + bit of RAM, but it is no longer a strict requirement for most systems. @@ -2127,7 +2127,7 @@ BUSY Then type boot, and your system should boot correctly. - To make this change permanent (ie so you don't have to + To make this change permanent (ie so you do not have to do this everytime you reboot or turn on your FreeBSD machine), put the line root_disk_unit="disk_number" in /boot/loader.conf.local @@ -2179,7 +2179,7 @@ disk wd2 at wdc1 drive 1 # change from wd3 to wd2wcarchive's configuration for more details. If you plan to install - this much memory into a machine, you need to be careful. You'll + this much memory into a machine, you need to be careful. You will probably want to use ECC memory and to reduce capacitive loading use 9 chip memory modules vice 18 chip memory modules. @@ -2398,7 +2398,7 @@ Filesystem 1024-blocks Used Avail Capacity Mounted on must. Please note that the security profile is just a default - setting. All programs can be enabled and disabled after you've + setting. All programs can be enabled and disabled after you have installed FreeBSD by editing or adding the appropriate line(s) to /etc/rc.conf. For more information on the latter, please see the &man.rc.conf.5; manual page. @@ -2517,7 +2517,7 @@ Filesystem 1024-blocks Used Avail Capacity Mounted on The security profile is not a silver bullet! Setting - it high does not mean you don't have to keep up with security + it high does not mean you do not have to keep up with security issues by reading an appropriate mailing list, using good passwords and passphrases, and @@ -2644,7 +2644,7 @@ Filesystem 1024-blocks Used Avail Capacity Mounted on 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. + if you would like to use this feature. ATAPI (IDE) Zip drives are supported in FreeBSD 2.2.6 and later releases. @@ -2679,7 +2679,7 @@ Filesystem 1024-blocks Used Avail Capacity Mounted on SCSI devices, so the should all look like SCSI disks to FreeBSD, and the IDE EZ should look like an IDE drive. - I'm not sure how well FreeBSD supports + I am not sure how well FreeBSD supports changing the media out while running. You will of course need to dismount the drive before swapping media, and make sure that any external units are powered on when you boot the system so @@ -2839,19 +2839,19 @@ usbd_flags="" - If you're running a post-2.2.5 version of FreeBSD, the + If you are running a post-2.2.5 version of FreeBSD, the necessary driver, psm, is included and enabled in the kernel. The kernel should detect your PS/2 mouse at boot time. - If you're running a previous but relatively recent version + If you are running a previous but relatively recent version of FreeBSD (2.1.x or better) then you can simply enable it in the kernel configuration menu at installation time, otherwise later with at the boot: prompt. It is disabled by default, so you will need to enable it explicitly. - If you're running an older version of FreeBSD then you'll + If you are running an older version of FreeBSD then you will have to add the following lines to your kernel configuration file and compile a new kernel. @@ -2869,7 +2869,7 @@ usbd_flags="" See the Handbook entry on - configuring the kernel if you've no experience with + configuring the kernel if you have no experience with building kernels. Once you have a kernel detecting @@ -3169,9 +3169,9 @@ diff -u -r1.60.2.1 -r1.60.2.2 &man.chio.1; man page. - If you're not using AMANDA + If you are not using AMANDA or some other product that already understands changers, - remember that they're only know how to move a tape from one + remember that they are only know how to move a tape from one point to another, so you need to keep track of which slot a tape is in, and which slot the tape currently in the drive needs to go back to. @@ -3195,7 +3195,7 @@ diff -u -r1.60.2.1 -r1.60.2.2 This is only for sound! This driver does not support CD-ROMs, SCSI or joysticks on these cards, except for the SoundBlaster. The SoundBlaster SCSI interface and some - non-SCSI CDROMS are supported, but you can't boot off this + non-SCSI CDROMS are supported, but you cannot boot off this device. @@ -3229,7 +3229,7 @@ diff -u -r1.60.2.1 -r1.60.2.2 - I don't have a math co-processor - is that bad? + I do not have a math co-processor - is that bad? @@ -3243,12 +3243,12 @@ diff -u -r1.60.2.1 -r1.60.2.2 or accuracy of the math emulation code (see the section on FP emulation). In particular, drawing arcs in X will be VERY slow. It is highly recommended that you - buy a math co-processor; it's well worth it. + buy a math co-processor; it is well worth it. Some math co-processors are better than others. It pains us to say it, but nobody ever got fired for buying - Intel. Unless you're sure it works with FreeBSD, beware of + Intel. Unless you are sure it works with FreeBSD, beware of clones. @@ -3290,7 +3290,7 @@ diff -u -r1.60.2.1 -r1.60.2.2 Certain Micron motherboards have a non-conforming PCI BIOS implementation that causes grief when FreeBSD boots because PCI - devices don't get configured at their reported addresses. + devices do not get configured at their reported addresses. Disable the Plug and Play Operating System flag in the BIOS to work around this problem. More information @@ -3440,7 +3440,7 @@ diff -u -r1.60.2.1 -r1.60.2.2 these automatically. However, many drives are shipped with this feature disabled, for some mysterious reason... - To enable this, you'll need to edit the first device page + To enable this, you will need to edit the first device page mode, which can be done on FreeBSD by giving the command (as root) @@ -3548,7 +3548,7 @@ ARRE (Auto Read Reallocation Enbld): 1 onwards. The revision letter is located after the Assembly number on the edge of the card. The 742a has 2 ROM chips on it, one is the BIOS chip and the other is the Firmware chip. - FreeBSD doesn't care what version of BIOS chip you have but it + FreeBSD does not care what version of BIOS chip you have but it does care about what version of firmware chip. Buslogic will send upgrade ROMS out if you call their tech support dept. The BIOS and Firmware chips are shipped as a matched pair. You must @@ -3613,7 +3613,7 @@ ARRE (Auto Read Reallocation Enbld): 1 quit at the prompt, and install your system as usual. While - it's recommended you compile and install a custom kernel + it is recommended you compile and install a custom kernel anyway. Hopefully, future versions will have a proper fix for @@ -3634,14 +3634,14 @@ quit - It's broken. It cannot handle commands on both channels + It is broken. It cannot handle commands on both channels simultaneously. There's a workaround available now and it is enabled automatically if your system uses this chip. For the details refer to the manual page of the disk driver (man 4 wd). - If you're already running FreeBSD 2.2.1 or 2.2.2 with a + If you are already running FreeBSD 2.2.1 or 2.2.2 with a CMD640 IDE controller and you want to use the second channel, build a new kernel with options "CMD640" enabled. This is the default for 2.2.5 and later. @@ -3664,7 +3664,7 @@ quit -c option and change the ed0/de0/... entry to match your board. - If you're using the BNC connector on your network card, + If you are using the BNC connector on your network card, you may also see device timeouts because of bad termination. To check this, attach a terminator directly to the NIC (with no cable) and see if the error messages go away. @@ -3720,9 +3720,9 @@ quit drive, or the drive is not visible on the bus. Feed the drive something, and/or check its master/slave status if it is IDE (ATAPI). It can take a couple of seconds for a CDROM drive to - notice that it's been fed, so be patient. + notice that it has been fed, so be patient. - Sometimes a SCSI CD-ROM may be missed because it hadn't + Sometimes a SCSI CD-ROM may be missed because it had not enough time to answer the bus reset. If you have a SCSI CD-ROM please try to add the following symbol into your kernel configuration file and recompile. @@ -3743,7 +3743,7 @@ quit This extension specifies that all filenames are stored using Unicode two-byte characters. Currently, efforts are under way to introduce a generic Unicode interface into the FreeBSD - kernel, but since that isn't ready yet, the CD9660 driver does + kernel, but since that is not ready yet, the CD9660 driver does not have the ability to decode the characters in the filenames. @@ -3761,7 +3761,7 @@ quit - If it's parallel, and the only problem is that it's terribly + If it is parallel, and the only problem is that it is terribly slow, try setting your printer port into polled mode: @@ -3796,20 +3796,20 @@ quit - If it's a problem with part of the base FreeBSD system, + If it is a problem with part of the base FreeBSD system, it may also be buggy code, but more often than not these problems are found and fixed long before us general FAQ - readers get to use these bits of code (that's what -current + readers get to use these bits of code (that is what -current is for). In particular, a dead giveaway that this is *not* a FreeBSD - bug is if you see the problem when you're compiling a program, + bug is if you see the problem when you are compiling a program, but the activity that the compiler is carrying out changes each time. - For example, suppose you're running make buildworld, and + For example, suppose you are running make buildworld, and the compile fails while trying to compile ls.c in to ls.o. If you next run make buildworld again, and the compile fails in the same place then this is a broken build -- try updating your @@ -3822,7 +3822,7 @@ quit the point in the program which is attempting to access a bogus address and then fix it. - In the second case you need to verify that it's not your + In the second case you need to verify that it is not your hardware at fault. Common causes of this include: @@ -3838,15 +3838,15 @@ quit The processor running is overheating: This might be because the processor has been overclocked, or the fan on the processor might have died. In either case you need to - ensure that you have hardware running at what it's + ensure that you have hardware running at what it is specified to run at, at least while trying to solve this problem. i.e. Clock it back to the default settings. - If you are overclocking then note that it's far cheaper + If you are overclocking then note that it is far cheaper to have a slow system than a fried system that needs replacing! Also the wider community is not often sympathetic to problems on overclocked systems, whether you - believe it's safe or not. + believe it is safe or not. @@ -3887,10 +3887,10 @@ quit or hardware can still pass faulty memory. Finally, if none of this has helped it is possible that - you've just found a bug in FreeBSD, and you should follow the + you have just found a bug in FreeBSD, and you should follow the instructions to send a problem report. - There's an extensive FAQ on this at There is an extensive FAQ on this at the SIG11 problem FAQ @@ -3907,7 +3907,7 @@ quit The problem is that this card uses address 2e8, and the fourth serial port does too. Due to a bug (feature?) in the &man.sio.4; - driver it will touch this port even if you don't have the + driver it will touch this port even if you do not have the fourth serial port, and even if you disable sio3 (the fourth port) which normally uses this address. @@ -3926,7 +3926,7 @@ quit sio1, sio2 and sio3 (all of them). This way - the sio driver doesn't get activated -> no + the sio driver does not get activated -> no problems. @@ -3935,7 +3935,7 @@ quit - If you want to be able to use your serial ports, you'll + If you want to be able to use your serial ports, you will have to build a new kernel with the following modification: in /usr/src/sys/i386/isa/sio.c find the one occurrence of the string 0x2e8 and remove @@ -3967,16 +3967,16 @@ quit To work around this problem, you need to use the kernel option specified below. There is a way to get complete memory - information from the BIOS, but we don't have room in the + information from the BIOS, but we do not have room in the bootblocks to do it. Someday when lack of room in the - bootblocks is fixed, we'll use the extended BIOS functions to - get the full memory information...but for now we're stuck with + bootblocks is fixed, we will use the extended BIOS functions to + get the full memory information...but for now we are stuck with the kernel option. options "MAXMEM=n" Where n is your memory in - Kilobytes. For a 128 MB machine, you'd want to use + Kilobytes. For a 128 MB machine, you would want to use 131072. @@ -4003,7 +4003,7 @@ quit to your kernel config file, where n is a number in the range 512-4096, depending on the number of concurrent TCP connections you need - to support. I'd recommend trying 2048 - this should get rid of + to support. I would recommend trying 2048 - this should get rid of the panic completely. You can monitor the number of mbuf clusters allocated/in use on the system with netstat @@ -4169,7 +4169,7 @@ quit persists, keep the sysctl set to one and set the NTIMECOUNTER option in your kernel to increasingly large values. If by the time you have reached - NTIMECOUNTER=20 the problem isn't solved, + NTIMECOUNTER=20 the problem is not solved, interrupts are too hosed on your machine for reliable timekeeping. @@ -4395,7 +4395,7 @@ IO range check 0x00 activate 0x01 information. If this is on the global Internet, the problem may be that your server's resolver is not functioning correctly. To check, try to look up another host--say, - www.yahoo.com. If it doesn't work, that's + www.yahoo.com. If it does not work, that is your problem. @@ -4541,7 +4541,7 @@ kern.timecounter.hardware: TSC -> i8254 Commercial Applications - This section is still very sparse, though we're hoping, of + This section is still very sparse, though we are hoping, of course, that companies will add to it! :) The FreeBSD group has no financial interest in any of the companies listed here but simply lists them as a public service (and feels that commercial @@ -4642,7 +4642,7 @@ kern.timecounter.hardware: TSC -> i8254 Be sure to specify that you want the FreeBSD version of - Motif when ordering (don't forget to mention the architecture + Motif when ordering (do not forget to mention the architecture you want too)! Versions for NetBSD and OpenBSD are also sold by Apps2go. This is currently a FTP only download. @@ -4933,7 +4933,7 @@ kern.timecounter.hardware: TSC -> i8254 /stand/sysinstall (under the post-configuration menu item) or invoke the &man.pkg.add.1; command on the specific package - files you're interested in installing. Package files can + files you are interested in installing. Package files can usually be identified by their .tgz suffix and CDROM distribution people will have a packages/All directory on their CD which @@ -5001,7 +5001,7 @@ kern.timecounter.hardware: TSC -> i8254 Because POSIX says that there shall be such a shell. The more complicated answer: many people need to write shell - scripts which will be portable across many systems. That's why + scripts which will be portable across many systems. That is why POSIX specifies the shell and utility commands in great detail. Most scripts are written in Bourne shell, and because several important programming interfaces (&man.make.1;, &man.system.3;, @@ -5015,7 +5015,7 @@ kern.timecounter.hardware: TSC -> i8254 The existing implementation is our best effort at meeting as many of these requirements simultaneously as we can. In order to keep /bin/sh small, we have not provided many - of the convenience features that other shells have. That's why the + of the convenience features that other shells have. That is why the Ports Collection includes more featureful shells like bash, scsh, tcsh, and zsh. (You can compare for yourself the memory utilization of all these shells by looking at the @@ -5058,7 +5058,7 @@ kern.timecounter.hardware: TSC -> i8254 - You don't have a math co-processor, right? + You do not have a math co-processor, right? You will need to add the alternative math emulator to your kernel; you do this by adding the following to your kernel config file and it will be compiled in. @@ -5090,7 +5090,7 @@ ibcs2=NO It will load the ibcs2 kernel module at startup. - You'll then need to set up /compat/ibcs2/dev to look + You will then need to set up /compat/ibcs2/dev to look like: lrwxr-xr-x 1 root wheel 9 Oct 15 22:20 X0R@ -> /dev/null @@ -5118,7 +5118,7 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx After installing the inn package or port, an excellent place to start is Dave Barr's - INN Page where you'll find the INN FAQ. + INN Page where you will find the INN FAQ. @@ -5151,7 +5151,7 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx - If you're running a FreeBSD version that lags + If you are running a FreeBSD version that lags significantly behind -CURRENT or -STABLE, you may need a ports upgrade kit from http://www.FreeBSD.org/ports/. If you are up to date, @@ -5222,7 +5222,7 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx - I'd like to customize my kernel. Is it difficult? + I would like to customize my kernel. Is it difficult? @@ -5238,7 +5238,7 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx 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 + important if you are now booting off a controller that is not supported in the GENERIC kernel. @@ -5254,10 +5254,10 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx Let me guess. You removed npx0 (see &man.npx.4;) - from your kernel configuration file because you don't have a + from your kernel configuration file because you do not have a math co-processor, right? Wrong! :-) The npx0 is - MANDATORY. Even if you don't have a + MANDATORY. Even if you do not have a mathematic co-processor, you must include the npx0 device. @@ -5279,7 +5279,7 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx panic. However, if you are running low on disk space, or - you simply don't want to run a debug kernel, make sure + you simply do not want to run a debug kernel, make sure that both of the following are true: @@ -5348,8 +5348,8 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr buildkernel and make installkernel targets, and your source tree is different from the one used to build the currently running - system (e.g., you're compiling 4.3-RELEASE on a 4.0-RELEASE - system). If you're attempting an upgrade, please read the + system (e.g., you are compiling 4.3-RELEASE on a 4.0-RELEASE + system). If you are attempting an upgrade, please read the /usr/src/UPDATING file, paying particular attention to the COMMON ITEMS section at the end. @@ -5375,7 +5375,7 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr linkend="stable">FreeBSD-STABLE builds fine the majority of the time. If you have not already done so, try re-fetching the source tree and see if the problem goes - away. Try using a different server in case the one you're + away. Try using a different server in case the one you are using is having problems. @@ -5477,9 +5477,9 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr - Whether it's a removable drive like a ZIP or an EZ drive + Whether it is a removable drive like a ZIP or an EZ drive (or even a floppy, if you want to use it that way), or a new - hard disk, once it's installed and recognized by the system, + hard disk, once it is installed and recognized by the system, and you have your cartridge/floppy/whatever slotted in, things are pretty much the same for all devices. @@ -5487,32 +5487,32 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr URL="http://www.vmunix.com/mark/FreeBSD/ZIP-FAQ.html"> Mark Mayo's ZIP FAQ) - If it's a ZIP drive or a floppy , you've already got a DOS + If it is a ZIP drive or a floppy , you have already got a DOS filesystem on it, you can use a command like this: &prompt.root; mount -t msdos /dev/fd0c /floppy - if it's a floppy, or this: + if it is a floppy, or this: &prompt.root; mount -t msdos /dev/da2s4 /zip for a ZIP disk with the factory configuration. - For other disks, see how they're laid out using + For other disks, see how they are laid out using &man.fdisk.8; or &man.sysinstall.8;. The rest of the examples will be for a ZIP drive on da2, the third SCSI disk. - Unless it's a floppy, or a removable you plan on sharing - with other people, it's probably a better idea to stick a BSD - file system on it. You'll get long filename support, at least a + Unless it is a floppy, or a removable you plan on sharing + with other people, it is probably a better idea to stick a BSD + file system on it. You will get long filename support, at least a 2X improvement in performance, and a lot more stability. First, you need to redo the DOS-level partitions/filesystems. You can either use &man.fdisk.8; or /stand/sysinstall, or for a small drive - that you don't want to bother with multiple operating system + that you do not want to bother with multiple operating system support on, just blow away the whole FAT partition table (slices) and just use the BSD partitioning: @@ -5521,11 +5521,11 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr You can use disklabel or /stand/sysinstall to create multiple BSD - partitions. You'll certainly want to do this if you're adding - swap space on a fixed disk, but it's probably irrelevant on a + partitions. You will certainly want to do this if you are adding + swap space on a fixed disk, but it is probably irrelevant on a removable drive like a ZIP. - Finally, create a new file system, this one's on our ZIP + Finally, create a new file system, this one is on our ZIP drive using the whole disk: &prompt.root; newfs /dev/rda2c @@ -5534,7 +5534,7 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr &prompt.root; mount /dev/da2c /zip - and it's probably a good idea to add a line like this to + and it is probably a good idea to add a line like this to /etc/fstab (see &man.fstab.5;) so you can just type mount /zip in the future: @@ -5572,7 +5572,7 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr will notice them automatically. If you want something to be run once per day, week, or - month, it's probably better to add shell scripts + month, it is probably better to add shell scripts /usr/local/etc/periodic, and let the &man.periodic.8; command run from the system cron schedule it with the other periodic system tasks. @@ -5602,9 +5602,9 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr group. If this feature were not there, anybody with an account on a system who also found out root's password would be able to gain superuser level access to the - system. With this feature, this isn't strictly true; + system. With this feature, this is not strictly true; &man.su.1; will prevent them from even trying to enter the - password if they aren't in wheel. + password if they are not in wheel. To allow someone to su to root, simply put them in the wheel group. @@ -5615,7 +5615,7 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr I made a mistake in rc.conf, or another startup file, and - now I can't edit it because the filesystem is read-only. + now I cannot edit it because the filesystem is read-only. What should I do? @@ -5725,7 +5725,7 @@ C:\="DOS" 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) + Mount a DOS-formatted floppy (if you have converted to NTFS) or the FAT partition, under, say, /mnt. @@ -5844,7 +5844,7 @@ C:\="DOS" instead of in the Master Boot Record. You can then boot LILO from BootEasy. - If you're running Windows-95 and Linux this is recommended + If you are running Windows-95 and Linux this is recommended anyway, to make it simpler to get Linux booting again if you should need to reinstall Windows95 (which is a Jealous Operating System, and will bear no other Operating Systems in @@ -5872,7 +5872,7 @@ C:\="DOS" compatible with other operating systems. So why it is called dangerous? A disk in - this mode doesn't contain what normal PC utilities would + this mode does not contain what normal PC utilities would consider a valid fdisk table. Depending on how well they have been designed, they might complain at you once they are getting in contact with such a disk, or even worse, they might damage @@ -5881,10 +5881,10 @@ C:\="DOS" layout is known to confuse many BIOSsen, including those from AWARD (eg. as found in HP Netserver and Micronics systems as well as many others) and Symbios/NCR (for the popular 53C8xx - range of SCSI controllers). This isn't a complete list, there + range of SCSI controllers). This is not a complete list, there are more. Symptoms of this confusion include the read error message printed by the FreeBSD bootstrap when it - can't find itself, as well as system lockups when + cannot find itself, as well as system lockups when booting. Why have this mode at all then? It only saves a few kbytes @@ -5900,40 +5900,40 @@ C:\="DOS" disks. When the FreeBSD installer creates slices, it has to record the location of these slices on the disk in a fashion that corresponds with the way the BIOS expects to find them. If - it gets it wrong, you won't be able to boot. + it gets it wrong, you will not be able to boot. Dangerously dedicated mode tries to work around this by making the problem simpler. In some cases, it - gets it right. But it's meant to be used as a last-ditch + gets it right. But it is meant to be used as a last-ditch alternative - there are better ways to solve the problem 99 times out of 100. So, how do you avoid the need for DD mode - when you're installing? Start by making a note of the geometry + when you are installing? Start by making a note of the geometry that your BIOS claims to be using for your disks. You can arrange to have the kernel print this as it boots by specifying at the boot: prompt, or using boot -v in the loader. Just before the installer starts, the kernel will print a list of BIOS - geometries. Don't panic - wait for the installer to start and + geometries. Do not panic - wait for the installer to start and then use scrollback to read the numbers. Typically the BIOS disk units will be in the same order that FreeBSD lists your disks, first IDE, then SCSI. - When you're slicing up your disk, check that the disk + When you are slicing up your disk, check that the disk geometry displayed in the FDISK screen is correct (ie. it - matches the BIOS numbers); if it's wrong, use the + matches the BIOS numbers); if it is wrong, use the g key to fix it. You may have to do this if - there's absolutely nothing on the disk, or if the disk has been + there is absolutely nothing on the disk, or if the disk has been moved from another system. Note that this is only an issue with - the disk that you're going to boot from; FreeBSD will sort + the disk that you are going to boot from; FreeBSD will sort itself out just fine with any other disks you may have. - Once you've got the BIOS and FreeBSD agreeing about the + Once you have got the BIOS and FreeBSD agreeing about the geometry of the disk, your problems are almost guaranteed to be over, and with no need for DD mode at all. If, however, you are still greeted with the dreaded read - error message when you try to boot, it's time to cross + error message when you try to boot, it is time to cross your fingers and go for it - there's nothing left to lose. @@ -5989,7 +5989,7 @@ C:\="DOS" in order to be able to accomodate a kernel core. IDE drives are not able to allow access to both drives on - the same channel at the same time (FreeBSD doesn't support mode + the same channel at the same time (FreeBSD does not support mode 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 @@ -6237,7 +6237,7 @@ C:\="DOS" non-PnP-aware driver is compiled into the kernel. These include devices such as keyboard controllers, the programmable interrupt controller chip, and several other - bits of standard infrastructure. The resources can't be + bits of standard infrastructure. The resources cannot be assigned because there is already a driver using those addresses. @@ -6253,7 +6253,7 @@ C:\="DOS" - Don't turn on quotas on /, + Do not turn on quotas on /, @@ -6294,7 +6294,7 @@ C:\="DOS" - What's inappropriate about my ccd? + What is inappropriate about my ccd? @@ -6386,15 +6386,15 @@ options SYSVMSG # enable for messaging files under /usr/src/usr.sbin/sendmail/cf - If you didn't install your system with full sources, + If you did not install your system with full sources, the sendmail config stuff has been broken out into a separate - source distribution tarball just for you. Assuming you've got + source distribution tarball just for you. Assuming you have got your CD-ROM mounted, do: &prompt.root; cd /cdrom/src &prompt.root; cat scontrib.?? | tar xzf - -C /usr/src contrib/sendmail - Don't panic, this is only a few hundred kilobytes in size. + Do not panic, this is only a few hundred kilobytes in size. The file README in the cf directory can serve as a basic introduction to m4 configuration. @@ -6444,11 +6444,11 @@ Cw youruucpnodename.UUCP nocanonify features will prevent any usage of the DNS during mail delivery. The UUCP_RELAY clause is needed for bizarre - reasons, don't ask. Simply put an Internet hostname there that + reasons, do not ask. Simply put an Internet hostname there that is able to handle .UUCP pseudo-domain addresses; most likely, you will enter the mail relay of your ISP there. - Once you've got this, you need this file called + Once you have got this, you need this file called /etc/mailertable. A typical example of this gender again: @@ -6516,25 +6516,25 @@ rewrite: ruleset 0 returns: $# uucp-dom $@ if-bus $: foo \ - If you've got a statically assigned IP number, you should + If you have got a statically assigned IP number, you should not need to adjust anything from the default. Set your host name up as your assigned internet name and sendmail will do the rest. - If you've got a dynamically assigned IP number and use a + If you have got a dynamically assigned IP number and use a dialup ppp connection to the internet, you will probably be given a mailbox on your ISPs mail server. Lets assume your ISPs domain is myISP.com, and that your user name is - user. Lets also assume you've + user. Lets also assume you have called your machine bsd.home and that your ISP has told you that you may use relay.myISP.com as a mail relay. - In order to retrieve mail from your mailbox, you'll need + In order to retrieve mail from your mailbox, you will need to install a retrieval agent. Fetchmail is a good choice as it supports many different protocols. Usually, POP3 will be provided by - your ISP. If you've chosen to use user-ppp, you can + your ISP. If you have chosen to use user-ppp, you can automatically fetch your mail when a connection to the 'net is established with the following entry in /etc/ppp/ppp.linkup: @@ -6552,7 +6552,7 @@ rewrite: ruleset 0 returns: $# uucp-dom $@ if-bus $: foo \ process your mailqueue as soon as the connection to the 'net is established. - I'm assuming that you have an account for + I am assuming that you have an account for user on bsd.home. In the home directory of user on @@ -6602,34 +6602,35 @@ define(`confDELIVERY_MODE',`deferred')dnl - What's this UID 0 toor account? Have I + What is this UID 0 toor account? Have I been compromised? - Don't worry. toor is an + Do not worry. toor is an + alternative superuser account (toor is root spelt backwards). Previously it was created when the &man.bash.1; shell was installed but now it is created by default. It is intended to be used with a non-standard shell so - you don't have to change root's default - shell. This is important as shells which aren't part of the + you do not have to change root's default + shell. This is important as shells which are not part of the base distribution (for example a shell installed from ports or packages) are likely be to be installed in /usr/local/bin which, by default, resides on a different filesystem. If root's shell is located in /usr/local/bin and /usr (or whatever filesystem contains - /usr/local/bin) isn't mounted for some - reason, root won't be able to log in to + /usr/local/bin) is not mounted for some + reason, root will not be able to log in to fix a problem (although if you reboot into single user mode - you'll be prompted for the path to a shell). + you will be prompted for the path to a shell). Some people use toor for day-to-day root tasks with a non-standard shell, leaving root, with a standard shell, for - single user mode or emergencies. By default you can't log - in using toor as it doesn't have a + single user mode or emergencies. By default you cannot log + in using toor as it does not have a password, so log in as root and set a password for toor if you want to use it. @@ -6637,14 +6638,14 @@ define(`confDELIVERY_MODE',`deferred')dnl - I've fogotten the root password! What do I do? + I have fogotten the root password! What do I do? - Don't Panic! Simply restart the system, type + Do not Panic! Simply restart the system, type boot -s at the Boot: prompt (just -s for FreeBSD releases before 3.2) to enter Single User mode. At the question about the shell to use, - hit ENTER. You'll be dropped to a &prompt.root; prompt. Enter + hit ENTER. You will be dropped to a &prompt.root; prompt. Enter mount -u / to remount your root filesystem read/write, then run mount -a to remount all the filesystems. Run passwd root to change @@ -6730,7 +6731,7 @@ define(`confDELIVERY_MODE',`deferred')dnl The error comes from the Kerberos distributed - authentication system. The problem isn't fatal but annoying. + authentication system. The problem is not fatal but annoying. You can either run su with the -K option, or uninstall Kerberos as described in the next question. @@ -6745,7 +6746,7 @@ define(`confDELIVERY_MODE',`deferred')dnl To remove Kerberos from the system, reinstall the bin distribution for the release you are running. If you have - the CDROM, you can mount the cd (we'll assume on /cdrom) + the CDROM, you can mount the cd (we will assume on /cdrom) and run &prompt.root; cd /cdrom/bin @@ -6765,7 +6766,7 @@ define(`confDELIVERY_MODE',`deferred')dnl If you have lots of telnet, ssh, X, or screen users, - you'll probably run out of pseudoterminals. Here's how to + you will probably run out of pseudoterminals. Here is how to add more: @@ -6800,7 +6801,7 @@ define(`confDELIVERY_MODE',`deferred')dnl - Reboot the system with the new kernel and you're + Reboot the system with the new kernel and you are ready to go. @@ -7098,7 +7099,7 @@ define(`confDELIVERY_MODE',`deferred')dnl The best way is to reinstall the OS on the new disk, then move the user data over. This is highly - recommended if you've been tracking -stable for more + recommended if you have been tracking -stable for more than one release, or have updated a release instead of installing a new one. You can install booteasy on both disks with &man.boot0cfg.8;, and dual boot them until @@ -7117,8 +7118,8 @@ define(`confDELIVERY_MODE',`deferred')dnl formatting-media tutorial for details on this process. - Now you've got the new disk set up, and are ready - to move the data. Unfortunately, you can't just blindly + Now you have got the new disk set up, and are ready + to move the data. Unfortunately, you cannot just blindly copy the data. Things like device files (in /dev) and symbolic links tend to screw that up. You need to use tools that understand @@ -7156,7 +7157,7 @@ define(`confDELIVERY_MODE',`deferred')dnl For example, if you are going to move root to /dev/ad1s1a, with /mnt as the temporary mount point, - it's: + it is: &prompt.root; newfs /dev/ad1s1a &prompt.root; mount /dev/ad1s1a @@ -7168,7 +7169,7 @@ define(`confDELIVERY_MODE',`deferred')dnl say, splitting one into two, or combing two into one, you may find yourself needing to move everything under a subdirectory to a new location. Since &man.dump.8; - works with file systems, it can't do this. So you use + works with file systems, it cannot do this. So you use &man.tar.1;. The general command to move /old to /new for &man.tar.1; is: @@ -7177,7 +7178,7 @@ define(`confDELIVERY_MODE',`deferred')dnl If /old has file systems mounted on that, and you - don't want to move that data or unmount them, you just + do not want to move that data or unmount them, you just add the 'l' flag to the first &man.tar.1;: &prompt.root; (cd /old; tar clf - .) | (cd /new; tar xpf -). @@ -7190,11 +7191,11 @@ define(`confDELIVERY_MODE',`deferred')dnl I tried to update my system to the latest -STABLE, but - got -RC or -BETA! What's going on? + got -RC or -BETA! What is going on? - Short answer: it's just a name. RC stands for + Short answer: it is just a name. RC stands for Release Candidate. It signifies that a release is imminent. In FreeBSD, -BETA is typically synonymous with the code freeze before a release. @@ -7214,7 +7215,7 @@ define(`confDELIVERY_MODE',`deferred')dnl which it will be derived from has to undergo a certain process. Part of this process is a code freeze. When a code freeze is initiated, the name of the branch is - changed to reflect that it's about to become a release. + changed to reflect that it is about to become a release. For example, if the branch used to be called 4.0-STABLE, its name will be changed to 4.1-BETA to signify the code freeze and signify that extra pre-release testing should @@ -7235,7 +7236,7 @@ define(`confDELIVERY_MODE',`deferred')dnl - Short answer: You're probably at security level + Short answer: You are probably at security level greater than 0. Reboot directly to single user mode to install the kernel. @@ -7256,12 +7257,12 @@ define(`confDELIVERY_MODE',`deferred')dnl - I can't change the time on my system by more than one second! + I cannot change the time on my system by more than one second! How do I get around this? - Short answer: You're probably at security level + Short answer: You are probably at security level greater than 1. Reboot directly to single user mode to change the date. @@ -7287,7 +7288,7 @@ define(`confDELIVERY_MODE',`deferred')dnl - No, there is no memory leak, and it's not using 256 Mbytes + No, there is no memory leak, and it is not using 256 Mbytes of memory. It simply likes to (i.e., always does) map an obscene amount of memory into its address space for convenience. There is nothing terribly wrong with this from a technical @@ -7311,7 +7312,7 @@ define(`confDELIVERY_MODE',`deferred')dnl - You're running at an elevated (i.e., greater than 0) + You are running at an elevated (i.e., greater than 0) securelevel. Lower the securelevel and try again. For more information, see the FAQ entry on securelevel and the &man.init.8; manual page. @@ -7390,7 +7391,7 @@ define(`confDELIVERY_MODE',`deferred')dnl - Your system is running at a raised securelevel, isn't + Your system is running at a raised securelevel, is not it? It is, indeed, impossible to start X at a raised securelevel. To see why, look at the &man.init.8; man page. @@ -7543,8 +7544,8 @@ EndSection Using Your X Server to Translate the Wheel Events - If you aren't running &man.moused.8;, or if - you don't want &man.moused.8; to translate your + If you are not running &man.moused.8;, or if + you do not want &man.moused.8; to translate your wheel events, you can have the X server do the event translation instead. This requires a couple of modifications to your @@ -7564,7 +7565,7 @@ EndSection 5. This is done with the ZAxisMapping option. - For example, if you aren't using + For example, if you are not using &man.moused.8;, and you have an IntelliMouse attached to the PS/2 mouse port you would use the following in @@ -7753,7 +7754,7 @@ ttyvb "/usr/libexec/getty Pc" cons25 on secure must leave at least one virtual terminal unused (or turned off) for it to use. That is to say that if you want to have a login prompt pop up for all - twelve of your Alt-function keys, you're out of luck - you + twelve of your Alt-function keys, you are out of luck - you can only do this for eleven of them if you also want to run an X server on the same machine. @@ -7787,13 +7788,13 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure &prompt.root; sh MAKEDEV vty12 Next, the easiest (and cleanest) way to activate the - virtual consoles is to reboot. However, if you really don't + virtual consoles is to reboot. However, if you really do not want to reboot, you can just shut down the X Window system and execute (as root): &prompt.root; kill -HUP 1 - It's imperative that you completely shut down X Window if + It is imperative that you completely shut down X Window if it is running, before running this command. If you don't, your system will probably appear to hang/lock up after executing the kill command. @@ -7850,7 +7851,7 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure rc.local (see &man.rc.8;) or from a X.sh script in /usr/local/etc/rc.d. Both are equally - valid, and one may work in situations where the other doesn't. + valid, and one may work in situations where the other does not. In both cases the result is the same: X will popup a graphical login: prompt. @@ -7900,7 +7901,7 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure xconsole not working. This is because of the way console permissions are set - by default. On a multi-user system, one doesn't necessarily + by default. On a multi-user system, one does not necessarily want just any user to be able to write on the system console. For users who are logging directly onto a machine with a VTY, the &man.fbtab.5; @@ -7978,7 +7979,7 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure options PSM_CHECKSYNC See the section on building - a kernel if you've no experience with building + a kernel if you have no experience with building kernels. With this option, there should be less chance of @@ -8001,7 +8002,7 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure psmintr: out of sync (xxxx != yyyy) - and find your mouse doesn't seem to work properly. + and find your mouse does not seem to work properly. If this happens, disable the synchronization check code by setting the driver flags for the PS/2 mouse driver to 0x100. @@ -8035,7 +8036,7 @@ UserConfig> quit and 2.1.X. In versions 2.2 through 2.2.5, apply the following patch to /sys/i386/isa/psm.c and rebuild the kernel. See the section on building a kernel if you've no + linkend="make-kernel">building a kernel if you have no experience with building kernels. @@ -766,6 +766,8 @@ @@ -8068,7 +8069,7 @@ UserConfig> quit - When building an X app, imake can't + When building an X app, imake cannot find Imake.tmpl. Where is it? @@ -8127,7 +8128,7 @@ UserConfig> quit The first step is to find a bitmap version of your splash screen. Release 3.1 only supports Windows bitmap - splash screens. Once you've found your splash screen of + splash screens. Once you have found your splash screen of choice copy it to /boot/splash.bmp. Next, you need to have a /boot/loader.rc file that contains @@ -8164,7 +8165,7 @@ bitmap_load="YES" This assumes you are using /boot/splash.bmp for your splash - screen. If you'd rather use a PCX file, copy it to + screen. If you would rather use a PCX file, copy it to /boot/splash.pcx, create a /boot/loader.rc as instructed above, and create a @@ -8250,7 +8251,7 @@ keycode 117 = F15 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 pops up the main Workplace (application) menu even if the - cursor is not on the desktop, which is useful if you don't have + cursor is not on the desktop, which is useful if you do not have any part of the desktop visible (and the logo on the key matches its functionality). @@ -8452,7 +8453,7 @@ Key F15 A A Menu Workplace Nop - If you want to use the other ports, you'll have to specify + If you want to use the other ports, you will have to specify an additional parameter on the &man.ifconfig.8; command line. The default port is link0. To use the AUI port instead of the @@ -8780,7 +8781,7 @@ Znyx (2.2.x) ZX312, ZX314, ZX342, ZX345, ZX346, ZX348 Place an established rule early - on to handle the majority of TCP traffic. Don't put any + on to handle the majority of TCP traffic. Do not put any allow tcp statements before this rule. @@ -8924,7 +8925,7 @@ Znyx (2.2.x) ZX312, ZX314, ZX342, ZX345, ZX346, ZX348 - How do I mount a disk from a Windows machine that's on my + How do I mount a disk from a Windows machine that is on my network, like smbmount in Linux? @@ -8968,7 +8969,7 @@ Znyx (2.2.x) ZX312, ZX314, ZX342, ZX345, ZX346, ZX348 The first number in the message tells you how many - packets the kernel would have sent if the limit wasn't in + packets the kernel would have sent if the limit was not in place, and the second number tells you the limit. You can control the limit using the net.inet.icmp.icmplim sysctl variable @@ -8977,7 +8978,7 @@ Znyx (2.2.x) ZX312, ZX314, ZX342, ZX345, ZX346, ZX348 &prompt.root; sysctl -w net.inet.icmp.icmplim=300 - If you don't want to see messages about this in your + If you do not want to see messages about this in your log files, but you still want the kernel to do response limiting, you can use the net.inet.icmp.icmplim_output sysctl @@ -9001,7 +9002,7 @@ Znyx (2.2.x) ZX312, ZX314, ZX342, ZX345, ZX346, ZX348 - I can't make &man.ppp.8; work. What am I doing wrong? + I cannot make &man.ppp.8; work. What am I doing wrong? @@ -9026,12 +9027,12 @@ Znyx (2.2.x) ZX312, ZX314, ZX342, ZX345, ZX346, ZX348 *.* /var/log/ppp.log and that the file /var/log/ppp.log - exists. You can now find out a lot about what's going on - from the log file. Don't worry if it doesn't all make sense. + exists. You can now find out a lot about what is going on + from the log file. Do not worry if it does not all make sense. If you need to get help from someone, it may make sense to them. - If your version of ppp doesn't understand the + If your version of ppp does not understand the set log command, you should download the latest version. It will build on FreeBSD version @@ -9045,7 +9046,7 @@ Znyx (2.2.x) ZX312, ZX314, ZX342, ZX345, ZX346, ZX348 - This is usually because your hostname won't resolve. + This is usually because your hostname will not resolve. The best way to fix this is to make sure that /etc/hosts is consoluted by your resolver first by editing /etc/host.conf @@ -9060,7 +9061,7 @@ Znyx (2.2.x) ZX312, ZX314, ZX342, ZX345, ZX346, ZX348 Consult the relevant man pages for more details. You should be able to successfully - ping -c1 `hostname` when you're done. + ping -c1 `hostname` when you are done. @@ -9071,18 +9072,18 @@ Znyx (2.2.x) ZX312, ZX314, ZX342, ZX345, ZX346, ZX348 - First, check that you've got a default route. By running + First, check that you have got a default route. By running netstat -rn (see &man.netstat.1;), you should see two entries like this: Destination Gateway Flags Refs Use Netif Expire default 10.0.0.2 UGSc 0 0 tun0 10.0.0.2 10.0.0.1 UH 0 0 tun0 - This is assuming that you've used the addresses from the + This is assuming that you have used the addresses from the handbook, the man page or from the ppp.conf.sample file. - If you haven't got a default route, it may be because you're + If you haven't got a default route, it may be because you are running an old version of &man.ppp.8; - that doesn't understand the word HISADDR + that does not understand the word HISADDR in the ppp.conf file. If your version of ppp is from before FreeBSD 2.2.5, change the @@ -9124,7 +9125,7 @@ default 10.0.0.2 UGSc 0 0 tun0 section in your /etc/ppp/ppp.linkup file. This is only necessary if you have a dynamic IP address - or don't know the address of your gateway. If you're using + or do not know the address of your gateway. If you are using interactive mode, you can type the following after entering packet mode (packet mode is indicated by the capitalized PPP in the @@ -9194,7 +9195,7 @@ add 0 0 HISADDR call waiting enabled, your modem may hang up because it thinks (incorrectly) that it lost carrier. - There's a setting on most modems for determining how + There is a setting on most modems for determining how tolerant it should be to temporary losses of carrier. On a USR Sportster for example, this is measured by the S10 register in tenths of a second. To make your modem more @@ -9220,14 +9221,14 @@ add 0 0 HISADDR If you are using an external modem, you can simply try using &man.ping.8; to see if the TD light is flashing when you transmit data. - If it flashes (and the RD light doesn't), + If it flashes (and the RD light does not), the problem is with the remote end. If TD - doesn't flash, the problem is local. With an internal modem, - you'll need to use the set server command in + does not flash, the problem is local. With an internal modem, + you will need to use the set server command in your ppp.conf file. When the hang occurs, connect to ppp using pppctl. If your network connection suddenly revives (ppp was revived due to the activity on the - diagnostic socket) or if you can't connect (assuming the + diagnostic socket) or if you cannot connect (assuming the set socket command succeeded at startup time), the problem is local. If you can connect and things are still hung, enable local async logging with set log @@ -9248,13 +9249,13 @@ add 0 0 HISADDR - There's very little you can do about this. Most ISPs - will refuse to help if you're not running a Microsoft OS. + There is very little you can do about this. Most ISPs + will refuse to help if you are not running a Microsoft OS. You can enable lqr in your ppp.conf file, allowing ppp to detect the remote failure and hang up, but this detection is relatively slow and therefore not that useful. You may want to - avoid telling your ISP that you're running user-ppp.... + avoid telling your ISP that you are running user-ppp.... First, try disabling all local compression by adding the following to your configuration: @@ -9266,7 +9267,7 @@ deny pred1 deflate deflate24 protocomp acfcomp shortseq vj If things improve or if the problem is solved completely, determine which setting makes the difference through trial and error. This will provide good amunition when you contact - your ISP (although it may make it apparent that you're not + your ISP (although it may make it apparent that you are not running a Microsoft product). Before contacting your ISP, enable async logging locally @@ -9341,14 +9342,14 @@ deny pred1 deflate deflate24 protocomp acfcomp shortseq vj in the log that say magic is the same. Sometimes, these messages are harmless, and sometimes one side or the other exits. Most ppp implementations cannot survive - this problem, and even if the link seems to come up, you'll see + this problem, and even if the link seems to come up, you will see repeated configure requests and configure acknowledgements in the log file until ppp eventually gives up and closes the connection. This normally happens on server machines with slow disks that are spawning a getty on the port, and executing ppp from - a login script or program after login. I've also heard reports + a login script or program after login. I have also heard reports of it happening consistently when using slirp. The reason is that in the time taken between getty exiting and ppp starting, the client-side ppp starts sending Line Control Protocol (LCP) @@ -9367,8 +9368,8 @@ deny pred1 deflate deflate24 protocomp acfcomp shortseq vj (which also means ppp must change its magic). This produces a potentially enormous number of magic number changes, all of which are happily piling into the server's tty buffer. As soon - as ppp starts on the server, it's flooded with magic number - changes and almost immediately decides it's tried enough to + as ppp starts on the server, it is flooded with magic number + changes and almost immediately decides it has tried enough to negotiate LCP and gives up. Meanwhile, the client, who no longer sees the reflections, becomes happy just in time to see a hangup from the server. @@ -9401,7 +9402,7 @@ deny pred1 deflate deflate24 protocomp acfcomp shortseq vj There is currently an implementation mis-feature in - ppp where it doesn't associate + ppp where it does not associate LCP, CCP & IPCP responses with their original requests. As a result, if one ppp implementation is more than 6 seconds slower than the other @@ -9414,8 +9415,8 @@ deny pred1 deflate deflate24 protocomp acfcomp shortseq vj sending LCP requests immediately after connecting and B takes 7 seconds to start. When B starts, A - has sent 3 LCP REQs. We're assuming the line has ECHO switched - off, otherwise we'd see magic number problems as described in + has sent 3 LCP REQs. We are assuming the line has ECHO switched + off, otherwise we would see magic number problems as described in the previous section. B sends a REQ, then an ACK to the first of A's REQs. This results in @@ -9442,7 +9443,7 @@ deny pred1 deflate deflate24 protocomp acfcomp shortseq vj immediately receives the following ACK and enters OPENED. - This goes on 'till one side figures out that they're + This goes on 'till one side figures out that they are getting nowhere and gives up. The best way to avoid this is to configure one side to be @@ -9480,7 +9481,7 @@ deny pred1 deflate deflate24 protocomp acfcomp shortseq vj ppp mis-handling Predictor1 compression negotiation. This would only happen if both sides tried to negotiate different Compression Control Protocols - (CCP). This problem is now corrected, but if you're still + (CCP). This problem is now corrected, but if you are still running an old version of ppp, the problem can be circumvented with the line @@ -9496,7 +9497,7 @@ deny pred1 deflate deflate24 protocomp acfcomp shortseq vj When you execute the shell or ! command, ppp executes a - shell (or if you've passed any arguements, + shell (or if you have passed any arguements, ppp will execute those arguements). Ppp will wait for the command to complete before continuing. If you attempt to use the ppp link while running the command, the link @@ -9645,7 +9646,7 @@ CCP: Received Terminate Ack (1) state = Req-Sent (6) string. If you wish to see your connect speed and are using PAP - or CHAP (and therefore don't have anything to + or CHAP (and therefore do not have anything to chat after the CONNECT in the dial script - no set login script), you must make sure that you instruct ppp to expect the whole CONNECT @@ -9683,7 +9684,7 @@ CCP: Received Terminate Ack (1) state = Req-Sent (6) escapes. If you wish to actually send a \ - character to (say) your modem, you'd need something + character to (say) your modem, you would need something like: set dial "\"\" ATZ OK-ATZ-OK AT\\\\X OK" @@ -9723,7 +9724,7 @@ ATDT1234567 is actually termating due to a segmentation violation or some other signal that normally causes core to be dumped, and - you're sure you're using the latest version (see the start of + you are sure you are using the latest version (see the start of this section), then you should do the following: &prompt.user; tar xfz ppp-*.src.tar.gz @@ -9758,7 +9759,7 @@ ATDT1234567 All of this information should be given alongside your question, making it possible to diagnose the problem. - If you're familiar with gdb, you may wish to find out some + If you are familiar with gdb, you may wish to find out some other bits and pieces such as what actually caused the dump and the addresses & values of the relevant variables. @@ -9786,7 +9787,7 @@ ATDT1234567 ppps dynamic IP assignment, the interface address is changed, the original socket endpoint will be invalid. Any subsequent packets sent to the peer will usually - be dropped. Even if they aren't, any responses will not route + be dropped. Even if they are not, any responses will not route back to the originating machine as the IP number is no longer owned by that machine. @@ -9794,7 +9795,7 @@ ATDT1234567 problem. It would be nicest if the peer would re-assign the same IP number if possible :-) The current version of ppp does - this, but most other implementations don't. + this, but most other implementations do not. The easiest method from our side would be to never change the tun interface IP number, but instead to change all outgoing @@ -9804,7 +9805,7 @@ ATDT1234567 the latest version of ppp is doing (with the help of &man.libalias.3; and ppp's switch) - - it's maintaining all previous interface addresses and NATing + it is maintaining all previous interface addresses and NATing them to the last negotiated address. Another alternative (and probably the most reliable) would @@ -9820,7 +9821,7 @@ ATDT1234567 given an IP number of 255.255.255.255 up until the first SIOCAIFADDR ioctl is done. This would result in fully binding the socket. It would be up to ppp - to change the source IP number, but only if it's set to + to change the source IP number, but only if it is set to 255.255.255.255, and only the IP number and IP checksum would need to change. This, however is a bit of a hack as the kernel would be sending bad packets to an improperly configured @@ -9835,21 +9836,21 @@ ATDT1234567 - The reason games and the like don't work when libalias + The reason games and the like do not work when libalias is in use is that the machine on the outside will try to open a connection or send (unsolicited) UDP packets to the machine on - the inside. The NAT software doesn't know that it should send + the inside. The NAT software does not know that it should send these packets to the interior machine. To make things work, make sure that the only thing - running is the software that you're having problems with, then + running is the software that you are having problems with, then either run tcpdump on the tun interface of the gateway or enable ppp tcp/ip logging (set log +tcp/ip) on the gateway. When you start the offending software, you should see packets passing through the gateway machine. When something - comes back from the outside, it'll be dropped (that's the + comes back from the outside, it will be dropped (that is the problem). Note the port number of these packets then shut down the offending software. Do this a few times to see if the port numbers are consistent. If they are, then the following line in @@ -9865,13 +9866,13 @@ ATDT1234567 port is the destination port number of the packets. - You won't be able to use the software on other machines + You will not be able to use the software on other machines without changing the above command, and running the software on two internal machines at the same time is out of the question - after all, the outside world is seeing your entire internal network as being just a single machine. - If the port numbers aren't consistent, there are three + If the port numbers are not consistent, there are three more options: @@ -9927,7 +9928,7 @@ ATDT1234567 :65000 65000 Manually change the port number within the game to - 65000. If you've got a number of machines that you wish + 65000. If you have got a number of machines that you wish to play on assign a unique port number for each (i.e. 65001, 65002, etc) and add a nat port line for each one. @@ -10010,7 +10011,7 @@ ATDT1234567 modem, make sure your cable is properly shielded from interference - this may eradicate the problem. - If your link freezes as soon as you've connected and you + If your link freezes as soon as you have connected and you see a large number of FCS errors, this may be because your link is not 8 bit clean. Make sure your modem is not using software flow control (XON/XOFF). If your datalink @@ -10024,7 +10025,7 @@ ATDT1234567 may want to enable async logging at this point to determine if the incoming data is actually a login or shell prompt. If you have a shell prompt at the remote end, - it's possible to terminate ppp without dropping the line by + it is possible to terminate ppp without dropping the line by using the close lcp command (a following term command will reconnect you to the shell on the remote machine. @@ -10047,18 +10048,18 @@ ATDT1234567 Dan Flemming danflemming@mac.com for the Mac solution: - This is due to what's called a Black Hole + This is due to what is called a Black Hole router. MacOS and Windows 98 (and maybe other Microsoft OSs) send TCP packets with a requested segment size too big to fit into a PPPoE frame (MTU is 1500 by default for ethernet) - and have the don't + and have the do not fragment bit set (default of TCP) and the Telco router is not sending ICMP must fragment back to the www site you are trying to load. (Alternatively, the router is sending the ICMP packet correctly, but the firewall at the www site is dropping it.) When the www server is sending - you frames that don't fit into the PPPoE pipe the Telco router - drops them on the floor and your page doesn't load (some + you frames that do not fit into the PPPoE pipe the Telco router + drops them on the floor and your page does not load (some pages/graphics do as they are smaller than a MSS.) This seems to be the default of most Telco PPPoE configurations (if only they knew how to program a router... sigh...) @@ -10100,7 +10101,7 @@ ATDT1234567 The latest version of ppp (2.3 or greater) has an enable tcpmssfixup command that will automatically adjust the MSS to an appropriate - value. This facility is enabled by default. If you're stuck + value. This facility is enabled by default. If you are stuck with an older version of ppp, you may want to look at the tcpmssd port. @@ -10109,12 +10110,12 @@ ATDT1234567 - None of this helps - I'm desperate! What can I do? + None of this helps - I am desperate! What can I do? If all else fails, send as much information as you can, - including your config files, how you're starting + including your config files, how you are starting ppp, the relevant parts of your log file and the output of the netstat -rn command (before and after connecting) to @@ -10150,9 +10151,9 @@ ATDT1234567 &prompt.user; dmesg | grep sio - after your system's up and running. + after your system is up and running. - Here's some example output from the above command: + Here is some example output from the above command: sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A @@ -10169,7 +10170,7 @@ sio1: type 16550A The GENERIC kernel includes support for two serial ports using the same irq and port address - settings in the above example. If these settings aren't + settings in the above example. If these settings are not right for your system, or if you've added modem cards or have more serial ports than your kernel is configured for, just reconfigure your kernel. See section @@ -10197,8 +10198,8 @@ sio1: type 16550A - Don't worry, they have been merged with the - ttydX devices. You'll have to change + Do not worry, they have been merged with the + ttydX devices. You will have to change any old configuration files you have, though. @@ -10213,7 +10214,7 @@ sio1: type 16550A sio2 (see &man.sio.4;, known as COM3 in DOS), is on /dev/cuaa2 for dial-out devices, and on /dev/ttyd2 - for dial-in devices. What's the difference between these two + for dial-in devices. What is the difference between these two classes of devices? You use ttydX for dial-ins. When @@ -10222,10 +10223,10 @@ sio1: type 16550A cuaaX device to become inactive, and then wait for the carrier detect line to go active. When you open the cuaaX device, it makes sure the serial - port isn't already in use by the ttydX - device. If the port's available, it steals it + port is not already in use by the ttydX + device. If the port is available, it steals it from the ttydX device. Also, the - cuaaX device doesn't care about carrier + cuaaX device does not care about carrier detect. With this scheme and an auto-answer modem, you can have remote users log in and you can still dialout with the same modem and the system will take care of all the @@ -10273,7 +10274,7 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr - Not yet. You'll have to use a different irq for each + Not yet. You will have to use a different irq for each card. @@ -10288,14 +10289,14 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr The ttydX (or cuaaX) device is the regular device - you'll want to open for your applications. When a process - opens the device, it'll have a default set of terminal I/O + you will want to open for your applications. When a process + opens the device, it will have a default set of terminal I/O settings. You can see these settings with the command &prompt.root; stty -a -f /dev/ttyd1 When you change the settings to this device, the settings - are in effect until the device is closed. When it's reopened, + are in effect until the device is closed. When it is reopened, it goes back to the default set. To make changes to the default set, you can open and adjust the settings of the initial state device. For example, to turn on @@ -10337,7 +10338,7 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr So you want to become an Internet service provider, eh? - First, you'll need one or more modems that can auto-answer. + First, you will need one or more modems that can auto-answer. Your modem will need to assert carrier-detect when it detects a carrier and not assert it all the time. It will need to hang up the phone and reset itself when the data terminal ready @@ -10373,10 +10374,10 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointrdialup. The port is on and is insecure---meaning root logins on the port - aren't allowed. For dialin ports like this one, use the + are not allowed. For dialin ports like this one, use the ttydX entry. - It's common practice to use dialup as + It is common practice to use dialup as the terminal type. Many users set up in their .profile or .login files a prompt for the actual terminal type if the starting type is dialup. The example shows the port as @@ -10412,13 +10413,13 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr - If you're using another computer as a terminal into your + If you are using another computer as a terminal into your FreeBSD system, get a null modem cable to go between the two - serial ports. If you're using an actual terminal, see its + serial ports. If you are using an actual terminal, see its accompanying instructions. Then, modify - /etc/ttys (see &man.ttys.5;), like above. For example, if you're + /etc/ttys (see &man.ttys.5;), like above. For example, if you are hooking up a WYSE-50 terminal to the fifth serial port, use an entry like this: @@ -10460,7 +10461,7 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr - My stock Hayes modem isn't supported---what + My stock Hayes modem is not supported---what can I do? @@ -10470,7 +10471,7 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointrat=hayes in your /etc/remote (see &man.remote.5;) file. - The Hayes driver isn't smart enough to recognize some of + The Hayes driver is not smart enough to recognize some of the advanced features of newer modems---messages like BUSY, NO DIALTONE, or CONNECT 115200 will just confuse it. You @@ -10479,10 +10480,10 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointrAlso, the dial timeout for &man.tip.1; is 60 seconds. Your modem should use something less, or else tip - will think there's a communication problem. Try + will think there is a communication problem. Try ATS7=45&W. - Actually, as shipped &man.tip.1; doesn't yet + Actually, as shipped &man.tip.1; does not yet support it fully. The solution is to edit the file tipconf.h in the directory /usr/src/usr.bin/tip/tip. Obviously you @@ -10501,8 +10502,8 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr - Make what's called a direct entry in your - /etc/remote file (see &man.remote.5;). For example, if your modem's hooked + Make what is called a direct entry in your + /etc/remote file (see &man.remote.5;). For example, if your modem is hooked up to the first serial port, /dev/cuaa0, then put in the following line: @@ -10511,7 +10512,7 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointrUse the highest bps rate your modem supports in the br capability. Then, type tip cuaa0 (see &man.tip.1;) - and you'll be connected to your modem. + and you will be connected to your modem. If there is no /dev/cuaa0 on your system, do this: @@ -10552,7 +10553,7 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr - Put what's called a generic entry in your + Put what is called a generic entry in your /etc/remote file (see &man.remote.5;). For example: tip115200|Dial any phone number at 115200 bps:\ @@ -10583,7 +10584,7 @@ tip57600|Dial any phone number at 57600 bps:\ rate is appropriate with the br capability. &man.tip.1; thinks a good default is 1200 bps which is why it looks for - a tip1200 entry. You don't have to use 1200 + a tip1200 entry. You do not have to use 1200 bps, though. @@ -10595,7 +10596,7 @@ tip57600|Dial any phone number at 57600 bps:\ - Rather than waiting until you're connected and typing + Rather than waiting until you are connected and typing CONNECT host each time, use tip's cm capability. For example, these entries in @@ -10671,7 +10672,7 @@ big-university 5551114 then the force character is the nul character, which you can get by typing CTRL+2 or CTRL+SPACE. A pretty good value for single-char is SHIFT+CTRL+6, which - I've seen only used on some terminal servers. + I have seen only used on some terminal servers. You can have the force character be whatever you want by specifying the following in your @@ -10687,7 +10688,7 @@ big-university 5551114 - You must've pressed CTRL+A, &man.tip.1; + You must have pressed CTRL+A, &man.tip.1; raise character, specially designed for people with broken caps-lock keys. Use ~s as above and set the variable @@ -10695,7 +10696,7 @@ big-university 5551114 you can set it to the same as the force character, if you never expect to use either of these features. - Here's a sample .tiprc file perfect for Emacs users who + Here is a sample .tiprc file perfect for Emacs users who need to type CTRL+2 and CTRL+A a lot: force=^^ @@ -10712,7 +10713,7 @@ raisechar=^^ - If you're talking to another UNIX system, you can send + If you are talking to another UNIX system, you can send and receive files with ~p (put) and ~t (take). These commands run &man.cat.1; and @@ -10722,7 +10723,7 @@ raisechar=^^ ~p <local-file> [<remote-file>] ~t <remote-file> [<local-file>] - There's no error checking, so you probably should use + There is no error checking, so you probably should use another protocol, like zmodem. @@ -10804,7 +10805,7 @@ raisechar=^^ The simple answer is that free memory is wasted - memory. Any memory that your programs don't actively + memory. Any memory that your programs do not actively allocate is used within the FreeBSD kernel as disk cache. The values shown by &man.top.1; labelled as Inact, Cache, and @@ -10841,7 +10842,7 @@ raisechar=^^ The oldest and classic unix object format. It uses a short and compact header with a magic - number at the beginning that's often used to + number at the beginning that is often used to characterize the format (see &man.a.out.5; for more details). It contains three loaded segments: .text, .data, and .bss plus a symbol @@ -10871,7 +10872,7 @@ raisechar=^^ FreeBSD tries to work around this problem somewhat by providing a utility for branding a known ELF executable with - information about the ABI it's compliant with. See the + information about the ABI it is compliant with. See the man page for &man.brandelf.1; for more information. @@ -10928,7 +10929,7 @@ raisechar=^^ the Motorola 68k, VAXen, etc. Then some bright hardware engineer decided that if he - could force software to do some sleazy tricks, then he'd be + could force software to do some sleazy tricks, then he would be able to shave a few gates off the design and allow his CPU core to run faster. While it was made to work with this new kind of hardware (known these days as RISC), a.out @@ -10953,7 +10954,7 @@ raisechar=^^ automatically. Lots of hacks were done to the a.out format to allow all of these things to happen, and they basically worked for a time. In time, - a.out wasn't up to handling all these + a.out was not up to handling all these problems without an ever increasing overhead in code and complexity. While ELF solved many of these problems, it would be painful to switch from the system that @@ -10969,7 +10970,7 @@ raisechar=^^ support for building cross compilers, plugging in different formats at will, etc. Since many people wanted to build cross compilers targeting FreeBSD, they were out of luck since the - older sources that FreeBSD had for as and ld weren't up to the + older sources that FreeBSD had for as and ld were not up to the task. The new gnu tools chain (binutils) does support cross compiling, ELF, shared libraries, C++ extnensions, etc. In addition, many vendors are releasing @@ -11054,7 +11055,7 @@ raisechar=^^ - You'd think it'd be easy enough to change + You would think it would be easy enough to change UT_NAMESIZE and rebuild the whole world, and everything would just work. Unfortunately there are often scads of applications and utilities (including system tools) @@ -11064,7 +11065,7 @@ raisechar=^^ structures and buffers. Not only will this get you log files which are trashed (due to variable-length records getting written when fixed records were expected), but it can break - Sun's NIS clients and potentially cause other problems in + Suns NIS clients and potentially cause other problems in interacting with other UNIX systems. In FreeBSD 3.0 and later, the maximum name length has @@ -11073,13 +11074,13 @@ raisechar=^^ that this touched so many areas of the system is why, in fact, the change was not made until 3.0. - If you're absolutely confident in your ability to find + If you are absolutely confident in your ability to find and fix these sorts of problems for yourself when and if they pop up, you can increase the login name length in earlier releases by editing /usr/include/utmp.h and changing UT_NAMESIZE accordingly. You must also update MAXLOGNAME in /usr/include/sys/param.h to match the UT_NAMESIZE change. - Finally, if you build from sources, don't forget that + Finally, if you build from sources, do not forget that /usr/include is updated each time! Change the appropriate files in /usr/src/.. instead. @@ -11095,7 +11096,7 @@ raisechar=^^ doscmd DOS emulation which has been integrated and enhanced. Send mail to The FreeBSD - emulation discussion list if you're interested in + emulation discussion list if you are interested in joining this ongoing effort! For pre-3.0 systems, there is a neat utility called @@ -11187,7 +11188,7 @@ raisechar=^^ - Who's scratching in my memory banks?? + Who is scratching in my memory banks?? @@ -11198,9 +11199,9 @@ raisechar=^^ strange scratchy sound emanates from what appears to be the memory banks. - A. Yes! You'll see frequent references to + A. Yes! You will see frequent references to daemons in the BSD documentation, and what most - people don't know is that this refers to genuine, non-corporeal + people do not know is that this refers to genuine, non-corporeal entities that now possess your computer. The scratchy sound coming from your memory is actually high-pitched whispering exchanged among the daemons as they best decide how to deal @@ -11208,14 +11209,14 @@ raisechar=^^ If the noise gets to you, a good fdisk /mbr from DOS will get rid of them, - but don't be surprised if they react adversely and try to stop + but do not be surprised if they react adversely and try to stop you. In fact, if at any point during the exercise you hear the satanic voice of Bill Gates coming from the built-in speaker, 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. - Now that you know, given a choice you'd probably prefer to get + Now that you know, given a choice you would probably prefer to get used to the scratchy noises, no? @@ -11227,7 +11228,7 @@ raisechar=^^ MFC is an acronym for Merged From -CURRENT. - It's used in the CVS logs to denote when a change was + It is used in the CVS logs to denote when a change was migrated from the CURRENT to the STABLE branches. @@ -11239,7 +11240,7 @@ raisechar=^^ It stands for something in a secret language that only - members can know. It doesn't translate literally but its ok + members can know. It does not translate literally but its ok to tell you that BSD's translation is something between, Formula-1 Racing Team, Penguins are tasty snacks, and We have a better sense of @@ -11284,7 +11285,7 @@ raisechar=^^ - The really, really short answer is that you shouldn't. + The really, really short answer is that you should not. The somewhat longer answer is that just because you are capable of building a bikeshed doesn't mean you should stop others from building one just because you don't like the @@ -11312,7 +11313,7 @@ raisechar=^^ What is it about this bike shed? Some of you have asked me. - It's a long story, or rather it's an old story, but + It is a long story, or rather it is an old story, but it is quite short actually. C. Northcote Parkinson wrote a book in the early 1960'ies, called Parkinson's Law, which contains a lot of insight into the @@ -11512,7 +11513,7 @@ raisechar=^^ HEAD is not an actual branch tag, - like the other two; it's simply a symbolic constant for + like the other two; it is simply a symbolic constant for the current, non-branched development stream which we simply refer to as -CURRENT. @@ -11568,8 +11569,8 @@ doc-all the good bits onto your box... Finally, you need a chunk of empty space to build into. - Let's say it's in /some/big/filesystem, - and from the example above you've got the CVS repository in + Let's say it is in /some/big/filesystem, + and from the example above you have got the CVS repository in /home/ncvs: &prompt.root; setenv CVSROOT /home/ncvs # or export CVSROOT=/home/ncvs @@ -11589,7 +11590,7 @@ doc-all /some/big/filesystem/release and you will have a full FTP-type installation in /some/big/filesystem/release/R/ftp when - you're done. If you want to build your SNAP along some other + you are done. If you want to build your SNAP along some other branch than -CURRENT, you can also add RELEASETAG=SOMETAG to the make release command line above, e.g. RELEASETAG=RELENG_2_2 @@ -11652,7 +11653,7 @@ doc-all TUNE_1542 kernel configuration option in order to have this take place. Using it on those systems where it works may make your disks run faster, but on those systems - where it doesn't, your data could be corrupted. + where it does not, your data could be corrupted. @@ -11692,7 +11693,7 @@ ${RELEASEDIR}/tarballs/bindist/bin_tgz.) - I've written a kernel extension, who do I send it + I have written a kernel extension, who do I send it to? @@ -11762,7 +11763,7 @@ ${RELEASEDIR}/tarballs/bindist/bin_tgz.) This info is then combined with info from any ECU files on the hard disk or wired into the MLB BIOS. The ECU and BIOS PnP support for hardware on the MLB is usually synthetic, and - the peripherals don't really do genuine PnP. However by + the peripherals do not really do genuine PnP. However by examining the BIOS info plus the ECU info, the probe routines can cause the devices that are PnP to avoid those devices the probe code cannot relocate. @@ -11771,7 +11772,7 @@ ${RELEASEDIR}/tarballs/bindist/bin_tgz.) their I/O, DMA, IRQ and Memory-map address assignments. The devices will then appear at those locations and remain there until the next reboot, although there is nothing that says you - can't move them around whenever you want. + cannot move them around whenever you want. There is a lot of oversimplification above, but you should get the general idea. @@ -11826,7 +11827,7 @@ ${RELEASEDIR}/tarballs/bindist/bin_tgz.) - Can you assign a major number for a device driver I've + Can you assign a major number for a device driver I have written? @@ -11842,7 +11843,7 @@ ${RELEASEDIR}/tarballs/bindist/bin_tgz.) not, or are unable to because of licensing restrictions, then character major number 32 and block major number 8 have been reserved specifically for this purpose; please use them. In any - case, we'd appreciate hearing about your driver on + case, we would appreciate hearing about your driver on freebsd-hackers@FreeBSD.org. @@ -11916,14 +11917,14 @@ Cc: current@FreeBSD.org > trap number = 12 > panic: page fault - [When] you see a message like this, it's not enough to just + [When] you see a message like this, it is not enough to just reproduce it and send it in. The instruction pointer value that - I highlighted up there is important; unfortunately, it's also + I highlighted up there is important; unfortunately, it is also configuration dependent. In other words, the value varies - depending on the exact kernel image that you're using. If - you're using a GENERIC kernel image from one of the snapshots, - then it's possible for somebody else to track down the - offending function, but if you're running a custom kernel then + depending on the exact kernel image that you are using. If + you are using a GENERIC kernel image from one of the snapshots, + then it is possible for somebody else to track down the + offending function, but if you are running a custom kernel then only you can tell us where the fault occured. @@ -11933,7 +11934,7 @@ Cc: current@FreeBSD.org Write down the instruction pointer value. Note that the 0x8: part at the begining is not - significant in this case: it's the + significant in this case: it is the 0xf0xxxxxx part that we want. @@ -11947,17 +11948,17 @@ Cc: current@FreeBSD.org match since the symbols in the kernel symbol table are for the entry points of functions and the instruction pointer address will be somewhere inside a function, not - at the start. If you don't get an exact match, omit the + at the start. If you do not get an exact match, omit the last digit from the instruction pointer value and try again, i.e.: &prompt.user; nm -n /kernel.that.caused.the.panic | grep f0xxxxx - If that doesn't yield any results, chop off another + If that does not yield any results, chop off another digit. Repeat until you get some sort of output. The result will be a possible list of functions which caused the panic. This is a less than exact mechanism for - tracking down the point of failure, but it's better than + tracking down the point of failure, but it is better than nothing. @@ -12033,11 +12034,11 @@ Cc: current@FreeBSD.org FreeBSD crash dumps are usually the same size as the physical RAM size of your machine. That is, if you have 64MB of RAM, you will get a 64MB crash dump. Therefore you - must make sure there's enough space in + must make sure there is enough space in /var/crash to hold the dump. Alternatively, you run &man.savecore.8; manually and have it recover the crash dump to another - directory where you have more room. It's possible to limit + directory where you have more room. It is possible to limit the size of the crash dump by using options MAXMEM=(foo) to set the amount of memory the kernel will use to something a little more sensible. For @@ -12063,13 +12064,13 @@ Cc: current@FreeBSD.org the contents of various variables or structures in order to examine the system state at the time of the crash. - Now, if you're really insane and have a second computer, + Now, if you are really insane and have a second computer, you can also configure &man.gdb.1; to do remote debugging such that you can use &man.gdb.1; on one system to debug the kernel on another system, including setting breakpoints, single-stepping through the kernel code, - just like you can do with a normal user-mode program. I haven't - played with this yet as I don't often have the chance to set up + just like you can do with a normal user-mode program. I have not + played with this yet as I do not often have the chance to set up two machines side by side for debugging purposes. [Bill adds: "I forgot to mention one thing: if @@ -12117,12 +12118,12 @@ Cc: current@FreeBSD.org aspects to this. First, you need to tell the kernel to reserve a larger portion of the address space for itself. Second, since the kernel is loaded at the top of the address space, you need - to lower the load address so it doesn't bump its head against + to lower the load address so it does not bump its head against the ceiling. The first goal is achieved by increasing the value of NKPDE in - src/sys/i386/include/pmap.h. Here's what + src/sys/i386/include/pmap.h. Here is what it looks like for a 1 GB address space: #ifndef NKPDE @@ -12170,7 +12171,7 @@ SECTIONS multiple of four megabytes. [&a.dg; adds: I think the kernel address space - needs to be a power of two, but I'm not certain about that. The + needs to be a power of two, but I am not certain about that. The old(er) boot code used to monkey with the high order address bits and I think expected at least 256MB granularity.] @@ -12250,7 +12251,7 @@ SECTIONS - And to any others we've forgotten, apologies and heartfelt + And to any others we have forgotten, apologies and heartfelt thanks!