Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/17/84 chuqui version 1.7 9/23/84; site daisy.UUCP
Path: utzoo!utcs!lsuc!pesnta!hplabs!nsc!daisy!david
From: david@daisy.UUCP (David Schachter)
Newsgroups: net.lan
Subject: Re: Transparent Remote File Access Systems: Short Summary
Message-ID: <54@daisy.UUCP>
Date: Wed, 20-Feb-85 22:47:34 EST
Article-I.D.: daisy.54
Posted: Wed Feb 20 22:47:34 1985
Date-Received: Wed, 27-Feb-85 09:19:19 EST
References: <257@oblio.UUCP>
Reply-To: david@daisy.UUCP (David Schachter)
Organization: Daisy Systems Corp., Mountain View, Ca
Lines: 20
Summary: 


Daisy Systems was not listed in the summary.  Our network support is based
on Ethernet, conforming to XNS (pretty strictly, our troika of LAN gurus
tells me.)  To refer to a local file, you use a standard Unix-style path-
name:

     "ls /usr/david"

To refer to a remote file on some other Ethernet node, you still use a 
standard Unix-style pathname prefixed with the node name:

     "ls /net/david/usr/david"

The "/net" tells the name server where to go, it pulls the ".../david..."
out as a node name and sends the ".../usr/david" off to the remote node
named "david".  The "/net" is not fixed, it is merely the default: local
installations can change it to valid Unix-style filename.  Ditto for node
names, I think.

Can't get usefully more transparent....