From: Bakul Shah <bakul@iitbombay.org>
To: Lars Brinkhoff <lars@nocrew.org>
Cc: Paul Ruizendaal <pnr@planet.nl>, "tuhs@tuhs.org" <tuhs@tuhs.org>
Subject: [TUHS] Re: Earliest UNIX Workstations?
Date: Thu, 26 Jan 2023 11:39:30 -0800 [thread overview]
Message-ID: <347AA7EF-C028-4C27-806D-B8549BEECD38@iitbombay.org> (raw)
In-Reply-To: <7wo7qlb1rv.fsf@junk.nocrew.org>
The V sources on bitsavers has a w command. But don't get excited!
It seems to be similar to unix's w, a variation on the who command.
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
The ideal interface must take into account four fundamental principles:
(1) The interface to application programs should be independent of
particular physical devices or intervening networks.
(2) The user should be allowed to perform multiple tasks
simultaneously.
(3) The command interaction discipline should be consistent and
natural.
(4) Response to user interaction should be fast.
The first principle has led to work in virtual terminals (VTs) and
deviceindependent graphics packages, the second to work in window
systems, and the third to work in what has recently been called user
interface management systems, the most common examples of which are
command languages. Without adhering to the fourth principle, however,
much of the other work is moot. In a distributed environment, in
particular, the supporting network protocols cannot incur inordinate
overhead.
From concluding remarks:
To summarize the major attributes of the VGTS:
- Instead of describing how to draw a picture, the application
describes what is to be drawn. The user then specifies where the
picture should be displayed.
- Objects have a hierarchical structure. Hence, the VGTS supports
structured display files rather than segmented display files.
- The VGTS is portable to a range of relatively high-performance
devices.
- Applications can be distributed over multiple machines.
- A single user can access several different applications
simultaneously.
- It performs well!
VGTS code is in the V system sources at bitsavers.
> On Jan 26, 2023, at 10:15 AM, Lars Brinkhoff <lars@nocrew.org> wrote:
>
> Warner Losh wrote:
>> If this is the Standford Unix Networked (?) sun, then I don't know.
>
> Stanford University Network workstation. I have seen some documents
> about it on stacks.stanford.edu, but I don't remember about the
> software. In some versions, it's a more of a multi-head remote graphics
> terminal, so maybe not Unix.
>
>> - Wikipedia says that X1 was 1984 and X11 was 1987; I’m not sure when it
>> became Unix centered
>>
>> I believe very early. It ran first on the VS100
>
> Note that the VAXstation 100 is not a VAX, and not a standalone
> computer. It's a 68000-based graphics terminal that attaches to a VAX.
> The VS100 has some firmware in ROM, and the host uploads additional
> software. There is such a software blob in X10R3.
>
>> There was also a pointer to a blog about pictures of the W window
>> system. None exist, it seems.
>
> I have asked Asante, Reid, and Kent. No luck so far.
next prev parent reply other threads:[~2023-01-26 19:40 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
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 [this message]
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=347AA7EF-C028-4C27-806D-B8549BEECD38@iitbombay.org \
--to=bakul@iitbombay.org \
--cc=lars@nocrew.org \
--cc=pnr@planet.nl \
--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).