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=-1.0 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, HTML_MESSAGE,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 31853 invoked from network); 11 Mar 2021 21:03:51 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 11 Mar 2021 21:03:51 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id 220B59BB26; Fri, 12 Mar 2021 07:03:50 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id 068A49C2E5; Fri, 12 Mar 2021 07:03:07 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=pass (2048-bit key; unprotected) header.d=iitbombay-org.20150623.gappssmtp.com header.i=@iitbombay-org.20150623.gappssmtp.com header.b="DImoefGh"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id 4B8D59B92B; Fri, 12 Mar 2021 07:03:05 +1000 (AEST) Received: from mail-qv1-f53.google.com (mail-qv1-f53.google.com [209.85.219.53]) by minnie.tuhs.org (Postfix) with ESMTPS id 209D89C5FD for ; Fri, 12 Mar 2021 07:02:54 +1000 (AEST) Received: by mail-qv1-f53.google.com with SMTP id x27so3241638qvd.2 for ; Thu, 11 Mar 2021 13:02:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iitbombay-org.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=H/A3aiV2opUB1XvFFRsu/RyLgZWsxjlcDOJg4B7aQD8=; b=DImoefGhgF5TJynwxr7e1VNM8dxeDKkfEpig/r591BS2/BN7KdUQcdN0UcXWIficLn the6j0FkFu5QgDKEP2Fj1YpYMeqep+mGt+A1Fk0QrYL0aIay0OatDii/ga9521TYepwk U23qO1DQCXGxtPfsUbzxls7EloFELhrY8J4bpFhzXUZn+Os6TvmEClfvzAsu2oU/wolA Ky/JJcoqygqGhXb1QLxE9lRUlvSLLq78ydkop6W+YEoXLz7XTe39ONY2nSvSbDgjIGNZ i0fZ6BxdwYzZzMBn5XwBk4jZBUKMbl01oiAMl0IVD4Ap4+TUfXLQQqxQ8gziyXOmjK2F hqww== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=H/A3aiV2opUB1XvFFRsu/RyLgZWsxjlcDOJg4B7aQD8=; b=XMwa+t5xzreXDzPeMMjwzlJwhdCkBDI+m7+BK6dFewY0mz5oqN9IQW6JzQVTTbH3JE oi3YQUDN+FosicUQnFn7jpa1epNmxV4sO79lGE1apO/EJQo5lNLbmYuQmgTb6xuDDtZu OQMRXqgdaIVcUNxyQ97uS9dG3MLdggWP6Wq+TiBwnmJKu7tie4/XthGBYcn+ToXCYG/g jECk8lE/UHZLoZ02VdemjBpV4JlKxAhcmfyuMijHXjoOvTQHPb8LTn4668EzBAhJMrGO 7SgcvEHeOJ++PCF8+OuFSBtUXSdvObb/2Yg/QCwbA+LJNhM9uVR/zovE2tkCE0VJQoJm 6PKg== X-Gm-Message-State: AOAM532XoDXY/lKy8VwRk7aAbgDxX/s+SQqpvRGvIS+4b48vIXyBqQ1P Y/JfJBfPGpUhTJJGBIRdAIWaEaEk3LuCzQ== X-Google-Smtp-Source: ABdhPJzPWv8K1YAJHb8LP3I6ag4wuO/qAASxyLn20onsWBissd15+j4Q1av6+7mUUtYrZz2JJ7aYww== X-Received: by 2002:a0c:d843:: with SMTP id i3mr3955644qvj.16.1615496573297; Thu, 11 Mar 2021 13:02:53 -0800 (PST) Received: from [192.168.125.11] (107-215-223-229.lightspeed.sntcca.sbcglobal.net. [107.215.223.229]) by smtp.gmail.com with ESMTPSA id 18sm2959417qkr.90.2021.03.11.13.02.51 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 11 Mar 2021 13:02:52 -0800 (PST) From: Bakul Shah Message-Id: <555F9514-DD67-41F1-8151-480F0D9D0EAC@iitbombay.org> Content-Type: multipart/alternative; boundary="Apple-Mail=_A201FDDF-E37F-4146-ABDA-500F61502B3A" Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\)) Date: Thu, 11 Mar 2021 13:02:50 -0800 In-Reply-To: To: Ron Natalie References: <02d10a8e-2f39-4f88-f4c9-ecb295e0f01e@spamtrap.tnetconsulting.net> X-Mailer: Apple Mail (2.3654.60.0.2.21) 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: , Cc: The Unix Heritage Society , Internet History Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --Apple-Mail=_A201FDDF-E37F-4146-ABDA-500F61502B3A Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On Mar 11, 2021, at 12:32 PM, Ron Natalie wrote: >=20 > Amusingly one day we got an Imagen ethernet-connected laser printer. = 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 in the entry in the host table. >=20 > The next day I got all kinds of hate mail from other BSD sites who = assumed I had intentionally sabotaged the host table. Apparently, the = BSD systems used a YACC grammar to parse the NIC table into the Berkeley = one. The only problem is they got the grammar wrong and assumed the = CPU type always began with a letter. There parse blew up on my "ZAP" = host and they assumed that was the desired effect. This is understandable as a) All the "official machine names" in various assigned numbers RFCs = start with a letter. b) the BNF syntax for the "host table specification" entries in RFC 952 = or 810 are not precise enough. ::=3D PDP-11/70 | DEC-1080 | C/30 | CDC-6400...etc. NOTE: See "Assigned Numbers" for specific options and acronyms for machine types, operating systems, and protocol/services. for machine types, operating systems, and protocol/services. c) 68000 was not an official name! :-) :-) :-) > I countered back that using a YACC grammar for this was rediculous. = There was already a real popular file on UNIX that had a bunch of fields = separated by colons and commas (/etc/passwd anybody) that it was never = necessary to use YACC to parse. Can't argue with that! Though that doesn't mean a handwritten parser = wouldn't have complained about 68000. --Apple-Mail=_A201FDDF-E37F-4146-ABDA-500F61502B3A Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii On = Mar 11, 2021, at 12:32 PM, Ron Natalie <ron@ronnatalie.com> = wrote:

Amusingly one day we got an Imagen ethernet-connected = laser printer.    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 in the entry in the = host table.

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

This is understandable as
a) All the = "official machine names" in various assigned numbers RFCs start with a = letter.
b) the BNF syntax for the "host table = specification" entries in RFC 952 or 810 are not precise = enough.
	<cputype> ::=3D PDP-11/70 | =
DEC-1080 | C/30 | CDC-6400...etc.

NOTE:  See "Assigned Numbers" for =
specific options and acronyms
         for machine types, operating systems, and protocol/services.

         for machine types, =
operating systems, and protocol/services.

c) 68000 was not =
an official name!
:-) :-) =
:-)

I = countered back that using a YACC grammar for this was rediculous.  =  There was already a real popular file on UNIX that had a bunch of = fields separated by colons and commas (/etc/passwd anybody) that it was = never necessary to use YACC to parse.

Can't argue with that! Though that doesn't mean a = handwritten parser wouldn't have complained about 68000.

= --Apple-Mail=_A201FDDF-E37F-4146-ABDA-500F61502B3A--