I’m curious to know why people use systemd-less distributions. Which one would you recommend to someone who wants to stop using systemd?

  • BB_C@programming.dev
    link
    fedilink
    arrow-up
    0
    ·
    4 days ago

    Let’s play a game. Pick a “separate utility” from the list above, and let’s see if you know what you’re talking about, or just waffling.

      • BB_C@programming.dev
        link
        fedilink
        arrow-up
        0
        ·
        4 days ago

        First one on the list.

        % readelf -d /usr/bin/bootctl | rg -r '$1' '.*NEEDED.*\[(.*)\]'
        libsystemd-shared-262-1.so
        libgcc_s.so.1
        libc.so.6
        
        • esc@piefed.social
          link
          fedilink
          English
          arrow-up
          0
          ·
          edit-2
          3 days ago

          Are you familiar with the concept of shared libraries? Please, stop embarrasing yourself.

            • esc@piefed.social
              link
              fedilink
              English
              arrow-up
              0
              ·
              3 days ago

              How boring.

              Will you ever get to the point where you say clearly why exactly bootctl isn’t a separate utility? No, having dependencies doesn’t make something not a separate utility. And no, communicating with systemd daemon over unix sockets doesn’t as well.

              • BB_C@programming.dev
                link
                fedilink
                arrow-up
                1
                ·
                3 days ago

                Good.

                So the tool YOU chose is NOT:

                • standalone at the project level ✅
                • standalone at the repo level ✅
                • standalone at the source level (trivially shown with the libsystemd-shared.so dep without requiring looking further) ✅
                • standalone/fully independent at the runtime level ✅

                This and the sibling sub-thread where I mentioned presets show with actual facts how the systemd forced hegemony actually works, where it’s not just a simple case of “they just have some stand-alone cli tools under their umbrella bro”.

                The project itself wouldn’t try to (clumsily) dispute this either, since it’s at the core of what they consider a selling point; interface unification and deeper integration with the system.

                • esc@piefed.social
                  link
                  fedilink
                  English
                  arrow-up
                  1
                  ·
                  3 days ago

                  So, you’ve demonstarted nothing and all your points were refuted. Then you’ve made up a list with checkmarks and proudly proclamed yourself right? 😮‍💨