From: Stan Bubrouski <stan@ccs.neu.edu>
To: arjanv@redhat.com
Cc: Russell King <rmk+lkml@arm.linux.org.uk>,
Larry McVoy <lm@work.bitmover.com>,
Tim Cambrant <tim@cambrant.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Too soon for stable release?
Date: Sat, 29 Nov 2003 15:22:25 -0500 [thread overview]
Message-ID: <1070137345.19063.7.camel@duergar> (raw)
In-Reply-To: <1070127768.5228.1.camel@laptop.fenrus.com>
[-- Attachment #1: Type: text/plain, Size: 1637 bytes --]
On Sat, 2003-11-29 at 12:42, Arjan van de Ven wrote:
> On Sat, 2003-11-29 at 18:11, Russell King wrote:
> > On Sat, Nov 29, 2003 at 09:01:04AM -0800, Larry McVoy wrote:
> > > The news media hasn't picked up on this yet, they seem to think that
> > > 2.6.0 is something that will be useful. It won't be, there will be a
> > > period of months during which things stablize and then you'll see the
> > > distros pick up the release. I don't remember where it was exactly
> > > (2.4.18?) but Red Hat waited quite a while before switching to 2.4
> > > from 2.2. This is normal and it works out quite well in practice.
> >
> > Red Hat did a 2.4.2 release which was 2.4.2 + a lot of stability changes.
>
> which was basically a 2.4.4-pre
>
> > IIRC, RH7.2 was based on 2.4.7,
>
> 2.4.7 lived for half a day but the VM of 2.4.7 was so bad we had to go
> to 2.4.9 immediately..
I remember trying stock 2.4.7...it was the first 2.4.x kernel I tried
and I wasn't all that impressed (and i had a plethora of problems). I
didn't like 2.4.9 much either to be honest, but it was a lot better than
earlier 2.4.x releases. 2.4.x is where I learned exactly what Larry
stated earlier in the thread about stable kernels taking a while to
actually stabilize. But when they do, the result is quite worth it.
And for the record, I'm finding 2.6-test kernels more stable than early
2.4.x release kernels, so I think you guys have a come a long way and
done an awesome job. I think 2.6 is going to be a kernel that blows
away people who whined about 2.4s desktop performance.
Kudos guys for a job well done,
Stan
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-11-29 20:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-29 17:49 Too soon for stable release? Tim Cambrant
2003-11-29 17:01 ` Larry McVoy
2003-11-29 17:11 ` Russell King
2003-11-29 17:42 ` Arjan van de Ven
2003-11-29 20:22 ` Stan Bubrouski [this message]
2003-11-29 17:16 ` William Lee Irwin III
2003-12-01 18:56 ` Mike Fedyk
2003-11-29 18:03 ` Tim Cambrant
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=1070137345.19063.7.camel@duergar \
--to=stan@ccs.neu.edu \
--cc=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@work.bitmover.com \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=tim@cambrant.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