From: Pavel Machek <pavel@suse.cz>
To: Alexander Viro <viro@math.psu.edu>
Cc: Rik van Riel <riel@conectiva.com.br>,
Rakesh Kumar Banka <Rakesh@asu.edu>,
linux-kernel@vger.kernel.org
Subject: Re: Monolithic Vs. Microkernel
Date: Tue, 5 Mar 2002 21:47:37 +0100 [thread overview]
Message-ID: <20020305204737.GC318@elf.ucw.cz> (raw)
In-Reply-To: <20020304144923.A96@toy.ucw.cz> <Pine.GSO.4.21.0203051533160.18755-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0203051533160.18755-100000@weyl.math.psu.edu>
Hi!
> > Not *all* of them. On vsta, you could do
> >
> > ( killall keyboard; sleep 1; keyboard ) &
> >
> > to change your keymap. On linux you need special tools for managing
> > modules and are not protected from module bugs. Try developing filesystem
> > on production box.... You can do that on u-kernels.
>
> Userland filesystems != microkernel.
Yep, but microkernel => userland filesystems ;-). Anyway, they *can*
do things linux can't do (or linux has hard time with), like
partitioning physical machine into few logical ones, filesystems in
userland, ability to debug drivers on production machines, etc.
I like those features, but I'm not sure if costs introduced by
u-kernels are worth it.
Pavel
--
(about SSSCA) "I don't say this lightly. However, I really think that the U.S.
no longer is classifiable as a democracy, but rather as a plutocracy." --hpa
next prev parent reply other threads:[~2002-03-06 13:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 6:11 Monolithic Vs. Microkernel Rakesh Kumar Banka
2002-02-26 6:17 ` Larry McVoy
2002-02-26 9:49 ` Alan Cox
2002-02-26 6:17 ` David Lang
2002-02-26 6:23 ` Eric Krout
2002-02-26 11:45 ` Rik van Riel
2002-03-04 14:49 ` Pavel Machek
2002-03-05 20:34 ` Alexander Viro
2002-03-05 20:47 ` Pavel Machek [this message]
2002-03-05 21:04 ` Rik van Riel
2002-03-05 21:17 ` Xavier Bestel
2002-03-06 11:22 ` Pavel Machek
2002-03-05 21:32 ` Bernd Eckenfels
-- strict thread matches above, loose matches on Subject: below --
2002-02-26 10:34 Hans Adams
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=20020305204737.GC318@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=Rakesh@asu.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
--cc=viro@math.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.