The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: arrigo@alchemistowl.org (Arrigo Triulzi)
Subject: [TUHS] Why did PDPs become so popular?
Date: Sun, 31 Dec 2017 10:59:12 +0100	[thread overview]
Message-ID: <0890C038-B442-4F57-86AD-243D17D43F77@alchemistowl.org> (raw)
In-Reply-To: <CAEdTPBf40grB_nCqXgyB8-yJbJx3oCY7Yva9-W2PQQVCeH0qTw@mail.gmail.com>

On 31 Dec 2017, at 04:00, Henry Bent <henry.r.bent at gmail.com> wrote:
> I'm curious about this.  As far as I know the development of the released OS for the Alpha went this way:
> (OSF/1 reference) -> (OSF/1 for MIPS) -> OSF/1 V[1.2, 2, 3.0] -> Digital UNIX [3.2, 4] -> Tru64[5].  Was there ever a branch of this for the VAX?

Actually OSF/1 T1.0 was shipped to customers. I know because it was on the three Alphas we received at Imperial College in the UK. It also came with an early version of MX, the 32-bit MIPS to 64-bit Alpha translator which we used to get Ghostscript working (essential for our Mathematicians, after getting TeX to compile).

We tried to get Ghostscript ported as soon as the machines were up but failed miserably and were (still am, actually) grateful for MX saving the day.

Arrigo 


  reply	other threads:[~2017-12-31  9:59 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-29 16:38 Larry McVoy
2017-12-29 23:54 ` Kevin Bowling
2017-12-30  0:04   ` Larry McVoy
2017-12-30  0:54   ` Lawrence Stewart
2017-12-30  1:47     ` Kevin Bowling
2017-12-30  2:19       ` Lawrence Stewart
2017-12-30  2:35         ` Paul Winalski
2017-12-30  2:20       ` Paul Winalski
2017-12-31  2:47     ` Henry Bent
2017-12-30  1:07   ` Ron Natalie
2017-12-30  2:30     ` Paul Winalski
2017-12-31  3:00       ` Henry Bent
2017-12-31  9:59         ` Arrigo Triulzi [this message]
2017-12-31 15:55         ` Paul Winalski
  -- strict thread matches above, loose matches on Subject: below --
2017-12-31  5:20 Rudi Blom
2017-12-31 12:56 ` Clement T. Cole
2017-12-31 15:03   ` Steve Simon
2017-12-28 14:05 Noel Chiappa
2017-12-28 15:59 ` Paul Winalski
2017-12-28 16:08   ` Larry McVoy
2017-12-28 23:28     ` Theodore Ts'o
2017-12-29 11:04       ` Kevin Bowling
2017-12-29 23:35         ` Jon Forrest
2017-12-29 23:58           ` Larry McVoy
     [not found] <109152082.5216233.1514413535270.ref@mail.yahoo.com>
2017-12-27 22:25 ` Dave Ritchie
2017-12-27 22:32   ` Dave Horsfall
2017-12-27 23:44     ` Paul Winalski
2017-12-27 23:38   ` Kevin Bowling
2017-12-28  0:07     ` Paul Winalski
2017-12-28  0:45       ` Kevin Bowling
2017-12-28  1:39       ` Ron Natalie
2017-12-27 21:02 Alec Muffett
2017-12-27 21:50 ` Grant Taylor
2017-12-28  1:23   ` Alec Muffett
2017-12-27 21:51 ` Clem Cole
2017-12-27 21:52   ` Clem Cole
2017-12-28  2:14   ` Greg 'groggy' Lehey

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=0890C038-B442-4F57-86AD-243D17D43F77@alchemistowl.org \
    --to=arrigo@alchemistowl.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).