From: "Albert D. Cahalan" <acahalan@cs.uml.edu>
To: newt@scyld.com (Daniel Ridge)
Cc: beowulf@beowulf.org,
linux-kernel@vger.kernel.org (Linux Kernel Mailing List)
Subject: Re: Will Mosix go into the standard kernel?
Date: Wed, 28 Feb 2001 18:58:07 -0500 (EST) [thread overview]
Message-ID: <200102282358.f1SNw7b177652@saturn.cs.uml.edu> (raw)
In-Reply-To: <Pine.LNX.4.21.0102281732210.22184-100000@eleanor.wdhq.scyld.com> from "Daniel Ridge" at Feb 28, 2001 06:06:37 PM
Daniel Ridge writes:
> Fellow Beowulfers,
>
> I have yet to hear a compelling argument about why any of them should
> go into the standard kernel -- let alone a particular one or a duck of a
> compromise.
>
> The Scyld system is based on BProc -- which requires only a 1K patch to
> the kernel. This patch adds 339 net lines to the kernel, and changes 38
> existing lines.
Well, that explains your viewpoint and your motivation. :-)
> I think we should instead focus our collective will on removing things
> from the kernel. For years, projects like ALSA, pcmcia-cs, and VMware
ALSA: driver work gets done twice
pcmcia-cs: this was so bad that Linus himself was unable to install
Linux on his new laptop, so now PCMCIA support is in the kernel.
VMware: quite a pain I think
You are basically suggesting the often-rejected "split up the kernel"
idea. I think the linux-kernel FAQ covers this.
> have done an outstanding job sans 'inclusion' and we should more
> frequently have the courage to do the same. RedHat and other linux vendors
> have demonstrated ably that they know how to build and package systems
> that draw together these components in an essentially reasonable way.
So people should only get kernels from linux vendors? This is great
for your business I'd imagine, but one of the nice things about Linux
is that you can replace the kernel without too much trouble.
next prev parent reply other threads:[~2001-02-28 23:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-27 17:17 Will Mosix go into the standard kernel? Zack Brown
2001-02-27 21:20 ` David L. Nicol
2001-02-27 21:32 ` Rik van Riel
2001-02-28 23:06 ` Daniel Ridge
2001-02-28 23:58 ` Albert D. Cahalan [this message]
2001-03-01 0:53 ` Dan Hollis
2001-03-01 1:35 ` Daniel Ridge
2001-03-01 2:37 ` zbrown
2001-03-02 0:52 ` Pavel Machek
2001-02-27 21:37 ` Alexander Viro
2001-02-27 21:56 ` Zack Brown
2001-02-27 22:29 ` zbrown
2001-02-27 22:33 ` J . A . Magallon
2001-02-28 17:59 ` Ric Wheeler
2001-02-27 17:31 Christopher Chimelis
2001-02-27 17:40 ` Zack Brown
[not found] <fa.o4k0c0v.smgv2v@ifi.uio.no>
[not found] ` <fa.m9jgfcv.17n8s2n@ifi.uio.no>
2001-03-01 15:02 ` Tor Arntsen
2001-03-01 19:13 ` Tim Wright
2001-03-02 10:22 Tor Arntsen
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=200102282358.f1SNw7b177652@saturn.cs.uml.edu \
--to=acahalan@cs.uml.edu \
--cc=beowulf@beowulf.org \
--cc=linux-kernel@vger.kernel.org \
--cc=newt@scyld.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).