From: Rik van Riel <riel@conectiva.com.br>
To: Stephen Satchell <satch@fluent-access.com>
Cc: Daniel <ddickman@nyc.rr.com>,
Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: obsolete code must die
Date: Thu, 14 Jun 2001 01:26:02 -0300 (BRST) [thread overview]
Message-ID: <Pine.LNX.4.21.0106140125010.14934-100000@imladris.rielhome.conectiva> (raw)
In-Reply-To: <4.3.2.7.2.20010613204443.00bbb150@mail.fluent-access.com>
On Wed, 13 Jun 2001, Stephen Satchell wrote:
> At 12:24 AM 6/14/01 -0300, Rik van Riel wrote:
> >Everything you propose to get rid of are DRIVERS. They
> >do NOT complicate the core kernel, do NOT introduce bugs
> >in the core kernel and have absolutely NOTHING to do with
> >how simple or maintainable the core kernel is.
>
> Not quite. There were two non-driver suggestions that the man did
> make: remove 386/486 support and remove floating-point emulation
> support. Both are bad for the embedded-systems space, because the 486
> is still used there widely.
Both are waaaay outside the core of the kernel, though.
> Are all the bus support code exclusively in drivers, or is there
> something compiled into the nucleus for start-up?
They're compiled into the nucleus (if you want to), but
they're in no way clogging up the source code of the core
kernel.
regards,
Rik
--
Virtual memory is like a game you can't win;
However, without VM there's truly nothing to lose...
http://www.surriel.com/ http://distro.conectiva.com/
Send all your spam to aardvark@nl.linux.org (spam digging piggy)
next prev parent reply other threads:[~2001-06-14 4:26 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.21.0106140018140.14934-100000@imladris.rielhome .conectiva>
2001-06-14 0:44 ` obsolete code must die Daniel
2001-06-14 0:54 ` Rik van Riel
2001-06-14 0:56 ` Jaswinder Singh
2001-06-14 1:00 ` Jeff Garzik
[not found] ` <20010613204729.A18297@pimlott.ne.mediaone.net>
2001-06-14 1:05 ` Daniel Dickman
2001-06-14 1:09 ` Rik van Riel
2001-06-14 1:20 ` Gary E. Miller
2001-06-14 1:08 ` Colonel
2001-06-13 22:23 ` Rafael Diniz
2001-06-15 19:45 ` Eric Hancock
2001-06-14 19:00 ` Mike A. Harris
2001-06-14 1:11 ` John Chris Wren
2001-06-14 1:13 ` Claudio Martins
2001-06-14 1:23 ` Justin Guyett
2001-06-14 1:51 ` Mohammad A. Haque
2001-06-14 1:55 ` Horst von Brand
2001-06-14 3:41 ` Arnaldo Carvalho de Melo
2001-06-14 1:58 ` D. Stimits
2001-06-14 2:22 ` Alan Olsen
2001-06-14 1:24 ` Robert Love
2001-06-14 1:32 ` Colonel
2001-06-14 1:45 ` Rainer Mager
2001-06-14 2:00 ` Download process for a "split kernel" (was: obsolete code must die) David Luyer
2001-06-14 2:30 ` Jaswinder Singh
2001-06-14 7:56 ` Daniel Phillips
2001-06-14 8:34 ` Alexander Viro
2001-06-14 16:25 ` Daniel Phillips
2001-06-14 17:21 ` Richard Gooch
2001-06-14 12:07 ` Horst von Brand
2001-06-14 12:14 ` David Luyer
2001-06-14 12:18 ` Rob Landley
2001-06-14 7:56 ` obsolete code must die Alan Cox
2001-06-14 9:06 ` Ghozlane Toumi
2001-06-14 9:24 ` James Sutherland
2001-06-14 14:45 ` Michael Bacarella
2001-06-15 3:58 ` Michael Peddemors
2001-06-15 4:09 ` Joel Jaeggli
2001-06-15 11:51 ` Rogier Wolff
2001-06-14 1:41 ` David Luyer
2001-06-14 2:37 ` Tom Vier
2001-06-14 8:35 ` Bohdan Vlasyuk
2001-06-14 10:25 ` Andrzej Krzysztofowicz
2001-06-14 2:31 ` James Stevenson
2001-06-14 3:24 ` Rik van Riel
2001-06-14 3:48 ` Stephen Satchell
2001-06-14 4:26 ` Rik van Riel [this message]
2001-06-14 6:31 ` Russell King
2001-06-14 6:54 ` Daniel Dickman
2001-06-14 7:12 ` L. K.
2001-06-14 8:44 ` Luigi Genoni
2001-06-14 9:55 ` Thomas Pornin
2001-06-14 15:15 ` Brad Johnson
2001-06-14 18:57 ` Mike A. Harris
2001-06-15 3:48 ` Michael Peddemors
2001-06-15 14:21 ` Horst von Brand
2001-06-14 10:22 Heusden, Folkert van
2001-06-14 13:05 ` Nils Holland
2001-06-14 14:01 Jesse Pollard
2001-06-14 17:21 ` richard
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=Pine.LNX.4.21.0106140125010.14934-100000@imladris.rielhome.conectiva \
--to=riel@conectiva.com.br \
--cc=ddickman@nyc.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=satch@fluent-access.com \
/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).