Hint: If you want to reproduce this bug, it might help to do as me; run the DHCP server on a really slow machine, overload it with respect to cpu-load and memory-usage. Then boot your JeOS maing a DHCP request to this slow server.
And further when considering a real solution to this bug (some DHCP waiting mechanism), don't forget to have a time-out mechanism, there might not be a DHCP server in the network.
Hint: If you want to reproduce this bug, it might help to do as me; run the DHCP server on a really slow machine, overload it with respect to cpu-load and memory-usage. Then boot your JeOS maing a DHCP request to this slow server.
And further when considering a real solution to this bug (some DHCP waiting mechanism), don't forget to have a time-out mechanism, there might not be a DHCP server in the network.
Jarl