<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Storage on ShieldedBytes</title>
    <link>https://linuxeries.org/tags/storage/</link>
    <description>Recent content in Storage on ShieldedBytes</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 18 Jun 2026 10:47:30 +0200</lastBuildDate>
    <atom:link href="https://linuxeries.org/tags/storage/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Taming Wild Directories: Mastering Setgid, Sticky Bits, and ACLs for Shared Storage</title>
      <link>https://linuxeries.org/post/2026-06-18-taming-wild-directories-mastering-setgid-stic/</link>
      <pubDate>Thu, 18 Jun 2026 10:47:30 +0200</pubDate>
      <guid>https://linuxeries.org/post/2026-06-18-taming-wild-directories-mastering-setgid-stic/</guid>
      <description>&lt;h2 id=&#34;introduction-to-shared-storage&#34;&gt;Introduction to Shared Storage&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve seen this go wrong when teams don&amp;rsquo;t manage permissions and access control properly - it&amp;rsquo;s a recipe for data breaches and collaboration headaches. When working with shared storage in Linux, it&amp;rsquo;s crucial to understand setgid, sticky bits, and ACLs (Access Control Lists). These tools can help you master shared storage and keep your data safe.&lt;/p&gt;&#xA;&lt;h2 id=&#34;setgid-and-sticky-bits&#34;&gt;Setgid and Sticky Bits&lt;/h2&gt;&#xA;&lt;p&gt;The real trick is to use setgid and sticky bits to control the behavior of files and subdirectories within a directory. Setgid, when set on a directory, ensures that all new files created within that directory inherit the group ownership of the directory. This is particularly useful in shared storage scenarios where multiple users need to collaborate on files. To set the setgid bit on a directory, use the following command:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
