Re: starting with 2.7

[Marcelo Tosatti]

On Tue, Jan 04, 2005 at 04:01:17PM -0500, Theodore Ts'o wrote:
> On Tue, Jan 04, 2005 at 05:53:01PM +0100, Adrian Bunk wrote:
> > 
> > My opinion is to fork 2.7 pretty soon and to allow into 2.6 only the 
> > amount of changes that were allowed into 2.4 after 2.5 forked.
> > 
> > Looking at 2.4, this seems to be a promising model.
> 
> You have *got* to be kidding.  In my book at least, 2.4 ranks as one
> of the less successful stable kernel series, especially as compared
> against 2.2 and 2.0.  2.4 was far less stable, and a vast number of
> patches that distributions were forced to apply in an (only partially
> successful) attempt to make 2.4 stable meant that there are some
> 2.4-based distributions where you can't even run with a stock 2.4
> kernel from kernel.org. 

You got to be kidding now?

99% of the features distributions have applied to their 2.4 based kernels 
are "enterprise" features such as direct IO, AIO, etc.

Really I can't recall any "attempt to make 2.4 stable" from the distros,
its mostly "attempt to backport nice v2.6 feature".

Do you have any example?

> Much of the reputation that Linux had of a
> rock-solid OS that never crashed or locked up that we had gained
> during the 2.2 days was tarnished by 2.4 lockups, especially in high
> memory pressure situations.
> 
> One of the things which many people have pointed out was that even
> 2.6.0 was more stable than 2.4 was for systems under high load.

It took sometime to happen, but instability related to "high memory pressure" 
has been fixed in almost all cases long ago (the only remaining issue to
my knowledged is loopback device with highmemory).

I hardly see complaints of "crashes under load" problems since v2.4.19/20 
or so.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/