3 ms·
> 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)
by eeZi 11y ago
> 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).
- 5ilv3r 11y agoMy 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.
- ambrice 11y agoIt seems to me like it's a bad thing that an accidental rm in an efivarfs filesystem can brick the system, regardless of whether the filesystem was automounted or not.
- EmanueleAina 11y agoWindows 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.