The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: Paul Ruizendaal <pnr@planet.nl>
Cc: "tuhs@tuhs.org" <tuhs@tuhs.org>
Subject: [TUHS] Re: Earliest UNIX Workstations?
Date: Fri, 27 Jan 2023 10:36:26 -0700	[thread overview]
Message-ID: <CANCZdfrB9dW82ngt45_rf5=yM0=QEPwCL8F44GiVV6wxu+hSbg@mail.gmail.com> (raw)
In-Reply-To: <E03D5C67-58A9-4F7F-927C-29060B6EAA32@planet.nl>

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

On Fri, Jan 27, 2023 at 10:16 AM Paul Ruizendaal via TUHS <tuhs@tuhs.org>
wrote:

>
> On Jan 27, 2023, at 1:19 AM, Paul Ruizendaal <pnr@planet.nl> wrote:
>
> 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.”
>
>
> This X is not on the TUHS Unix tree website, nor on the CSRG disks. It
> turns out that there is a directory “src/new” that is not included there.
> It is here:
>
> http://www.retro11.de/ouxr/43bsd/usr/src/new/
>
> The version of X included with 4.3BSD was X10. I assume this is the oldest
> surviving X Window source code.
>

There's X10R3 and X10R4 at https://www.x.org/archive/X10R3/ and
https://www.x.org/archive/X10R4/. On the FTP site, there's sym links for
R1, R2, R3, R4, R5, R6, R6.1, R6.3, R6.4, R6.5.1, R6.6 and R6.8 in the pub
directory as well, but they are dead links and correspond to the X11
releases that are also there, not X1, etc.

The X10R3 is from Feb 2, 1986. X10R4 is from December 2, 1986. The
retro11.de files are from June 1986, so
are no later than X10R4, and most likely either X10R3 or an internal
snapshot (I've not downloaded them both
to run a diff to see which).

Google searches for X9, X8, etc aren't at all helpful.

Of course the source code for the Blit has survived, as has the source code
> of MGR. The source code for Sunwindows and NeWS is presumably lost?
>

When I was a Solbroune, we started the OI toolkit with pdb, swm, uib, etc
because Sun refused to license the source code to SunView. Although I had
easy access to SunOS (which I wish I'd saved a copy of now), the SunView
code was never in the building. It was relatively easy to get SunOS sources
for a fee, but much harder for SunView. So I'm less than completely hopeful
here. And NeWS was a fringe thing with a significantly shorter product
life, so I'm even less hopeful there.

Warner

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

  reply	other threads:[~2023-01-27 17:38 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 [this message]
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='CANCZdfrB9dW82ngt45_rf5=yM0=QEPwCL8F44GiVV6wxu+hSbg@mail.gmail.com' \
    --to=imp@bsdimp.com \
    --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).