<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Udisks on Linux Café</title>
    <link>https://mrtomlinux.org/tags/udisks/</link>
    <description>Recent content in Udisks on Linux Café</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 30 May 2026 10:15:43 +0200</lastBuildDate>
    <atom:link href="https://mrtomlinux.org/tags/udisks/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Taming Removable Device Chaos: Automatically Mounting and Naming Disks on Desktop Linux</title>
      <link>https://mrtomlinux.org/post/2026-05-30-taming-removable-device-chaos-automatically-m/</link>
      <pubDate>Sat, 30 May 2026 10:15:43 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-05-30-taming-removable-device-chaos-automatically-m/</guid>
      <description>&lt;h2 id=&#34;introduction-to-removable-device-chaos&#34;&gt;Introduction to Removable Device Chaos&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve lost count of how many times I&amp;rsquo;ve struggled with removable devices on my Linux desktop. Whether it&amp;rsquo;s a USB drive, an SD card, or an external hard drive, these devices can be a real hassle to manage. The problem usually starts when you plug in a device and your system assigns it a cryptic device file in the &lt;code&gt;/dev&lt;/code&gt; directory. For example, a USB drive might become &lt;code&gt;/dev/sdb1&lt;/code&gt;. Not exactly user-friendly, right?&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
