After a few conversations with people on Lemmy and other places it became clear to me that most aren’t aware of what it can do and how much more robust it is compared to the usual “jankiness” we’re used to.

In this article I highlight less known features and give out a few practice examples on how to leverage Systemd to remove tons of redundant packages and processes.

And yes, Systemd does containers. :)

  • @TCB13@lemmy.worldOP
    9•2 years ago

    imagine some kind of GUI like Windows has for system services

    The problem is that systemd has so many possible options and ways to do things that you’ll either end up with something that “lags behind the actual systemd resources” or a glorified text editor specially made to write systemd units.

    • Skull giver
      5•2 years ago

      I don’t think so. There are a few freeform fields, but most settings only allow a few options you could easily put in a drop down menu or even a few checkboxes.

      Windows has a similarly complex configuration system in its registry (arguably it’s even more complicated). It’s more based around integers than arbitrary string values, but the concepts aren’t all that difficult.

        • Skull giver
          9•2 years ago

          If systemd can parse them, the GUI can list them. A simple list view with add/edit/delete would work just fine.

          Microsoft solved this problem decades ago:

          A screenshot the Windows 2000 control panel, showing a dialog to edit the IP address and subnet mask from a list

          • @TCB13@lemmy.worldOP
            7•2 years ago

            Good old Win32 GUIs with their tabs can do anything. Too bad people don’t want those anymore.