From mboxrd@z Thu Jan  1 00:00:00 1970
To: 9fans@cse.psu.edu
From: "Thomas Bushnell, BSG" <tb+usenet@becket.net>
Message-ID: <87pu6tvzqe.fsf@becket.becket.net>
Content-Type: text/plain; charset=us-ascii
References: <20011108130611.4DD15199BB@mail.cse.psu.edu>
Subject: Re: [9fans] Plan 9
Date: Fri,  9 Nov 2001 10:08:26 +0000
Topicbox-Message-UUID: 1c06155a-eaca-11e9-9e20-41e7f4b1d025

rob@plan9.bell-labs.com (rob pike) writes:

> > 1) The same tools should work on all file names, however set up, to
> >    create them, remove them, rename them, and so forth.
> > 2) Whether a file name mapping is per-user or not should be decoupled
> >    from what the user sees.
>
> I guess I'm dim. I can't see how either of these properties is unmet by
> Plan 9.

For number 1), the issue is decoupling different kinds of sharing from
the tools that set them up.

Depending on exactly what kind of sharing I want in doing a bind, I
can type a shell command, edit a per-user config file or edit a system
config file.

There are very different tools to set up these different kinds of
sharing.

For number 2), suppose I want to set up a file that is visible in my
name space, but not in other peoples'.  How do I do that?

Those aren't the only cases, but they are the most immediately clear,
I think.