The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Paul Ruizendaal <pnr@planet.nl>
To: "tuhs@tuhs.org" <tuhs@tuhs.org>
Cc: Bakul Shah <bakul@iitbombay.org>
Subject: [TUHS] Re: Earliest UNIX Workstations?
Date: Fri, 27 Jan 2023 01:19:58 +0100	[thread overview]
Message-ID: <F9B7616E-F8A6-434D-BF9D-453BF6974727@planet.nl> (raw)
In-Reply-To: <BD0E1656-F491-40B9-B017-1205EB1CF1A2@iitbombay.org>


> On 26 Jan 2023, at 23:45, Bakul Shah <bakul@iitbombay.org> wrote:
> 
> On Jan 26, 2023, at 2:17 PM, Paul Ruizendaal <pnr@planet.nl> wrote:
>> 
>>> 
>>> Bakul Shah bakul at iitbombay.org 
>>> Fri Jan 27 05:39:30 AEST 2023
>>> 
>>> I wonder if this mythical w is the same as V's VGTS as it seems to have
>>> pretty much the same model.
>>> From https://dl.acm.org/doi/pdf/10.1145/357332.357334

And the answer is “no”:

From https://apps.hci.rwth-aachen.de/borchers-old/cs377a/materials/p79-scheifler.pdf :

"The name X derives from the lineage of the system. At Stanford University, Paul Asente and Brian Reid had begun work on the W window system [3] as an alternative to VGTS [13, 22] for the V system [5]. Both VGTS and W allow network-transparent access to the display, using the synchronous V communication mechanism. Both systems provide “text” windows for ASCII terminal emulation. VGTS provides graphics windows driven by fairly high-level object definitions from a structured display file; W provides graphics windows based on a simple display-list mechanism, with limited functionality. We acquired a UNIX- based version of W for the VSlOO (with synchronous communication over TCP [24] produced by Asente and Chris Kent at Digital’s Western Research Laboratory. From just a few days of experimentation, it was clear that a network- transparent hierarchical window system was desirable, but that restricting the system to any fixed set of application-specific modes was completely inadequate. It was also clear that, although synchronous communication was perhaps acceptable in the V system (owing to very fast networking primitives), it was completely inadequate in most other operating environments. X is our “reaction” to W.”

The reference [3] is "ASENTE, P. W reference manual. Internal document, Dept. Computer Science, Stanford Univ., Calif., 1984.”

The version of X discussed in the paper was apparently part of the 4.3BSD distribution tapes:

"The use of X has grown far beyond anything we had imagined. Digital has incorporated X into a commercial product, and other manufacturers are following suit. With the appearance of such products and the release of complete X sources on the Berkeley 4.3 UNIX distribution tapes, it is no longer feasible to track all X use and development.”

And I was wrong with:

> I never really distinguished between the Stanford "SUN" and the Sun Microsystems "Sun-1”, oops. Taking Clem’s comment into account I could see that the SUN ran the V kernel and the W graphics system, and that the Sun-1 was using an early form of X.

Whilst the part about SUN may be correct, the Sun-1 was apparently using MGR and SunWindows/SunView -- at least according to the interesting blog post here (discussed on TUHS a few months ago):

https://oldvcr.blogspot.com/2022/10/if-one-guis-not-enough-for-your-sparc.html




  reply	other threads:[~2023-01-27  0:20 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 [this message]
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
  -- 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=F9B7616E-F8A6-434D-BF9D-453BF6974727@planet.nl \
    --to=pnr@planet.nl \
    --cc=bakul@iitbombay.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).