9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: nemo@gsyc.escet.urjc.es
To: 9fans@cse.psu.edu
Subject: Re: [9fans] micro vs monolithic kernels
Date: Tue, 17 Apr 2001 10:35:33 +0200	[thread overview]
Message-ID: <20010417083334.281B019A11@mail.cse.psu.edu> (raw)


The funny thing is that services like drivers, file systems, et al.
are out of the kernel in Plan 9 since they come mostly from the network.
Certainly, you get your drivers in the kernel, but I'm used to import
many of them from the network. So, you can replace, develop and debug much
`kernel software' in user space, which IMHO was the original aim of the
uKernel camp. What I like most is that the system design is not pushed too far
just to get more stuff out of the kernel.

I'd say that Plan 9 has a well-engineered kernel: Not micro, not macro. ☺


:  Andrey A Mirtchovski <aam396@mail.usask.ca> wrote:
:  >i seem to remember reading somewhere a reasoning on why it was chosen to
:  >implement p9 with a monolithic kernel, instead of a micro one..
:
:  Charles Forsyth <forsyth@vitanuova.com> replied:
:  >the implied comparison is false.  to start with, the plan 9 kernel
:  >is not  `monolithic'.  it is highly modular.
:
:  I've heard people use the term `monolithic' to describe an operating
:  system that may or may not have been modular, but was a `monolithic
:  monitor'. Years ago, I was a junior on a project developing such a



             reply	other threads:[~2001-04-17  8:35 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-17  8:35 nemo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-04-10 11:56 forsyth
2001-04-10 11:50 forsyth
2001-04-10 11:35 Matt
2001-04-10 10:52 forsyth
     [not found] <200104092210.RAA06371@einstein.ssz.com>
2001-04-09 22:12 ` Jim Choate
2001-04-10  9:00   ` Boyd Roberts
2001-04-09 22:00 jmk
2001-04-09 22:30 ` Jim Choate
2001-04-09 21:47 presotto
2001-04-09 21:43 Russ Cox
2001-04-09 22:16 ` Jim Choate
2001-04-10  8:59   ` Douglas A. Gwyn
2001-04-10  9:00   ` Boyd Roberts
2001-04-09 21:15 Russ Cox
2001-04-09 21:52 ` Jim Choate
2001-04-09 21:36   ` Lyndon Nerenberg
2001-04-09 22:08     ` Jim Choate
2001-04-09 22:34       ` Lyndon Nerenberg
2001-04-10  0:45       ` Steve Kilbane
2001-04-10  0:28         ` Jim Choate
2001-04-10  8:18           ` Steve Kilbane
2001-04-10  8:57       ` Douglas A. Gwyn
2001-04-09 21:40   ` William Josephson
2001-04-09 22:10     ` Jim Choate
2001-04-09 22:16       ` William Josephson
2001-04-09 22:42   ` Dan Cross
2001-04-09 23:10     ` Jim Choate
2001-04-10  0:30       ` Dan Cross
2001-04-09 22:10 ` Mike Haertel
     [not found] <john@cs.york.ac.uk>
2001-04-09 14:33 ` John A. Murdie
2001-04-09 23:31   ` Steve Kilbane
2001-04-09 10:19 forsyth
2001-04-09  9:09 forsyth
2001-04-09  9:32 ` Dave Iafrate - CSCI/F1997
2001-04-09 16:14   ` Douglas A. Gwyn
2001-04-08 19:36 presotto
2001-04-08 17:55 Andrey A Mirtchovski

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=20010417083334.281B019A11@mail.cse.psu.edu \
    --to=nemo@gsyc.escet.urjc.es \
    --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).