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 -- JeOS does not have name resolution in place when boot.sh is executed. https://bugs.launchpad.net/bugs/391980 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
