From: Dave Horsfall <dave@horsfall.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Earliest UNIX Workstations?
Date: Thu, 26 Jan 2023 18:33:30 +1100 (EST) [thread overview]
Message-ID: <alpine.BSF.2.21.9999.2301261830050.58710@aneurin.horsfall.org> (raw)
In-Reply-To: <CAD2gp_QtUPmd78yAixvKK1wzPX67HKZXzU5cJnVUbcWtMounGQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 571 bytes --]
On Thu, 26 Jan 2023, John Cowan wrote:
> WP says the Terak 8510/a was the first graphical workstation; it came
> out in 1976-77 and ran the UCSD p-System. I had never heard of it
> before. The first *personal* workstation (non-graphical) was probably
> the IBM 1620 (aka the CADET system, "Can't Add, Doesn't Even Try") from
> 1959.
Mmm... Would a GT-40 connected to a PDP-11/40 count as a workstation? I
started using that around 1975 (along with serial terminals, of course),
in my first job at Uni of NSW (after graduating from there).
-- Dave
next prev parent reply other threads:[~2023-01-26 7:33 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
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 [this message]
[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=alpine.BSF.2.21.9999.2301261830050.58710@aneurin.horsfall.org \
--to=dave@horsfall.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).