The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Phil Budne <phil@ultimate.com>
To: tuhs@tuhs.org
Subject: [TUHS]  Re: Collecting notes for future “historians” was: Earliest UNIX Workstations?
Date: Mon, 30 Jan 2023 01:13:22 -0500	[thread overview]
Message-ID: <202301300613.30U6DMe5030381@ultimate.com> (raw)
In-Reply-To: <CAKH6PiVARZufGGa5CgvxiFreLOZO7TY-vht8KDVqtdOUmA-PPQ@mail.gmail.com>

Douglas McIlroy wrote:
> Date: Sat, 28 Jan 2023 16:16:56 -0500
>
> > * 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?
>
> Certainly integration is critical. The display should be integral to the
> terminal, not simply an available device.
>
> Without that stipulation Ken's original single-user PDP-7 system would
> count (unless, perhaps, the system had not yet been christened "Unix").

Tho perhaps the EXACT same PDP-7 (in its original use as a prototype
for the PDP-9 based Graphic-2 circuit design/simulation system) would
qualify as a workstation?

Here's a 1965 video of the earlier (PDP-5 based?) Graphic-1 system in use:
https://techchannel.att.com/playvideo/2012/09/07/AT&T-Archives-Graphic-1

Both Graphic-1 and Graphic-2 were display "workstations" that fronted
for mainframes.

  reply	other threads:[~2023-01-30  6:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-28 21:16 Douglas McIlroy
2023-01-30  6:13 ` Phil Budne [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-01-26  0:31 [TUHS] " Joseph Holsten
2023-01-26  1:47 ` [TUHS] " Chris Hanson
2023-01-26  7:20   ` John Cowan
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

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=202301300613.30U6DMe5030381@ultimate.com \
    --to=phil@ultimate.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).