From: Dave Horsfall <dave@horsfall.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: /usr/mdec
Date: Mon, 21 Nov 2022 15:25:43 +1100 (EST) [thread overview]
Message-ID: <alpine.BSF.2.21.9999.2211211521220.95052@aneurin.horsfall.org> (raw)
In-Reply-To: <27941134744AD184AC73F12C29DE3471.for-standards-violators@oclsc.org>
On Sun, 20 Nov 2022, Norman Wilson wrote:
> I'm curious about the origin of the directory name /usr/mdec. (I am
> reminded of it because I've noticed that it lives on in at least one of
> the BSDs.)
>
> I had a vague notion that it meant `DEC maintenance' but that seems a
> bit clumsy to describe a place holding boot blocks.
As far as I know, that's right; MAINDEC was certainly on all of their
standalone diagnostic media (a beauty was DECEX, which thrashed the PDP-11
and uncovered a bug in our RK-11 controller; it screwed up on overlapped
seeks which RSX didn't use but Harvard(?) did, so DEC's view was that it
was obviously a Unix problem).
-- Dave
next prev parent reply other threads:[~2022-11-21 4:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 3:11 [TUHS] /usr/mdec Norman Wilson
2022-11-21 4:25 ` Dave Horsfall [this message]
2022-11-21 9:56 ` [TUHS] /usr/mdec Angelo Papenhoff
2022-11-21 18:43 Noel Chiappa
2022-11-21 21:11 ` Dave Horsfall
2022-11-27 2:22 Rudi Blom
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=alpine.BSF.2.21.9999.2211211521220.95052@aneurin.horsfall.org \
--to=dave@horsfall.org \
--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).