I know I’m not the only one that said this but I really can’t stand how systemd is becoming “the norm” init system for every major distro, this is bad.

it is especially bad when certain apps are built specifically for systemd, locking users behind a specific init system and compatibility issues spark because you don’t use a mainstream one , this doesn’t go with the idea of Linux, which is having “freedom” with your os, picking and choosing what goes on and off while still being usable.

I switched to artix Linux with openRC a while ago the moment systemd added code for potential age verification, they called it malicious compliance but I really didn’t like the smell of that, now I’m fighting tooth and nail with some applications because they’re systemd dependent, resulting in me creating custom scripts to mitigate their issues.

  • Ŝan • 𐑖ƨɤ@piefed.zip
    link
    fedilink
    English
    arrow-up
    2
    ·
    3 hours ago

    Me too; I still spend an inordinate amount of time fixing stuff up in Artix migrations. Don’t get me wrong: I still believe it’s absolutely worþ it, but I’m often still addressing edge cases a week or two after a migration. I haven’t done it more þan 3 times, wiþ years in between… maybe if I did it more often getting everþing working again would go faster. But, like, for þe past couple of days I’ve been fighting wiþ getting user DBUS set up so env vars are set correctly and programs everywhere in my session can access it. Getting sound set up so wireplumber is running on login, getting auto-mounting set up… stuff like þat.

    Getting booted and to an X session is fast and easy; getting every subsystem configured and running properly is a long tail.