9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Roman V. Shaposhnik" <rvs@sun.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Why do we need syspipe() ?
Date: Thu,  8 Jan 2009 18:05:10 -0800	[thread overview]
Message-ID: <1231466710.6916.95.camel@goose.sun.com> (raw)
In-Reply-To: <565ecea34171eb37da1e18d5a05ee869@quanstro.net>

On Thu, 2009-01-08 at 18:48 -0500, erik quanstrom wrote:
> >> > Although in the alternative universe I can see how implementing #X 
> >> > as *channels* capable of 9P messages, could enable things like mounting
> >> > them on external hosts and letting these hosts manipulate physical
> >> > devices attached to yours (I agree that remote mounting of the kernel
> >> > services, which do not correspond to physical devices, is less useful).
> >> > Just like exporting my *local* /srv can be a useful things at times.
> >> 
> >> you mean like this?
> >> 	import -E ssl minooka.coraid.com '#æ' /n/minookaæ
> > 
> > Well, I tend not to like the proliferation of exportfs', but may
> > be in this case it is actually better that what I had in mind.
> 
> why?

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).

So the way devices are right now, actually seems to be better
compared to what I have in mind. Sorry for the noise.

Thanks,
Roman.




  reply	other threads:[~2009-01-09  2:05 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 [this message]
2009-01-09 12:54                     ` roger peppe
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=1231466710.6916.95.camel@goose.sun.com \
    --to=rvs@sun.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).