<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Live-Patching on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/live-patching/</link>
    <description>Recent content in Live-Patching 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/live-patching/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Linux Kernel Live Patching: kpatch vs kgraft vs Canonical Livepatch</title>
      <link>https://www.pistack.xyz/posts/2026-05-29-self-hosted-linux-kernel-live-patching-kpatch-kgraft-canonical-livepatch-guide/</link>
      <pubDate>Sat, 23 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-29-self-hosted-linux-kernel-live-patching-kpatch-kgraft-canonical-livepatch-guide/</guid>
      <description>&lt;p&gt;Linux kernel live patching allows system administrators to apply critical security patches and bug fixes to a running kernel &lt;strong&gt;without rebooting&lt;/strong&gt;. For production servers handling enterprise workloads, even a few minutes of planned downtime can translate into significant revenue loss, SLA violations, or disrupted user experiences. This guide compares the three major open-source live patching solutions available for self-hosted Linux environments.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
