search for: naming_schemes_hierarchy

...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 at negate.org>

...t 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 > Okay that makes sense. eno1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether 0c:c4:7a:c8:a5:4c txqueuelen 1000 (Ethernet) eno2: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether 0c:c4:7a:c8:a5:4d txqueuelen 1000 (Ethernet) Those two are my onboard nic,...

...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 >> >> > > Okay that makes sense. > > eno1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 > ether 0c:c4:7a:c8:a5:4c txqueuelen 1000 (Ethernet) > eno2: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 > ether 0c:c4:7a:c8:a5:4d txqueuelen 1000...

Pete Orrall wrote: >> So, at which stage are you in w/ regards to adopting systemd? Are you >> still >> ridiculing it, violently opposed to it, or have you mellowed to it? > > I've never had to write my own init scripts before so I'm not feeling > the pain of others, but having professionally managed machines running > SystemD for a while now honestly I