For context, this is in reference to a bug that was discussed a couple weeks ago: <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=10999335" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=10999335</a><p><pre><code>  Systemd mounted efivarfs read-write, allowing motherboard bricking via &#x27;rm&#x27; 
</code></pre>
Essentially, systemd defaulted to a configuration where the computer&#x27;s motherboard could be permanently destroyed by removing a &#x27;file&#x27; from the command line.  The bug reporter argued that this was unduly dangerous, but the systemd developers thought that systemd was working as intended.<p>Here&#x27;s a reasonably impartial discussion on a FreeBSD list that gives an overview: <a href="https:&#x2F;&#x2F;forums.freebsd.org&#x2F;threads&#x2F;54951&#x2F;" rel="nofollow">https:&#x2F;&#x2F;forums.freebsd.org&#x2F;threads&#x2F;54951&#x2F;</a><p>And from that thread, here&#x27;s a link to Matthew Garrett (the creator of efivarfs) saying that efivarfs is at fault here rather than systemd: <a href="https:&#x2F;&#x2F;twitter.com&#x2F;mjg59&#x2F;status&#x2F;693494314941288448" rel="nofollow">https:&#x2F;&#x2F;twitter.com&#x2F;mjg59&#x2F;status&#x2F;693494314941288448</a>