From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,HTML_FONT_LOW_CONTRAST, HTML_MESSAGE,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from minnie.tuhs.org (minnie.tuhs.org [45.79.103.53]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id 43381b22 for ; Fri, 19 Apr 2019 22:52:00 +0000 (UTC) Received: by minnie.tuhs.org (Postfix, from userid 112) id B625C93D27; Sat, 20 Apr 2019 08:51:58 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id 9E42B93D23; Sat, 20 Apr 2019 08:51:21 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=pass (1024-bit key; unprotected) header.d=ccc.com header.i=@ccc.com header.b="k14iw0ri"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id 7651193D23; Sat, 20 Apr 2019 08:51:19 +1000 (AEST) Received: from mail-wr1-f67.google.com (mail-wr1-f67.google.com [209.85.221.67]) by minnie.tuhs.org (Postfix) with ESMTPS id 0EBA893D21 for ; Sat, 20 Apr 2019 08:51:18 +1000 (AEST) Received: by mail-wr1-f67.google.com with SMTP id k17so8395957wrx.10 for ; Fri, 19 Apr 2019 15:51:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ccc.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=sS4krL5JI8lincz0k7EERe81hQX4RKKhot0BOP3ke4M=; b=k14iw0ridAYyL+dmCRbin5bzKsoazBAVVhkYGujrLbbvjPuk1X9LNPq8I6abqwxp9L fheRIRE+bdjr2+tHafeqv+LGH7Lj/cib+61DVMw9iHxVlg0RGPQihS+Gc4ASi8RjpTf4 3x5u6ZVW0eqf1YHdCuF17Duwkpdhnc1AXBgIo= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=sS4krL5JI8lincz0k7EERe81hQX4RKKhot0BOP3ke4M=; b=DTti4tre3RzxuRCs/Pmfgf1afn3Y7melKpK20AdSv21Orvk5VsR0BoiAcOxPWrNiww DZPNasV5pN3cQNCXaZ2aSj+ZsOM01O/kKlf6ttV0KvrSo+k30ExfSnwgmMI4o8R9zWUm 9ihWMN1YEOZ2q2fbOzgBpXUHQ2s5Lbs4GavDz2hld6QTgwEhn8GxQItGJEnJ8BidjnfW OofrLrv7XSGUS9sWk3oxLn6LqnNkgNr+NFmLx+RD1QxZIfora+eYUIt2EawERm+2t37W B8vRW8yjpc0WSVJGDv9+m2wc5pFkyuIOPjYdIcQoarKQKcueMcVSzzW4HSDf0Q5l0BXR RisQ== X-Gm-Message-State: APjAAAVkauQgxXH5OUt7KYWNYJsjcme3d3Y3M33s1ckxXplBRlvAIaTT bfpTSdOzEC9zs+ErCpbII2+2akOkZDSPsdSoeMypFQjrDZ8= X-Google-Smtp-Source: APXvYqyzxDZp/pUYDpWKZDLGikp5pxVfUwMCqVnDKvgJwWA3wH8inDlFUwXCa4oedwTUFrlbMBxNyeh2HBwGdhY+qmU= X-Received: by 2002:adf:e40b:: with SMTP id g11mr4436994wrm.207.1555714276430; Fri, 19 Apr 2019 15:51:16 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Clem Cole Date: Fri, 19 Apr 2019 18:50:50 -0400 Message-ID: To: "Jeremy C. Reed" Content-Type: multipart/alternative; boundary="000000000000d1bc780586e9f4d6" Subject: Re: [TUHS] looking for HOSTS.TXT parsers and how is /dev/net/HOSTNAME enabled? X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: TUHS main list Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --000000000000d1bc780586e9f4d6 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Frankly, I don't remember what Rob did but you might want to poke around the BBN archives too which Warren should also have. Gurwitz might have written something before the UCB code came about that used ftp. At CMU we used rsync between the UNIX boxes for files like the host table, (that where rsync was originally written for those that's don't know); but how it was kept up to date from the 10's -- I don't remember. As Lars said, MIT would have used ITS as its master before the DNS was birthed, but how the UNIX boxes got it from there is unknown to me [Noel do you know?]. Clem =E1=90=A7 =E1=90=A7 On Fri, Apr 19, 2019 at 5:53 PM wrote: > Replying to two messages here: > > On Fri, 19 Apr 2019, Lars Brinkhoff wrote: > > Here is a collection, but most of them are from after that date. > > > > https://github.com/ttkzw/hosts.txt > > Thanks. I should have mentioned I looked there. It doesn't have it as > far as I see. It has the same data for the pre-1982 files I already > have (but they are not RFC 608 style). > > But it was interesting to see the three MIT/Stanford versions. I think > they have a different format unless I misunderstand. Since I cannot find > SRI-NIC examples (before RFC 810) I don't know for sure. > https://github.com/ttkzw/hosts.txt/blob/master/pub/hosts/19830119/HOSTS.T= XT > > If you can point me to PDP-10 ITS routines, I'd appreciate it. > > On Fri, 19 Apr 2019, Clem Cole wrote: > > 1) I am looking for parsers for ancient (pre mid 1982) > ... > > Got to Warren's archives for BSD 4.2 and look for the htable(8) and > > gettable(8).? I believe the parsing routines will be in htable(8). > > Thanks. I have them already (including 4.1c.2). They are the newer > format. I had looked at htable before. I just looked at my sccs for it: > > MRs: > COMMENTS: > date and time created 82/10/20 21:26:49 by sam > > 4.1 #ifndef lint > 4.1 static char sccsid[] =3D "@(#)htable.c 4.1 (Berkeley) 10/20/82= "; > 4.1 #endif > 4.1 > 4.1 /* > 4.1 * htable - convert NIC host table into a UNIX format. > 4.1 * NIC format is described in RFC 810, 1 March 1982. > 4.1 */ > > I was hoping there was an early revision for previous format there, but > that is the first revision I see in SCCS. > > Thank you for reminding me and thanks for pointing me to gettable. I see > that is a TCP client implementation of the RFC 811 NIC Internet > Hostnames Server. Awesome. I will be writing about it. > > Just noticed the long-obsolete manpage has an error; it says: > > Gettable is a simple program used to obtain the NIC standard host > tables > from a ``nicname'' server. > ... > Gettable operates by opening a TCP connection to the port indicated = in > the service specification for ``nicname''. > > It is not a "nicname" client. It is a RFC 811 "hostnames" client. > > The first code before 4.2BSD has: > > sp =3D getservbyname("nicname", "tcp"); > > The later code has: > sp =3D getservbyname("hostnames", "tcp"); > > 4.1c.2 /etc/services had: > > nicname 101/tcp hostname # usually from sri-nic > > 4.2BSD /etc/services had: > > whois 43/tcp nicname > > hostnames 101/tcp hostname # usually from sri-nic > > nicname is RFC 812. > > but the manpage never got fixed (well I didn't look after FreeBSD 1.0 > which is the newest version of gettable I have). > > I was hoping that gettable(8) had HNAME/HADDR query commands then I > think it would be a very early network name lookup tool. But it just > had the ALL support to return entire host table. > > Still looking for the pre RFC 810 tables from SRI-NIC ... > > --000000000000d1bc780586e9f4d6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Frankly, I don't remember what Rob did but you migh= t want to poke around the BBN archives too which Warren should also have.= =C2=A0 =C2=A0 Gurwitz might have written something before the UCB code came= about that used ftp.=C2=A0 At CMU we used rsync between the UNIX boxes for= files like the host table, (that where rsync was originally written for th= ose that's don't know); but how it was kept up to date from the 10&= #39;s -- I don't remember.=C2=A0 =C2=A0As Lars said, MIT would have use= d ITS as its master before the DNS was birthed, but how the UNIX boxes got = it from there is unknown to me [Noel do you know?].

