<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Shared-Directories on ShieldedBytes</title>
    <link>https://linuxeries.org/tags/shared-directories/</link>
    <description>Recent content in Shared-Directories on ShieldedBytes</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 23 May 2026 11:24:31 +0200</lastBuildDate>
    <atom:link href="https://linuxeries.org/tags/shared-directories/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Taming the Chaos of Shared Directories with Setgid and Sticky Bits</title>
      <link>https://linuxeries.org/post/2026-05-23-taming-the-chaos-of-shared-directories-with-s/</link>
      <pubDate>Sat, 23 May 2026 11:24:31 +0200</pubDate>
      <guid>https://linuxeries.org/post/2026-05-23-taming-the-chaos-of-shared-directories-with-s/</guid>
      <description>&lt;h2 id=&#34;introduction-to-shared-directories&#34;&gt;Introduction to Shared Directories&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve seen this go wrong when multiple users are working on the same project - files get overwritten or deleted unintentionally. To avoid this chaos, Linux provides two useful features: setgid and sticky bits. These permissions can help you manage shared directories and prevent unwanted changes to files.&lt;/p&gt;&#xA;&lt;h2 id=&#34;setgid-bit&#34;&gt;Setgid Bit&lt;/h2&gt;&#xA;&lt;p&gt;The real trick is to ensure that all files within a shared directory are owned by the same group. This is where the setgid bit comes in - it&amp;rsquo;s a special permission that can be applied to a directory. When a directory has the setgid bit set, any new files created within that directory will inherit the group ownership of the directory. To set the setgid bit on a directory, you can use the &lt;code&gt;chmod&lt;/code&gt; command:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
