Subject: Re: [2.6 patch] the scheduled removal of the obsolete raw driver
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Adrian Bunk <bunk@stusta.de>
Cc: "Chen, Kenneth W" <kenneth.w.chen@intel.com>,
       "'Andrew Morton'" <akpm@osdl.org>, linux-kernel@vger.kernel.org,
       Badari Pulavarty <pbadari@us.ibm.com>
In-Reply-To: <20060121010229.GP31803@stusta.de>
References: <20060118194103.5c569040.akpm@osdl.org>
	 <200601190543.k0J5hBg06542@unix-os.sc.intel.com>
	 <20060121010229.GP31803@stusta.de>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: Sat, 21 Jan 2006 01:49:17 +0000
Message-Id: <1137808158.24161.64.camel@localhost.localdomain>
Mime-Version: 1.0
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 984
Lines: 25

On Sad, 2006-01-21 at 02:02 +0100, Adrian Bunk wrote:
> Why did noone tell me anythong about such issues although I'm the one 
> listed as having this driver deprecated?

Because they don't spend their lives tracking the base kernel, they
expect sanity to prevail and their idea of an obsolescence cycle is
about five years.

ISV = "Independant software vendor"

Obsoleting stuff which is distribution internal configuration type stuff
(eg devfs->udev) is one thing but core syscall related stuff has to
undergo a much much longer cycle, or in many cases you just have to look
at it and treat it as a lesson for the future and a thing to tackle in
whatever OS obsoletes Linux.

Thats why 0.98.5 libc 2.2 and rogue still work on 2.6.

Alan

-
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/