From: "roger peppe" <rogpeppe@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] Why do we need syspipe() ?
Date: Fri, 9 Jan 2009 12:54:23 +0000 [thread overview]
Message-ID: <df49a7370901090454pa41938pa3d5a4f175261ad@mail.gmail.com> (raw)
In-Reply-To: <1231466710.6916.95.camel@goose.sun.com>
On Fri, Jan 9, 2009 at 2:05 AM, Roman V. Shaposhnik <rvs@sun.com> wrote:
> Multiplexing. If devices exposed channel interface, and got
> exported there would be no kernel protecting from clients
> sending random sequences of 9P messages (on a single host
> you can't mount a channel and then continue reading/writing
> 9P messages over it).
a year or so back i mentioned a way that this could be done,
by having an "auth" (DMAUTH) file visible in the namespace representing the
channel to be mounted. you can turn this file into a new namespace
by opening it and handing it to an attach message (as the afid).
i've probably still got a working inferno kernel that i modified to
allow this, but i didn't take it any further.
this mechanism *could* potentially be used to replace the # namespace.
next prev parent reply other threads:[~2009-01-09 12:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-04 5:04 Roman V. Shaposhnik
2009-01-04 6:56 ` Russ Cox
2009-01-05 4:39 ` Roman V. Shaposhnik
2009-01-05 6:20 ` Russ Cox
2009-01-05 7:28 ` lucio
2009-01-05 11:00 ` roger peppe
2009-01-08 23:36 ` Roman V. Shaposhnik
2009-01-06 17:40 ` Nathaniel W Filardo
2009-01-06 20:37 ` Charles Forsyth
2009-01-06 23:13 ` Roman V. Shaposhnik
2009-01-06 23:15 ` erik quanstrom
2009-01-08 23:45 ` Roman V. Shaposhnik
2009-01-08 23:48 ` erik quanstrom
2009-01-09 2:05 ` Roman V. Shaposhnik
2009-01-09 12:54 ` roger peppe [this message]
2009-01-07 3:48 ` lucio
2009-01-07 7:00 ` Roman Shaposhnik
2009-01-07 9:31 ` Charles Forsyth
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=df49a7370901090454pa41938pa3d5a4f175261ad@mail.gmail.com \
--to=rogpeppe@gmail.com \
--cc=9fans@9fans.net \
/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).