From: Dan Cross <crossd@gmail.com>
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: [TUHS] Directory services in early Unix networks?
Date: Mon, 5 Nov 2018 20:41:38 -0500 [thread overview]
Message-ID: <CAEoi9W7uCUgY3C1qTghi5QEBXDo4dwZqTc8T40LxUWCBr42zRA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 826 bytes --]
Spurred by the recent discussion of NIS, NIS+, LDAP et al, I'm curious what
the landscape was like for distributing administrative information in early
Unix networks.
Specifically I'm thinking about things like the Newcastle Connection, etc.
I imagine that PDP-11's connected to the ARPAnet running Unix would (e.g.,
RFC 681 style) would have adapted the HOSTS.TXT format somehow. What about
CHAOS? Newcastle? Datakit?
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.
NIS and playing around with Hesiod are probably the earliest such things I
ever saw, but I know there must have been prior art.
Supposedly field 5 from /etc/passwd is the GECOS username for remote job
entry (or printing)? How did that work?
- Dan C.
[-- Attachment #2: Type: text/html, Size: 1044 bytes --]
next reply other threads:[~2018-11-06 3:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 1:41 Dan Cross [this message]
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
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=CAEoi9W7uCUgY3C1qTghi5QEBXDo4dwZqTc8T40LxUWCBr42zRA@mail.gmail.com \
--to=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).