From: Clem Cole <clemc@ccc.com>
To: Warner Losh <imp@bsdimp.com>
Cc: The Unix Heritage Society <tuhs@minnie.tuhs.org>,
Bakul Shah <bakul@iitbombay.org>, COFF <coff@minnie.tuhs.org>,
Internet History <internet-history@postel.org>,
Grant Taylor <gtaylor@tnetconsulting.net>
Subject: Re: [TUHS] [COFF] Pondering the hosts file
Date: Thu, 11 Mar 2021 13:12:55 -0500 [thread overview]
Message-ID: <CAC20D2OF_ERtaioLWdw5N3vik6orb34ZKt=fgfM4PyEq8Mnfjw@mail.gmail.com> (raw)
In-Reply-To: <CANCZdfrfKBcj3s4gW=y2bLd2nuM0nnSVMA0ZkcJ300p6szyzWw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2243 bytes --]
The SRI file was different format. There was a tool that fetched and
converted from the PDP-10 scheme to the UNIX scheme - gethtable(8) or
something like that.
ᐧ
ᐧ
On Thu, Mar 11, 2021 at 1:08 PM Warner Losh <imp@bsdimp.com> wrote:
>
>
> On Thu, Mar 11, 2021 at 10:40 AM Bakul Shah <bakul@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@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: 4909 bytes --]
next prev parent reply other threads:[~2021-03-11 18:13 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 [this message]
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
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='CAC20D2OF_ERtaioLWdw5N3vik6orb34ZKt=fgfM4PyEq8Mnfjw@mail.gmail.com' \
--to=clemc@ccc.com \
--cc=bakul@iitbombay.org \
--cc=coff@minnie.tuhs.org \
--cc=gtaylor@tnetconsulting.net \
--cc=imp@bsdimp.com \
--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).