Re: A users thoughts on the new dev. model

From: Florin Andrei
Date: Fri Jul 23 2004 - 14:34:20 EST

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

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

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

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at