From owner-freebsd-current@FreeBSD.ORG Thu Apr 1 17:35:52 2004 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 E4B6816A4CE; Thu, 1 Apr 2004 17:35:52 -0800 (PST) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id D162143D2F; Thu, 1 Apr 2004 17:35:52 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) i321Zj82070339; Thu, 1 Apr 2004 17:35:45 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.9p2/8.12.9/Submit) id i321ZjK6070338; Thu, 1 Apr 2004 17:35:45 -0800 (PST) (envelope-from dillon) Date: Thu, 1 Apr 2004 17:35:45 -0800 (PST) From: Matthew Dillon Message-Id: <200404020135.i321ZjK6070338@apollo.backplane.com> To: "Jacques A. Vidrine" References: <1080773331.1956.36.camel@server.mcneil.com> <20040401124519.GA12985@lum.celabo.org> cc: freebsd-current@freebsd.org cc: Sean McNeil cc: Oliver Eikemeier Subject: Re: nss_ldap broken 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: Fri, 02 Apr 2004 01:35:53 -0000 :I don't know if you overestimate it or not for practical purposes, i.e. :I'm not sure how many applications are actually affected. However, it :makes me quite nervous. There are many uses of `plug-in' APIs that :involve dlopen/dlclose of dynamic objects. So, I also think we should :codify how these cases should be handled. Ha. I think people know where I stand on NSS. The CAPS (ipc) code in DFly is coming along nicely, and I just finished a portable structural encoding for requests and responses (it's a userlevel encoding. The actual syscall interface passes opaque data and doesn't care what the message's format is). The next step is to actually begin implementing directory services with it in DFly. The primary syscall interface for CAPS is now using XIO in DFly (which is basically an encapsulation of Alan Cox's use of SF_BUF's, similar to how his PIPE code works), so it would be easily ported to FreeBSD. The syscall API isn't quite up to snuff yet, I need to change its cid's over to use real file descriptros, but it's very close to what I wanted. -Matt