From: Martin C.Atkins <martin@mca-ltd.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] A proposal regarding # in bind
Date: Tue, 25 Feb 2003 10:30:08 +0530 [thread overview]
Message-ID: <20030225103008.5ec58473.martin@mca-ltd.com> (raw)
In-Reply-To: <3203694a344338d2aae59b328b9fe67a@vitanuova.com>
On Mon, 24 Feb 2003 19:04:01 0000 rog@vitanuova.com wrote:
>...
>
> a) there's still an escape from the namespace, but a smaller one:
> there could be one (and only one) device nameable in the '#' name
> space, the proto device. (whether one allows an attach spec is a
> matter of taste). that at least would solve some of the naming
> problems.
>
> b) have a special system call for attaching proto.
I was hoping to avoid any visibility from user space of the mechanism
for attaching /proto. (See my reply to Rob's message)
>
> martin:
> > One could have a /proto/ctl file to which commands could be sent to remove
> > (or even add?!) devices from the visibility of this, and inheriting, processes
> > (a sort of fine-grained NODEVS).
>
> this would require that the namespace served by the proto device
> was specific to a namespace group. how would the proto device
> know to serve the same namespace to a process that's just
> done an rfork(RFNAMEG)?
Ahh yes - good point. That's one reason why I said that it may be going
too far!
> you could make it so each attach to '#' (the proto device) gave
> you a new instance of that device, so:
>
> unmount /proto
> bind '#' /proto
>
> would allow changing of availability of devices in /proto
> without affecting anything else.
>
See above....
Martin
--
Martin C. Atkins martin@mca-ltd.com
Mission Critical Applications Ltd, U.K. http://www.mca-ltd.com
next prev parent reply other threads:[~2003-02-25 5:00 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-24 19:04 rog
2003-02-24 19:04 ` rob pike, esq.
2003-02-24 19:53 ` Jack Johnson
2003-02-25 4:37 ` Martin C.Atkins
2003-02-25 11:02 ` chris
2003-02-25 14:01 ` Martin C.Atkins
2003-02-25 14:11 ` Russ Cox
2003-02-25 14:17 ` Martin C.Atkins
2003-02-25 14:34 ` Russ Cox
2003-02-25 14:36 ` Russ Cox
2003-02-25 14:52 ` Ronald G. Minnich
2003-02-25 19:57 ` northern snowfall
2003-02-25 16:49 ` Dan Cross
2003-02-26 5:12 ` Martin C.Atkins
2003-02-24 19:29 ` Fco.J.Ballesteros
2003-02-24 22:34 ` George Michaelson
2003-02-24 23:32 ` Bruce Ellis
2003-02-25 5:02 ` Martin C.Atkins
2003-02-25 11:19 ` chris
2003-02-25 14:06 ` Martin C.Atkins
2003-02-26 0:04 ` Bruce Ellis
2003-02-26 6:06 ` Skip Tavakkolian
2003-02-25 5:00 ` Martin C.Atkins [this message]
2003-02-25 9:05 ` [9fans] lpdaemon probs Conor Williams
2003-02-25 10:07 ` Geoff Collyer
2003-02-25 10:33 ` Conor Williams
2003-02-25 23:50 ` Geoff Collyer
2003-02-27 9:59 ` [9fans] lpdaemon probs (fix) Conor Williams
2003-02-27 20:57 ` Geoff Collyer
-- strict thread matches above, loose matches on Subject: below --
2003-02-26 23:46 [9fans] A proposal regarding # in bind a
2003-02-26 22:44 a
2003-02-26 23:02 ` Russ Cox
2003-02-26 21:26 John Stalker
2003-02-27 8:29 ` Fco.J.Ballesteros
2003-02-26 14:56 rog
2003-02-26 15:02 ` Russ Cox
2003-02-26 6:21 okamoto
2003-02-26 13:32 ` Digby Tarvin
2003-02-26 13:58 ` Russ Cox
2003-02-26 14:14 ` Russ Cox
2003-02-26 14:33 ` Boyd Roberts
2003-02-26 15:28 ` Ronald G. Minnich
2003-02-24 19:25 Joel Salomon
2003-02-25 4:33 ` Martin C.Atkins
2003-02-24 15:19 Martin C.Atkins
2003-02-24 15:28 ` Boyd Roberts
2003-02-24 18:36 ` rob pike, esq.
2003-02-25 4:57 ` Martin C.Atkins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030225103008.5ec58473.martin@mca-ltd.com \
--to=martin@mca-ltd.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).