On Tue, Apr 11, 2017 at 08:09:01AM -0400, Pete Orrall wrote:
> > 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?
>
> As someone else had stated, it's not related to SystemD but
> Fedora/RHEL has changed the way they handle some things. NICs, for
> instance, are no longer named after the device number (eth0, eth1,
> eth2, etc.) but after the *driver* name. Yes, it's a change but it
> also makes sense. IIRC this is how FreeBSD handles NIC names.
It's true that FreeBSD names their network interfaces after the driver.
But the consistent device naming in Linux comes from slot index
numbers, physical location and even the MAC (if so configured), and
not what driver it uses.
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Networking_Guide/ch-Consistent_Network_Device_Naming.html#sec-Naming_Schemes_Hierarchy
--
Jonathan Billings <billings@xxxxxxxxxx>
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
