<?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" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by R3d1n1t on Medium]]></title>
        <description><![CDATA[Stories by R3d1n1t on Medium]]></description>
        <link>https://medium.com/@r3d1n1t?source=rss-e1defcaba618------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Stories by R3d1n1t on Medium</title>
            <link>https://medium.com/@r3d1n1t?source=rss-e1defcaba618------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 21:41:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@r3d1n1t/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Understanding Linux Processes: My Hands-on Learning Journey]]></title>
            <link>https://r3d1n1t.medium.com/understanding-linux-processes-my-hands-on-learning-journey-3fa340072f25?source=rss-e1defcaba618------2</link>
            <guid isPermaLink="false">https://medium.com/p/3fa340072f25</guid>
            <category><![CDATA[linux-security]]></category>
            <category><![CDATA[sysadmin]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[security-operation-center]]></category>
            <category><![CDATA[linux]]></category>
            <dc:creator><![CDATA[R3d1n1t]]></dc:creator>
            <pubDate>Tue, 10 Nov 2026 07:52:03 GMT</pubDate>
            <atom:updated>2026-11-10T07:52:03.947Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>Linux processes are one of the fundamental concepts I wanted to understand while building my Linux and cybersecurity foundations.</p><p>Rather than simply memorizing commands, I decided to explore how Linux handles processes, how processes relate to each other, and how we can observe their behaviour through the terminal.</p><p>In this article, I’ll share my practical learning experience with Linux processes, including the commands I used, the observations I made, and the concepts I understood along the way.</p><h3>1. What is a Process?</h3><p>Before exploring processes, I wanted to understand the difference between a program and a process.</p><p>A <strong>program</strong> is a set of instructions stored on a system, usually as an executable file.</p><p>A <strong>process</strong> is a running instance of a program.</p><p>For example, when I execute:</p><pre>sleep 300</pre><p>Linux creates a process that waits for 300 seconds before completing.</p><p>This helped me understand that a program is something stored on the system, whereas a process represents its execution.</p><h3>2. Exploring Running Processes</h3><p>Linux provides several commands to observe processes.</p><p>I started with the ps command.</p><pre>ps</pre><p>This displays processes associated with the current terminal.</p><p>Next, I explored:</p><pre>ps -f</pre><p>This provides a fuller process listing, including information such as the process ID and parent process ID.</p><p>Finally:</p><pre>ps aux</pre><p>This displays a broad snapshot of processes running on the system.</p><p>Some important fields in its output include:</p><ul><li><strong>USER:</strong> User associated with the process.</li><li><strong>PID:</strong> Process ID.</li><li><strong>%CPU:</strong> CPU usage.</li><li><strong>%MEM:</strong> Memory usage.</li><li><strong>STAT:</strong> Process state.</li><li><strong>COMMAND:</strong> Command associated with the process.</li></ul><p>One important thing I learned is that ps provides a snapshot rather than continuously monitoring processes.</p><h3>3. Understanding PID and PPID</h3><p>Every Linux process has a Process ID (PID).</p><p>A process also has a Parent Process ID (PPID), which identifies its parent process.</p><p>To understand this relationship practically, I executed:</p><pre>sleep 300 &amp;</pre><p>Then I inspected the process:</p><pre>ps -f</pre><p>My terminal showed:</p><pre>UID   PID   PPID  C  STIME  TTY    TIME      CMD<br>red   1378  1358  0  ...    pts/0  00:00:00  bash<br>red   1871  1378  0  ...    pts/0  00:00:00  sleep 300</pre><p>Here:</p><ul><li>The Bash process had PID 1378.</li><li>The sleep process had PID 1871.</li><li>The sleep process had PPID 1378.</li></ul><p>This means Bash started the sleep process.</p><p>I understood that processes can have parent-child relationships, and examining these relationships can help us understand how processes are started.</p><p>This is also useful in security investigations, where process ancestry can provide important context about suspicious activity.</p><h3>4. Understanding Linux Process States</h3><p>A process does not continuously execute instructions on the CPU. It can enter different states during its lifetime.</p><p>I explored the STAT column using:</p><pre>ps -o pid,ppid,user,stat,cmd -p 1871</pre><p>Here are the common Linux process states I learned:</p><ul><li>R : Running or runnable</li><li>S : Interruptible sleep</li><li>D : Uninterruptible sleep</li><li>T : Stopped or traced</li><li>Z : Zombie</li></ul><h3>Understanding the S state practically</h3><p>When I executed:</p><pre>sleep 300 &amp;</pre><p>I observed:</p><pre>PID    PPID   USER   STAT   CMD<br>1871   1378   red    S      sleep 300</pre><p>The process was in the S state, meaning it was in interruptible sleep.</p><p>Why?</p><p>The sleep command was waiting for its requested time interval to expire.</p><p>This helped me understand an important concept:</p><p>A sleeping process has not terminated. It still has a PID and occupies system resources, but it does not need to continuously consume CPU time while waiting.</p><p>I also learned that S and D represent different types of waiting.</p><h3>5. Foreground vs. Background Processes</h3><p>Another important concept I explored was foreground and background execution.</p><h3>Foreground execution</h3><p>I executed:</p><pre>sleep 30</pre><p>The terminal waited for the command to finish before returning the shell prompt.</p><p>During that time, I couldn’t enter another command in the same terminal session.</p><h3>Background execution</h3><p>Next, I executed:</p><pre>sleep 300 &amp;</pre><p>The &amp; operator starts the command as a background job.</p><p>The shell immediately returned the prompt, allowing me to execute other commands while the sleep process continued running.</p><p>I also explored:</p><pre>jobs</pre><p>This displays jobs managed by the current shell.</p><p>I compared it with:</p><pre>ps -f</pre><p>This helped me understand the difference between a process and a shell job.</p><p>A process is a running instance of a program managed by the Linux kernel.</p><p>A shell job is a command or pipeline managed by the shell’s job-control mechanism. A single job can contain multiple processes.</p><p>One important distinction I learned is that foreground/background execution is different from process states.</p><p>A background process can still be in the R or S state, for example.</p><h3>6. What I Learned</h3><p>Through these practical exercises, I developed an initial understanding of:</p><ol><li>The difference between programs and processes.</li><li>How to list processes using ps.</li><li>How PID and PPID identify process relationships.</li><li>How to identify common process states.</li><li>Why a sleeping process does not continuously consume CPU.</li><li>The difference between foreground and background execution.</li><li>The difference between a Linux process and a shell job.</li></ol><p>These concepts gave me a better starting point for understanding how Linux manages running programs.</p><h3>7. What’s Next?</h3><p>Understanding process fundamentals is only the beginning.</p><p>My next learning phase is Linux Process Control, where I’ll explore:</p><ul><li>What signals are.</li><li>SIGTERM and SIGKILL.</li><li>The kill command.</li><li>Managing and terminating processes.</li><li>Process priorities using nice and renice.</li></ul><p>Eventually, I want to combine these concepts with practical process investigation from a SOC analyst’s perspective.</p><h3>Conclusion</h3><p>Learning Linux is not just about knowing commands. I want to understand what happens behind those commands and why the operating system behaves the way it does.</p><p>Working through these small experiments helped me move beyond simply reading documentation and start observing Linux behaviour directly.</p><p>This is one step in my ongoing journey of learning Linux and cybersecurity through practical work.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3fa340072f25" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Linux User & Group Management]]></title>
            <link>https://r3d1n1t.medium.com/linux-user-group-management-7fb5d43bad88?source=rss-e1defcaba618------2</link>
            <guid isPermaLink="false">https://medium.com/p/7fb5d43bad88</guid>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[linux-tutorial]]></category>
            <category><![CDATA[linux-commands]]></category>
            <dc:creator><![CDATA[R3d1n1t]]></dc:creator>
            <pubDate>Sun, 04 Jan 2026 14:22:07 GMT</pubDate>
            <atom:updated>2026-01-04T14:22:07.228Z</atom:updated>
            <content:encoded><![CDATA[<p>User and group management is a fundamental part of Linux system administration. It is used to control access, manage permissions, and organize users within a Linux system. In this blog, we will cover the basic concepts of Linux users and groups and demonstrate how they are managed using practical examples.</p><h3>Understanding Users &amp; Groups</h3><h3>Users</h3><p>A user is an individual identity in Linux that represents a person or process accessing the system, with specific permissions that control what resources can be accessed and what actions can be performed. Each user is assigned a unique identifier known as a UID (User ID), which the system uses to track ownership and permissions. Linux includes different types of users, one of which is the root user — the superuser account with unrestricted access and full control over the entire system.</p><h3>Groups</h3><p>A group is a collection of users in Linux used to manage permissions more efficiently. Instead of assigning permissions to individual users, groups allow access to resources to be controlled for multiple users at once. Each group is assigned a unique identifier known as a GID (Group ID), which the system uses to manage group ownership and permissions. Users can be members of one or more groups, and file access is often determined by group membership.</p><h3>User Management</h3><h4>1. Creating Users</h4><p>To create a new user, use the useradd command followed by the username. For example, to create a user named “ batman” run:</p><pre>sudo useradd batman</pre><h4>2. Setting User Password</h4><p>User the passwd command to set a password for the newly created user:</p><pre>sudo passwd batman</pre><h4>3. Deleting Users</h4><p>To remove a user account including their home directory and files</p><pre>sudo userdel -r batman</pre><h4>4. User Database files</h4><p>/etc/passwd : this file contains all user details</p><p>/etc/shadow : this file contain all user password in hash format</p><h3>Group Management</h3><h4>1. Creating Groups</h4><p>To create group we can use</p><pre>sudo groupadd &lt;group_name&gt;</pre><h4>2. Adding User to Groups</h4><p>To add user to group we can use</p><pre>sudo usermod -aG &lt;group_name&gt; batman</pre><h4>3. Changing Group Ownership of Files</h4><p>To change group ownership of a file/directory, we can use</p><pre>sudo chown :&lt;group_name&gt; &lt;file/directory&gt;</pre><h4>4. Delete Groups</h4><p>To delete a group, we can use</p><pre>sudo groupdel &lt;group_name&gt;</pre><h4>5. Group Database Files</h4><p>/etc/group : this file contain all group informations</p><p>/etc/gshadow : this file contain all group members details</p><h3>Conclusion</h3><p>User and group management in Linux is important for maintaining security and access control. By understanding how to create, modify and delete users and groups, we can effectively manage permissions and organize user in our Linux system. These fundamentals skills are essential for any Linux system administrator.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7fb5d43bad88" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is Networking? A Beginner’s Guide to How Devices Connect and Communicate]]></title>
            <link>https://r3d1n1t.medium.com/what-is-networking-a-beginners-guide-to-how-devices-connect-and-communicate-606605eb7696?source=rss-e1defcaba618------2</link>
            <guid isPermaLink="false">https://medium.com/p/606605eb7696</guid>
            <category><![CDATA[networking-for-beginners]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[internet]]></category>
            <dc:creator><![CDATA[R3d1n1t]]></dc:creator>
            <pubDate>Mon, 13 Oct 2025 05:47:53 GMT</pubDate>
            <atom:updated>2025-10-13T05:47:53.959Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Y9-UTJvnC-jKCQNB" /><figcaption>Photo by <a href="https://unsplash.com/@jouwdan?utm_source=medium&amp;utm_medium=referral">Jordan Harrison</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Networking is what makes our digital world possible — connecting computers, phones, routers, and servers to share data and communicate. In this post, you’ll learn what networking is, its types (LAN, WAN, Internet), and why it’s the foundation of everything from home Wi-Fi to global communication.</p><h3>What is Networking</h3><p>Networking is the art of <strong>connecting devices together</strong> so they can communicate, share information, and access resources efficiently.</p><p>A network can be as simple as <strong>two devices connected by a cable</strong> or as vast as the <strong>Internet</strong>, which links millions of systems around the globe.</p><h3>In Simple Words</h3><p>A <strong>network</strong> is a collection of devices connected to each other to <strong>share resources, exchange data, and communicate</strong>.</p><h3>These devices can include:</h3><ul><li>Computers &amp; Laptops</li><li>Smartphones &amp; Tablets</li><li>Routers &amp; Switches</li><li>Printers, Servers, Smart TVs, and more</li></ul><h3>Why Do We Use Networking?</h3><p>Networking powers almost everything we do in the digital world. It allows us to:</p><ul><li>Share data and files (documents, videos, photos)</li><li>Make voice and video calls (Zoom, WhatsApp, Teams)</li><li>Access the Internet (browsing, gaming, streaming)</li><li>Use shared resources (like printers, cloud storage, or servers)</li></ul><h3>Types of Networks</h3><h3>LAN (Local Area Network)</h3><p>A LAN connects devices within a <strong>small area</strong> such as a home, office, or school.<br> <strong>Example:</strong> Wi-Fi or Ethernet connecting your laptop, phone, and printer.</p><h3>WAN (Wide Area Network)</h3><p>A WAN connects multiple LANs across <strong>larger geographical distances</strong>, often using routers and service providers.<br> <strong>Example:</strong> A company’s branch offices connected across different cities.</p><h3>Internet</h3><p>The <strong>Internet</strong> is the world’s largest network — a global system interconnecting millions of LANs and WANs to enable communication, resource sharing, and services like websites, emails, and cloud storage.</p><h3>Example: From LAN to the Internet</h3><p>When you connect your <strong>phone, laptop, and TV</strong> to your home Wi-Fi, they form a <strong>LAN (Local Area Network).</strong></p><p>Now imagine:</p><ul><li>Your LAN connects to your neighbor’s LAN</li><li>Many LANs form larger <strong>WANs</strong></li><li>All these WANs connect together to form the <strong>Internet</strong></li></ul><pre>LAN → Multiple LANs → WAN → Internet</pre><h3>A Good Way to Think About It</h3><ul><li>At home, all your devices connected via Wi-Fi form your <strong>Local Area Network (LAN)</strong>.</li><li>When multiple LANs interconnect, they create <strong>Wide Area Networks (WANs).</strong></li><li>All these LANs and WANs together build the <strong>Internet</strong> — the massive “network of networks.”</li></ul><h3>Final Thoughts</h3><p>Networking is the <strong>foundation of the digital world</strong>. Whether it’s browsing a website, streaming a movie, or connecting to a cloud server — it’s all possible because of networks working behind the scenes.</p><p>Understanding networking is your <strong>first step</strong> into cybersecurity, ethical hacking, and IT infrastructure — so mastering this concept early will give you a solid base for everything ahead.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=606605eb7696" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Linux File Permissions: An Introduction for Beginners]]></title>
            <link>https://r3d1n1t.medium.com/linux-file-permissions-an-introduction-for-beginners-9f1cffa6e77f?source=rss-e1defcaba618------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f1cffa6e77f</guid>
            <category><![CDATA[linux-tutorial]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[pentesting]]></category>
            <category><![CDATA[linuxworld]]></category>
            <dc:creator><![CDATA[R3d1n1t]]></dc:creator>
            <pubDate>Thu, 24 Jul 2025 07:49:34 GMT</pubDate>
            <atom:updated>2025-07-24T07:49:34.149Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/970/1*doGP94kjCEJsG9loLtOuXg.jpeg" /></figure><h3>Understanding Linux File Permissions with a Simple Analogy</h3><p>Linux file permissions are like the security system in front of a house only privileged or authorized people are allowed to access certain areas. Similarly, in Linux, files and directories have permissions that control who can read, modify, or execute them.</p><p>This permission system acts as a barrier between users and files that don’t belong to them or that they’re not meant to access. Just like a guest can’t walk into someone else’s private room without permission, a normal user in Linux cannot access or execute sensitive files owned by the system or other users.</p><p>In simple terms, Linux file permissions protect the system by ensuring only the right people can do the right things with each file — keeping everything secure and organized.</p><h3>Why are they important for system security and user control?</h3><p>File permissions are extremely important because a system or operating system holds many sensitive files and programs. These need to be protected from unprivileged users who might accidentally or intentionally perform harmful or unauthorized actions, including hacking or system abuse.</p><p>An operating system is used for many purposes and holds our personal data, system settings, and important applications. All of this is valuable and must be secured.</p><p>While file permissions can’t protect everything completely, they act as a strong first line of defense. They help ensure that only the right users can access or modify certain files — helping to protect the system from unauthorized access, misuse, or damage.</p><p>In simple words, Linux file permissions help keep your system safe and your data under your control.</p><h4>This is how file permissions appear when you check them in Linux:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*LNjiu7STE0BibrPZ0WQdHQ.png" /></figure><pre>-rwx rwx rwx<br>  │   │  │<br>  │   │  └── Others(o)<br>  │   └────  Group(g)<br>  └────────  Owner(u)</pre><h3>Understanding rwx – Read, Write, and Execute</h3><p>In Linux, each file and directory has three basic types of permissions represented by the letters r, w, and x</p><ul><li><strong>r – Read Permission, </strong>this allows the user to read the contents of a file or list the contents of a directory.</li><li>w <strong>– Write Permission, </strong>this gives the user the ability to modify a file, add content, or rename/delete a file or directory basically, anything that changes the data or structure.</li><li>x <strong>– Execute Permission, </strong>this allows the user to run or execute files and scripts (like .sh , .py , …etc). for directories, it allows entering into the directory (using cd).</li></ul><h3>Changing Permissions Using chmod (Symbolic &amp; Numeric)</h3><p>Now that we understand how permissions work, let’s learn how we can change them using the chmod command — short for change mode. It allows us to modify file and directory permissions in two ways:</p><ol><li><strong>Symbolic Mode</strong> — using letters like r, w, and x</li><li><strong>Numeric Mode</strong> — using numbers like 755, 644, etc.</li></ol><h3>Symbolic Mode</h3><p>in symbolic mode, we directly add or remove specific permissions:</p><p>Let’s try a real example on our Linux system:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/519/1*Nlk_TDw9mvfTfyi0pBpsZQ.png" /><figcaption>Add execute permission for all (owner, group, others).</figcaption></figure><p>Once we understand one command, we can try others too:</p><pre>chmod +x file.sh # Add execute permission for all(owner, group, others)<br>chmod +r file.sh # Add read permission for all(owner, group, others)<br>chmod +w file.sh # Add write permission for all(owner, group, others)<br>chmod u+x file.sh # Add execute permission for the owner only<br>chmod g+w file.sh # Add write permission for the group only<br>chmod u-x file.sh # Remove execute permission from owner<br>chmod g-w file.sh # Remove write permission from group</pre><h3>Numeric Mode</h3><p>Apart from symbolic mode, we can also use numeric mode to set permissions in a quicker way.</p><p>There are three digits used in numeric mode:</p><ul><li>first digit is for the owner</li><li>second digit is for the group</li><li>third digit is for others</li></ul><p>Each permission has a number value:</p><p>read(r) = 4</p><p>write(w) = 2</p><p>execute(x) = 1</p><p>We add the values based on the permissions we want to give.</p><h3>How to Calculate Numeric Permissions (With Example)</h3><pre>User	 | Permissions |	Value Calculation	| Final Digit |<br>---------|-------------|--------------------------------|-------------|<br>Owner	 | rwx	       |        4 + 2 + 1	        | 7           |<br>Group	 | r-x	       |        4 + 0 + 1	        | 5           |<br>Others   | r--	       |        4 + 0 + 0	        | 4           |</pre><pre>chmod 754 file.sh</pre><p>result;</p><pre>-rwxr-xr--</pre><h3>Applying Numeric Permissions;</h3><p>we created a test file and used the chmod 754 command to change its permissions. As shown below, the file now has rwx for the owner, r-x for the group, and r-- for others.</p><p>Let’s try a real example on our Linux system:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/587/1*u95Poxcu6O_a-5fYJc1XPA.png" /></figure><h3>chown – Changing Ownership in Linux</h3><p>In Linux, every file and directory has an <strong>owner</strong> and a <strong>group</strong> assigned to it. Sometimes we may need to change the ownership.</p><p>That’s where the <br>chown command comes in.</p><h3>What is chown?</h3><p>The chown command allows us to change:</p><ul><li>The owner of a file or directory</li><li>the group</li><li>Or both at the same time</li></ul><p>Basic Syntax;</p><pre>chown user:group filename</pre><ol><li>user — new owner</li><li>group — new group</li><li>filename — the file/directory we want change</li></ol><h3>Example(chown);</h3><p>In this example, we changed the ownership(owner) of a file using the chown command;</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/645/1*xOdyGPu_UqOFPbFwetm5gQ.png" /><figcaption>changed the owner of the file using chown.</figcaption></figure><p>we changed the group of a file step by step using the chown command;</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/641/1*5ntUgDxkFx1S4E_iIxv4TA.png" /><figcaption>changed the group of a file using chown.</figcaption></figure><h3>Conclusion</h3><p>Understanding Linux file permissions is a critical step toward becoming confident in managing a secure and well-organized system. Just like a security system in a house, permissions act as digital locks — determining who can <strong>read</strong>, <strong>modify</strong>, or <strong>execute</strong> files and directories.</p><p>We explored how the <strong>rwx </strong>(Read, Write, Execute) defines access, and how both <strong>symbolic</strong> (chmod u+x) and <strong>numeric</strong> (chmod 754) modes allow us to precisely control these permissions. We also learned how to adjust file ownership using the <strong>chown </strong>command, giving us full control over who owns what and who can do what.</p><p>These tools are essential in real-world Linux environments, where multiple users and processes coexist. Proper permission management helps prevent unauthorized access, accidental changes, and potential security risks — making it a cornerstone of system administration and cybersecurity.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f1cffa6e77f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Linux Terminal for Beginners: A Simple Guide]]></title>
            <link>https://r3d1n1t.medium.com/linux-terminal-for-beginners-a-simple-guide-3843606c7fa0?source=rss-e1defcaba618------2</link>
            <guid isPermaLink="false">https://medium.com/p/3843606c7fa0</guid>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[linux-tutorial]]></category>
            <category><![CDATA[linux-commands]]></category>
            <category><![CDATA[linuxworld]]></category>
            <dc:creator><![CDATA[R3d1n1t]]></dc:creator>
            <pubDate>Sun, 22 Jun 2025 09:00:28 GMT</pubDate>
            <atom:updated>2025-06-22T09:00:28.650Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k5VbkXLG46zCa62kZtpz9A.avif" /></figure><h3>Why Learn the Linux Command Line?</h3><p>The Linux command line, also known as the <strong>terminal</strong>, is a powerful tool used to interact with the Linux operating system. Instead of clicking through menus like in a graphical interface (GUI), you type commands to perform tasks. With the terminal, you can <strong>run programs, manage files, configure the system, troubleshoot issues</strong>, and so much more — often <strong>faster and more precisely</strong> than using a GUI. While it may look intimidating at first, the command line gives you full control over your system, which is why system administrators, developers, hackers, and power users rely on it every day.</p><h3>What is a Shell?</h3><p>A <strong>shell</strong> is a program that takes your commands and tells the operating system what to do. When you type something in the terminal and press Enter, the shell processes that command and runs it.</p><p>Think of the shell as a <strong>middleman between you and the Linux system</strong>. It reads your commands, understands them, and executes them for you.</p><p>There are different types of shells in Linux. The most common ones are:</p><ul><li>Bash(Bourne Again Shell) — Default on many Linux systems</li><li>Zsh — A powerful alternative with more features</li><li>fish — User-friendly and modern</li></ul><p>Most beginners use bash, and its a great place to start.</p><h3>Basic Commands Every Beginners Should Know</h3><pre>Command | Description<br>--------------------------------------------<br>pwd     | Print current directory<br>        <br>ls      | List files and directories<br><br>cd      | Change directory<br><br>mkdir   | Make new directory<br><br>touch   | Create a new empty file<br><br>echo    | Display a line of text<br><br>cat     | Show contents of a file<br><br>cp      | Copy files or directories<br><br>mv      | Move/rename files or directories<br><br>rm      | Remove files or directories<br><br>clear   | Clear terminal screen<br><br>man     | Show manual/help for a command</pre><h3>Navigation Tips</h3><pre>Command | Description<br>---------------------------------------<br>cd ..   | Go up one directory<br>cd ~    | Go to your home directory<br>cd /    | Go to your root directory<br>cd -    | Go to the previous directory</pre><h3>Conclusion</h3><p>The Linux command line or terminal might feel confusing at first — I get it, it felt heavy for me too. But honestly, it’s the best way to understand Linux deeply. It gives you full control, helps you run tasks more efficiently, and shows you how Linux truly works behind the scenes.</p><p>If you’re just starting, don’t worry — there are plenty of great resources to help you. Some of the best ones I’ve found are:</p><ul><li><a href="https://linuxjourney.com/">LinuxJourney — simple and beginner friendly</a></li><li><a href="https://tryhackme.com/room/linuxfundamentalspart1">TryHackMe Linux fundamentals(room)— great for beginners</a></li><li>YouTube — Tons of visual guides and tutorials</li></ul><p>Just take it step by step, try the commands, and keep going. You’ll get better every day. I’m learning too — and this blog is part of my journey.</p><blockquote>I’ll also be writing more posts soon where I explain other Linux commands, how they work, and why they matter. I plan to cover topics like permissions, user management, process management, and more — so stay tuned!</blockquote><p>Thanks for reading — let’s learn Linux together! <br> — Written by Redinit</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3843606c7fa0" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>