From owner-freebsd-hackers Mon Jul 19 12:55:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (Postfix) with ESMTP id D796415239 for ; Mon, 19 Jul 1999 12:55:55 -0700 (PDT) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from lestat (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with ESMTP id MAA13308; Mon, 19 Jul 1999 12:55:19 -0700 (PDT) Message-Id: <199907191955.MAA13308@lestat.nas.nasa.gov> To: Dominic Mitchell Cc: "David E. Cross" , Oscar Bonilla , freebsd-hackers@FreeBSD.ORG Subject: Re: PAM & LDAP in FreeBSD, and userfs too. Reply-To: Jason Thorpe From: Jason Thorpe Date: Mon, 19 Jul 1999 12:55:19 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Jul 1999 20:44:18 +0100 Dominic Mitchell wrote: > Lovely. Sounds like a much better way to do the Solaris/Linux (and > NetBSD?) /etc/nsswitch.conf stuff. On Solaris at least, this is > implemented using masses of weird shared objects... The plan for NetBSD is that things will also be handled with dynamic modules, but those dynamic modules will be glued into a `nscd'[*] (if you use Solaris, you're familiar with the name :-). [*] We are planning on not having all of the problems that the Solaris nscd has, and that people often complain about. This will allow libc to simply make a call to nscd (or fallback onto traditional `files' lookup), and nscd will handle all but the `files' case. This allows system-wide caching, and puts all of the complexity in one place. Involving one or more user mode file systems seems like ... the wrong approach for a name service switch. -- Jason R. Thorpe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message