SUSE does this in /etc/udev/rules.d/
cat 70-persistent-net.rules
# This file was automatically generated by the /usr/lib/udev/write_net_rules
# program,run by the persistent-net-generator.rules rules file.
#
# You can modify it,as long as you keep each rule on a single
# line,and change only the value of the NAME= key.
# S/390 qeth device at 0.0.3000
# S/390 qeth device at 0.0.4000
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="qeth", ATTR{dev_id}=="0x0",
KERNELS=="0.0.3000", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="qeth", ATTR{dev_id}=="0x0",
KERNELS=="0.0.4000", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
FWIW.
-----Original Message-----
From: Linux on 390 Port <LINUX-390@VM.MARIST.EDU> On Behalf Of Grzegorz
Powiedziuk
Sent: Tuesday, January 15, 2019 1:03 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] order of eth0/eth1 and udev rules vs kernel discovery
> But if I want device 2000 to become eth0 and it happened to be eth0 then
> it will fail because 3000 is using already eth0 name ...
>
> Sorry, I had a typo which turned above into a complete nonsense
I meant of course that it it happened to be eth1 after kernel discovery and
I want it to be renamed to eth0 it will fail (because eth0 is used by 3000)
thanks
Gregory
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
