From owner-freebsd-current@FreeBSD.ORG Fri Nov 21 16:14:34 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1902F16A4CE for ; Fri, 21 Nov 2003 16:14:34 -0800 (PST) Received: from kientzle.com (h-66-166-149-50.SNVACAID.covad.net [66.166.149.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id CAE6D43F93 for ; Fri, 21 Nov 2003 16:14:32 -0800 (PST) (envelope-from kientzle@acm.org) Received: from acm.org ([66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id hAM0EWkX035472; Fri, 21 Nov 2003 16:14:32 -0800 (PST) (envelope-from kientzle@acm.org) Message-ID: <3FBEAA68.7060201@acm.org> Date: Fri, 21 Nov 2003 16:14:32 -0800 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20031006 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Garrett Wollman 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> In-Reply-To: <200311212348.hALNmkCf010040@khavrinen.lcs.mit.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: Unfortunate dynamic linking for everything X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: kientzle@acm.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Nov 2003 00:14:34 -0000 Garrett Wollman wrote: > < 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. Tim