From: Lars Brinkhoff <lars@nocrew.org>
To: Paul Ruizendaal <pnr@planet.nl>
Cc: "tuhs@tuhs.org" <tuhs@tuhs.org>
Subject: [TUHS] Re: Earliest UNIX Workstations?
Date: Sat, 28 Jan 2023 18:50:58 +0000 [thread overview]
Message-ID: <7wlelma3xp.fsf@junk.nocrew.org> (raw)
In-Reply-To: <697E8876-C2A9-4FE6-A2F7-B4DCEC3BA2C7@planet.nl> (Paul Ruizendaal's message of "Sat, 28 Jan 2023 12:05:51 +0100")
Paul Ruizendaal wrote:
>> V source code exists, right? It seems likely W would have been
>> written in the same language as [V]. 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 [VS1OO] (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.
I checked V, and it's written in C.
next prev parent reply other threads:[~2023-01-28 18:51 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 [this message]
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=7wlelma3xp.fsf@junk.nocrew.org \
--to=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).