The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: rudi.j.blom@gmail.com (Rudi Blom)
Subject: [TUHS] Why did PDPs become so popular?
Date: Sun, 31 Dec 2017 12:20:06 +0700	[thread overview]
Message-ID: <CAMYpm85uJvDK6rdKUu9G5hDFThtuTv0tJRmUbw-MjJe0774e_w@mail.gmail.com> (raw)

A bit off the PDPs, but to do a minor correction on mail below

The commercial version of 'UNIX' on Alpha was maybe first called
Digital Unix OSF/1, but quickly changed to Digital Unix at least with
v3 and v4.0 (A - G). From there we had a 'break' which only in part
was due to take over by Compaq and we had Tru64 UNIX v5.1A and V5.1B.
The V5.1B saw updates till B-6.

As for the Digital C compiler, I'm still using
 DTCCMPLR650  installed  Compaq C Version 6.5 for Compaq Tru64 UNIX Systems

When I get some old source (some even developed on SCO UNIX 3.2V4.2) I
like to run it through all compiler /OS-es I got handy. With the
Compaq C compiler and HP-UX ANSI C I mostly get pages of warning and a
few errors. By the time I 'corrected' what I think is relevant some
nasty coredumps tend to disappear :-)

Compile for a better 2018,
uncle rubl

>Date: Fri, 29 Dec 2017 21:30:11 -0500.
>From: Paul Winalski <paul.winalski at gmail.com>
>To: Ron Natalie <ron at ronnatalie.com>
>Cc: TUHS main list <tuhs at minnie.tuhs.org>
>Subject: Re: [TUHS] Why did PDPs become so popular?
>Message-ID:     <CABH=_VRwNXUctFPav5rHX83wfUS0twMQuBhinRZ6QEY1cB3TNQ at mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
>
>On 12/29/17, Ron Natalie <ron at ronnatalie.com> wrote:
> The Alpha was hot
> stuff for about nine months.   Ran OSF/1 formerly DigitalUnix formerly
> OSF/1.

>Digital UNIX for the VAX was indeed derived from OSF/1.  The port to
>Alpha was called Tru64 UNIX.

>Tru64 UNIX was initially a pure 64-bit system, with no provision for
>building or running 32-bit program images.  This turned out to be a
>mistake .  DEC found out that a lot of ISVs had code that implicitly
>"knew" that sizeof() a pointer was the same as sizeof(int) was the
>same as 4 bytes.  Tru64 was forced to implement a 32-bit compatibility
>mode.

>There was also a problem with the C compiler initially developed at
>DECwest in Seattle.  It supported ONLY ANSI standard C and issued
>fatal errors for violations/extensions of the standard.  We (DEC
>mainstream compiler group) called it the Rush Limbaugh
>compiler--extremely conservative, and you can't argue with it.


             reply	other threads:[~2017-12-31  5:20 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-31  5:20 Rudi Blom [this message]
2017-12-31 12:56 ` Clement T. Cole
2017-12-31 15:03   ` Steve Simon
  -- strict thread matches above, loose matches on Subject: below --
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
2017-12-31 15:55         ` Paul Winalski
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=CAMYpm85uJvDK6rdKUu9G5hDFThtuTv0tJRmUbw-MjJe0774e_w@mail.gmail.com \
    --to=rudi.j.blom@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).