My understanding is that the amount of software that wants&#x2F;needs to write to efivarfs is fairly small[1] compared to the amount of software that is normally run with root privileges.<p>The fact is that &#x27;rm -rf &#x2F;&#x27; is a common mistake, both at the command line (i.e. manually typing) and in scripts that don&#x27;t adequately protect against things like missing variables. E.g.:<p><pre><code>  MY_DIR=
  rm -rf &quot;$MY_DIR&#x2F;&quot;
</code></pre>
The fact that this could brick a system is a <i>big deal</i>. Pushing blame around doesn&#x27;t do anybody any good.<p>[1] I realize that boot loaders like grub are everywhere and probably need to write to efivarfs, but that&#x27;s still a data point of 1. Would it be that difficult for grub and it&#x27;s related scripts to upgrade to remount the filesystem readwrite when it needs to perform an operation? I&#x27;m sure it&#x27;s only been a couple of years since efivarfs functionality was even added to grub.