From: tor@spacetec.no (Tor Arntsen)
To: linux-kernel@vger.kernel.org
Subject: Re: Will Mosix go into the standard kernel?
Date: Thu, 1 Mar 2001 16:02:11 +0100 [thread overview]
Message-ID: <200103011502.QAA25429@pallas.spacetec.no> (raw)
In-Reply-To: <fa.o4k0c0v.smgv2v@ifi.uio.no> <fa.m9jgfcv.17n8s2n@ifi.uio.no>
In-Reply-To: <fa.m9jgfcv.17n8s2n@ifi.uio.no>
Daniel Ridge <newt@scyld.com> writes:
[...]
>Compare this total volume to the thousands of lines of patches that
>RedHat or VA add to their kernel RPMS before shipping. I just don't see
[...]
What's good about that? The first thing I do is to rip out the RedHat
kernel and compile and install a pure kernel from ftp.kernel.org.
It's *bad* that those vendors deliver hacked kernels. It's not
something that should be recommended as a *goal*!
When I need a new kernel version I can't sit back and hope with
crossed fingers that RedHat (or whatever vendor) comes out with a
new, hacked version of Linus' latest.
-Tor
next parent reply other threads:[~2001-03-01 15:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.o4k0c0v.smgv2v@ifi.uio.no>
[not found] ` <fa.m9jgfcv.17n8s2n@ifi.uio.no>
2001-03-01 15:02 ` Tor Arntsen [this message]
2001-03-01 19:13 ` Tim Wright
2001-03-02 10:22 Tor Arntsen
-- strict thread matches above, loose matches on Subject: below --
2001-02-27 17:31 Christopher Chimelis
2001-02-27 17:40 ` Zack Brown
2001-02-27 17:17 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
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
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=200103011502.QAA25429@pallas.spacetec.no \
--to=tor@spacetec.no \
--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
all inboxes | Powered by JetHome®