https://giacomodiclerico.com/en/tags/linux/Recent content in Linux on Giacomo Di ClericoHugoen-usTue, 28 Jul 2026 00:00:00 +0000https://giacomodiclerico.com/en/blog/from-gentoo-to-nixos/Tue, 28 Jul 2026 00:00:00 +0000https://giacomodiclerico.com/en/blog/from-gentoo-to-nixos/<p>I&rsquo;ve been distro-hopping with intent for a while now. Not for fun — each switch taught me something fundamentally different about Linux. This is the story of how I went from Arch to Gentoo to NixOS on my main workstation.</p> <hr> <h2 id="arch--a-solid-year-as-my-daily-driver">Arch — a solid year as my daily driver</h2> <p>I&rsquo;ve been using Linux for a long time across various distributions, so I was already quite experienced when I moved to Arch Linux. Arch became my main operating system for over a year. Rolling release, minimal base install, and the wiki made it a solid daily driver. It taught me how to construct and maintain a system from the ground up. But after more than a year of running it daily, I wanted even deeper control — not just over what packages were installed, but over <em>how</em> they were compiled and configured.</p>https://giacomodiclerico.com/en/blog/server-bootc-to-nixos/Tue, 28 Jul 2026 00:00:00 +0000https://giacomodiclerico.com/en/blog/server-bootc-to-nixos/<p>I recently migrated my homelab server from a <strong>bootc</strong> (bootable container) setup on Fedora to <strong>NixOS</strong>. The trigger wasn&rsquo;t philosophical — it was a real breakage caused by the iptables/nft transition and Fedora&rsquo;s kernel policy.</p> <hr> <h2 id="the-bootc-setup">The bootc setup</h2> <p><strong>bootc</strong> is a model where your entire OS is defined as an OCI container image. You write a <code>Containerfile</code>, build the image, push it to a registry, and the server pulls and boots from it. It&rsquo;s immutable infrastructure taken to its logical extreme — your OS has a CI/CD pipeline.</p>