Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site eagle.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!eagle!mjs
From: mjs@eagle.UUCP (M.J.Shannon)
Newsgroups: net.bugs.uucp
Subject: Re: System V introduces yet another inconsistency
Message-ID: <1242@eagle.UUCP>
Date: Thu, 28-Feb-85 21:34:35 EST
Article-I.D.: eagle.1242
Posted: Thu Feb 28 21:34:35 1985
Date-Received: Fri, 1-Mar-85 09:44:53 EST
References: <454@lsuc.UUCP>
Organization: AT&T Bell Laboratories, Summit, NJ
Lines: 25

> In other words,    uucp file site!~uucp/file     works.
> 
> Dave Sherman

In all the documentation, the claim has been made that the proper way of saying
what you meant is:

	uucp file site!~/file

Many machines (and many more as time goes on and people realize the need for
security) use different logins for each uucp neighbor.  The code that comes
from AT&T correctly deals with this by special casing the particular idiom
"~/file" as meaning "file in the uucppublic directory, whatever it may be
called at the destination site".  The fact that your usage may work on some
machines is simply an indication that login name uucp has /usr/spool/uucppublic
as its home directory on those machines.

Simply because you have come to depend on a "feature" that (to my knowledge)
has never been documented, you may not claim that System V has introduced an
inconsistency.  The moral of the story is that if you don't play by the letter
of the rules, you'll eventually get bitten.
-- 
	Marty Shannon
UUCP:	ihnp4!eagle!mjs
Phone:	+1 201 522 6063