From: henry.r.bent at gmail.com (Henry Bent)
Subject: [COFF] [TUHS] Pondering the hosts file
Date: Thu, 11 Mar 2021 13:18:20 -0500 [thread overview]
Message-ID: <CAEdTPBfejUkNfxW2efF5eQW5kCtX30AMVOMwvv1bTrcWNyHBLQ@mail.gmail.com> (raw)
While this is true wrt the history of FreeBSD/Unix, I'm almost positive
> that BSD didn't invent it. I'm pretty sure it was picked up from the
> existing host file that was published by sri-nic.arpa before DNS.
The CSRG history doesn't seem to have saved the full SCCS history of the
hosts manpage, but it must have appeared sometime around the addition of
ARP support to 4.1BSD - it's not in the 4.1C sources without ARP, but it is
in the sources with it. That version does indeed mention its origins:
HOSTS(5) File Formats Manual
hosts - host name data base
The hosts file contains information regarding the known hosts on
DARPA Internet. For each host a single line should be present with
official host name
Items are separated by any number of blanks and/or tab characters.
``#'' indicates the beginning of a comment; characters up to the end
the line are not interpreted by routines which search the file.
file is normally created from the official host data base maintained
the Network Information Control Center (NIC), though local changes
be required to bring it up to date regarding unofficial aliases
Network addresses are specified in the conventional ``.'' notation
ing the inet_addr() routine from the Internet address manipulation
brary, inet(3). Host names may contain any printable character
than a field delimiter, newline, or comment character.
A name server should be used instead of a static file. A binary
dexed file format should be available for fast access.
15 January 1983
-------------- next part --------------
An HTML attachment was scrubbed...
next prev parent reply other threads:[~2021-03-11 18:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 17:13 [COFF] " gtaylor
2021-03-11 17:29 ` steffen
2021-03-11 21:03 ` gtaylor
2021-03-11 21:21 ` bakul
2021-03-11 21:29 ` steffen
2021-03-11 17:40 ` [COFF] [TUHS] " bakul
2021-03-11 18:08 ` imp
2021-03-11 18:12 ` clemc
2021-03-11 18:21 ` jaapna
2021-03-11 18:21 ` beebe
2021-03-11 18:27 ` henry.r.bent
2021-03-11 18:18 ` henry.r.bent [this message]
2021-03-11 18:02 ` [COFF] " clemc
2021-03-11 21:08 ` gtaylor
2021-03-11 18:30 [COFF] [TUHS] " bakul
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).