Comment by constantcrying
3 months ago
>I did not know and I must not know that to get a service running on start.
Exactly. So why is it part of your init system? Can you think of a reason why it is not a totally separate project which is totally independent of systemd?
From a surface glance systemd and openrc are almost identical. Both require very little to get something to work. The difference is that systemd does a million things more.
What you probably should know though is that many systemd distros do not have a real fstab, the fstab is just a file which systemd uses to create mount units, which are then used during boot.
Another important piece of knowledge is what a systemd "transaction" is, that is a very unintuitive concept which you absolutely need to know if you are debugging on your init system.
> Exactly. So why is it part of your init system?
Is it?
Systemd is not an init system. One component of systemd is an init. There are other components.
And that is why people hate systemd. Legitimately one of the worst software projects in existence.
People hate it because one part of it is designed to run as pid 1? I don't follow.
(People hate systemd? They hate a piece of software? Eesh)
3 replies →
> Exactly. So why is it part of your init system? Can you think of a reason why it is not a totally separate project which is totally independent of systemd?
What?
You can use SystemD to have services like a webserver or a python script started after boot. Doing it with systemd is exponentially more easy than with an init script.
How else would you start that if not with systemd (if that's all you have). I'm not sure you really understand what you can do with systemd, or you would not have written the comment you did