The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Angelo Papenhoff <aap@papnet.eu>
To: tuhs@tuhs.org
Subject: [TUHS] Re: /usr/mdec
Date: Mon, 21 Nov 2022 10:56:29 +0100	[thread overview]
Message-ID: <Y3tLTflF/BC7y9Sz@indra> (raw)
In-Reply-To: <27941134744AD184AC73F12C29DE3471.for-standards-violators@oclsc.org>

I was also wondering! My theory was that it stands for Magtape & DECtape,
but not sure. Perhaps ken remembers?

aap

On 20/11/22, 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.
> 
> 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

  parent reply	other threads:[~2022-11-21  9:57 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 ` [TUHS] /usr/mdec Dave Horsfall
2022-11-21  9:56 ` Angelo Papenhoff [this message]
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=Y3tLTflF/BC7y9Sz@indra \
    --to=aap@papnet.eu \
    --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).