On Thu, 2011-02-17 at 01:04 +0100, Samuel Thibault wrote: > Diego Nieto Cid, le Wed 16 Feb 2011 14:33:15 -0300, a écrit : > > Not really. IMHO, get_hw_addr is an orthogonal feature poorly > > abstracted in isc-dhcp. To choose the implementation you have to use > > dirty hacks like the following: > > > > https://lists.isc.org/mailman/htdig/dhcp-hackers/2009-March/001781.html > > > > The easiest way of getting it working under GNU/Hurd is by using > > sockets for sending and receiving packets and LPF's get_hw_addr.
Thanks Diego, I managed to build it by splitting out lpfs get_hw_addr to a separate function. (and of course fixing the PATH_MAX stuff) > > However, I found some trouble with hardware types identified with an > > integer bigger than 255 (ARPHRD_IEEE802_TR and ARPHRD_FDDI) and I gave > > up. Leaving them out when compiling for GNU is probably the easiest > > workaround. I had to comment these out, why it there a limit of 255? > Yes. I will integrate your patch with my changed to a create proper patch. There is a need for a dhclient-script.hurd.udeb, which is a stripped down version of dhclient-script.hurd. Samuel, can you create this file? Furthermore, the built packages are not functionally tested yet. This has to be done too, before we can say that isc-dchp-4.1.x is available.
