64 lines
2.9 KiB
HTML
64 lines
2.9 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>Site Naming</TITLE>
|
|
</HEAD>
|
|
<BODY LANG="EN">
|
|
<A HREF="node1.html"><IMG WIDTH=65 HEIGHT=24 ALIGN=BOTTOM ALT="contents" SRC="contents_motif.gif"></A> <BR>
|
|
<B> Next:</B> <A HREF="node157.html">Taylor Configuration Files</A>
|
|
<B>Up:</B> <A HREF="node153.html">UUCP Configuration Files</A>
|
|
<B> Previous:</B> <A HREF="node155.html">What UUCP Needs to </A>
|
|
<BR> <P>
|
|
<H2><A NAME="SECTION0014330000">Site Naming</A></H2>
|
|
<P>
|
|
<A NAME="uucpstartingsitename"></A>
|
|
<A NAME="5961"></A>
|
|
<A NAME="5962"></A>
|
|
<A NAME="5963"></A>
|
|
<A NAME="5964"></A>
|
|
<P>
|
|
As with TCP/IP-based networking, your host has to have a name for UUCP
|
|
networking. As long as you simply want to use UUCP for file transfers to
|
|
or from sites you dial up directly, or on a local network, this name
|
|
does not have to meet any standards.<A HREF="footnode.html#5965"><IMG ALIGN=BOTTOM ALT="gif" SRC="foot_motif.gif"></A>
|
|
<P>
|
|
However, if you use UUCP for a mail or news link, you should think about
|
|
having the name registered with the UUCP Mapping project. The UUCP
|
|
Mapping Project is described in chapter-<A HREF="node186.html#mail"><IMG ALIGN=BOTTOM ALT="gif" SRC="cross_ref_motif.gif"></A>. Even if you
|
|
participate in a domain, you might consider having an official UUCP name
|
|
for your site.
|
|
<P>
|
|
Frequently, people choose their UUCP name to match the first component
|
|
of their fully qualified domain name. Suppose your site's domain
|
|
address is swim.twobirds.com, then your UUCP host name would be
|
|
swim. Think of UUCP sites as knowing each other on a
|
|
first-name basis. Of course, you can also use a UUCP name completely
|
|
unrelated to your fully qualified domain name.
|
|
<P>
|
|
<A NAME="5969"></A>
|
|
However, make sure not to use the unqualified site name in mail
|
|
addresses unless you have registered it as your official UUCP
|
|
name.<A HREF="footnode.html#5970"><IMG ALIGN=BOTTOM ALT="gif" SRC="foot_motif.gif"></A> At the very best, mail to an unregistered UUCP host will vanish in
|
|
some big black bit bucket. If you use a name already held by some other
|
|
site, this mail will be routed to that site, and cause its postmaster
|
|
no end of headaches.
|
|
<P>
|
|
By default, the UUCP suite uses the name set by hostname as the
|
|
site's UUCP name. This name is commonly set in the /etc/rc.local
|
|
script. If your UUCP name is different from what you set your host name
|
|
to, you have to use the hostname option in the config
|
|
file to tell uucico about your UUCP name. This is described
|
|
below.
|
|
<P>
|
|
<HR><A HREF="node1.html"><IMG WIDTH=65 HEIGHT=24 ALIGN=BOTTOM ALT="contents" SRC="contents_motif.gif"></A> <BR>
|
|
<B> Next:</B> <A HREF="node157.html">Taylor Configuration Files</A>
|
|
<B>Up:</B> <A HREF="node153.html">UUCP Configuration Files</A>
|
|
<B> Previous:</B> <A HREF="node155.html">What UUCP Needs to </A>
|
|
<P><ADDRESS>
|
|
<I>Andrew Anderson <BR>
|
|
Thu Mar 7 23:22:06 EST 1996</I>
|
|
</ADDRESS>
|
|
</BODY>
|
|
</HTML>
|