From: pnr@planet.nl (Paul Ruizendaal)
Subject: [TUHS] Early Internet work (Was: History of select(2))
Date: Mon, 30 Jan 2017 22:20:45 +0100 [thread overview]
Message-ID: <ADD89732-6B8E-4811-98A9-BEA39CA8B2BB@planet.nl> (raw)
In-Reply-To: <20170130153426.D9CFA18C0B4@mercury.lcs.mit.edu>
On 30 Jan 2017, at 16:34 , Noel Chiappa wrote:
>
>>> the headers say they date from 1974-75.
>
>> Wow, that's great! That means that you have the initial version.
>
> The file write dates are May 1979, so that's the latest it can be. There is
> one folder called 'DTI' which contains an email message from someone at DTI to
> someone at SRI which is dated "10 Apr 1979" so that seems to indicate that
> that's indeed when they are from.
Based on that extra info I think you have a later version of Network Unix, which
is still wonderful and exciting.
> I could have sworn that I'd seen _listings_ of the code in a UIllinois
> document about NCP Unix that I had found (and downloaded) on the Internet, but
> I can't find them here now. I did look again and found:
>
> "A Network Unix System for the Arpanet", by Karl C. Kelley, Richard Balocca,
> and Jody Kravitz
>
> but it doesn't contain any sources.
The initial 1975 implementation was - in the authors' recollection - only some
one to two thousand lines of extra kernel code and one thousand for the NCP
daemon. That would make for some 50 pages of printout. It is possible.
I know the Kelley document well and sections 5 and 6 contain a fairly
detailed code walkthrough. Perhaps this is what lingered in your memory.
I suspect this (Oct 1978) code walkthrough will match with the code on your
tape.
next prev parent reply other threads:[~2017-01-30 21:20 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-30 15:34 Noel Chiappa
2017-01-30 21:20 ` Paul Ruizendaal [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-01-30 16:15 Noel Chiappa
2017-01-30 16:41 ` Clem Cole
2017-01-30 16:44 ` Clem Cole
2017-01-30 2:50 Noel Chiappa
2017-01-30 3:33 ` Nick Downing
2017-01-30 3:38 ` Ron Natalie
2017-02-08 3:58 ` Dave Horsfall
2017-01-30 8:26 ` Paul Ruizendaal
2017-01-30 1:44 Noel Chiappa
2017-01-29 18:35 Noel Chiappa
2017-01-29 17:41 Noel Chiappa
2017-01-29 20:28 ` Paul Ruizendaal
2017-01-30 1:34 ` Nick Downing
2017-01-30 2:19 ` Clem Cole
2017-01-30 2:30 ` Larry McVoy
2017-01-30 2:43 ` Ron Natalie
2017-01-30 2:43 ` Clem Cole
2017-01-30 2:32 ` Larry McVoy
2017-01-30 2:39 ` Clem Cole
2017-01-30 13:13 ` Dave Horsfall
2017-01-30 13:37 ` Larry McVoy
2017-01-16 15:17 Noel Chiappa
2017-01-16 14:42 Noel Chiappa
[not found] <mailman.1.1484532001.2693.tuhs@minnie.tuhs.org>
2017-01-16 10:21 ` Johnny Billquist
2017-01-16 1:47 Noel Chiappa
2017-01-16 10:06 ` Paul Ruizendaal
2017-01-16 1:01 Noel Chiappa
2017-01-16 10:31 ` Paul Ruizendaal
2017-01-16 12:07 ` Tony Finch
2017-01-15 2:30 Noel Chiappa
2017-01-13 13:19 Noel Chiappa
2017-01-09 2:35 [TUHS] History of select(2) Warren Toomey
2017-01-09 10:36 ` Paul Ruizendaal
2017-01-12 3:54 ` Clem Cole
2017-01-13 9:13 ` Paul Ruizendaal
[not found] ` <20170114164102.GA31665@yeono.kjorling.se>
2017-01-16 0:13 ` [TUHS] Early Internet work (Was: History of select(2)) 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=ADD89732-6B8E-4811-98A9-BEA39CA8B2BB@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).