←back to thread

279 points the_why_of_y | 1 comments | | HN request time: 0.001s | source
Show context
tvbn ◴[] No.11153444[source]
They disabled kernel feature to prevent systemd bug? It doesn't make any sense.
replies(5): >>11153459 #>>11153462 #>>11153477 #>>11153479 #>>11153602 #
kbenson ◴[] No.11153479[source]
It's not a systemd bug, it was just exposed by systemd. This was what most everyone seemed to completely miss in the prior exchanges.

Another thing that was missed was that Lennart wasn't being unreasonable, nor was he saying it wasn't a problem (he specifically stated the opposite, in fact). I had a feeling at the time (based on his responses) that the reason he wasn't specifically stating he was going to fix it or open a bug report for it in systemd was that he was going to push it up-stack to a more appropriate place, and it looks like that's what happened.

replies(2): >>11153687 #>>11153716 #
eeZi ◴[] No.11153716[source]
> Another thing that was missed was that Lennart wasn't being unreasonable, nor was he saying it wasn't a problem (he specifically stated the opposite, in fact). I had a feeling at the time (based on his responses) that the reason he wasn't specifically stating he was going to fix it or open a bug report for it in systemd was that he was going to push it up-stack to a more appropriate place, and it looks like that's what happened.

This. It's really hard to blame this on systemd (not that people didn't try anyway).

replies(1): >>11153819 #
5ilv3r ◴[] No.11153819[source]
My bsd init and sysv init machines do not have this issue. They don't automount every damn filesystem they see at boot for no reason.
replies(2): >>11154317 #>>11157755 #
1. EmanueleAina ◴[] No.11157755{3}[source]
Windows does not have this issue either.

But on sysvinit if you mount efivars rw for any reason and your hands slip a bit a stray `rm` could still brick your motherboard, so it's not really fair to say that without automounting the issue goes away.