Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!zephyr!tektronix!percival!parsely!sopwith!snoopy
From: snoopy@sopwith.UUCP (Snoopy)
Newsgroups: comp.unix.wizards
Subject: Re: What kinds of things would you want in the GNU OS?
Keywords: GNU OS features kernel fun!
Message-ID: <209@sopwith.UUCP>
Date: 4 Jun 89 18:13:47 GMT
References: <106326@sun.Eng.Sun.COM> <4315@ficc.uu.net> <338@arc.UUCP> <7439@bsu-cs.bsu.edu> <1989May26.224924.5293@eci386.uucp>
Reply-To: snoopy@sopwith.UUCP (Snoopy)
Organization: The Daisy Hill Puppy Farm
Lines: 30

In article <1989May26.224924.5293@eci386.uucp> woods@eci386.UUCP (Greg Woods) writes:

| Second, a leading '//' with a special meaning is a tremendous KLUDGE!
| It's even worse than "machine_A:/"!

Nope, sorry, // is a small kludge, and machine_A:/ is the tremendous kludge.
Your syntax attaches special to another character.  With the // syntax,
the special chars remain limited to / and null.

|I HOPE to see future distributed filesystems become (remain :-)
|completely transparent ala RFS.  You should be able to mount any
|(advertised) directory from any machine on the network anywhere
|into your local filesystem hierarchy.

Why do you want to have to mount somebody else's filesystem on your
system just to be able to access it?  It's already mounted on their
system.  All you need is a way to get to it.

One additional requirement I forgot to list in my previous article
is that remote devices must be as transparent as regular files.
Some inferior network filesystems break the "a file is a file is a file"
rule.

    _____     						  .-----.
   /_____\    Snoopy					./  RIP	 \.
  /_______\   qiclab!sopwith!snoopy			|  	  |
    |___|     parsely!sopwith!snoopy			| tekecs  |
    |___|     sun!nosun!illian!sopwith!snoopy		|_________|

		"I *am* the next man!"  -Indy