Hello, Besides the documentation in the busybox tarball (1.5.0 is what I'm currently using), where can I find an overview of how busybox's zcip, udhcp and mdev work? Even better would be examples. The scripts/command-line info/source code all seem a little terse.
I need to connect to a control device that can be connected directly to my box or over a DHCP controlled network. I'd like to startup and have an IP address as soon as possible. The other device appears to use ZCIP from Windows CE. Do I need to use both tools (udhcpc, zcip), or will zcip manage everything? How are other people using zcip/udhcpc in their embedded applications? Is mdev capable of notifying on when a cable is connected/disconnected from ethernet that can then be used also to control the network interface? I'm using the e100.o driver in kernel 2.6.21.1 and it prints stuff on the console when the link status changes, so at least the driver itself knows. How does zcip obtain an IP address? Is it based off the MAC or something similar, so it's pretty much the same for each device, or is it trying to be as random as possible? And my device doesn't have a writable partition to save info across powercycles (I can't guarantee how the system shuts down and I'm just using ext2fs, hence I make it readonly). Thanks in advance for any advice. Jason. _______________________________________________ busybox mailing list [email protected] http://busybox.net/cgi-bin/mailman/listinfo/busybox
