From owner-freebsd-stable Sun Sep 28 08:39:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA09503 for stable-outgoing; Sun, 28 Sep 1997 08:39:06 -0700 (PDT) Received: from sabre.goldsword.com (sabre.goldsword.com [199.170.202.32]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA09480 for ; Sun, 28 Sep 1997 08:38:40 -0700 (PDT) Received: (from jfarmer@localhost) by sabre.goldsword.com (8.8.7/8.7.3) id LAA19834; Sun, 28 Sep 1997 11:41:08 -0400 (EDT) Date: Sun, 28 Sep 1997 11:41:08 -0400 (EDT) From: "John T. Farmer" Message-Id: <199709281541.LAA19834@sabre.goldsword.com> To: bde@zeta.org.au, jfarmer@sabre.goldsword.com, mdean@best.com Subject: Re: bad144 Cc: freebsd-stable@FreeBSD.ORG, jfarmer@goldsword.com Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 28 Sep 1997 20:39:18 +1000 Bruce Evans said: >>> Why use bad144 at all? It's a relic left over from the VAX/PDP-11 days... >>> Search the archives, this has come up several times. It the drive checks >>> good with the vendors utilities (for IDE and SCSI) then it's good. >>> >>> bad144 had it's day when drives _didn't_ do automatic bad block >>> replacement. >>> >>> John (Yes, I'm old enought to have had to deal with such beasts. >>> My first Unix box was a PDP-11/34 with Version 6.... And >>> _big_ RK-05 drives, all of 2.5mb each...) > >For FreeBSD, bad144 should only be necessary for MFM and ESDI drives. > >Bruce Smacks side of head. Of course! Most ESDI & MFM drives _didn't_ do bad-block replacement. (The last time I installed an Unix system on an ESDI drive was Xenix on a Dell 386/25. 386/33's had been shipping for all of a month...) John ------------------------------------------------------------------------- John T. Farmer Proprietor, GoldSword Systems jfarmer@goldsword.com Public Internet Access in East Tennessee dial-in (423)470-9953 for info, e-mail to info@goldsword.com Network Design, Internet Services & Servers, Consulting