From owner-freebsd-current@FreeBSD.ORG Thu Apr 17 18:07:53 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 3C42A37B401 for ; Thu, 17 Apr 2003 18:07:53 -0700 (PDT) Received: from gw.nectar.cc (gw.nectar.cc [208.42.49.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id 282D943FCB for ; Thu, 17 Apr 2003 18:07:52 -0700 (PDT) (envelope-from nectar@celabo.org) Received: from madman.celabo.org (madman.celabo.org [10.0.1.111]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "madman.celabo.org", Issuer "celabo.org CA" (verified OK)) by gw.nectar.cc (Postfix) with ESMTP id A3AEE51; Thu, 17 Apr 2003 20:07:51 -0500 (CDT) Received: by madman.celabo.org (Postfix, from userid 1001) id 07F5678C66; Thu, 17 Apr 2003 20:07:50 -0500 (CDT) Date: Thu, 17 Apr 2003 20:07:50 -0500 From: "Jacques A. Vidrine" To: Gordon Tetlow Message-ID: <20030418010750.GC4001@madman.celabo.org> Mail-Followup-To: "Jacques A. Vidrine" , Gordon Tetlow , freebsd-current@FreeBSD.org References: <20030417141133.GA4155@madman.celabo.org> <20030418004345.GD9682@roark.gnf.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030418004345.GD9682@roark.gnf.org> X-Url: http://www.celabo.org/ User-Agent: Mutt/1.5.3i-ja.1 cc: freebsd-current@FreeBSD.org 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: Fri, 18 Apr 2003 01:07:53 -0000 On Thu, Apr 17, 2003 at 05:43:45PM -0700, Gordon Tetlow wrote: > The nss_ldap port has a bug in it. See the attached patch. Thanks! I must have originally downloaded the un-versioned `nss_ldap.tgz', and renamed it. > Also, by > default, we don't compile with schema-mapping. I'm working on a > patch for that (schema-mapping is needed to work in a M$ Active > Directory environment). It's a db3 vs db185 issue and I'm looking > at how to solve it. I have it band-aided for my setup (which works > now btw), but the potential for foot-shooting is really high, so I > want to make sure I test it out. OK, let me know what you discover. Since personally I will not be using nss_ldap that much, I'm happy to relinquish maintainership of the port to someone such as yourself. Regardless, feel free to commit. Cheers, -- Jacques A. Vidrine http://www.celabo.org/ NTT/Verio SME . FreeBSD UNIX . Heimdal Kerberos jvidrine@verio.net . nectar@FreeBSD.org . nectar@kth.se