> Ideas yes, solutions no. > > Odccm does everything internally, so to use dhcp you'd need to implement > it in C or call dhclient externally. > > synce-hal currently uses ifconfig in the callout script, so this could > easily be replaced with dhclient. The problem is then how to pass the > recovered ip address to dccm so it knows which interface to listen on. I > seem to remember that there is a dbus controllable dhclient, I'll > investigate at some point. > > Mark
One sinister option is to take advantage of the fact that the callout script can be written in python.. so we could use popen and friends to call dhclient and scrape its returned output. Possibly after trying the dbus controlled DHCP client first... When the callout script starts hal-dccm it can use bog standard command line args to tell hal-dccm what to do, or use dbus and hal to set the IPs on the HAL node.. I will get round to testing hal-dccm, its next on my list after some Conduit stuff and some work on JhDebuild (jhdebuild will allow rapid deployment of debian packages of SVN versions... i'm talking a case of typing "jhuild debuild sync-engine" to package sync-engine and all its deps (if they have changed) and push them into a local repository. But thats another story/blog post/mailing list post. John ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ SynCE-Devel mailing list SynCE-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synce-devel
