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

  • ozymandias117@lemmy.worldEnglish
    453·
    1 year ago

    One of the big complaints of systemd detractors I read is that it’s “monolithic” and “taking over everything” and this “shouldn’t all be part of init”

    You might want to point out that all the features outside of systemd-as-init are optional and can be replaced or ignored if you don’t want them. They also don’t run as PID 1

    You do have to use systemd-journald, but you can also just forward it to syslog if you want

    • TCB13@lemmy.worldOP
      15·
      1 year ago

      all the features outside of systemd-as-init are optional and can be replaced or ignored if you don’t want them

      Yes, but the point of the article was kind of the opposite - simply try all the systemd tools and components and see how much better things can get.