The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: alan@alanlee.org
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] The John Snow's of the UNIX family
Date: Wed, 16 Jan 2019 10:44:08 -0500	[thread overview]
Message-ID: <CAC20D2OAi-5KXBHT454PJSNb00Z=o8vXbC9ke5COQNwdrKjS+g@mail.gmail.com> (raw)
In-Reply-To: <f6021eda609b1b820d4c0350abd028c8@alanlee.org>

[-- Attachment #1: Type: text/plain, Size: 3204 bytes --]

Let me see if I can illuminate from a little I was aware.  I know some of
the histories from my time at Locus when DG was a customer of ours.
 Although, I'm going to show my old f*rt, cultural illiteracy (not a TV
person) by having no idea who 'John Snow' is, so I can not comment on that
reference ;-)

I think you are right that some of the histories tend to tided to people's
experience at their college or universities and I'm not sure how well DG
sold in those markets.  Plus they bet on Moto, who fumbled with the 68000
replacement (88k), compared to IBM's PPC and later Intel's remarkable
recovery with the 386.  Since they joined the losing side of the chip war,
I suspect that also hurt them, even though the system was actually well
done.

At one time I had access to the sources of DG/UX and yes you are correct it
was very clean and easy to understand (and fairly well documented).   At
the time, we (LCC) had the sources to DG/UX, Ultrix, Tru64, OSF/1, SunOS,
Solaris, HP-UX, AIX, Prime, as well as all of the AT&T releases.  (The
management at Locus used to say we were the Swiss of the UNIX industry  -
we sold arms to all the sides of the war).

As for  DG/UX, their kernel seemed like it was a rewrite (I never knew how
much of it was the SW folks in NC (who had been building their failed
"Fountainhead" system that the Soul-Of-The-New-Machine book talks about,
and how much was the MA folks that did Clarion later on).  It was
definitely the sanest of all of the UNIX kernels we had access and had the
least amount of cruft in it of the commercial systems.  The locking scheme
was the one of the cleanest, I ever saw (Stellar's Stellix was the only one
that was as good, IMO).  The memory system was really impressive.  I
remember when we were doing the TNC distributed FS work that what would
become the TruCluster FS for DEC at the same time.   The DG/UX version was
the simplest (and the HP/UX version the most twisted confused).

I'm now mixing up the differences in my mind, but I think I remember DG/UX
had some sort of file system stacking scheme at the inode level.  I'm not
sure if it ever shipped, but we worked on a Union file system for them;
that I remember was very cool (Plan9ish in splicing file system namespaces
together).   I seem to remember it was all made possible because of the
lower level memory scheme.   But I might be mixing that up with one of the
systems we were hacking (it was definately not OSF/1 or its child Tru64).

As you said, the user space API was basically System V, but DG did support
a lot of BSDism also; so bringing networking code from 4.2/4.3 was not
terrible; although since it was not fish or fowl, you had to be careful.
 The big issue when it came out, is that SunOS (and later Solaris) had
become the defacto system at most universities, where much 'free software'
was being produced.  Since it was more System V user API at the heart
(which was good for DG's targetted ISVs), it did suffer from the porting
issues.  Since it was an 88K and SunOS had been 68K, the Endian issues of
the free SW was less of a problem, but not only was not a VAX, but it was
not BSD.

Clem

> ᐧ

[-- Attachment #2: Type: text/html, Size: 4895 bytes --]

      parent reply	other threads:[~2019-01-16 15:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-16  3:49 alan
2019-01-16  4:07 ` George Michaelson
2019-01-16  4:47   ` Henry Bent
2019-01-16  6:05     ` Warner Losh
2019-01-16 14:24   ` Dan Cross
2019-01-16 14:40     ` Jon Forrest
2019-01-16 14:40     ` Kevin Bowling
2019-01-16 14:58       ` Dan Cross
2019-01-16 15:10         ` Lars Brinkhoff
2019-01-16 15:50       ` Clem Cole
2019-01-16 14:51     ` Chet Ramey
2019-01-16 15:05     ` Adam Sampson
2019-01-17  6:53     ` [TUHS] UREP - Unix RSCS Emulation Program arnold
2019-01-16 15:44 ` Clem Cole [this message]

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='CAC20D2OAi-5KXBHT454PJSNb00Z=o8vXbC9ke5COQNwdrKjS+g@mail.gmail.com' \
    --to=clemc@ccc.com \
    --cc=alan@alanlee.org \
    --cc=tuhs@tuhs.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).