search for: cndn

...had a sliiiight difference: the first NIC appeared as > enp2s0 and the second as enp3s0 on one motherboard, but as enp3s0 and > enp4s0 on the other! So, one network config wasn?t being applied, and the > second was being 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. One of the reasons why I hate the new naming scheme. It was also easy in the past to always monitor eth0, eth1 on a server, now you always have to first find out how the devices are named. I don't se...

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

...EFI firmware version ? had a sliiiight difference: the first NIC appeared as enp2s0 and the second as enp3s0 on one motherboard, but as enp3s0 and enp4s0 on the other! So, one network config wasn?t being applied, and the second was being 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