The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <>
To: Will Senn <>
Subject: Re: [TUHS] 4.3 BSD network name resolution
Date: Sat, 29 Jan 2022 17:59:02 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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

Isn't time wonderful .....   4.2 and 4.3BSD predates the release of bind,
which was separately sent into the wild..

The good news is that you can certainly get things working with a static
host table.   And frankly for a simulated system, the network is likely to
be very small and you are unlikely to need more modern services like a
browser with URLs et al.   That said, the early bind will work on 4.2/4.3
without a lot of hassle, as that's the system that it was developed.
Except .....   the problem is the >>client side<< is used all over the
place AND that needs to know you a DNS.

My suggestion is getting 4.3 running up with a very small (static) host
table.   Then take on the DNS.   The resolv library (client code) is likely
to have a lot of static calls to the old (non-DNS based) versions of
gethostbyXXX and the like.   If you bring bind over, you'r probably going
to have to do a full rebuild and relink , reinstall of applications space
clients use the DNS, not the static tables.

Have fun.


On Sat, Jan 29, 2022 at 4:49 PM Will Senn <> 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
> not to work in 4.3, or by some miracle is gettable still a
> functional system?
> Will
> Sent from my iPhone

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

  parent reply	other threads:[~2022-01-29 22:59 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
2022-01-29 22:25   ` George Michaelson
2022-01-29 22:35     ` Erik E. Fair
2022-01-29 22:59 ` Clem Cole [this message]
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).