From: Clem Cole <clemc@ccc.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Setting up an X Development Environment for Mac OS
Date: Wed, 25 Jan 2023 16:25:32 -0500 [thread overview]
Message-ID: <CAC20D2NgrjJF-yGOBYFwr=rbRog+YFHF7tL_qozY=AZOf19-XA@mail.gmail.com> (raw)
In-Reply-To: <20230125203805.4762218C083@mercury.lcs.mit.edu>
[-- Attachment #1: Type: text/plain, Size: 1079 bytes --]
On Wed, Jan 25, 2023 at 3:38 PM Noel Chiappa <jnc@mercury.lcs.mit.edu>
wrote:
>
> Do any of the really early versions of X (and W) still exist?
>
Not that I have found. I looked a couple a years ago. FWIW: I would be
surprised if any of it was in CLU, because the first version of X was a
redo from synchronous W protocol to the async one Bob did. If I remember
it correctly ... W as for the V Kernel on the Stanford (68K based) Sun
Terminal, that Paul Asente and Brian Reid did at Stanford (in C). The
Paul and Chris Kent at DEC (either WRL or SRC I foirget which) took it and
made it work on a VS100 and microvax. That version when to MIT via the
Athena connection and Bob rewrote the back-end creating the X from W.
Shortly after that Gettys brought the Microvax X version out to me in
Westford where, he, Jack Burness and I got it running on a 68K based
Masscomp over a weekend fairly soon after Jack his first version of his new
BITBLT primitive working - which until then we lacked (it was pretty cool
how quick it came up).
Clem
ᐧ
ᐧ
[-- Attachment #2: Type: text/html, Size: 3017 bytes --]
next prev parent reply other threads:[~2023-01-25 21:27 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 20:38 Noel Chiappa
2023-01-25 21:25 ` Clem Cole [this message]
2023-01-26 6:30 ` Lars Brinkhoff
2023-01-26 10:56 ` Ralph Corderoy
2023-01-26 12:01 ` arnold
2023-01-26 13:25 ` Lars Brinkhoff
2023-01-26 15:28 ` [TUHS] " josh
2023-01-26 16:07 ` [TUHS] " segaloco via TUHS
2023-01-26 16:48 ` emanuel stiebler
2023-01-26 21:19 ` segaloco via TUHS
2023-01-26 22:51 ` Andy Kosela
2023-01-27 0:48 ` segaloco via TUHS
2023-01-27 4:07 ` Will Senn
2023-01-27 14:08 ` Chet Ramey
2023-01-27 14:49 ` Ron Natalie
2023-01-27 15:53 ` Dan Cross
2023-01-27 16:12 ` [TUHS] NEXTSTEP 486 [was " Charles H Sauer (he/him)
2023-01-27 14:17 ` [TUHS] " Ralph Corderoy
2023-01-27 13:56 ` Ralph Corderoy
2023-01-27 14:54 ` Ron Natalie
2023-01-27 16:10 ` Larry McVoy
2023-01-28 22:15 ` Dave Horsfall
2023-01-29 0:31 ` Kevin Bowling
2023-01-29 11:07 ` emanuel stiebler
2023-01-27 21:42 ` Tom Perrine
2023-01-28 2:18 ` Larry McVoy
2023-01-28 2:49 ` Tom Perrine
2023-01-26 6:32 ` Lars Brinkhoff
2023-01-26 9:45 ` emanuel stiebler via TUHS
-- strict thread matches above, loose matches on Subject: below --
2023-01-25 1:46 [TUHS] " Will Senn
2023-01-25 7:45 ` [TUHS] " segaloco via TUHS
2023-01-25 8:00 ` Lars Brinkhoff
2023-01-25 16:41 ` Rich Salz
2023-01-25 19:53 ` Theodore Ts'o
2023-01-25 20:04 ` Dan Cross
2023-01-25 20:23 ` Larry McVoy
2023-01-25 20:27 ` Chet Ramey
2023-01-27 4:49 ` Theodore Ts'o
2023-01-27 18:05 ` Henry Mensch
2023-01-27 18:24 ` Charles H Sauer (he/him)
2023-01-26 13:17 ` Marc Donner
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='CAC20D2NgrjJF-yGOBYFwr=rbRog+YFHF7tL_qozY=AZOf19-XA@mail.gmail.com' \
--to=clemc@ccc.com \
--cc=jnc@mercury.lcs.mit.edu \
--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).