On Mon, 2008-01-28 at 16:22 +0100, Guido Diepen wrote: > Mark Ellis wrote: > > On Mon, 2008-01-28 at 10:57 +0000, John Carr wrote: > >> > 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... > >> > > > > Interesting, yes I'd say that rules out dhcdbd. Be nice to find out what > > the problem was, and maybe how they now do it. > > > >> 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..) > >> > > > > While I think this could still be a pain, I can't see any problem with > > going with it to start with and see how it goes. > > > > This is a hal solution of course. Odccm needs a different solution until > > everyone is happy with hal. As a short term solution in odccm I'd say > > calling dhclient is the easy answer, except for parsing its output using > > C, which would probably result in a dependency on a regex lib. > > I don't understand exactly how exactly you are getting the results about > the IP address and the IP address of the DHCP server (i.e. the device) > with hal-dccm. (or what the exact idea behind it is) I don't have that > much experience with HAL related stuff though ;) Could you please explain > in a bit more detail what the idea is for the hal-dccm? > > For the odccm case, I will have another look at the whole thing this > afternoon after work. >
synce-hal isn't using dhcp at the moment, it's just doing an ifconfig with the default addresses. So the plan would be to instead call dhclient and parse the output to get the assigned ip address. Mark ------------------------------------------------------------------------- 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
