<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>zanny</author><text>It is &lt;i&gt;not&lt;/i&gt; a systemd bug to mount efivars read&amp;#x2F;write. The efitools - efibootmgr et al - &lt;i&gt;require&lt;/i&gt; write access to that table. By the spec, this should not brick computers.&lt;p&gt;The problem is not systemd, its disastrous proprietary UEFI implementations that are shipping the most insecure and awful code in the world.&lt;p&gt;The &lt;i&gt;problem&lt;/i&gt; is we &lt;i&gt;cannot&lt;/i&gt; fix this for 9233. MSI will absolutely refuse to disclose the firmware to his laptop so that he can make it so his replacement does not also brick itself. People have been treating coreboot &amp;#x2F; libreboot like a joke for a decade, but this is exactly why those projects matter and why the continued erosion and trend towards firmware blobs and proprietary bootloaders cripples individuals control of the hardware they supposedly own.&lt;p&gt;Its the John Deere tractor problem, but until enough people care - I mean, enthusiasts and techies already don&amp;#x27;t care, and we would need a popular general consumer movement to care to inspire real change - it will only get worse.&lt;p&gt;All the 802.11 AC wireless NICs in the Linux kernel use firmware blobs. As of Skylake, there is not a single GPU supported on x86 systems in Linux that does not use firmware blobs. Almost every Chromebook is shipping Coreboot with cancerous unauditable firmware blobs. Samsung SSDs have bricked themselves because of their proprietary firmware blobs. Its a constant endemic problem yet nobody cares to put their money where their mouth is.</text><parent_chain><item><author>Cartwright2</author><text>Reading poettering&amp;#x27;s response (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;systemd&amp;#x2F;systemd&amp;#x2F;issues&amp;#x2F;2402&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;systemd&amp;#x2F;systemd&amp;#x2F;issues&amp;#x2F;2402&lt;/a&gt;) I&amp;#x27;m left feeling like he needs a thorough &amp;quot;Mauro, SHUT THE F&lt;i&gt;&lt;/i&gt;* UP&amp;quot; response from Linus himself (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;lkml.org&amp;#x2F;lkml&amp;#x2F;2012&amp;#x2F;12&amp;#x2F;23&amp;#x2F;75&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;lkml.org&amp;#x2F;lkml&amp;#x2F;2012&amp;#x2F;12&amp;#x2F;23&amp;#x2F;75&lt;/a&gt;)</text></item></parent_chain></comment><story><title>No POST after rm -rf /</title><url>https://bbs.archlinux.org/viewtopic.php?id=207549</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>nextos</author><text>He needs one, and you shouldn&amp;#x27;t get downvoted for saying this.&lt;p&gt;Systemd has brought lots of good things to Linux, but tons of bloat and insanity too. I&amp;#x27;m quite scared because the next thing they seem to be tackling is one of the core things that makes Linux so nice, package management [1].&lt;p&gt;They intend to container-ize everything. While that might be in principle good (NixOS got it right), their solution is likely to end up being a mess: no control over container contents. Imagine a critical security bug on e.g. OpenSSL. Good luck patching all your dozens of unmanaged containers running different OpenSSL library instances.&lt;p&gt;[1] &lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;0pointer.net&amp;#x2F;blog&amp;#x2F;revisiting-how-we-put-together-linux-systems.html&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;0pointer.net&amp;#x2F;blog&amp;#x2F;revisiting-how-we-put-together-linu...&lt;/a&gt;</text><parent_chain><item><author>Cartwright2</author><text>Reading poettering&amp;#x27;s response (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;systemd&amp;#x2F;systemd&amp;#x2F;issues&amp;#x2F;2402&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;systemd&amp;#x2F;systemd&amp;#x2F;issues&amp;#x2F;2402&lt;/a&gt;) I&amp;#x27;m left feeling like he needs a thorough &amp;quot;Mauro, SHUT THE F&lt;i&gt;&lt;/i&gt;* UP&amp;quot; response from Linus himself (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;lkml.org&amp;#x2F;lkml&amp;#x2F;2012&amp;#x2F;12&amp;#x2F;23&amp;#x2F;75&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;lkml.org&amp;#x2F;lkml&amp;#x2F;2012&amp;#x2F;12&amp;#x2F;23&amp;#x2F;75&lt;/a&gt;)</text></item></parent_chain></comment><story><title>No POST after rm -rf /</title><url>https://bbs.archlinux.org/viewtopic.php?id=207549</url></story>