by Here is Hal Stern's comments on what looks to be your topic/question:
" It's possible to remove the automounter's influence by telling the
automounter to use a null map for that directory:
automountd /tools null "
In your case you want to execute:
$ automoutnd /system null
If you want the article which is one of 3 here it is (Hal knows
automounter):
http://www.sunworld.com/sunworldonline/swol-05-1996/swol-05-sysadmin....
Regards
Frank
> I work in a development environment where there is a
> standard login , standard set of auto and direct mounts controller
> by a local NIS server. One such nfs mount is /system. The problem
> is that /system contains some popular tools but it is also
> a place where HP Openview likes to install some files. Since
> /system is shared ro, I can't install HP OV.
> By the way I have a Sparc Ultra5 running 2.5.1.
> I noticed automountd has a /<mountpoint> -null option
> so I tried to add /system -null but that didn't seem to work.
> I got a bit closer to a solution by removing /system and replacing
> it with a symbolic link. The result was automountd refused to
> mount the nfs filesystem on /system but HP OV was happy.
> So I kludged solution but... not very elegant.
> Does anyone know a better way that does not involve
> access to NIS to remove /system from the common environment/
----
Frank Ober