<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Hello Buggy]]></title><description><![CDATA[Hello Buggy]]></description><link>https://utsavlamichhane.com.np</link><generator>RSS for Node</generator><lastBuildDate>Mon, 13 Apr 2026 23:16:18 GMT</lastBuildDate><atom:link href="https://utsavlamichhane.com.np/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[📂 Understanding Linux File and Directory Properties]]></title><description><![CDATA[ls -l command
When you run the ls -l command in a Linux terminal, you get detailed information about the files and folders in your directory.
Here’s an example output:
drwxrwxr-x 3 utsav utsav 4096 मई 11 2024 build
drwxr-xr-x 22 utsav utsav 4096 अप्र...]]></description><link>https://utsavlamichhane.com.np/understanding-linux-file-and-directory-properties</link><guid isPermaLink="true">https://utsavlamichhane.com.np/understanding-linux-file-and-directory-properties</guid><category><![CDATA[Linux]]></category><category><![CDATA[file system]]></category><category><![CDATA[permissions]]></category><category><![CDATA[blog]]></category><category><![CDATA[#Linux #LinuxBlog #LinuxCommunity #OpenSource #FOSS #SysAdmin #DevOps #Programming #TechBlogger #LinuxGeek #LinuxTips #LinuxLife #LinuxLove #CommandLine #TechCommunity #LinuxWorld #Software #IT #Technology #GeekLife #OperatingSystem #Coding #LinuxUsers #TechTips #LinuxMatters #ITPro #LinuxServer #LinuxKernel #TechNews #TechUpdates #Blogging #LinuxSupport #LinuxGuru]]></category><dc:creator><![CDATA[Utsav Lamichhane]]></dc:creator><pubDate>Mon, 21 Apr 2025 18:15:00 GMT</pubDate><content:encoded><![CDATA[<hr />
<h3 id="heading-ls-l-command"><em>ls -l command</em></h3>
<p>When you run the <code>ls -l</code> command in a Linux terminal, you get detailed information about the files and folders in your directory.</p>
<p>Here’s an example output:</p>
<pre><code class="lang-bash">drwxrwxr-x 3 utsav utsav 4096 मई 11 2024 build
drwxr-xr-x 22 utsav utsav 4096 अप्रेल 26 23:11 Desktop
-rw-r--r-- 1 root    root    101639228 नवम्बर 25 23:25 discord-0.0.76.deb
drwxr-xr-x 9 utsav utsav 4096 अप्रेल 21 21:37 Documents
-rwxr-xr-x 1 root    root    62121 फरवरी 9 2024 dotnet-install.sh
drwxrwxr-x 2 utsav utsav 4096 फरवरी 11 2024 dotTraceSnapshots
drwxr-xr-x 15 utsav utsav 32768 अप्रेल 27 11:16 Downloads
</code></pre>
<p>Let’s see this in a proper tabluar form:</p>
<div class="hn-table">
<table>
<thead>
<tr>
<td><strong>File/Directory Permissions</strong></td><td><strong>Links</strong></td><td><strong>Owner</strong></td><td><strong>Group</strong></td><td><strong>Size (bytes)</strong></td><td><strong>Last Modified</strong></td><td><strong>Name</strong></td></tr>
</thead>
<tbody>
<tr>
<td>drwxrwxr-x</td><td>3</td><td>utsav</td><td>utsav</td><td>4096</td><td>मई 11 2024</td><td>build</td></tr>
<tr>
<td>drwxr-xr-x</td><td>22</td><td>utsav</td><td>utsav</td><td>4096</td><td>अप्रैल 26 23:11</td><td>Desktop</td></tr>
<tr>
<td>-rw-r--r--</td><td>1</td><td>root</td><td>root</td><td>101639228</td><td>नवम्बर 25 23:25</td><td>discord-0.0.76.deb</td></tr>
<tr>
<td>drwxr-xr-x</td><td>9</td><td>utsav</td><td>utsav</td><td>4096</td><td>अप्रैल 21 21:37</td><td>Documents</td></tr>
<tr>
<td>-rwxr-xr-x</td><td>1</td><td>root</td><td>root</td><td>62121</td><td>फरवरी 9 2024</td><td><a target="_blank" href="http://dotnet-install.sh">dotnet-install.sh</a></td></tr>
<tr>
<td>drwxrwxr-x</td><td>2</td><td>utsav</td><td>utsav</td><td>4096</td><td>फरवरी 11 2024</td><td>dotTraceSnapshots</td></tr>
</tbody>
</table>
</div><p>Let's break this down:</p>
<hr />
<h2 id="heading-what-each-column-means">🛠️ What Each Column Means</h2>
<div class="hn-table">
<table>
<thead>
<tr>
<td>Column</td><td>Meaning</td></tr>
</thead>
<tbody>
<tr>
<td>1</td><td>File type and permissions</td></tr>
<tr>
<td>2</td><td>Number of links (or subdirectories inside if a folder)</td></tr>
<tr>
<td>3</td><td>Owner/User (who owns the file)</td></tr>
<tr>
<td>4</td><td>Group (group the file belongs to)</td></tr>
<tr>
<td>5</td><td>File size (in bytes)</td></tr>
<tr>
<td>6, 7, 8</td><td>Last modified date and time</td></tr>
<tr>
<td>9</td><td>File or directory name</td></tr>
</tbody>
</table>
</div><hr />
<h2 id="heading-understanding-file-types">📌 Understanding File Types</h2>
<ul>
<li><p>If the first character is <code>d</code>, it’s a <strong>directory</strong> (folder).</p>
</li>
<li><p>If it’s <code>-</code>, it’s a <strong>regular file</strong>.</p>
</li>
<li><p>If it’s <code>l</code>, it’s a <strong>symbolic link</strong> (like a shortcut).</p>
</li>
</ul>
<blockquote>
<p><strong>Important:</strong><br />- You can only use the <code>cd</code> command (change directory) on directories (<code>d</code>).<br />- If you try <code>cd</code> on a regular file (<code>-</code>), you’ll get an error!</p>
<p>Example:</p>
<h3 id="heading-attempting-to-navigate-into-discord-0076deb">Attempting to Navigate into <code>discord-0.0.76.deb</code></h3>
<p>When you try to change into a file that is not a directory, such as the <code>.deb</code> file in this case, you will encounter an error. Here's the command and the resulting error:</p>
<pre><code class="lang-bash">$ <span class="hljs-built_in">cd</span> discord-0.0.76.deb
bash: <span class="hljs-built_in">cd</span>: discord-0.0.76.deb: Not a directory
</code></pre>
</blockquote>
<hr />
<h2 id="heading-permission-details-r-w-x">🔐 Permission Details (r, w, x)</h2>
<p>The first 10 characters represent <strong>permissions</strong>:</p>
<p>Example:</p>
<pre><code class="lang-plaintext">-rwxr-xr-x
</code></pre>
<p>Breakdown:</p>
<div class="hn-table">
<table>
<thead>
<tr>
<td>Set</td><td>Meaning</td></tr>
</thead>
<tbody>
<tr>
<td>1st character</td><td>File type (<code>-</code> for file, <code>d</code> for directory)</td></tr>
<tr>
<td>2-4</td><td>Owner permissions (e.g., <code>rwx</code> = read, write, execute)</td></tr>
<tr>
<td>5-7</td><td>Group permissions (e.g., <code>r-x</code> = read, execute)</td></tr>
<tr>
<td>8-10</td><td>Others permissions (e.g., <code>r-x</code> = read, execute)</td></tr>
</tbody>
</table>
</div><p><strong>Permission letters:</strong></p>
<ul>
<li><p><code>r</code> → Read</p>
</li>
<li><p><code>w</code> → Write</p>
</li>
<li><p><code>x</code> → Execute</p>
</li>
<li><p><code>-</code> → No permission</p>
</li>
</ul>
<hr />
<h2 id="heading-example-breaking-down-a-permission">🎯 Example: Breaking Down a Permission</h2>
<pre><code class="lang-plaintext">-rwxr-xr--
</code></pre>
<p>Means:</p>
<ul>
<li><p><strong>Owner</strong> can <strong>read</strong>, <strong>write</strong>, and <strong>execute</strong>.</p>
</li>
<li><p><strong>Group</strong> can <strong>read</strong> and <strong>execute</strong>, but <strong>not write</strong>.</p>
</li>
<li><p><strong>Others</strong> can <strong>read</strong> only.</p>
</li>
</ul>
<blockquote>
<p>📌 A user with <code>rwx</code> permissions can perform <strong>all CRUD operations</strong> (Create, Read, Update, Delete).</p>
</blockquote>
<hr />
<h2 id="heading-linux-vs-windows-a-simple-comparison">🖥️ Linux vs Windows: A Simple Comparison</h2>
<ul>
<li><p>In <strong>Linux</strong>, <code>ls -l</code> shows you file properties directly in the terminal.</p>
</li>
<li><p>In <strong>Windows</strong>, you <strong>right-click → Properties</strong> to see the same kind of info (like size, permissions, owner, etc.).</p>
</li>
</ul>
<hr />
<h1 id="heading-wrapping-up">🏁 Wrapping Up</h1>
<p>Understanding file types, ownership, and permissions is <strong>critical</strong> when working in Linux.<br />It helps you move safely between directories, manage files properly, and avoid common permission errors.</p>
<p>Next time you list files with <code>ls -l</code>, you’ll know exactly what each part means! 🐧</p>
<hr />
]]></content:encoded></item><item><title><![CDATA[How to Change Passwords and Understand Password Policies in Linux]]></title><description><![CDATA[Changing your password in Linux is a simple task — but behind the scenes, there are a few important rules and systems making sure your passwords stay strong and secure.In this blog post, we'll walk through how to change passwords, what happens when y...]]></description><link>https://utsavlamichhane.com.np/how-to-change-passwords-and-understand-password-policies-in-linux</link><guid isPermaLink="true">https://utsavlamichhane.com.np/how-to-change-passwords-and-understand-password-policies-in-linux</guid><category><![CDATA[ubu]]></category><category><![CDATA[passwords]]></category><category><![CDATA[#Security #Linux #PasswordManagement #CyberSecurity #TechTips #OpenSource]]></category><dc:creator><![CDATA[Utsav Lamichhane]]></dc:creator><pubDate>Mon, 21 Apr 2025 18:15:00 GMT</pubDate><content:encoded><![CDATA[<p>Changing your password in Linux is a simple task — but behind the scenes, there are a few important rules and systems making sure your passwords stay strong and secure.<br />In this blog post, we'll walk through how to change passwords, what happens when you pick a weak one, and where Linux keeps its password policies.</p>
<p>Let’s dive in!</p>
<h3 id="heading-changing-your-own-password">Changing Your Own Password</h3>
<p>If you want to update your own password, the process couldn't be easier.</p>
<p>Just open your terminal and run:</p>
<pre><code class="lang-bash">$ passwd
</code></pre>
<p>When you do this, Linux will:</p>
<ul>
<li><p>Ask you to enter your <strong>current password</strong>.</p>
</li>
<li><p>Then prompt you to type in your <strong>new password</strong>.</p>
</li>
<li><p>Finally, it will ask you to <strong>retype</strong> the new password to confirm.</p>
</li>
</ul>
<p>That’s it! Quick and secure.</p>
<h3 id="heading-changing-another-users-password">Changing Another User's Password</h3>
<p>If you’re logged in as <strong>root</strong> or have <strong>sudo</strong> privileges, you can also reset passwords for other users.</p>
<p>Use this command:</p>
<pre><code class="lang-bash">$ sudo passwd username
</code></pre>
<p>Just replace <code>username</code> with the actual username of the person you’re updating the password for.<br />You'll be prompted to enter the new password for them — no need to know their old one.</p>
<p>This is super handy for system administrators who need to reset forgotten passwords.</p>
<h3 id="heading-why-linux-complains-about-bad-passwords">Why Linux Complains About "Bad Passwords"</h3>
<p>These days, Linux systems are very strict about password strength.<br />If you try setting a simple password like <code>12345678</code>, you’ll get an error like this:</p>
<pre><code class="lang-bash">utsav@utsav:~$ passwd
Changing password <span class="hljs-keyword">for</span> utsav.
Current password:
BAD PASSWORD: The password fails the dictionary check - it is too simplistic/systematic
</code></pre>
<p>This happens because Linux is protecting you — it doesn’t want anyone guessing your password easily.</p>
<p>Most Linux systems expect your password to:</p>
<ul>
<li><p>Be at least <strong>8 characters</strong> long,</p>
</li>
<li><p>Include a mix of <strong>uppercase letters</strong>, <strong>lowercase letters</strong>, <strong>numbers</strong>, and <strong>special characters</strong>,</p>
</li>
<li><p>Avoid simple or dictionary-based words.</p>
</li>
</ul>
<p>Strong passwords are your first line of defense against unauthorized access!</p>
<h3 id="heading-where-linux-password-rules-are-set">Where Linux Password Rules Are Set</h3>
<p>You might be wondering: <strong>where are all these password rules coming from?</strong></p>
<p>Linux uses a few important configuration files to control password policies:</p>
<div class="hn-table">
<table>
<thead>
<tr>
<td>File</td><td>Purpose</td></tr>
</thead>
<tbody>
<tr>
<td><code>/etc/login.defs</code></td><td>Sets basic password behavior like minimum length and expiration policies.</td></tr>
<tr>
<td><code>/etc/pam.d/common-password</code></td><td>Applies password complexity requirements using PAM (Pluggable Authentication Modules).</td></tr>
<tr>
<td><code>/etc/security/pwquality.conf</code></td><td>Allows detailed control over password strength requirements.</td></tr>
</tbody>
</table>
</div><p>Each of these files plays a role in making sure users pick strong, secure passwords.</p>
<h3 id="heading-customizing-password-policies">Customizing Password Policies</h3>
<p>If you're a system administrator, you might want to tighten (or loosen) your system’s password rules.<br />You can do this by editing the <code>/etc/security/pwquality.conf</code> file.</p>
<p>Here's an example of what you might see inside:</p>
<pre><code class="lang-bash">minlen = 8
minclass = 3
maxrepeat = 2
</code></pre>
<p>What these settings mean:</p>
<ul>
<li><p><code>minlen = 8</code>: Passwords must be at least 8 characters long.</p>
</li>
<li><p><code>minclass = 3</code>: Passwords must contain characters from at least three different classes (like uppercase, lowercase, digits, symbols).</p>
</li>
<li><p><code>maxrepeat = 2</code>: No more than two of the same character in a row.</p>
</li>
</ul>
<p>To edit the file, you can use:</p>
<pre><code class="lang-bash">$ sudo nano /etc/security/pwquality.conf
</code></pre>
<p>Make your changes, save the file, and your new policies will be enforced immediately.</p>
<h3 id="heading-final-thoughts">Final Thoughts</h3>
<p>Keeping your passwords strong on Linux isn’t just a good habit — it’s one of the best ways to keep your system safe.<br />A tough, complex password (plus a few smart rules) can protect you from hackers, mistakes, and all kinds of trouble.</p>
<p>The more you know about how Linux handles password changes and security, the better (and more confident) you’ll be — whether you're just using your system or running the whole show.</p>
<p>So next time you’re picking a new password, take a few extra seconds to make it strong. It’s a small thing that makes a <em>huge</em> difference!</p>
]]></content:encoded></item><item><title><![CDATA[🐧 Diving Into the Linux Filesystem Structure]]></title><description><![CDATA[If you’ve just started exploring Linux, you’ve probably run into a bunch of folders with weird names like /etc, /var, or /usr. At first glance, it might look confusing — even intimidating — but once you understand the structure, it all starts to make...]]></description><link>https://utsavlamichhane.com.np/diving-into-the-linux-filesystem-structure</link><guid isPermaLink="true">https://utsavlamichhane.com.np/diving-into-the-linux-filesystem-structure</guid><category><![CDATA[Linux]]></category><category><![CDATA[file system]]></category><category><![CDATA[operating system]]></category><category><![CDATA[os]]></category><category><![CDATA[Ubuntu]]></category><category><![CDATA[debian]]></category><dc:creator><![CDATA[Utsav Lamichhane]]></dc:creator><pubDate>Mon, 21 Apr 2025 06:17:27 GMT</pubDate><content:encoded><![CDATA[<p>If you’ve just started exploring Linux, you’ve probably run into a bunch of folders with weird names like <code>/etc</code>, <code>/var</code>, or <code>/usr</code>. At first glance, it might look confusing — even intimidating — but once you understand the structure, it all starts to make sense.</p>
<p>This post is here to break it down for you in a simple, friendly way. By the end, you'll know your way around the Linux filesystem like a local.</p>
<hr />
<h2 id="heading-so-whats-the-linux-filesystem-anyway">📁 So, What’s the Linux Filesystem Anyway?</h2>
<p>In Linux, everything lives under a single directory: <code>/</code>, known as the <strong>root directory</strong> (not to be confused with the root <em>user</em>). It’s kind of like the trunk of a tree. All other directories branch out from it.</p>
<p>Unlike Windows, which uses drive letters like <code>C:\</code> or <code>D:\</code>, Linux uses one unified directory tree — your hard drive, USBs, system files, everything gets “mounted” into this tree somewhere.</p>
<hr />
<h2 id="heading-the-filesystem-tree-with-real-world-analogies">🌳 The Filesystem Tree (With Real-World Analogies)</h2>
<p>Here’s a rundown of the key directories you’ll find in Linux, along with a bit of what they’re for. I’ll keep the tech talk light and sprinkle in a few analogies to make it stick.</p>
<div class="hn-table">
<table>
<thead>
<tr>
<td>Directory</td><td>What It’s For</td></tr>
</thead>
<tbody>
<tr>
<td><code>/</code></td><td>The <strong>root</strong> of it all. Everything on your system starts here.</td></tr>
<tr>
<td><code>/bin</code>or <code>/usr/bin</code></td><td>Essential <strong>user commands</strong> like <code>ls</code>, <code>cp</code>, and <code>rm</code>. If something breaks here, you're in trouble.</td></tr>
<tr>
<td><code>/boot</code></td><td>All the files needed to <strong>boot up your system</strong>, including the Linux kernel.</td></tr>
<tr>
<td><code>/dev</code></td><td>Represents your <strong>devices</strong>. Disks, USBs, even your mouse — all show up as files here.</td></tr>
<tr>
<td><code>/etc</code></td><td>System <strong>configuration files</strong> live here. If <code>/etc</code> was a room, it’d be the server closet full of switches and settings.</td></tr>
<tr>
<td><code>/home</code></td><td>This is where <strong>your stuff</strong> goes. Every user gets a personal directory, like <code>/home/utsav</code></td></tr>
<tr>
<td><code>/lib</code> or <code>/usr/lib</code></td><td>Shared <strong>libraries</strong> that help software run. Like C standard Library files needed by commands and application</td></tr>
<tr>
<td><code>/media</code></td><td>When you plug in a USB stick or insert a CD, it gets mounted here.</td></tr>
<tr>
<td><code>/mnt</code></td><td>A generic <strong>mount point</strong> — used mostly by system admins for mounting extra stuff manually. Mounts external file system</td></tr>
<tr>
<td><code>/opt</code></td><td><strong>Optional software or add-on applications</strong> lives here — stuff that isn’t part of the core OS.</td></tr>
<tr>
<td><code>/proc</code></td><td>A strange one — it's a <strong>virtual filesystem</strong> that gives you info about running processes and the kernel, processes that only exist in the memory.</td></tr>
<tr>
<td><code>/root</code></td><td>The <strong>home directory of the root user</strong> (i.e., the system's superadmin). It is not the same as <code>/</code></td></tr>
<tr>
<td><code>/run</code></td><td>Stores temporary runtime data for system processes and daemons that start very early in the boot process — like <code>systemd</code> and <code>udevd</code>. It holds things like PID files, sockets, and other state information needed while the system is running.</td></tr>
<tr>
<td><code>/sbin</code></td><td>Similar to <code>/bin</code>, but specifically for <strong>system binaries</strong> used by admins.</td></tr>
<tr>
<td><code>/srv</code></td><td>Data for <strong>services</strong> like web or FTP servers. Kind of like <code>/var</code>, but service-specific.</td></tr>
<tr>
<td><code>/sys</code></td><td>Another <strong>virtual filesystem</strong> that gives info about hardware and kernel modules.</td></tr>
<tr>
<td><code>/tmp</code></td><td>A place for <strong>temporary files</strong>. Gets cleaned up automatically. Think of it as a scratchpad.</td></tr>
<tr>
<td><code>/usr</code></td><td>Short for “Unix System Resources” — basically where most of the <strong>user-installed software</strong> lives.</td></tr>
<tr>
<td><code>/var</code></td><td>Stands for <strong>variable</strong> — because this data changes often. Logs, emails, and such go here.</td></tr>
</tbody>
</table>
</div><hr />
<h2 id="heading-think-of-it-like-a-house">🧠 Think of It Like a House</h2>
<p>If the Linux filesystem was your house:</p>
<ul>
<li><p><code>/</code> is the front door.</p>
</li>
<li><p><code>/home</code> is your bedroom.</p>
</li>
<li><p><code>/etc</code> is the electrical panel — full of wires and switches.</p>
</li>
<li><p><code>/bin</code> and <code>/sbin</code> are your toolboxes.</p>
</li>
<li><p><code>/tmp</code> is the sticky note on your fridge.</p>
</li>
<li><p><code>/dev</code> is your collection of power outlets connected to devices.</p>
</li>
<li><p><code>/var/log</code> is your diary — it records everything.</p>
</li>
</ul>
<hr />
<hr />
<h2 id="heading-wrapping-up">✨ Wrapping Up</h2>
<p>The Linux filesystem might seem intimidating at first glance, but it’s actually pretty logical once you break it down. Everything has its place and purpose. Bookmark this post, explore a bit using <code>cd</code>, <code>ls</code>, and <code>tree</code>, and don’t be afraid to poke around (carefully!).</p>
<p>Got questions? Drop them in the comments — or let me know if you'd like a deeper dive into any of the folders we covered.</p>
<p>Happy exploring! 🐧</p>
]]></content:encoded></item><item><title><![CDATA[What Is Root in Linux?]]></title><description><![CDATA[🌱 What Is Root in Linux—3 Different Meanings
As someone who may be new to Linux, you're going to hear the word "root" countless times. However, it doesn't always mean the same thing. Depending on the context, "root" can mean very different (but rela...]]></description><link>https://utsavlamichhane.com.np/what-is-root-in-linux</link><guid isPermaLink="true">https://utsavlamichhane.com.np/what-is-root-in-linux</guid><category><![CDATA[terminal]]></category><category><![CDATA[Ubuntu]]></category><category><![CDATA[sudo]]></category><category><![CDATA[Root User]]></category><category><![CDATA[root user, sudo-su, su]]></category><dc:creator><![CDATA[Utsav Lamichhane]]></dc:creator><pubDate>Sat, 19 Apr 2025 18:15:00 GMT</pubDate><content:encoded><![CDATA[<hr />
<h2 id="heading-what-is-root-in-linux3-different-meanings">🌱 What Is Root in Linux—3 Different Meanings</h2>
<p>As someone who may be new to Linux, you're going to hear the word <strong>"root"</strong> countless times. However, it doesn't always mean the same thing. Depending on the context, "root" can mean very different (but related) things.</p>
<p>This blog post breaks it down into <strong>three major meanings</strong> of "root" within a Linux system — with clear examples to make it click 💡.</p>
<hr />
<h3 id="heading-1-root-user-superuser-account">1️⃣ Root User (Superuser Account)</h3>
<p>The <strong>root account</strong> is the most powerful user in a Linux system. This user has <strong>unrestricted access</strong> to all commands and files and can perform any administrative operation — including ones that can break the system!</p>
<p>It’s basically the <strong>superuser</strong> of the Linux world.</p>
<h4 id="heading-example">🔧 Example</h4>
<p>Say you're a regular user trying to install software:</p>
<pre><code class="lang-bash">apt install nginx
</code></pre>
<p>This might give you a permissions error. But run it as root:</p>
<pre><code class="lang-bash">sudo apt install nginx
</code></pre>
<p>Boom — it works! That's because <code>sudo</code> lets you run commands as the root user.</p>
<blockquote>
<p>🛑 <strong>Warning:</strong> Be very careful when using root or <code>sudo</code>. A single typo can mess up your entire system!</p>
</blockquote>
<hr />
<h3 id="heading-2-root-directory">2️⃣ Root Directory (<code>/</code>)</h3>
<p>In the Linux file system, everything starts from a single top-level directory called the <strong>root directory</strong>, represented by just a <strong>forward slash</strong> <code>/</code>.</p>
<p>It’s the <strong>base of the entire file system tree</strong> — every other file and folder is nested inside this root.</p>
<h4 id="heading-example-1">📂 Example</h4>
<p>Here’s a simplified view of a typical root directory:</p>
<pre><code class="lang-bash">/
├── bin
├── etc
├── home
├── root
├── usr
└── var
</code></pre>
<p>So when someone says “from the root directory,” they mean from <code>/</code>.</p>
<blockquote>
<p>❗ Don’t confuse this with the root <strong>user</strong> — this is about file system structure.</p>
</blockquote>
<hr />
<h3 id="heading-3-roots-home-directory-root">3️⃣ Root’s Home Directory (<code>/root</code>)</h3>
<p>Just like every user has their own home directory (e.g., <code>/home/utsav</code> for the user <code>utsav</code>), the <strong>root user</strong> has one too.</p>
<p>But instead of being in <code>/home</code>, it's located at:</p>
<pre><code class="lang-bash">/root
</code></pre>
<p>This directory is private to the root user and holds its configuration files, scripts, and personal data.</p>
<h4 id="heading-example-2">📂 Example</h4>
<p>If you're the root user, you can access your home with:</p>
<pre><code class="lang-bash"><span class="hljs-built_in">cd</span> /root
ls -a
</code></pre>
<p>You'll likely see hidden files like <code>.bashrc</code> or <code>.profile</code> — just like in any user's home.</p>
<hr />
<h2 id="heading-summary">🧠 Summary</h2>
<p>Here’s a quick recap of the 3 meanings of “root” in Linux:</p>
<div class="hn-table">
<table>
<thead>
<tr>
<td>Term</td><td>Meaning</td></tr>
</thead>
<tbody>
<tr>
<td><strong>Root User</strong></td><td>The superuser with full system privileges.</td></tr>
<tr>
<td><strong>Root Directory (</strong><code>/</code>)</td><td>The top-level directory of the Linux file system.</td></tr>
<tr>
<td><strong>Root Home Directory</strong></td><td>The root user’s personal folder, found at <code>/root</code>.</td></tr>
</tbody>
</table>
</div><hr />
<p>So next time someone says “run it as root” or “check from root,” you’ll know exactly what they mean — context is everything!</p>
<p>Have a happy terminal-ing! 🔥</p>
]]></content:encoded></item></channel></rss>