Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.unix.wizards
Subject: Re: //host vs "mount point"
Message-ID: <6759@brl-smoke.ARPA>
Date: Sun, 29-Nov-87 03:08:26 EST
Article-I.D.: brl-smok.6759
Posted: Sun Nov 29 03:08:26 1987
Date-Received: Tue, 1-Dec-87 04:56:47 EST
References: <648@tut.cis.ohio-state.edu> <1668@tut.cis.ohio-state.edu> <12122@think.UUCP> <38c15248.4580@hi-csc.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) )
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 21

In article <38c15248.4580@hi-csc.UUCP> giebelhaus@hi-csc.UUCP (Timothy R. Giebelhaus) writes:
>I like the // mount because it places my machine at the same level as
>all the rest of the machines on the network.

The main problem with the // scheme is that it is not sufficiently
general.  "grep -i gwyn /n/ucbvax/n/monet/etc/passwd" should work,
but I doubt that "grep -i gwyn //ucbvax//monet/etc/passwd" would,
given the already-existing rule about stripping out redundant
embedded adjacent /s.  One would have to change that rule also.

>I put the name of the machine in the name server (ns) and then all machines
>can access it.

There is no reason that /n could not be a name-server file system.

>NFS seems to be implementing file locking which I believe means it is no
>longer a stateless protocol.

Fundamentally, NFS remains stateless.  Last I heard, the locking was
being done by arrangement with external daemons.  (It is actually record
locking, in support of SVID requirements, not just whole-file locking.)