The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Henry Bent <henry.r.bent@gmail.com>
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Directory services in early Unix networks?
Date: Wed, 7 Nov 2018 15:15:24 -0500	[thread overview]
Message-ID: <CAEdTPBeK0A3fh3yTMZ8DY1Dm0ajrXeU28E_RReVai+ihJtLBMg@mail.gmail.com> (raw)
In-Reply-To: <CAEoi9W5bzit9y7oew9UCCHn_QHjFa+PCRe_LJPqF80kFUje+Tw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1270 bytes --]

On Wed, 7 Nov 2018 at 14:57, Dan Cross <crossd@gmail.com> wrote:

>
> 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. This would have been in the Ultrix
> 4.4 or 4.5 era on MIPS. I remember seeing some description of a
> configuration file accompanied by an editorialized comment saying something
> like, "this is an idea that's time has come: Ultrix has had it for several
> years." The dig on uglix was, well, kind of funny (I had a DECstation at
> home at the time).
>

Ultrix 4.0 (1990) had /etc/svc.conf for controlling distributed service
lookups, and you are correct that the only options were local, yp, and
bind.  Ultrix 3 (1988) had /etc/svcorder which was much more limited, only
allowing for setting the order of host lookups, but it did have support for
resolv.conf and BIND lookups (which still works!).

-Henry

[-- Attachment #2: Type: text/html, Size: 1594 bytes --]

  parent reply	other threads:[~2018-11-07 23:10 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 [this message]
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=CAEdTPBeK0A3fh3yTMZ8DY1Dm0ajrXeU28E_RReVai+ihJtLBMg@mail.gmail.com \
    --to=henry.r.bent@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).