Go to file
2007-05-24 10:26:36 +00:00
.cvsignore - New upstream release 2007-02-19 20:44:22 +00:00
autofs.schema auto-import changelog data from openldap-2.0.7-14.src.rpm 2004-09-09 09:28:35 +00:00
db-4.4.20-1.patch 2.3.21 2006-04-27 20:28:17 +00:00
db-4.4.20-2.patch 2.3.21 2006-04-27 20:28:17 +00:00
guide.html - Include --enable-multimaster to close 2006-09-22 18:32:00 +00:00
ldap.init better stale lock recognition 2007-05-24 10:13:18 +00:00
Makefile - update to 2.2.17 (stable-20040923) (#135188) 2004-11-02 15:42:16 +00:00
migration-tools.txt auto-import changelog data from openldap-1.2.11-15.src.rpm 2004-09-09 09:28:22 +00:00
MigrationTools-26-suffix.patch auto-import changelog data from openldap-2.1.22-8.src.rpm 2004-09-09 09:39:22 +00:00
MigrationTools-27-simple.patch auto-import changelog data from openldap-2.1.22-8.src.rpm 2004-09-09 09:39:22 +00:00
MigrationTools-36-mktemp.patch auto-import openldap-2.0.11-8 from openldap-2.0.11-8.src.rpm 2004-09-09 09:28:57 +00:00
MigrationTools-38-instdir.patch auto-import openldap-2.0.11-8 from openldap-2.0.11-8.src.rpm 2004-09-09 09:28:57 +00:00
MigrationTools-45-noaliases.patch - update to 2.2.17 (stable-20040923) (#135188) 2004-11-02 15:42:16 +00:00
MigrationTools-46-ddp.patch - do not import ddp services with migrate_services.pl 2007-05-23 13:09:09 +00:00
MigrationTools-46-schema.patch It helps if I use the correct version of the patch, too. 2005-11-11 05:00:27 +00:00
MigrationTools-46-unique-hosts.patch sort the hosts by adders, preventing duplicities in migrate*nis*.pl 2007-05-24 09:32:33 +00:00
nptl-abi-note.S auto-import changelog data from openldap-2.1.22-8.src.rpm 2004-09-09 09:39:22 +00:00
openldap-1.2.11-cldap.patch auto-import changelog data from openldap-1.2.11-15.src.rpm 2004-09-09 09:28:22 +00:00
openldap-2.0.11-ldaprc.patch auto-import openldap-2.0.11-8 from openldap-2.0.11-8.src.rpm 2004-09-09 09:28:57 +00:00
openldap-2.2.13-pie.patch - update to 2.2.17 (stable-20040923) (#135188) 2004-11-02 15:42:16 +00:00
openldap-2.2.13-setugid.patch auto-import changelog data from openldap-2.2.13-1.src.rpm 2004-09-09 09:42:43 +00:00
openldap-2.2.13-tls-fix-connection-test.patch * Thu Sep 29 2005 Jay Fenlason <fenlason@redhat.com> 2.2.28-2 2005-09-30 19:29:43 +00:00
openldap-2.2.15-config.patch * Thu Sep 29 2005 Jay Fenlason <fenlason@redhat.com> 2.2.28-2 2005-09-30 19:29:43 +00:00
openldap-2.2.23-resolv.patch - search for __res_query in libresolv before checking libbind 2005-03-02 01:21:23 +00:00
openldap-2.2.29-ads.patch Upgrade to 2.3.11, with much fanfare. 2005-11-11 03:39:40 +00:00
openldap-2.3.11-ads.patch Upgrade to 2.3.11, with much fanfare. 2005-11-11 03:39:40 +00:00
openldap-2.3.11-config.patch - Upgrade to 2.3.19, which upstream now considers stable 2006-01-31 21:47:36 +00:00
openldap-2.3.11-nosql.patch Upgrade to 2.3.11, with much fanfare. 2005-11-11 03:39:40 +00:00
openldap-2.3.11-toollinks.patch Upgrade to 2.3.11, with much fanfare. 2005-11-11 03:39:40 +00:00
openldap-2.3.19-gethostbyXXXX_r.patch The non-reentrant gethostbyXXXX() functions deadlock if called recursively, for 2006-02-24 01:09:36 +00:00
openldap-2.3.34-pthread.patch -changelog update 2007-04-24 09:12:34 +00:00
openldap-2.3.34-quiet-slaptest.patch Making slaptest quiet 2007-04-23 10:39:20 +00:00
openldap-ntlm.diff auto-import changelog data from openldap-2.2.13-2.src.rpm 2004-09-09 09:43:01 +00:00
openldap.spec add ldconfig to devel post/postun 2007-05-24 10:26:36 +00:00
README.evolution - spell out explicitly that the evo-openldap stuff shouldn't be used for any 2005-02-02 23:44:13 +00:00
README.nss_ldap - add bind-libbind-devel and libtool-ltdl-devel buildprereqs 2005-03-01 21:40:56 +00:00
README.upgrading - update to 2.2.23 (stable-20050125) 2005-02-01 00:19:35 +00:00
sources - New upstream release 2007-02-19 20:44:22 +00:00

Before upgrading from OpenLDAP 2.0 or 2.1 to OpenLDAP 2.2, the system
administrator should dump out the contents of the the directory server's
databases using the 'slapcat' utility included in the openldap-servers package
and save the LDIF files which it produces.

After the upgrade is complete, the data can be re-imported using the 'slapadd'
utility.  Some data which was exported from an OpenLDAP 2.0 server may not
import directly into an OpenLDAP 2.2 server.  If this happens, check for these
common problems:

  * Missing parent entries.
    Entries in the directory are no longer allowed to be children of entries
    which are not present in the directory.  For example, earlier releases
    would allow an entry with distinguished name (DN)
    "cn=foo,dc=devel,dc=example,dc=com" to be imported into a database for
    suffix "dc=example,dc=com" which contained neither an entry for
    "dc=devel,dc=example,dc=com" nor an entry for "dc=example,dc=com".

  * Deprecated objectclasses and attribute types.
    Entries of these classes should be replaced by entries of a different
    class.
     * the automountMap objectclass
       Use the nisMap objectclass instead, replacing these old attributes
       with new attributes:
       +====================================+
       | old attribute	    new attribute   |
       |------------------------------------|
       | ou		    nisMapName      |
       +====================================+
     * the automount objectclass
       Use the nisObject objectclass instead, replacing these old attributes
       with new attributes:
       +====================================+
       | old attribute	      new attribute |
       |------------------------------------|
       | cn                   cn            |
       | automountInformation nisMapEntry   |
       | (no counterpart)     nisMapName    |
       +====================================+

  * Missing objectclass definitions.
    Some objectclasses are no longer defined because they are no longer used.
    Remove the objectclass from the entry's list of objectclasses, and
    remove any values for attributes which are unique to that objectclass.
    These include:
     * the "kerberosSecurityObject" objectclass and the "krbName" attribute
     * the "dynamicObject" objectclass
     * the "LDAPsubEntry" objectclass

  * Missing attribute values.
    Some objectclass definitions mark a given attribute as both optional (MAY)
    and required (MUST).  While such attributes may have been treated as
    optional before, they are now treated as required.  Some examples:
     * the "ipProtocol" object class and its "description" attribute
     * the "rpcService" object class and its "description" attribute
     * the "oncRpc" object class and its "description" attribute
     * the "residentialPerson" object class and its "localityName" attribute

  * Structural vs. auxiliary objectclasses.
    The set of objectclasses which any entry lists should include exactly one
    STRUCTURAL class.  This requirement may not have been enforced in previous
    releases.

  * The entry does not contain its own RDN as an attribute-value pair.
    The naming attribute and value used as the entry's relative distinguished
    name (RDN) must be explicitly defined for the entry.  For example, an
    entry named "cn=contrived,dc=example,dc=com" must include "contrived" as a
    value for its "cn" attribute.