<?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 Linux Café</title>
    <link>https://mrtomlinux.org/tags/udev/</link>
    <description>Recent content in Udev on Linux Café</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 12 Jun 2026 08:51:43 +0200</lastBuildDate>
    <atom:link href="https://mrtomlinux.org/tags/udev/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Taming the Chaos of Removable Device Mounting in Desktop Linux</title>
      <link>https://mrtomlinux.org/post/2026-06-12-taming-the-chaos-of-removable-device-mounting/</link>
      <pubDate>Fri, 12 Jun 2026 08:51:43 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-06-12-taming-the-chaos-of-removable-device-mounting/</guid>
      <description>&lt;h2 id=&#34;introduction-to-removable-device-mounting&#34;&gt;Introduction to Removable Device Mounting&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve seen this go wrong when dealing with multiple removable devices and various file systems - it can get chaotic. As a Linux user, you&amp;rsquo;re likely familiar with the convenience of removable devices like USB drives and SD cards. To manage these devices effectively, you need to understand how &lt;code&gt;udev&lt;/code&gt; and &lt;code&gt;systemd&lt;/code&gt; work together.&lt;/p&gt;&#xA;&lt;h2 id=&#34;understanding-udev-and-systemd&#34;&gt;Understanding udev and systemd&lt;/h2&gt;&#xA;&lt;p&gt;The real trick is to grasp the roles of &lt;code&gt;udev&lt;/code&gt; and &lt;code&gt;systemd&lt;/code&gt;. &lt;code&gt;udev&lt;/code&gt; handles device events, such as device insertion and removal, while &lt;code&gt;systemd&lt;/code&gt; manages system services and devices. When a removable device is inserted, &lt;code&gt;udev&lt;/code&gt; generates an event, which is then handled by &lt;code&gt;systemd&lt;/code&gt;. By default, &lt;code&gt;systemd&lt;/code&gt; mounts removable devices under the &lt;code&gt;/media&lt;/code&gt; directory. You can verify the current mount points using the &lt;code&gt;findmnt&lt;/code&gt; command:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Taming the Chaos of External Drives on Desktop Linux with Udev Rules and Automounting</title>
      <link>https://mrtomlinux.org/post/2026-05-16-taming-the-chaos-of-external-drives-on-deskto/</link>
      <pubDate>Sat, 16 May 2026 08:15:18 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-05-16-taming-the-chaos-of-external-drives-on-deskto/</guid>
      <description>&lt;h2 id=&#34;introduction-to-external-drive-management&#34;&gt;Introduction to External Drive Management&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve been using Linux for years, and one thing that&amp;rsquo;s always been a bit of a pain is managing external drives. Whether it&amp;rsquo;s a USB flash drive, an external hard drive, or an SSD, keeping track of these devices can be a chore. I&amp;rsquo;ve seen this go wrong when you&amp;rsquo;ve got multiple drives connected and you&amp;rsquo;re not sure which one is which. In practice, this can lead to a lot of confusion and wasted time. That&amp;rsquo;s why I&amp;rsquo;ve started using udev rules and automounting to manage my external drives.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
