Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 9 Oct 2001 16:14:32 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 9 Oct 2001 16:14:22 -0400 Received: from dfw-smtpout3.email.verio.net ([129.250.36.43]:31384 "EHLO dfw-smtpout3.email.verio.net") by vger.kernel.org with ESMTP id ; Tue, 9 Oct 2001 16:14:03 -0400 Message-ID: <3BC35A71.9F783868@bigfoot.com> Date: Tue, 09 Oct 2001 13:13:37 -0700 From: Tim Moore Organization: Yoyodyne Propulsion Systems, Inc. X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.2.20p10i i686) X-Accept-Language: en MIME-Version: 1.0 To: linux-kernel@vger.kernel.org CC: Bill Davidsen Subject: Re: Breaking system configuration in stable kernels In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Bill Davidsen wrote: > > I've beaten this dead horse before, but Linux will not look to > management like a viable candidate for default o/s until whoever releases > new versions of *stable* kernel series with cosmetic changes which break > existing systems running earlier releases of the same stable kernel > series. > > [cmpci module stuff] > > I love getting problems like this on my vacation, I'm pissed, and I > really think it indicates a lack of attention to detail. I think I saw I wouldn't use a new release of Windows or OSF/1 or Digital Unix or Solaris in a commercial situation and linux is no different. In this case [cmpci] it sounds like some user's desktop which is also asking for problems. Having it visible to management is just too much risk regardless of the os. Stick with distribution OR 2.2.x (2.2.19pre2 or higher) kernels. rgds, tim. -- - 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/