From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HTML_MESSAGE,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 28236 invoked from network); 11 Mar 2021 20:33:17 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 11 Mar 2021 20:33:17 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id 920AF9BC2A; Fri, 12 Mar 2021 06:33:15 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id 0E98F9507E; Fri, 12 Mar 2021 06:33:02 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=fail reason="signature verification failed" (1024-bit key; secure) header.d=mxes.net header.i=@mxes.net header.b="t3zoZMaE"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id 8D3989507E; Fri, 12 Mar 2021 06:33:00 +1000 (AEST) Received: from smtp-out-4.mxes.net (smtp-out-4.mxes.net [198.205.123.69]) by minnie.tuhs.org (Postfix) with ESMTPS id F04E695074 for ; Fri, 12 Mar 2021 06:32:58 +1000 (AEST) Received: from Customer-MUA (mua.mxes.net [10.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 4DxLHD1W7Hz3cBS; Thu, 11 Mar 2021 15:32:55 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mxes.net; s=mta; t=1615494777; bh=/BvXkqsgILZVD8/QAuYWy7LsHdBFGdC9IVlxWjDHSC0=; h=From:To:Subject:Date:Message-Id:In-Reply-To:References:Reply-To: Mime-Version:Content-Type; b=t3zoZMaEWpHXQ6S3qdYUz5naCbKaPfgjztE0hRb51UaU8k6kknBE94AZDY2khbAZB Who6VQtRRLR5bWdRE0amrmreTMHJVtaIc/ZP20f/bZ5yNWXVdQAbMSte7qYwiPwz2x Dw3dk6/fEA5qHk2yMZFAITs8YuiK8mEvmYuNbOH4= From: "Ron Natalie" To: "The Unix Heritage Society" Date: Thu, 11 Mar 2021 20:32:52 +0000 Message-Id: In-Reply-To: References: <02d10a8e-2f39-4f88-f4c9-ecb295e0f01e@spamtrap.tnetconsulting.net> User-Agent: eM_Client/8.1.1054.0 Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="------=_MB8CA99302-82E2-4422-9408-8F5742F71AE4" X-Sent-To: Subject: Re: [TUHS] [COFF] Pondering the hosts file 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: , Reply-To: Ron Natalie Cc: Internet History Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --------=_MB8CA99302-82E2-4422-9408-8F5742F71AE4 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Which hosts table? The Berkeley one or the REAL internet one? The Berkeley one (which I think may predate the IP implementation) is=20 the one that we know as /etc/hosts that has the address then the namees=20 of the hosts. The "real" one is the one the NIC put out in the pre-domain days. =20 It's defined in RFC 952, looks like HOST : 10.0.0.29 : BRL.ARPA, BRL : PDP-11/70 : UNIX : TCP : There was also a simple TCP service that would serve up the file. I detested the Berkeley one and we always downloaded and used the NIC=20 table on our machines. I rewrote "rhost" and it's successors=20 (gethostbyname, etc...) to read directly from the NIC format. Amusingly one day we got an Imagen ethernet-connected laser printer. =20 Mike Muuss decided the thing should be named BRL-ZAP and since I didn't=20 know what to put down as the machine type, and it did have a 68000 in=20 it, I had Jake put 68000 in the entry in the host table. The next day I got all kinds of hate mail from other BSD sites who=20 assumed I had intentionally sabotaged the host table. Apparently, the=20 BSD systems used a YACC grammar to parse the NIC table into the Berkeley=20 one. The only problem is they got the grammar wrong and assumed the=20 CPU type always began with a letter. There parse blew up on my "ZAP"=20 host and they assumed that was the desired effect. I countered back that using a YACC grammar for this was rediculous. =20 There was already a real popular file on UNIX that had a bunch of fields=20 separated by colons and commas (/etc/passwd anybody) that it was never=20 necessary to use YACC to parse. -Ron --------=_MB8CA99302-82E2-4422-9408-8F5742F71AE4 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable Which hosts table?=C2=A0 T= he Berkeley one or the REAL internet one?

The Berkeley = one (which I think may predate the IP implementation) is the one that we k= now as /etc/hosts that has the address then the namees of the hosts.
<= div>
The "real" one is the one the NIC put out in the pre-d= omain days.=C2=A0 =C2=A0 It's defined in RFC 952,=C2=A0 looks like

HOST : 10.0.0.29 : BRL.ARPA, BRL : PDP-11/70 : UNIX : TC= P :

There was also a simple TCP service that wou= ld serve up the file.

I detested the Berkeley on= e and we always downloaded and used the NIC table on our machines.=C2=A0 I= rewrote "rhost" and it's successors (gethostbyname, etc...) to read directl= y from the NIC format.

Amusingly one day we got= an Imagen ethernet-connected laser printer.=C2=A0 =C2=A0 Mike Muuss decided = the thing should be named BRL-ZAP and since I didn't know what to put down = as the machine type, and it did have a 68000 in it, I had Jake put 68000 i= n the entry in the host table.

The next day I go= t all kinds of hate mail from other BSD sites who assumed I had intentional= ly sabotaged the host table.=C2=A0 =C2=A0Apparently, the BSD systems used a = YACC grammar to parse the NIC table into the Berkeley one.=C2=A0 =C2=A0The = only problem is they got the grammar wrong and assumed the CPU type always = began with a letter.=C2=A0 =C2=A0 There parse blew up on my "ZAP" host and = they assumed that was the desired effect.

I cou= ntered back that using a YACC grammar for this was rediculous.=C2=A0 =C2=A0= There was already a real popular file on UNIX that had a bunch of fields se= parated by colons and commas (/etc/passwd anybody) that it was never necess= ary to use YACC to parse.

-Ron
--------=_MB8CA99302-82E2-4422-9408-8F5742F71AE4--