<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Module-Management on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/module-management/</link>
    <description>Recent content in Module-Management on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 24 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/module-management/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Linux Kernel Module Management: DKMS vs akmods vs module-assistant (2026)</title>
      <link>https://www.pistack.xyz/posts/2026-05-24-self-hosted-linux-kernel-module-management-dkms-akmods-module-assistant-guide/</link>
      <pubDate>Sun, 24 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-24-self-hosted-linux-kernel-module-management-dkms-akmods-module-assistant-guide/</guid>
      <description>&lt;p&gt;When you install third-party kernel modules on a self-hosted Linux server — NVIDIA GPU drivers, VirtualBox guest additions, WireGuard out-of-tree modules, or custom hardware drivers — those modules must be rebuilt every time the kernel updates. Without automated module management, a routine &lt;code&gt;apt upgrade&lt;/code&gt; or &lt;code&gt;yum update&lt;/code&gt; can leave your server unable to load critical drivers until you manually recompile them.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
