<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Boot-Management on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/boot-management/</link>
    <description>Recent content in Boot-Management on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 23 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/boot-management/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Linux kexec Fast Reboot: kexec-tools vs Alternatives — Self-Hosted Kernel Live Boot Management</title>
      <link>https://www.pistack.xyz/posts/2026-05-23-linux-kexec-fast-reboot-kexec-tools-alternatives-guide/</link>
      <pubDate>Sat, 23 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-23-linux-kexec-fast-reboot-kexec-tools-alternatives-guide/</guid>
      <description>&lt;p&gt;Rebooting a Linux server traditionally involves a full hardware reset cycle — the BIOS/UEFI firmware reinitializes, the bootloader loads the kernel, and the kernel performs its complete hardware discovery and driver initialization sequence. On large servers with extensive hardware, this process can take several minutes. The &lt;strong&gt;kexec&lt;/strong&gt; system call bypasses this entire sequence by loading a new kernel directly into memory and jumping to it from the running kernel — achieving a &amp;ldquo;fast reboot&amp;rdquo; in seconds instead of minutes. Three approaches to kexec management exist: &lt;strong&gt;kexec-tools&lt;/strong&gt; (the standard userspace utility), &lt;strong&gt;kexec-fastboot&lt;/strong&gt; (systemd integration), and manual &lt;strong&gt;kexec&lt;/strong&gt; invocation with custom scripts. For self-hosted server administrators managing kernel updates, crash recovery, and high-availability systems, understanding kexec is essential for minimizing downtime.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
