No, the discussion was mostly about the parameter as a way to suppress fsck if you know you're in a hurry at boot time. That argument was followed with other '

No, the discussion was mostly about the parameter as a way to suppress fsck if you know you're in a hurry at boot time. 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.