The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Henry Bent <henry.r.bent@gmail.com>
To: Jan Schaumann <jschauma@netmeister.org>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] [COFF] Pondering the hosts file
Date: Thu, 11 Mar 2021 15:30:00 -0500	[thread overview]
Message-ID: <CAEdTPBfmSGxeUgzJZOsaS_qPuUUB=y=CXu4LMMi=47S-6pFv-A@mail.gmail.com> (raw)
In-Reply-To: <20210311200558.GW3990@netmeister.org>

[-- Attachment #1: Type: text/plain, Size: 1100 bytes --]

On Thu, Mar 11, 2021, 15:12 Jan Schaumann <jschauma@netmeister.org> wrote:

> "Nelson H. F. Beebe" <beebe@math.utah.edu> wrote:
> > The hosts file format definition appears in
> >
> >       RFC 752: Universal host table
> >       RFC 810: DoD Internet host table specification
> >       RFC 952: DoD Internet host table specification
> >
> > A 1986 hosts.txt file in my PDP-10 archives notes:
>
> The earliest copy of the hosts file I could find was
>
> http://pdp-10.trailing-edge.com/tops20_v6_1_tcpip_installation_tp_ft6/06/new-system/hosts.txt
>
> ;GIDNEY::<PAETZOLD.ARPANET>HOSTS.TXT.5, 27-Mar-85 13:11:54, Edit by
> PAETZOLD
> ;GIDNEY::<PAETZOLD.ARPANET>HOSTS.TXT.4, 25-Mar-85 13:56:55, Edit by
> PAETZOLD
> ;local stuff
>
> ; DoD Internet Host Table
> ;  22-Mar-85
> ;  Version number 436
>
> Does anybody have an earlier copy?
>
> -Jan


This was in the first page of Google search results for "DoD Internet Host
Table"; I bet with a little more research I could come up with something
much older.  Or one of the PDP-10 folks will find the original...

https://emaillab.jp/dns/hosts/

-Henry

[-- Attachment #2: Type: text/html, Size: 1881 bytes --]

  reply	other threads:[~2021-03-11 20:30 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 [this message]
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='CAEdTPBfmSGxeUgzJZOsaS_qPuUUB=y=CXu4LMMi=47S-6pFv-A@mail.gmail.com' \
    --to=henry.r.bent@gmail.com \
    --cc=jschauma@netmeister.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).