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 majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
