Path: utzoo!mnetor!uunet!mcvax!unido!pcsbst!jh
From: jh@pcsbst.UUCP
Newsgroups: comp.unix.wizards
Subject: Re: //host vs "mount point" - (nf)
Message-ID: <4300009@pcsbst.UUCP>
Date: 28 Nov 87 16:38:00 GMT
References: <9398@tekecs.UUCP>
Lines: 22
Nf-ID: #R:tekecs:-939800:pcsbst:4300009:000:663
Nf-From: pcsbst!jh    Nov 28 17:38:00 1987

I don't like the //a solution either. E.g. I have seen cpio
producing names like //usr/....

We at PCS use mount point for our *transparent* network MUNIX/NET.
These mount points are normally located within a superroot
directory "/.." (which is not linked to "/"). Thus,

	/../remote/etc/passwd

would give you the access to the password file on a remote site.
For name transparency even

	/../local/etc/passwd

is allowed. This is not a mount point but a link.
We do not have difficulties with unexpected shutdowns or crashes
of remotes sites, because once mounted, each site is remounted
automatically if it comes up again.


		Johannes Heuft
		unido!pcsbst!jh