The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.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 15:13:25 -0700	[thread overview]
Message-ID: <CANCZdfrSnLm89mHh3PJJh4D6xJkQzcLRXxRWa5YuDY3waC+PgQ@mail.gmail.com> (raw)
In-Reply-To: <0C7FF60E-D7B1-434A-87D1-35E1102D7DC6@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 876 bytes --]

On Sat, Jan 29, 2022 at 2:49 PM 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?
>

DNS post-dates 4.3BSD. The first DNS RFC was published in Nov 1987. 4.3BSD
was June 1986. The host table update was a thing, but my school was far
enough off the beaten path that by the time we were on the internet, DNS
was a thing...

Warner

[-- Attachment #2: Type: text/html, Size: 1667 bytes --]

  parent reply	other threads:[~2022-01-29 22:13 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
2022-01-29 23:02     ` Theodore Y. Ts'o
2022-01-29 22:13 ` Warner Losh [this message]
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=CANCZdfrSnLm89mHh3PJJh4D6xJkQzcLRXxRWa5YuDY3waC+PgQ@mail.gmail.com \
    --to=imp@bsdimp.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).