On Thu, May 26, 2011 at 09:12, Greg KH <greg@xxxxxxxxx> wrote: > On Wed, May 25, 2011 at 08:42:47PM +0200, Kay Sievers wrote: >> In the future, udev will not do anything for any unconfigured >> interface, not rename it, not write out a rule for the next reboot. >> The majority of systems does not need these stable names, and the >> current *magic* creates far too many problems. The deal does not seem >> right and the fix it not to do it. > > Yeah! > > That sounds like the correct solution to me as well, thanks for planning > on doing this. People who don't rely on it can already do: ./configure --disable-rule_generator Which will not install any of the files that mangle udev rules ad hotplug time. The big distros just need to coordinate with the people who do the system-management tools, that these tools get updated to allow editing the 70-persistent-net.rules file without udev ever touching it. They should also make sure, that network devices are never renamed in the ethX namespace. The current biosdevname solution with the lomX and slotX names which Dell uses, seems to work well, and shows that we should not fear moving to the proper solution. It is either leaving the names completely up to the kernel and run something like NetworkManager which does not care at all what names the devices have, or the system has manually configured interfaces and they get meaningful names like 'lom' (for on motherboard) or the PCI slot number, or something like 'internal', 'external', 'dmz'. The lom, slot logic, which is pretty simple, we might even want to move inside the kernel after a while, when things have proven to work reliably that way. Only one thing seems sure for now, that udev must stop renaming things in the kernel namespace. The details for the rest we will need to find out. :) Kay -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
