Yes, which is what we have here.  My point is that I don&#x27;t think there was ever any indication that the systemd developers thought there wasn&#x27;t a problem to be fixed.  That the fix was pushed farther up-stack so it was more comprehensive is not a bad thing in my eyes.<p>Put another way, systemd mounting efivarfs read-only doesn&#x27;t necessarily prevent you from bricking your machine by deleting files within that file system, it protects only those using systemd.  The problem stems from the nature of efivarfs, and that it was implemented as a file system and not some other interface.  Making it <i>default</i> to something more sane is a better (but by no means the best) solution, and that ideally would happen within the source, which is the kernel.