From owner-freebsd-current@FreeBSD.ORG Thu Apr 17 08:35:16 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 79A5037B401; Thu, 17 Apr 2003 08:35:16 -0700 (PDT) Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4BD1B43FCB; Thu, 17 Apr 2003 08:35:15 -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 h3HFZEdt028209 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 17 Apr 2003 08:35:14 -0700 (PDT) (envelope-from jdp@strings.polstra.com) Received: (from jdp@localhost) by strings.polstra.com (8.12.6/8.12.6/Submit) id h3HFZEFs094589; Thu, 17 Apr 2003 08:35:14 -0700 (PDT) (envelope-from jdp) Date: Thu, 17 Apr 2003 08:35:14 -0700 (PDT) Message-Id: <200304171535.h3HFZEFs094589@strings.polstra.com> To: current@freebsd.org From: John Polstra In-Reply-To: <20030417144449.GA4530@madman.celabo.org> References: <20030417141133.GA4155@madman.celabo.org> <1050590195.76150.8.camel@owen1492.uf.corelab.com> <20030417144449.GA4530@madman.celabo.org> 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 15:35:16 -0000 In article <20030417144449.GA4530@madman.celabo.org>, Jacques A. Vidrine wrote: > On Thu, Apr 17, 2003 at 09:36:35AM -0500, Craig Boston wrote: > > Out of curiosity, how do the staticly-linked binaries in /bin and /sbin > > handle this since they can't dlopen anything? Do users handled by > > dynamically-loaded NSS modules just show up as UIDs with no name in > > /bin/ls? > > Yep. > The following is a work-around: > > cd /usr/src/bin/ls > make clean > make NOSHARED=NO depend > make NOSHARED=NO > make NOSHARED=NO install 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. John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa