From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <fddf406cfd1897e19d414b993e1f1c33@vitanuova.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] an idea
From: rog@vitanuova.com
In-Reply-To: <6.0.0.22.0.20040426195547.0ae42140@pop.noos.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Mon, 26 Apr 2004 19:16:07 +0100
Topicbox-Message-UUID: 6ebd01f2-eacd-11e9-9e20-41e7f4b1d025

> With /srv/sharp, can these exceptions in 'chan.c:namec()' be treated
> with a file flag ?

i'm not sure that /srv/sharp would be a great idea.  after all, isn't
the idea of this to lose the distinction between user and kernel
devices, and to be able to arrange things arbitrarily for a given
process?

after all, it might be quite reasonable, in some circumstances, to
allow a process access to #S but deny it to #p.

in the scheme i'm thinking of, the exceptions in namec() would
go, along with RFNOMNT.