On Tue, Sep 22, 2009 at 02:28:32PM +0100, Phil Blundell wrote: > On Mon, 2009-09-21 at 18:39 -0400, Denys Dmytriyenko wrote: > > On Mon, Sep 21, 2009 at 08:45:06PM +0100, Phil Blundell wrote: > > > It seems like there must be a better way of solving this problem. How > > > about just teaching "ifup -a" to spot interfaces that are already up and > > > leave them alone? > > > > Won't work for the case of kernel-acquired DHCP address, i.e. kernel level > > autoconfig, aka IP_PNP, aka ip=dhcp command line. > > True, but your original patch won't help with this situation either > (since "ip=dhcp" won't match the regex). I think this is a different
Not true. The default is to start udhcpc always. I just cover one case to prevent it from starting when ip=x.x.x.x > problem and probably requires a different solution: the ideal thing > would be for the kernel to set a flag on the interface to say that it > needs to be taken over by a DHCP client, or alternatively to invoke the > DHCP client itself via the hotplug mechanism. Failing that you could > arrange for the startup scripts to poke around at /proc/cmdline and try > to second-guess what the kernel has done, although that would be rather > less satisfactory. _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
