From owner-freebsd-arch@FreeBSD.ORG Fri Jun 27 23:25:13 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A497937B401; Fri, 27 Jun 2003 23:25:13 -0700 (PDT) Received: from asterix.rsu.ru (asterix.rsu.ru [195.208.245.250]) by mx1.FreeBSD.org (Postfix) with ESMTP id F142A44011; Fri, 27 Jun 2003 23:25:11 -0700 (PDT) (envelope-from os@rsu.ru) Received: from brain.cc.rsu.ru (brain.cc.rsu.ru [195.208.252.154]) (authenticated bits=0) by asterix.rsu.ru (8.12.9/8.12.9) with ESMTP id h5S6P34e063146 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 28 Jun 2003 10:25:03 +0400 (MSD) (envelope-from os@rsu.ru) Date: Sat, 28 Jun 2003 10:25:03 +0400 (MSD) From: Oleg Sharoiko X-X-Sender: os@brain.cc.rsu.ru To: Bosko Milekic In-Reply-To: <20030627121646.GA8678@technokratis.com> Message-ID: <20030628092435.B547@brain.cc.rsu.ru> References: <20030627115950.GA8424@technokratis.com> <20030627121646.GA8678@technokratis.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Status: No, hits=-100.5 required=5.0 tests=EMAIL_ATTRIBUTION,USER_IN_WHITELIST version=2.54 X-Spam-Checker-Version: SpamAssassin 2.54 (1.174.2.17-2003-05-11-exp) cc: arch@freebsd.org cc: Robert Watson cc: "Michael A. Bushkov" Subject: Re: dynamically linked root and nscd X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jun 2003 06:25:13 -0000 On Fri, 27 Jun 2003, Bosko Milekic wrote: BM> So, to the guys from RSU: why is a dynamically-linked-root important BM> for the daemon dispatcher/cache engine idea? We (guys from RSU) have to have a clear understanding of the road FreeBSD's NSS will be developed. Linux/Solaris seem to implement 'in process' model of NSS. MacOS X seem to have 'IPC' model (correct me if I'm wrong). 'In process' model has the benefit of being (semi-)compatible with existing NSS modules (at least it can be implemented this way). This means that third-party open source modules can be used in FreeBSD (ex. padl's nss_ldap). But 'in process' model doesn't support static binaries. 'IPC' model will work fine with static binaries, but it's very different from 'in process' model. With 'ICP' model FreeBSD will need it's own set of NSS modules. If I understood correctly there is some interest in combination of both of these model, correct? Do we really need both of this models? With dynamicly linked root we have a working 'in process' NSS and only 'clean caching' daemon is required. We are ready to work hard on a project that is really needed but we can not waste our time on code that will be discarded (as it happened with our IPC implementation of NSS). Our final question is: should we develop a 'caching only' daemon or a daemon which will also dispatch requests to NSS agents? I hope my English is understandable. If not - please let me know and I'll try to re-express my thoughts. -- Oleg Sharoiko. Software and Network Engineer Computer Center of Rostov State University.