El 24/03/13 14:53, Marc Chamberlin escribió:
I suspect there are a lot of services,
applications and tools which are very dependent on the device interface name and any sort of a change is very likely to break many of them.
Yes, and that's why the rules must apply only to new installations. Case
in point is this removal of the persistence mechanism for giving/maintaining device names to NICs. In openSuSE 12.3, it's sudden disappearance broke YaST and my ability to use it to set up a gateway system.
Well, it was removed from udev upstream, because it did not work.
Such changes should be more orderly, done gradually over a couple of releases, defaulting at first to the continued usage of the old (even if buggy) method(s).
Such change will run in 13.1 , not "between a couple of releases".. you are asking for an approach that will pose a burden on mainteniance and will in practice make things worst, not better.
Even better is to pass along with this warning, information on how to move to the new mechanism(s) so that it can be tested and time given to the developers of all those other applications, services etc..
Applications do not have hardcoded interface names, configuration does and existing configuration means existing installation. to adapt to the new
change(s). And then finally switching to the new method as the default. IMHO this transition is being done too rapidly, especially considering the significance of its impact, and not enough time being given to work out the kinks that are likely to occur...
It does not work the way you expect. it is either the new method or the old one in one step. old method: ln -s /dev/null /etc/udev/rules.d/80-net-name-slot.rules New method : NO action required. If you think it is going too fast, you need an "enterprise" distribution or a walking-dead BSD. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org