From owner-freebsd-current Thu Nov 25 12:30: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id BC1BA14A1B for ; Thu, 25 Nov 1999 12:29:59 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40323>; Fri, 26 Nov 1999 07:22:49 +1100 Content-return: prohibited Date: Fri, 26 Nov 1999 07:29:48 +1100 From: Peter Jeremy Subject: Re: ST-506, ESDI and BAD144 ? In-reply-to: <19991125130920.10078@mojave.sitaranetworks.com> To: Greg Lehey Cc: current@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Nov26.072249est.40323@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii References: <33801.943436384@critter.freebsd.dk> <19991125130920.10078@mojave.sitaranetworks.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Nov-26 05:09:20 +1100, Greg Lehey wrote: >I don't suppose it would be that big a deal to remove the old driver, >but what speaks against leaving it in the tree along with a comment in >the GENERIC config file saying "if you use antediluvial disk hardware, >you may prefer to use an old driver too"? The primary problem I can see is bitrot. There seem to be a number of fairly intrusive architecture changes coming up - block/character device merging, CardBus, `proper' thread support and SMP improvements. The WD driver will presumably live long enough to see the end of the block/character merge. The other changes seem further off, but have the potential to require changes to all drivers. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message