Date: Fri, 21 Nov 2003 16:14:32 -0800 From: Tim Kientzle <kientzle@acm.org> To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> Cc: freebsd-current@freebsd.org Subject: Re: Unfortunate dynamic linking for everything Message-ID: <3FBEAA68.7060201@acm.org> In-Reply-To: <200311212348.hALNmkCf010040@khavrinen.lcs.mit.edu> References: <200311182307.hAIN7Wpm000717@dyson.jdyson.com> <20031118164905.R35009@pooker.samsco.home> <20031119141059.GA14308@madman.celabo.org> <20031119141950.GA95734@ussenterprise.ufp.org> <3FBEA209.20006@acm.org> <200311212348.hALNmkCf010040@khavrinen.lcs.mit.edu>
index | next in thread | previous in thread | raw e-mail
Garrett Wollman wrote: > <<On Fri, 21 Nov 2003 15:38:49 -0800, Tim Kientzle <kientzle@acm.org> said: >>There have been a lot of proposed solutions: >> * Rewrite NSS to not require dlopen(). >> * Rewrite dlopen() to not require dynamic linking. >> * Don't support NSS in /bin/sh. >> * Change the default script interpreter for rc and such. >> * Make dynamic linking faster. > > You forgot: > > * Allow statically-linked programs to use dynamic NSS modules > by forking a (dynamically-linked) resolver process when > needed. > > This leads to a related, but widely disparaged option: > > * Have a persistent NSS caching daemon with an RPC interface > that all programs can access for NSS lookups. You might > call such a program `nscd'. (Might as well be honest about > it.) Jacques seems to be of the opinion that the current 'nscd' is not up to the task. He would know better than I. Timhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3FBEAA68.7060201>