From: Clem Cole <clemc@ccc.com>
To: Grant Taylor <gtaylor@tnetconsulting.net>
Cc: Internet History <internet-history@postel.org>,
The Unix Heritage Society <tuhs@minnie.tuhs.org>,
COFF <coff@minnie.tuhs.org>
Subject: Re: [TUHS] [COFF] Pondering the hosts file
Date: Thu, 11 Mar 2021 13:02:22 -0500 [thread overview]
Message-ID: <CAC20D2NgRziycz+25N3NfM1Q49dBz0Owzx+xOn3J2+dYcihrNQ@mail.gmail.com> (raw)
In-Reply-To: <02d10a8e-2f39-4f88-f4c9-ecb295e0f01e@spamtrap.tnetconsulting.net>
[-- Attachment #1: Type: text/plain, Size: 1643 bytes --]
Grant, are you asking about a multi-homed host?
IIRC the original BSD code did the first hit and stop, when looking
something up. What we sometimes did was give the host an alias : host-en
for the ethernet and host-pro proteon HW. Host would be on both lines, so
you wanted to make the first 'host' to be the default.
ᐧ
On Thu, Mar 11, 2021 at 12:13 PM Grant Taylor via COFF <coff@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@minnie.tuhs.org
> https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff
>
[-- Attachment #2: Type: text/html, Size: 2902 bytes --]
next prev parent reply other threads:[~2021-03-11 18:03 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 [this message]
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
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=CAC20D2NgRziycz+25N3NfM1Q49dBz0Owzx+xOn3J2+dYcihrNQ@mail.gmail.com \
--to=clemc@ccc.com \
--cc=coff@minnie.tuhs.org \
--cc=gtaylor@tnetconsulting.net \
--cc=internet-history@postel.org \
--cc=tuhs@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).