So, a one-liner brings down systemd as an unprivileged user. Why the fuck is this reported via twitter and not a proper bug report?
-
-
Replying to @carlosefr
Not me, but if it were me: because people have been telling the systemd folks how moronic is to have this in PID 1 for *years*.
1 reply 0 retweets 0 likes -
Replying to @marcan42 @carlosefr
When your development model pretty much *guarantees* a plethora of bugs like this, what's the point of responsible disclosure?
1 reply 0 retweets 0 likes -
Replying to @marcan42
Because responsible disclosure isn't for the user's sake, not the developers? The guy only opened the bug report *after* posting.
2 replies 0 retweets 0 likes -
Replying to @carlosefr
RD only works when bugs are scarce enough. If your model is broken and anyone can look at the code and find bugs, RD fails.
1 reply 0 retweets 0 likes -
Replying to @marcan42
However you spin it, it's the *users* that pay the price for the guy's 15 minutes of fame. That's unacceptable in my book.
2 replies 0 retweets 1 like -
Replying to @carlosefr
Short-term, yes. Long-term, deserved shaming *might* have more positive effects on the development model, benefiting users.
1 reply 0 retweets 0 likes -
Replying to @marcan42
What has even more positive effects is enough contributions from outside the core devs to make a difference.
1 reply 0 retweets 0 likes -
Replying to @carlosefr
When the core devs have stubbornly decided on the wrong design, outside contributions can rarely change that.
1 reply 0 retweets 0 likes -
Replying to @marcan42
systemd is now on every major distribution. Any of those can gather enough resources to shift the balance.
1 reply 0 retweets 0 likes
Given how every major distribution that currently defaults to systemd used something worse previously, not sure I trust them.
-
-
Replying to @marcan42 @carlosefr
(as far as init systems that is; systemd is worse than all the non-init daemons/services it's trying to replace)
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.