5 ms·
This isn't a systemd problem. It's a kernel problem. Allowing accidental access to a resource capable of doing permanent damage is dumb. Even embedded proces
by bsder 11y ago
This isn't a systemd problem. It's a kernel problem.
Allowing accidental access to a resource capable of doing permanent damage is dumb. Even embedded processors generally have an "unlock/lock" sequence when you want to write to their flash memory.
The fact that the kernel doesn't require you to write a "magic number" somewhere to gain access is foolhardy.