I don't mind vi ...now that I know it.

...and, at one time, I knew edlin, too -- because, when you're on telephone technical support, you can walk somebody through fixing their config.sys & autoexec.bat files with edlin, and feel fairly confident that after you hang up, they won't go playing around with edlin because they think it's cool, neat, or pretty. (vs. dragging pictures around in windows and totally screwing things up!)

udhcpc seems to be invoked elsewhere. For the moment, my hack was:
# mv /sbin/udhcpc /sbin/udhcpc.real
# vi /sbin/udhcpc

and put in the following line:
/sbin/udhcpc.real -H whateverhostnameuwant $@

# chmod +x /sbin/udhcpc

Hope this helps till they fix it.

From what I know, it's icd that invokes it. Check the /etc/network/ifup scripts and the icd init script.

If you have a Mac or use Avahi/Bonjour this might be easier.

http://www.internettablettalk.com/fo...ighlight=avahi

Search for udhcpc in this file:

http://busybox.net/cgi-bin/viewcvs.c...83&view=markup

I think busybox calls the udhcp binary from within ifupdown. It has some support for altering the invocation via environmental variables, but I just couldn't work out where to set them. I'd still love to know how to add a dhcp-client-identifier to the dhcp request