[lkml]   [2004]   [Oct]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRE: My thoughts on the "new development model"
> On Tuesday 26 October 2004 01:40, Chuck Ebbert wrote:
> > Bill Davidsen wrote:
> >
> > > I don't see the need for a development kernel, and it is
> desirable
> > > to be
> > > able to run kernels.
> >
> > Problem is, 'release' kernels are quite buggy. For
> > example 2.6.9 has a long list of bugs:
> >
> > Sure, the next release will (may?) fix these bugs, but it will
> > definitely add a whole set of new ones.

> To my mind this just points out the need for a bug fix
> branch. e.g. a
> branch containing just bug/security fixes against the current
> stable kernel. It might also be worth keeping the branch
> active for the n-1 stable kernel too.

To my mind, we only need to make clear that a stable kernel is a stable
Not a kernel for experiments.

To my mind, stock 2.6 kernels are nice for nerds trying patches and
willing to recompile their kernel once a day. They are not suitable for
servers. Several times on testing machines, switching from a 2.6 to the
next one has caused bugs on PCI, acpi, networking and so on.

The direction is lost. How many patchsets for vanilla kernel exist?

Someone has decided that linux must go on desktops as well and
developing new magnificent features for desktop users is causing serious
problems to the ones who use linux at work on production servers.

2.4 tree is still the best solution for production.
2.6 tree is great for gentoo users who like gcc consuming all CPU
(maxumum respect to gentoo but I prefer debian)

Massimo Cetra

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

 \ /
  Last update: 2005-03-22 14:07    [W:0.102 / U:1.404 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site