From: arnold@skeeve.com
To: tuhs@minnie.tuhs.org, crossd@gmail.com
Subject: Re: [TUHS] Directory services in early Unix networks?
Date: Wed, 07 Nov 2018 02:05:58 -0700 [thread overview]
Message-ID: <201811070905.wA795wxP017303@freefriends.org> (raw)
In-Reply-To: <CAEoi9W7uCUgY3C1qTghi5QEBXDo4dwZqTc8T40LxUWCBr42zRA@mail.gmail.com>
Dan Cross <crossd@gmail.com> wrote:
> What was the introduction of DNS into the mix like? I can imagine that that
> changed all sorts of assumptions about failure modes and the like.
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. I think the average user didn't
see any big difference since all the apps (ftp, telnet) just went
through gethostbyname().
DNS configuration files were a trip, especially for someone used to the
very simple Unix configuration files like /etc/passwd and /etc/hosts.
Circa 1985/1986 I was responsible for bringing up DNS at the Emory U
campus. Once in place, things pretty much just worked. Or at least,
from this distant vantage point, that's what I seem to remember.
Arnold
next prev parent reply other threads:[~2018-11-07 11:38 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 [this message]
2018-11-07 15:52 ` ron minnich
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=201811070905.wA795wxP017303@freefriends.org \
--to=arnold@skeeve.com \
--cc=crossd@gmail.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).