The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: George Michaelson <ggm@algebras.org>
To: "Jeremy C. Reed" <reed@reedmedia.net>
Cc: TUHS main list <tuhs@minnie.tuhs.org>,
	Internet History <internet-history@postel.org>
Subject: Re: [TUHS] [COFF] Pondering the hosts file
Date: Fri, 12 Mar 2021 13:27:12 +1000	[thread overview]
Message-ID: <CAKr6gn3fnM0PKy5cWqSMiPdKHYdOgg7Tvin2SOCgXSxFGcpDSw@mail.gmail.com> (raw)
In-Reply-To: <alpine.NEB.2.22.394.2103111844390.6117@t1.m.reedmedia.net>

Funny story about /etc/hosts. and HOSTS.TXT. It was SRI NIC or NIC
DDN/MIL's job to maintain and distribute. Centrex model to keep the
numbers up, and hostnames aligned. We did shell ftp fetches and local
distribution. Yellow pages was a godsend in mant ways, the operations
duty cycle to keep this stuff up to date was a bit of a PITA.

Enter yourself in HOSTS.TXT. It was sorted. Often, Alpha. So people
like BBN were up top. People like MIT were midway. UCL-CS was down
low. Oh well. Good thing we don't do linear lookup.. Or it was sorted
by IP. But, somehow no matter what sort, we were down the back. Some
things basically seemed to to linear. And, as the host count rose, be
it sorted by IP or sorted by name, hosts in UCL-CS seemed to be
"bottom" for finding. Bottom in time sense.

So: you try to telnet to a US node, (or FTP) -and it dies. BBN
butterfly has LRUd you out. You get that fixed. That takes time too.
Hopefully less often. Shame BBN was on a fixed price fixed term
contract and the EGP (pre BGP) was not patchable. Things come back
eventually.

You try to telnet to a node again. You get connected. Long pause. you
get login: prompt. Long pause. You start typing login.. it drops link.

Getty/login had a 30 second timer. We were sitting on 29-31 seconds
lookup delay to resolve the client IP, to assert the login prompt.
Sucked to be us.

-G

  reply	other threads:[~2021-03-12  3:27 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-11 17:13 [TUHS] " Grant Taylor via TUHS
2021-03-11 17:29 ` [TUHS] [COFF] " Steffen Nurpmeso
2021-03-11 17:40 ` [TUHS] " Bakul Shah
2021-03-11 18:08   ` [TUHS] [COFF] " Warner Losh
2021-03-11 18:12     ` Clem Cole
2021-03-11 18:21       ` Jaap Akkerhuis
2021-03-11 18:21       ` Nelson H. F. Beebe
2021-03-11 20:05         ` Jan Schaumann
2021-03-11 20:30           ` Henry Bent
2021-03-11 20:42             ` Henry Bent
2021-03-11 21:20               ` Henry Bent
2021-03-11 23:46               ` Richard Salz
2021-03-12  1:15               ` Jeremy C. Reed
2021-03-12  3:27                 ` George Michaelson [this message]
2021-03-11 20:44           ` Lars Brinkhoff
2021-03-11 21:05             ` Henry Bent
2021-03-12  5:53               ` Lars Brinkhoff
2021-03-11 21:12             ` Ron Natalie
2021-03-11 22:33           ` Jeremy C. Reed
2021-03-11 18:27       ` Henry Bent
2021-03-11 18:18     ` Henry Bent
2021-03-11 18:02 ` Clem Cole
2021-03-11 20:32   ` Ron Natalie
2021-03-11 21:02     ` Bakul Shah
2021-03-11 21:08       ` Ron Natalie
2021-03-11 21:15         ` Bakul Shah
2021-03-12  1:14         ` Mary Ann Horton
2021-03-11 21:20   ` Grant Taylor via TUHS
2021-03-11 18:30 Bakul Shah
2021-03-12 10:53 Paul Ruizendaal via TUHS

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=CAKr6gn3fnM0PKy5cWqSMiPdKHYdOgg7Tvin2SOCgXSxFGcpDSw@mail.gmail.com \
    --to=ggm@algebras.org \
    --cc=internet-history@postel.org \
    --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).