The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: Paul Ruizendaal <pnr@planet.nl>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Earliest UNIX Workstations?
Date: Sat, 28 Jan 2023 08:38:55 -0700	[thread overview]
Message-ID: <CANCZdfq-g3Tj5YnRcyD7pdHpYEaBL0gohfShuSAQ0+i_i-eURg@mail.gmail.com> (raw)
In-Reply-To: <697E8876-C2A9-4FE6-A2F7-B4DCEC3BA2C7@planet.nl>

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

On Sat, Jan 28, 2023, 4:05 AM Paul Ruizendaal <pnr@planet.nl> wrote:

>
> > On 28 Jan 2023, at 10:14, Lars Brinkhoff <lars@nocrew.org> wrote:
> >
> > Warner Losh wrote:
> >> Rich Salz wrote:
> >>> I'd like to know what the first versions of X were written in
> >>
> >> Without the earlier versions' source, it's hard to answer this
> question...
> >
> > V source code exists, right?  It seems likely W would have been written
> > in the same language as W.  And that early X would also be the same.
> > Another source of information would be to ask Bob Scheifler and Jim
> > Gettys.
>
> Whilst that is a reasonable assumption, I’m not sure it is true in this
> case. Bob Scheifler writes in 1986:
>
> "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.”
>
> It does not say “C based”, but it is quite possible that the Unix port
> also meant moving to C.
>
> Also, the work started in June 1984 and had gone to version 10, release 3
> by February 1986. That is 12 versions in 20 months. Most likely X1-X10R2
> are all snapshots done in rapid succession.


X11 is the 11th version of the wire protocol. They bumped that number each
time there was a protocol change. It's not clear that all the early
versions were distributed beyond the local network. The Xlib book stated
something along these lines, but I can't find my copy to quote it or
refresh my recollection.


The change notes for X10R3 read as describing a work still in progress:
>
> http://www.retro11.de/ouxr/43bsd/usr/src/new/X/CHANGES
>
> That “work-in-progress” feel also shows in the Xterm README:
>
> "Xterm is in a reasonably usable state.  We are sick and tired of working
> on it, but there are clearly major areas of improvement possible.  Do
> not look to us to do more than integration work on other people's
> improvement.  About 50% of it is the oldest existing code in the package
> and needing major rewrite.  Our thanks to Bob McNamara for the 50% which
> is solid."
>

Rolling releases were quite common. They went out of style for a while, but
are back in vouge with CI....

The README for the X server itself (written in August 1985 it seems,
> http://www.retro11.de/ouxr/43bsd/usr/src/new/X/X/README) says:
>
> "The server has been completely rewritten several times now, and I am
> reasonably
> happy with it.  I have fine-tuned it specifically for the current
> (sub-optimal)
> VAX compiler.  For other machines, faster code may be obtained in some
> cases
> by changing sizes (e.g., to avoid indexing shifts on the 68000) or register
> declarations.  Attempts to parameterize along these lines have only been
> made
> for the byte-swapping code.”
>
> So there were several rewrites from Summer 1984 till Summer 1985. In case
> the first version was in CLU, it would seem that the change-over to C
> happened in the very first months of the code base’s lifespan.
>

Most likely the CLU library bindings in X10R3 are a hold over from other
software other departments were still using given the fast pace here...

The next paragraph as to the state of the code base at this time is
> revealing:
>
> Unfortunately, a great many invariants are not written down.  Hopefully you
> will spend a few weeks understanding the code before you muck with it.  If
> something seems easy to add or change, you probably forgot something
> important.
> Almost everything depends on everything else.  It is almost impossible to
> devise rigorous test cases.  Innocuous looking changes can have large
> performance effects, so watch out.  If you muck with fundamental window
> components, a good cross-check is to see how quickly you can manipulate a
> window with, say, 100 non-adjacent subwindows.
>
> After reading the above, Jon Steinhart’s post from 5 years ago about X is
> all the more interesting:
> https://minnie.tuhs.org/pipermail/tuhs/2017-September/012089.html


I'd forgotten about that...

Warner

>
>

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

  reply	other threads:[~2023-01-28 15: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 [this message]
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=CANCZdfq-g3Tj5YnRcyD7pdHpYEaBL0gohfShuSAQ0+i_i-eURg@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).