From owner-freebsd-hackers@FreeBSD.ORG  Mon Apr 14 06:50:05 2003
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id ED50D37B401
	for <freebsd-hackers@freebsd.org>;
	Mon, 14 Apr 2003 06:50:05 -0700 (PDT)
Received: from asterix.rsu.ru (asterix.rsu.ru [195.208.245.250])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 13B6A43F85
	for <freebsd-hackers@freebsd.org>;
	Mon, 14 Apr 2003 06:50:04 -0700 (PDT)	(envelope-from bushman@rsu.ru)
Received: from rsu.ru (mac.cc.rsu.ru [195.208.252.173])
	by asterix.rsu.ru (8.12.6p2/8.12.6) with ESMTP id h3EDnug5072531;
	Mon, 14 Apr 2003 17:49:56 +0400 (MSD)
	(envelope-from bushman@rsu.ru)
Date: Mon, 14 Apr 2003 17:49:50 +0400
Mime-Version: 1.0 (Apple Message framework v551)
To: freebsd-hackers@freebsd.org
From: "Michael A. Bushkov" <bushman@rsu.ru>
Message-Id: <F62F7D8D-6E7F-11D7-BFAE-000393BC13C6@rsu.ru>
X-Mailer: Apple Mail (2.551)
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed
Content-Transfer-Encoding: 7bit
X-Content-Filtered-By: Mailman/MimeDel 2.1.1
cc: bork@rsu.ru
cc: and@rsu.ru
cc: os@rsu.ru
Subject: Re: Re: nsswitch implementation
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2003 13:50:06 -0000

>
>> The daemon (level 2) should be able do dynamically open modules - we
>> can't call dlopen() directly from libc.
>
> Sure we can.  You just can't if you are a statically-linked
> executable.  [The implementation that will be committed shortly allows
> for building an NSS module with world so that statically-linked
> binaries are also supported.]

Do you want to statically compile nss-modules in libc? If you do that, 
you'll have to statically link a lot of stuff into libc (for example, 
if we have nss_ldap module - we must compile whole ldap implementation 
into libc). And if we do it that way, libc will grow and grow... 
Besides, if you want to change a module code, you'll have to recompile 
whole libc.
We are very interested to know your way of solving these problems...

Michael A. Bushkov
Computer Center of Rostov State University