mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "willy tarreau" <wtarreau@yahoo.fr>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] 2.5/2.6/2.7 transition [was Re: Linux 2.4.16-pre1]
Date: Mon, 26 Nov 2001 13:26:49 +0100 (CET)	[thread overview]
Message-ID: <20011126122649.51511.qmail@web20508.mail.yahoo.com> (raw)

> The _real_ solution is to make fewer fundamental
changes
> between stable kernels, and that's a real solution
that I
> expect to become more and more realistic as the
kernel
> stabilizes. I already expect 2.5 to have a _lot_
less
> fundamental changes than the 2.3.x tree ever had -
the
> SMP scaliability efforts and page-cachification
between
> 2.2.x and 2.4.x is really quite a big change.

Well, I know this has been discussed several times,
but why
not having 2 stable trees : one for the average "joe"
user
which would include fixes and new features, and one
for
prod servers which will have only bugfixes, and quite
old, 
tested features, with less risks of regression. I
think that all
in all, current 2.4 kernels are fairly stable except,
perhaps
for a few, not so common, features. There are still
lots of
people who don't upgrade their 2.2 to 2.4 (or even old
2.4 to
newer 2.4) because of a "well known bug" in a feature
they
might even never use.

I'm myself used to build kernels from Alan's tree, on
which
I add several features (ipsec...), and backport
bugfixes from
more recent kernels (as far as my understanding can
go, of
course). When 2.4.14 went out, I was still using a
2.4.10ac12
+many fixes, but without any feature upgrade. I have
several
friends using my kernels because they find them more
stable
although I couldn't judge because they don't always
report
bugs as people do on LKML.

A very conservative branch could be maintained with
not 
much effort since we would only have to include new
fixes
(ok, sometimes you can't keep up and have to make the
step, that's why I jumped from 2.4.10ac to 2.4.13ac).
We
could even count failure and success reports for some 
features to help those paranoïd to decide which kernel
to
use.

Perhaps it's what distro makers do, but at least they
don't
announce their kernels on LKML as you, Alan, or Andrea
actually do.

I even may participate in this, given my very limited
time (ie,
if people are ready to wait 3 weeks without news, and 
accept sometimes completely broken kernels when I jump
from one major release to one other), but honnestly,
that's
not my primary goal.

Just my 2 euro-cents here,
Willy


___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Courrier : http://courrier.yahoo.fr

             reply	other threads:[~2001-11-26 12:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-26 12:26 willy tarreau [this message]
2001-11-26 14:54 ` Horst von Brand
  -- strict thread matches above, loose matches on Subject: below --
2001-11-25 14:15 Linux 2.4.16-pre1 Stephan von Krawczynski
2001-11-25 18:17 ` Linus Torvalds
2001-11-25 23:53   ` [RFC] 2.5/2.6/2.7 transition [was Re: Linux 2.4.16-pre1] Mike Fedyk
2001-11-26  3:58     ` Linus Torvalds
2001-11-26  5:33       ` Mike Fedyk
2001-11-26 10:59       ` Rik van Riel
2001-11-26 14:58         ` jlnance
2001-11-26 18:18         ` H. Peter Anvin
2001-11-26 12:41       ` Horst von Brand
2001-11-26 19:35         ` Andrew Morton
2001-11-26 17:44       ` Rob Landley
2001-11-26 21:08         ` Alan Cox
2001-11-26 21:42           ` Rob Landley
2001-11-26 23:52             ` Rob Landley
2001-11-27  3:40               ` Johan Kullstam
2001-11-26  8:13     ` John Alvord

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=20011126122649.51511.qmail@web20508.mail.yahoo.com \
    --to=wtarreau@yahoo.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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

all inboxes | Powered by JetHome®