3
Aldar
5y

I really don't know how I feel about SystemD.

Their recent reveal of Systemd-Homed made me once again doubt the logic behind the project. I mean, yes, systemd is handy to work with at some occasions (SysVInit, for example, doesn't store information about when a certain service failed), but SystemD is slowly eating up more and more of the system's jobs, and I'm a little worried, what would happen if SystemD suddenly went bust.

That will never happen, I know, but... Wasn't the idea behind Unix... Its modularity? That its made up of clearly defined parts that cooperate with each other, rather than a huge, monolithic projects that handle several functions at once?

This is not meant to be a hate post about Systemd, just a little... reminiscence about its goal and role in the Linux community.

Any ideas are appreciated! Discussions are welcome. Just... keep it civil. Please.

Comments
  • 0
    My biggest concern is that systemd is locked to Linux and because of its widespread usage, may separate Linux from the rest of the *nix-world.
    My favorite alternatives are OpenRC and Runit.
  • 0
    What's wrong with systemd-homed?
  • 1
    @terraria99 the idea itself is alright, I just... Feel unsure about the overall size of SystemD's role in the Linux environment.

    If it keeps taking over more and more, it will be an entirely different system. It will be a GNU/Linux/Systemd

    If users were given options which part of the environment they want to install, then I guess, but shipping it preconfigured with everything? Thats huge!

    And when something breaks, you will not be able to isolate the issue as easily as with SysVInit, but will have to debug the entire systemd environment.
Add Comment