From owner-freebsd-hackers Thu Feb 5 19:30:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA10725 for hackers-outgoing; Thu, 5 Feb 1998 19:30:45 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fledge.watson.org (root@FLEDGE.RES.CMU.EDU [128.2.91.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA10704 for ; Thu, 5 Feb 1998 19:30:34 -0800 (PST) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.6.10) with SMTP id WAA20419; Thu, 5 Feb 1998 22:29:36 -0500 (EST) Date: Thu, 5 Feb 1998 22:29:35 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Mike Smith cc: alk@pobox.com, hackers@FreeBSD.ORG Subject: Re: wd0s1e hard errors In-Reply-To: <199802060033.LAA01638@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe hackers" On Fri, 6 Feb 1998, Mike Smith wrote: > > Should bad144 be retired? > > I get the distinct feeling that the time has prettymuch come for this, > yes. It's only real use is for old 'wd' disks, most of whom are dead > and gone. > > Killing it from the boot floppy in particular would win us some more > space. Hey! :) My Kerberos server is running quite happily on a hard disk that I have had for the last 9 or 10 years. Great drive -- all of my Maxtors have lasted really well. It has one or two bad sectors, but has had those for at least 4 years. I keep backups of important data, but have had no problems. Bad144 on a boot-floppy for install seems quite necessary to me. If we do retire it from a boot floppy, maybe we should have an "old install floppy" that supports bad144, etc, but skips out on PCI support, for example. It may be a more fair assumption that PCI-based machines won't need bad144, but my old 386 does. :) As to why I kept the machine? A Kerberos server just does a little DES, and why fix something that is clearly not broken? Robert N Watson Carnegie Mellon University http://www.cmu.edu/ SafePort Network Services http://www.safeport.com/ robert@fledge.watson.org http://www.watson.org/~robert/