<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Linux on XSAH | Practical Journey to DevOps</title><link>https://xsah.ir/topics/linux/</link><description>Recent content in Linux on XSAH | Practical Journey to DevOps</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 All rights reserved.</copyright><lastBuildDate>Tue, 08 Sep 2026 20:50:32 +0330</lastBuildDate><atom:link href="https://xsah.ir/topics/linux/index.xml" rel="self" type="application/rss+xml"/><item><title>Linux Foundations: Connecting the Pieces</title><link>https://xsah.ir/posts/linux-foundation-pieces/</link><pubDate>Tue, 08 Sep 2026 20:50:32 +0330</pubDate><guid>https://xsah.ir/posts/linux-foundation-pieces/</guid><description>&lt;h2 class="relative group"&gt;Introduction&#10; &lt;div id="introduction" class="anchor"&gt;&lt;/div&gt;&#10; &#10;&lt;/h2&gt;&#10;&lt;p&gt;Learning Linux is not just about learning commands. It is easy to learn how to run &lt;code&gt;ls&lt;/code&gt;, &lt;code&gt;mount&lt;/code&gt;, &lt;code&gt;chmod&lt;/code&gt;, &lt;code&gt;ps&lt;/code&gt;, or &lt;code&gt;systemctl&lt;/code&gt; individually. The more important step is understanding how these commands relate to the system underneath them.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://xsah.ir/posts/linux-foundation-pieces/featured.jpg"/></item><item><title>Understanding Linux Processes and System Monitoring</title><link>https://xsah.ir/posts/linux-processes-monitoring/</link><pubDate>Sun, 06 Sep 2026 19:42:35 +0330</pubDate><guid>https://xsah.ir/posts/linux-processes-monitoring/</guid><description>&lt;h2 class="relative group"&gt;Introduction&#10; &lt;div id="introduction" class="anchor"&gt;&lt;/div&gt;&#10; &#10;&lt;/h2&gt;&#10;&lt;p&gt;A Linux system is constantly running programs in the background.&lt;/p&gt;&#10;&lt;p&gt;From system services and daemons to shells and user applications, each running program needs CPU time, memory, and other system resources. Linux manages these running instances as &lt;strong&gt;processes&lt;/strong&gt;.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://xsah.ir/posts/linux-processes-monitoring/featured.jpg"/></item><item><title>From UEFI/BIOS to GRUB: Understanding the Linux Boot Process</title><link>https://xsah.ir/posts/linux-boot-process/</link><pubDate>Sat, 05 Sep 2026 12:17:32 +0330</pubDate><guid>https://xsah.ir/posts/linux-boot-process/</guid><description>&lt;h2 class="relative group"&gt;Introduction&#10; &lt;div id="introduction" class="anchor"&gt;&lt;/div&gt;&#10; &#10;&lt;/h2&gt;&#10;&lt;p&gt;When a Linux system starts, several components work together before the first login prompt or graphical desktop appears.&lt;/p&gt;&#10;&lt;p&gt;The process begins with system firmware, continues through a bootloader, loads the Linux kernel and its initial userspace environment, and eventually hands control to &lt;code&gt;systemd&lt;/code&gt; and the services it manages.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://xsah.ir/posts/linux-boot-process/featured.jpg"/></item><item><title>Linux Permissions, Ownership and umask</title><link>https://xsah.ir/posts/linux-permissions/</link><pubDate>Fri, 04 Sep 2026 19:47:28 +0330</pubDate><guid>https://xsah.ir/posts/linux-permissions/</guid><description>&lt;h2 class="relative group"&gt;Introduction&#10; &lt;div id="introduction" class="anchor"&gt;&lt;/div&gt;&#10; &#10;&lt;/h2&gt;&#10;&lt;p&gt;Linux is a multi-user operating system, so it needs a way to control who can access files and directories and what they can do with them.&lt;/p&gt;&#10;&lt;p&gt;Permissions and ownership provide this basic access-control mechanism. They determine whether a user can read, modify, or execute a file, as well as whether they can access the contents of a directory.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://xsah.ir/posts/linux-permissions/featured.jpg"/></item><item><title>Inodes, Hard Links and Symbolic Links</title><link>https://xsah.ir/posts/linux-inodes-links/</link><pubDate>Thu, 03 Sep 2026 17:59:30 +0330</pubDate><guid>https://xsah.ir/posts/linux-inodes-links/</guid><description>&lt;h2 class="relative group"&gt;Introduction&#10; &lt;div id="introduction" class="anchor"&gt;&lt;/div&gt;&#10; &#10;&lt;/h2&gt;&#10;&lt;p&gt;When you work with files in Linux, you normally interact with names such as &lt;code&gt;config.txt&lt;/code&gt; or &lt;code&gt;/var/log/syslog&lt;/code&gt;. But underneath the filesystem hierarchy, Linux uses another layer of information to identify and manage the actual filesystem objects.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://xsah.ir/posts/linux-inodes-links/featured.jpg"/></item><item><title>Mounting Filesystems and /etc/fstab</title><link>https://xsah.ir/posts/linux-mount-fstab/</link><pubDate>Wed, 02 Sep 2026 15:17:24 +0330</pubDate><guid>https://xsah.ir/posts/linux-mount-fstab/</guid><description>&lt;h2 class="relative group"&gt;Introduction&#10; &lt;div id="introduction" class="anchor"&gt;&lt;/div&gt;&#10; &#10;&lt;/h2&gt;&#10;&lt;p&gt;&lt;a href="https://xsah.ir/posts/linux-filesystem/" &gt;&lt;strong&gt;Understanding the Linux filesystem&lt;/strong&gt;&lt;/a&gt; hierarchy is only the first step. Knowing where directories such as &lt;code&gt;/&lt;/code&gt;, &lt;code&gt;/etc&lt;/code&gt;, &lt;code&gt;/var&lt;/code&gt;, and &lt;code&gt;/home&lt;/code&gt; are located does not yet explain how the storage behind that hierarchy is actually connected.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://xsah.ir/posts/linux-mount-fstab/featured.jpg"/></item><item><title>Understanding the Linux Filesystem</title><link>https://xsah.ir/posts/linux-filesystem/</link><pubDate>Tue, 01 Sep 2026 11:56:13 +0330</pubDate><guid>https://xsah.ir/posts/linux-filesystem/</guid><description>&lt;h2 class="relative group"&gt;Introduction&#10; &lt;div id="introduction" class="anchor"&gt;&lt;/div&gt;&#10; &#10;&lt;/h2&gt;&#10;&lt;p&gt;One of the first things to understand when working seriously with Linux is how its filesystem is organized.&lt;/p&gt;&#10;&lt;p&gt;At first, the Linux filesystem can look like a collection of directories with familiar names such as &lt;code&gt;/etc&lt;/code&gt;, &lt;code&gt;/var&lt;/code&gt;, &lt;code&gt;/home&lt;/code&gt;, and &lt;code&gt;/tmp&lt;/code&gt;. But these directories are not arbitrary. Each one has a specific role, and understanding that role becomes increasingly important as we move from basic Linux administration toward DevOps.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://xsah.ir/posts/linux-filesystem/featured.jpg"/></item></channel></rss>