9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Multiple '#s' ?
Date: Tue, 16 Dec 2008 20:21:45 +0000	[thread overview]
Message-ID: <82a974fdec1d7b1026e47ff473a8cd78@terzarima.net> (raw)
In-Reply-To: <20081216192511.GT9593@masters10.cs.jhu.edu>

>Or is there some active problem with the idea of multiple named
>pipe namespaces on one kernel?

they aren't named-pipe name spaces, but holders of arbitrary file descriptors,
which allows them to hold references to any open device, including network connections.
that means there's no problem in principle with having more than one.
one (incompatible) convention would be to make new ones and allow
an attach name such as #sxyz to refer to a particular instance, "xyz".
another variant, which is orthogonal, would allow directory structures
and track ownership.

named-pipe spaces are created by binding #| to a name, and each one is a new pipe.



      reply	other threads:[~2008-12-16 20:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-16 19:25 Nathaniel W Filardo
2008-12-16 20:21 ` Charles Forsyth [this message]

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=82a974fdec1d7b1026e47ff473a8cd78@terzarima.net \
    --to=forsyth@terzarima.net \
    --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).