Path: utzoo!utgpu!attcan!uunet!husc6!mailrus!ames!killer!tness7!tness1!sugar!karl
From: karl@sugar.uu.net (Karl Lehenbauer)
Newsgroups: comp.unix.microport
Subject: More RFS questions: advertising subdirectories
Keywords: national botch packet header
Message-ID: <2442@sugar.uu.net>
Date: 11 Aug 88 05:00:16 GMT
References: <2411@sugar.uu.net>
Organization: Sugar Land Unix - Houston, TX
Lines: 24

In article <2411@sugar.uu.net>, I posted some RFS questions.

Jeff Bowles (bowles@lll-crg.llnl.gov), via mail, pointed me at the 'idload'
command, which by setting /usr/nserve/auth.info/uid.rules and gid.rules to:
global
default transparent
...and creating a common password file (not essential) and running idload, 
enabled transparent ownership of files across machines.

We still don't know what 'national botch packet header' means.

I had also asked why it isn't a good idea to create a link of the machine
to / on that machine so there would be filepaths that work for all machines.
Jeff pointed out that this breaks find and can cause other problems.

What I'm wondering about now is, is it OK to advertise a subdirectory of
a resource that's already being advertised?  If so, I can do something
like advertise /usr/spool/news as "news" from the news server, and remote
mount it as /usr/spool/news on the others.  I tilde-banged out just now and 
tried it and it works, so let's put it this way, does anyone know of a reason 
why this should not be done?
-- 
-- 
-- Karl Lehenbauer, karl@sugar.uu.net aka uunet!sugar!karl, +1 713 274 5184