From: Henry Bent <henry.r.bent@gmail.com>
To: Clem Cole <clemc@ccc.com>
Cc: The Unix Heritage Society <tuhs@minnie.tuhs.org>,
Bakul Shah <bakul@iitbombay.org>, COFF <coff@minnie.tuhs.org>,
Grant Taylor <gtaylor@tnetconsulting.net>,
Internet History <internet-history@postel.org>
Subject: Re: [TUHS] [COFF] Pondering the hosts file
Date: Thu, 11 Mar 2021 13:27:48 -0500 [thread overview]
Message-ID: <CAEdTPBdck300XiXwKyihJGHRsOeu0uOgNjTgs74UT3sfU6cgVA@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2OF_ERtaioLWdw5N3vik6orb34ZKt=fgfM4PyEq8Mnfjw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2765 bytes --]
On Thu, 11 Mar 2021 at 13:14, Clem Cole <clemc@ccc.com> wrote:
> The SRI file was different format. There was a tool that fetched and
> converted from the PDP-10 scheme to the UNIX scheme - gethtable(8) or
> something like that.
> ᐧ
> ᐧ
>
gettable(8) and htable(8):
GETTABLE(8C)
GETTABLE(8C)
NAME
gettable - get NIC format host tables from a host
SYNOPSIS
/etc/gettable host
DESCRIPTION
Gettable is a simple program used to obtain the NIC standard host
tables from a ``nicname'' server. The indicated host is queried for the
tables.
The tables, if retrieved, are placed in the file hosts.txt.
Gettable operates by opening a TCP connection to the port indicated
in the service specification for ``nicname''. A request is then made
for
``ALL'' names and the resultant information is placed in the output
file.
Gettable is best used in conjunction with the htable(8) program
which converts the NIC standard file format to that used by the network
library
lookup routines.
SEE ALSO
intro(3N), htable(8)
BUGS
Should allow requests for only part of the database.
4th Berkeley Distribution 4
March 1983
GETTABLE(8C)
HTABLE(8) System Manager's Manual
HTABLE(8)
NAME
htable - convert NIC standard format host tables
SYNOPSIS
/etc/htable file
DESCRIPTION
Htable is used to convert host files in the format specified in
Inter-
net RFC 810 to the format used by the network library routines.
Three
files are created as a result of running htable: hosts, networks,
and
gateways. The hosts file is used by the gethostent(3N) routines
in
mapping host names to addresses. The networks file is used by the
get-
netent(3N) routines in mapping network names to numbers. The
gateways
file is used by the routing daemon in identifying ``passive''
Internet
gateways; see routed(8C) for an explanation.
If any of the files localhosts, localnetworks, or localgateways
are
present in the current directory, the file's contents is prepended
to
the output file without interpretation. This allows sites to
maintain
local aliases and entries which are not normally present in the
master
database.
Htable is best used in conjunction with the gettable(8C) program
which
retrieves the NIC database from a host.
SEE ALSO
intro(3N), gettable(8C)
BUGS
Does not properly calculate the gateways file.
4th Berkeley Distribution 4 March 1983
HTABLE(8)
-Henry
[-- Attachment #2: Type: text/html, Size: 4511 bytes --]
next prev parent reply other threads:[~2021-03-11 18:28 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
2021-03-11 18:30 Bakul Shah
2021-03-12 10:53 Paul Ruizendaal 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=CAEdTPBdck300XiXwKyihJGHRsOeu0uOgNjTgs74UT3sfU6cgVA@mail.gmail.com \
--to=henry.r.bent@gmail.com \
--cc=bakul@iitbombay.org \
--cc=clemc@ccc.com \
--cc=coff@minnie.tuhs.org \
--cc=gtaylor@tnetconsulting.net \
--cc=internet-history@postel.org \
--cc=tuhs@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).