From owner-freebsd-current Wed Nov 24 1:40: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 1809715001 for ; Wed, 24 Nov 1999 01:39:53 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id KAA33803 for ; Wed, 24 Nov 1999 10:39:44 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: ST-506, ESDI and BAD144 ? From: Poul-Henning Kamp Date: Wed, 24 Nov 1999 10:39:44 +0100 Message-ID: <33801.943436384@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sørens new ATA driver can handle all IDE disks as far as has been tested now, but it doesn't provide bad sector remapping which is needed for ESDI and ST-506 disks. Having two drivers fight for the same class of drivers is a rather messy process, and it complicates the code a fair bit, not to mention the clutter in end-user documentation. Considering that most of the machines with ST-506 and ESDI disks are limited to 16MB ram anyway, I think it would be reasonable to simply tell the users of these old irons to stick with the 3.X branch until end of life (there is probably at least 1.5 years more life in the 3.X branch judging from the history of the 2.2.X branch). So I would like to propose that we discontinue support for ST-506, ESDI disks and BAD144 bad-sector remapping starting with the 4.0 release. So, is anyone running -current on ESDI or ST-506 disks in actual applications (as opposed for the gadget/novelty thrill or testing purposes) ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message