Peter:
perhaps I was not clear... the share from carbon is /carbon/disk1 &
/carbon/disk5
ie)
#carbon:/etc/exports
/carbon/disk1 -access=rsgroup,32bitclients
/carbon/disk5 -access=rsgroup,32bitclients
I want the structure to remain the same on local machines so I create the
mount point as carbon in auto.master and point it as below...
> > #auto.carbon
> > #key mount-options location
> > disk1 -rw,exec,dev,soft,intr,nosuid,vers=2 carbon:/carbon/&
> > disk5 -rw,exec,dev,soft,intr,nosuid,vers=2 carbon:/carbon/&
I don't want to see the contents of the external mounts! In the same way that
the /carbon appears on the root's structure from the auto.master file, why
shouldn't I see the disk1 and disk5 under it from the auto.carbon file. I
don't want it to mount until I cd to it, or use it somehow. Isn't it just a
matter of making a /carbon/disk1 /carbon/disk5 mount points that are then
mounted if required?
I mean I could, I suppose, make a /.automount /etc/auto.automount
-nosuid,rw,intr
and then mkdir /carbon and ln -s /.automount/disk1 /carbon/disk1 etc.....
but it seems that an automount program could do this easily..... am I missing
something?
> This is not supported. It would be fairly easy to support readdir()
> (except that you would have to enumerate the map, which is an expensive
> operation.) The problem is that 99% of all programs which do readdir()
> do stat(), which would cause a mount to be performed. The solution is
> something called "inode spoofing", which is a huge mess to support.
>
> -hpa
--
Brock Murch
[EMAIL PROTECTED]
University of South Florida
Remote Sensing Laboratory
System Administrator / Programmer
X-Band Manager
