The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: arnold@skeeve.com
To: lm@mcvoy.com, crossd@gmail.com
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Directory services in early Unix networks?
Date: Thu, 08 Nov 2018 04:34:27 -0700	[thread overview]
Message-ID: <201811081134.wA8BYRl9001763@freefriends.org> (raw)
In-Reply-To: <20181107201520.GA14737@mcvoy.com>

Larry McVoy <lm@mcvoy.com> wrote:

> On Wed, Nov 07, 2018 at 12:15:32PM -0500, Dan Cross 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?). 
>
> Yeah, this is right, I remember doing this as well and I worked at Sun
> at that point.  It was a pain.  

OK, so now that everyone mentions it, I was wrong. I think I only
had to do this same kind of thing once though.

We ran the Mt. Xinu 4.3 BSD + NFS and it had YP also, so at some
point they were doing it and I sorta think we had /etc/nsswitch.conf
on the vaxen, but I could be wrong. We definitely had it on the SunOS 4.0
Sun servers that we bought later on.

Our connection was via CSNet - slow X.25 line to Georgia Tech and from
there to the rest of the world. We most certainly did NOT do daily FTPs
of the HOSTS.TXT file or anything like that.  At the time we had very
few TCP/IP-savy users; you could probably count them on two hands and
have a few fingers left over. :-)

Those were the days. :-)

Arnold

  reply	other threads:[~2018-11-08 14:51 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 [this message]
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=201811081134.wA8BYRl9001763@freefriends.org \
    --to=arnold@skeeve.com \
    --cc=crossd@gmail.com \
    --cc=lm@mcvoy.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).