Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 19 Aug 2002 10:00:58 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 19 Aug 2002 10:00:58 -0400 Received: from louise.pinerecords.com ([212.71.160.16]:7947 "EHLO louise.pinerecords.com") by vger.kernel.org with ESMTP id ; Mon, 19 Aug 2002 10:00:57 -0400 Date: Mon, 19 Aug 2002 16:04:43 +0200 From: Tomas Szepe To: Dana Lacoste Cc: Jan-Benedict Glaw , linux-kernel@vger.kernel.org Subject: Re: IDE? Message-ID: <20020819140443.GA25789@louise.pinerecords.com> References: <20020817181624.GM10730@lug-owl.de> <1029765431.32209.77.camel@dlacoste.ottawa.loran.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1029765431.32209.77.camel@dlacoste.ottawa.loran.com> User-Agent: Mutt/1.4i X-OS: GNU/Linux 2.4.19-pre10/sparc SMP X-Uptime: 75 days, 22:25 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 636 Lines: 14 > Are there not several uses of 2.0.x that are not compatible with > 2.2/2.4? And if 2.0 is working, then why are you worried about > being able to use 3.2? Why do we need to maintain compatibility > with OLD (not 'low-end' but OLD) hardware if there's an existing > kernel that meets that hardware's needs already? Because new userspace won't roll with old kernels (reliably|at all). T. - 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/