Cl= em
3D==E1=90=A7
3D""=E1=90=A7

On Fri, Apr 19, 2= 019 at 5:53 PM <= reed@reedmedia.net> wrote:
Replying to two messages here:

On Fri, 19 Apr 2019, Lars Brinkhoff wrote:
> Here is a collection, but most of them are from after that date.
>
> https://github.com/ttkzw/hosts.txt

Thanks. I should have mentioned I looked there. It doesn't have it as <= br> far as I see. It has the same data for the pre-1982 files I already
have (but they are not RFC 608 style).

But it was interesting to see the three MIT/Stanford versions. I think
they have a different format unless I misunderstand. Since I cannot find SRI-NIC examples (before RFC 810) I don't know for sure.=C2=A0
https://github.com/ttkzw/= hosts.txt/blob/master/pub/hosts/19830119/HOSTS.TXT

If you can point me to PDP-10 ITS routines, I'd appreciate it.

On Fri, 19 Apr 2019, Clem Cole wrote:
>=C2=A0 =C2=A0 =C2=A0 =C2=A01) I am looking for parsers for ancient (pre= mid 1982)
...
> Got to Warren's archives for BSD 4.2 and look for the htable(8) an= d
> gettable(8).? I believe the parsing routines will be in htable(8).

Thanks. I have them already (including 4.1c.2). They are the newer
format. I had looked at htable before. I just looked at my sccs for it:

