PATCH: ifupdown.c, udhcpc, and standalone shell

[Gabriel L. Somlo]

Eric,

> >> Thanks for the fix. It works, but I'd like to re-arrange the order in
> >> which it attempts to execute various dhcp clients. Right now, udhcpc is
> >> the last one it tries, so you get a series of error messages:

My origial patch only removed the check for a hardcoded path for
udhcpc, so the shell could run it without requiring symlinks to be
installed.

Dennis thought checking for *any* hardcoded paths was ugly (and I agree
with him on that one) so he removed all hardcoded paths, and is now simply
going down the list of potential dhcp clients. This generates one
error message per client tried, unless you're lucky and happen to use
the first one that's being tried. To which I replied that the first
one should be udhcpc, since it's the "official" busybox dhcp client...

> Why should we accept to put up with error/warnings messages, it didn't
> generate those messages with the previous version. Personally I don't
> think this is an improvent.

Your beef is not with me :) :)

Maybe the answer is for ifupdown to have a config file (oh, wait,
that's /etc/network/interfaces) where we can specify exactly which
client we want to use. Maybe something like this:

auto eth0
iface eth0 inet dhcp
    dhcp-client udhcpc
    udhcpc-script /etc/network/scripts/udhcpc.script

or

auto eth0
iface eth0 inet dhcp
    dhcp-client dhclient
    <dhclient config options, if necessary>


What do you guys think ? I'm not much of a Debian-ite, so I don't know
if doing the above to /etc/network/interfaces is politically correct,
but if I don't get slapped around too hard for suggesting it, I can
write up a patch :) :)

Cheers,
Gabriel