Systemd is incredibly versatile and most people, including myself, are unaware of its full potential. Despite its usefulness, it is often overlooked due to controversy and the current state of things when it comes to software development. Begin today your journey thought Systemd's capabilities and discover how to efficiently manage systems with fewer processes than traditionally used.

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. :)

    • Tobias Hunger@programming.dev
      111·
      1 year ago

      Where are those alternatives? I have not seen anything that is Baustoff convincing yet…

      It is not a project owned by redhat… the lead guy not even works there anymore. So the more interesting question is: What happens if Microsoft closes down the project? The answer: It will be forked.

    • garrett@kbin.social
      10·
      1 year ago

      Red Hat didn’t “close up the source” to anything. All the source to RHEL is available in CenOS Stream’s git repos. All of the source to all Red Hat products is available in upstream projects too. Nothing’s “closed”.

      What was announced was that the source to RHEL would only be publicly published in git (with history, tagged releases, etc.) instead of publically available SRPMs (unless you use a Red Hat account — even a free one — then you could also download SRPMs).