From: imp at bsdimp.com (Warner Losh)
Subject: [COFF] [TUHS] Pondering the hosts file
Date: Thu, 11 Mar 2021 11:08:03 -0700 [thread overview]
Message-ID: <CANCZdfrfKBcj3s4gW=y2bLd2nuM0nnSVMA0ZkcJ300p6szyzWw@mail.gmail.com> (raw)
In-Reply-To: <120EC052-FB1F-438F-985F-64E9CD82A9C1@iitbombay.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2042 bytes --]
On Thu, Mar 11, 2021 at 10:40 AM Bakul Shah <bakul at iitbombay.org> wrote:
> From https://www.freebsd.org/cgi/man.cgi?hosts(5)
>
> For each host a single line should be present with the following information:
>
> Internet address
> official host name
> aliases
>
> *HISTORY* <https://www.freebsd.org/cgi/man.cgi?hosts(5)#end>
> The *hosts* file format appeared in 4.2BSD.
>
>
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.
Warner
> On Mar 11, 2021, at 9:14 AM, Grant Taylor via TUHS <tuhs at minnie.tuhs.org>
> wrote:
>
> Hi,
>
> I'm not sure where this message best fits; TUHS, COFF, or Internet
> History, so please forgive me if this list is not the best location.
>
> I'm discussing the hosts file with someone and was wondering if there's
> any historical documentation around it's format and what should and should
> not be entered in the file.
>
> I've read the current man page on Gentoo Linux, but suspect that it's far
> from authoritative. I'm hoping that someone can point me to something more
> authoritative to the hosts file's format, guidelines around entering data,
> and how it's supposed to function.
>
> A couple of sticking points in the other discussion revolve around how
> many entries a host is supposed to have in the hosts file and any
> ramifications for having a host appear as an alias on multiple lines /
> entries. To whit, how correct / incorrect is the following:
>
> 192.0.2.1 host.example.net host
> 127.0.0.1 localhost host.example.net host
>
>
>
> --
> Grant. . . .
> unix || die
>
> _______________________________________________
> COFF mailing list
> COFF at minnie.tuhs.org
> https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20210311/a5d2f615/attachment.htm>
next prev parent reply other threads:[~2021-03-11 18:08 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 [this message]
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
2021-03-11 18:02 ` [COFF] " clemc
2021-03-11 21:08 ` gtaylor
2021-03-11 18:30 [COFF] [TUHS] " bakul
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='CANCZdfrfKBcj3s4gW=y2bLd2nuM0nnSVMA0ZkcJ300p6szyzWw@mail.gmail.com' \
--to=coff@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).