Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!wb3ffv!ka3ovk!raysnec!shwake
From: shwake@raysnec.UUCP (Ray Shwake)
Newsgroups: comp.sys.apollo
Subject: Re: uuname -l, gethostname etc.
Message-ID: <189@raysnec.UUCP>
Date: 2 Jan 91 20:08:21 GMT
References: <9012271224.AA01013@soda.Berkeley.EDU>
Organization: IRS/CI - Technical Solutions Branch
Lines: 22

glass@SODA.BERKELEY.EDU writes:

>I have a machine with the hostname "soda.berkeley.edu" .  I'm trying
>to set it up so that it can do uucp but it thinks its "uuname -l" is
>"soda.Berkeley.".  The name is bad enough but the trailing dot breaks
>lots of stuff (mainly sendmail).  So how do I convince my machine that
>my uuname is really "soda"?  uuname in and of itself is relatively
>innocuous but uucico seems to have the same confusion.

	Well, soda.berkeley.edu may be your FQDN (fully qualified domain
name), but "uuname -l" should point only to your nodename. (Don't know
where apollo is pulling the name; often it's the kernel, or /etc/sitename,
or ....) Since "soda.Berkeley." comes to 14 characters, I would assume
your system runs an HDB-like UUCP, which recognizes only 14 character
nodenames.

	uuname in and of itself may be innocuous, but what it reveals is
not. If a site spools a request for "soda", and you come in and identify
yourself as "soda.Berkeley.", you will not be given that spooled request.

----------------
uunet!media!ka3ovk!raysnec!shwake			shwake@rsxtech