The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Dan Cross <crossd@gmail.com>
To: George Michaelson <ggm@algebras.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 09:24:54 -0500	[thread overview]
Message-ID: <CAEoi9W5quyXkE3PQEhN4GacybFLjNqmHz10m5FxVOeKynoQ+Wg@mail.gmail.com> (raw)
In-Reply-To: <CAKr6gn0n1dV1msPb6DcCHKNQCOT=-2=5e3Ge-p6CZAz17yBURw@mail.gmail.com>

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

On Tue, Jan 15, 2019 at 11:08 PM George Michaelson <ggm@algebras.org> wrote:

> In my opinion, the popularity of a UNIX platform is tightly tied to
> the availability of the platform at university.
>
> If DG was available to tinker on, to run ROFF, to write small programs
> for other reasons, to introspect and familiarise yourself with, Then
> for those students, it became the logical choice.
>
> If they ignored the tertiary education market, sold into industry,
> they could have established a huge loyal fanbase in E.G. Finance and
> Insurance. Or in the decision support systems in Oil. Or shoe makers
> inventory control. But if you don't have a cohort of students who
> recognize your brand, your flavour of UNIX, and you then face these
> students flexing muscles at purchase time, Instead of "lets buy the
> upgrade option from DG" you get "why don't we buy Sun, and then get
> cheap kids to run it"
>
> TL;DR DG did not have significant presence in the tertiary education
> systems I played in (York, Leeds, UCL, UQ) and by my visibility,
> almost any tertiary education facility I have seen. They didn't feed
> the beast.
>

Interesting. When I was in high school in central Pennsylvania and begging,
borrowing (and yeah a little stealing) computer time from Penn State
systems, there was a CS professor who'd made his bones building something
called UREP: Unix RSCS Emulation Program. I can't remember the fellow's
name; something "Roberts" maybe. He was known for being somewhat acerbic
(he'd call students "stupid" in class, was known to be nasty on USENET,
etc) and he wasn't a healthy man. He died of a heart attack when I was in
my late teens. Anyway....

What's notable about that, to me, was that he wrote UREP for DG/UX and was
known to be fond of Data General machines. This let him talk to the
university's mainframe, which was run by the computer center, ran VM, and
was the major compute engine on campus at the time outside of specially
purchased machines supporting research. There was a Cray somewhere on
campus, for example, but that was purchased out of research funds and
wasn't generally accessible. It also let Unix machines participate on
BITNET, which was a big deal locally at the time (probably because of the
close association with mainframes). But this was well before the AViiON
series; probably around the time of the Eagle. So maybe just after the
"Soul of a New Machine" era in DG's history.

Anyway, the point is that they did have a footprint in the academic market.
I suspect their lack of success had more to do with them as a company and
their foibles in the market than anything else. Like many of the "Route
128" minicomputer companies of the early 70s, I get the impression that
they ran themselves into the ground chasing the minicomputer market and
missing the shift to microprocessors, workstations and PCs. By the time
they could try and turn things around with the storage kit, they were a bit
player in the server market. The storage thing only set them apart and kept
them afloat long enough to get bought out.

        - Dan C.

(PS: I worked for a startup in NYC in the very late 1990s and early 2000;
one of those "dot com" companies [all the stories are true, though in my
defense I had no idea just how much drama was happening around me at the
time]. We picked up some kind of engineering director guy via some merger
with another dot com startup-y sort of thing based in Boston and that guy
had come from Data General. Of course, he wanted to move everything to
Boston/Cambridge and thought us New Yorkers were a bunch of dullards. It
stuck out to me because I don't think I've ever worked with an emptier
suit, though I've seen a few that gave him a run for his money.... If DG
management was anything like him, no wonder they died an inglorious death.)

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

  parent reply	other threads:[~2019-01-16 14:26 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 [this message]
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 ` [TUHS] The John Snow's of the UNIX family Clem Cole

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=CAEoi9W5quyXkE3PQEhN4GacybFLjNqmHz10m5FxVOeKynoQ+Wg@mail.gmail.com \
    --to=crossd@gmail.com \
    --cc=ggm@algebras.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).