Oh yeah, systemd. The new and improved init replacement.
It sure looks less complex,
http://en.wikipedia.org/wiki/Systemd#mediaviewer/File:Systemd_components.svg
Yeah, I know about net.ifnames=0, but that just gets you back
to the ethX paradigm. So very "helpful" in a very generic
way. What about the idea about actually telling me what
the damn underlying hardware is by using a descriptive
device name. In the BSDs I know I can "man fxp" and actually
learn something about my NIC.
Any way, this was meant to be a post thanking OpenBSD
project and it's developers. So I'll stop the rant here.
diana
Past hissy-fits are not a predictor of future hissy-fits.
Nick Holland(06 Dec 2005)
On Wed, 11 Feb 2015, Giancarlo Razzolini wrote:
On 10-02-2015 22:26, Diana Eichert wrote:
My day job entails a lot of Linux support, lately I've been
dealing with the big screwup associated with network interface
naming. WHY can't Linux follow BSD's straightforward NIC
naming?
This answer is a simple one: systemd
It's positively bizarre all the crappy little files
and "utilities" they have come up with so you can munge NIC
names to something more useful than "p3p2"!!!.
I don't know if you know this, but just put net.ifnames=0 in your
kernel's parameters and it will revert to the old way.
Anyway, I, like you, have many OpenBSD systems that "just work". Thank
you OpenBSD.
Cheers,
Giancarlo Razzolini
