<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Warning for #NixOS users out there:]]></title><description><![CDATA[<p>Warning for <a href="https://social.zerojay.com/tags/NixOS" rel="tag">#<span>NixOS</span></a> users out there:</p><p>The new systemd intird was submitted to NixOS unstable and is now the default as of a few days ago. I discovered the hard way that if you have the <a href="https://github.com/FlameFlag/nixcord" rel="nofollow noopener"><span>https://</span><span>github.com/FlameFlag/nixcord</span><span></span></a> flake in your configuration after updating your flakes and rebuild, you'll be unable to properly boot.</p><p>After spending time with the people working on NixOS's systemd, we discovered that there's an activation script that nixcord uses that causes the problem.</p><p>So the only solutions are to disable the systemd initrd (which will be the default in unstable and the next release of NixOS), or disable Nixcord.</p><p><a href="https://social.zerojay.com/tags/linux" rel="tag">#<span>linux</span></a> <a href="https://social.zerojay.com/tags/discord" rel="tag">#<span>discord</span></a> <a href="https://social.zerojay.com/tags/opensource" rel="tag">#<span>opensource</span></a></p>]]></description><link>https://board.circlewithadot.net/topic/5b77d3bd-45c5-46ee-89bc-03d0c07a90c3/warning-for-nixos-users-out-there</link><generator>RSS for Node</generator><lastBuildDate>Fri, 15 May 2026 00:27:26 GMT</lastBuildDate><atom:link href="https://board.circlewithadot.net/topic/5b77d3bd-45c5-46ee-89bc-03d0c07a90c3.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 16 Apr 2026 21:20:35 GMT</pubDate><ttl>60</ttl></channel></rss>