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

  • GlowHuddy@lemmy.world
    10·
    1 year ago

    Thinking about it from your point of view, maybe MS was right and Linux is a cancer too. Technically it behaves similarly to systemd, since most Unixes are actually Linuxes nowadays (excluding BSD ofc, but they are still in the minority, similarly to alternatives to systemd). It even is a binary blob as well!

    Should every distro use/develop a different kernel? Should we focus our resources on providing alternatives and again have a multitude of different Unix versions, every incompatible with each other? Isn’t it better that we have this solid foundation and make it as good as it can be?

    Overall I think standardization of init is not so bad, just like adopting the Linux kernel was. It is actually quite nice that you can hop from distro to distro and know what to expect from such a basic thing as init process.

    Anyways, in Linux land you actually have a possibility to replace it. Granted, it is not as easy, however there are plenty of distros that allow you to ditch systemd in favor of something else.