9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Eli Cohen <echoline@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] novel userspace paradigms introduced by plan 9
Date: Sat,  2 Jul 2011 11:23:02 -0700	[thread overview]
Message-ID: <CAHwi9bxG_=kJSeKNn4iD_OewWu5HQB7zEisgpLbNWQNRBwu7Jg@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=Cic53c+jpgQPt6MiA2vPVNH+-Jw@mail.gmail.com>

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

I have used gentoo extensively and plan9 for a few years now as well, and
this concept of "namespaces" for processes is a confusing but interesting
concept.  maybe you could use grsec to limit the access to gentoo's "file
system" at a per-process level.  This would be somewhat similar to what
plan9 does, but you'd have to also find a good way to bind a directory
elsewhere in the tree at a per-process level, unified with what was already
there (aka, hopefully NOT like mount -o bind).  This is only the tip of the
iceberg; plan9 does this per-process filesystem namespacing to set up a good
environment for a system which adheres to the orginal unix "philosophies"
such as, everything has a "file" to represent it.  linux does this well for
data on the disk, device nodes, and whatever gets put in /proc.  it does not
do this, generally, for something like an email message.  a good plan9
program, however, is likely to do this.
as an example of the power of this concept, `% topng < /dev/screen >
screenshot.png' will use the relatively simple program topng to convert the
*file* /dev/screen into the *file* screenshot.png.
One major difference is X11.  In plan9, the system handles the graphics more
directly.  network export of windows is handled differently.  it might be
interesting to make a rio for linux which draws directly to /dev/fb0.  Or it
might be better to convert /dev/fb0 to a /dev/screen on linux, even in
userspace, and then more or less use rio for plan9.  performance might be an
issue, but plan9 people are still waiting on 3d graphics if they even care
enough to wait...

-Eli

On Sat, Jul 2, 2011 at 10:24 AM, Jack Johnson <knapjack@gmail.com> wrote:

> On Sat, Jul 2, 2011 at 8:29 AM, dexen deVries <dexen.devries@gmail.com>
> wrote:
> > disclaimer: i'm not a plan 9 person for any viable value of `p9 person'
>
> I'm in the same boat, but I aspire to be in the other boat. :)
>
> -Jack
>
>

[-- Attachment #2: Type: text/html, Size: 2372 bytes --]

  parent reply	other threads:[~2011-07-02 18:23 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-02 16:15 Robert Seaton
2011-07-02 16:23 ` Jacob Todd
2011-07-17 12:37   ` Eugene Gorodinsky
2011-07-17 13:54     ` Charles Forsyth
2011-07-18  8:32       ` Eugene Gorodinsky
2011-07-18 17:14         ` Charles Forsyth
2011-07-19  7:50           ` Eugene Gorodinsky
2011-07-02 16:29 ` dexen deVries
2011-07-02 17:24   ` Jack Johnson
2011-07-02 17:34     ` [9fans] To p9 or not to p9? (was: novel userspace paradigms introduced by plan 9) dexen deVries
2011-07-02 18:23     ` Eli Cohen [this message]
2011-07-02 18:36       ` [9fans] novel userspace paradigms introduced by plan 9 dexen deVries
2011-07-02 23:10         ` simon softnet
2011-07-02 23:31           ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-07-03  8:55             ` simon softnet
2011-07-03 11:06         ` Connor Lane Smith
2011-07-03 14:38           ` Iruatã Souza
2011-07-03 22:05             ` Charles Forsyth
2011-07-03 17:57           ` Lyndon Nerenberg
2011-07-03 18:10             ` dexen deVries
2011-07-03 20:44             ` erik quanstrom
2011-07-03 20:53               ` Lyndon Nerenberg
2011-07-03 20:57                 ` erik quanstrom
2011-07-03 21:08                   ` andrey mirtchovski
2011-07-03 21:29                     ` ron minnich
2011-07-03 21:38                       ` andrew zerger
2011-07-03 21:39                         ` andrew zerger
2011-07-03 21:51                       ` andrey mirtchovski
2011-07-17 16:25                     ` Nicolas Bercher
     [not found]         ` <CAMdzYRr4_2JdEXaZ8cg=_9CJYzZr63HtEAtaG6x8WXGrPtp_DQ@mail.gmail.c>
2011-07-03 11:55           ` erik quanstrom
2011-07-03 12:32             ` Connor Lane Smith
     [not found]             ` <CAMdzYRowH+Y3UA4iyPy+4dP-cE064A6XZXvTbB1M-jBypu_ORw@mail.gmail.c>
2011-07-03 12:51               ` erik quanstrom
2011-07-03 13:13                 ` Connor Lane Smith
2011-07-04  6:44 ` Yaroslav
2011-07-04 14:59   ` Robert Seaton
2011-07-16 10:52     ` simon softnet
2011-07-16 19:12       ` David Leimbach
2011-07-16 19:17         ` simon softnet
2011-07-16 19:32           ` Ethan Grammatikidis
2011-07-16 21:10             ` simon softnet
2011-07-17  9:38               ` Ethan Grammatikidis
2011-07-18  9:04       ` Balwinder S Dheeman
2011-07-18  9:30         ` dexen deVries

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='CAHwi9bxG_=kJSeKNn4iD_OewWu5HQB7zEisgpLbNWQNRBwu7Jg@mail.gmail.com' \
    --to=echoline@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).