The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: rminnich@gmail.com (ron minnich)
Subject: [TUHS] lost ports
Date: Wed, 04 Jan 2017 21:24:37 +0000	[thread overview]
Message-ID: <CAP6exYLat4Xucfj7V99Ev8SeA8jV3NDA7axia6Ta=k+mr62Kiw@mail.gmail.com> (raw)

So there are a few ports I know of that I wonder if they ever made it back
into that great github repo.I don't think they did.

harris
gould
That weird BBN 20-bit machine
   (20 bits? true story: 5 4-bit modules fit in a 19" rack. So 20 bits)
Alpha port (Tru64)
Precision Architecture
Unix port to Cray vector machines

others? What's the list of "lost machines" look like? Would companies
consider a donation, do you think?

If that Cray port is of any interest I have a thread I can push on maybe.

but another true story: I visited DEC in 2000 or so, as LANL was about to
spend about $120M on an Alpha system. The question came up about the SRM
firmware for Alpha. As it was described to me, it was written in BLISS and
the only machine left that could build it was an 11/750, "somewhere in the
basement, man, we haven't turned that thing on in years". I suspect there's
a lot of these containing oxide oersteds of interest.

ron
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170104/74fb2664/attachment.html>


             reply	other threads:[~2017-01-04 21:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-04 21:24 ron minnich [this message]
2017-01-04 21:41 ` Ron Natalie
2017-01-04 21:58 ` Larry McVoy
2017-01-05  1:52   ` Larry McVoy
2017-01-04 22:01 ` Robert Swierczek
2017-01-04 22:01 ` Dan Cross
2017-01-05 16:01 ` Clem Cole
2017-01-05 16:20   ` Clem Cole
2017-01-05 17:23   ` ron minnich
2017-01-05 19:08     ` Clem Cole
2017-01-05 19:16       ` ron minnich
2017-01-05 20:08         ` Clem Cole
     [not found]           ` <E3DA30C5-7227-4143-8DA1-401A161C74C6@gmail.com>
     [not found]             ` <CAP6exYLvXvtGEWSg_t5bqjJwunGKC1xiiaoLj7yb5QxkHsMvuA@mail.gmail.com>
2017-01-05 23:40               ` Lawrence Stewart
2017-01-05 16:15 ` Derek Fawcus
2017-01-05 18:34   ` Pierre DAVID
2017-01-05 12:28 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='CAP6exYLat4Xucfj7V99Ev8SeA8jV3NDA7axia6Ta=k+mr62Kiw@mail.gmail.com' \
    --to=rminnich@gmail.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).