MRs:
COMMENTS:
date and time created 82/10/20 21:26:49 by sam

4.1=C2=A0 =C2=A0 =C2=A0#ifndef lint
4.1=C2=A0 =C2=A0 =C2=A0static char sccsid[] =3D "@(#)htable.c=C2=A0 = =C2=A0 4.1 (Berkeley) 10/20/82";
4.1=C2=A0 =C2=A0 =C2=A0#endif
4.1=C2=A0 =C2=A0 =C2=A0
4.1=C2=A0 =C2=A0 =C2=A0/*
4.1=C2=A0 =C2=A0 =C2=A0 * htable - convert NIC host table into a UNIX forma= t.
4.1=C2=A0 =C2=A0 =C2=A0 * NIC format is described in RFC 810, 1 March 1982.=
4.1=C2=A0 =C2=A0 =C2=A0 */

I was hoping there was an early revision for previous format there, but that is the first revision I see in SCCS.

Thank you for reminding me and thanks for pointing me to gettable. I see that is a TCP client implementation of the RFC 811 NIC Internet
Hostnames Server. Awesome. I will be writing about it.

Just noticed the long-obsolete manpage has an error; it says:

=C2=A0 =C2=A0 =C2=A0Gettable is a simple program used to obtain the NIC sta= ndard host tables
=C2=A0 =C2=A0 =C2=A0from a ``nicname'' server.
...
=C2=A0 =C2=A0 =C2=A0Gettable operates by opening a TCP connection to the po= rt indicated in
=C2=A0 =C2=A0 =C2=A0the service specification for ``nicname''.

It is not a "nicname" client. It is a RFC 811 "hostnames&quo= t; client.

The first code before 4.2BSD has:

=C2=A0 =C2=A0 =C2=A0 =C2=A0 sp =3D getservbyname("nicname", "= ;tcp");

The later code has:
=C2=A0 =C2=A0 =C2=A0 =C2=A0 sp =3D getservbyname("hostnames", &qu= ot;tcp");

4.1c.2 /etc/services had:

nicname=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0101/tcp=C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0hostname=C2=A0 =C2=A0 =C2=A0 =C2=A0 # usually from sri-nic

4.2BSD /etc/services had:

whois=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A043/tcp=C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 nicname

hostnames=C2=A0 =C2=A0 =C2=A0 =C2=A0101/tcp=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0hostname=C2=A0 =C2=A0 =C2=A0 =C2=A0 # usually from sri-nic

nicname is RFC 812.

but the manpage never got fixed (well I didn't look after FreeBSD 1.0 <= br> which is the newest version of gettable I have).

I was hoping that gettable(8) had HNAME/HADDR query commands then I
think it would be a very early network name lookup tool. But it just
had the ALL support to return entire host table.

Still looking for the pre RFC 810 tables from SRI-NIC ...

--000000000000d1bc780586e9f4d6--