From: Clem Cole <clemc@ccc.com>
To: Ronald Natalie <ron@ronnatalie.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] /crp
Date: Wed, 7 Nov 2018 10:14:20 -0500 [thread overview]
Message-ID: <CAC20D2PkKf06Loh3_B_ze+qYt82qmYwfEWL7KOjxd98442QNkw@mail.gmail.com> (raw)
In-Reply-To: <218a01d47693$f83fd530$e8bf7f90$@ronnatalie.com>
[-- Attachment #1: Type: text/plain, Size: 777 bytes --]
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). What would happen is that the format was messed with the point a
bad block at on the reserved sectors.
This scheme caused nasty performance issues because seek schedualing was
defeated; and since UNIX did not originally obey DEC STD144, the standard
UNIX scheme in those days was buy 'perfect' media. BTW: the Ultrix team -
Fred Canter IIRC -- added support for BAD144, and I think DEC gave that
code to BSD evetually.
Clem
ᐧ
[-- Attachment #2: Type: text/html, Size: 2039 bytes --]
next prev parent reply other threads:[~2018-11-07 16:46 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 [this message]
2018-11-07 23:40 ` Greg 'groggy' Lehey
2018-11-08 3:04 ` Warner Losh
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=CAC20D2PkKf06Loh3_B_ze+qYt82qmYwfEWL7KOjxd98442QNkw@mail.gmail.com \
--to=clemc@ccc.com \
--cc=ron@ronnatalie.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).