From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <4a4d7a917c90dae841515d955887cc94@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] A proposal regarding # in bind
From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
In-Reply-To: <200302262126.h1QLQYO23923@fine1008.math.princeton.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Thu, 27 Feb 2003 09:29:59 +0100
Topicbox-Message-UUID: 7405e0fe-eacb-11e9-9e20-41e7f4b1d025

> In some sense # has to be a special case.  The / hierarchy is (potentially)
> different for each process.  The # hierarchy is not.  You need a global
> namespace from which to choose what to include in a local namespace.  At least

This suggests that we could just keep a separate (per machine)
namespace with all devices attached on it.  You could mount it,
then bind whatever you want from there to
"/ur", then unmount /n/devs if you dont want that to be there.

This would require also a change in devices like #| that build
resources on attach.

But after all the discussion, I just think that keeping '#' is the
simplest answer.