I&#x27;d say it wasn&#x27;t a bug in systemd&#x27;s implementation, it was a bug in the <i>design</i> of systemd. Why require that evivarfs be mounted at runtime? You could easily make it so that it is only mounted at boot time if neccessary, or only when you run a tool that wants to write to EFI.<p>I&#x27;d expect file operations to only permanently affect storage devices per default. Sure you can mount almost anything as a file in Unix, but to automatically mount more than necessary is bad design. It&#x27;s like placing mystery files in the filesystem, and when a curious user deletes or modifies them, they loose their monitor&#x27;s color profile, there printer&#x27;s firmware, or all of their GMail attachments. You could say it was the user&#x27;s fault to mess with it, but I&#x27;d say it&#x27;s weird to expose such things as files (unless explicitly asked for by the user or a tool).