From owner-freebsd-hackers Wed Aug 4 4:52:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 2E09714D21 for ; Wed, 4 Aug 1999 04:52:26 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id HAA06202; Wed, 4 Aug 1999 07:53:57 -0400 (EDT) Date: Wed, 4 Aug 1999 07:53:55 -0400 (EDT) From: Alfred Perlstein To: Peter Jeremy Cc: hackers@FreeBSD.ORG Subject: Re: NSS Project In-Reply-To: <99Aug4.074656est.40329@border.alcanet.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 4 Aug 1999, Peter Jeremy wrote: > Oscar Bonilla wrote: > >If anyone has any comments, suggestions, etc. I would appreciate it. > > Overall, I like the idea of NSS. But, having worked on Solaris 2.x > for some time, we need to avoid some of the blunders Sun made: The > biggest problem with Sun's NSS implementation is that it's no longer > possible to statically link an application that uses any of the > get...byname() functions that have NSS backends. > > We need to be able to build an application that has no dynamically > loaded code for recovery purposes (/stand and /sbin) as well as for > security. well you could just link in the shared nss object statically into it...? -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message