From: Grant Taylor via TUHS <tuhs@minnie.tuhs.org>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] [COFF] Pondering the hosts file
Date: Thu, 11 Mar 2021 14:20:30 -0700 [thread overview]
Message-ID: <b6516987-a669-1717-bce3-a9fc09c47724@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <CAC20D2NgRziycz+25N3NfM1Q49dBz0Owzx+xOn3J2+dYcihrNQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 952 bytes --]
Cross-posting to TUHS my original response to COFF.
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.
*nod*
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
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4013 bytes --]
next prev parent reply other threads:[~2021-03-11 21:20 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
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 [this message]
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=b6516987-a669-1717-bce3-a9fc09c47724@spamtrap.tnetconsulting.net \
--to=tuhs@minnie.tuhs.org \
--cc=gtaylor@tnetconsulting.net \
/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).