The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: "Greg 'groggy' Lehey" <grog@lemis.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] /crp
Date: Wed, 7 Nov 2018 20:04:23 -0700	[thread overview]
Message-ID: <CANCZdfoX1i8R-LkB_mgkZ7Acj1c91psOC=XKdKD_Ha_gys9a3A@mail.gmail.com> (raw)
In-Reply-To: <20181107234037.GA3826@eureka.lemis.com>

[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]

On Wed, Nov 7, 2018 at 7:26 PM Greg 'groggy' Lehey <grog@lemis.com> wrote:

> On Wednesday,  7 November 2018 at 10:14:20 -0500, Clem Cole wrote:
> > On Wed, Nov 7, 2018 at 9:09 AM <ron@ronnatalie.com> wrote:
> >
> >> The DEC drivers just left off the last 72 sectors.   There was no
> >> provision using them for block replacement.
> >
> > Minor update -- *no dynamic replacement provision*.  There was a
> > standard alone utility called BAD144 that implemented DEC Standard
> > 144 (Bad Blocks).
>
> Yes, this was also present in early FreeBSD distributions.  I have a
> vague recollection that people warned against using it.
>

It was OK for the super-duper old IDE drives from the IBM/AT and 80386 era.
It was better for the ESDI drives because those tended to ship with a list
of bad blocks printed on the label (which was itself a carry over from the
MFM days). The MFM drives *did* have a DEC standard to list bad blocks and
reserve spare cylinders which was derived from the earlier rkXX drives.
bad144 was for the rkXX drives and then adopted, badly, for the newer
drives types and wasn't super-great by the time FreeBSD came along...

Warner

[-- Attachment #2: Type: text/html, Size: 1589 bytes --]

  reply	other threads:[~2018-11-08  6:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-06 17:09 Angelo Papenhoff
2018-11-06 19:22 ` ron
2018-11-06 19:25 ` ron
2018-11-06 21:51   ` Dave Horsfall
2018-11-07 12:18     ` ron
2018-11-07 15:14       ` Clem Cole
2018-11-07 23:40         ` Greg 'groggy' Lehey
2018-11-08  3:04           ` Warner Losh [this message]
2018-11-07 16:43     ` Paul Winalski
2018-11-08 16:55   ` Mary Ann Horton
2018-11-09  5:30     ` Lars Brinkhoff
2018-11-06 23:31 Norman Wilson
2018-11-07 15:08 ` Clem Cole
2018-11-07 23:30   ` Rob Pike

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CANCZdfoX1i8R-LkB_mgkZ7Acj1c91psOC=XKdKD_Ha_gys9a3A@mail.gmail.com' \
    --to=imp@bsdimp.com \
    --cc=grog@lemis.com \
    --cc=tuhs@tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).