9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Plan9 advancements over Unix
Date: Fri, 27 Jul 2007 11:56:36 -0400	[thread overview]
Message-ID: <1e314e347f4ab316668ef8d6e187c01b@coraid.com> (raw)
In-Reply-To: <1185547777.637534.191320@22g2000hsm.googlegroups.com>

> - Why was 8 1/2 abandoned? Is it because the graphics is much advanced
> over bitmap operations? Does plan9 use Xorg now? I think at least the
> idea of having a single private console sounds good.

plan 9 uses rio, which is a decendent of 8½.  plan b, a close relative of plan 9,
uses omero.

> 
> - Having private namespaces means maintaining a namespace *per-
> process*. Would this not be more complicated than having a single one?
>

in principle, each process may have its own namespace.  in practice large
numbers of processes do share the same namespace.

this is simplier than having one global namespace.  one prototypical use
of this in plan 9 is the handling of network stacks.  on plan 9 i can
import the network stack from a gatway that has the access i need and
bind it on /net (the place where ip networking stuff lives).  processes
started in this namespace will do their networking through the gateway,
while other processes in the system are oblivious.

> Is there a paper that compares or evaluates how well Plan9's new
> features performed over Unix?

i don't think plan 9 has new "features".  it's quite different.  "devices"
are implemented by fileservers, for example.  thus it makes not difference
(to the client) if the "device" is in the kernel, in userland or on another
machine.

- erik


      parent reply	other threads:[~2007-07-27 15:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-27 15:01 Bilgehan.Balban
2007-07-27 15:41 ` Kris Maglione
2007-07-27 15:56 ` erik quanstrom [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=1e314e347f4ab316668ef8d6e187c01b@coraid.com \
    --to=quanstro@coraid.com \
    --cc=9fans@cse.psu.edu \
    /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).