The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: aki@insinga.com
To: George Michaelson <ggm@algebras.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>, simh@groups.io
Subject: [TUHS] Re: Sad but not unexpected news about the LCM-L
Date: Wed, 26 Jun 2024 12:22:39 -0500	[thread overview]
Message-ID: <9e2458fb146d6e3d23bf940069193380@insinga.com> (raw)
In-Reply-To: <CAKr6gn2Yn-W0Fepec=1yqrhyO1Hm0MeTACpESyoU9t5q6EpBLg@mail.gmail.com>

They did, in one of DEC's buildings in Marlborough, Massachusetts: The 
Digital Computer Museum dba The Computer Museum.  Later it moved to 
Boston in the same building as the Children's Museum there; space that 
was used by an automobile museum for a while.  After the End of the Age 
of Minicomputers, it moved to California and eventually became the 
Computer History Museum.  MIT Lincoln Lab took back the TX-0 and 
disassembled it to some extent so that it could be moved and put into 
storage, where it sits, in a classified facility which we mere insecure 
civilians can't access.  A few things were on display in The Science 
Museum in Boston (it inherited the Massachusetts non-profit organization 
of TCM IIUC) but I think they've been moved to CHM too.  And at least 
some of those giants have now passed away too.

And make that an actually *endowed* museum.  I've been reminded that 
Allen also created a Science Fiction Museum and a Rock & Roll Museum.  
The SF has been merged into the R&R because that's the one that will 
probably sell enough tickets to keep paying the bills and the staff.

- Aron



On 2024-06-25 20:42, George Michaelson wrote:
...
> You would think somebody in Maynard would fund oh, I don't know.. an
> old Mill structure to be repurposed as a museum? Or many in Armonk?
> 
> The Indy "this belongs in a museum" really needs a rider: A nationally
> recognized, affiliated, publicly endowable museum.
...


  reply	other threads:[~2024-06-26 17:22 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-25 18:17 [TUHS] " Clem Cole
2024-06-26  0:56 ` [TUHS] " Aron Insinga
2024-06-26  1:29   ` Larry McVoy
2024-06-26  3:34     ` [TUHS] Re: Trust stuff, " John Levine
2024-06-26  9:22     ` [TUHS] Wills. (Was: Sad but not unexpected news about the LCM-L) Ralph Corderoy
2024-06-26  1:42 ` [TUHS] Re: Sad but not unexpected news about the LCM-L George Michaelson
2024-06-26 17:22   ` aki [this message]
2024-06-26  1:44 ` Paul Guertin
2024-06-26  1:46   ` Dan Cross
2024-06-26  2:46     ` Paul Guertin
2024-06-26  5:36     ` Lars Brinkhoff
2024-06-26 14:30       ` [TUHS] Planning for the future was " Will Senn
2024-06-26 15:18         ` [TUHS] " Al Kossow
2024-06-26 21:57         ` [TUHS] Re: Planning for the future Warren Toomey via TUHS
2024-06-30 13:05           ` Will Senn
2024-06-26 16:56       ` [TUHS] Re: Sad but not unexpected news about the LCM-L aki
2024-06-25 18:45 Noel Chiappa
2024-06-25 18:53 ` Al Kossow
2024-06-27 15:19 Noel Chiappa
2024-06-27 17:06 ` Al Kossow
2024-06-27 17:32   ` John Levine

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=9e2458fb146d6e3d23bf940069193380@insinga.com \
    --to=aki@insinga.com \
    --cc=ggm@algebras.org \
    --cc=simh@groups.io \
    --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).