From owner-freebsd-hackers Fri Apr 4 17:20:24 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA14281 for hackers-outgoing; Fri, 4 Apr 1997 17:20:24 -0800 (PST) Received: from bookcase.com (root@notes.bookcase.com [207.22.115.2]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA14273 for ; Fri, 4 Apr 1997 17:20:16 -0800 (PST) Received: from localhost (chadf@localhost) by bookcase.com (8.8.5/8.7.3) with SMTP id TAA17720 for ; Fri, 4 Apr 1997 19:23:55 -0500 (EST) Date: Fri, 4 Apr 1997 20:23:54 -0400 (EST) From: "Chad M. Fraleigh" X-Sender: chadf@notes To: hackers@FreeBSD.ORG Subject: Re: Code maintenance In-Reply-To: <19970402211157.WU57156@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Yes, aic(4) and ft(4) still work, more or less. We'd probably have > removed them otherwise. But in particular ft(4) suffers from a not > very elegant design, and its unmaintained state resulted in it being > almost worthless over time, since it doesn't handle the more modern > drives that are available now at all. If it remains unmaintained, the > day will come when all the previously existing drives it used to > support on the earth are dead. I was once doing a little work on trying to fix the ft driver (ok, more like rewrite the whole thing). But to do so the way I wanted would of required rewritting half the fdc/fd code into independent, generalized moduals (like the scsi ones). Of course in the process it would of broke the floppy drive (at least for awhile) and annoyed many, many people. Just what I need.. an electronic linch mob after me. ;) Eventually somebody else said they wanted to work on it, and since I didn't have the time, and no docs (was doing it by reverse enginering the current source with *alot* of guess work), I just gave up. Anyway.. now I'm working on a way to trace kernel memory leaks. -Chad