From: ron minnich <rminnich@gmail.com>
To: Aharon Robbins <arnold@skeeve.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Directory services in early Unix networks?
Date: Wed, 7 Nov 2018 07:52:47 -0800 [thread overview]
Message-ID: <CAP6exYLGJKHLt99g2n4D-Bfan3rR2cTWfpJvju3-wK6MznOqBw@mail.gmail.com> (raw)
In-Reply-To: <201811070905.wA795wxP017303@freefriends.org>
On Wed, Nov 7, 2018 at 3:38 AM <arnold@skeeve.com> wrote:
> I'm not sure what you're asking. When DNS came along, it became
> a matter of editing /etc/nsswitch.conf to include dns as one of the
> options along with files and yp/nis.
This does not align with my memory at all. I was at udel until 1988
and we started dealing with dns ca. 1986, and the shared library stuff
I dealt with in sunos came later.
Was there really an nsswitch.conf before 1988 that used shared
libraries? When did you first see nsswitch.conf? I first saw the
shared libraries with sunos 4.0 when I moved to super.org in 1988. I
always thought it started with them on Unix anyway.
In any event, dns was in some ways a big improvement in life. We were
ftp'ing the 256KiB host file from prep frequently (along with many)
and the load on prep, evidently, was getting high.
And a linear search of a 256KiB hosts file for every single
gethostbyname was getting ... noticeable. I assume this is part of why
stayopen was an option in the library.
People got upset about some things with DNS: "it's called prep, not
prep.ai.mit.edu, what is this nonsense?"
But we adjusted.
next prev parent reply other threads:[~2018-11-07 18:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 1:41 Dan Cross
2018-11-07 9:05 ` arnold
2018-11-07 15:52 ` ron minnich [this message]
2018-11-07 18:27 ` Arthur Krewat
2018-11-07 21:28 ` William Pechter
2018-11-07 17:15 ` Dan Cross
2018-11-07 20:15 ` Larry McVoy
2018-11-08 11:34 ` arnold
2018-11-08 16:39 ` Arthur Krewat
2018-11-08 23:14 ` Warner Losh
2018-11-09 0:06 ` Arthur Krewat
2018-11-07 20:15 ` Henry Bent
2018-11-07 21:11 ` Mantas Mikulėnas
2018-11-07 15:02 ` Clem Cole
2018-11-07 15:05 ` Clem Cole
2018-11-07 17:02 ` Jon Forrest
2018-11-07 19:08 ` Aaron Jackson
2018-11-07 19:48 ` Jim Davis
2018-11-07 19:51 ` Clem Cole
2018-11-09 17:05 Richard Tobin
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=CAP6exYLGJKHLt99g2n4D-Bfan3rR2cTWfpJvju3-wK6MznOqBw@mail.gmail.com \
--to=rminnich@gmail.com \
--cc=arnold@skeeve.com \
--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).