From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: coff@tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: [COFF] More LCM fallout
Date: Sat, 13 Jul 2024 09:17:16 -0400 (EDT) [thread overview]
Message-ID: <20240713131716.A741818C075@mercury.lcs.mit.edu> (raw)
I just noticed this:
Sep 2018: The Multics History Project Archives were donated to the Living
Computer Museum in Seattle. This included 11 boxes of tapes, and 58 boxes of
Multics and CTSS documentation and listings. What will happen to these items
is unknown.
https://multicians.org/multics-news.html#events
That last sentence is ironic; I _assume_ it was written before the recent news.
I wonder what will happen to all such material at the LCM. Anyone know?
Noel
next reply other threads:[~2024-07-13 13:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-13 13:17 Noel Chiappa [this message]
2024-07-27 21:18 ` [COFF] " Chris Hanson
2024-07-28 18:04 ` Aron Insinga
2024-07-29 3:14 ` Charles Anthony
2024-07-31 22:24 ` Chris Hanson
2024-08-01 6:22 ` Lars Brinkhoff
2024-08-30 21:50 ` Dan Halbert
2024-08-30 22:09 ` John Levine
2024-09-02 2:21 ` Chris Hanson
2024-09-02 9:45 ` John R Levine
2024-09-08 17:39 ` Grant Taylor via COFF
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=20240713131716.A741818C075@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.edu \
--cc=coff@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).