> OK, I have to agree that dhclient is quite within any distro core yes. But > one other thing mentioned was a dbus controlled dhclient. The problem with > that is that it is already less core. Furthermore, I can remember that it > was you that was telling sometime that you don't like a lot of daemons > running all of the time (which my guess is this program would be ;) ) > > I could look into calling the dhclient, or even adding the dbus > functionality-enabled dhclient to it. I will take a look at this either > this afternoon, or tomorrow. > > I have to say that I like using a d-bus controlled dhclient more than > calling another executable from within the odccm binary.
I'm against dhcdbd, if NetworkManager has stopped using it [1] [2] then it must suck... The HAL callout parsing dhclient output wouldnt involve a daemon, other than hal-dccm which would be started by it. Directly parsing the output of dhclient from a python HAL callout seems easy, and while its not the nicest thing I think it might be useful for non SynCE devices too. (I'm sure i've seen at least one other non-SynCE device that needs DHCPing before it will work..) John [1] http://blogs.gnome.org/dcbw/2007/10/15/networkmanager-07-is-the-new-chuck-norris/ [2] http://svn.gnome.org/viewvc/NetworkManager?view=revision&revision=2666 ------------------------------------------------------------------------- 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
