From: Paul Ruizendaal <pnr@planet.nl>
To: Anthony Martin <ality@pbrane.org>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Research Datakit notes
Date: Sun, 26 Jun 2022 13:04:39 +0200 [thread overview]
Message-ID: <14E73B91-1A99-4A14-9EE2-6331A4804C27@planet.nl> (raw)
In-Reply-To: <Yre5RfvTGz1ZLBG8@alice>
> On 26 Jun 2022, at 03:41, Anthony Martin <ality@pbrane.org> wrote:
>
> Really nice outline. I felt some déjà vu when opening the document: I
> remember reading your notes in April of 2020.
Thank you. Yes, I have not updated these notes since then.
> Would you happen to know where I can find copies of these three
> papers?
>
> A. G. Fraser, "Datakit - A Modular Network for Synchronous and
> Asynchronous Traffic", Proc. ICC 79, June 1979, Boston, Ma.,
> pp.20.1.1-20.1.3
>
> G. L. Chesson, "Datakit Software Architecture", Proc. ICC 79, June
> 1979, Boston Ma., pp.20.2.1-20.2.5
>
> G. L. Chesson and A. G. Fraser, "Datakit Network Architecture," Proc.
> Compcon 80, February 1980, San Fransisco CA., pp.59-61
Two of these three were in Sandy Fraser’s archives:
https://www.jslite.net/notes/dk1.pdf
https://www.jslite.net/notes/dk2.pdf
The middle one is I fear lost - unless a paper copy of the proceedings is still lurking in some university library. I think it will be mostly about the “CMC” switch control software, which is somewhat described in the Luderer paper as well. As far as I can tell, there is no surviving Unix code that was designed for the CMC version of Datakit (unless someone is sitting on a V7 tape with the Datakit drivers still included).
> To connect to one of the Plan 9 cpu servers at Bell Labs, you would
> dial "nj/astro/helix!9fs”.
Out of interest, would you know if the switch-host interface for Datakit in the days of Plan9 worked more or less the same as in 8th Edition? Or had it much evolved by then?
next prev parent reply other threads:[~2022-06-26 11:05 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-25 23:01 [TUHS] " Paul Ruizendaal
2022-06-25 23:09 ` [TUHS] " Larry McVoy
2022-06-25 23:57 ` Rob Pike
2022-06-26 1:17 ` Paul Ruizendaal
2022-07-02 2:51 ` Grant Taylor via TUHS
2022-07-02 2:57 ` Larry McVoy
2022-06-28 10:38 ` Derek Fawcus
2022-06-28 12:36 ` Rob Pike
2022-06-28 12:45 ` Rob Pike
2022-06-28 13:33 ` Dan Cross
2022-06-28 21:19 ` Lawrence Stewart
2022-06-28 21:34 ` Richard Salz
2022-06-29 6:07 ` Stuart Remphrey
2022-06-28 16:11 ` Tom Teixeira
2022-06-28 18:28 ` John Floren
2022-06-28 12:47 ` Rich Morin
2022-06-28 13:13 ` Marc Donner
2022-06-28 14:41 ` Clem Cole
2022-06-28 15:54 ` Tom Teixeira
2022-06-28 17:05 ` Adam Thornton
2022-06-28 17:43 ` John Labovitz
2022-06-28 22:45 ` [TUHS] HTTP (was Re: Re: Research Datakit notes) Derek Fawcus
2022-06-26 1:41 ` [TUHS] Re: Research Datakit notes Anthony Martin
2022-06-26 9:52 ` Ralph Corderoy
2022-06-26 11:04 ` Paul Ruizendaal [this message]
2022-06-29 20:21 ` Paul Ruizendaal
2022-06-26 2:19 Noel Chiappa
2022-06-26 9:46 ` steve jenkin
2022-06-26 20:35 ` Erik Fair
2022-06-26 21:53 ` Steve Jenkin
2022-06-26 10:16 ` Paul Ruizendaal via TUHS
2022-06-26 13:07 ` John Cowan
2022-06-26 13:35 ` Larry McVoy
2022-06-26 13:58 ` John Cowan
2022-06-27 0:43 Noel Chiappa
2022-06-27 3:00 ` Erik Fair
2022-06-27 21:40 Noel Chiappa
2022-06-27 22:40 ` George Michaelson
2022-06-28 15:50 Noel Chiappa
2022-06-28 21:32 ` Lawrence Stewart
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=14E73B91-1A99-4A14-9EE2-6331A4804C27@planet.nl \
--to=pnr@planet.nl \
--cc=ality@pbrane.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).