Control: tag -1 moreinfo Hello Russell,
Russell Coker [2016-02-22 15:29 +1100]: > To preserve the functionality of systems where the sysadmin deliberately named > interfaces as well as systems where the sysadmin just configured things to > work with > the defaults that udev put in 70-persistent-net.rules I think that the > upgrade of > systemd should at least give the option of creating > /etc/systemd/network/*.link files > for the user. That seems rather complicated, in some cases not possible (udev rules can match on more attributes than *.link files), and rather error prone IMHO. I think it's much safer to keep the originally created 70-persistent-net.rules on upgrades, as only this guarantees that after the upgrade the network names are exactly the same as before the upgrade. The suggestion to remove it and update your firewall config etc. is done because the persistent naming schema used the same namespace as the kernel, and thus is inherently racy and broken. The mechanism (udev rule vs. *.link file) is irrelevant there, i. e. converting to link files would not gain anything. So, my questions: What do you want achieved with that conversion? Why is that severity "important"? Thanks, Martin -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)