From: Clem Cole <clemc@ccc.com>
To: "Jeremy C. Reed" <reed@reedmedia.net>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] looking for HOSTS.TXT parsers and how is /dev/net/HOSTNAME enabled?
Date: Fri, 19 Apr 2019 14:43:40 -0400 [thread overview]
Message-ID: <CAC20D2OOtRZA0PXWUj6JJBHjWT3337dbzfN3VBT7NxKNJS5JoA@mail.gmail.com> (raw)
In-Reply-To: <alpine.NEB.2.21.1904181949240.2488@t1.m.reedmedia.net>
[-- Attachment #1: Type: text/plain, Size: 435 bytes --]
On Thu, Apr 18, 2019 at 10:33 PM <reed@reedmedia.net> 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 :)
>
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).
ᐧ
[-- Attachment #2: Type: text/html, Size: 1284 bytes --]
next prev parent reply other threads:[~2019-04-19 18:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-19 1:54 reed
2019-04-19 2:38 ` Warner Losh
2019-04-19 4:03 ` Lars Brinkhoff
2019-04-19 11:57 ` ron
2019-04-19 18:43 ` Clem Cole [this message]
2019-04-19 18:54 ` Clem Cole
2019-04-19 21:52 ` reed
2019-04-19 22:50 ` Clem Cole
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=CAC20D2OOtRZA0PXWUj6JJBHjWT3337dbzfN3VBT7NxKNJS5JoA@mail.gmail.com \
--to=clemc@ccc.com \
--cc=reed@reedmedia.net \
--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).