Jonathan Billings wrote: <snip>
And *why* random NIC names? Quick, you've got servers from 5 manufacturers, of different ages... what's the NIC going to be called? Do names like enp5s0 offer any convenience to *anyone* not a hardware engineer?
Unrelated to systemd. This actually started happening in RHEL6 with the biosdevname feature. systemd can handle the NIC naming stuff, but it started happening well before systemd appeared in RHEL.
Having consistent device names is helpful when you've got more than one NIC and you don't want to rely on the order in which the network driver is loaded to define the interface name.
In what universe are those "consistant" device names, as opposed to eth[0...]? And how could it help automated scripts that you can run on *any* system you're administering?
mark