Wanted to try this because I really, really would like to deploy 389 directory with a more sensible file system layout than the standard LSB architecture. What I wouldn’t do for a basic .zip installation package…
… like Sun did for DSEE before it was acquired.
Doing the compile from source turned out to be easier than I thought it would be. I used the latest stable source for 389-ds-base, 220.127.116.11 as of this writing.
I already had 389 directory for RHEL 6 installed, up and running from the developer’s yum repository.
The only additional pieces I had to install were the following rpms.
Some other packages you might need that were already on my machine:
Then I did a
and a “make” and “make install”.
Found the setup-ds.pl script under /opt/dirsrv/sbin. Setting up a new instance called “localhost” created it under /opt/dirsrv/var/lib/dirsrv/slapd-localhost.
Have not tested thoroughly yet, so I’m not sure what limitations there might be (can I get LDAPS working?).
This was just the core directory server. Will leave mucking around with the console for later.
A higher priority would be flattening the file system paths a bit to get “/opt/dirsrv/etc” rather than “/opt/dirsrv/etc/dirsrv”, or “/opt/dirsrv/var/lib/dirsrv/slapd-localhost” to “/opt/dirsrv/var/slapd-localhost” or even “/opt/dirsrv/slapd-localhost” like I can do with DSEE.
Ultimately I’d like to come up with a zip distribution of my own that I can deploy to any server I like. One of the challenges in doing something like that is understanding, in detail, all the dependencies that need to be in place.