<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Boot on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/boot/</link>
    <description>Recent content in Boot on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 22 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/boot/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Initramfs Builders: dracut vs mkinitcpio vs initramfs-tools</title>
      <link>https://www.pistack.xyz/posts/2026-05-22-self-hosted-initramfs-builders-dracut-vs-mkinitcpio-vs-initramfs-tools-guide/</link>
      <pubDate>Fri, 22 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-22-self-hosted-initramfs-builders-dracut-vs-mkinitcpio-vs-initramfs-tools-guide/</guid>
      <description>&lt;p&gt;When a Linux server boots, the kernel needs access to the root filesystem — which may reside on LVM, encrypted volumes, RAID arrays, or network storage. The &lt;strong&gt;initramfs&lt;/strong&gt; (initial RAM filesystem) bridges this gap by loading drivers, unlocking encrypted disks, and assembling storage before the real root mounts. But not all initramfs builders are created equal.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
