From: Henry Bent <henry.r.bent@gmail.com>
To: Will Senn <will.senn@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] 4.3 BSD network name resolution
Date: Sat, 29 Jan 2022 17:08:32 -0500 [thread overview]
Message-ID: <CAEdTPBd1ABWgMWSs8dv_Uvtm4VKE-FWG6KnRz+pkmZj49HBpOQ@mail.gmail.com> (raw)
In-Reply-To: <CAEdTPBdN9obvF7GNqwAMvFcEqJhTnrO80esN3HHZogGpMd39MA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1473 bytes --]
On Sat, 29 Jan 2022 at 16:56, Henry Bent <henry.r.bent@gmail.com> wrote:
> On Sat, 29 Jan 2022 at 16:49, Will Senn <will.senn@gmail.com> wrote:
>
>> I'm working through 4.3BSD setup and configuration and came across this:
>>
>>
>> "There is no equivalent service for network names yet. The full host and
>> network name databases are normally derived from a file retrieved from
>> Internet Network Information Center at SRI... use gettable to retrieve the
>> NIC host database and htable to convert it to the format used by the
>> libraries."
>>
>>
>> Does this mean I should expect functionality like resolv.conf and ping
>> yahoo.com not to work in 4.3, or by some miracle is gettable still a
>> functional system?
>>
>
> gettable uses flat files to map names to numbers. It hasn't existed in
> probably 30+ years, and I can't even imagine how large the files it creates
> would be for the modern internet.
>
> Amusingly, for some strange reason it still exists in Solaris 11.2:
> https://docs.oracle.com/cd/E36784_01/html/E36871/gettable-1m.html
>
>
A quick search found me a site with an archive of the HOSTS.TXT files that
gettable and friends used: https://emaillab.jp/dns/hosts/
To give you an idea of how soon things were obsolete, the files from the
'90s have 132.162.32.243 listed as Oberlin's VAX 11/780 ocvaxa, a machine
that had not existed for many years at that point. The distributed nature
of DNS made things much, much easier to keep current.
-Henry
[-- Attachment #2: Type: text/html, Size: 2712 bytes --]
next prev parent reply other threads:[~2022-01-29 22:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 21:48 Will Senn
2022-01-29 21:56 ` Henry Bent
2022-01-29 22:08 ` Henry Bent [this message]
2022-01-29 23:02 ` Theodore Y. Ts'o
2022-01-29 22:13 ` Warner Losh
2022-01-29 22:25 ` George Michaelson
2022-01-29 22:35 ` Erik E. Fair
2022-01-29 22:59 ` Clem Cole
2022-01-29 23:24 ` Phil Budne
2022-01-30 0:09 ` Jeremy C. Reed
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=CAEdTPBd1ABWgMWSs8dv_Uvtm4VKE-FWG6KnRz+pkmZj49HBpOQ@mail.gmail.com \
--to=henry.r.bent@gmail.com \
--cc=tuhs@tuhs.org \
--cc=will.senn@gmail.com \
/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).