The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: grog@lemis.com (Greg 'groggy' Lehey)
Subject: [TUHS] Some notes on running UNIX v6 in 2015, using SimH and a healthy dose of documentation
Date: Sat, 5 Dec 2015 09:36:18 +1100	[thread overview]
Message-ID: <20151204223618.GA91061@eureka.lemis.com> (raw)
In-Reply-To: <1F998DC4-275F-4DE1-81F2-CC19BE714A7A@ronnatalie.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1659 bytes --]

On Friday,  4 December 2015 at 13:17:58 -0500, Ronald Natalie wrote:
>
> I guess you???re going to have to qualify that.  It???s the oldest
> ???surviving??? (though it???s unclear what that means to a computer
> not running) STORED PROGRAM machine.

Guilty as charged.

> The ENIAC, which by some standards is the first programmable digital
> computer still exists at the Smithsonian.  Some of my coworkers there
> were on the team that took it down from BRL to the Smithsonian and
> actually tested it as operational when it was handed over to the
> museum.  I don???t think it???s ever been powered on since.

My understanding, which is borne out by the Wikipedia article, is that
only parts of ENIAC are on display at the Smithsonian.  It lists a
number of other places with parts.

But then there's yet another computer, the Zuse Z4 at the Deutsches
Museum in München.  Again from Wikipedia, it was built between 1942
and 1945, and thus predates ENIAC.  It seems that it's complete, but
of course it's not electronic.  So until proof of the contrary, CSIRAC
is the oldest surviving complete electronic computer.

Do I need more adjectives?

Greg
--
Sent from my desktop computer.
Finger grog at FreeBSD.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft MUA reports
problems, please read http://tinyurl.com/broken-mua
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20151205/68702d65/attachment.sig>


  parent reply	other threads:[~2015-12-04 22:36 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-02 21:37 Will Senn
2015-12-03  0:20 ` Warren Toomey
2015-12-03  2:37   ` Will Senn
2015-12-03  4:11     ` Dave Horsfall
2015-12-03  4:18       ` Will Senn
2015-12-03  6:05         ` Peter Jeremy
2015-12-03 12:59           ` John Cowan
2015-12-04  6:22           ` Dave Horsfall
2015-12-04  6:38             ` Greg 'groggy' Lehey
2015-12-04 14:52               ` John Cowan
2015-12-04 18:17                 ` Ronald Natalie
2015-12-04 18:33                   ` Gregg Levine
2015-12-04 22:36                   ` Greg 'groggy' Lehey [this message]
     [not found]                 ` <CAKt831GfmmKQ75TRy1tCmmbnx4CGLmjy12zns6-c+_oJB+h2dA@mail.gmail.com>
2015-12-04 19:13                   ` SZIGETI Szabolcs
2015-12-04 12:41             ` Peter Jeremy
2015-12-03 15:21 Noel Chiappa
2015-12-03 17:27 ` Random832
2015-12-03 18:46 ` Will Senn
2015-12-03 15:42 Noel Chiappa
2015-12-03 18:54 ` Will Senn
2015-12-04  0:52 ` Greg 'groggy' Lehey
2015-12-04 21:33   ` Win Treese
2015-12-04 22:00     ` John Cowan

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=20151204223618.GA91061@eureka.lemis.com \
    --to=grog@lemis.com \
    /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).