From: Norman Wilson <norman@oclsc.org>
To: tuhs@tuhs.org
Subject: [TUHS] Chaos networking in 8th edition (and in 7th)
Date: Mon, 18 May 2020 17:52:38 -0400 [thread overview]
Message-ID: <1589838762.16960.for-standards-violators@oclsc.org> (raw)
Paul Ruizendaal:
Was Chaos networking in use at the labs, or is it just an artifact
present on the surviving tape?
===
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, perhaps before my time (I arrived in
August 1984).
I certainly don't remember anyone raising objections to
discarding it.
Norman Wilson
Toronto ON
next reply other threads:[~2020-05-18 21:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 21:52 Norman Wilson [this message]
2020-05-19 3:41 ` Lars Brinkhoff
-- strict thread matches above, loose matches on Subject: below --
2020-05-20 3:29 Doug McIlroy
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:50 ` Paul Winalski
2020-05-21 17:25 ` thomas kirk
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=1589838762.16960.for-standards-violators@oclsc.org \
--to=norman@oclsc.org \
--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).