old-www/LDP/nag/footnode.html

3933 lines
27 KiB
HTML

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<!--Converted with LaTeX2HTML 96.1-c (Feb 29, 1996) by Nikos Drakos (nikos@cbl.leeds.ac.uk), CBLU, University of Leeds -->
<HTML>
<HEAD>
<TITLE>Footnotes</TITLE>
</HEAD>
<BODY LANG="EN">
<DL> <DT><A NAME="157">...distributed.</A><DD>
The copyright notice is reproduced on the page immediately following
the title page.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="245">...herself?</A><DD>
Note that while you are allowed to print out the online version, you
may <em>not</em> run the O'Reilly book through a photocopier, and much
less sell any of those (hypothetical) copies.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="246">...Dawson</A><DD>
Terry Dawson can be reached at terryd@extro.ucc.su.oz.au.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="247">...fun</A><DD>
Don't you think we could do it with sed, Vince?
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="255">...match.</A><DD>
The original spirit of which (see above) still shows on some
occasions in Europe.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="268">...bugfixes.</A><DD>
Not that the times had changed that much...
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="416">...swim:</A><DD>
When using bash, the GNU Bourne Again Shell, you might have to
escape the exclamation mark, because it uses it as its history
character.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="523">...links.</A><DD>
SLIP is described in RFC-1055. The header compression CSLIP is based
in is described in RFC-1144.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="744">...Tridgell.</A><DD>
NetBIOS is the protocol on which applications like lanmanager
and Windows for Workgroups are based.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="747">...directory?</A><DD>
We will come back to this in chapter-<A HREF="node124.html#appl"><IMG ALIGN=BOTTOM ALT="gif" SRC="cross_ref_motif.gif"></A>.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="748">...alike.</A><DD>
There have been commercial you have to pay lots of money for
that came with a setuid-root shell script which allowed users to
gain root privilege using a simple standard trick.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="749">...consequences.</A><DD>
In 1988, the RTM worm brought much of the Internet to a grinding halt,
partly by exploiting a gaping hole in some sendmail programs.
This hole has long been fixed since.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="684">...tripwire</A><DD>
Written by Gene Kim and Gene Spafford.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="891">...NIC.</A><DD>
Frequently, IP-addresses will be assigned to you by the provider you
buy your IP-connectivity from. However, you may also apply to
NIC directly for an IP address for your network by sending a mail to
hostmaster@internic.net.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="877">...versa.</A><DD>
Autonomous systems are slightly more general, however. They may comprise
more than one IP-network.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="1305">...daemon.</A><DD>
routed is considered broken by many people. Since gated
supports RIP as well, it is better to use that instead.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="1590">...directly.</A><DD>
If it didn't, then DNS would be about as bad as any other method,
because each query would involve the root name servers.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="1748">...domain.</A><DD>
Well, almost. A name server at least has to provide name service
for localhost and reverse lookups of 127.0.0.1.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="1905">...IRQ.</A><DD>
IRQs 2 and 9 are the same because the PC has two cascaded interrupt
processors with eight IRQs each; the secondary processor is connected
to IRQ-2 of the primary one.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="1973">...links.</A><DD>
This is to avoid fragmentation by links that have a very small
maximum packet size.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="2215">...Gortmaker.</A><DD>
Paul can be reached at gpg109@rsphysse.anu.edu.au.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="2220">...telnet.</A><DD>
NCSA telnet is a popular program for DOS that runs TCP/IP
over Ethernet or PLIP, and supports telnet and FTP.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="2395">...Hankins,</A><DD>
To be reached at gregh@cc.gatech.edu.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="2360">...NSC-16550A</A><DD>
There was also a NSC-16550, but it's FIFO never really worked.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="2589">...each.</A><DD>
The last number on each subnet is reserved as the broadcast address,
so it's in fact 63 hosts per subnet.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="3165">...used.</A><DD>
You will need the address of any NIS servers only if you use Peter
Eriksson's NYS. Other NIS implementations locate their servers at
run-time only by using ypbind.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="3166">...this:</A><DD>
Note that names in networks must not collide with hostnames
from the hosts file, else some programs may produce strange
results.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="2695">...device</A><DD>
Anyone remember Pink Floyd's ``Echoes''?
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="3175">...operation.</A><DD>
For instance, all applications based on RPC use the loopback interface
to register themselves with the portmapper daemon at startup.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="3180">...commands:</A><DD>
Note that pointopoint is not a typo. It's really
spelt like this.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="2854">...191.72.1.1.</A><DD>
Just as a matter of caution, you should however configure a PLIP or
SLIP link only after you have completely set up the routing table
entries for your Ethernets. With some older kernels, your network
route might otherwise end up pointing at the point-to-point link.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="3193">...vbardolino.</A><DD>
You can tell whether a connection is outgoing or not from the port
numbers involved. The port number shown for the <em>calling</em> host
will always be a simple integer, while on the host being called, a
well-known service port will be in use, for which netstat uses
the symbolic name found in /etc/services.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="3689">...queries.</A><DD>
There are various named binaries floating around FTP
sites, each configured a little differently. Some have their pid file
in /etc, some store it in /tmp or /var/tmp.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="3691">...HREF="node87.html#resolvfignamedboot"><IMG ALIGN=BOTTOM ALT="gif" SRC="cross_ref_motif.gif"></A>.</A><DD>
Note that the domain names in this example are given <em>without</em>
trailing dot. Earlier versions of named seem to treat trailing
dots in named.boot as an error, and silently discards the
line. BIND-4.9.3 is said to fix this.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="3697">...chapter.</A><DD>
Note that you can't query your name server for the root servers if
you don't have any root server hints installed: Catch-22! To escape
this dilemma, you can either make nslookup use a different name
server, or you can use the sample file in
figure-<A HREF="node89.html#resolvfignamedcache"><IMG ALIGN=BOTTOM ALT="gif" SRC="cross_ref_motif.gif"></A> as a starting point, and then
obtain the full list of valid servers.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="3743">...IP-packets.</A><DD>
Van Jacobson header compression is described in RFC-1441.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="4006">...for.</A><DD>
dip means <em>Dialup IP</em>. It was written by Fred van-Kempen.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="4007">...root.</A><DD>
diplogin can (and must) be run setuid, too. See the section
at the end of this chapter.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="4009">.../etc/dip.pid:</A><DD>
See the newsgroup alt.tla for more palindromic fun with
three-letter acronyms.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="4068">...RFCs.</A><DD>
The relevant RFCs are listed in the Annoted Bibiliography at the end
of this book.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="4071">...HDLC,</A><DD>
In fact, HDLC is a much more general protocol devised by the
International Standards Organization (ISO).
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="4539">...Longyear.</A><DD>
Both authors have said they will be very busy for some time to come.
If you have any questions on PPP in general, you'd best ask the people
on the NET channel of the activists mailing list.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="4540">...Fox.</A><DD>
karl@morningstar.com.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="4149">...option.</A><DD>
The default network route is only installed if none is present yet.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="4546">...facility.</A><DD>
If you edit syslog.conf to redirect these log messages to
a file, make sure this file isn't world readable, as chat
also logs the entire chat script by default-- including passwords
and all.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="4282">...hostnames.</A><DD>
Using hostnames in this option has consequences on CHAP
authentication. Please refer to the section on CHAP below.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="4549">...established.</A><DD>
You can allow the peer PPP to override your ideas of IP addresses by
giving pppd the ipcp-accept-local and
ipcp-accept-remote options. Please refer to the manual page
for details.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="4424">...vlager:</A><DD>
The double quotes are not part of the password, they merely serve to
protect the white space within the password.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="4434">...c3po.lucas.com,</A><DD>
This hostname is taken from the CHAP challenge.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="4869">...tcpd,</A><DD>
Written by Wietse Venema, wietse@wzv.win.tue.nl.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="4871">...dot.</A><DD>
Usually only local host names obtained from lookups in /etc/hosts
contain no dots.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="4806">...ignored.</A><DD>
In an NFS environment, you may need to give it a protection of 444,
because the super user is often very restricted in accessing files on
disks mounted via NFS.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="4898">...hosts.equiv</A><DD>
Note that the hosts.equiv file is <em>not</em>
searched when someone attempts to log in as root.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="5317">...Th&#252;mmler.</A><DD>
To be reached at swen@uni-paderborn.de. The NIS clients are
available as <TT>yp-linux.tar.gz</TT> from sunsite.unc.edu in
system/Network.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="5318">...yps.</A><DD>
The current version (as of this writing) is <TT>yps-0.21</TT> and can
be obtained from ftp.lysator.liu.se in the /pub/NYS
directory.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="5320">...Eriksson,</A><DD>
To be reached at pen@lysator.liu.se.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="5321">...files.</A><DD>
DBM is a simple database management library that uses hashing
techniques to speed up search operations. There's a free DBM
implementation from the GNU project called gdbm, which is
part of most distributions.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="5348">...problem.</A><DD>
The source for yp-linux can be gotten from
ftp.uni-paderborn.de in directory /pub/Linux/LOCAL.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="5585">...Sladkey,</A><DD>
Rick can be reached at jrs@world.std.com.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="5586">...vale:</A><DD>
Note that you can omit the -t nfs argument, because
mount sees from the colon that this specifies an NFS
volume.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="5405">...someday.</A><DD>
The problem with write-behind is that the kernel buffer cache is indexed
by device/inode pairs, and therefore can't be used for NFS-mounted
file systems.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="5410">...circumstances.</A><DD>
As explained to me by Alan Cox:
The NFS specification requires the server to flush each write to disk
before it returns an acknowledgement. As BSD kernels are only capable
of page-sized writes (4K), writing a 4 chunks of 1K each to a BSD-based
NFS server results in 4 write operations of 4K each.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="5430">...volumes</A><DD>
One doesn't say file system, because these are not proper file systems.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="5622">...UUCP-1.04,</A><DD>
Written and copyrighted by Ian Taylor, 1993.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="5806">...600.</A><DD>
Note that although most UUCP commands must be setuid to uucp,
you must make sure the uuchk program is <em>not</em>. Otherwise,
users will be able to display passwords even though they have mode
600.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="6604">...machine.</A><DD>
If you're just going to try out UUCP, get the number of an archive
site near you. Write down the login and password-- they're public to
make anonymous downloads possible. In most cases, they're something
like uucp/uucp or nuucp/uucp.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="5965">...standards.</A><DD>
The only limitation is that it shouldn't be longer than 7-characters,
so as to not confuse hosts with filesystems that impose a narrow limit
on file names.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="5970">...name.</A><DD>
The UUCP Mapping Project registers all UUCP hostnames world-wide and
makes sure they are unique. To register your UUCP name, ask the
maintainers of the site that handles your mail; they will be able to
help you with it.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="6011">...on.</A><DD>
Older Version 2 UUCP's don't broadcast their name when being called;
however, newer implementations often do, and so does Taylor UUCP.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="6030">...set.</A><DD>
The Baud rate of the tty must be at least as high as the maximum
transfer speed.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="6127">...request.</A><DD>
If the remote system runs Taylor UUCP, it will obey.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="6612">.../dev/cua1.</A><DD>
Some people use the ttyS* devices instead, which are intended
for dial-in only.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="6197">...mode.</A><DD>
You can also configure some modems to reset themselves when
detecting a transition on DTR. Some of them, however, don't
seem to like this, and occasionally get hung.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="6617">...rnews:</A><DD>
rsmtp is used to deliver mail with batched SMTP. This is
described in the mail chapters.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="6623">.../etc/inetd.conf:</A><DD>
Note that usually, tcpd has mode 700, so that you must
invoke it as user root, not uucp as you would
usually do.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="6626">...option.</A><DD>
The -u option is present in 1.04, too, but is only a no-op.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="6627">...4096.</A><DD>
Most binaries included in distributions default to a window
size of 7 and 128 byte packets.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="6629">...files</A><DD>
That is, files whose name begins with a dot. Such files aren't
normally displayed by the ls command.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="7158">...line.</A><DD>
It is customary to append a <em>signature</em> or .sig to a mail
message, usually containing information on the author, along with a
joke or a motto. It is offset from the mail message by a line
containing ``- ''.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="6870">...space.</A><DD>
This is because disk space is usually allocated in blocks of 1024 Bytes.
So even a message of at most 400 Bytes will eat a full KB.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="7189">...host::user.</A><DD>
When trying to reach a DECnet address from an RFC-822 environment, you
may use &quot;host::user&quot;@relay, where relay
is the name of a known Internet-DECnet relay.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="7166">...Usenet.</A><DD>
Maps for sites registered with The UUCP Mapping Project are distributed
through the newsgroup comp.mail.maps; other organizations may
publish separate maps for their network.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="7174">...world-wide.</A><DD>
They are posted regularly in news.lists.ps-maps. Beware. They're
HUGE.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="7779">.../usr/sbin/sendmail.</A><DD>
This is the new standard location of sendmail according to the
File System Standard. Another common location is /usr/lib.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="7786">...instead.</A><DD>
The reason is this: Assume your hostname is monad, but is not
registered in the maps. However, there is a site in the maps called
monad, so every mail to monad!root, even sent from
a direct UUCP neighbor of yours, will wind up on the other
monad. This is a nuisance for everybody.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="7423">...consolation.</A><DD>
Don't use this if you're in a really bad mood.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="7801">...FTP.</A><DD>
If you bought this with a distribution from a vendor, you are
entitled to the source code ``for a nominal shipping charge'',
according to smail's copying conditions.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="7815">...distribution,</A><DD>
The default configuration files can be found in samples/generic
below the source directory.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="7845">...connections.</A><DD>
The authors call this support ``simple''. For a future version of
smail, they advertise a complete backend which will handle this
more efficiently.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="7744">...path.</A><DD>
However, the use of routes in the Internet is discouraged altogether.
Fully qualified domain names should be used instead.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="8405">...program</A><DD>
deliver was written by Chip Salzenberg (chip%tct@ateng.com).
It is part of several distributions and can be found in the
usual anonymous FTP archives such as ftp.uu.net.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="8518">...value.</A><DD>
The format of Usenet news messages is specified in RFC-1036,
``Standard for interchange of USENET messages''.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="8634">...day.</A><DD>
Wait a moment: 60-Megs at 9600-bps, that's 60 million by 1200,
that is...mutter, mutter,...Hey! That's 34-hours!
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="8654">...<em>batching</em>.</A><DD>
The golden rule of netnews, according to Geoff Collyer: ``Thou shalt
batch thine articles.''
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="8658">...NNTP.</A><DD>
Described in RFC-977.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="8673">...resource,</A><DD>
Some people claim that Usenet is a conspiracy by modem and hard disk
vendors.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="8835">...group.</A><DD>
There may be a difference between the groups that exist at your site,
and those that your site is willing to receive. For example, the
subscription list may specify comp.all, which means all
newsgroups below the comp hierarchy, but at your site, only a
number of comp groups are listed in active. articles
posted to those groups will be moved to junk.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="8837">...entry,</A><DD>
Note that this should be the crontab of news, in order not
to mangle file permissions.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="9513">...own.</A><DD>
If you don't care about the number of spool files (because
you're the only person using your computer, and you don't
write articles by the megabyte), you may replace the script's
contents by a simple exit 0 statement.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="9515">...batch.</A><DD>
As shipped with C-News, compcun uses compress with the
12-bit option, since this is the least common denominator for most
sites. You may produce a copy of it, say compcun16,
where you use 16-bit compression. The improvement is not too
impressive, though.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="9518">...doexpire.</A><DD>
In older versions of C News, this was done by a script called
upact.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="9288">...expiration.</A><DD>
The article's date of arrival is kept in the middle field of the
history line, given in seconds since January-1, 1970.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="9520">...them.</A><DD>
I don't know <em>why</em> this happens, but for me, it does from time
to time.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="9363">...newsmaster,</A><DD>
There's a funny typo in RFC-1036 (p.12):
``Implementors and administrators may choose to allow control
messages to be carried out automatically, or to queue them for annual
processing.''
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="9429">...network.</A><DD>
I wouldn't try this on the Internet, either.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="9623">...Standard.</A><DD>
Formally specified in RFC-977.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="9767">...information.</A><DD>
When posting an article over NNTP, the server always adds at least one
header field, which is Nntp-Posting-Host:. It contains the
client's host name.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="9633">...faking</em>.</A><DD>
The same problem exists with SMTP, the Simple Mail Transfer Protocol.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="9802">...tass.</A><DD>
Written by Rich Skrenta.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="9805">...minutes.</A><DD>
Things improve drastically if the NNTP
server does the threading itself, and lets the client retrieve the
threads databases; INN-1.4 does this, for instance.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="9930">...account.</A><DD>
However, do <em>not</em> use nobody for this. As a rule, no files
or commands whatsoever should be associated with this user.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="9931">...it.</A><DD>
This is the reason why you will get ugly error messages when invoking
it as super user. But then, you shouldn't work as root, anyway.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="9936">...removed.</A><DD>
Note that C-news doesn't update this low water mark automatically;
you have to run updatemin to do so. Please refer to
chapter-<A HREF="node259.html#cnews"><IMG ALIGN=BOTTOM ALT="gif" SRC="cross_ref_motif.gif"></A>.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE><DT><A NAME="9940">...appear.</A><DD>
This is because their order has to agree with that of the entries in the
(binary) MASTER file.
<P>
<PRE>.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
</PRE> </DL>
<P><ADDRESS>
<I>Andrew Anderson <BR>
Thu Mar 7 23:22:06 EST 1996</I>
</ADDRESS>
</BODY>
</HTML>