https://bugzilla.novell.com/show_bug.cgi?id=809843 https://bugzilla.novell.com/show_bug.cgi?id=809843#c6 Marius Tomaschewski <mt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner@suse.com See Also| |https://bugzilla.novell.com | |/show_bug.cgi?id=810076 --- Comment #6 from Marius Tomaschewski <mt@suse.com> 2013-03-18 18:13:44 UTC --- (In reply to comment #5)
Like Marius said, in the newer udev the persistent names are dropped and before they were unreliable which I can't do anyting about.
This is not correct. biosdevname is not reliable, not even on Dell boxes, where it aims to work: see bnc#810076 (because of BIOS versions, bugs in biosdecode, BIOS update?). Renaming inside of the same namespace as the kernel e.g. "eth" like try to rename "eth1" to "eth0" and "eth0" to "eth1" is not reliable. This is just a question of using different name scheme (e.g. "nicX") than the kernel to be reliable.
Now the fact that eth0 is renamed to eth1 or something like that, is not udev, udev doesn't handle the network devices anymore, so not much I can do here.
This is a mandatory functionality which has to available - we need a replacement. Just dropping it without a replacement is a no-go. Do you provide any replacement? We've dropped the persistent name encoding from sysconfig (ifcfg-bus-... ifcfg-id... on 10.x/SLES-10), because udev aimed to provide it. Removing persistent interface names breaks almost every network related configuration file, including sysconfig, SuSEfirewall2, dhcp, ... It is simply not possible to rewrite any configuration file at boot. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.