![](/static/66c60d9/assets/icons/icon-96x96.png)
![](https://beehaw.org/pictrs/image/cd7879c3-cd1c-4108-806e-f9ca45e9b22a.png)
Yup. The corruption is blatant, and the worst part is, they don’t even hide it… the threat of impending doom keeps the voters subservient. Instead of pointing out the corruption, we equivocate. I’m not a nihilist or a pessimist and most certainly do not want Trump to win. But refusing to acknowledge the blatant corruption puts us right where we started.
Props to you for actually reading the article. If anyone else who replied to the comment had done the same, there wouldn’t be as many “what-about-isms”
As a data center engineer of 10+ years, I struggled to understand this at first. In my world, the hardware does a POST before the OS boots and has an inventory of what hardware components are available, so it shouldn’t matter in what order they are discovered, since the interface names should make a correlation between the interface and the pcie slot that NIC exists in.
Where the water gets muddled is in virtualized servers. The NICs no longer have a correlation to a specific hardware component, and you may need to configure different interfaces in the virtualized OS for different networks. I think in trying to create a methodology that is agnostic to bare metal/virtualized OSs, it was decided that the naming convention should be uniform.
Probably seems like bloat to the average admin who is unconcerned with whether these NICs are physical or virtual, they just want to configure their server.