2 ms·
well windows can get write access to these aswell. (just not by using rm or any other tool to remove files by default). I think this is a big difference and sho
by merb 9y ago
well windows can get write access to these aswell. (just not by using rm or any other tool to remove files by default).
I think this is a big difference and should probably be addressed. make /sys read-only and allow to write them differently with a interface where I need to call THIS_METHOD_CAN_BREAK_A_SYSTEM_IF_USED_INCORRECT_WRITE_SYS() command. but well, systemd guys will/won't do that.
- JdeBP 9y agoIt wasn't a systemd thing. The people who relate the tale as if it were a systemd thing or something that the systemd people did are ill-informed. Much as in the case of the headlined bug at hand, it was entirely a kernel thing. This was even stated outright at the time by the creator of that particular kernel mechanism. To learn the real story, go and read https://news.ycombinator.com/item?id=11152880 https://news.ycombinator.com/item?id=11152880 where you will find Matthew Garrett xyrself participating in the discussion.