9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] What is Plan9 exactly?
Date: Fri,  6 Jun 2014 08:28:16 -0400	[thread overview]
Message-ID: <6bfc2cbb201875b5151532f2c4f7bac1@brasstown.quanstro.net> (raw)
In-Reply-To: <CAPTfE6X7RgwHUeE9Rg3u7GKN3kubhfM7EO+J1Ze3PhCa4MxNUg@mail.gmail.com>

> P.S. The kernel is monolithic. Although, IIRC, there were attempts to make
> it a hybrid.

this is far from the full story.  because of the mount driver, many things
may be in the kernel or userland according to what makes sense.  for
example, the ip stack has moved back and forth several times.  the usb
interface implementations are in user space.  etc.  partfs(8) (sic, should
be in section 4) and sdloop(3) in 9atom are both loopback drivers that
appear to be served through sd(3), but partfs is in userspace and sdloop
is in the kernel.

likewise, resources can be imported from other machines' kernels or
userspace in the same way.  for example, i can import a gateway's ip stack
and use it directly as if it were local.

thus, while the kernel is fairly traditional, the capabilities are not.

- erik



  reply	other threads:[~2014-06-06 12:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-05  3:14 sl
2014-06-05 20:33 ` Yoann Padioleau
2014-06-06 12:13   ` Eugene Gorodinsky
2014-06-06 12:28     ` erik quanstrom [this message]
2014-06-06 12:39       ` lucio
  -- strict thread matches above, loose matches on Subject: below --
2014-06-05  3:10 OMAR RADWAN
2014-06-05  3:26 ` Winston Kodogo
2014-06-05  3:28   ` andrey mirtchovski
2014-06-05  3:37     ` OMAR RADWAN
2014-06-05  3:47       ` Alex Jordan
2014-06-05  5:11         ` OMAR RADWAN
2014-06-05 10:35           ` Charles Forsyth
2014-06-05 11:02             ` erik quanstrom
2014-06-05 18:08 ` brz-systemd-dev

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=6bfc2cbb201875b5151532f2c4f7bac1@brasstown.quanstro.net \
    --to=quanstro@quanstro.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).