2 ms·
There is a lot of strong criticism of systemd in that thread. I was actually considering posting it as sympathetic to my point. It simultaneously expresses wha
by asveikau 12y ago
There is a lot of strong criticism of systemd in that thread. I was actually considering posting it as sympathetic to my point. It simultaneously expresses what both of us are saying. (You can read the command line, but don't do it for stupid shit.) From your link:
> But the problem appears when system services seem to think that they
own those flags, and nothing else matters, and they don't do
something "sane" any more.
Then later:
> It does become a problem when you have a system service developer who
thinks the universe revolves around him, and nobody else matters, and
people sending him bug-reports are annoyances that should be ignored
rather than acknowledged and fixed. At that point, it's a problem.
Next paragraph indicates the rant is directed at Kay Sievers, udev and systemd developer, and his "continued bad behavior".
It does ring true for me as a user, I have noticed systemd-based systems spam a lot of things that used to be "for the kernel" and a bit more sacred, like dmesg and command line.