When most beginners learn Linux, they start with commands like ls, cd, and mkdir. Those commands are useful, but they only scratch the surface.

What makes Linux truly fascinating is the idea that almost everything in the system is represented as a file. Users, processes, devices, DNS settings, boot configuration, and even kernel information are exposed through the filesystem.

For this assignment, I explored a real Linux environment and investigated how different directories and files control system behavior. Instead of focusing on commands, I focused on understanding why these files exist, what problems they solve, and what they reveal about Linux internals.

1. /etc/passwd and /etc/shadow — How Linux Stores User Accounts

What They Do

• /etc/passwd stores information about all user accounts.
• /etc/shadow stores encrypted passwords and password policies.

Why They Exist

Linux separates public account information from sensitive password data.

What Problem They Solve

Originally, password hashes were stored directly in /etc/passwd, which was readable by everyone. This created security risks. Moving hashes to /etc/shadow, which only root can read, significantly improved security.

Example

cat /etc/passwd
sudo cat /etc/shadow

Insight Learned

Every user on the system is just a line in a text file. Linux user management is fundamentally file-based.

2. /etc/resolv.conf — How DNS Works

What It Does

This file tells Linux which DNS servers to use when resolving domain names.

Why It Exists

Applications need a standard place to find DNS configuration.

What Problem It Solves

Without DNS, users would need to remember IP addresses instead of domain names.

Example

cat /etc/resolv.conf

Typical content:

nameserver 8.8.8.8

Insight Learned

DNS resolution in Linux depends on a single configuration file. Changing one line can redirect all domain lookups.

3. /etc/hosts — Local Name Resolution

What It Does

Maps hostnames to IP addresses before DNS is consulted.

Why It Exists

Provides local overrides for hostname resolution.

What Problem It Solves

Useful for development, testing, and blocking domains.

Example

127.0.0.1 mylocalapp.test

Insight Learned

A single entry in /etc/hosts can make any domain point to any IP address on your machine.

4. /proc/cpuinfo and /proc/meminfo — Real-Time Kernel Data

What They Do

Provide live information about CPU and memory.

Why They Exist

Expose kernel information through files rather than specialized APIs.

What Problem They Solve

Allow administrators and tools to inspect hardware and system resources easily.

Example

cat /proc/cpuinfo
cat /proc/meminfo

Insight Learned

These files are generated dynamically by the kernel. They do not exist on disk but are created when read.

5. /proc/net/route — Routing Table Information

What It Does

Shows how Linux decides where to send network packets.

Why It Exists

Networking tools need access to the kernel routing table.

What Problem It Solves

Determines whether traffic goes to the local network, a gateway, or another interface.

Example

cat /proc/net/route

Insight Learned

Routing decisions are exposed as plain text, proving that Linux networking is deeply integrated into the filesystem.

6. /var/log — The System's Memory

What It Does

Stores logs for authentication, kernel events, and services.

Important Files

• /var/log/syslog
• /var/log/auth.log
• /var/log/kern.log

Why It Exists

Systems need persistent records of activity for debugging and auditing.

What Problem It Solves

Without logs, diagnosing failures or security incidents would be nearly impossible.

Example

tail -f /var/log/syslog

Insight Learned

Logs reveal everything from login attempts to service crashes, making them one of the most valuable directories in Linux.

7. /dev — Hardware as Files

What It Does

Represents devices as special files.

Examples

• /dev/sda — Disk
• /dev/null — Discards all input
• /dev/random — Random number generator
• /dev/tty — Terminal

Why It Exists

Provides a consistent interface to hardware.

What Problem It Solves

Applications can interact with devices using the same read/write operations used for normal files.

Insight Learned

Linux treats hardware and software uniformly. A hard drive can be accessed just like a file.

8. /boot — Files Required to Start Linux

What It Does

Contains the kernel, initramfs, and bootloader data.

Important Files

• vmlinuz-*
• initrd.img-*
• grub/

Why It Exists

The bootloader needs a dedicated location for startup files.

What Problem It Solves

Provides everything necessary to initialize the kernel and mount the root filesystem.

Insight Learned

Without /boot, Linux cannot start. This directory is the foundation of the entire operating system.

9. /etc/systemd/system — Service Management

What It Does

Stores custom service definitions for systemd.

Why It Exists

Allows administrators to control which programs start automatically.

What Problem It Solves

Automates background services such as databases, web servers, and schedulers.

Example

sudo systemctl status nginx

Insight Learned

Modern Linux startup is driven by text-based service files rather than hardcoded scripts.

10. /etc/environment and .bashrc — Environment Configuration

What They Do

Define environment variables such as PATH.

Why They Exist

Programs rely on environment variables for configuration and executable discovery.

What Problem They Solve

Ensure applications can find commands and configuration consistently.

Example

echo $PATH
cat /etc/environment

Insight Learned

The ability to run commands without typing full paths depends entirely on environment configuration.

Bonus Discovery: Every Process Has a Directory in /proc

Each running process has its own directory under /proc/<PID>/.

Example

ls /proc/1/

These directories include:

• cmdline
• status
• fd/
• environ

Insight Learned

Processes are exposed as files, allowing administrators to inspect command-line arguments, open files, and memory usage.

Most Surprising Lesson

The most surprising discovery was that Linux does not hide system internals behind proprietary interfaces. Instead, it exposes nearly everything through readable files and directories.

This design makes Linux incredibly transparent, scriptable, and powerful.

Conclusion

This exploration changed how I think about Linux.

I used to view the filesystem as a place to store documents and programs. After investigating directories like /etc, /proc, /dev, /boot, and /var/log, I realized that the filesystem is actually the control center of the entire operating system.

• Users are stored in text files.
• DNS is configured in one file.
• Hardware appears as files.
• Processes have their own directories.
• Logs record every important event.
• Services are controlled through configuration files.
• Boot depends on a dedicated directory.

Linux follows a simple but powerful philosophy: everything is a file.

Once you understand the filesystem, you begin to understand how Linux itself works.