[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: BDB Corruption...



If you wish, I have relocatable  openldap 2.2.17 source RPM package at
http://www.int-evry.fr/mci/user/procacci/SRPMS/

And Fedora Core 2 binary RPM packages at
http://www.int-evry.fr/mci/user/procacci/SRPMS/FC2

for instructions, see readme-jehan.txt  enclosed int the rpm.

Dominic Ijichi wrote:

Quoting Tony Earnshaw <tonye@billy.demon.nl>:



ons, 20.10.2004 kl. 04.42 skrev Quanah Gibson-Mount:



WHEN WILL REDHAT WAKE UP AND MAKE MY JOB EASIER?


I simply suggest not using RedHat. :)


I have many reasons for sticking with RH; it's just the whole attitude
to directory services (and RDBs for that matter) that gets my goat.

AFAIK the only OS that officially offers Openldap 2.2 as a standard
update, is FreeBSD; for all the others one has to jump through hoops. I
can understand that the jump from 2.0 to 2.2 could break client
applications, but surely the user should be given the choice and offered
the assistance in adopting modern technology, especially when the
software authors urge doing so? And I don't regard offering Netscape
Directory Server as being the answer ...



after having exclusively used heavily hacked/customised redhat for years and years, i switched this year to suse. Suse Linux Enterprise Server 9 has OpenLdap2.2 as standard, more than that it uses it as the standard backend for users, groups AND a lot of the system configuration. I have a 2-server cluster with near-realtime journalled replication, a decent FS (Reiser!), failover host/service/network clustering, and DHCP, DDNS, Samba PDC, SMTP/IMAP, HTTP all using a openldap backend for auth/config. This is without a single line of custom/compiled code or config, all configured through a GUI (well, a couple of lines of cluster stuff by hand).

redhat for me is consigned to the bin forever, Novell/Suse rocks.

------------------------------------------
This message was penned by the hand of Dom