Comment # 6 on bug 953769 from andreas bittner

Hello there, thanks for the support, so if I add those parameters to the kernel
boot parameters and those other things you described

it will make use of my 'old' enpXsY config files with the leap 42.1 4.1.x
kernel when i reboot it?

so it will not become into ethX and ethY right? then i can fix the stuff later
of if you guys bring us some fixed packages or patches for this situation.

only I feel i will have nightmares again when i keep these enpXsY config style
with the next leap 42.2 or whatever :)

or I can of course fix this stuff again manually when I am at the site of that
machine again next time.


p.s. maybe dmesg kernel boot logs will tell me which ethernet card briefly gets
assigned eth0 and eth1 or similar during the bootup process and then gets
renamed into enpXsY again and use my existing config files, and then after the
initial successful boot I can then rename my files and modifiy susefirewall
config file and other places and then have that system turned back into the
official clean way of leap 42.1 configuration. Does this sound like a valid
attempt?