From: Florin Andrei <florin@andrei.myip.org>
To: linux-kernel@vger.kernel.org
Cc: barnowl@unix.eng.ua.edu
Subject: Re: A users thoughts on the new dev. model
Date: Fri, 23 Jul 2004 12:32:38 -0700 [thread overview]
Message-ID: <1090611158.2931.13.camel@stantz.corp.sgi.com> (raw)
In-Reply-To: <40FFD760.8060504@unix.eng.ua.edu>
On Thu, 2004-07-22 at 08:04, Evan Hisey wrote:
> As an end use of the vanilla
> tree, I would like to point out that a large number of people and
> projects rely on the vanilla kernel to be the stable tree do to the
> overly varied and random patching nature of vendor supplied kernels
It looks like a communication problem.
Like someone else noted, 2.6 is currently more stable than the
correspondent 2.2 and 2.4 versions, due to efforts by OSDL and others,
and perhaps due to significant contribution from A. Morton, etc.
So, when Andrew says that perhaps 2.6 is not going to be the most stable
series, it does not mean "it's going to be the least stable series among
2.0, 2.2, 2.4, etc." In fact, even taking Andrew's words into account,
it may well be that 2.6 is going to be more stable than 2.4 - the same
2.4 that "clueless" users were happily using on their production
servers, while at the same time complaining about 2.6 being too
"unstable".
It could be that the ones who are complaining have an oversimplified,
"binary" view of how things are:
- Caveman thinks 2.2, 2.4 stable is
- Caveman thinks 2.6 stable is not
Or, in other words, stability seems to be a magical property that's
added or removed to/from a software based on their names/numbers/etc.
While the reality might well be more complex. So, 2.6 is not the most
stable series. That's fine, vanilla "stable" was never the most stable -
that title goes to the Red Hat Enterprise kernels and the like.
But if 2.6 is more stable than 2.4, then by all means that's fine with
me.
It seems to me that some users do not want to just use the most stable
kernel. They want to use the most stable kernel AND that kernel must be
the "stable" vanilla kernel.
Sorry guys, but the vanilla kernel has many goals. Stability is only one
of them.
--
Florin Andrei
http://florin.myip.org/
prev parent reply other threads:[~2004-07-23 19:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-22 15:04 A users thoughts on the new dev. model Evan Hisey
2004-07-22 22:25 ` Bill Davidsen
2004-07-23 13:58 ` H. Peter Anvin
2004-07-23 15:24 ` szonyi calin
2004-07-23 16:39 ` David Ford
2004-07-23 19:06 ` Xiong Jiang
2004-07-23 20:00 ` Tim Wright
2004-07-23 21:40 ` Adrian Bunk
2004-07-23 23:04 ` hpa
2004-07-24 10:38 ` Adrian Bunk
2004-07-27 20:08 ` Bill Davidsen
2004-07-22 22:57 ` Paul Jackson
2004-07-27 20:20 ` Bill Davidsen
2004-07-28 7:31 ` Paul Jackson
2004-07-23 19:32 ` Florin Andrei [this message]
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=1090611158.2931.13.camel@stantz.corp.sgi.com \
--to=florin@andrei.myip.org \
--cc=barnowl@unix.eng.ua.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.