From: Anthony Martin <ality@pbrane.org>
To: Paul Ruizendaal <pnr@planet.nl>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: forgotten versions
Date: Sat, 25 Jun 2022 12:16:59 -0700 [thread overview]
Message-ID: <YrdfK5rguPEftall@alice> (raw)
In-Reply-To: <38ED67E4-4D75-47A8-BA44-4A08DF487EC2@planet.nl>
The following papers are a good overview of Datakit and its
predecessors.
A. Fraser, "Towards a Universal Data Transport System," in IEEE
Journal on Selected Areas in Communications, vol. 1, no. 5, pp.
803-816, November 1983, doi: 10.1109/JSAC.1983.1145998.
A. G. Fraser, "Early experiments with asynchronous time division
networks," in IEEE Network, vol. 7, no. 1, pp. 12-26, Jan. 1993,
doi:10.1109/65.193084.
The latter mentions Plan 9 but only in passing.
Paul Ruizendaal <pnr@planet.nl> once said:
> Probably you will see echoes of this in early Plan9 network code, but I have not studied that.
As someone how has studied Plan 9 extensively, though with no insider
knowledge, it's definitely noticeable.
"In the aftermath, perhaps the most valuable effect of dealing with
Datakit was to encourage the generalized and flexible approach to
networking begun in 8th edition Unix that is carried forward into Plan
9." - dmr (2004)
Cheers,
Anthony
next prev parent reply other threads:[~2022-06-25 19:17 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 6:47 Paul Ruizendaal
2022-06-25 19:16 ` Anthony Martin [this message]
2022-06-25 20:45 ` Paul Ruizendaal
2022-06-27 0:57 ` Kevin Bowling
-- strict thread matches above, loose matches on Subject: below --
2022-06-23 2:18 Noel Chiappa
2022-06-22 12:06 Noel Chiappa
2022-06-23 0:02 ` Dan Cross
2022-06-18 19:55 Paul Ruizendaal
2022-06-18 0:35 Douglas McIlroy
2022-06-18 5:00 ` Kevin Bowling
2022-06-18 5:13 ` Adam Thornton
2022-06-18 16:58 ` Clem Cole
2022-06-18 17:18 ` Warner Losh
2022-06-18 17:57 ` Clem Cole
2022-06-17 14:50 Paul Ruizendaal
2022-06-16 23:06 [TUHS] " Rob Pike
2022-06-16 23:17 ` [TUHS] " Earl Baugh
2022-06-16 23:18 ` George Michaelson
2022-06-16 23:44 ` George Michaelson
2022-06-17 0:10 ` Larry McVoy
2022-06-17 7:20 ` Diomidis Spinellis
2022-06-17 7:33 ` Rob Pike
2022-06-17 8:34 ` arnold
2022-06-17 10:52 ` arnold
2022-06-18 7:05 ` Angelo Papenhoff
2022-06-19 7:50 ` Rob Pike
2022-06-19 8:17 ` Angelo Papenhoff
2022-06-19 8:53 ` Rob Pike
2022-06-19 9:02 ` Angelo Papenhoff
2022-06-19 9:14 ` arnold
2022-06-19 9:19 ` Angelo Papenhoff
2022-06-19 9:23 ` arnold
2022-06-19 11:37 ` Matthias Bruestle
2022-06-19 14:47 ` Kenneth Goodwin
2022-06-19 16:27 ` Al Kossow
2022-06-19 18:32 ` Theodore Ts'o
2022-06-19 18:38 ` Dan Cross
2022-06-21 23:56 ` Jacob Moody
2022-06-22 0:13 ` Larry McVoy
2022-06-22 0:48 ` Rob Pike
2022-06-22 1:55 ` George Michaelson
2022-06-22 2:10 ` Bakul Shah
2022-06-22 2:14 ` Jon Steinhart
2022-06-22 2:19 ` Andrew Hume
2022-06-22 2:58 ` Rob Pike
2022-06-22 3:09 ` George Michaelson
2022-06-22 2:16 ` Andrew Hume
2022-06-22 2:55 ` Brad Spencer
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=YrdfK5rguPEftall@alice \
--to=ality@pbrane.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).