systemd cat and GNU cat hugging a Linux cat.

      • Remy Rose@piefed.social
        link
        fedilink
        English
        arrow-up
        11
        ·
        3 days ago

        The gui installer was roughly about as simple as any other distro I’ve tried, and stuff generally seemed to work out of the box. There are more packages than one might expect from such a small distro too. Not sure I have any advice specific to Void really, although getting a custom bootloader onto a Chromebook was certainly a trip lol

  • NeatNit@discuss.tchncs.de
    link
    fedilink
    arrow-up
    24
    arrow-down
    1
    ·
    3 days ago

    As a user, why should I care whether the distro I use uses systemd? I use Mint and I don’t remember having to interact with that kind of low-level nonsense. The distro maintainers can use whatever reasoning they want to pick these details.

    • kautau@lemmy.world
      link
      fedilink
      arrow-up
      10
      ·
      3 days ago

      Tribalism exists in every circle, perhaps moreso in tech circles. Ironically anyone who hates on a distro could just switch, or build their own distro if they were so inclined, but it’s often the hating that people participate more in than using their system. Use what works for you, and if it no longer works for you use something else.

    • kiri@ani.social
      link
      fedilink
      arrow-up
      9
      arrow-down
      1
      ·
      3 days ago

      There is an openrc package in aur, so perhaps arch can use non-systemd init as well.

      • Lucy :3@feddit.org
        link
        fedilink
        arrow-up
        15
        ·
        3 days ago

        Would probably be a hell to actually implement, as everything is made for systemd (as in, all packages rely on systemd for being run)

  • misterbzr@lemm.ee
    link
    fedilink
    arrow-up
    19
    ·
    3 days ago

    Alpine.

    Have used crux but using low end / old hardware results in almost permanent building software.

    • mynona@lemmy.world
      link
      fedilink
      arrow-up
      4
      ·
      3 days ago

      I wonder how far we are from CI drivers ala Nix that fork builds out to idle hardware like a distributed torrent network. As someone with three out of tree modules in use, there must be dozens of us I’d like to think.

      • Illecors@lemmy.cafe
        link
        fedilink
        English
        arrow-up
        1
        ·
        3 days ago

        That is something I’ve already run into at my previous workplace. The name escapes me atm…

  • notabot@piefed.social
    link
    fedilink
    English
    arrow-up
    14
    ·
    3 days ago

    Debian, installed without systemd as per the wiki. So far I’ve not hit any issues, whilst I’ve recently ended up diving through both kernel and systemd code to find the root cause of an issue I was hitting on one server. I could have just bodged past it, but I wanted to actually understand what the issue was, and what else it was going to affect.

      • notabot@piefed.social
        link
        fedilink
        English
        arrow-up
        7
        ·
        3 days ago

        Honestly, I’m not sure, I was looking at Devuan, but then noticed that Debian supported sysvinit natively so I went that route instead. I figure that sticking to the source distro was going to give me fewer headaches, and so far it’s been plain sailing.

    • rtxn@lemmy.worldM
      link
      fedilink
      arrow-up
      8
      ·
      3 days ago

      Some people think it handles too many low-level systems. It’s a valid concern because if systemd itself were to become compromised (like Xz Utils was) or a serious bug was introduced, all of the userland processes would be affected. People who are stuck in the 90s and think that the Unix philosophy is still relevant will also point out that it’s a needlessly complex software suite and we should all go back to writing initscripts in bash.

      Red Hat, the owner of systemd, has also had its fair share of controversies. It’s a company that many distrust.

      Ultimately, those whose opinion mattered the most decided that systemd’s benefits outweigh the risks and drawbacks. Debian held a vote to determine the project’s future regarding init systems. Arch Linux replaced initscripts because systemd was simply better, and replicating and maintaining its features (like starting services once their dependencies are running) with initscripts would’ve been unjustifiably complicated.

  • boaratio@lemmy.world
    link
    fedilink
    arrow-up
    11
    arrow-down
    4
    ·
    3 days ago

    So the old init.d system was better? Come on people, let’s stop infighting. I have zero preference on init systems. You know why? Because they’re just plumbing. Stop this nonsense. Do I click on an init system? Do I use the init system to check my email? Or play games? No. I know poettering can be controversial, but let’s just move on. Run freebsd if you’re so butt hurry.

    • dblsaiko@discuss.tchncs.de
      link
      fedilink
      arrow-up
      1
      ·
      3 days ago

      Yeah, on a desktop I don’t really mind whatever*. On a server however, I think systemd is great and I wouldn’t want to miss it anymore.

      * except Debian’s frankenstein systemd + sysvinit combination. Burn it

  • juipeltje@lemmy.world
    link
    fedilink
    arrow-up
    9
    ·
    3 days ago

    I don’t care about the init system, however i do love void mainly because of the package manager.