The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Luther Johnson <luther@makerlisp.com>
To: tuhs@tuhs.org
Subject: [TUHS] Re: Earliest UNIX Workstations?
Date: Wed, 25 Jan 2023 18:06:36 -0700	[thread overview]
Message-ID: <eda11939-09a5-2dd1-2b5a-dcbdb2feb82c@makerlisp.com> (raw)
In-Reply-To: <BMsRLs2wvKH0iixW0Eo49huSqZ4zAi_vnew1uMpaw1pFKBQNyXPztO46Z03iKSgJ2USkeTDcioaYrsH9k1Yf-u6ztc_sOSeDyUFlItm19aM=@protonmail.com>

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

I think what made 'workstations' different was:

1) You had your own computer, you were not just using a terminal 
connected to a computer, that was time-shared with a bunch of other users

2) A very capable large bit-mapped display, hence the variation on this 
term, "graphic workstation"

3) Networking to shared filesystems - in time sharing, you're all on one 
computer, going to the same files on the same disk(s), in a network of 
workstations, you're all going to a network with filesystems mounted on 
disks on machines all over the network. Some workstations had disks and 
filesystems, some did not - hence another variation, "disk-less 
workstation", which booted from the network. "Servers" were big machines 
with big disks, really the same kinds of machines, basically, but 
configured to be effective at hosting resources and people were 
discouraged from logging in and camping out on them.

That's how I remember it, the machines and capabilities were also 
accompanied by the different modes of resource use that they enabled.

On 01/25/2023 05:51 PM, segaloco via TUHS wrote:
> Nothing says a PDP-11 has to be in a rack with peripherals right? If 
> one could devise up emulated peripherals that plug into the backplane 
> or otherwise tear them down to fit in much less space, a PDP-11 could 
> probably be made to inhabit similar desk real-estate as a workstation, 
> especially some of the smaller LSI models. There's also the MicroVAXen 
> but the SUN-1 beats those to the market.
>
> All in all, I would wager workstation has never been a well regulated 
> term and, especially once PCs and other micros got better, the 
> delineation between a workstation and a consumer PC has just gotten 
> blurrier and blurrier. For instance, I would use the term workstation 
> to apply to my Raspberry Pi, someone else would probably chuckle at 
> the thought while sitting at their modern POWER9 system. It fits all 
> the needs of my non-day-job computing, so workstation enough for me.
>
> - Matt G.
> ------- Original Message -------
> On Wednesday, January 25th, 2023 at 4: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 <http://josephholsten.com/>
>> mailto:joseph@josephholsten.com <mailto:joseph@josephholsten.com>
>> tel:+1-360-927-7234 <tel:%28360%29%20927-7234>
>


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

  reply	other threads:[~2023-01-26  1:06 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 [this message]
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 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=eda11939-09a5-2dd1-2b5a-dcbdb2feb82c@makerlisp.com \
    --to=luther@makerlisp.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).