From owner-freebsd-current Wed Oct 16 13:46:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA04342 for current-outgoing; Wed, 16 Oct 1996 13:46:51 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA04334; Wed, 16 Oct 1996 13:46:45 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id WAA00930; Wed, 16 Oct 1996 22:45:57 +0200 (MET DST) To: Garrett Wollman cc: current@FreeBSD.org Subject: Re: scsi drives left locked by shutdown In-reply-to: Your message of "Wed, 16 Oct 1996 16:30:01 EDT." <9610162030.AA03123@halloran-eldar.lcs.mit.edu> Date: Wed, 16 Oct 1996 22:45:57 +0200 Message-ID: <928.845498757@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In message <9610162030.AA03123@halloran-eldar.lcs.mit.edu>, Garrett Wollman wri tes: >< >said: > >> Your one-month deadline for coming up with either a finished >> implementation or a bit of documentation about the intentions >> was gracefully extended to more than 6 months before devconf >> was taken out behind the barn and shot. > >And what have you done to replace it? You should have bloody well >LEFT IT ALONE until you had written the replacement. (You certainly >haven't demonstrated that it somehow was never useful or necessary.) I have talked with various people about the problem (who all agreed to the removal btw) and we have some good ideas, and we will probably find a good solution when we have time. In the meantime your code doesn't prevent people from thinking about it and toying with it, and it doesn't infect all our kernel sources with a bunch of unreadable code. I'm about to zap the isdn stuff for exactly the same reason. People sit there looking at it, expecting it to evolve and it's dead. >> I have sent you my preliminary comments on your document about >> a replacement > >You sent me one comment, about it being too complex for you. Well that was more than 3 times longer than your standard reply: "NO!!!!" (I'm sorry if I got it wrong, I'm not sure if you use 3 or 4 '!'s) >You have >not sent me a single USEFUL reply, and so far as I can tell, nobody >else has even bothered to look at it. Well, we're more alike than I thought then. >I have no intention of actually /writing/ >that replacement; I'll stick to my networking and leave device >configuration up to you and Justin. A wise decision that will undoubtedly help our networking code. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so.