From: Willy Tarreau <w@w.ods.org>
To: Andre Hedrick <andre@linux-ide.org>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
linux-kernel@vger.kernel.org
Subject: Re: SATA support merge in 2.4.27
Date: Fri, 16 Apr 2004 22:50:28 +0200 [thread overview]
Message-ID: <20040416205028.GC596@alpha.home.local> (raw)
In-Reply-To: <Pine.LNX.4.10.10404160259480.22035-100000@master.linux-ide.org>
> Marcelo,
>
> You are suggesting that 2.6 is not stable ? How could that be ?
Andre, ressure me, you were drunk ?
A stable kernel is a kernel in which a new release does not induce 20 rejects
when applying the same patches as on the previous one, and in which you can
confidently upgrade to fix a security issue without worrying that everything
else will break under your feet. I'm really happy that 2.4 *WILL* become
stable with 2.4.27, and probably will be the first 2.4 kernel ready for far
remote deployment. Since about 2.4.23, it has become a lot easier to maintain
up-to-date parallel trees in sync with Marcelo's because of less core changes
all the time, and I really thank him for this progressive feature freeze.
When I'll have a fair insurance that 2.6 does not change so fast, may be I'll
start to think about it. But right now, 2.6 only serves me as a boot loader
in conjunction with Randy's kexec patch. Sad but true.
> Should it not be backported to 2.2 and why not 2.0 ?
I thought you were more aware than that about the number of people still
using 2.0 and 2.2. They are "a lot". What does "a lot" mean ? Well, I think
that there are more people still running production machines on 2.2 and 2.0
than people who have ever used 1.0 or 1.2. And at these times, we considered
that "a lot". I know some people who still install RedHat 6.2 from time to
time. Why do they do this ? certainly because a standard 2.2.26 kernel +
grsecurity offers them enough stability and security to satisfy their needs
and not to have to upgrade every 4 months.
> Necessary? But their is the new and improved called 2.6.
> It is time for the old and lousy to quietly wimper off and die.
I would better say that it's time for the old and stable to live long and
quitely, and for the young baby to slowly discover the desktop world, then
the production world before engaging its reputation on mission-critical
systems.
Regards,
Willy
next prev parent reply other threads:[~2004-04-16 20:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-15 17:17 SATA support merge in 2.4.27 Marcelo Tosatti
2004-04-15 19:06 ` Stefan Smietanowski
2004-04-16 1:08 ` Jeff Garzik
2004-04-16 9:29 ` Andre Hedrick
2004-04-16 10:03 ` Andre Hedrick
2004-04-16 10:20 ` John Bradford
2004-04-16 10:24 ` Arjan van de Ven
2004-04-16 10:30 ` John Bradford
2004-04-16 10:28 ` Arjan van de Ven
2004-04-16 12:37 ` John Bradford
2004-04-16 12:36 ` Arjan van de Ven
2004-04-16 12:39 ` Marc-Christian Petersen
2004-04-16 10:28 ` Andre Hedrick
2004-04-16 12:51 ` John Bradford
[not found] ` <20040416135102.GB1485@logos.cnet>
2004-04-16 14:23 ` Marcelo Tosatti
2004-04-16 20:50 ` Willy Tarreau [this message]
2004-04-17 9:46 ` Andre Hedrick
2004-04-16 13:53 ` Marcelo Tosatti
[not found] <1Ljts-1eQ-29@gated-at.bofh.it>
2004-04-15 19:24 ` Andi Kleen
2004-04-15 19:32 ` Jeff Garzik
2004-04-15 19:36 ` Jeff Garzik
2004-04-15 19:41 ` Bartlomiej Zolnierkiewicz
2004-04-16 6:29 ` Mihai RUSU
-- strict thread matches above, loose matches on Subject: below --
2004-04-16 17:48 Martin Knoblauch
[not found] <fa.dv8bnkv.rjkl9b@ifi.uio.no>
[not found] ` <fa.dvodmcu.r3ql14@ifi.uio.no>
2004-04-17 4:59 ` Andreas Hartmann
[not found] <1LQfz-2na-5@gated-at.bofh.it>
[not found] ` <1LQfz-2na-7@gated-at.bofh.it>
[not found] ` <1LQfz-2na-3@gated-at.bofh.it>
2004-04-17 11:36 ` Andi Kleen
2004-04-17 20:28 Mikael Pettersson
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=20040416205028.GC596@alpha.home.local \
--to=w@w.ods.org \
--cc=andre@linux-ide.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.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