Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262007AbVADDcm (ORCPT ); Mon, 3 Jan 2005 22:32:42 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262000AbVADDcl (ORCPT ); Mon, 3 Jan 2005 22:32:41 -0500 Received: from out006pub.verizon.net ([206.46.170.106]:17332 "EHLO out006.verizon.net") by vger.kernel.org with ESMTP id S262007AbVADDci (ORCPT ); Mon, 3 Jan 2005 22:32:38 -0500 From: Gene Heskett Reply-To: gene.heskett@verizon.net Organization: Organization: None, detectable by casual observers To: linux-kernel@vger.kernel.org Subject: Re: starting with 2.7 Date: Mon, 3 Jan 2005 22:32:36 -0500 User-Agent: KMail/1.7 Cc: Bill Davidsen , Jesper Juhl , Horst von Brand , "Theodore Ts'o" , Adrian Bunk , Diego Calleja , Willy Tarreau , wli@holomorphy.com, aebr@win.tue.nl, solt2@dns.toxicfilms.tv References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200501032232.36606.gene.heskett@verizon.net> X-Authentication-Info: Submitted using SMTP AUTH at out006.verizon.net from [151.205.52.185] at Mon, 3 Jan 2005 21:32:37 -0600 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2642 Lines: 54 On Monday 03 January 2005 19:02, Bill Davidsen wrote: [...] >Somewhere there is a pawn shop with only one big brass ball, and I > know where the other two are... Yeah, well, one does get used to carrying them around after a while Bill. Not quite in this context, but I have been asked how in hell I can sit so comfortably by witnesses, after just having torn some $10k piece of broadcast gear down, and then put it back together again, and it works when I'm done, something it didn't do whan I started... And thats what it does take sometimes, big (brass?) balls. And thats what keeps me lurking here and playing with new kernels all the time at age 70. Currently running 2.6.10-ac2. But, I have to agree with the general tone of this thread, we do not IMO have, as 2005 opens up, a kernel code base that runs on everything its supposed to run on, not by a long shot. And to apply the 'stable' label to this is stretching the point like a used car salesman selling a 49 nash. Don't get me wrong either, I choose to do this and generally speaking I'm having a lot of fun trying to keep up with the various new kernels. And if something doesn't work, you all hear from me fairly quick, and thats how stability is achieved, by folks like me taking the chance and getting burnt. I may not know how to fix it cause this ain't an amiga anymore, but I can be the remote hands to furnish the clues those of you who do code in your sleep can fix. Its moving way too fast in terms of new features to ever get to a 'stable' point, and I think it is now time to fork things off into a 2.7 tree, while 2.6 continues on till the individual distros don't have the huge menu of patches they are now applying to their own kernels, as everything worth doing in 2.6 has made it to the kernel.org downloadable code by the time it gets to 2.6.20 or so. And thats what I'd call stable, stable like the 2.4.20-sthg-or-other-ck6 I've been running on my firewall box for years. It 'just works' in between hardware glitches... -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) 99.31% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2004 by Maurice Eugene Heskett, all rights reserved. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/