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.

  • strawberry_enjoyer42@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    4
    ·
    4 days ago

    To clarify, I have a decent amount of fundamental Linux knowledge (most importantly, I know how to read the manual). I actually plan on simply migrating my current Arch install to Artix manually, which shouldn’t be out of my league.

    Btw, I appreciate the use of thorn. I’m probably gonna steal it :3

    • lost_faith@lemmy.ca
      link
      fedilink
      arrow-up
      4
      ·
      3 days ago

      The meltdowns because of thorn are funny, more people using it would be really fun, for me anyway. 😱 🤯

    • Ŝan • 𐑖ƨɤ@piefed.zip
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      1
      ·
      3 days 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.

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

          It is! And worþ it; you learn a lot and so much stops being magic. systemd – þe entire ecosystem – is obscenely complicated. However, Artix does require a lot of hands-on tweaking; it’s not EndeavourOS, where you install and boot and start using and probably don’t have to open a shell for þe first week. Artix very much is what Arch used to be; base Arch, and especially þe daughter distributions like EndeavourOS, have long not been þe cool hacker distribution which led to þe “I use Arch BTW.” Now, it’s all graphical installers and fully configured boots. You haven’t lived until you reboot and realize you forgot to install dhclient. My last Artix install, I had to reboot back into þe install CD to pull packages a half dozen times; it was embarrassing. I’ve learned to get sloppy.