From: Marc Donner <marc.donner@gmail.com>
To: Larry Stewart <stewart@serissa.com>
Cc: Joseph Holsten <joseph@josephholsten.com>, tuhs@tuhs.org
Subject: [TUHS] Re: Earliest UNIX Workstations?
Date: Thu, 26 Jan 2023 08:25:43 -0500 [thread overview]
Message-ID: <CALQ0xCBcbsfTuaUGyY8+1L4ADMupqRMANjLXQSWDiG3hFd02dg@mail.gmail.com> (raw)
In-Reply-To: <23432965-52D6-4331-A4D8-8A6FDDB3F751@serissa.com>
[-- Attachment #1: Type: text/plain, Size: 2331 bytes --]
PERQ
There was some talk of making Unix run on it, but POS (PERQ-OS) was written
in Pascal and there was no reasonable way to port over all of the existing
stuff without rewriting it all. I had a PERQ in my office for a while … it
put out so much heat and noise that my officemates lobbied to have me
evicted.
On Wed, Jan 25, 2023 at 8:01 PM Larry Stewart <stewart@serissa.com> wrote:
> There was quite a lot of early activity of course!
> Essentially all of computer science academia was aware of the Xerox Alto,
> although it wasn't a commercial product and wasn't Unix.
>
> Jim Morris left PARC and went off to CMU and began talking up the idea of
> the "3M" workstation. One MIPs, One Megabyte of RAM, and One Million
> Pixels.
>
> One of the early commercial attempts was the Three Rivers PERC (or PERQ?)
> from the Pittsburgh startup. There were Unix adjacent systems as well,
> such as Apollo Domain.
>
> Of course then Sun got started, and MIPS, and the IBM RT and VaxStations
> so by the mid '80s it was quite crowded.
>
> There is a whole other arc about the graphics workstations, with SGI,
> Ardent, Stellar, Stardent, and so on.
>
> Also, before graphics became affordable, there were various clustered
> character generator based systems like Convergent Technologies.
>
> -L
>
> On Jan 25, 2023, at 7:31 PM, Joseph Holsten <joseph@josephholsten.com>
> wrote:
>
> It seems like there are bountiful articles able the decline and fall of
> the UNIX workstation, but I’ve had a hard time finding narrative about
> workstations prior to the Stanford SUN workstation.
>
>
> * was the SUN-1 the first commercially successful product? What are the
> “it depends” edge cases?
> * were there common recipes for proto-workstations within academic or
> industrial research? What did those look like, who was involved?
> * What do I really mean by workstation? Ex.gr. If an installation had a
> PDP-11 with a single terminal and operator, is it not a workstation? Is it
> the integration of display into the system that differentiates?
>
> --
> Joseph Holsten
> http://josephholsten.com
> mailto:joseph@josephholsten.com
> tel:+1-360-927-7234 <(360)%20927-7234>
>
> --
=====
nygeek.net
mindthegapdialogs.com/home <https://www.mindthegapdialogs.com/home>
[-- Attachment #2: Type: text/html, Size: 4314 bytes --]
next prev parent reply other threads:[~2023-01-26 13:27 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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 21:29 ` [TUHS] Collecting notes for future “historians” was: " Joseph Holsten
2023-01-26 21:38 ` [TUHS] " Jon Steinhart
2023-01-26 22:41 ` Joseph Holsten
2023-01-27 0:34 ` segaloco via TUHS
2023-01-27 0:36 ` G. Branden Robinson
2023-01-27 0:53 ` segaloco via TUHS
2023-01-27 1:28 ` David Arnold
2023-01-27 1:35 ` Warner Losh
2023-01-26 9:52 ` [TUHS] " 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
2023-01-26 13:15 Paul Ruizendaal via TUHS
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
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
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
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=CALQ0xCBcbsfTuaUGyY8+1L4ADMupqRMANjLXQSWDiG3hFd02dg@mail.gmail.com \
--to=marc.donner@gmail.com \
--cc=joseph@josephholsten.com \
--cc=stewart@serissa.com \
--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).