From: gtaylor at tnetconsulting.net (Grant Taylor)
Subject: [COFF] Pondering the hosts file
Date: Thu, 11 Mar 2021 14:08:31 -0700 [thread overview]
Message-ID: <email@example.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1135 bytes --]
On 3/11/21 11:02 AM, Clem Cole wrote:
> Grant, are you asking about a multi-homed host?
I had specifically elided multi-homing for simplicity.
> IIRC the original BSD code did the first hit and stop, when looking
> something up.
That's my understanding.
> What we sometimes did was give the host an alias : host-en for the
> ethernet and host-pro proteon HW.
If I understand what you're saying:
192.0.2.1 host.example.net host-en
198.51.100.1 host.example.net host-pro
> Host would be on both lines, so you wanted to make the first 'host'
> to be the default.
I guess I shouldn't elide multi-homing and instead address it directly.
Or at least clarify the paradigm.
Should a given host name appear on more than one entry / line in the
hosts file if it's only got one IP (other than 127.0.0.1 / ::1)?
Grant. . . .
unix || die
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 4013 bytes
Desc: S/MIME Cryptographic Signature
prev parent reply other threads:[~2021-03-11 21:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 17:13 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
2021-03-11 18:02 ` [COFF] " clemc
2021-03-11 21:08 ` gtaylor [this message]
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).