The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: David Arnold <davida@pobox.com>
To: Jon Forrest <nobozo@gmail.com>
Cc: TUHS@minnie.tuhs.org
Subject: Re: [TUHS] Unix on DEC AlphaServer 4000
Date: Sun, 20 Sep 2020 07:56:53 +1000	[thread overview]
Message-ID: <F18FEA73-4BC8-4F50-8EC3-17124CBF682C@pobox.com> (raw)
In-Reply-To: <58699dd0-5477-2fe4-5435-ccadeebed821@gmail.com>

I worked at a Digital-sponsored lab in Australia from the early 90’s. DEC offered us a great deal on DEC 3000-era workstations, replacing all our Ultrix DECstations in (I think) 1994.

At that point, very little of the freely available software would build cleanly for 64 bit platforms. Even the stuff with Cray support often didn’t work with OSF/1’s 32 bit int/64 bit long model. 

And pthreads was a mess, with all the Unix-like systems having implementations of different drafts that were incompatible. 

After a while Digital started redistributing a “freeware” collection of suitably patched versions to bootstrap everyone’s workflows. 




d


> On 19 Sep 2020, at 14:34, Jon Forrest <nobozo@gmail.com> wrote:
> 
> 
> 
>> On 9/18/2020 8:26 PM, Paul Riley wrote:
>> I have an opportunity to buy a DEC AlphaServer. Is there a version of Unix which will run on this?
> 
> Absolutely! The CS Dept. at UC Berkeley got some of the first Alphas
> released by DEC back in the 90s (I don't remember the exact dates).
> We ran OSF/1 (a.k.a. Digital Unix, a.k.a other names). In fact, what
> became PostgreSQL was developed on Alphas running that Unix.
> 
> Jon
> 


  reply	other threads:[~2020-09-19 22:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-19  3:26 Paul Riley
2020-09-19  4:19 ` Rico Pajarola
2020-09-19  4:26 ` Nelson H. F. Beebe
2020-09-19 17:45   ` Clem Cole
2020-09-19 19:42     ` John Gilmore
2020-09-19  4:27 ` Adam Thornton
2020-09-19  4:33 ` Jon Forrest
2020-09-19 21:56   ` David Arnold [this message]
2020-09-20  5:29 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=F18FEA73-4BC8-4F50-8EC3-17124CBF682C@pobox.com \
    --to=davida@pobox.com \
    --cc=TUHS@minnie.tuhs.org \
    --cc=nobozo@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).