Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site scgvaxd.UUCP
Path: utzoo!watmath!clyde!bonnie!akgua!sdcsvax!sdcrdcf!trwrb!scgvaxd!kvc
From: kvc@scgvaxd.UUCP (Kevin Carosso)
Newsgroups: net.eunice
Subject: Re: EUNICE, TCP/IP installation problems
Message-ID: <233@scgvaxd.UUCP>
Date: Fri, 2-Nov-84 21:34:48 EST
Article-I.D.: scgvaxd.233
Posted: Fri Nov  2 21:34:48 1984
Date-Received: Tue, 6-Nov-84 04:11:31 EST
References: <>
Reply-To: kvc@scgvaxd.UUCP (Kevin Carosso)
Distribution: net
Organization: Hughes Aircraft Co., El Segundo, CA
Lines: 18
Summary: 


Don't listen to TWG regarding rooted logical names...   Unless there
is something drastically wrong with Eunice, you shouldn't have any
trouble with putting your users one directory down and giving them
a root, I do it all the time.  Unless TWG says that Eunice can't hack
rooted directories, then I wouldn't bother to take their suggestion.

In any case, if they suggested using physical device names in authorize
they are definitely confused.  Even if you move your users out of the
one-level root, do NOT use the device names in the SYSUAF.  Create
a (concealed) logical name for the disk (all our users are on a disk
(actually several disks) called USER:).  If you put a physical name
in there, then you will have to manually change every entry in your
UAF should you ever want to move disks around.  Using the logical
name means you change only the logical name if you move disks around.

	/Kevin Carosso               scgvaxd!kvc
	 Hughes Aircraft Co.