I should just block systemd apologists preemptively
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.
-
-
What really pissed me off was when Ubuntu went from em1/em2/... to eno1/eno2/.... between 14.04 and 16.04. *That* was a useless change. How did they manage to get it wrong the first time? That broke VM live migration across versions for me on a certain cluster.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
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.
- Show replies
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.