http://bugzilla.novell.com/show_bug.cgi?id=522839
User mt@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=522839#c3
Marius Tomaschewski
As a workaround, you should use BusID position instead of MAC address to identify device (example: KERNELS=="0000:00:03.0" instead of ATTR{address}=="08:00:27:d1:1f:41")
Marius, what about some config option to switch between this 2 possibilities?
You mean a switch to enable/disable the rule generator? Maybe... I'd say, in the normal usage, the persistent names make also sense in virtual box machines and MAC based by default IMO is OK too and simply works. The MAC is in the virtual box .xml config, not in the .vdi file. Do you ship only the .vdi file with you appliance? The "problem" occurs also when you push the generate button before every boot and may also happen with BusID, e.g. when the user changes the NIC driver or adds another NIC using another driver (PCNET II -> PCNET III) or removes existing NIC and adds again. But this is OK to "fail" then - the user changed something and we don't know any more if it is OK to setup the network as before or not. I don't know it this works (jump to a label in another rule file), but perhaps this helps in your case: echo 'SUBSYSTEM="net" GOTO="persistent_net_generator_end"' > \ /etc/udev/rules.d/74-persistent-net-skip-generator.rules You can also add a rule 69, resetting 70-persistent-net.rules. But this are hacks, some udev config option would _perhaps_ make sense to catch some special cases. It is easy to implement it e.g. adding a check like the following one to the 75-persistent-net-generator.rules and similar GOTO and LABEL around the rules in 70-persistent-net.rules. IMPORT{file}="/etc/udev/persistent-net-generator.conf" ENV{DISABLE_PERSISTENT_NET_NAMES}=="yes",GOTO="persistent_net_generator_end" But this is a question to Kay, rather than to me. I've added Mili, since this may be interesting for him as well. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.