Jarod Wilson and myself have taken ownership to make sure that FDS is in the
repository in time for Fedora 7.
I believe that most pieces are already in place that there is a few small
remaining packages before the admin tools get it.
Can someone give me a list of what is left to be done?
,-._|\ Dennis Gilmore, RHCE
/Aussie\ Proud Australian
\_.--._/ | Aurora | Fedora |
I've been working to allow Fedora DS to backend Samba4, much as OpenLDAP
can. This, I hope, will bring us the benefits of a replicated backend
between Samba4 servers.
To set this up, I've placed some notes in setup/fedora-ds-init.ldif and
extended the provision script. The provision now succeeds, and Win2k3
can join and log into the Samba4/FDS domain.
The next step is to test the Fedora DS backend in our 'make test'
script. For that, I'll need some help. I need to automatically
configure and start fedora DS, from within the test scripts. I
understand some testing scripts to do this exist...
To integrate such scripts with Samba4, I need a few things:
Ideally it would bind to an ldapi:// socket (this is redhat bug 219573:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=219573 ), but for
now a high port would do.
Likewise, it would be ideal if fedora DS could terminate with the
process group, so we don't risk leaving ldap servers around after a
Finally, I need USN support in Fedora DS, or something very much like
the contextCSN attribute in OpenLDAP. (With a way to obtain a highest
value, preferably also a way to get a 'new' value too).
Later, we need to figure out how ACLs should behave for all our
Andrew Bartlett http://samba.org/~abartlet/
Authentication Developer, Samba Team http://samba.org
Samba Developer, Red Hat Inc. http://redhat.com