From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: From: Russ Cox To: 9fans@cse.psu.edu Subject: Re: [9fans] an idea Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: Date: Mon, 26 Apr 2004 12:59:10 -0400 Topicbox-Message-UUID: 6e919800-eacd-11e9-9e20-41e7f4b1d025 > These are neat ideas but there is one thing I still like about '#' -- it > distinguishes what for me is non-private stuff from private stuff. I.e. in > my (probably too simplistic) way of thinking, all the '#' stuff in > addition to being devices means 'if bound in a name space, it's common to > all'. If all the # stuff becomes things in /srv we'll lost the distinction no it doesn't. #d. #c/user. etc. i think what you're really getting at is that # always means what you want it to mean and not what your parent process set it up to mean. and yes, there is a tension between really getting the recursion right and being able to do this. but a convention that /srv/sharp was always the root of the name space would be enough. even now, #p doesn't always means the process table. sometimes it means "you're running RFNOMT -- go away."