From: Pavel Machek <pavel@suse.cz>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Rakesh Kumar Banka <Rakesh@asu.edu>, linux-kernel@vger.kernel.org
Subject: Re: Monolithic Vs. Microkernel
Date: Mon, 4 Mar 2002 14:49:24 +0000 [thread overview]
Message-ID: <20020304144923.A96@toy.ucw.cz> (raw)
In-Reply-To: <Pine.GSO.4.21.0202252301510.24728-100000@general3.asu.edu> <Pine.LNX.4.33L.0202260844260.7820-100000@imladris.surriel.com>
In-Reply-To: <Pine.LNX.4.33L.0202260844260.7820-100000@imladris.surriel.com>; from riel@conectiva.com.br on Tue, Feb 26, 2002 at 08:45:29AM -0300
Hi!
> > Anyone working on the Microkernel implementation
> > of Linux? Specially in the area of seperating the process
> > and the file management activities out of the kernel.
>
> You have to remember that the source code for Linux is available.
>
> This means we can have all the advantages of modularity at the
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.
Pavel
--
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.
next prev parent reply other threads:[~2002-03-05 20:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 6:11 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 [this message]
2002-03-05 20:34 ` Alexander Viro
2002-03-05 20:47 ` Pavel Machek
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
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=20020304144923.A96@toy.ucw.cz \
--to=pavel@suse.cz \
--cc=Rakesh@asu.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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
all inboxes | Powered by JetHome®