On 1/2/06, Steve Simon <[EMAIL PROTECTED]> wrote: > > One of these flat files could be DNS info from LDAP in ndb(6) format > which you could simply reference in /lib/ndb/local, e.g. [...] > This is all very neat but vapourware at present - sorry, If I do get > around to such a thing I will announce it here.
It looks like it will be the first job in our 'Hack club' :D IDEA: On linux machine, every x hours, a cron job will check ldap database for new/changed/deleted entries and translate them to format supported by plan9 software (updating the fileserver's user database in the process). And I decided not to read RFC's nor libldap manual/code... python-ldap or perl-ldap will be used, and since perl-ldap is written entirely in Perl, it might be possible to set it working as native plan9 fileserver (If you call perl program native :) ) The only problem I have is: * Is there a simple way to setup linux box as ndb/auth/fileserver and so on for plan9? * How can I configure some unix DHCP server to send fileserver/auth info to plan9 (I tried with ISC DHCPd... for some reason I can't get it working) * OR set-up Plan9's dhcp server (dhcp info isn't going to change that often as to use LDAP :P ) > -Steve > -- Paweł Lasek "Once a hitokiri, always a hitokiri. This will never change" - Jine-Ei http://plasek.jogger.pl [in polish] http://plasek.wordpress.com [in polish too ;-) ]
