From: norman@oclsc.org (Norman Wilson)
To: tuhs@tuhs.org
Subject: [TUHS] /usr/mdec
Date: Sun, 20 Nov 2022 22:11:30 -0500 (EST) [thread overview]
Message-ID: <27941134744AD184AC73F12C29DE3471.for-standards-violators@oclsc.org> (raw)
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.
A random web board suggests it meant `magnetic DECtape.'
That's certainly not true by the time I came along, when it
contained the master copy of the disk boot block(s).
But I suppose it could have meant that early on and
the name just carried forward.
A quick skim of the V1-V7 manuals doesn't explain the name.
Anyone have any clearer memories than I do? Doug or Ken or
anyone who was there when it was coined, do you still recall?
Norman Wilson
Toronto ON
next reply other threads:[~2022-11-21 3:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 3:11 Norman Wilson [this message]
2022-11-21 4:25 ` [TUHS] /usr/mdec Dave Horsfall
2022-11-21 9:56 ` Angelo Papenhoff
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=27941134744AD184AC73F12C29DE3471.for-standards-violators@oclsc.org \
--to=norman@oclsc.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).