3 ms·
Ah ah, same usual shit of systemd wanting to be this monolith that takes control of all of your linux system (login, home dir, oom, ...), with strong opinions a
by greatgib 4y ago
Ah ah, same usual shit of systemd wanting to be this monolith that takes control of all of your linux system (login, home dir, oom, ...), with strong opinions and low quality code. And as usual, you introduce it and it starts to break for users.
If only it was the first time...
- thawaya3113 4y agoExcept systemd is almost the exact opposite of a monolith. Systemd runs just fine even without systemd-oomd and can probably be disabled by a command as simple as: > systemctl disable --now systemd-oomd and doesn’t need to be installed in the first place.
- seabird 4y agoIt's not not-a-monolith just because you can disable or remove an ever increasing number of "tested"/supported functionalities and move further and further away from the supported configuration. This might be OK for personal or toy systems, but it's an immediate pass for anybody who cares about their time. This comes up every time the systemd discussion happens and it's a little absurd that people need constant reminders that replacing a decent chunk of a base Linux install piecemeal is not viable.