I should just block systemd apologists preemptively
-
-
It's eno1, eno2, etc. for internal ethernet when the motherboard firmware is decent and falls back to bus location. The default of using the USB topology instead of a MAC might be what ends up annoying people most since it changes if you switch the port. https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ …
-
I turn it off on my laptop, since it almost always only has eth0/wlan0 on boot and anything else is hotplugged. I also sometimes turn it off on trivial systems with a single port and no hotplugging (e.g. embedded). But it's good for anything with 2+ ports, particularly servers.
-
It's somewhat useful here since it calls the internal one eno1 (since the motherboard is sane) and provides consistent naming for USB tethering via Android / CopperheadOS based on USB port.
-
Can see why someone would be unhappy about it if they use a laptop with USB tethering and don't plug into the same port every time. Instead of eth0 they get enp5s0u1, enp5s0u2 or similar depending on port. Configuring it to use MAC would be worse since it's random each time.
-
The vast majority of consumer hardware I've seen does not provide the proper metadata to make eno1 work. I've only seen that on servers (and even then not on older servers). It's great when it works though.
-
This is consumer hardware, but at the high end (X99 with a Broadwell-E CPU): https://www.evga.com/articles/00941/EVGA-X99-Micro2-Motherboard/ ….
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.