<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Udev on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/udev/</link>
    <description>Recent content in Udev 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/udev/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Linux Device Management: systemd-udevd vs eudev vs mdev (2026)</title>
      <link>https://www.pistack.xyz/posts/2026-05-24-self-hosted-linux-device-management-systemd-udevd-vs-eudev-vs-mdev-guide/</link>
      <pubDate>Sun, 24 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-24-self-hosted-linux-device-management-systemd-udevd-vs-eudev-vs-mdev-guide/</guid>
      <description>&lt;p&gt;Linux device management is the unsung hero of every self-hosted infrastructure. When you plug in a USB drive, insert a PCIe card, or attach a network interface, the device manager is what creates the device nodes, sets permissions, and triggers the actions that make hardware usable. For self-hosted server administrators managing bare-metal infrastructure, homelab setups, or container hosts with GPU passthrough, choosing the right device management framework directly impacts system reliability, boot time, and device hot-plug behavior.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
