From: Doug McIlroy <doug@cs.dartmouth.edu>
To: tuhs@tuhs.org
Subject: Re: [TUHS] Chaos networking in 8th edition (and in 7th)
Date: Tue, 19 May 2020 23:29:48 -0400 [thread overview]
Message-ID: <202005200329.04K3TmBF006901@tahoe.cs.Dartmouth.EDU> (raw)
>> I don't recall any use of Chaos in 1127. Possibly one of
>> the nearby groups who also used the Research system needed
>> it at some point
> Speculating wildly, maybe there was a Lisp machine somewhere?
None that I can remember.
Doug
next reply other threads:[~2020-05-20 3:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 3:29 Doug McIlroy [this message]
2020-05-20 6:06 ` Rob Pike
2020-05-20 11:43 ` William Cheswick
2020-05-20 12:30 ` John P. Linderman
2020-05-21 15:18 ` Dave Horsfall
2020-05-21 16:29 ` Nemo Nusquam
2020-05-21 16:59 ` Lars Brinkhoff
2020-05-21 18:39 ` [TUHS] EMACS (was Re: Chaos networking in 8th edition (and in 7th)) Derek Fawcus
2020-05-21 18:50 ` [TUHS] Chaos networking in 8th edition (and in 7th) Paul Winalski
2020-05-21 17:25 ` thomas kirk
-- strict thread matches above, loose matches on Subject: below --
2020-05-18 21:52 Norman Wilson
2020-05-19 3:41 ` Lars Brinkhoff
2020-05-18 21:01 Paul Ruizendaal
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=202005200329.04K3TmBF006901@tahoe.cs.Dartmouth.EDU \
--to=doug@cs.dartmouth.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).