<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: AP</title>
    <description>The latest articles on DEV Community by AP (@anshulx77).</description>
    <link>https://dev.to/anshulx77</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3874857%2F808813ed-96b2-4a75-a490-517b0795cc7b.png</url>
      <title>DEV Community: AP</title>
      <link>https://dev.to/anshulx77</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/anshulx77"/>
    <language>en</language>
    <item>
      <title>Linux Never Hides Anything</title>
      <dc:creator>AP</dc:creator>
      <pubDate>Wed, 22 Apr 2026 18:24:50 +0000</pubDate>
      <link>https://dev.to/anshulx77/linux-never-hides-anything-3f8p</link>
      <guid>https://dev.to/anshulx77/linux-never-hides-anything-3f8p</guid>
      <description>&lt;p&gt;Linux never hides anything. It's just quiet. Everything: users, processes, network behavior, even hardware exists as files, quietly sitting in plain sight. I just never looked.&lt;/p&gt;

&lt;p&gt;The moment I started exploring the filesystem instead of just running commands, Linux stopped feeling like a tool… and started feeling like a system I could actually understand.&lt;/p&gt;

&lt;h2&gt;
  
  
  It Started With Simple Exploration
&lt;/h2&gt;

&lt;p&gt;At first, I wasn't doing anything advanced. Just moving around, checking what exists.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;pwd&lt;/code&gt;, &lt;code&gt;cd&lt;/code&gt;, &lt;code&gt;ls -l&lt;/code&gt;, &lt;code&gt;ls -a&lt;/code&gt; : understanding where I am, lists all the files in current directory&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;touch&lt;/code&gt; : creates files&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;man&lt;/code&gt; : short manual, to explore tools&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That's when it clicked; The system already explains itself. You just have to ask properly.&lt;/p&gt;

&lt;h2&gt;
  
  
  Reading Files
&lt;/h2&gt;

&lt;p&gt;Instead of opening files blindly, I started reading them strategically.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;cat&lt;/code&gt; : quick full view&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;head&lt;/code&gt; / &lt;code&gt;tail&lt;/code&gt; : check only the beginning or end&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;less&lt;/code&gt; : scroll without overwhelming the terminal&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Each thing changed, how I read data. Logs stopped being chaos and started becoming information.&lt;/p&gt;

&lt;h2&gt;
  
  
  Logs or Filtering
&lt;/h2&gt;

&lt;p&gt;Raw logs are noisy chaos. So I stopped reading everything and started filtering :&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;cat &lt;/span&gt;syslog | &lt;span class="nb"&gt;grep&lt;/span&gt; &lt;span class="s2"&gt;"error"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  &lt;code&gt;/etc&lt;/code&gt; : Control Center
&lt;/h2&gt;

&lt;p&gt;While exploring configs, I used :&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;find / &lt;span class="nt"&gt;-name&lt;/span&gt; &lt;span class="s2"&gt;".conf"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That one command showed me how spread out system behavior really is.&lt;/p&gt;

&lt;p&gt;Files in &lt;code&gt;/etc&lt;/code&gt; aren't random, they define everything.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;users
&lt;/li&gt;
&lt;li&gt;DNS
&lt;/li&gt;
&lt;li&gt;networking
&lt;/li&gt;
&lt;li&gt;services
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This is where Linux decides how to behave.&lt;/p&gt;




&lt;h2&gt;
  
  
  Permissions
&lt;/h2&gt;

&lt;p&gt;Permissions felt small… until they weren't.&lt;/p&gt;

&lt;p&gt;Using :&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;chmod &lt;/span&gt;600 db.conf
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;or changing ownership:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;chown &lt;/span&gt;user:user db.conf
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Processes
&lt;/h2&gt;

&lt;p&gt;To see what's actually running:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;top
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Live processes, CPU usage, memory; it's all there.&lt;/p&gt;

&lt;p&gt;And when something misbehaves :&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;kill&lt;/span&gt; &amp;lt;pid&amp;gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;No UI. No drama. Just direct control.&lt;/p&gt;




&lt;h2&gt;
  
  
  Services
&lt;/h2&gt;

&lt;p&gt;Services don't "just run"&lt;/p&gt;

&lt;p&gt;They are controlled.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;systemctl status docker
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Start, stop, restart : it's all explicit.&lt;/p&gt;

&lt;p&gt;Once you see this, "background processes" stop feeling mysterious.&lt;/p&gt;




&lt;h2&gt;
  
  
  Files Can Be Packed, Moved, Reused
&lt;/h2&gt;

&lt;p&gt;Even handling files taught something :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;zip&lt;/code&gt; / &lt;code&gt;unzip&lt;/code&gt; : bundling and extracting data/file&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Not just convenience.&lt;/p&gt;

&lt;p&gt;It shows how Linux treats everything as transferable units.&lt;/p&gt;




&lt;h2&gt;
  
  
  &lt;code&gt;/proc&lt;/code&gt; and &lt;code&gt;/dev&lt;/code&gt;
&lt;/h2&gt;

&lt;p&gt;At some point, commands became less important.&lt;/p&gt;

&lt;p&gt;Because the real system was already visible:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;/proc&lt;/code&gt; : live system state
&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;/dev&lt;/code&gt; : hardware as files
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Commands were just ways to look better.&lt;/p&gt;




&lt;h2&gt;
  
  
  What Changed
&lt;/h2&gt;

&lt;p&gt;Before :&lt;br&gt;
I used commands.&lt;/p&gt;

&lt;p&gt;Now :&lt;br&gt;
I understand why they exist.&lt;/p&gt;

&lt;p&gt;They're not the system. They're just ways to interact with it.&lt;/p&gt;




&lt;h2&gt;
  
  
  Final Thought
&lt;/h2&gt;

&lt;p&gt;Linux never tried to be complicated. It just stayed quiet. &lt;/p&gt;

&lt;p&gt;Everything is there : not hidden, just waiting to be noticed.&lt;/p&gt;




&lt;h2&gt;
  
  
  Shout-out
&lt;/h2&gt;

&lt;p&gt;Part of this exploration was inspired by a walkthrough focused on real-world troubleshooting using a small set of commands.&lt;/p&gt;

&lt;p&gt;I came across this video during that phase, and it genuinely changed how I look at Linux :&lt;br&gt;&lt;br&gt;
&lt;a href="https://youtu.be/CLh2ACdXNbc" rel="noopener noreferrer"&gt;Watch the video&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;It helped me move from running commands to actually understanding the system.&lt;/p&gt;

</description>
      <category>linux</category>
      <category>filesystem</category>
      <category>webdev</category>
      <category>learning</category>
    </item>
  </channel>
</rss>
