The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: Paul Ruizendaal <pnr@planet.nl>
Cc: "tuhs@tuhs.org" <tuhs@tuhs.org>
Subject: [TUHS] Re: Earliest UNIX Workstations?
Date: Thu, 26 Jan 2023 09:51:59 -0700	[thread overview]
Message-ID: <CANCZdfq6O0U12=eM+Ox+U7qNwwPV2B4PLX7d=rWDmFgvNeODQQ@mail.gmail.com> (raw)
In-Reply-To: <0C5D8AF8-BAB2-48B5-854B-34E3A949DE50@planet.nl>

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

On Thu, Jan 26, 2023 at 8:58 AM Paul Ruizendaal <pnr@planet.nl> wrote:

>
> As a result of the recent discussion on this list I’m trying to understand
> the timeline of graphical computing on Unix, first of all in my preferred
> time slot ’75 -’85.
>
> When it comes to Bell Labs I’m aware of the following:
>
> - around 1975 the Labs worked on the Glance-G vector graphics terminal.
> This was TSS-516 based with no Unix overlap I think.
> - around the same time the Labs seem to have used the 1973 Dec VT11 vector
> graphics terminal; at least the surviving LSX Unix source has a driver for
> it
> - in 1976 there was the Terak 8510; this ran primarily USCD pascal, but it
> also ran LSX and/or MX (but maybe only much later)
> - then it seems to jump 1981 and to the Blit.
> - in 1984 there was MGR that was done at Bellcore
>
> Outside of the labs (but on Unix), I have:
>
> - I am not sure what graphics software ran on the SUN-1, but it must have
> been something
>

If this is the sun microsystem sun-1, the leaked sources online suggest
that these initially ran a V7 port by Unisoft. This switched to a 4.2BSD
port maybe before it went to customers as SunOS 1.0 if other leaked sources
can be believed.

If this is the Standford Unix Networked (?) sun, then I don't know.


> - Clem just mentioned the 1981 Tektronix Magnolia system
> - Wikipedia says that X1 was 1984 and X11 was 1987; I’m not sure when it
> became Unix centered
>

I believe very early. It ran first on the VS100, and I believe that those
machines at project athena were running Unix, but I'm not sure of the cut
over from Stanford V. Another thread posted the X announcement which was in
June 1984. There was also a pointer to a blog about pictures of the W
window system. None exist, it seems. The windowing system pictured in the
glossy marketing sheets for the VS100 were for VMS and VMS Windowing
System. I'd put money against the first X running on VMS. :)

We had X10R3 running on Sun 3/50s in our lab, though more often they ran
SunView since it was faster and more familiar to the admins that ran the
machines. This was in 86 or 87 I believe.


> - Sun’s NeWS arrived only in 1989, I think?
>

No. It had to be late 1987 or 1988 because I ran that on the Sun 3/60 that
the Hydrology department that I worked for ran. I didn't run it often, mind
you, and the 'generic terminal emulator for any termcap entry' terminal was
cool, but it was just a notch too weird for a daily driver.

Warner


> Outside of Unix, in the microcomputer world there was a lot of cheap(er)
> graphics hardware. Lot’s of stuff at 256 x 192 resolution, but up to 512 x
> 512 at the higher end. John Walker writes that the breakout product for
> Autodesk was Interact (the precursor to AutoCAD). Initially developed for
> S-100 bus systems it quickly moved to the PC. There was a lot of demand for
> CAD at a 5K price point that did not exist at a 50K price point.
>
>
>
>
>
>

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

  parent reply	other threads:[~2023-01-26 16:53 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-26 15:58 [TUHS] " Paul Ruizendaal
2023-01-26 16:04 ` [TUHS] " Larry McVoy
2023-01-26 16:37   ` emanuel stiebler
2023-01-26 16:51     ` segaloco via TUHS
2023-01-26 16:29 ` Clem Cole
2023-01-26 22:17   ` Paul Ruizendaal
2023-01-26 22:45     ` Bakul Shah
2023-01-27  0:19       ` Paul Ruizendaal
2023-01-27 17:16         ` Paul Ruizendaal via TUHS
2023-01-27 17:36           ` Warner Losh
2023-01-27 17:37             ` Warner Losh
2023-01-27 17:45               ` Rich Salz
2023-01-27 17:54                 ` Warner Losh
2023-01-28  9:14                   ` Lars Brinkhoff
2023-01-28 11:05                     ` Paul Ruizendaal
2023-01-28 15:38                       ` Warner Losh
2023-01-28 18:50                       ` Lars Brinkhoff
2023-01-29  6:48                     ` Lars Brinkhoff
2023-01-29 20:39                       ` Paul Ruizendaal
2023-01-27 17:43           ` josh
2023-01-26 16:51 ` Warner Losh [this message]
2023-01-26 18:15   ` Lars Brinkhoff
2023-01-26 19:39     ` Bakul Shah
2023-01-27 10:59     ` Lars Brinkhoff
2023-01-26 18:14 ` Jon Steinhart
2023-01-26 20:44 ` Rob Pike
  -- strict thread matches above, loose matches on Subject: below --
2023-01-29 23:20 Paul Ruizendaal via TUHS
2023-01-30  0:25 ` Jonathan Gray
2023-01-30  5:23 ` Jonathan Gray
2023-01-30  8:45   ` Paul Ruizendaal
2023-01-30  9:22   ` Jonathan Gray
2023-01-31 11:35   ` Paul Ruizendaal
2023-01-31 23:29   ` Chris Hanson
2023-01-30 13:00 ` Lars Brinkhoff
2023-02-06  7:01 ` Jonathan Gray
2023-02-06  8:39   ` Jonathan Gray
2023-01-26 13:15 Paul Ruizendaal via TUHS
2023-01-26  0:31 [TUHS] " Joseph Holsten
2023-01-26  0:51 ` [TUHS] " segaloco via TUHS
2023-01-26  1:06   ` Luther Johnson
2023-01-26  1:15     ` Jon Steinhart
2023-01-26  1:01 ` Larry Stewart
2023-01-26 13:25   ` Marc Donner
2023-01-26 13:58     ` arnold
2023-01-31  2:03   ` Mary Ann Horton
2023-01-31 17:43     ` Marc Donner
2023-01-26  1:12 ` Tom Lyon
2023-01-26  1:47 ` Chris Hanson
2023-01-26  7:20   ` John Cowan
2023-01-26  7:33     ` Dave Horsfall
     [not found]     ` <CAD2gp_QtUPmd78yAixvKK1wzPX67HKZXzU5cJnVUbcWtMounGQ@mail.g mail.com>
2023-01-26 16:35       ` John Foust via TUHS
2023-01-26 17:58     ` Jon Forrest
2023-01-26 18:04     ` Jon Steinhart
2023-01-26  9:52 ` emanuel stiebler
2023-01-26  9:58   ` Rob Pike
2023-01-26 10:09   ` Jaap Akkerhuis via TUHS
2023-01-26 15:14 ` 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='CANCZdfq6O0U12=eM+Ox+U7qNwwPV2B4PLX7d=rWDmFgvNeODQQ@mail.gmail.com' \
    --to=imp@bsdimp.com \
    --cc=pnr@planet.nl \
    --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).