diff --git a/en/handbook/README b/en/handbook/README index cf002e533d..849cdb4f4c 100644 --- a/en/handbook/README +++ b/en/handbook/README @@ -263,3 +263,17 @@ for example, 18. Yet more things that should be filenames marked up as such. + 19. Use the new element to mark up hostnames, IP addresses and + such. The markup choice is as follows. + + ... is a simple hostname. + ... is an IP address. + ... is a domain name. + ... is a fully qualified domain name. + ... is a netmask. + ... is a network card MAC address. + + These might migrate to being separate elements in the future. However, + if they do then changing the markup can be done automatically. + + diff --git a/en/handbook/handbook.sgml b/en/handbook/handbook.sgml index 43c2c91dce..b209b60d73 100644 --- a/en/handbook/handbook.sgml +++ b/en/handbook/handbook.sgml @@ -4333,8 +4333,7 @@ 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 + localhost (a.k.a. 127.0.0.1) it will come back at you through this pseudo-device. Mandatory. @@ -5695,7 +5694,7 @@ kinit, see above) access to rlogin to jane's account or files on this system - (grunt) via rlogin, rsh or + (grunt) via rlogin, rsh or rcp. For example, Jane now logs into another system, using @@ -7530,13 +7529,13 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4: In this example, the first printer is named - rattan and has as aliases + rattan and has as aliases line, diablo, lp, and Diablo 630 Line Printer. Since it has the alias lp, it is also the default printer. The - second is named bamboo, and has + second is named bamboo, and has as aliases ps, , S, panasonic, and rattan and bamboo: + rattan and bamboo: mkdir /var/spool/lpd mkdir /var/spool/lpd/rattan mkdir /var/spool/lpd/bamboo @@ -7663,9 +7661,8 @@ /etc/printcap file using the lp capability. - In our running example, let us assume that rattan is on the first parallel port, - and bamboo is on a sixth serial + In our running example, let us assume that rattan is on the first parallel port, + and bamboo is on a sixth serial port; here are the additions to /etc/printcap: @@ -8082,8 +8079,7 @@ /etc/printcap from a host called orchid. It has a single printer attached to its first parallel port, a Hewlett Packard - LaserJet 3Si named teak. It is using the + LaserJet 3Si named teak. It is using the above script as its text filter: # # /etc/printcap for host @@ -8197,8 +8193,7 @@ (lf) capability to the entry for the printer you are debugging in the /etc/printcap file. For example, - here is the entry for rattan, with the rattan, with the lf capability: rattan|line|diablo|lp|Diablo 630 Line @@ -8304,8 +8299,7 @@ lpr -P printer-name filename... This example prints a long listing of the - current directory to the printer named rattan: + current directory to the printer named rattan: ls -l | lpr -P rattan Because no files were listed for the lpq -P bamboo - shows the queue for the printer named bamboo. Here is an example of the output of + shows the queue for the printer named bamboo. Here is an example of the output of the lpq command: bamboo is ready and printing Rank Owner Job Files @@ -8353,7 +8346,7 @@ input) 1635 bytes 3rd mary 11 ... 78519 bytes This shows three jobs in the queue for - bamboo. The first job, submitted by + bamboo. The first job, submitted by user kelly, got assigned job number 9. Every job for a printer gets a unique job number. Most of the time you can ignore the job number, but you will need it if you want to @@ -8421,8 +8414,7 @@ job-number To remove the job from a specific printer, add the option. The following command removes job - number 10 from the queue for the printer bamboo: + number 10 from the queue for the printer bamboo: lprm -P bamboo 10 The Just use the option with the above shortcuts to operate on a specific printer instead of the default. For example, the following command removes all jobs for the - current user in the queue for the printer named rattan: + current user in the queue for the printer named rattan: @@ -8521,7 +8512,7 @@ For example, the following command prints a DVI file (from the TeX typesetting system) named fish-report.dvi to the printer named - bamboo: + bamboo: lpr -P bamboo -d fish-report.dvi These options apply to every file in the job, @@ -9588,11 +9579,10 @@ /etc/printcap. In our example, we will add the DVI conversion filter to - the entry for the printer named bamboo. Here is the example + the entry for the printer named bamboo. Here is the example /etc/printcap file again, with the new df capability for the printer - bamboo + bamboo # # /etc/printcap for host rose - added df filter for bamboo # rattan|line|diablo|lp|Diablo 630 Line @@ -9656,7 +9646,7 @@ The following script is a conversion filter for troff data from the groff typesetting system for the PostScript printer - named bamboo: + named bamboo: #!/bin/sh # # pstf - Convert groff's troff data into PS, then print. # Installed in @@ -9680,23 +9670,21 @@ Here is an example that might make old hands at FORTRAN blush. It is a FORTRAN-text filter for any printer that can directly print plain text. We will install it for the printer - teak: + teak: #!/bin/sh # # hprf - FORTRAN text filter for LaserJet 3si: # Installed in /usr/local/libexec/hprf # printf "\033&k2G" && fpr && printf "\f" && exit 0 exit 2 And we will add this line to the - /etc/printcap for the printer teak to enable this filter: + /etc/printcap for the printer teak to enable this filter: :rf=/usr/local/libexec/hprf: Here is one final, somewhat complex example. We will add - a DVI filter to the LaserJet printer teak introduced earlier. First, the + a DVI filter to the LaserJet printer teak introduced earlier. First, the easy part: updating /etc/printcap with the location of the DVI filter: @@ -9968,7 +9956,7 @@ remap="Output Filters"> for more information. Here is an example /etc/printcap file - for the printer teak that we + for the printer teak that we introduced earlier; we enabled header pages and added the above output filter: @@ -9977,8 +9965,7 @@ :lp=/dev/lpt0:sd=/var/spool/lpd/teak:mx#0:\ :if=/usr/local/libexec/hpif:\ :vf=/usr/local/libexec/hpvf:\ :of=/usr/local/libexec/hpof: - Now, when users print jobs to teak, they get a header page with each + Now, when users print jobs to teak, they get a header page with each job. If users want to spend time searching for their printouts, they can suppress header pages by submitting the job with lpr -h; see /etc/printcap file. Here is an example. The host rose has two printers, - bamboo and rattan. We will enable users on the host + bamboo and rattan. We will enable users on the host orchid to print to those printers. Here is the /etc/printcap file for orchid (back from section ). It already had the entry for - the printer teak; we have added + the printer teak; we have added entries for the two printers on the host rose: # # /etc/printcap for host orchid - added @@ -10383,17 +10369,14 @@ - Now, users on orchid can print to rattan and bamboo. If, for example, a user on orchid + Now, users on orchid can print to rattan and bamboo. If, for example, a user on orchid typed lpr -P bamboo -d sushi-review.dvi the LPD system on orchid would copy the job to the spooling directory /var/spool/lpd/bamboo and note that it was - a DVI job. As soon as the host rose has room in its bamboo spooling directory, the two LPDs + a DVI job. As soon as the host rose has room in its bamboo spooling directory, the two LPDs would transfer the file to rose. The file would wait in rose's queue until it was finally printed. It would be converted from DVI to PostScript (since bamboo is a PostScript printer) on @@ -10508,9 +10491,8 @@ Here is an example. This is the /etc/printcap file for the host rose. The - printer rattan is quite hearty, so - we will allow multiple copies, but the laser printer bamboo's a bit more delicate, so we will + printer rattan is quite hearty, so + we will allow multiple copies, but the laser printer bamboo's a bit more delicate, so we will disable multiple copies by adding the sc capability: @@ -10526,8 +10508,7 @@ Now, we also need to add the sc capability on the host orchid's /etc/printcap (and while we are at it, let - us disable multiple copies for the printer teak): + us disable multiple copies for the printer teak): # # /etc/printcap for host orchid - no multiple copies for local # printer teak or remote printer @@ -10579,10 +10560,8 @@ ). - For example, we will let anyone access the printer rattan, but only those in group artists can use bamboo. Here is the familiar + For example, we will let anyone access the printer rattan, but only those in group artists can use bamboo. Here is the familiar /etc/printcap for host rose: # # /etc/printcap for host rose - restricted @@ -10596,8 +10575,7 @@ :df=/usr/local/libexec/psdf: Let us leave the other example /etc/printcap file (for the host orchid) - alone. Of course, anyone on orchid can print to bamboo. It might be the case that we only + alone. Of course, anyone on orchid can print to bamboo. It might be the case that we only allow certain logins on orchid anyway, and want them to have access to the printer. Or not. @@ -10634,9 +10612,7 @@ discarded. Whether this is correct behavior is up for debate. - Let us add limits to our example printers rattan and bamboo. Since those artists' PostScript + Let us add limits to our example printers rattan and bamboo. Since those artists' PostScript files tend to be large, we will limit them to five megabytes. We will put no limit on the plain text line printer: @@ -10726,10 +10702,9 @@ For example, let us add a minfree file for the printer - bamboo. We examine + bamboo. We examine /etc/printcap to find the spooling - directory for this printer; here is bamboo's entry: + directory for this printer; here is bamboo's entry: bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ @@ -19387,14 +19362,14 @@ - The first line defines the alias ``localhost'' as a synonym + The first line defines the alias localhost as a synonym for the current machine. Regardless of your own IP address, the - IP address for this line should always be 127.0.0.1. The second - line maps the name ``foo.bar.com'' (and the shorthand ``foo'') - to the IP address 10.0.0.1. + IP address for this line should always be 127.0.0.1. The second + line maps the name foo.bar.com (and the shorthand foo) + to the IP address 10.0.0.1. If your provider allocates you a static IP address and name, - then use these in place of the 10.0.0.1 entry. + then use these in place of the 10.0.0.1 entry. @@ -19591,7 +19566,7 @@ replaced by the IP address that your ISP indicated for their gateway (the machine to which you connect). If your ISP hasn't given you a gateway address, use - 10.0.0.2/0. If you need + 10.0.0.2/0. If you need to use a guessed address, make sure that you create an entry in /etc/ppp/ppp.linkup as per the instructions for @@ -19683,10 +19658,10 @@ - This tells ppp to negotiate using address 0.0.0.0 rather than 10.0.0.1. Do not use 0.0.0.0/0 as the first argument + This tells ppp to negotiate using address 0.0.0.0 rather than 10.0.0.1. Do not use 0.0.0.0/0 as the first argument to set ifaddr as it prevents ppp from setting up an initial route in and @@ -19952,8 +19927,8 @@ The file /etc/ppp/ppp.linkup should also contain routing information for each static IP user if - required. The line below would add a route for the 203.14.101.0 class C via the client's + required. The line below would add a route for the 203.14.101.0 class C via the client's ppp link. @@ -21353,8 +21328,7 @@ asks to speak to the SLIP client's IP address. When using the example above, be sure to replace the - Ethernet MAC address (00:11:22:33:44:55) with the MAC address of + Ethernet MAC address (00:11:22:33:44:55) with the MAC address of your system's Ethernet card, or your proxy ARP will definitely not work! You can discover your SLIP server's Ethernet MAC address by looking at the results of running @@ -21370,7 +21344,7 @@ which indicates that this particular system's Ethernet MAC - address is 00:02:c1:28:5f:4a -- + address is 00:02:c1:28:5f:4a -- the periods in the Ethernet MAC address given by netstat -i must be changed to colons and leading zeros should be added to each single-digit hexadecimal @@ -21604,8 +21578,7 @@ The first two lines specify the default route (which we will - cover in the next section) and the localhost route. + cover in the next section) and the localhost route. The interface (Netif column) that it specifies to use for - The next thing that stands out are the 0:e0:... addresses. These are ethernet + The next thing that stands out are the 0:e0:... addresses. These are ethernet hardware addresses. FreeBSD will automatically identify any hosts (test0 in the example) on the local ethernet and add a route for that host, directly to it over the @@ -21630,9 +21602,9 @@ determination. FreeBSD will also add subnet routes for the local subnet - (10.20.30.255 is the broadcast - address for the subnet 10.20.30, and - foobar.com is the domain name + (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 the machine. You will notice no additional interface is specified @@ -21767,8 +21739,7 @@ - The hosts Local1 and Local2 are at your site, with the formed + The hosts Local1 and Local2 are at your site, with the formed being your PPP connection to your ISP's Terminal Server. Your ISP has a local network at their site, which has, among other things, the server where you connect and a hardware device (T1-GW) @@ -21795,11 +21766,11 @@ the T1-GW machine, so there is no need for the intermediate step of sending traffic to the ISP server. - As a final note, it is common to use the address ...1 as the gateway address for your local + As a final note, it is common to use the address ...1 as the gateway address for your local network. So (using the same example), if your local class-C - address space was 10.20.30 and your - ISP was using 10.9.9 then the + address space was 10.20.30 and your + ISP was using 10.9.9 then the default routes would be: @@ -22610,10 +22581,10 @@ - Run a name server ( man -k named ) and have your own domain - smallminingco.com + smallminingco.com - Get mail delivered to the current DNS name for your host. - Ie: dorm6.ahouse.school.edu + Ie: dorm6.ahouse.school.edu No matter what option you choose, to have mail delivered directly to your host, you must be a full Internet host. You must @@ -22682,8 +22653,8 @@ To setup up a network mailhost, you need to direct the mail from arriving at all the workstations. In other words, you want to - hijack all mail for *.smallminingco.com - and divert it to one machine, your mailhost. + hijack all mail for *.smallminingco.com + and divert it to one machine, your mailhost. The network users on their workstations will most likely pick up their mail over POP or telnet. @@ -22900,22 +22871,23 @@ Why do I have to use the FQDN for hosts on my site? You will probably find that the host is actually in a - different domain; for example, if you are in foo.bar.edu and you - wish to reach a host called ``mumble'' in the bar.edu domain, you + different domain; for example, if you are in foo.bar.edu and you + wish to reach a host called mumble in the bar.edu domain, you will have to refer to it by the fully-qualified domain name, - ``mumble.bar.edu'', instead of just ``mumble''. + mumble.bar.edu, instead of just mumble. Traditionally, this was allowed by BSD BIND resolvers. However the current version of BIND that ships with FreeBSD no longer provides default abbreviations for non-fully qualified domain names other than the domain you are in. So an - unqualified host mumble must either - be found as mumble.foo.bar.edu, or + unqualified host mumble must either + be found as mumble.foo.bar.edu, or it will be searched for in the root domain. This is different from the previous behavior, where the search - continued across mumble.bar.edu, - and mumble.edu. Have a look at + continued across mumble.bar.edu, + and mumble.edu. Have a look at RFC 1535 for why this was considered bad practice, or even a security hole. diff --git a/en_US.ISO8859-1/books/handbook/book.sgml b/en_US.ISO8859-1/books/handbook/book.sgml index 43c2c91dce..b209b60d73 100644 --- a/en_US.ISO8859-1/books/handbook/book.sgml +++ b/en_US.ISO8859-1/books/handbook/book.sgml @@ -4333,8 +4333,7 @@ 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 + localhost (a.k.a. 127.0.0.1) it will come back at you through this pseudo-device. Mandatory. @@ -5695,7 +5694,7 @@ kinit, see above) access to rlogin to jane's account or files on this system - (grunt) via rlogin, rsh or + (grunt) via rlogin, rsh or rcp. For example, Jane now logs into another system, using @@ -7530,13 +7529,13 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4: In this example, the first printer is named - rattan and has as aliases + rattan and has as aliases line, diablo, lp, and Diablo 630 Line Printer. Since it has the alias lp, it is also the default printer. The - second is named bamboo, and has + second is named bamboo, and has as aliases ps, , S, panasonic, and rattan and bamboo: + rattan and bamboo: mkdir /var/spool/lpd mkdir /var/spool/lpd/rattan mkdir /var/spool/lpd/bamboo @@ -7663,9 +7661,8 @@ /etc/printcap file using the lp capability. - In our running example, let us assume that rattan is on the first parallel port, - and bamboo is on a sixth serial + In our running example, let us assume that rattan is on the first parallel port, + and bamboo is on a sixth serial port; here are the additions to /etc/printcap: @@ -8082,8 +8079,7 @@ /etc/printcap from a host called orchid. It has a single printer attached to its first parallel port, a Hewlett Packard - LaserJet 3Si named teak. It is using the + LaserJet 3Si named teak. It is using the above script as its text filter: # # /etc/printcap for host @@ -8197,8 +8193,7 @@ (lf) capability to the entry for the printer you are debugging in the /etc/printcap file. For example, - here is the entry for rattan, with the rattan, with the lf capability: rattan|line|diablo|lp|Diablo 630 Line @@ -8304,8 +8299,7 @@ lpr -P printer-name filename... This example prints a long listing of the - current directory to the printer named rattan: + current directory to the printer named rattan: ls -l | lpr -P rattan Because no files were listed for the lpq -P bamboo - shows the queue for the printer named bamboo. Here is an example of the output of + shows the queue for the printer named bamboo. Here is an example of the output of the lpq command: bamboo is ready and printing Rank Owner Job Files @@ -8353,7 +8346,7 @@ input) 1635 bytes 3rd mary 11 ... 78519 bytes This shows three jobs in the queue for - bamboo. The first job, submitted by + bamboo. The first job, submitted by user kelly, got assigned job number 9. Every job for a printer gets a unique job number. Most of the time you can ignore the job number, but you will need it if you want to @@ -8421,8 +8414,7 @@ job-number To remove the job from a specific printer, add the option. The following command removes job - number 10 from the queue for the printer bamboo: + number 10 from the queue for the printer bamboo: lprm -P bamboo 10 The Just use the option with the above shortcuts to operate on a specific printer instead of the default. For example, the following command removes all jobs for the - current user in the queue for the printer named rattan: + current user in the queue for the printer named rattan: @@ -8521,7 +8512,7 @@ For example, the following command prints a DVI file (from the TeX typesetting system) named fish-report.dvi to the printer named - bamboo: + bamboo: lpr -P bamboo -d fish-report.dvi These options apply to every file in the job, @@ -9588,11 +9579,10 @@ /etc/printcap. In our example, we will add the DVI conversion filter to - the entry for the printer named bamboo. Here is the example + the entry for the printer named bamboo. Here is the example /etc/printcap file again, with the new df capability for the printer - bamboo + bamboo # # /etc/printcap for host rose - added df filter for bamboo # rattan|line|diablo|lp|Diablo 630 Line @@ -9656,7 +9646,7 @@ The following script is a conversion filter for troff data from the groff typesetting system for the PostScript printer - named bamboo: + named bamboo: #!/bin/sh # # pstf - Convert groff's troff data into PS, then print. # Installed in @@ -9680,23 +9670,21 @@ Here is an example that might make old hands at FORTRAN blush. It is a FORTRAN-text filter for any printer that can directly print plain text. We will install it for the printer - teak: + teak: #!/bin/sh # # hprf - FORTRAN text filter for LaserJet 3si: # Installed in /usr/local/libexec/hprf # printf "\033&k2G" && fpr && printf "\f" && exit 0 exit 2 And we will add this line to the - /etc/printcap for the printer teak to enable this filter: + /etc/printcap for the printer teak to enable this filter: :rf=/usr/local/libexec/hprf: Here is one final, somewhat complex example. We will add - a DVI filter to the LaserJet printer teak introduced earlier. First, the + a DVI filter to the LaserJet printer teak introduced earlier. First, the easy part: updating /etc/printcap with the location of the DVI filter: @@ -9968,7 +9956,7 @@ remap="Output Filters"> for more information. Here is an example /etc/printcap file - for the printer teak that we + for the printer teak that we introduced earlier; we enabled header pages and added the above output filter: @@ -9977,8 +9965,7 @@ :lp=/dev/lpt0:sd=/var/spool/lpd/teak:mx#0:\ :if=/usr/local/libexec/hpif:\ :vf=/usr/local/libexec/hpvf:\ :of=/usr/local/libexec/hpof: - Now, when users print jobs to teak, they get a header page with each + Now, when users print jobs to teak, they get a header page with each job. If users want to spend time searching for their printouts, they can suppress header pages by submitting the job with lpr -h; see /etc/printcap file. Here is an example. The host rose has two printers, - bamboo and rattan. We will enable users on the host + bamboo and rattan. We will enable users on the host orchid to print to those printers. Here is the /etc/printcap file for orchid (back from section ). It already had the entry for - the printer teak; we have added + the printer teak; we have added entries for the two printers on the host rose: # # /etc/printcap for host orchid - added @@ -10383,17 +10369,14 @@ - Now, users on orchid can print to rattan and bamboo. If, for example, a user on orchid + Now, users on orchid can print to rattan and bamboo. If, for example, a user on orchid typed lpr -P bamboo -d sushi-review.dvi the LPD system on orchid would copy the job to the spooling directory /var/spool/lpd/bamboo and note that it was - a DVI job. As soon as the host rose has room in its bamboo spooling directory, the two LPDs + a DVI job. As soon as the host rose has room in its bamboo spooling directory, the two LPDs would transfer the file to rose. The file would wait in rose's queue until it was finally printed. It would be converted from DVI to PostScript (since bamboo is a PostScript printer) on @@ -10508,9 +10491,8 @@ Here is an example. This is the /etc/printcap file for the host rose. The - printer rattan is quite hearty, so - we will allow multiple copies, but the laser printer bamboo's a bit more delicate, so we will + printer rattan is quite hearty, so + we will allow multiple copies, but the laser printer bamboo's a bit more delicate, so we will disable multiple copies by adding the sc capability: @@ -10526,8 +10508,7 @@ Now, we also need to add the sc capability on the host orchid's /etc/printcap (and while we are at it, let - us disable multiple copies for the printer teak): + us disable multiple copies for the printer teak): # # /etc/printcap for host orchid - no multiple copies for local # printer teak or remote printer @@ -10579,10 +10560,8 @@ ). - For example, we will let anyone access the printer rattan, but only those in group artists can use bamboo. Here is the familiar + For example, we will let anyone access the printer rattan, but only those in group artists can use bamboo. Here is the familiar /etc/printcap for host rose: # # /etc/printcap for host rose - restricted @@ -10596,8 +10575,7 @@ :df=/usr/local/libexec/psdf: Let us leave the other example /etc/printcap file (for the host orchid) - alone. Of course, anyone on orchid can print to bamboo. It might be the case that we only + alone. Of course, anyone on orchid can print to bamboo. It might be the case that we only allow certain logins on orchid anyway, and want them to have access to the printer. Or not. @@ -10634,9 +10612,7 @@ discarded. Whether this is correct behavior is up for debate. - Let us add limits to our example printers rattan and bamboo. Since those artists' PostScript + Let us add limits to our example printers rattan and bamboo. Since those artists' PostScript files tend to be large, we will limit them to five megabytes. We will put no limit on the plain text line printer: @@ -10726,10 +10702,9 @@ For example, let us add a minfree file for the printer - bamboo. We examine + bamboo. We examine /etc/printcap to find the spooling - directory for this printer; here is bamboo's entry: + directory for this printer; here is bamboo's entry: bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ @@ -19387,14 +19362,14 @@ - The first line defines the alias ``localhost'' as a synonym + The first line defines the alias localhost as a synonym for the current machine. Regardless of your own IP address, the - IP address for this line should always be 127.0.0.1. The second - line maps the name ``foo.bar.com'' (and the shorthand ``foo'') - to the IP address 10.0.0.1. + IP address for this line should always be 127.0.0.1. The second + line maps the name foo.bar.com (and the shorthand foo) + to the IP address 10.0.0.1. If your provider allocates you a static IP address and name, - then use these in place of the 10.0.0.1 entry. + then use these in place of the 10.0.0.1 entry. @@ -19591,7 +19566,7 @@ replaced by the IP address that your ISP indicated for their gateway (the machine to which you connect). If your ISP hasn't given you a gateway address, use - 10.0.0.2/0. If you need + 10.0.0.2/0. If you need to use a guessed address, make sure that you create an entry in /etc/ppp/ppp.linkup as per the instructions for @@ -19683,10 +19658,10 @@ - This tells ppp to negotiate using address 0.0.0.0 rather than 10.0.0.1. Do not use 0.0.0.0/0 as the first argument + This tells ppp to negotiate using address 0.0.0.0 rather than 10.0.0.1. Do not use 0.0.0.0/0 as the first argument to set ifaddr as it prevents ppp from setting up an initial route in and @@ -19952,8 +19927,8 @@ The file /etc/ppp/ppp.linkup should also contain routing information for each static IP user if - required. The line below would add a route for the 203.14.101.0 class C via the client's + required. The line below would add a route for the 203.14.101.0 class C via the client's ppp link. @@ -21353,8 +21328,7 @@ asks to speak to the SLIP client's IP address. When using the example above, be sure to replace the - Ethernet MAC address (00:11:22:33:44:55) with the MAC address of + Ethernet MAC address (00:11:22:33:44:55) with the MAC address of your system's Ethernet card, or your proxy ARP will definitely not work! You can discover your SLIP server's Ethernet MAC address by looking at the results of running @@ -21370,7 +21344,7 @@ which indicates that this particular system's Ethernet MAC - address is 00:02:c1:28:5f:4a -- + address is 00:02:c1:28:5f:4a -- the periods in the Ethernet MAC address given by netstat -i must be changed to colons and leading zeros should be added to each single-digit hexadecimal @@ -21604,8 +21578,7 @@ The first two lines specify the default route (which we will - cover in the next section) and the localhost route. + cover in the next section) and the localhost route. The interface (Netif column) that it specifies to use for - The next thing that stands out are the 0:e0:... addresses. These are ethernet + The next thing that stands out are the 0:e0:... addresses. These are ethernet hardware addresses. FreeBSD will automatically identify any hosts (test0 in the example) on the local ethernet and add a route for that host, directly to it over the @@ -21630,9 +21602,9 @@ determination. FreeBSD will also add subnet routes for the local subnet - (10.20.30.255 is the broadcast - address for the subnet 10.20.30, and - foobar.com is the domain name + (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 the machine. You will notice no additional interface is specified @@ -21767,8 +21739,7 @@ - The hosts Local1 and Local2 are at your site, with the formed + The hosts Local1 and Local2 are at your site, with the formed being your PPP connection to your ISP's Terminal Server. Your ISP has a local network at their site, which has, among other things, the server where you connect and a hardware device (T1-GW) @@ -21795,11 +21766,11 @@ the T1-GW machine, so there is no need for the intermediate step of sending traffic to the ISP server. - As a final note, it is common to use the address ...1 as the gateway address for your local + As a final note, it is common to use the address ...1 as the gateway address for your local network. So (using the same example), if your local class-C - address space was 10.20.30 and your - ISP was using 10.9.9 then the + address space was 10.20.30 and your + ISP was using 10.9.9 then the default routes would be: @@ -22610,10 +22581,10 @@ - Run a name server ( man -k named ) and have your own domain - smallminingco.com + smallminingco.com - Get mail delivered to the current DNS name for your host. - Ie: dorm6.ahouse.school.edu + Ie: dorm6.ahouse.school.edu No matter what option you choose, to have mail delivered directly to your host, you must be a full Internet host. You must @@ -22682,8 +22653,8 @@ To setup up a network mailhost, you need to direct the mail from arriving at all the workstations. In other words, you want to - hijack all mail for *.smallminingco.com - and divert it to one machine, your mailhost. + hijack all mail for *.smallminingco.com + and divert it to one machine, your mailhost. The network users on their workstations will most likely pick up their mail over POP or telnet. @@ -22900,22 +22871,23 @@ Why do I have to use the FQDN for hosts on my site? You will probably find that the host is actually in a - different domain; for example, if you are in foo.bar.edu and you - wish to reach a host called ``mumble'' in the bar.edu domain, you + different domain; for example, if you are in foo.bar.edu and you + wish to reach a host called mumble in the bar.edu domain, you will have to refer to it by the fully-qualified domain name, - ``mumble.bar.edu'', instead of just ``mumble''. + mumble.bar.edu, instead of just mumble. Traditionally, this was allowed by BSD BIND resolvers. However the current version of BIND that ships with FreeBSD no longer provides default abbreviations for non-fully qualified domain names other than the domain you are in. So an - unqualified host mumble must either - be found as mumble.foo.bar.edu, or + unqualified host mumble must either + be found as mumble.foo.bar.edu, or it will be searched for in the root domain. This is different from the previous behavior, where the search - continued across mumble.bar.edu, - and mumble.edu. Have a look at + continued across mumble.bar.edu, + and mumble.edu. Have a look at RFC 1535 for why this was considered bad practice, or even a security hole. diff --git a/en_US.ISO_8859-1/books/handbook/book.sgml b/en_US.ISO_8859-1/books/handbook/book.sgml index 43c2c91dce..b209b60d73 100644 --- a/en_US.ISO_8859-1/books/handbook/book.sgml +++ b/en_US.ISO_8859-1/books/handbook/book.sgml @@ -4333,8 +4333,7 @@ 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 + localhost (a.k.a. 127.0.0.1) it will come back at you through this pseudo-device. Mandatory. @@ -5695,7 +5694,7 @@ kinit, see above) access to rlogin to jane's account or files on this system - (grunt) via rlogin, rsh or + (grunt) via rlogin, rsh or rcp. For example, Jane now logs into another system, using @@ -7530,13 +7529,13 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4: In this example, the first printer is named - rattan and has as aliases + rattan and has as aliases line, diablo, lp, and Diablo 630 Line Printer. Since it has the alias lp, it is also the default printer. The - second is named bamboo, and has + second is named bamboo, and has as aliases ps, , S, panasonic, and rattan and bamboo: + rattan and bamboo: mkdir /var/spool/lpd mkdir /var/spool/lpd/rattan mkdir /var/spool/lpd/bamboo @@ -7663,9 +7661,8 @@ /etc/printcap file using the lp capability. - In our running example, let us assume that rattan is on the first parallel port, - and bamboo is on a sixth serial + In our running example, let us assume that rattan is on the first parallel port, + and bamboo is on a sixth serial port; here are the additions to /etc/printcap: @@ -8082,8 +8079,7 @@ /etc/printcap from a host called orchid. It has a single printer attached to its first parallel port, a Hewlett Packard - LaserJet 3Si named teak. It is using the + LaserJet 3Si named teak. It is using the above script as its text filter: # # /etc/printcap for host @@ -8197,8 +8193,7 @@ (lf) capability to the entry for the printer you are debugging in the /etc/printcap file. For example, - here is the entry for rattan, with the rattan, with the lf capability: rattan|line|diablo|lp|Diablo 630 Line @@ -8304,8 +8299,7 @@ lpr -P printer-name filename... This example prints a long listing of the - current directory to the printer named rattan: + current directory to the printer named rattan: ls -l | lpr -P rattan Because no files were listed for the lpq -P bamboo - shows the queue for the printer named bamboo. Here is an example of the output of + shows the queue for the printer named bamboo. Here is an example of the output of the lpq command: bamboo is ready and printing Rank Owner Job Files @@ -8353,7 +8346,7 @@ input) 1635 bytes 3rd mary 11 ... 78519 bytes This shows three jobs in the queue for - bamboo. The first job, submitted by + bamboo. The first job, submitted by user kelly, got assigned job number 9. Every job for a printer gets a unique job number. Most of the time you can ignore the job number, but you will need it if you want to @@ -8421,8 +8414,7 @@ job-number To remove the job from a specific printer, add the option. The following command removes job - number 10 from the queue for the printer bamboo: + number 10 from the queue for the printer bamboo: lprm -P bamboo 10 The Just use the option with the above shortcuts to operate on a specific printer instead of the default. For example, the following command removes all jobs for the - current user in the queue for the printer named rattan: + current user in the queue for the printer named rattan: @@ -8521,7 +8512,7 @@ For example, the following command prints a DVI file (from the TeX typesetting system) named fish-report.dvi to the printer named - bamboo: + bamboo: lpr -P bamboo -d fish-report.dvi These options apply to every file in the job, @@ -9588,11 +9579,10 @@ /etc/printcap. In our example, we will add the DVI conversion filter to - the entry for the printer named bamboo. Here is the example + the entry for the printer named bamboo. Here is the example /etc/printcap file again, with the new df capability for the printer - bamboo + bamboo # # /etc/printcap for host rose - added df filter for bamboo # rattan|line|diablo|lp|Diablo 630 Line @@ -9656,7 +9646,7 @@ The following script is a conversion filter for troff data from the groff typesetting system for the PostScript printer - named bamboo: + named bamboo: #!/bin/sh # # pstf - Convert groff's troff data into PS, then print. # Installed in @@ -9680,23 +9670,21 @@ Here is an example that might make old hands at FORTRAN blush. It is a FORTRAN-text filter for any printer that can directly print plain text. We will install it for the printer - teak: + teak: #!/bin/sh # # hprf - FORTRAN text filter for LaserJet 3si: # Installed in /usr/local/libexec/hprf # printf "\033&k2G" && fpr && printf "\f" && exit 0 exit 2 And we will add this line to the - /etc/printcap for the printer teak to enable this filter: + /etc/printcap for the printer teak to enable this filter: :rf=/usr/local/libexec/hprf: Here is one final, somewhat complex example. We will add - a DVI filter to the LaserJet printer teak introduced earlier. First, the + a DVI filter to the LaserJet printer teak introduced earlier. First, the easy part: updating /etc/printcap with the location of the DVI filter: @@ -9968,7 +9956,7 @@ remap="Output Filters"> for more information. Here is an example /etc/printcap file - for the printer teak that we + for the printer teak that we introduced earlier; we enabled header pages and added the above output filter: @@ -9977,8 +9965,7 @@ :lp=/dev/lpt0:sd=/var/spool/lpd/teak:mx#0:\ :if=/usr/local/libexec/hpif:\ :vf=/usr/local/libexec/hpvf:\ :of=/usr/local/libexec/hpof: - Now, when users print jobs to teak, they get a header page with each + Now, when users print jobs to teak, they get a header page with each job. If users want to spend time searching for their printouts, they can suppress header pages by submitting the job with lpr -h; see /etc/printcap file. Here is an example. The host rose has two printers, - bamboo and rattan. We will enable users on the host + bamboo and rattan. We will enable users on the host orchid to print to those printers. Here is the /etc/printcap file for orchid (back from section ). It already had the entry for - the printer teak; we have added + the printer teak; we have added entries for the two printers on the host rose: # # /etc/printcap for host orchid - added @@ -10383,17 +10369,14 @@ - Now, users on orchid can print to rattan and bamboo. If, for example, a user on orchid + Now, users on orchid can print to rattan and bamboo. If, for example, a user on orchid typed lpr -P bamboo -d sushi-review.dvi the LPD system on orchid would copy the job to the spooling directory /var/spool/lpd/bamboo and note that it was - a DVI job. As soon as the host rose has room in its bamboo spooling directory, the two LPDs + a DVI job. As soon as the host rose has room in its bamboo spooling directory, the two LPDs would transfer the file to rose. The file would wait in rose's queue until it was finally printed. It would be converted from DVI to PostScript (since bamboo is a PostScript printer) on @@ -10508,9 +10491,8 @@ Here is an example. This is the /etc/printcap file for the host rose. The - printer rattan is quite hearty, so - we will allow multiple copies, but the laser printer bamboo's a bit more delicate, so we will + printer rattan is quite hearty, so + we will allow multiple copies, but the laser printer bamboo's a bit more delicate, so we will disable multiple copies by adding the sc capability: @@ -10526,8 +10508,7 @@ Now, we also need to add the sc capability on the host orchid's /etc/printcap (and while we are at it, let - us disable multiple copies for the printer teak): + us disable multiple copies for the printer teak): # # /etc/printcap for host orchid - no multiple copies for local # printer teak or remote printer @@ -10579,10 +10560,8 @@ ). - For example, we will let anyone access the printer rattan, but only those in group artists can use bamboo. Here is the familiar + For example, we will let anyone access the printer rattan, but only those in group artists can use bamboo. Here is the familiar /etc/printcap for host rose: # # /etc/printcap for host rose - restricted @@ -10596,8 +10575,7 @@ :df=/usr/local/libexec/psdf: Let us leave the other example /etc/printcap file (for the host orchid) - alone. Of course, anyone on orchid can print to bamboo. It might be the case that we only + alone. Of course, anyone on orchid can print to bamboo. It might be the case that we only allow certain logins on orchid anyway, and want them to have access to the printer. Or not. @@ -10634,9 +10612,7 @@ discarded. Whether this is correct behavior is up for debate. - Let us add limits to our example printers rattan and bamboo. Since those artists' PostScript + Let us add limits to our example printers rattan and bamboo. Since those artists' PostScript files tend to be large, we will limit them to five megabytes. We will put no limit on the plain text line printer: @@ -10726,10 +10702,9 @@ For example, let us add a minfree file for the printer - bamboo. We examine + bamboo. We examine /etc/printcap to find the spooling - directory for this printer; here is bamboo's entry: + directory for this printer; here is bamboo's entry: bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ @@ -19387,14 +19362,14 @@ - The first line defines the alias ``localhost'' as a synonym + The first line defines the alias localhost as a synonym for the current machine. Regardless of your own IP address, the - IP address for this line should always be 127.0.0.1. The second - line maps the name ``foo.bar.com'' (and the shorthand ``foo'') - to the IP address 10.0.0.1. + IP address for this line should always be 127.0.0.1. The second + line maps the name foo.bar.com (and the shorthand foo) + to the IP address 10.0.0.1. If your provider allocates you a static IP address and name, - then use these in place of the 10.0.0.1 entry. + then use these in place of the 10.0.0.1 entry. @@ -19591,7 +19566,7 @@ replaced by the IP address that your ISP indicated for their gateway (the machine to which you connect). If your ISP hasn't given you a gateway address, use - 10.0.0.2/0. If you need + 10.0.0.2/0. If you need to use a guessed address, make sure that you create an entry in /etc/ppp/ppp.linkup as per the instructions for @@ -19683,10 +19658,10 @@ - This tells ppp to negotiate using address 0.0.0.0 rather than 10.0.0.1. Do not use 0.0.0.0/0 as the first argument + This tells ppp to negotiate using address 0.0.0.0 rather than 10.0.0.1. Do not use 0.0.0.0/0 as the first argument to set ifaddr as it prevents ppp from setting up an initial route in and @@ -19952,8 +19927,8 @@ The file /etc/ppp/ppp.linkup should also contain routing information for each static IP user if - required. The line below would add a route for the 203.14.101.0 class C via the client's + required. The line below would add a route for the 203.14.101.0 class C via the client's ppp link. @@ -21353,8 +21328,7 @@ asks to speak to the SLIP client's IP address. When using the example above, be sure to replace the - Ethernet MAC address (00:11:22:33:44:55) with the MAC address of + Ethernet MAC address (00:11:22:33:44:55) with the MAC address of your system's Ethernet card, or your proxy ARP will definitely not work! You can discover your SLIP server's Ethernet MAC address by looking at the results of running @@ -21370,7 +21344,7 @@ which indicates that this particular system's Ethernet MAC - address is 00:02:c1:28:5f:4a -- + address is 00:02:c1:28:5f:4a -- the periods in the Ethernet MAC address given by netstat -i must be changed to colons and leading zeros should be added to each single-digit hexadecimal @@ -21604,8 +21578,7 @@ The first two lines specify the default route (which we will - cover in the next section) and the localhost route. + cover in the next section) and the localhost route. The interface (Netif column) that it specifies to use for - The next thing that stands out are the 0:e0:... addresses. These are ethernet + The next thing that stands out are the 0:e0:... addresses. These are ethernet hardware addresses. FreeBSD will automatically identify any hosts (test0 in the example) on the local ethernet and add a route for that host, directly to it over the @@ -21630,9 +21602,9 @@ determination. FreeBSD will also add subnet routes for the local subnet - (10.20.30.255 is the broadcast - address for the subnet 10.20.30, and - foobar.com is the domain name + (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 the machine. You will notice no additional interface is specified @@ -21767,8 +21739,7 @@ - The hosts Local1 and Local2 are at your site, with the formed + The hosts Local1 and Local2 are at your site, with the formed being your PPP connection to your ISP's Terminal Server. Your ISP has a local network at their site, which has, among other things, the server where you connect and a hardware device (T1-GW) @@ -21795,11 +21766,11 @@ the T1-GW machine, so there is no need for the intermediate step of sending traffic to the ISP server. - As a final note, it is common to use the address ...1 as the gateway address for your local + As a final note, it is common to use the address ...1 as the gateway address for your local network. So (using the same example), if your local class-C - address space was 10.20.30 and your - ISP was using 10.9.9 then the + address space was 10.20.30 and your + ISP was using 10.9.9 then the default routes would be: @@ -22610,10 +22581,10 @@ - Run a name server ( man -k named ) and have your own domain - smallminingco.com + smallminingco.com - Get mail delivered to the current DNS name for your host. - Ie: dorm6.ahouse.school.edu + Ie: dorm6.ahouse.school.edu No matter what option you choose, to have mail delivered directly to your host, you must be a full Internet host. You must @@ -22682,8 +22653,8 @@ To setup up a network mailhost, you need to direct the mail from arriving at all the workstations. In other words, you want to - hijack all mail for *.smallminingco.com - and divert it to one machine, your mailhost. + hijack all mail for *.smallminingco.com + and divert it to one machine, your mailhost. The network users on their workstations will most likely pick up their mail over POP or telnet. @@ -22900,22 +22871,23 @@ Why do I have to use the FQDN for hosts on my site? You will probably find that the host is actually in a - different domain; for example, if you are in foo.bar.edu and you - wish to reach a host called ``mumble'' in the bar.edu domain, you + different domain; for example, if you are in foo.bar.edu and you + wish to reach a host called mumble in the bar.edu domain, you will have to refer to it by the fully-qualified domain name, - ``mumble.bar.edu'', instead of just ``mumble''. + mumble.bar.edu, instead of just mumble. Traditionally, this was allowed by BSD BIND resolvers. However the current version of BIND that ships with FreeBSD no longer provides default abbreviations for non-fully qualified domain names other than the domain you are in. So an - unqualified host mumble must either - be found as mumble.foo.bar.edu, or + unqualified host mumble must either + be found as mumble.foo.bar.edu, or it will be searched for in the root domain. This is different from the previous behavior, where the search - continued across mumble.bar.edu, - and mumble.edu. Have a look at + continued across mumble.bar.edu, + and mumble.edu. Have a look at RFC 1535 for why this was considered bad practice, or even a security hole.