[lkml]   [2003]   [Aug]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: linux-2.2 future?
On 26 Aug 2003, Alan Cox wrote:

> On Llu, 2003-08-25 at 17:42, Marc-Christian Petersen wrote:
> > like .21 and .22 IDE code is, but it works very very smooth and nice and rock
> > solid. We use the 2.2-secure tree for almost all customers in my company.
> > Biggest harddisk is a 160GB Maxtor IDE disk.
> The problem is that change breaks stuff. a lot of the 2.2 users will
> happily trade lack of LBA48 support for stability and predictability.
> Thats why I took a basically "if its not a serious bugfix its not going
> in" approach

As a 2.2 user, I have to agree with this sentiment.

Just as Rome wasn't built in a day, 2.2 didn't get as stable as it is
overnight. Unfortunately, any change now risks subtley destabilizing 2.2
for some obscure case somewhere. Such destabilization could literally
happen overnight {:-(

OTOH, some users may find that the stability of 2.2 combined with some
other feature(s) (be it LBA48/IPSec/whatever (in my case it's MPPE from
-secure + a timer hack)) works just fine for them.

I.e. we can be well-served by a very stable "official" 2.2 tree which is
supplemented by the likes of MCP's -secure patchset, and others.

Perhaps the middle ground is to keep the 2.2 kernel pretty much as-is
(modulo bugfixes) and include pointers to optional patch(sets)? That's
certainly more palatable than people maintaining patch-reversions to
retain their stability!

Worse still, as is too often the case, feature updates may provoke some
2.2 users to NOT upgrade (and hence miss security fixes) lest they
compromise stability.

HTH and many thanks for your contributions,

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 13:48    [W:0.163 / U:1.908 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site