From owner-freebsd-current@FreeBSD.ORG Thu Apr 17 12:44:04 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 9EE1D37B408 for ; Thu, 17 Apr 2003 12:44:04 -0700 (PDT) Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8341C43FDD for ; Thu, 17 Apr 2003 12:44:03 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from strings.polstra.com (strings.polstra.com [206.213.73.20]) by wall.polstra.com (8.12.3p2/8.12.3) with ESMTP id h3HJi1dt029261 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 17 Apr 2003 12:44:02 -0700 (PDT) (envelope-from jdp@strings.polstra.com) Received: (from jdp@localhost) by strings.polstra.com (8.12.6/8.12.6/Submit) id h3HJi1jK095151; Thu, 17 Apr 2003 12:44:01 -0700 (PDT) (envelope-from jdp) Date: Thu, 17 Apr 2003 12:44:01 -0700 (PDT) Message-Id: <200304171944.h3HJi1jK095151@strings.polstra.com> To: current@freebsd.org From: John Polstra In-Reply-To: <20030418014500.B94094@iclub.nsu.ru> References: <20030417141133.GA4155@madman.celabo.org> <20030417144449.GA4530@madman.celabo.org> <200304171535.h3HFZEFs094589@strings.polstra.com> <20030418014500.B94094@iclub.nsu.ru> Organization: Polstra & Co., Seattle, WA Subject: Re: HEADS UP: new NSS X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Apr 2003 19:44:05 -0000 In article <20030418014500.B94094@iclub.nsu.ru>, Max Khon wrote: > On Thu, Apr 17, 2003 at 08:35:14AM -0700, John Polstra wrote: > > > You might want to look at how libpam handles this situation. In the > > static case, all of the known modules are linked into it statically. > > Then they are located and registered at runtime by means of a linker > > set. > > statically linking pam_ldap to /bin/ls will be a nightmare :) True, but why would /bin/ls need anything from PAM at all? It doesn't currently use PAM. > we need either allow dlopen(3) to be used in statically linked programs > or move to dynamically linked /. Moving to a fully dynamically linked system sounds easier to me. But in the past there has been strong opposition to the idea every time it has been proposed. John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa