From owner-freebsd-current@FreeBSD.ORG Tue Nov 18 17:03:26 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 9E4D716A4CE; Tue, 18 Nov 2003 17:03:26 -0800 (PST) Received: from dyson.jdyson.com (dsl-static-206-246-160-137.iquest.net [206.246.160.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88CA643F3F; Tue, 18 Nov 2003 17:03:25 -0800 (PST) (envelope-from toor@dyson.jdyson.com) Received: from dyson.jdyson.com (localhost [127.0.0.1]) by dyson.jdyson.com (8.12.8/8.9.3) with ESMTP id hAJ13NXQ000924; Tue, 18 Nov 2003 20:03:23 -0500 (EST) (envelope-from toor@dyson.jdyson.com) Received: (from toor@localhost) by dyson.jdyson.com (8.12.8/8.12.8/Submit) id hAJ13Nlg000923; Tue, 18 Nov 2003 20:03:23 -0500 (EST) Message-Id: <200311190103.hAJ13Nlg000923@dyson.jdyson.com> In-Reply-To: <62981.24.0.61.35.1069202574.squirrel@mail.yazzy.org> from masta at "Nov 18, 2003 06:42:54 pm" To: masta@wifibsd.org Date: Tue, 18 Nov 2003 20:03:23 -0500 (EST) From: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: dyson@iquest.net cc: current@freebsd.org cc: imp@bsdimp.com Subject: Re: Unfortunate dynamic linking for everything X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: dyson@iquest.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Nov 2003 01:03:26 -0000 masta said: > > One of ther things he might have "forgot" to mention is dynamic tricks > releated to PAM, which sorta falls in the same league as NSS working out > of the box. It was worth mentioning IMHO. > I guess that I have to remember that my own goals of 'performance' and handling 'highest workload' for efficient use of hardware isn't everyone's goal. However, PAM and NSS 'tricks' really seem to be exactly that, and certainly worthy of special builds. However, that isn't necessary, yet still not building everything with a shared libc. Note that none of this requires that libc be shared (libc and its ilk are the worst offenders.) Dynamic loading can certainly be used (if you want to load a wierd, special purpose, tricky module.) John