From: Paul Ruizendaal via TUHS <tuhs@minnie.tuhs.org>
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] [COFF] Pondering the hosts file
Date: Fri, 12 Mar 2021 11:53:05 +0100 [thread overview]
Message-ID: <1CD8545D-4D5C-4360-A5A1-3B931433C711@planet.nl> (raw)
BBN’s TCP implementation contained something akin to the hosts file, called hostmap there:
https://www.tuhs.org/cgi-bin/utree.pl?file=BBN-Vax-TCP/doc
I have not looked at the code for a while, but if I remember correctly the BBN kernel code also read in this file (pre-processed into a binary form) to build its internal routing table.
I do not recall having seen an equivalent file with UoI's NCP Unix in any of the surviving docs or sources - but that does not exclude a library having existed to do lookups in a local copy the SRI-NIC host file. In fact there is some evidence for that in the 2.9 BSD source.
The only surviving copy of the 4.1a (network) source code that I know is in the back-port of this code to 2.8/2.9 BSD. This code includes #ifdef’ed code for accessing the SRI-NIC online host table via NCP:
https://www.tuhs.org/cgi-bin/utree.pl?file=2.9BSD/usr/net/local
This source also contains tools to convert the SRI-NIC data into - inter alia - a hosts file:
https://www.tuhs.org/cgi-bin/utree.pl?file=2.9BSD/usr/net/man/man8/htable.8
https://www.tuhs.org/cgi-bin/utree.pl?file=2.9BSD/usr/net/man/man8/gettable.8c
It would seem that the modern host.txt on Unix evolved late ’81 (BBN code) to early ’82 (4.1a BSD). Possibly NCP Unix has prior work.
Paul
next reply other threads:[~2021-03-12 10:54 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 10:53 Paul Ruizendaal via TUHS [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-03-11 18:30 Bakul Shah
2021-03-11 17:13 [TUHS] " Grant Taylor via TUHS
2021-03-11 17:29 ` [TUHS] [COFF] " Steffen Nurpmeso
2021-03-11 17:40 ` [TUHS] " Bakul Shah
2021-03-11 18:08 ` [TUHS] [COFF] " Warner Losh
2021-03-11 18:12 ` Clem Cole
2021-03-11 18:21 ` Jaap Akkerhuis
2021-03-11 18:21 ` Nelson H. F. Beebe
2021-03-11 20:05 ` Jan Schaumann
2021-03-11 20:30 ` Henry Bent
2021-03-11 20:42 ` Henry Bent
2021-03-11 21:20 ` Henry Bent
2021-03-11 23:46 ` Richard Salz
2021-03-12 1:15 ` Jeremy C. Reed
2021-03-12 3:27 ` George Michaelson
2021-03-11 20:44 ` Lars Brinkhoff
2021-03-11 21:05 ` Henry Bent
2021-03-12 5:53 ` Lars Brinkhoff
2021-03-11 21:12 ` Ron Natalie
2021-03-11 22:33 ` Jeremy C. Reed
2021-03-11 18:27 ` Henry Bent
2021-03-11 18:18 ` Henry Bent
2021-03-11 18:02 ` Clem Cole
2021-03-11 20:32 ` Ron Natalie
2021-03-11 21:02 ` Bakul Shah
2021-03-11 21:08 ` Ron Natalie
2021-03-11 21:15 ` Bakul Shah
2021-03-12 1:14 ` Mary Ann Horton
2021-03-11 21:20 ` Grant Taylor via TUHS
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=1CD8545D-4D5C-4360-A5A1-3B931433C711@planet.nl \
--to=tuhs@minnie.tuhs.org \
--cc=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).