From owner-freebsd-current@FreeBSD.ORG  Mon Aug  2 12:50:00 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 0741D16A4CE
	for <freebsd-current@freebsd.org>;
	Mon,  2 Aug 2004 12:50:00 +0000 (GMT)
Received: from fillmore.dyndns.org (port-212-202-50-15.dynamic.qsc.de
	[212.202.50.15])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8284843D48
	for <freebsd-current@freebsd.org>;
	Mon,  2 Aug 2004 12:49:59 +0000 (GMT)
	(envelope-from eikemeier@fillmore-labs.com)
Received: from dhcp-11.local ([172.16.0.11])
	by fillmore.dyndns.org with esmtp (TLSv1:DES-CBC3-SHA:168)
	(Exim 4.41 (FreeBSD))
	id 1BrcFg-000G5f-EW; Mon, 02 Aug 2004 14:49:18 +0200
Date: Mon, 2 Aug 2004 14:50:36 +0200
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v482)
To: Kirk Strauser <kirk@strauser.com>
From: Oliver Eikemeier <eikemeier@fillmore-labs.com>
In-Reply-To: <200407291450.49400.kirk@strauser.com>
Message-Id: <8C9CBFBF-E482-11D8-9C56-00039312D914@fillmore-labs.com>
Content-Transfer-Encoding: 7bit
User-Agent: KMail/1.5.9
cc: freebsd-current@freebsd.org
Subject: Re: Upgrading to net/openldap22-sasl-server giving fits
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2004 12:50:00 -0000

Kirk Strauser wrote:

> On Thursday 29 July 2004 13:21, Doug White wrote:
>
>> It would not suprise me if you need to dump + reload your database to
>> update to a new bdb schema in openldap2.2.
>
> <whine>But I don't WANT to reload my database!</whine>

Sorry, internal structures have changed. You *have to* use 
slapcat/slapadd. That is why OpenLDAP 2.1 is still around, upgrading the 
client part is pretty painless...

> Is there a generalized way to upgrade Berkeley databases?  I tried to
> RTFDocs, but they seem to be aimed at BDB programmers ("Simply call the
> DB->transmogrify method...") instead of command-line users.

You can update the underlying Berkeley database, but this doesn't mean 
OpenLDAP can still work with it. You can even use slapd-bdb(5) instead 
of slapd-ldbm(5) when you use OpenLDAP 2.2 + BerkelyDB 4.2, but they are 
not binary compatible.

I'll add an entry to ports/UPGRADING, since this seems to be a FAQ.

-Oliver