Path: utzoo!utgpu!attcan!uunet!husc6!psuvax1!rutgers!ucsd!nosc!helios.ee.lbl.gov!lll-tis!lll-winken!lll-crg.llnl.gov!bowles
From: bowles@lll-crg.llnl.gov (Jeff Bowles)
Newsgroups: comp.unix.microport
Subject: Re: More RFS questions: advertising subdirectories
Keywords: national botch packet header
Message-ID: <11237@lll-winken.llnl.gov>
Date: 11 Aug 88 14:38:30 GMT
References: <2411@sugar.uu.net> <2442@sugar.uu.net>
Sender: usenet@lll-winken.llnl.gov
Reply-To: bowles@lll-crg.llnl.gov.UUCP (Jeff Bowles)
Organization: Lawrence Livermore National Laboratory
Lines: 30

In article <2442@sugar.uu.net> karl@sugar.uu.net (Karl Lehenbauer) writes:
>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?

On the main node in my  my two-machine RFS network, I advertise:
	/
	/usr/local
	/usr/local/lib/font
	/usr/lib/tmac
	/usr/src

And... the other machine  mounts [most of] these, with no problems.
The ONLY problem I can see is that if someone on the other machine

mounts lots of these, a "find /" will examine some files more than
once --- "find / -local" gets around this. In backup strategies,
that's a concern.

Go to it! (And let me know if you find out what the "National Packet
Header Botch" means. Gad. I have had it, living without source for
the past year.)

	Jeff