search for: consistent_network_device_nam

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

...on 82571EB Gigabit Ethernet Controller (rev 06) 08:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06) [0] https://access.redhat.com/site/articles/3078 [1] https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/appe-Consistent_Network_Device_Naming.html -- ---~~.~~--- Mike // SilverTip257 //

...er 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 > 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 (Ethe...

...eing applied to the wrong NIC. And here I thought the point of [CNDN][1] was to make such replacements more reliable than the plug-and-pray logic behind ethN. This is the sort of reason why I need non-Linux sysadmin types to be able to change IPs in the field. [1]: https://en.wikipedia.org/wiki/Consistent_Network_Device_Naming

...>> 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 >> >> > > 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 > eth...

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

We had a complaint recently from a customer that received a server we shipped out that their monitor just showed a black screen. It turns out that they?d hooked it up to an ancient POS with 800x600 as its best resolution, and gdm in CentOS 7 apparently assumes at least 1024x768. It was apparently a major hassle for them to hunt down a reasonable monitor for us. Since we almost never use the GUI