it's not eth0 anymore, it's enp5s0
@hipsterelectron @arrjay @jiub actually kinda like that
@c0dec0dec0de @hipsterelectron @jiub *sigh* I deeply do not care for what systemd did, though. and wound up with a pile of systemd.link files to match on path/firmware/property=DEVPATH keys so all my crap reliably has wl and be([0|1]) interfaces. I still think that was a very arbitrary and painful break.
@arrjay @c0dec0dec0de @jiub after engaging poettering on the dlopen backdoor i am ruthless about any and all systemd hate. my body is a machine that turns keyboards into flaming systemd
@hipsterelectron @c0dec0dec0de @jiub no no, see, we just assume the user has NO AGENCY AT ALL and systemd's choices and defaults make sense
@arrjay @hipsterelectron @c0dec0dec0de @jiub I've been in more than one workplace where install scripts override systemd's device enumeration. The thing was, they'd do it in stupid, broken ways, that actually left me biased in favor of systemd, until a year or two ago.
@foolishowl @arrjay @hipsterelectron @c0dec0dec0de @jiub 12, maybe 15 years ago, I *liked* systemd and didn't get all the hate.
Now that I have seen it expand to encompass the entire fucking system (which is everything the haters said it would do!) I am not just a hater, but a person who has attempted to evaluate their prior positions on trust and learned a lesson about how some fucking asshole can basically utilize their software as a wedge to gain a prominent position in the software world and shut out everyone else.
I am still mad that a systemd system fucking kills all your processes when you log out of a graphical session. Yes, sure, there's an option to disable that. There's "always an option" to disable that. But we're all opted into whatever random ass decision leo made and blah blah blah.
@foolishowl @arrjay @hipsterelectron @c0dec0dec0de @jiub I also don't need systemd's random sudo re-implementation, in the same way I don't need canonical's sudo re-implementation, in the same way I don't need the default behavior of a failed mount to *completely stop the startup sequence*, in the same way that I don't need to learn an entirely new bespoke language to write a fucking daemon, in the same way that I don't need Docker II But It Somehow Sucks More, in the same way that I don't need a literal blue screen of death, in the same way that I-
@foolishowl @arrjay @hipsterelectron @c0dec0dec0de @jiub I get that I'm old crank yelling at clouds blah blah blah
but I do not trust Lennart; I do not like his decisions; I sure as hell do not like how it's *always more* with systemd. It always creeps just a bit further, replacing more and more and more.
@foolishowl @arrjay @hipsterelectron @c0dec0dec0de @jiub@evilcyberhacker.net also? pulseaudio BLOWS lenny, you should have fucking fixed *that*
@aud @arrjay @hipsterelectron @c0dec0dec0de One init system to rule them all and in the confusion bind them.
(Also we need Galadriel as OpenRC or something along those lines.)
misinfo
wifey says that eowyn fits for openrc better, i'd play that part
(illumos/*BSD use the driver name as base)