9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Nathaniel W Filardo <nwf@cs.jhu.edu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] Multiple '#s' ?
Date: Tue, 16 Dec 2008 14:25:11 -0500	[thread overview]
Message-ID: <20081216192511.GT9593@masters10.cs.jhu.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 481 bytes --]

Is it crazy to propose that the kernel should offer multiple devsrv sources?
It seems to me that it might be a useful to isolate proesses from things
that have been posted in /srv's even if they run as the same user under,
without preventing the use of /srv altogether.

If something like this is possible, how?  If not, has there just not been
demand?  Or is there some active problem with the idea of multiple named
pipe namespaces on one kernel?

Thanks much.
--nwf;

[-- Attachment #2: Type: application/pgp-signature, Size: 204 bytes --]

             reply	other threads:[~2008-12-16 19:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-16 19:25 Nathaniel W Filardo [this message]
2008-12-16 20:21 ` 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=20081216192511.GT9593@masters10.cs.jhu.edu \
    --to=nwf@cs.jhu.edu \
    --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).