3 ms·

That bug is like the quintessence of why systemd is bad. Breaking the system when getting user input that previously worked, not even knowing that the existing

by onli 10y ago

That bug is like the quintessence of why systemd is bad. Breaking the system when getting user input that previously worked, not even knowing that the existing tools they replaced had safe-guards against this problem, and when confronted with the issue having a first reaction of "that's not a problem". The one good thing about this is that they did not close it as 'won't fix'.

majewsky 10y ago
The first reaction was to fix the bug. The discussion started after that.
kasabali 10y ago
> The one good thing about this is that they did not close it as 'won't fix'. My educated guess based on reading several previous bug reports is that Poettering would've drag his feet and maybe first close it as wontfix before fixing the issue some time later. Thankfully Martin Pitt fixed it quickly before Poettering came over to badmouth UNIX and point out how everybody else is wrong.