From: "Mantas Mikulėnas" <grawity@gmail.com>
To: crossd@gmail.com
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Directory services in early Unix networks?
Date: Wed, 7 Nov 2018 23:11:28 +0200 [thread overview]
Message-ID: <CAPWNY8WOCzNuOcuBZOr7fY3gGRNqzLTGQ-65ULTPRXug=aRCoA@mail.gmail.com> (raw)
In-Reply-To: <CAEoi9W5bzit9y7oew9UCCHn_QHjFa+PCRe_LJPqF80kFUje+Tw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1214 bytes --]
On Wed, Nov 7, 2018 at 9:57 PM Dan Cross <crossd@gmail.com> wrote:
> On Wed, Nov 7, 2018 at 4:05 AM <arnold@skeeve.com> wrote:
>
>> 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().
>>
>
> This doesn't mesh with my memory. I recall building BIND from source and
> having to rebuild network programs (e.g. on 4.3 on the RT or VAXen) to pick
> up the new version of libresolv.a, and hacking the resolver library into
> libc.so on Suns. I remember using resolv.conf fairly early on, but my
> memory is that nsswitch.conf came later (Solaris 2.x era?). Ultrix did have
> a configuration file for where to do host lookups, but I think the set of
> sources was fixed: files, NIS or DNS.
>
I always assumed that nsswitch came much later than DNS, based just on the
fact that Linux glibc on older systems still ships an /etc/host.conf
"resolver configuration file" that has such parameters as "order
hosts,bind,nis" (although they're inoperative).
--
Mantas Mikulėnas
[-- Attachment #2: Type: text/html, Size: 1914 bytes --]
next prev parent reply other threads:[~2018-11-07 23:11 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
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 [this message]
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='CAPWNY8WOCzNuOcuBZOr7fY3gGRNqzLTGQ-65ULTPRXug=aRCoA@mail.gmail.com' \
--to=grawity@gmail.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).