From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: tuhs@tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: [TUHS] Re: /usr/mdec
Date: Mon, 21 Nov 2022 13:43:48 -0500 (EST) [thread overview]
Message-ID: <20221121184348.33A7118C087@mercury.lcs.mit.edu> (raw)
> From: Dave Horsfall
> MAINDEC was certainly on all of their standalone diagnostic media
Actually, it was the name for all their diagnostics (usually stand-alone),
dating back to the paper tape days - when that was the only form they were
distributed in. So it makes sense that it's a short form of 'MAINDEC'.
Noel
next reply other threads:[~2022-11-21 18:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 18:43 Noel Chiappa [this message]
2022-11-21 21:11 ` Dave Horsfall
-- strict thread matches above, loose matches on Subject: below --
2022-11-27 2:22 Rudi Blom
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
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=20221121184348.33A7118C087@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.edu \
--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).