From owner-freebsd-hackers Thu Jul 22 6:50:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rebel.net.au (rebel.rebel.net.au [203.20.69.66]) by hub.freebsd.org (Postfix) with ESMTP id 6CE3A15227 for ; Thu, 22 Jul 1999 06:50:18 -0700 (PDT) (envelope-from kkenn@rebel.net.au) Received: from 203.20.69.80 (dialup-10.rebel.net.au [203.20.69.80]) by rebel.net.au (8.8.5/8.8.4) with ESMTP id XAA25188 for ; Thu, 22 Jul 1999 23:19:16 +0930 Received: (qmail 27811 invoked from network); 22 Jul 1999 13:49:36 -0000 Received: from localhost (kkenn@127.0.0.1) by localhost with SMTP; 22 Jul 1999 13:49:36 -0000 Date: Thu, 22 Jul 1999 23:19:35 +0930 (CST) From: Kris Kennaway Reply-To: kkenn@rebel.net.au To: freebsd-hackers@FreeBSD.ORG Subject: Re: PAM & LDAP in FreeBSD, and userfs too. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 22 Jul 1999, Dominic Mitchell wrote: > > PAM is also "using masses of weird shared objects" but nevertheless it's > > quite usable > > By statically linked binaries? This is also an issue for a modularized libcrypt(). Peter Wemm suggested having the library fork and exec a static helper binary module and communicate via a pipe. So essentially you'd have two files for each module, one which is a shared library and loaded via dlopen() and one which is the same code with a small amount of wrapper (main() etc) to make it into a standalone binary. Solaris seem to be deprecating static libraries; you cannot have a fully static libc and they have to resort to keeping (a copy of) libdl (and presumably the run-time linker) under /etc so it's available on the root partition. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message