Edit: I guess downvoters don't care about code smell. This is literally like an unrelated process pulling out someone else's argv and using it as their own. Ick.
> 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.
That argument was followed with other 'bad luck, if you want tonchange your choice' examples, like rm-ing a file. The argument sucks, but at no point a hard reset was part of the suggestion, really. More a "Yeah, so why didn't you pass the parameter and why do you complain about that afterwards"
That said, both sides of the discussion became immature rather quickly (my favorite is the "I killed a Windows 8 laptop because only that stopped the updates") and the issue isn't all that big in the first place, because systemd might support fsck interruption in the future/it seems to be on the todo list and therefor accepted as a missing feature.