linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aaron Smith <aws4y@virginia.edu>
To: linux-kernel@vger.kernel.org
Subject: Re: Rewrite Kernel
Date: Wed, 07 Apr 2004 14:12:17 -0400	[thread overview]
Message-ID: <40744481.7050002@virginia.edu> (raw)
In-Reply-To: <20040407150516.GC23517@marowsky-bree.de>

Lars Marowsky-Bree wrote:

>Guys, gals,
>
>you are all missing the point.
>
>It is obvious that what we really need is a hand-optimized in-kernel
>core LISP machine written in >i386 assembly, then we need to port the
>rest of the kernel to run as LISP bytecode on top of that in ring1 (in
>particular the security policies).
>
>Of course, important privileged user-space such as glibc should be
>ported to this highly efficient non-recursive LISP machine too for
>efficiency and run on ring 2 for speed and security.
>  
>
What you are talking about is a LISP machine micro-kernel in Ring0 which 
sort of defeats the whole point of Linux being monolithic kernel. Also 
couldn't we just run HURD, or for that matter EMACS ;-), as a kernel. I, 
personally have come around to Linus point of view on the whole 
micro-kernel thing so I don't see much of a advantage to this, as there 
are other micro kernel projects ( HURD, Darwin/*BSD?).

-Aaron

  parent reply	other threads:[~2004-04-07 18:17 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-07 12:54 Rewrite Kernel Mohamed Aslan
2004-04-07 12:57 ` viro
2004-04-07 12:59 ` Wichert Akkerman
2004-04-07 13:08 ` John Bradford
2004-04-07 13:13 ` Sean Neakums
2004-04-07 13:46   ` Dumitru Ciobarcianu
2004-04-07 13:58   ` Richard B. Johnson
2004-04-07 14:36     ` Nick Piggin
2004-04-07 18:58     ` Valdis.Kletnieks
2004-04-07 13:22 ` Zwane Mwaikambo
2004-04-07 13:56 ` Richard B. Johnson
2004-04-07 14:02 ` Erik Mouw
2004-04-07 14:04 ` Trent Lloyd
2004-04-07 14:27 ` Redeeman
2004-04-07 14:55   ` John Bradford
2004-04-07 15:05     ` Lars Marowsky-Bree
2004-04-07 15:17       ` John Bradford
2004-04-07 15:20       ` Emmanuel Fleury
2004-04-07 15:21       ` John Bradford
2004-04-07 17:21       ` Redeeman
2004-04-07 18:47         ` Paulo Marques
2004-04-07 18:12       ` Aaron Smith [this message]
2004-04-07 19:58         ` Måns Rullgård
2004-04-07 23:03           ` David B. Stevens
2004-04-08 10:34             ` David Weinehall
2004-04-07 14:57 ` Rob Couto
2004-04-13 14:03   ` Eric W. Biederman
2004-04-07 16:00 ` Brian Pawlowski
2004-04-10 16:59 ` J. Ryan Earl
2004-04-10 17:21   ` Denis Vlasenko
2004-04-10 19:57     ` J. Ryan Earl
2004-04-11 16:58       ` Denis Vlasenko
  -- strict thread matches above, loose matches on Subject: below --
2004-04-07 13:05 Mohamed Aslan
2004-04-07 17:27 ` Robin Rosenberg
2004-04-24 13:24 Mohamed Aslan
2004-04-24 15:10 ` billy rose
2004-04-24 15:45 ` David B. Stevens

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=40744481.7050002@virginia.edu \
    --to=aws4y@virginia.edu \
    --cc=linux-kernel@vger.kernel.org \
    /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).