From: gtaylor at tnetconsulting.net (Grant Taylor)
Subject: [COFF] Pondering the hosts file
Date: Thu, 11 Mar 2021 10:13:50 -0700 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
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
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 4013 bytes
Desc: S/MIME Cryptographic Signature
next reply other threads:[~2021-03-11 17:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 17:13 gtaylor [this message]
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
2021-03-11 18:02 ` [COFF] " clemc
2021-03-11 21:08 ` gtaylor
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).