From ef411ca3f46f2bb32ceb39975a70a4f98421b25f Mon Sep 17 00:00:00 2001 From: Nik Clayton Date: Tue, 11 Aug 1998 08:28:42 +0000 Subject: [PATCH] ... -> ... --- en/handbook/README | 2 + en/handbook/handbook.sgml | 414 +++++++++------------- en_US.ISO8859-1/books/handbook/book.sgml | 414 +++++++++------------- en_US.ISO_8859-1/books/handbook/book.sgml | 414 +++++++++------------- 4 files changed, 527 insertions(+), 717 deletions(-) diff --git a/en/handbook/README b/en/handbook/README index c0810586d3..5f3c9c9738 100644 --- a/en/handbook/README +++ b/en/handbook/README @@ -313,3 +313,5 @@ for example, file looking for ">... -> ... + diff --git a/en/handbook/handbook.sgml b/en/handbook/handbook.sgml index 7e0b598780..e36c246d94 100644 --- a/en/handbook/handbook.sgml +++ b/en/handbook/handbook.sgml @@ -1045,30 +1045,26 @@ - SoundBlaster SCSI and ProAudio Spectrum SCSI (cd) + SoundBlaster SCSI and ProAudio Spectrum SCSI (cd) - Mitsumi (all models) proprietary interface (mcd) + Mitsumi (all models) proprietary interface (mcd) Matsushita/Panasonic (Creative) CR-562/CR-563 - proprietary interface (matcd) + proprietary interface (matcd) - Sony proprietary interface (scd) + Sony proprietary interface (scd) ATAPI IDE interface (experimental and should be - considered ALPHA quality!) (wcd) + considered ALPHA quality!) (wcd) @@ -3287,7 +3283,7 @@ The general format of a configuration file is quite simple. Each line contains a keyword and one or more arguments. For simplicity, most lines only contain one argument. Anything following a - # is considered a comment and ignored. + # is considered a comment and ignored. The following sections describe each keyword, generally in the order they are listed in GENERIC, although some related keywords have been grouped together in a single section @@ -3307,7 +3303,7 @@ this caused a creeping optionism, with nobody really knowing which option has been referenced in what files. - In the new scheme, every #ifdef + In the new scheme, every #ifdef that is intended to be dependent upon an option gets this option out of an opt_foo.h declaration file created in the compile directory by config. The list of valid options for @@ -3327,8 +3323,7 @@ machine "i386" - The first keyword is machine, which, since FreeBSD only + The first keyword is machine, which, since FreeBSD only runs on Intel 386 and compatible chips, is i386. @@ -3343,7 +3338,7 @@ cpu "cpu_type" - The next keyword is cpu, + The next keyword is cpu, which includes support for each CPU supported by FreeBSD. The possible values of cpu_type @@ -3366,8 +3361,7 @@ I686_CPU - and multiple instances of the cpu line may be present with + and multiple instances of the cpu line may be present with different values of cpu_type as are present in the GENERIC kernel. @@ -3381,25 +3375,23 @@ ident machine_name - Next, we have ident, + Next, we have ident, which is the identification of the kernel. You should change this from GENERIC to whatever you named your kernel, in this example, MYKERNEL. The value you put in - ident will print when you + ident will print when you boot up the kernel, so it is useful to give a kernel a different name if you want to keep it separate from your usual kernel (if you want to build an experimental kernel, - for example). Note that, as with machine and - cpu, enclose your kernel's name in quotation + for example). Note that, as with machine and + cpu, enclose your kernel's name in quotation marks if it contains any numbers. Since this name is passed to the C compiler as a switch, do not use names like , or something that could be - confused with another machine or CPU name, like vax. + confused with another machine or CPU name, like vax. @@ -3410,21 +3402,20 @@ system tables. This number is supposed to be roughly equal to the number of simultaneous users you expect to have on your machine. However, under normal - circumstances, you will want to set maxusers to at least four, + circumstances, you will want to set maxusers to at least four, especially if you are using the X Window System or compiling software. The reason is that the most important - table set by maxusers is the + table set by maxusers is the maximum number of processes, which is set to 20 + 16 * maxusers, so if you set - maxusers to one, then you + maxusers to one, then you can only have 36 simultaneous processes, including the 18 or so that the system starts up at boot time, and the 15 or so you will probably create when you start the X Window System. Even a simple task like reading a man page will start up nine processes to filter, decompress, and view it. Setting - maxusers to 4 will allow you + maxusers to 4 will allow you to have up to 84 simultaneous processes, which should be enough for anyone. If, however, you see the dreaded proc table full error when trying to start another @@ -3433,7 +3424,7 @@ you can always increase this number and rebuild. - maxuser does + maxuser does not limit the number of users which can log into your machine. It simply sets various table sizes to reasonable values considering the maximum @@ -3461,8 +3452,8 @@ render numerous system utilities inoperative. The second part of the line specifies the disk and partition where the root filesystem and kernel can be found. Typically - this will be wd0 for systems - with non-SCSI drives, or sd0 + this will be wd0 for systems + with non-SCSI drives, or sd0 for systems with SCSI drives. @@ -3730,10 +3721,9 @@ controller fdc0 - Floppy drive controller: fd0 is the A: floppy drive, and - fd1 is the B: drive. - ft0 is a QIC-80 tape drive + Floppy drive controller: fd0 is the A: floppy drive, and + fd1 is the B: drive. + ft0 is a QIC-80 tape drive attached to the floppy controller. Comment out any lines corresponding to devices you do not have. @@ -3748,10 +3738,8 @@ controller wdc0 - This is the primary IDE controller. wd0 and wd1 are the master and slave hard - drive, respectively. wdc1 is + This is the primary IDE controller. wd0 and wd1 are the master and slave hard + drive, respectively. wdc1 is a secondary IDE controller where you might have a third or fourth hard drive, or an IDE CD-ROM. Comment out the lines which do not apply (if you have a SCSI hard drive, @@ -3765,11 +3753,11 @@ This device provides IDE CD-ROM support. Be sure to - leave wdc0 uncommented, and - wdc1 if you have more than + leave wdc0 uncommented, and + wdc1 if you have more than one IDE controller and your CD-ROM is on the second one card. To use this, you must also include the line - options ATAPI. + options ATAPI. @@ -3777,7 +3765,7 @@ vector npxintr - npx0 is the interface to + npx0 is the interface to the floating point math unit in FreeBSD, either the hardware co-processor or the software math emulator. It is NOT optional. @@ -3983,7 +3971,7 @@ Support for SCSI CD-ROM drives. - Note that the number 0 + Note that the number 0 in the above entries is slightly misleading: all these devices are automatically configured as they are found, regardless of how many of them are hooked up to the SCSI @@ -4012,12 +4000,11 @@ device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr - sc0 is the default + sc0 is the default console driver, which resembles an SCO console. Since most full-screen programs access the console through a terminal database library like termcap, it - should not matter much whether you use this or vt0, the VT220 compatible console + should not matter much whether you use this or vt0, the VT220 compatible console driver. When you log in, set your TERM variable to scoansi if full-screen programs have trouble running under this console. @@ -4030,8 +4017,7 @@ This is a VT220-compatible console driver, backwards compatible to VT100/102. It works well on some laptops - which have hardware incompatibilities with sc0. Also, set your TERM variable + which have hardware incompatibilities with sc0. Also, set your TERM variable to vt100 or vt220 when you log in. This driver might also prove useful when connecting to a large number of different machines over the network, where the @@ -4045,19 +4031,17 @@ options "PCVT_FREEBSD=210" - Required with the vt0 console driver. + Required with the vt0 console driver. options XSERVER - Only applicable with the vt0 console driver. This + Only applicable with the vt0 console driver. This includes code required to run the XFree86 X Window Server - under the vt0 + under the vt0 console driver. @@ -4328,7 +4312,7 @@ pseudo-device loop - loop is the generic + loop is the generic loopback device for TCP/IP. If you telnet or FTP to localhost (a.k.a. 127.0.0.1) it will come back at you through this pseudo-device. Mandatory. @@ -4338,7 +4322,7 @@ pseudo-device ether - ether is only needed if + ether is only needed if you have an Ethernet card and includes generic Ethernet protocol code. @@ -4348,12 +4332,12 @@ number - sl is for SLIP (Serial + sl is for SLIP (Serial Line Internet Protocol) support. This has been almost entirely supplanted by PPP, which is easier to set up, better suited for modem-to-modem connections, as well as more powerful. The number after - sl specifies how many + sl specifies how many simultaneous SLIP sessions to support. This handbook has more information on setting up a SLIP number - ppp is for kernel-mode + ppp is for kernel-mode PPP (Point-to-Point Protocol) support for dial-up Internet connections. There is also version of PPP implemented as a user application that uses the - section of the handbook. As with the sl device, + section of the handbook. As with the sl device, number specifies how many simultaneous PPP connections to support. @@ -4385,11 +4368,10 @@ number - tun is used by the + tun is used by the user-mode PPP software. This program is easy to set up and very fast. It also has special features such as automatic - dial-on-demand. The number after tun specifies the number of + dial-on-demand. The number after tun specifies the number of simultaneous PPP sessions to support. See the section of the handbook for more @@ -4433,8 +4415,7 @@ controller snd0 Generic sound driver code. Required for all of the - following sound cards except pca. + following sound cards except pca. @@ -4454,9 +4435,9 @@ If your SoundBlaster is on a different IRQ (such as - 5), change irq 7 to, for - example, irq 5 and remove - the conflicts keyword. + 5), change irq 7 to, for + example, irq 5 and remove + the conflicts keyword. Also, you must add the line: options "SBC_IRQ=5" @@ -4470,8 +4451,8 @@ If your SB16 is on a different 16-bit DMA channel - (such as 6 or 7), change the drq - 5 keyword appropriately, and then add the + (such as 6 or 7), change the drq + 5 keyword appropriately, and then add the line: options "SB16_DMA=6" @@ -4565,7 +4546,7 @@ pseudo-device gzip - gzip allows you to run + gzip allows you to run FreeBSD programs that have been compressed with gzip. The programs in /stand are compressed so it is a good idea to have this option in your kernel. @@ -4575,7 +4556,7 @@ pseudo-device log - log is used for logging + log is used for logging of kernel error messages. Mandatory. @@ -4585,13 +4566,13 @@ id="kernelconfig-ptys"> - pty is a + pty is a pseudo-terminal or simulated login port. It is used by incoming telnet and rlogin sessions, xterm, and some other applications such as emacs. The number indicates the number of - ptys to create. If you need + ptys to create. If you need more than GENERIC default of 16 simultaneous xterm windows and/or remote logins, be sure to increase this number accordingly, up to a maximum of 64. @@ -5247,22 +5228,22 @@ - The first line (permit - internet) allows users whose IP source address + The first line (permit + internet) allows users whose IP source address (which is vulnerable to spoofing) matches the specified value and mask, to use UNIX passwords. This should not be considered a security mechanism, but rather, a means to remind authorized users that they are using an insecure network and need to use S/Key for authentication. - The second line (permit user) + The second line (permit user) allows the specified user to use UNIX passwords at any time. Generally speaking, this should only be used for people who are either unable to use the key program, like those with dumb terminals, or those who are uneducable. - The third line (permit port) + The third line (permit port) allows all users logging in on the specified terminal line to use UNIX passwords; this would be used for dial-ups. @@ -6442,8 +6423,8 @@ to write a list of the current rules out to a file, and then - use a text editor to prepend `ipfw - ' before all the lines. This will allow the script to + use a text editor to prepend `ipfw + ' before all the lines. This will allow the script to be fed into /bin/sh and reload the rules into the kernel. Perhaps not the most efficient way, but it works. @@ -7019,11 +7000,10 @@ port where port is the device entry for the - port you want to make. Use lpt0 for the first parallel port, - lpt1 for the second, and - so on; use ttyd0 for the - first serial port, ttyd1 + port you want to make. Use lpt0 for the first parallel port, + lpt1 for the second, and + so on; use ttyd0 for the + first serial port, ttyd1 for the second, and so on. @@ -7088,16 +7068,14 @@ Edit your kernel configuration file. Look for or - add an lpt0 entry. If you - are setting up the second parallel port, use lpt1 instead. Use lpt2 for the third port, and so + add an lpt0 entry. If you + are setting up the second parallel port, use lpt1 instead. Use lpt2 for the third port, and so on. If you want interrupt-driven mode, add the - irq specifier: + irq specifier: device lpt0 at isa? port? tty irq N @@ -7110,7 +7088,7 @@ If you want polled mode, do not add the - irq specifier: + irq specifier: device lpt0 at isa? port? tty vector lptintr @@ -7297,16 +7275,12 @@ printer:dv=/dev/port:br#bps-rate:pa=parity where port is the device entry for the - serial port (ttyd0, - ttyd1, etc.), ttyd0, + ttyd1, etc.), bps-rate is the bits-per-second rate at which the printer communicates, and parity is the parity required by - the printer (either even, odd, none, or zero). + the printer (either even, odd, none, or zero). Here is a sample entry for a printer connected via @@ -7499,10 +7473,10 @@ At least one of the printers specified in the /etc/printcap should have the alias - lp. This is the default + lp. This is the default printer's name. If users do not have the PRINTER environment variable nor specify a printer name on the command line of any - of the LPD commands, then lp + of the LPD commands, then lp will be the default printer they get to use. Also, it is common practice to make the last alias for a @@ -7778,7 +7752,7 @@ When LPD opens the device specified by the lp capability, it reads the flag bits in - the sgttyb structure; it clears + the sgttyb structure; it clears any bits in the fc capability, then sets bits in the fs capability, then applies the resultant setting. It does the @@ -8354,7 +8328,7 @@ the lpr command line are treated as part of a single job. It is the currently - active job (note the word active + active job (note the word active under the Rank column), which means the printer should be currently printing that job. The second job consists of data passed as the standard input to the @@ -8851,7 +8825,7 @@ URL="http://www.freebsd.org/cgi/man.cgi?lpc">lpc commands. Most of the commands takes a printer-name argument to tell on which - printer to operate. You can use all + printer to operate. You can use all for the printer-name to mean all printers listed in /etc/printcap. @@ -8975,8 +8949,7 @@ with the listed job numbers or the jobs belonging to username at the top of the queue. - For this command, you cannot use all as the all as the printer-name. @@ -9352,7 +9325,7 @@ text jobs to the printer, then you are urged to augment your printer setup. To do so, we have the text filter detect if the arriving job is plain text or PostScript. All PostScript jobs - must start with %! (for other + must start with %! (for other printer languages, see your printer documentation). If those are the first two characters in the job, we have PostScript, and can pass the rest of the job directly. If those are not the first @@ -9929,7 +9902,7 @@ In the , we turned off header pages by - specifying sh (meaning suppress + specifying sh (meaning suppress header) in the /etc/printcap file. To enable header pages for a printer, just remove the sh capability. @@ -10012,15 +9985,14 @@ /etc/printcap). If you prefer, LPD can make a short - header; specify sb + header; specify sb (short banner) in the /etc/printcap file. The header page will look like this: rose:kelly Job: outline Date: Sun Sep 17 11:07:51 1995 Also by default, LPD prints the header page - first, then the job. To reverse that, specify hl (header last) in + first, then the job. To reverse that, specify hl (header last) in /etc/printcap. @@ -13062,7 +13034,7 @@ Here is a config snippet from a machine with a Digi International PC/8 with 16550. It has 8 modems connected to these 8 lines, and they work just great. Do not forget to add - options COM_MULTIPORT or it will + options COM_MULTIPORT or it will not work very well! @@ -13301,10 +13273,7 @@ If appropriate, add entries to - by duplicating serial device (ttyd) entries and using ttyc in place of ttyd. For example: + by duplicating serial device (ttyd) entries and using ttyc in place of ttyd. For example: ttyc0 "/usr/libexec/getty std.38400" @@ -14468,8 +14437,7 @@ remap=tt>ahb, ahc, ncr and amd will automatically obtain the correct parameters from the host adapters themselves at boot - time; thus, you just need to write, for instance, "controller ahc0". + time; thus, you just need to write, for instance, "controller ahc0". An example loosely based on the FreeBSD 2.2.5-Release @@ -16702,8 +16670,7 @@ For each ttyv? entry in /etc/ttys change terminal type from - cons25 to cons25r, i.e. each entry should looks + cons25 to cons25r, i.e. each entry should looks like ttyv0 "/usr/libexec/getty Pc" cons25r on secure @@ -16928,10 +16895,9 @@ KOI8-R fonts, but this ones scaled better. - Check find "Files" section + Check find "Files" section in your /etc/XF86Config, following - lines must be before any other FontPath entries: + lines must be before any other FontPath entries: FontPath "/usr/X11R6/lib/X11/fonts/cyrillic/misc" FontPath "/usr/X11R6/lib/X11/fonts/cyrillic/75dpi" FontPath @@ -16945,9 +16911,9 @@ To activate Russian keyboard add XkbKeymap "xfree86(ru)" line into - "Keyboard" section in your + "Keyboard" section in your /etc/XF86Config, also make sure that - XkbDisable is turned off + XkbDisable is turned off (commented out) there. @@ -17466,10 +17432,8 @@ The file /etc/gettytab contains lots of entries for terminal lines both old and new. In almost all - cases, the entries that start with the text std will work for hardwired terminals. - These entries ignore parity. There is a std entry for each bps rate from 110 to + cases, the entries that start with the text std will work for hardwired terminals. + These entries ignore parity. There is a std entry for each bps rate from 110 to 115200. Of course, you can add your own entries to this file. The manual page gettytab5 provides more information. @@ -17497,8 +17461,8 @@ The third field in the /etc/ttys file lists the default terminal type for the port. For dialup ports, - you typically put unknown or - dialup in this field because users + you typically put unknown or + dialup in this field because users may dial up with practically any kind of terminal or software. For hardwired terminals, the terminal type does not change, so you can put a real terminal type in this field. @@ -17535,18 +17499,15 @@ Enabling the Port The next field in /etc/ttys, the fourth - field, tells whether to enable the port. Putting on here will have the init process start the program in the + field, tells whether to enable the port. Putting on here will have the init process start the program in the second field, getty, which will - prompt for a login. If you put off in the fourth field, there will be no + prompt for a login. If you put off in the fourth field, there will be no getty, and hence no logins on the port. - So, naturally, you want an on + So, naturally, you want an on in this field. Here again is the /etc/ttys - file. We have turned each port on. + file. We have turned each port on. ttyd1 "/usr/libexec/getty std.38400" wy50 on secure ttyd5 "/usr/libexec/getty std.19200" vt100 @@ -17561,7 +17522,7 @@ Specifying Secure Ports We have arrived at the last field (well, almost: there is an - optional window specifier, but we + optional window specifier, but we will ignore that). The last field tells whether the port is secure. @@ -17675,8 +17636,8 @@ 22189 d1 Is+ 0:00.03 /usr/libexec/getty std.38400 ttyd1 shows that a getty is running on the second - serial port ttyd1 and is - using the std.38400 entry in + serial port ttyd1 and is + using the std.38400 entry in /etc/gettytab. If no getty process is @@ -18005,9 +17966,8 @@ watch for messages while the kernel is booting, or use the /sbin/dmesg command to replay the kernel's boot messages. In particular, look for messages that - start with the characters sio. Hint: - to view just the messages that have the word sio, use the command: + start with the characters sio. Hint: + to view just the messages that have the word sio, use the command: @@ -18067,7 +18027,7 @@ changed between versions. - port "IO_COM1" is a + port "IO_COM1" is a substitution for port 0x3f8, IO_COM2 is 0x2f8, IO_COM3 is 0x3e8, and @@ -18237,8 +18197,7 @@ You will need to setup an entry in /etc/gettytab to give getty information about the speeds you wish to use for your modem. If you have a 2400 bps modem, you - can probably use the existing D2400 entry. This entry already exists + can probably use the existing D2400 entry. This entry already exists in the FreeBSD 1.1.5.1 gettytab file, so you do not need to add it unless it is missing under your version of FreeBSD: @@ -18272,8 +18231,7 @@ On FreeBSD 1.1.5 and later, this will result in 8-bit, no - parity connections. Under FreeBSD 1.1, add :np: parameters to the :np: parameters to the std.xxx entries at the top of the file for 8 bits, no parity; otherwise, the default is 7 bits, even parity. @@ -18342,29 +18300,27 @@ The first item in the above line is the device special file - for this entry - ttyd0 means + for this entry - ttyd0 means /dev/ttyd0 is the file that this getty will be watching. The second item, "/usr/libexec/getty xxx" (xxx will be replaced by the initial gettytab capability) is the process init will run on the - device. The third item, dialup, - is the default terminal type. The fourth parameter, on, indicates to dialup, + is the default terminal type. The fourth parameter, on, indicates to init that the line is operational. There - can be a fifth parameter, secure, + can be a fifth parameter, secure, but it should only be used for terminals which are physically secure (such as the system console). - The default terminal type (dialup in the example above) may depend on - local preferences. dialup is the + The default terminal type (dialup in the example above) may depend on + local preferences. dialup is the traditional default terminal type on dialup lines so that users may customize their login scripts to notice when the terminal is - dialup and automatically adjust + dialup and automatically adjust their terminal type. However, the author finds it easier at his - site to specify vt102 as the + site to specify vt102 as the default terminal type, since the users just use VT102 emulation on their remote systems. @@ -18402,7 +18358,7 @@ If your modem is locked at a different data rate, substitute the appropriate name for the std.speed - entry for std.19200 from + entry for std.19200 from /etc/gettytab for your modem's data rate. @@ -18417,8 +18373,7 @@ /etc/gettytab. For example, if you added the above suggested entry for a matching-speed modem that starts at 19.2 Kbps (the gettytab entry containing the V19200 starting point), your gettytab entry containing the V19200 starting point), your ttys entry might look like this: @@ -18872,9 +18827,9 @@ /usr/src/usr.bin/tip/tip Obviously you need the source distribution to do this. - Edit the line #define HAYES - 0 to #define HAYES - 1. Then make and + Edit the line #define HAYES + 0 to #define HAYES + 1. Then make and make install. Everything works nicely after that. @@ -18902,7 +18857,7 @@ Or use cu as root with the following command: cu -lline -sspeed with line being the serial port (e.g./dev/cuaa0) and speed being - the speed (e.g.57600). When you are + the speed (e.g.57600). When you are done entering the AT commands hit ~. to exit. @@ -18946,10 +18901,10 @@ Do I have to type in the bps rate every time I do that? - Put in an entry for tip1200 or - cu1200, but go ahead and use + Put in an entry for tip1200 or + cu1200, but go ahead and use whatever bps rate is appropriate with the br capability. tip thinks a good default is 1200 bps which - is why it looks for a tip1200 + is why it looks for a tip1200 entry. You do not have to use 1200 bps, though. @@ -19631,7 +19586,7 @@ circumstances, but the above example will almost always work. If it fails, you may be able to defeat some broken ppp implementations by supplying an additional - 0.0.0.0 argument: + 0.0.0.0 argument: @@ -19881,10 +19836,10 @@ Note the indenting is important. - The default: section is + The default: section is loaded for each session. For each dialup line enabled in /etc/ttys create an entry similar to the - one for ttyd0: above. Each line + one for ttyd0: above. Each line should get a unique IP from your pool of ip address for dynamic users. @@ -21034,11 +20989,9 @@ which sliplogin attached itself (slip interface 0, in the above example, which was the first parameter in the list given to slip.login) - to set the local IP address (dc-slip), remote IP address (sl-helmer), network mask for the SLIP + to set the local IP address (dc-slip), remote IP address (sl-helmer), network mask for the SLIP interface (0xfffffc00), and any additional - flags (autocomp). If something + flags (autocomp). If something goes wrong, sliplogin usually logs good informational messages via the daemon syslog facility, which usually goes into /var/log/messages @@ -21080,8 +21033,7 @@ The sl0 and sl1 interfaces shown in netstat -i's output indicate that there are two SLIP interfaces built into the kernel. (The asterisks after - the sl0 and sl1 indicate that the interfaces are + the sl0 and sl1 indicate that the interfaces are down.) However, FreeBSD's default kernels do not come configured to @@ -21196,22 +21148,22 @@ - normal - no header + normal - no header compression - compress - compress + compress - compress headers - autocomp - compress + autocomp - compress headers if the remote end allows it - noicmp - disable ICMP + noicmp - disable ICMP packets (so any ping packets will be dropped instead of using up your bandwidth) @@ -21470,7 +21422,7 @@ certainly turn off the tracing options if gated works OK for you. You will need to change the xxx.xxx.yy's into the network address of your own SLIP subnet (be sure to change the - net mask in the proto direct + net mask in the proto direct clause as well). When you get gated built and @@ -21563,8 +21515,7 @@ cover in the next section) and the localhost route. The interface (Netif column) - that it specifies to use for localhost is localhost is lo0, also known as the loopback device. This says to keep all traffic for this destination internal, rather than sending it out over the LAN, since it will only end up back @@ -21575,7 +21526,7 @@ (test0 in the example) on the local ethernet and add a route for that host, directly to it over the ethernet interface, ed0. There is - also a timeout (Expire column) + also a timeout (Expire column) associated with this type of route, which is used if we fail to hear from the host in a specific amount of time. In this case the route will be automatically deleted. These hosts are identified @@ -21587,8 +21538,7 @@ (10.20.30.255 is the broadcast address for the subnet 10.20.30, and foobar.com is the domain name - associated with that subnet). The designation link#1 refers to the first ethernet card in + associated with that subnet). The designation link#1 refers to the first ethernet card in the machine. You will notice no additional interface is specified for those. @@ -21598,29 +21548,26 @@ only routes which are statically defined (ie. entered explicitly) will exist. - The host1 line refers to our + The host1 line refers to our host, which it knows by ethernet address. Since we are the sending host, FreeBSD knows to use the loopback interface (lo0) rather than sending it out over the ethernet interface. - The two host2 lines are an + The two host2 lines are an example of what happens when we use an ifconfig alias (see the section of ethernet for reasons why we would do this). The - => symbol after the lo0 interface says that not only are we + => symbol after the lo0 interface says that not only are we using the loopback (since this is address also refers to the local host), but specifically it is an alias. Such routes only show up on the host that supports the alias; all other hosts on the local - network will simply have a link#1 + network will simply have a link#1 line for such. - The final line (destination subnet 224) deals with MultiCasting, which will be + The final line (destination subnet 224) deals with MultiCasting, which will be covered in a another section. - The other column that we should talk about are the Flags. Each route has different attributes + The other column that we should talk about are the Flags. Each route has different attributes that are described in the column. Below is a short table of some of these flags and their meanings: @@ -21702,8 +21649,7 @@ If all known paths fail, the system has one last option: the default route. This route is a special type of gateway route (usually the only one present in the - system), and is always marked with a c in the flags field. For hosts on a + system), and is always marked with a c in the flags field. For hosts on a local area network, this gateway is set to whatever machine has a direct connection to the outside world (whether via PPP link, or your hardware device attached to a dedicated data line). @@ -22875,12 +22821,12 @@ As a good workaround, you can place the line - search foo.bar.edu - bar.edu + search foo.bar.edu + bar.edu instead of the previous - domain foo.bar.edu + domain foo.bar.edu into your /etc/resolv.conf. However, make sure that the search order does not go beyond the boundary @@ -23480,8 +23426,8 @@ future, this will be the only place where announcements concerning the operations of the CTM system will be posted. Send an email to &a.majordomo; with a single - line of subscribe - ctm-announce to get added to the list. + line of subscribe + ctm-announce to get added to the list. @@ -24392,10 +24338,7 @@ collections are reflected by the use of indentation in the list below. - The most commonly used collections are src-all, cvs-crypto, and ports-all. The other collections are used + The most commonly used collections are src-all, cvs-crypto, and ports-all. The other collections are used only by small groups of people for specialized purposes, and some mirror sites may not carry all of them. @@ -25087,8 +25030,8 @@ Contributed by &a.nik;. Once you have synchronised your local source tree against a - particular version of FreeBSD (stable, - current and so on) you must then use + particular version of FreeBSD (stable, + current and so on) you must then use the source tree to rebuild the system. Currently, the best source of information on how to do that is a @@ -25732,7 +25675,7 @@ After filing a report, you should receive confirmation along with a tracking number. Keep this tracking number so that you can update us with details about the problem by sending mail to bug-followup@FreeBSD.ORG. Use the number as the message subject, e.g. "Re: kern/3377". Additional information for any bug report should be submitted this way. + URL="mailto:bug-followup@FreeBSD.ORG">bug-followup@FreeBSD.ORG. Use the number as the message subject, e.g. "Re: kern/3377". Additional information for any bug report should be submitted this way. If you do not receive confirmation in a timely fashion (3 days to a week, depending on your email connection) or are, for some @@ -25873,8 +25816,7 @@ To place a BSD-style copyright on your work, include the following text at the very beginning of every source code file you - wish to protect, replacing the text between the %% with the appropriate information. + wish to protect, replacing the text between the %% with the appropriate information. Copyright (c) %%proper_years_here%% %%your_name_here%%, %%your_state%% %%your_zip%%. All rights reserved. @@ -25940,7 +25882,7 @@ Only a fraction of the overridable variables - (${..}) are mentioned in + (${..}) are mentioned in this document. Most (if not all) are documented at the start of bsd.port.mk. This file uses a non-standard tab setting. Emacs and @@ -26034,7 +25976,7 @@ __FreeBSD__ is defined in all versions of FreeBSD. Use it if the change you are making ONLY affects FreeBSD. Porting gotchas like the use of - sys_errlist[] vs + sys_errlist[] vs strerror() are Berkeleyisms, not FreeBSD changes. @@ -26042,8 +25984,8 @@ In FreeBSD 2.x, __FreeBSD__ is - defined to be 2. In earlier - versions, it is 1. Later + defined to be 2. In earlier + versions, it is 1. Later versions will bump it to match their major version number. @@ -26055,8 +25997,8 @@ described above. If there actually is a FreeBSD specific change (such as special shared library options when using ld) then it is OK to use - __FreeBSD__ and #if - __FreeBSD__ > 1 to detect a FreeBSD 2.x + __FreeBSD__ and #if + __FreeBSD__ > 1 to detect a FreeBSD 2.x and later system. If you need more granularity in detecting FreeBSD systems since 2.0-RELEASE you can use the following: @@ -26156,7 +26098,7 @@ See if you can figure it out. Do not worry about the - contents of the $Id$ + contents of the $Id$ line, it will be filled in automatically by CVS when the port is imported to our main ports tree. You can find a more detailed example in the - If the port uses XmClientLibs in its Imakefile, + If the port uses XmClientLibs in its Imakefile, change it to ${MOTIFLIB} ${XTOOLLIB} ${XLIB}. @@ -30611,7 +30552,7 @@ People familiar with the C language will immediately recognize that everything could be counted as a config option where there - is at least a single #ifdef + is at least a single #ifdef referencing it... However, it's unlikely that many people would put @@ -30634,8 +30575,7 @@ The old-style option mechanism still has one advantage for local options or maybe experimental options that have a short anticipated - lifetime: since it is easy to add a new #ifdef to the kernel source, this has already + lifetime: since it is easy to add a new #ifdef to the kernel source, this has already made it a kernel config option. In this case, the administrator using such an option is responsible himself for knowing about its implications (and maybe manually forcing the recompilation of parts @@ -30688,8 +30628,7 @@ #include "opt_foo.h" - on top, before all the #include <xxx.h> stuff. This sequence + on top, before all the #include <xxx.h> stuff. This sequence is most important as the options could override defaults from the regular include files, if the defaults are of the form @@ -30728,8 +30667,8 @@ on a crash dump. They assume that you have enough swap space for a crash dump. If you have multiple swap partitions and the first one is too small to hold the dump, you can configure your kernel to use - an alternate dump device (in the config - kernel line), or you can specify an alternate using the + an alternate dump device (in the config + kernel line), or you can specify an alternate using the dumpon8 command. Dumps to non-swap devices, tapes for example, are currently not supported. Config your kernel using config -g. See However, it obviously points to garbage, so we have found our error! (For those unfamiliar with that particular - piece of code: tp->t_line + piece of code: tp->t_line refers to the line discipline of the console device here, which must be a rather small integer number.) @@ -30997,8 +30936,8 @@ Ctrl-Alt-ESC. For syscons, this can be remapped; some of the distributed maps do this, so watch out. There is an option available for serial consoles that allows the use of a serial line BREAK on - the console line to enter DDB (options - BREAK_TO_DEBUGGER in the kernel config file). It is + the console line to enter DDB (options + BREAK_TO_DEBUGGER in the kernel config file). It is not the default since there are a lot of crappy serial adapters around that gratuitously generate a BREAK condition, for example when pulling the cable. @@ -34265,19 +34204,16 @@ The following CVSup site is especially designed for users. Unlike the other CVSup mirrors, - it is kept up-to-date by CTM. That means if you CVSup cvs-all with release=cvs + it is kept up-to-date by CTM. That means if you CVSup cvs-all with release=cvs from this site, you get a version of the repository (including the inevitable .ctm_status file) which is - suitable for being updated using the CTM cvs-cur deltas. This allows users who track - the entire cvs-all tree to go from + suitable for being updated using the CTM cvs-cur deltas. This allows users who track + the entire cvs-all tree to go from CVSup to CTM without having to rebuild their repository from scratch using a fresh CTM base delta. - This special feature only works for the cvs-all distribution with + This special feature only works for the cvs-all distribution with cvs as the release tag. CVSupping any other distribution and/or release will get you the specified distribution, but it will not be suitable for CTM updating. diff --git a/en_US.ISO8859-1/books/handbook/book.sgml b/en_US.ISO8859-1/books/handbook/book.sgml index 7e0b598780..e36c246d94 100644 --- a/en_US.ISO8859-1/books/handbook/book.sgml +++ b/en_US.ISO8859-1/books/handbook/book.sgml @@ -1045,30 +1045,26 @@ - SoundBlaster SCSI and ProAudio Spectrum SCSI (cd) + SoundBlaster SCSI and ProAudio Spectrum SCSI (cd) - Mitsumi (all models) proprietary interface (mcd) + Mitsumi (all models) proprietary interface (mcd) Matsushita/Panasonic (Creative) CR-562/CR-563 - proprietary interface (matcd) + proprietary interface (matcd) - Sony proprietary interface (scd) + Sony proprietary interface (scd) ATAPI IDE interface (experimental and should be - considered ALPHA quality!) (wcd) + considered ALPHA quality!) (wcd) @@ -3287,7 +3283,7 @@ The general format of a configuration file is quite simple. Each line contains a keyword and one or more arguments. For simplicity, most lines only contain one argument. Anything following a - # is considered a comment and ignored. + # is considered a comment and ignored. The following sections describe each keyword, generally in the order they are listed in GENERIC, although some related keywords have been grouped together in a single section @@ -3307,7 +3303,7 @@ this caused a creeping optionism, with nobody really knowing which option has been referenced in what files. - In the new scheme, every #ifdef + In the new scheme, every #ifdef that is intended to be dependent upon an option gets this option out of an opt_foo.h declaration file created in the compile directory by config. The list of valid options for @@ -3327,8 +3323,7 @@ machine "i386" - The first keyword is machine, which, since FreeBSD only + The first keyword is machine, which, since FreeBSD only runs on Intel 386 and compatible chips, is i386. @@ -3343,7 +3338,7 @@ cpu "cpu_type" - The next keyword is cpu, + The next keyword is cpu, which includes support for each CPU supported by FreeBSD. The possible values of cpu_type @@ -3366,8 +3361,7 @@ I686_CPU - and multiple instances of the cpu line may be present with + and multiple instances of the cpu line may be present with different values of cpu_type as are present in the GENERIC kernel. @@ -3381,25 +3375,23 @@ ident machine_name - Next, we have ident, + Next, we have ident, which is the identification of the kernel. You should change this from GENERIC to whatever you named your kernel, in this example, MYKERNEL. The value you put in - ident will print when you + ident will print when you boot up the kernel, so it is useful to give a kernel a different name if you want to keep it separate from your usual kernel (if you want to build an experimental kernel, - for example). Note that, as with machine and - cpu, enclose your kernel's name in quotation + for example). Note that, as with machine and + cpu, enclose your kernel's name in quotation marks if it contains any numbers. Since this name is passed to the C compiler as a switch, do not use names like , or something that could be - confused with another machine or CPU name, like vax. + confused with another machine or CPU name, like vax. @@ -3410,21 +3402,20 @@ system tables. This number is supposed to be roughly equal to the number of simultaneous users you expect to have on your machine. However, under normal - circumstances, you will want to set maxusers to at least four, + circumstances, you will want to set maxusers to at least four, especially if you are using the X Window System or compiling software. The reason is that the most important - table set by maxusers is the + table set by maxusers is the maximum number of processes, which is set to 20 + 16 * maxusers, so if you set - maxusers to one, then you + maxusers to one, then you can only have 36 simultaneous processes, including the 18 or so that the system starts up at boot time, and the 15 or so you will probably create when you start the X Window System. Even a simple task like reading a man page will start up nine processes to filter, decompress, and view it. Setting - maxusers to 4 will allow you + maxusers to 4 will allow you to have up to 84 simultaneous processes, which should be enough for anyone. If, however, you see the dreaded proc table full error when trying to start another @@ -3433,7 +3424,7 @@ you can always increase this number and rebuild. - maxuser does + maxuser does not limit the number of users which can log into your machine. It simply sets various table sizes to reasonable values considering the maximum @@ -3461,8 +3452,8 @@ render numerous system utilities inoperative. The second part of the line specifies the disk and partition where the root filesystem and kernel can be found. Typically - this will be wd0 for systems - with non-SCSI drives, or sd0 + this will be wd0 for systems + with non-SCSI drives, or sd0 for systems with SCSI drives. @@ -3730,10 +3721,9 @@ controller fdc0 - Floppy drive controller: fd0 is the A: floppy drive, and - fd1 is the B: drive. - ft0 is a QIC-80 tape drive + Floppy drive controller: fd0 is the A: floppy drive, and + fd1 is the B: drive. + ft0 is a QIC-80 tape drive attached to the floppy controller. Comment out any lines corresponding to devices you do not have. @@ -3748,10 +3738,8 @@ controller wdc0 - This is the primary IDE controller. wd0 and wd1 are the master and slave hard - drive, respectively. wdc1 is + This is the primary IDE controller. wd0 and wd1 are the master and slave hard + drive, respectively. wdc1 is a secondary IDE controller where you might have a third or fourth hard drive, or an IDE CD-ROM. Comment out the lines which do not apply (if you have a SCSI hard drive, @@ -3765,11 +3753,11 @@ This device provides IDE CD-ROM support. Be sure to - leave wdc0 uncommented, and - wdc1 if you have more than + leave wdc0 uncommented, and + wdc1 if you have more than one IDE controller and your CD-ROM is on the second one card. To use this, you must also include the line - options ATAPI. + options ATAPI. @@ -3777,7 +3765,7 @@ vector npxintr - npx0 is the interface to + npx0 is the interface to the floating point math unit in FreeBSD, either the hardware co-processor or the software math emulator. It is NOT optional. @@ -3983,7 +3971,7 @@ Support for SCSI CD-ROM drives. - Note that the number 0 + Note that the number 0 in the above entries is slightly misleading: all these devices are automatically configured as they are found, regardless of how many of them are hooked up to the SCSI @@ -4012,12 +4000,11 @@ device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr - sc0 is the default + sc0 is the default console driver, which resembles an SCO console. Since most full-screen programs access the console through a terminal database library like termcap, it - should not matter much whether you use this or vt0, the VT220 compatible console + should not matter much whether you use this or vt0, the VT220 compatible console driver. When you log in, set your TERM variable to scoansi if full-screen programs have trouble running under this console. @@ -4030,8 +4017,7 @@ This is a VT220-compatible console driver, backwards compatible to VT100/102. It works well on some laptops - which have hardware incompatibilities with sc0. Also, set your TERM variable + which have hardware incompatibilities with sc0. Also, set your TERM variable to vt100 or vt220 when you log in. This driver might also prove useful when connecting to a large number of different machines over the network, where the @@ -4045,19 +4031,17 @@ options "PCVT_FREEBSD=210" - Required with the vt0 console driver. + Required with the vt0 console driver. options XSERVER - Only applicable with the vt0 console driver. This + Only applicable with the vt0 console driver. This includes code required to run the XFree86 X Window Server - under the vt0 + under the vt0 console driver. @@ -4328,7 +4312,7 @@ pseudo-device loop - loop is the generic + loop is the generic loopback device for TCP/IP. If you telnet or FTP to localhost (a.k.a. 127.0.0.1) it will come back at you through this pseudo-device. Mandatory. @@ -4338,7 +4322,7 @@ pseudo-device ether - ether is only needed if + ether is only needed if you have an Ethernet card and includes generic Ethernet protocol code. @@ -4348,12 +4332,12 @@ number - sl is for SLIP (Serial + sl is for SLIP (Serial Line Internet Protocol) support. This has been almost entirely supplanted by PPP, which is easier to set up, better suited for modem-to-modem connections, as well as more powerful. The number after - sl specifies how many + sl specifies how many simultaneous SLIP sessions to support. This handbook has more information on setting up a SLIP number - ppp is for kernel-mode + ppp is for kernel-mode PPP (Point-to-Point Protocol) support for dial-up Internet connections. There is also version of PPP implemented as a user application that uses the - section of the handbook. As with the sl device, + section of the handbook. As with the sl device, number specifies how many simultaneous PPP connections to support. @@ -4385,11 +4368,10 @@ number - tun is used by the + tun is used by the user-mode PPP software. This program is easy to set up and very fast. It also has special features such as automatic - dial-on-demand. The number after tun specifies the number of + dial-on-demand. The number after tun specifies the number of simultaneous PPP sessions to support. See the section of the handbook for more @@ -4433,8 +4415,7 @@ controller snd0 Generic sound driver code. Required for all of the - following sound cards except pca. + following sound cards except pca. @@ -4454,9 +4435,9 @@ If your SoundBlaster is on a different IRQ (such as - 5), change irq 7 to, for - example, irq 5 and remove - the conflicts keyword. + 5), change irq 7 to, for + example, irq 5 and remove + the conflicts keyword. Also, you must add the line: options "SBC_IRQ=5" @@ -4470,8 +4451,8 @@ If your SB16 is on a different 16-bit DMA channel - (such as 6 or 7), change the drq - 5 keyword appropriately, and then add the + (such as 6 or 7), change the drq + 5 keyword appropriately, and then add the line: options "SB16_DMA=6" @@ -4565,7 +4546,7 @@ pseudo-device gzip - gzip allows you to run + gzip allows you to run FreeBSD programs that have been compressed with gzip. The programs in /stand are compressed so it is a good idea to have this option in your kernel. @@ -4575,7 +4556,7 @@ pseudo-device log - log is used for logging + log is used for logging of kernel error messages. Mandatory. @@ -4585,13 +4566,13 @@ id="kernelconfig-ptys"> - pty is a + pty is a pseudo-terminal or simulated login port. It is used by incoming telnet and rlogin sessions, xterm, and some other applications such as emacs. The number indicates the number of - ptys to create. If you need + ptys to create. If you need more than GENERIC default of 16 simultaneous xterm windows and/or remote logins, be sure to increase this number accordingly, up to a maximum of 64. @@ -5247,22 +5228,22 @@ - The first line (permit - internet) allows users whose IP source address + The first line (permit + internet) allows users whose IP source address (which is vulnerable to spoofing) matches the specified value and mask, to use UNIX passwords. This should not be considered a security mechanism, but rather, a means to remind authorized users that they are using an insecure network and need to use S/Key for authentication. - The second line (permit user) + The second line (permit user) allows the specified user to use UNIX passwords at any time. Generally speaking, this should only be used for people who are either unable to use the key program, like those with dumb terminals, or those who are uneducable. - The third line (permit port) + The third line (permit port) allows all users logging in on the specified terminal line to use UNIX passwords; this would be used for dial-ups. @@ -6442,8 +6423,8 @@ to write a list of the current rules out to a file, and then - use a text editor to prepend `ipfw - ' before all the lines. This will allow the script to + use a text editor to prepend `ipfw + ' before all the lines. This will allow the script to be fed into /bin/sh and reload the rules into the kernel. Perhaps not the most efficient way, but it works. @@ -7019,11 +7000,10 @@ port where port is the device entry for the - port you want to make. Use lpt0 for the first parallel port, - lpt1 for the second, and - so on; use ttyd0 for the - first serial port, ttyd1 + port you want to make. Use lpt0 for the first parallel port, + lpt1 for the second, and + so on; use ttyd0 for the + first serial port, ttyd1 for the second, and so on. @@ -7088,16 +7068,14 @@ Edit your kernel configuration file. Look for or - add an lpt0 entry. If you - are setting up the second parallel port, use lpt1 instead. Use lpt2 for the third port, and so + add an lpt0 entry. If you + are setting up the second parallel port, use lpt1 instead. Use lpt2 for the third port, and so on. If you want interrupt-driven mode, add the - irq specifier: + irq specifier: device lpt0 at isa? port? tty irq N @@ -7110,7 +7088,7 @@ If you want polled mode, do not add the - irq specifier: + irq specifier: device lpt0 at isa? port? tty vector lptintr @@ -7297,16 +7275,12 @@ printer:dv=/dev/port:br#bps-rate:pa=parity where port is the device entry for the - serial port (ttyd0, - ttyd1, etc.), ttyd0, + ttyd1, etc.), bps-rate is the bits-per-second rate at which the printer communicates, and parity is the parity required by - the printer (either even, odd, none, or zero). + the printer (either even, odd, none, or zero). Here is a sample entry for a printer connected via @@ -7499,10 +7473,10 @@ At least one of the printers specified in the /etc/printcap should have the alias - lp. This is the default + lp. This is the default printer's name. If users do not have the PRINTER environment variable nor specify a printer name on the command line of any - of the LPD commands, then lp + of the LPD commands, then lp will be the default printer they get to use. Also, it is common practice to make the last alias for a @@ -7778,7 +7752,7 @@ When LPD opens the device specified by the lp capability, it reads the flag bits in - the sgttyb structure; it clears + the sgttyb structure; it clears any bits in the fc capability, then sets bits in the fs capability, then applies the resultant setting. It does the @@ -8354,7 +8328,7 @@ the lpr command line are treated as part of a single job. It is the currently - active job (note the word active + active job (note the word active under the Rank column), which means the printer should be currently printing that job. The second job consists of data passed as the standard input to the @@ -8851,7 +8825,7 @@ URL="http://www.freebsd.org/cgi/man.cgi?lpc">lpc commands. Most of the commands takes a printer-name argument to tell on which - printer to operate. You can use all + printer to operate. You can use all for the printer-name to mean all printers listed in /etc/printcap. @@ -8975,8 +8949,7 @@ with the listed job numbers or the jobs belonging to username at the top of the queue. - For this command, you cannot use all as the all as the printer-name. @@ -9352,7 +9325,7 @@ text jobs to the printer, then you are urged to augment your printer setup. To do so, we have the text filter detect if the arriving job is plain text or PostScript. All PostScript jobs - must start with %! (for other + must start with %! (for other printer languages, see your printer documentation). If those are the first two characters in the job, we have PostScript, and can pass the rest of the job directly. If those are not the first @@ -9929,7 +9902,7 @@ In the , we turned off header pages by - specifying sh (meaning suppress + specifying sh (meaning suppress header) in the /etc/printcap file. To enable header pages for a printer, just remove the sh capability. @@ -10012,15 +9985,14 @@ /etc/printcap). If you prefer, LPD can make a short - header; specify sb + header; specify sb (short banner) in the /etc/printcap file. The header page will look like this: rose:kelly Job: outline Date: Sun Sep 17 11:07:51 1995 Also by default, LPD prints the header page - first, then the job. To reverse that, specify hl (header last) in + first, then the job. To reverse that, specify hl (header last) in /etc/printcap. @@ -13062,7 +13034,7 @@ Here is a config snippet from a machine with a Digi International PC/8 with 16550. It has 8 modems connected to these 8 lines, and they work just great. Do not forget to add - options COM_MULTIPORT or it will + options COM_MULTIPORT or it will not work very well! @@ -13301,10 +13273,7 @@ If appropriate, add entries to - by duplicating serial device (ttyd) entries and using ttyc in place of ttyd. For example: + by duplicating serial device (ttyd) entries and using ttyc in place of ttyd. For example: ttyc0 "/usr/libexec/getty std.38400" @@ -14468,8 +14437,7 @@ remap=tt>ahb, ahc, ncr and amd will automatically obtain the correct parameters from the host adapters themselves at boot - time; thus, you just need to write, for instance, "controller ahc0". + time; thus, you just need to write, for instance, "controller ahc0". An example loosely based on the FreeBSD 2.2.5-Release @@ -16702,8 +16670,7 @@ For each ttyv? entry in /etc/ttys change terminal type from - cons25 to cons25r, i.e. each entry should looks + cons25 to cons25r, i.e. each entry should looks like ttyv0 "/usr/libexec/getty Pc" cons25r on secure @@ -16928,10 +16895,9 @@ KOI8-R fonts, but this ones scaled better. - Check find "Files" section + Check find "Files" section in your /etc/XF86Config, following - lines must be before any other FontPath entries: + lines must be before any other FontPath entries: FontPath "/usr/X11R6/lib/X11/fonts/cyrillic/misc" FontPath "/usr/X11R6/lib/X11/fonts/cyrillic/75dpi" FontPath @@ -16945,9 +16911,9 @@ To activate Russian keyboard add XkbKeymap "xfree86(ru)" line into - "Keyboard" section in your + "Keyboard" section in your /etc/XF86Config, also make sure that - XkbDisable is turned off + XkbDisable is turned off (commented out) there. @@ -17466,10 +17432,8 @@ The file /etc/gettytab contains lots of entries for terminal lines both old and new. In almost all - cases, the entries that start with the text std will work for hardwired terminals. - These entries ignore parity. There is a std entry for each bps rate from 110 to + cases, the entries that start with the text std will work for hardwired terminals. + These entries ignore parity. There is a std entry for each bps rate from 110 to 115200. Of course, you can add your own entries to this file. The manual page gettytab5 provides more information. @@ -17497,8 +17461,8 @@ The third field in the /etc/ttys file lists the default terminal type for the port. For dialup ports, - you typically put unknown or - dialup in this field because users + you typically put unknown or + dialup in this field because users may dial up with practically any kind of terminal or software. For hardwired terminals, the terminal type does not change, so you can put a real terminal type in this field. @@ -17535,18 +17499,15 @@ Enabling the Port The next field in /etc/ttys, the fourth - field, tells whether to enable the port. Putting on here will have the init process start the program in the + field, tells whether to enable the port. Putting on here will have the init process start the program in the second field, getty, which will - prompt for a login. If you put off in the fourth field, there will be no + prompt for a login. If you put off in the fourth field, there will be no getty, and hence no logins on the port. - So, naturally, you want an on + So, naturally, you want an on in this field. Here again is the /etc/ttys - file. We have turned each port on. + file. We have turned each port on. ttyd1 "/usr/libexec/getty std.38400" wy50 on secure ttyd5 "/usr/libexec/getty std.19200" vt100 @@ -17561,7 +17522,7 @@ Specifying Secure Ports We have arrived at the last field (well, almost: there is an - optional window specifier, but we + optional window specifier, but we will ignore that). The last field tells whether the port is secure. @@ -17675,8 +17636,8 @@ 22189 d1 Is+ 0:00.03 /usr/libexec/getty std.38400 ttyd1 shows that a getty is running on the second - serial port ttyd1 and is - using the std.38400 entry in + serial port ttyd1 and is + using the std.38400 entry in /etc/gettytab. If no getty process is @@ -18005,9 +17966,8 @@ watch for messages while the kernel is booting, or use the /sbin/dmesg command to replay the kernel's boot messages. In particular, look for messages that - start with the characters sio. Hint: - to view just the messages that have the word sio, use the command: + start with the characters sio. Hint: + to view just the messages that have the word sio, use the command: @@ -18067,7 +18027,7 @@ changed between versions. - port "IO_COM1" is a + port "IO_COM1" is a substitution for port 0x3f8, IO_COM2 is 0x2f8, IO_COM3 is 0x3e8, and @@ -18237,8 +18197,7 @@ You will need to setup an entry in /etc/gettytab to give getty information about the speeds you wish to use for your modem. If you have a 2400 bps modem, you - can probably use the existing D2400 entry. This entry already exists + can probably use the existing D2400 entry. This entry already exists in the FreeBSD 1.1.5.1 gettytab file, so you do not need to add it unless it is missing under your version of FreeBSD: @@ -18272,8 +18231,7 @@ On FreeBSD 1.1.5 and later, this will result in 8-bit, no - parity connections. Under FreeBSD 1.1, add :np: parameters to the :np: parameters to the std.xxx entries at the top of the file for 8 bits, no parity; otherwise, the default is 7 bits, even parity. @@ -18342,29 +18300,27 @@ The first item in the above line is the device special file - for this entry - ttyd0 means + for this entry - ttyd0 means /dev/ttyd0 is the file that this getty will be watching. The second item, "/usr/libexec/getty xxx" (xxx will be replaced by the initial gettytab capability) is the process init will run on the - device. The third item, dialup, - is the default terminal type. The fourth parameter, on, indicates to dialup, + is the default terminal type. The fourth parameter, on, indicates to init that the line is operational. There - can be a fifth parameter, secure, + can be a fifth parameter, secure, but it should only be used for terminals which are physically secure (such as the system console). - The default terminal type (dialup in the example above) may depend on - local preferences. dialup is the + The default terminal type (dialup in the example above) may depend on + local preferences. dialup is the traditional default terminal type on dialup lines so that users may customize their login scripts to notice when the terminal is - dialup and automatically adjust + dialup and automatically adjust their terminal type. However, the author finds it easier at his - site to specify vt102 as the + site to specify vt102 as the default terminal type, since the users just use VT102 emulation on their remote systems. @@ -18402,7 +18358,7 @@ If your modem is locked at a different data rate, substitute the appropriate name for the std.speed - entry for std.19200 from + entry for std.19200 from /etc/gettytab for your modem's data rate. @@ -18417,8 +18373,7 @@ /etc/gettytab. For example, if you added the above suggested entry for a matching-speed modem that starts at 19.2 Kbps (the gettytab entry containing the V19200 starting point), your gettytab entry containing the V19200 starting point), your ttys entry might look like this: @@ -18872,9 +18827,9 @@ /usr/src/usr.bin/tip/tip Obviously you need the source distribution to do this. - Edit the line #define HAYES - 0 to #define HAYES - 1. Then make and + Edit the line #define HAYES + 0 to #define HAYES + 1. Then make and make install. Everything works nicely after that. @@ -18902,7 +18857,7 @@ Or use cu as root with the following command: cu -lline -sspeed with line being the serial port (e.g./dev/cuaa0) and speed being - the speed (e.g.57600). When you are + the speed (e.g.57600). When you are done entering the AT commands hit ~. to exit. @@ -18946,10 +18901,10 @@ Do I have to type in the bps rate every time I do that? - Put in an entry for tip1200 or - cu1200, but go ahead and use + Put in an entry for tip1200 or + cu1200, but go ahead and use whatever bps rate is appropriate with the br capability. tip thinks a good default is 1200 bps which - is why it looks for a tip1200 + is why it looks for a tip1200 entry. You do not have to use 1200 bps, though. @@ -19631,7 +19586,7 @@ circumstances, but the above example will almost always work. If it fails, you may be able to defeat some broken ppp implementations by supplying an additional - 0.0.0.0 argument: + 0.0.0.0 argument: @@ -19881,10 +19836,10 @@ Note the indenting is important. - The default: section is + The default: section is loaded for each session. For each dialup line enabled in /etc/ttys create an entry similar to the - one for ttyd0: above. Each line + one for ttyd0: above. Each line should get a unique IP from your pool of ip address for dynamic users. @@ -21034,11 +20989,9 @@ which sliplogin attached itself (slip interface 0, in the above example, which was the first parameter in the list given to slip.login) - to set the local IP address (dc-slip), remote IP address (sl-helmer), network mask for the SLIP + to set the local IP address (dc-slip), remote IP address (sl-helmer), network mask for the SLIP interface (0xfffffc00), and any additional - flags (autocomp). If something + flags (autocomp). If something goes wrong, sliplogin usually logs good informational messages via the daemon syslog facility, which usually goes into /var/log/messages @@ -21080,8 +21033,7 @@ The sl0 and sl1 interfaces shown in netstat -i's output indicate that there are two SLIP interfaces built into the kernel. (The asterisks after - the sl0 and sl1 indicate that the interfaces are + the sl0 and sl1 indicate that the interfaces are down.) However, FreeBSD's default kernels do not come configured to @@ -21196,22 +21148,22 @@ - normal - no header + normal - no header compression - compress - compress + compress - compress headers - autocomp - compress + autocomp - compress headers if the remote end allows it - noicmp - disable ICMP + noicmp - disable ICMP packets (so any ping packets will be dropped instead of using up your bandwidth) @@ -21470,7 +21422,7 @@ certainly turn off the tracing options if gated works OK for you. You will need to change the xxx.xxx.yy's into the network address of your own SLIP subnet (be sure to change the - net mask in the proto direct + net mask in the proto direct clause as well). When you get gated built and @@ -21563,8 +21515,7 @@ cover in the next section) and the localhost route. The interface (Netif column) - that it specifies to use for localhost is localhost is lo0, also known as the loopback device. This says to keep all traffic for this destination internal, rather than sending it out over the LAN, since it will only end up back @@ -21575,7 +21526,7 @@ (test0 in the example) on the local ethernet and add a route for that host, directly to it over the ethernet interface, ed0. There is - also a timeout (Expire column) + also a timeout (Expire column) associated with this type of route, which is used if we fail to hear from the host in a specific amount of time. In this case the route will be automatically deleted. These hosts are identified @@ -21587,8 +21538,7 @@ (10.20.30.255 is the broadcast address for the subnet 10.20.30, and foobar.com is the domain name - associated with that subnet). The designation link#1 refers to the first ethernet card in + associated with that subnet). The designation link#1 refers to the first ethernet card in the machine. You will notice no additional interface is specified for those. @@ -21598,29 +21548,26 @@ only routes which are statically defined (ie. entered explicitly) will exist. - The host1 line refers to our + The host1 line refers to our host, which it knows by ethernet address. Since we are the sending host, FreeBSD knows to use the loopback interface (lo0) rather than sending it out over the ethernet interface. - The two host2 lines are an + The two host2 lines are an example of what happens when we use an ifconfig alias (see the section of ethernet for reasons why we would do this). The - => symbol after the lo0 interface says that not only are we + => symbol after the lo0 interface says that not only are we using the loopback (since this is address also refers to the local host), but specifically it is an alias. Such routes only show up on the host that supports the alias; all other hosts on the local - network will simply have a link#1 + network will simply have a link#1 line for such. - The final line (destination subnet 224) deals with MultiCasting, which will be + The final line (destination subnet 224) deals with MultiCasting, which will be covered in a another section. - The other column that we should talk about are the Flags. Each route has different attributes + The other column that we should talk about are the Flags. Each route has different attributes that are described in the column. Below is a short table of some of these flags and their meanings: @@ -21702,8 +21649,7 @@ If all known paths fail, the system has one last option: the default route. This route is a special type of gateway route (usually the only one present in the - system), and is always marked with a c in the flags field. For hosts on a + system), and is always marked with a c in the flags field. For hosts on a local area network, this gateway is set to whatever machine has a direct connection to the outside world (whether via PPP link, or your hardware device attached to a dedicated data line). @@ -22875,12 +22821,12 @@ As a good workaround, you can place the line - search foo.bar.edu - bar.edu + search foo.bar.edu + bar.edu instead of the previous - domain foo.bar.edu + domain foo.bar.edu into your /etc/resolv.conf. However, make sure that the search order does not go beyond the boundary @@ -23480,8 +23426,8 @@ future, this will be the only place where announcements concerning the operations of the CTM system will be posted. Send an email to &a.majordomo; with a single - line of subscribe - ctm-announce to get added to the list. + line of subscribe + ctm-announce to get added to the list. @@ -24392,10 +24338,7 @@ collections are reflected by the use of indentation in the list below. - The most commonly used collections are src-all, cvs-crypto, and ports-all. The other collections are used + The most commonly used collections are src-all, cvs-crypto, and ports-all. The other collections are used only by small groups of people for specialized purposes, and some mirror sites may not carry all of them. @@ -25087,8 +25030,8 @@ Contributed by &a.nik;. Once you have synchronised your local source tree against a - particular version of FreeBSD (stable, - current and so on) you must then use + particular version of FreeBSD (stable, + current and so on) you must then use the source tree to rebuild the system. Currently, the best source of information on how to do that is a @@ -25732,7 +25675,7 @@ After filing a report, you should receive confirmation along with a tracking number. Keep this tracking number so that you can update us with details about the problem by sending mail to bug-followup@FreeBSD.ORG. Use the number as the message subject, e.g. "Re: kern/3377". Additional information for any bug report should be submitted this way. + URL="mailto:bug-followup@FreeBSD.ORG">bug-followup@FreeBSD.ORG. Use the number as the message subject, e.g. "Re: kern/3377". Additional information for any bug report should be submitted this way. If you do not receive confirmation in a timely fashion (3 days to a week, depending on your email connection) or are, for some @@ -25873,8 +25816,7 @@ To place a BSD-style copyright on your work, include the following text at the very beginning of every source code file you - wish to protect, replacing the text between the %% with the appropriate information. + wish to protect, replacing the text between the %% with the appropriate information. Copyright (c) %%proper_years_here%% %%your_name_here%%, %%your_state%% %%your_zip%%. All rights reserved. @@ -25940,7 +25882,7 @@ Only a fraction of the overridable variables - (${..}) are mentioned in + (${..}) are mentioned in this document. Most (if not all) are documented at the start of bsd.port.mk. This file uses a non-standard tab setting. Emacs and @@ -26034,7 +25976,7 @@ __FreeBSD__ is defined in all versions of FreeBSD. Use it if the change you are making ONLY affects FreeBSD. Porting gotchas like the use of - sys_errlist[] vs + sys_errlist[] vs strerror() are Berkeleyisms, not FreeBSD changes. @@ -26042,8 +25984,8 @@ In FreeBSD 2.x, __FreeBSD__ is - defined to be 2. In earlier - versions, it is 1. Later + defined to be 2. In earlier + versions, it is 1. Later versions will bump it to match their major version number. @@ -26055,8 +25997,8 @@ described above. If there actually is a FreeBSD specific change (such as special shared library options when using ld) then it is OK to use - __FreeBSD__ and #if - __FreeBSD__ > 1 to detect a FreeBSD 2.x + __FreeBSD__ and #if + __FreeBSD__ > 1 to detect a FreeBSD 2.x and later system. If you need more granularity in detecting FreeBSD systems since 2.0-RELEASE you can use the following: @@ -26156,7 +26098,7 @@ See if you can figure it out. Do not worry about the - contents of the $Id$ + contents of the $Id$ line, it will be filled in automatically by CVS when the port is imported to our main ports tree. You can find a more detailed example in the - If the port uses XmClientLibs in its Imakefile, + If the port uses XmClientLibs in its Imakefile, change it to ${MOTIFLIB} ${XTOOLLIB} ${XLIB}. @@ -30611,7 +30552,7 @@ People familiar with the C language will immediately recognize that everything could be counted as a config option where there - is at least a single #ifdef + is at least a single #ifdef referencing it... However, it's unlikely that many people would put @@ -30634,8 +30575,7 @@ The old-style option mechanism still has one advantage for local options or maybe experimental options that have a short anticipated - lifetime: since it is easy to add a new #ifdef to the kernel source, this has already + lifetime: since it is easy to add a new #ifdef to the kernel source, this has already made it a kernel config option. In this case, the administrator using such an option is responsible himself for knowing about its implications (and maybe manually forcing the recompilation of parts @@ -30688,8 +30628,7 @@ #include "opt_foo.h" - on top, before all the #include <xxx.h> stuff. This sequence + on top, before all the #include <xxx.h> stuff. This sequence is most important as the options could override defaults from the regular include files, if the defaults are of the form @@ -30728,8 +30667,8 @@ on a crash dump. They assume that you have enough swap space for a crash dump. If you have multiple swap partitions and the first one is too small to hold the dump, you can configure your kernel to use - an alternate dump device (in the config - kernel line), or you can specify an alternate using the + an alternate dump device (in the config + kernel line), or you can specify an alternate using the dumpon8 command. Dumps to non-swap devices, tapes for example, are currently not supported. Config your kernel using config -g. See However, it obviously points to garbage, so we have found our error! (For those unfamiliar with that particular - piece of code: tp->t_line + piece of code: tp->t_line refers to the line discipline of the console device here, which must be a rather small integer number.) @@ -30997,8 +30936,8 @@ Ctrl-Alt-ESC. For syscons, this can be remapped; some of the distributed maps do this, so watch out. There is an option available for serial consoles that allows the use of a serial line BREAK on - the console line to enter DDB (options - BREAK_TO_DEBUGGER in the kernel config file). It is + the console line to enter DDB (options + BREAK_TO_DEBUGGER in the kernel config file). It is not the default since there are a lot of crappy serial adapters around that gratuitously generate a BREAK condition, for example when pulling the cable. @@ -34265,19 +34204,16 @@ The following CVSup site is especially designed for users. Unlike the other CVSup mirrors, - it is kept up-to-date by CTM. That means if you CVSup cvs-all with release=cvs + it is kept up-to-date by CTM. That means if you CVSup cvs-all with release=cvs from this site, you get a version of the repository (including the inevitable .ctm_status file) which is - suitable for being updated using the CTM cvs-cur deltas. This allows users who track - the entire cvs-all tree to go from + suitable for being updated using the CTM cvs-cur deltas. This allows users who track + the entire cvs-all tree to go from CVSup to CTM without having to rebuild their repository from scratch using a fresh CTM base delta. - This special feature only works for the cvs-all distribution with + This special feature only works for the cvs-all distribution with cvs as the release tag. CVSupping any other distribution and/or release will get you the specified distribution, but it will not be suitable for CTM updating. diff --git a/en_US.ISO_8859-1/books/handbook/book.sgml b/en_US.ISO_8859-1/books/handbook/book.sgml index 7e0b598780..e36c246d94 100644 --- a/en_US.ISO_8859-1/books/handbook/book.sgml +++ b/en_US.ISO_8859-1/books/handbook/book.sgml @@ -1045,30 +1045,26 @@ - SoundBlaster SCSI and ProAudio Spectrum SCSI (cd) + SoundBlaster SCSI and ProAudio Spectrum SCSI (cd) - Mitsumi (all models) proprietary interface (mcd) + Mitsumi (all models) proprietary interface (mcd) Matsushita/Panasonic (Creative) CR-562/CR-563 - proprietary interface (matcd) + proprietary interface (matcd) - Sony proprietary interface (scd) + Sony proprietary interface (scd) ATAPI IDE interface (experimental and should be - considered ALPHA quality!) (wcd) + considered ALPHA quality!) (wcd) @@ -3287,7 +3283,7 @@ The general format of a configuration file is quite simple. Each line contains a keyword and one or more arguments. For simplicity, most lines only contain one argument. Anything following a - # is considered a comment and ignored. + # is considered a comment and ignored. The following sections describe each keyword, generally in the order they are listed in GENERIC, although some related keywords have been grouped together in a single section @@ -3307,7 +3303,7 @@ this caused a creeping optionism, with nobody really knowing which option has been referenced in what files. - In the new scheme, every #ifdef + In the new scheme, every #ifdef that is intended to be dependent upon an option gets this option out of an opt_foo.h declaration file created in the compile directory by config. The list of valid options for @@ -3327,8 +3323,7 @@ machine "i386" - The first keyword is machine, which, since FreeBSD only + The first keyword is machine, which, since FreeBSD only runs on Intel 386 and compatible chips, is i386. @@ -3343,7 +3338,7 @@ cpu "cpu_type" - The next keyword is cpu, + The next keyword is cpu, which includes support for each CPU supported by FreeBSD. The possible values of cpu_type @@ -3366,8 +3361,7 @@ I686_CPU - and multiple instances of the cpu line may be present with + and multiple instances of the cpu line may be present with different values of cpu_type as are present in the GENERIC kernel. @@ -3381,25 +3375,23 @@ ident machine_name - Next, we have ident, + Next, we have ident, which is the identification of the kernel. You should change this from GENERIC to whatever you named your kernel, in this example, MYKERNEL. The value you put in - ident will print when you + ident will print when you boot up the kernel, so it is useful to give a kernel a different name if you want to keep it separate from your usual kernel (if you want to build an experimental kernel, - for example). Note that, as with machine and - cpu, enclose your kernel's name in quotation + for example). Note that, as with machine and + cpu, enclose your kernel's name in quotation marks if it contains any numbers. Since this name is passed to the C compiler as a switch, do not use names like , or something that could be - confused with another machine or CPU name, like vax. + confused with another machine or CPU name, like vax. @@ -3410,21 +3402,20 @@ system tables. This number is supposed to be roughly equal to the number of simultaneous users you expect to have on your machine. However, under normal - circumstances, you will want to set maxusers to at least four, + circumstances, you will want to set maxusers to at least four, especially if you are using the X Window System or compiling software. The reason is that the most important - table set by maxusers is the + table set by maxusers is the maximum number of processes, which is set to 20 + 16 * maxusers, so if you set - maxusers to one, then you + maxusers to one, then you can only have 36 simultaneous processes, including the 18 or so that the system starts up at boot time, and the 15 or so you will probably create when you start the X Window System. Even a simple task like reading a man page will start up nine processes to filter, decompress, and view it. Setting - maxusers to 4 will allow you + maxusers to 4 will allow you to have up to 84 simultaneous processes, which should be enough for anyone. If, however, you see the dreaded proc table full error when trying to start another @@ -3433,7 +3424,7 @@ you can always increase this number and rebuild. - maxuser does + maxuser does not limit the number of users which can log into your machine. It simply sets various table sizes to reasonable values considering the maximum @@ -3461,8 +3452,8 @@ render numerous system utilities inoperative. The second part of the line specifies the disk and partition where the root filesystem and kernel can be found. Typically - this will be wd0 for systems - with non-SCSI drives, or sd0 + this will be wd0 for systems + with non-SCSI drives, or sd0 for systems with SCSI drives. @@ -3730,10 +3721,9 @@ controller fdc0 - Floppy drive controller: fd0 is the A: floppy drive, and - fd1 is the B: drive. - ft0 is a QIC-80 tape drive + Floppy drive controller: fd0 is the A: floppy drive, and + fd1 is the B: drive. + ft0 is a QIC-80 tape drive attached to the floppy controller. Comment out any lines corresponding to devices you do not have. @@ -3748,10 +3738,8 @@ controller wdc0 - This is the primary IDE controller. wd0 and wd1 are the master and slave hard - drive, respectively. wdc1 is + This is the primary IDE controller. wd0 and wd1 are the master and slave hard + drive, respectively. wdc1 is a secondary IDE controller where you might have a third or fourth hard drive, or an IDE CD-ROM. Comment out the lines which do not apply (if you have a SCSI hard drive, @@ -3765,11 +3753,11 @@ This device provides IDE CD-ROM support. Be sure to - leave wdc0 uncommented, and - wdc1 if you have more than + leave wdc0 uncommented, and + wdc1 if you have more than one IDE controller and your CD-ROM is on the second one card. To use this, you must also include the line - options ATAPI. + options ATAPI. @@ -3777,7 +3765,7 @@ vector npxintr - npx0 is the interface to + npx0 is the interface to the floating point math unit in FreeBSD, either the hardware co-processor or the software math emulator. It is NOT optional. @@ -3983,7 +3971,7 @@ Support for SCSI CD-ROM drives. - Note that the number 0 + Note that the number 0 in the above entries is slightly misleading: all these devices are automatically configured as they are found, regardless of how many of them are hooked up to the SCSI @@ -4012,12 +4000,11 @@ device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr - sc0 is the default + sc0 is the default console driver, which resembles an SCO console. Since most full-screen programs access the console through a terminal database library like termcap, it - should not matter much whether you use this or vt0, the VT220 compatible console + should not matter much whether you use this or vt0, the VT220 compatible console driver. When you log in, set your TERM variable to scoansi if full-screen programs have trouble running under this console. @@ -4030,8 +4017,7 @@ This is a VT220-compatible console driver, backwards compatible to VT100/102. It works well on some laptops - which have hardware incompatibilities with sc0. Also, set your TERM variable + which have hardware incompatibilities with sc0. Also, set your TERM variable to vt100 or vt220 when you log in. This driver might also prove useful when connecting to a large number of different machines over the network, where the @@ -4045,19 +4031,17 @@ options "PCVT_FREEBSD=210" - Required with the vt0 console driver. + Required with the vt0 console driver. options XSERVER - Only applicable with the vt0 console driver. This + Only applicable with the vt0 console driver. This includes code required to run the XFree86 X Window Server - under the vt0 + under the vt0 console driver. @@ -4328,7 +4312,7 @@ pseudo-device loop - loop is the generic + loop is the generic loopback device for TCP/IP. If you telnet or FTP to localhost (a.k.a. 127.0.0.1) it will come back at you through this pseudo-device. Mandatory. @@ -4338,7 +4322,7 @@ pseudo-device ether - ether is only needed if + ether is only needed if you have an Ethernet card and includes generic Ethernet protocol code. @@ -4348,12 +4332,12 @@ number - sl is for SLIP (Serial + sl is for SLIP (Serial Line Internet Protocol) support. This has been almost entirely supplanted by PPP, which is easier to set up, better suited for modem-to-modem connections, as well as more powerful. The number after - sl specifies how many + sl specifies how many simultaneous SLIP sessions to support. This handbook has more information on setting up a SLIP number - ppp is for kernel-mode + ppp is for kernel-mode PPP (Point-to-Point Protocol) support for dial-up Internet connections. There is also version of PPP implemented as a user application that uses the - section of the handbook. As with the sl device, + section of the handbook. As with the sl device, number specifies how many simultaneous PPP connections to support. @@ -4385,11 +4368,10 @@ number - tun is used by the + tun is used by the user-mode PPP software. This program is easy to set up and very fast. It also has special features such as automatic - dial-on-demand. The number after tun specifies the number of + dial-on-demand. The number after tun specifies the number of simultaneous PPP sessions to support. See the section of the handbook for more @@ -4433,8 +4415,7 @@ controller snd0 Generic sound driver code. Required for all of the - following sound cards except pca. + following sound cards except pca. @@ -4454,9 +4435,9 @@ If your SoundBlaster is on a different IRQ (such as - 5), change irq 7 to, for - example, irq 5 and remove - the conflicts keyword. + 5), change irq 7 to, for + example, irq 5 and remove + the conflicts keyword. Also, you must add the line: options "SBC_IRQ=5" @@ -4470,8 +4451,8 @@ If your SB16 is on a different 16-bit DMA channel - (such as 6 or 7), change the drq - 5 keyword appropriately, and then add the + (such as 6 or 7), change the drq + 5 keyword appropriately, and then add the line: options "SB16_DMA=6" @@ -4565,7 +4546,7 @@ pseudo-device gzip - gzip allows you to run + gzip allows you to run FreeBSD programs that have been compressed with gzip. The programs in /stand are compressed so it is a good idea to have this option in your kernel. @@ -4575,7 +4556,7 @@ pseudo-device log - log is used for logging + log is used for logging of kernel error messages. Mandatory. @@ -4585,13 +4566,13 @@ id="kernelconfig-ptys"> - pty is a + pty is a pseudo-terminal or simulated login port. It is used by incoming telnet and rlogin sessions, xterm, and some other applications such as emacs. The number indicates the number of - ptys to create. If you need + ptys to create. If you need more than GENERIC default of 16 simultaneous xterm windows and/or remote logins, be sure to increase this number accordingly, up to a maximum of 64. @@ -5247,22 +5228,22 @@ - The first line (permit - internet) allows users whose IP source address + The first line (permit + internet) allows users whose IP source address (which is vulnerable to spoofing) matches the specified value and mask, to use UNIX passwords. This should not be considered a security mechanism, but rather, a means to remind authorized users that they are using an insecure network and need to use S/Key for authentication. - The second line (permit user) + The second line (permit user) allows the specified user to use UNIX passwords at any time. Generally speaking, this should only be used for people who are either unable to use the key program, like those with dumb terminals, or those who are uneducable. - The third line (permit port) + The third line (permit port) allows all users logging in on the specified terminal line to use UNIX passwords; this would be used for dial-ups. @@ -6442,8 +6423,8 @@ to write a list of the current rules out to a file, and then - use a text editor to prepend `ipfw - ' before all the lines. This will allow the script to + use a text editor to prepend `ipfw + ' before all the lines. This will allow the script to be fed into /bin/sh and reload the rules into the kernel. Perhaps not the most efficient way, but it works. @@ -7019,11 +7000,10 @@ port where port is the device entry for the - port you want to make. Use lpt0 for the first parallel port, - lpt1 for the second, and - so on; use ttyd0 for the - first serial port, ttyd1 + port you want to make. Use lpt0 for the first parallel port, + lpt1 for the second, and + so on; use ttyd0 for the + first serial port, ttyd1 for the second, and so on. @@ -7088,16 +7068,14 @@ Edit your kernel configuration file. Look for or - add an lpt0 entry. If you - are setting up the second parallel port, use lpt1 instead. Use lpt2 for the third port, and so + add an lpt0 entry. If you + are setting up the second parallel port, use lpt1 instead. Use lpt2 for the third port, and so on. If you want interrupt-driven mode, add the - irq specifier: + irq specifier: device lpt0 at isa? port? tty irq N @@ -7110,7 +7088,7 @@ If you want polled mode, do not add the - irq specifier: + irq specifier: device lpt0 at isa? port? tty vector lptintr @@ -7297,16 +7275,12 @@ printer:dv=/dev/port:br#bps-rate:pa=parity where port is the device entry for the - serial port (ttyd0, - ttyd1, etc.), ttyd0, + ttyd1, etc.), bps-rate is the bits-per-second rate at which the printer communicates, and parity is the parity required by - the printer (either even, odd, none, or zero). + the printer (either even, odd, none, or zero). Here is a sample entry for a printer connected via @@ -7499,10 +7473,10 @@ At least one of the printers specified in the /etc/printcap should have the alias - lp. This is the default + lp. This is the default printer's name. If users do not have the PRINTER environment variable nor specify a printer name on the command line of any - of the LPD commands, then lp + of the LPD commands, then lp will be the default printer they get to use. Also, it is common practice to make the last alias for a @@ -7778,7 +7752,7 @@ When LPD opens the device specified by the lp capability, it reads the flag bits in - the sgttyb structure; it clears + the sgttyb structure; it clears any bits in the fc capability, then sets bits in the fs capability, then applies the resultant setting. It does the @@ -8354,7 +8328,7 @@ the lpr command line are treated as part of a single job. It is the currently - active job (note the word active + active job (note the word active under the Rank column), which means the printer should be currently printing that job. The second job consists of data passed as the standard input to the @@ -8851,7 +8825,7 @@ URL="http://www.freebsd.org/cgi/man.cgi?lpc">lpc commands. Most of the commands takes a printer-name argument to tell on which - printer to operate. You can use all + printer to operate. You can use all for the printer-name to mean all printers listed in /etc/printcap. @@ -8975,8 +8949,7 @@ with the listed job numbers or the jobs belonging to username at the top of the queue. - For this command, you cannot use all as the all as the printer-name. @@ -9352,7 +9325,7 @@ text jobs to the printer, then you are urged to augment your printer setup. To do so, we have the text filter detect if the arriving job is plain text or PostScript. All PostScript jobs - must start with %! (for other + must start with %! (for other printer languages, see your printer documentation). If those are the first two characters in the job, we have PostScript, and can pass the rest of the job directly. If those are not the first @@ -9929,7 +9902,7 @@ In the , we turned off header pages by - specifying sh (meaning suppress + specifying sh (meaning suppress header) in the /etc/printcap file. To enable header pages for a printer, just remove the sh capability. @@ -10012,15 +9985,14 @@ /etc/printcap). If you prefer, LPD can make a short - header; specify sb + header; specify sb (short banner) in the /etc/printcap file. The header page will look like this: rose:kelly Job: outline Date: Sun Sep 17 11:07:51 1995 Also by default, LPD prints the header page - first, then the job. To reverse that, specify hl (header last) in + first, then the job. To reverse that, specify hl (header last) in /etc/printcap. @@ -13062,7 +13034,7 @@ Here is a config snippet from a machine with a Digi International PC/8 with 16550. It has 8 modems connected to these 8 lines, and they work just great. Do not forget to add - options COM_MULTIPORT or it will + options COM_MULTIPORT or it will not work very well! @@ -13301,10 +13273,7 @@ If appropriate, add entries to - by duplicating serial device (ttyd) entries and using ttyc in place of ttyd. For example: + by duplicating serial device (ttyd) entries and using ttyc in place of ttyd. For example: ttyc0 "/usr/libexec/getty std.38400" @@ -14468,8 +14437,7 @@ remap=tt>ahb, ahc, ncr and amd will automatically obtain the correct parameters from the host adapters themselves at boot - time; thus, you just need to write, for instance, "controller ahc0". + time; thus, you just need to write, for instance, "controller ahc0". An example loosely based on the FreeBSD 2.2.5-Release @@ -16702,8 +16670,7 @@ For each ttyv? entry in /etc/ttys change terminal type from - cons25 to cons25r, i.e. each entry should looks + cons25 to cons25r, i.e. each entry should looks like ttyv0 "/usr/libexec/getty Pc" cons25r on secure @@ -16928,10 +16895,9 @@ KOI8-R fonts, but this ones scaled better. - Check find "Files" section + Check find "Files" section in your /etc/XF86Config, following - lines must be before any other FontPath entries: + lines must be before any other FontPath entries: FontPath "/usr/X11R6/lib/X11/fonts/cyrillic/misc" FontPath "/usr/X11R6/lib/X11/fonts/cyrillic/75dpi" FontPath @@ -16945,9 +16911,9 @@ To activate Russian keyboard add XkbKeymap "xfree86(ru)" line into - "Keyboard" section in your + "Keyboard" section in your /etc/XF86Config, also make sure that - XkbDisable is turned off + XkbDisable is turned off (commented out) there. @@ -17466,10 +17432,8 @@ The file /etc/gettytab contains lots of entries for terminal lines both old and new. In almost all - cases, the entries that start with the text std will work for hardwired terminals. - These entries ignore parity. There is a std entry for each bps rate from 110 to + cases, the entries that start with the text std will work for hardwired terminals. + These entries ignore parity. There is a std entry for each bps rate from 110 to 115200. Of course, you can add your own entries to this file. The manual page gettytab5 provides more information. @@ -17497,8 +17461,8 @@ The third field in the /etc/ttys file lists the default terminal type for the port. For dialup ports, - you typically put unknown or - dialup in this field because users + you typically put unknown or + dialup in this field because users may dial up with practically any kind of terminal or software. For hardwired terminals, the terminal type does not change, so you can put a real terminal type in this field. @@ -17535,18 +17499,15 @@ Enabling the Port The next field in /etc/ttys, the fourth - field, tells whether to enable the port. Putting on here will have the init process start the program in the + field, tells whether to enable the port. Putting on here will have the init process start the program in the second field, getty, which will - prompt for a login. If you put off in the fourth field, there will be no + prompt for a login. If you put off in the fourth field, there will be no getty, and hence no logins on the port. - So, naturally, you want an on + So, naturally, you want an on in this field. Here again is the /etc/ttys - file. We have turned each port on. + file. We have turned each port on. ttyd1 "/usr/libexec/getty std.38400" wy50 on secure ttyd5 "/usr/libexec/getty std.19200" vt100 @@ -17561,7 +17522,7 @@ Specifying Secure Ports We have arrived at the last field (well, almost: there is an - optional window specifier, but we + optional window specifier, but we will ignore that). The last field tells whether the port is secure. @@ -17675,8 +17636,8 @@ 22189 d1 Is+ 0:00.03 /usr/libexec/getty std.38400 ttyd1 shows that a getty is running on the second - serial port ttyd1 and is - using the std.38400 entry in + serial port ttyd1 and is + using the std.38400 entry in /etc/gettytab. If no getty process is @@ -18005,9 +17966,8 @@ watch for messages while the kernel is booting, or use the /sbin/dmesg command to replay the kernel's boot messages. In particular, look for messages that - start with the characters sio. Hint: - to view just the messages that have the word sio, use the command: + start with the characters sio. Hint: + to view just the messages that have the word sio, use the command: @@ -18067,7 +18027,7 @@ changed between versions. - port "IO_COM1" is a + port "IO_COM1" is a substitution for port 0x3f8, IO_COM2 is 0x2f8, IO_COM3 is 0x3e8, and @@ -18237,8 +18197,7 @@ You will need to setup an entry in /etc/gettytab to give getty information about the speeds you wish to use for your modem. If you have a 2400 bps modem, you - can probably use the existing D2400 entry. This entry already exists + can probably use the existing D2400 entry. This entry already exists in the FreeBSD 1.1.5.1 gettytab file, so you do not need to add it unless it is missing under your version of FreeBSD: @@ -18272,8 +18231,7 @@ On FreeBSD 1.1.5 and later, this will result in 8-bit, no - parity connections. Under FreeBSD 1.1, add :np: parameters to the :np: parameters to the std.xxx entries at the top of the file for 8 bits, no parity; otherwise, the default is 7 bits, even parity. @@ -18342,29 +18300,27 @@ The first item in the above line is the device special file - for this entry - ttyd0 means + for this entry - ttyd0 means /dev/ttyd0 is the file that this getty will be watching. The second item, "/usr/libexec/getty xxx" (xxx will be replaced by the initial gettytab capability) is the process init will run on the - device. The third item, dialup, - is the default terminal type. The fourth parameter, on, indicates to dialup, + is the default terminal type. The fourth parameter, on, indicates to init that the line is operational. There - can be a fifth parameter, secure, + can be a fifth parameter, secure, but it should only be used for terminals which are physically secure (such as the system console). - The default terminal type (dialup in the example above) may depend on - local preferences. dialup is the + The default terminal type (dialup in the example above) may depend on + local preferences. dialup is the traditional default terminal type on dialup lines so that users may customize their login scripts to notice when the terminal is - dialup and automatically adjust + dialup and automatically adjust their terminal type. However, the author finds it easier at his - site to specify vt102 as the + site to specify vt102 as the default terminal type, since the users just use VT102 emulation on their remote systems. @@ -18402,7 +18358,7 @@ If your modem is locked at a different data rate, substitute the appropriate name for the std.speed - entry for std.19200 from + entry for std.19200 from /etc/gettytab for your modem's data rate. @@ -18417,8 +18373,7 @@ /etc/gettytab. For example, if you added the above suggested entry for a matching-speed modem that starts at 19.2 Kbps (the gettytab entry containing the V19200 starting point), your gettytab entry containing the V19200 starting point), your ttys entry might look like this: @@ -18872,9 +18827,9 @@ /usr/src/usr.bin/tip/tip Obviously you need the source distribution to do this. - Edit the line #define HAYES - 0 to #define HAYES - 1. Then make and + Edit the line #define HAYES + 0 to #define HAYES + 1. Then make and make install. Everything works nicely after that. @@ -18902,7 +18857,7 @@ Or use cu as root with the following command: cu -lline -sspeed with line being the serial port (e.g./dev/cuaa0) and speed being - the speed (e.g.57600). When you are + the speed (e.g.57600). When you are done entering the AT commands hit ~. to exit. @@ -18946,10 +18901,10 @@ Do I have to type in the bps rate every time I do that? - Put in an entry for tip1200 or - cu1200, but go ahead and use + Put in an entry for tip1200 or + cu1200, but go ahead and use whatever bps rate is appropriate with the br capability. tip thinks a good default is 1200 bps which - is why it looks for a tip1200 + is why it looks for a tip1200 entry. You do not have to use 1200 bps, though. @@ -19631,7 +19586,7 @@ circumstances, but the above example will almost always work. If it fails, you may be able to defeat some broken ppp implementations by supplying an additional - 0.0.0.0 argument: + 0.0.0.0 argument: @@ -19881,10 +19836,10 @@ Note the indenting is important. - The default: section is + The default: section is loaded for each session. For each dialup line enabled in /etc/ttys create an entry similar to the - one for ttyd0: above. Each line + one for ttyd0: above. Each line should get a unique IP from your pool of ip address for dynamic users. @@ -21034,11 +20989,9 @@ which sliplogin attached itself (slip interface 0, in the above example, which was the first parameter in the list given to slip.login) - to set the local IP address (dc-slip), remote IP address (sl-helmer), network mask for the SLIP + to set the local IP address (dc-slip), remote IP address (sl-helmer), network mask for the SLIP interface (0xfffffc00), and any additional - flags (autocomp). If something + flags (autocomp). If something goes wrong, sliplogin usually logs good informational messages via the daemon syslog facility, which usually goes into /var/log/messages @@ -21080,8 +21033,7 @@ The sl0 and sl1 interfaces shown in netstat -i's output indicate that there are two SLIP interfaces built into the kernel. (The asterisks after - the sl0 and sl1 indicate that the interfaces are + the sl0 and sl1 indicate that the interfaces are down.) However, FreeBSD's default kernels do not come configured to @@ -21196,22 +21148,22 @@ - normal - no header + normal - no header compression - compress - compress + compress - compress headers - autocomp - compress + autocomp - compress headers if the remote end allows it - noicmp - disable ICMP + noicmp - disable ICMP packets (so any ping packets will be dropped instead of using up your bandwidth) @@ -21470,7 +21422,7 @@ certainly turn off the tracing options if gated works OK for you. You will need to change the xxx.xxx.yy's into the network address of your own SLIP subnet (be sure to change the - net mask in the proto direct + net mask in the proto direct clause as well). When you get gated built and @@ -21563,8 +21515,7 @@ cover in the next section) and the localhost route. The interface (Netif column) - that it specifies to use for localhost is localhost is lo0, also known as the loopback device. This says to keep all traffic for this destination internal, rather than sending it out over the LAN, since it will only end up back @@ -21575,7 +21526,7 @@ (test0 in the example) on the local ethernet and add a route for that host, directly to it over the ethernet interface, ed0. There is - also a timeout (Expire column) + also a timeout (Expire column) associated with this type of route, which is used if we fail to hear from the host in a specific amount of time. In this case the route will be automatically deleted. These hosts are identified @@ -21587,8 +21538,7 @@ (10.20.30.255 is the broadcast address for the subnet 10.20.30, and foobar.com is the domain name - associated with that subnet). The designation link#1 refers to the first ethernet card in + associated with that subnet). The designation link#1 refers to the first ethernet card in the machine. You will notice no additional interface is specified for those. @@ -21598,29 +21548,26 @@ only routes which are statically defined (ie. entered explicitly) will exist. - The host1 line refers to our + The host1 line refers to our host, which it knows by ethernet address. Since we are the sending host, FreeBSD knows to use the loopback interface (lo0) rather than sending it out over the ethernet interface. - The two host2 lines are an + The two host2 lines are an example of what happens when we use an ifconfig alias (see the section of ethernet for reasons why we would do this). The - => symbol after the lo0 interface says that not only are we + => symbol after the lo0 interface says that not only are we using the loopback (since this is address also refers to the local host), but specifically it is an alias. Such routes only show up on the host that supports the alias; all other hosts on the local - network will simply have a link#1 + network will simply have a link#1 line for such. - The final line (destination subnet 224) deals with MultiCasting, which will be + The final line (destination subnet 224) deals with MultiCasting, which will be covered in a another section. - The other column that we should talk about are the Flags. Each route has different attributes + The other column that we should talk about are the Flags. Each route has different attributes that are described in the column. Below is a short table of some of these flags and their meanings: @@ -21702,8 +21649,7 @@ If all known paths fail, the system has one last option: the default route. This route is a special type of gateway route (usually the only one present in the - system), and is always marked with a c in the flags field. For hosts on a + system), and is always marked with a c in the flags field. For hosts on a local area network, this gateway is set to whatever machine has a direct connection to the outside world (whether via PPP link, or your hardware device attached to a dedicated data line). @@ -22875,12 +22821,12 @@ As a good workaround, you can place the line - search foo.bar.edu - bar.edu + search foo.bar.edu + bar.edu instead of the previous - domain foo.bar.edu + domain foo.bar.edu into your /etc/resolv.conf. However, make sure that the search order does not go beyond the boundary @@ -23480,8 +23426,8 @@ future, this will be the only place where announcements concerning the operations of the CTM system will be posted. Send an email to &a.majordomo; with a single - line of subscribe - ctm-announce to get added to the list. + line of subscribe + ctm-announce to get added to the list. @@ -24392,10 +24338,7 @@ collections are reflected by the use of indentation in the list below. - The most commonly used collections are src-all, cvs-crypto, and ports-all. The other collections are used + The most commonly used collections are src-all, cvs-crypto, and ports-all. The other collections are used only by small groups of people for specialized purposes, and some mirror sites may not carry all of them. @@ -25087,8 +25030,8 @@ Contributed by &a.nik;. Once you have synchronised your local source tree against a - particular version of FreeBSD (stable, - current and so on) you must then use + particular version of FreeBSD (stable, + current and so on) you must then use the source tree to rebuild the system. Currently, the best source of information on how to do that is a @@ -25732,7 +25675,7 @@ After filing a report, you should receive confirmation along with a tracking number. Keep this tracking number so that you can update us with details about the problem by sending mail to bug-followup@FreeBSD.ORG. Use the number as the message subject, e.g. "Re: kern/3377". Additional information for any bug report should be submitted this way. + URL="mailto:bug-followup@FreeBSD.ORG">bug-followup@FreeBSD.ORG. Use the number as the message subject, e.g. "Re: kern/3377". Additional information for any bug report should be submitted this way. If you do not receive confirmation in a timely fashion (3 days to a week, depending on your email connection) or are, for some @@ -25873,8 +25816,7 @@ To place a BSD-style copyright on your work, include the following text at the very beginning of every source code file you - wish to protect, replacing the text between the %% with the appropriate information. + wish to protect, replacing the text between the %% with the appropriate information. Copyright (c) %%proper_years_here%% %%your_name_here%%, %%your_state%% %%your_zip%%. All rights reserved. @@ -25940,7 +25882,7 @@ Only a fraction of the overridable variables - (${..}) are mentioned in + (${..}) are mentioned in this document. Most (if not all) are documented at the start of bsd.port.mk. This file uses a non-standard tab setting. Emacs and @@ -26034,7 +25976,7 @@ __FreeBSD__ is defined in all versions of FreeBSD. Use it if the change you are making ONLY affects FreeBSD. Porting gotchas like the use of - sys_errlist[] vs + sys_errlist[] vs strerror() are Berkeleyisms, not FreeBSD changes. @@ -26042,8 +25984,8 @@ In FreeBSD 2.x, __FreeBSD__ is - defined to be 2. In earlier - versions, it is 1. Later + defined to be 2. In earlier + versions, it is 1. Later versions will bump it to match their major version number. @@ -26055,8 +25997,8 @@ described above. If there actually is a FreeBSD specific change (such as special shared library options when using ld) then it is OK to use - __FreeBSD__ and #if - __FreeBSD__ > 1 to detect a FreeBSD 2.x + __FreeBSD__ and #if + __FreeBSD__ > 1 to detect a FreeBSD 2.x and later system. If you need more granularity in detecting FreeBSD systems since 2.0-RELEASE you can use the following: @@ -26156,7 +26098,7 @@ See if you can figure it out. Do not worry about the - contents of the $Id$ + contents of the $Id$ line, it will be filled in automatically by CVS when the port is imported to our main ports tree. You can find a more detailed example in the - If the port uses XmClientLibs in its Imakefile, + If the port uses XmClientLibs in its Imakefile, change it to ${MOTIFLIB} ${XTOOLLIB} ${XLIB}. @@ -30611,7 +30552,7 @@ People familiar with the C language will immediately recognize that everything could be counted as a config option where there - is at least a single #ifdef + is at least a single #ifdef referencing it... However, it's unlikely that many people would put @@ -30634,8 +30575,7 @@ The old-style option mechanism still has one advantage for local options or maybe experimental options that have a short anticipated - lifetime: since it is easy to add a new #ifdef to the kernel source, this has already + lifetime: since it is easy to add a new #ifdef to the kernel source, this has already made it a kernel config option. In this case, the administrator using such an option is responsible himself for knowing about its implications (and maybe manually forcing the recompilation of parts @@ -30688,8 +30628,7 @@ #include "opt_foo.h" - on top, before all the #include <xxx.h> stuff. This sequence + on top, before all the #include <xxx.h> stuff. This sequence is most important as the options could override defaults from the regular include files, if the defaults are of the form @@ -30728,8 +30667,8 @@ on a crash dump. They assume that you have enough swap space for a crash dump. If you have multiple swap partitions and the first one is too small to hold the dump, you can configure your kernel to use - an alternate dump device (in the config - kernel line), or you can specify an alternate using the + an alternate dump device (in the config + kernel line), or you can specify an alternate using the dumpon8 command. Dumps to non-swap devices, tapes for example, are currently not supported. Config your kernel using config -g. See However, it obviously points to garbage, so we have found our error! (For those unfamiliar with that particular - piece of code: tp->t_line + piece of code: tp->t_line refers to the line discipline of the console device here, which must be a rather small integer number.) @@ -30997,8 +30936,8 @@ Ctrl-Alt-ESC. For syscons, this can be remapped; some of the distributed maps do this, so watch out. There is an option available for serial consoles that allows the use of a serial line BREAK on - the console line to enter DDB (options - BREAK_TO_DEBUGGER in the kernel config file). It is + the console line to enter DDB (options + BREAK_TO_DEBUGGER in the kernel config file). It is not the default since there are a lot of crappy serial adapters around that gratuitously generate a BREAK condition, for example when pulling the cable. @@ -34265,19 +34204,16 @@ The following CVSup site is especially designed for users. Unlike the other CVSup mirrors, - it is kept up-to-date by CTM. That means if you CVSup cvs-all with release=cvs + it is kept up-to-date by CTM. That means if you CVSup cvs-all with release=cvs from this site, you get a version of the repository (including the inevitable .ctm_status file) which is - suitable for being updated using the CTM cvs-cur deltas. This allows users who track - the entire cvs-all tree to go from + suitable for being updated using the CTM cvs-cur deltas. This allows users who track + the entire cvs-all tree to go from CVSup to CTM without having to rebuild their repository from scratch using a fresh CTM base delta. - This special feature only works for the cvs-all distribution with + This special feature only works for the cvs-all distribution with cvs as the release tag. CVSupping any other distribution and/or release will get you the specified distribution, but it will not be suitable for CTM updating.