Aside from the busybox issue.. Isn't the udev net persistence feature going to cause a lot more problems than it solves?
As I understand it, it is recording the MAC address of the NIC, and associating that with an ethernet interface. So, that if the order the NICs are initialized in changes, the association of NIC to eth device stays the same. This works fine in a physical server, where the expectation is that hardware changes are unlikely. But, in a VM environment, the MAC address can change when changes are made to the Virtual Machine configuration, or the location of the VM, etc. As it is now, any time he MAC changes, the user will lose connectivity, because it is now treated as eth1, rather than eth0, which has no configuration. This feature of udev should be turned off in the JeOS build, as it causes problems in common VM usage. Or, some additional logic could help it to do its job better, such as: - If only one NIC exists in the box, don't worry about order/mapping, treat it as eth0 (solves a large percentage of problems) - If the old MAC address doesn't exist anymore, don't hold the reservation/mapping. -- [Gutsy] broken 70-persistent-net.rules https://bugs.launchpad.net/bugs/145382 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
