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.0 required=5.0 tests=DKIMWL_WL_MED,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,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 86d64778 for ; Fri, 19 Apr 2019 02:39:26 +0000 (UTC) Received: by minnie.tuhs.org (Postfix, from userid 112) id E620A9B489; Fri, 19 Apr 2019 12:39:24 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id E667094EC3; Fri, 19 Apr 2019 12:38:58 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=pass (2048-bit key; unprotected) header.d=bsdimp-com.20150623.gappssmtp.com header.i=@bsdimp-com.20150623.gappssmtp.com header.b="G9ueLLFG"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id 0666E94EC3; Fri, 19 Apr 2019 12:38:57 +1000 (AEST) Received: from mail-qt1-f180.google.com (mail-qt1-f180.google.com [209.85.160.180]) by minnie.tuhs.org (Postfix) with ESMTPS id 3727594EB5 for ; Fri, 19 Apr 2019 12:38:56 +1000 (AEST) Received: by mail-qt1-f180.google.com with SMTP id v20so4312079qtv.12 for ; Thu, 18 Apr 2019 19:38:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=SuuiCKrtMoQWLZe+01q1pdMjiEHNgvDebYfumw4+mHI=; b=G9ueLLFGoNamBCtyLcPiV2qB3t2TdftTnlXW0m4irTpXkR2yCbcM56+hJzTtFUskJD kMD6/+xsA0bOKNPkbluUERjxWwLm2jTOb1E99G+vk3ysCbyYsitIR0GxIde9HPS48tz6 KHgwWMhS4qFWUDzjpsOiuWcoIX6GM1+GYcqADpI6bKmlYQKyo7M21uSINdhDdspBvw+H UmrLR9lJE+5ERhnvxL6awHVy+4DEiUSHaoujOtv3tLqXPs1PZa6hkdaJrZV1Y7TWFt5N Vx24iAslmL2rz/wgeDMZRpZ/EBP5IADXaU6yzLDqtR21yveSWRlaNhPbn8U9fTR7RxKL lO6g== 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=SuuiCKrtMoQWLZe+01q1pdMjiEHNgvDebYfumw4+mHI=; b=gNZ3YEsBtaf238j3KGkEf9sUbo30rGowq5hAu4oAv8B2BSvHyyLHGUMafw5Afbl26C nZO7l9JGMQ1wQKOr4RsiMU2XmaskZtl4iD9F6wmYob0BUbIg9pcvEMWEtfzGAV569rDx j5aPgQG6/fICd0uFAMHcPM0+KMyb+ByVSniLI7dbzyXyNE5zrZxz28hgLC/dl2dSLl8h KG4BbOvypEc9Oi1S0IE7zi9mXNucZ93FQcqTYtvhFPZsipQtLaKPoqnxZG4ktY1g2JX/ sQLlyjuUxp6MxIgYMEnBDpPUcM0RWrkjJ7YFpp6LSVmxti67Hz0UuotAVBmhY5M3a+2Z ydZg== X-Gm-Message-State: APjAAAXoXro4UC5BU4h0S7iqrXe4J8hlDRGpND14Yz43dLUwBSDL5ag8 R6Cftj3FqIdqZ9a5QpD9h0rrgWoVjZ9Ns5qE0kMgjLc4 X-Google-Smtp-Source: APXvYqwVHh0xu0e9fNANTCFXvTTU4BFfQ6E7pw9LdNULShr2+yc2zlMhUsNzJmqbPtLfkRANfhk5/Kk9i24aZsRQLzc= X-Received: by 2002:a0c:9e9a:: with SMTP id r26mr1411677qvd.57.1555641535006; Thu, 18 Apr 2019 19:38:55 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Warner Losh Date: Thu, 18 Apr 2019 20:38:44 -0600 Message-ID: To: "Jeremy C. Reed" Content-Type: multipart/alternative; boundary="00000000000017a0d80586d905fc" 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" --00000000000017a0d80586d905fc Content-Type: text/plain; charset="UTF-8" Can't help on the main thrust of this, but can answer one question... On Thu, Apr 18, 2019 at 8:33 PM wrote: > This email is two parts. I am researching 1970's symbolic name to > network address mapping routines. > > 1) I am looking for parsers for ancient (pre mid 1982) HOSTS.TXT. Since > this is Unix list, for Unix is fine :) > > RFC 597 (12 December 1973) says a hostname list will be maintained at > the NIC with the location to be announced. (Interestingly NIC as in > FEINLER@NIC is probably a nickname as it is not listed in the host > status list. I am guessing it is a nickname for SRI-ARC or OFFICE-1.) > NIC is probably what became know as SRI-NIC in latter days. By the time I joined the internet in the early 80s, SRI-NIC was where you registered your domain name. I just missed the hostfile by a few years. > RFC 607 (January 10, 1974) the NIC agrees that NIC maintain a text file > of hostnames, addresses, and attributes. (It has also been suggested > separately.) The source is maintained in NLS format with multiple > attributes. (What is this NLS format?) A program could be written to > generate a weekly ASCII file. They will write the program and the > generated file will be at OFFICE-1 (IMP #43?) with pathname of > HOSTS.TXT (It's not Unix. It's TENEX I think. The ">" is the > directory delimiter, but what is "<"?) > It's TENEX or TOPS-20 (they are the same for this purpose). FILE.EXT was the format. This was later extended to FILE.EXT. So the <> just contain the whole path, separated by dots. Warner --00000000000017a0d80586d905fc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Can't help on the main thrust of this= , but can answer one question...

On Thu, Apr 18, 2019 at 8:33 PM <reed@reedmedia.net> wrote:
<= blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l= eft:1px solid rgb(204,204,204);padding-left:1ex">This email is two parts. I= am researching 1970's symbolic name to
network address mapping routines.

1) I am looking for parsers for ancient (pre mid 1982) HOSTS.TXT. Since this is Unix list, for Unix is fine :)

RFC 597 (12 December 1973) says a hostname list will be maintained at
the NIC with the location to be announced. (Interestingly NIC as in
FEINLER@NIC is probably a nickname as it is not listed in the host
status list. I am guessing it is a nickname for SRI-ARC or OFFICE-1.)

NIC is probably what became know as SRI-NIC = in latter days. By the time I joined the internet in the early 80s, SRI-NIC= was where you registered your domain name. I just missed the hostfile by a= few years.
=C2=A0
RFC 607 (January 10, 1974) the NIC agrees that NIC maintain a te= xt file
of hostnames, addresses, and attributes. (It has also been suggested
separately.) The source is maintained in NLS format with multiple
attributes. (What is this NLS format?) A program could be written to
generate a weekly ASCII file. They will write the program and the
generated file will be at OFFICE-1 (IMP #43?) with pathname of
<NETINFO>HOSTS.TXT=C2=A0 (It's not Unix. It's TENEX I think. = The ">" is the
directory delimiter, but what is "<"?)
It's TENEX or TOPS-20 (they are the same for this purpose)= . <DIR>FILE.EXT was the format. This was later extended to <DIR.SU= B>FILE.EXT. So the <> just contain the whole path, separated by do= ts.

Warner
--00000000000017a0d80586d905fc--