From: gingell at computer.org (Rob Gingell)
Subject: [COFF] ARPAnet now 4 nodes
Date: Thu, 5 Dec 2019 19:25:38 -0800 [thread overview]
Message-ID: <e56716da-f014-469e-e3b3-cfe99512b861@computer.org> (raw)
In-Reply-To: <011f01d5abd3$41187a30$c3496e90$@gmail.com>
On 12/5/19 5:19 PM, amp1ron at gmail.com wrote:
> Maybe some of these hosts files that Lars Brinkhoff gathered together will help:
>
> https://github.com/ttkzw/hosts.txt
Thanks for the pointer. I had come across those. The trouble is, for the
NCP era, there's only one host file in the collection. The rest are all
from the post-Internet transition (and thus the numbers can't be
inferred to convey a probable chronological sequence.)
And for the one from the NCP era, it's the one that only has the first
page and so it's missing a bunch of stuff. (It's not really a HOSTS.TXT
file but a prettified annotated edition with other information, and so
the file in the repository is a PDF of a scanned physical printout.)
Still even that one page adds some information. From the information
exchanged previously we had hosts 1 through 4, and then host 13. And the
likely matches for about two dozen numbers. And the fragment from the
one page in the repository adds 5 (though it's clear from the comments
that it was a recycled number), 9, 12, confirms 13, 14, 15, 16, and then
a smattering of others up to 232.
Some of the liaison names are tickling memories of long ago acquaintances!
I had thought that once upon a time there was an archive of a mid-1970s
TENEX distribution, like 1.33 or 1.34. The distribution might have
embedded a stale HOSTS.TXT file that would have been complete for the
time. But I haven't managed to find it again.
Still none of this really answers Larry's query in a satisfying way. I
imagine somewhere there's just a ledger that has the answer to the
question I thought he posed about who showed up when with what on the
ARPAnet. The collected papers of someone like Jon Postel might have
something of that nature (but a brief search doesn't reveal an archive
literally like that) but then substantial body of his work lives on in
the RFC library.
next prev parent reply other threads:[~2019-12-06 3:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 0:08 dave
2019-12-05 4:19 ` lm
2019-12-05 8:01 ` lars
2019-12-05 12:37 ` clemc
2019-12-05 18:20 ` gingell
2019-12-05 18:33 ` lars
2019-12-05 19:05 ` lm
2019-12-05 20:41 ` gingell
2019-12-06 1:19 ` amp1ron
2019-12-06 3:25 ` gingell [this message]
2019-12-06 4:19 ` amp1ron
2019-12-06 4:43 ` amp1ron
2019-12-06 17:33 jnc
2019-12-06 18:02 ` lm
2019-12-06 19:38 ` lars
2019-12-09 1:09 ` stewart
2020-12-04 21:05 dave
2020-12-05 23:14 jnc
2020-12-09 2:41 ` dave
2020-12-10 8:12 rudi.j.blom
2021-12-04 20:29 Dave Horsfall
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=e56716da-f014-469e-e3b3-cfe99512b861@computer.org \
--to=coff@minnie.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).