The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: pnr@planet.nl (Paul Ruizendaal)
Subject: [TUHS] Unix with TCP/IP for small PDP-11s
Date: Tue, 23 May 2017 02:36:06 +0200	[thread overview]
Message-ID: <B4993820-5C5E-491D-BEAD-1B2E1CBD66D7@planet.nl> (raw)
In-Reply-To: <CAC20D2NP4C9V_0Rm93ka9zR572nFHYyJ-MU_+HeLbTws4rH+vw@mail.gmail.com>


On 23 May 2017, at 1:25 , Clem Cole wrote:

> As for DataKit et al..  Greg Chesson was a grad student at UoI.  The UoI folks did the original  V6 Arpanet for UNIX code and Greg was the one of the primary developers same.  What I do not remember is who came first, the Rand networking work for the UoI work.   Rand did the the ports (later called named pipes) and a few other things pretty early.   But again all those dates sort of mix together in the early middle 70s.  USENIX was not yet publishing proceedings so it's hard to keep straight.   It pretty much just email and memories of those of us that were sharing things at the time.

These dates I can fill in:
- UoI Arpanet Unix was initially done between December 1974 and March 1975, building on the experience gained with the earlier ANTS I and II projects.
- Rand ports were done in 1977, under contract to the air force (report dated June '77).

> Anyway, when Greg graduated, he was hired by Ken when he finished and developed DataKit at Bell labs.   One of the pieces of datakit that was released as part of V7 was Greg's mpx(2) code - which was the multiplexer.

Interesting. I always thought that mpx files were driven by the work on the Blit terminal, the link to networking is new to me.

I'm looking into the history of Spider and early Datakit. Sandy Fraser was kind enough to send me the 1974 report on Spider and it already mentions actual usage for remote printing, remote login and a central 'file store'. Spider was an interesting bit of technology, essentially it linked a dozen or so computers over a 1.5Mb/s shared link (a daisy chained twisted pair cable) to a central router/switch. There was only ever one Spider router, but the design allowed for multiple routers to be connected over T1 long distance lines.

Does anybody know of surviving v5/v6/v7 code for Spider networking (e.g. the 'tiu' device driver, the 'nfs' file transfer package, etc.)?



  reply	other threads:[~2017-05-23  0:36 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-22  9:28 Paul Ruizendaal
2017-05-22 14:09 ` Clem Cole
2017-05-22 14:51   ` Steve Simon
2017-05-22 16:29     ` Clem Cole
2017-05-22 16:35       ` Ron Natalie
2017-05-22 22:07       ` Paul Ruizendaal
2017-05-22 23:25         ` Clem Cole
2017-05-23  0:36           ` Paul Ruizendaal [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-05-24 15:21 Noel Chiappa
2017-05-24 17:19 ` Jeremy C. Reed
     [not found] <mailman.1.1495591202.25149.tuhs@minnie.tuhs.org>
2017-05-24  9:20 ` Paul Ruizendaal
2017-05-23 13:43 Noel Chiappa
2017-05-23 11:35 Paul Ruizendaal
2017-05-23  1:33 Noel Chiappa
2017-05-23  1:14 Noel Chiappa
     [not found] <mailman.1.1495245601.20449.tuhs@minnie.tuhs.org>
2017-05-20 10:46 ` Johnny Billquist
2017-05-20 17:39   ` Henry Bent
2017-05-20 20:40     ` Johnny Billquist
2017-05-20 20:44       ` Henry Bent
2017-05-20 18:18   ` Warner Losh
2017-05-20 19:05     ` arnold
2017-05-20 20:29       ` Warner Losh
2017-05-20 21:41       ` David Arnold
2017-05-20 21:59         ` Erik E. Fair
2017-05-20 20:40     ` Johnny Billquist
2017-05-20 21:05       ` Warner Losh
2017-05-20 21:34         ` Johnny Billquist
2017-05-21  5:13           ` Random832
2017-05-21 11:04             ` Ron Natalie
2017-05-19 15:15 Noel Chiappa
2017-05-19 16:29 ` Henry Bent
2017-05-19 19:04   ` Ron Natalie
2017-05-20  0:15     ` Warner Losh
2017-05-20  0:21       ` Warner Losh
2017-05-19 17:39 ` Clem Cole
2017-05-21 16:16   ` Dave Horsfall
2017-05-21 19:58     ` Clem Cole
2017-05-21 20:57       ` Ron Natalie
2017-05-21 21:26         ` Clem Cole
2017-05-21 21:46         ` William Pechter

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=B4993820-5C5E-491D-BEAD-1B2E1CBD66D7@planet.nl \
    --to=pnr@planet.nl \
    /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).