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: Tue,  6 Jan 2009 15:13:37 -0800	[thread overview]
Message-ID: <1231283617.5141.74.camel@goose.sun.com> (raw)
In-Reply-To: <a7cf0e2e300535562629960ea6885ceb@terzarima.net>

On Tue, 2009-01-06 at 20:37 +0000, Charles Forsyth wrote:
> >This just means that these services need to be mounted at the canonical
>
> there is no point binding #a or #D into the name space.
> they can be used only locally and might as well
> be accessed directly.  they might be considered similar to
> "push" in streams.  #s has a similar difficulty to #a and #D when creating the names,
> and requires special hacks to make existing files usable when exported.

Well, that's been the case for as long as Plan9 existed, and I don't
want to say that it doesn't work.

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.

Thanks,
Roman.




  reply	other threads:[~2009-01-06 23:13 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 [this message]
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
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=1231283617.5141.74.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).