Linux File System Explained: The Ultimate Guide to pwd, ls, cd, and the FHS

In our last guide, we faced the “scary black screen”—the Linux Terminal. We learned that it’s not a “hacker tool” to be feared, but an “engine room” of incredible power. We demystified the Terminal (the window), the Shell (the brain), and the CLI (the conversation). You learned why it’s a superpower for efficiency (Tab completion), power (| pipes), automation (scripts), and remote access (ssh). You learned the grammar of a command and how to use man to read the built-in instruction manual.

Today, you’re going to stop being a tourist. You’re going to become a navigator.

The single biggest difference between a GUI (Graphical User Interface) and a CLI (Command-Line Interface) is how you perceive “location.”

In a GUI, you have a “File Explorer.” It’s a visual, top-down map. You can see the “Projects” folder inside the “Documents” folder. You are a map-reader, floating above the world, pointing at where you want to go.

In the CLI, you are not above the world. You are in it. You are a “first-person” explorer. You “stand” inside a single directory at a time. You can’t see what’s inside a folder until you go into it.

This “first-person” navigation feels strange at first, but it is infinitely faster and more powerful once you internalize it. To do it, you need to master three things:

1. The “Map” (The File System): You need a mental map of the entire Linux “world.” Where are the “cities” (system files) and where is your “house” (home directory)? This is the Filesystem Hierarchy Standard (FHS).
2. Your “GPS” (pwd): A command to answer, “Where am I right now?”
3. Your “Eyes” (ls): A command to answer, “What’s around me?”
4. Your “Legs” (cd): A command to answer, “Let’s go somewhere else.”

These three simple commands—pwd, ls, and cd—will make up more than 50% of all the commands you will ever type. They are the “core loop” of all terminal work. Mastering them is not optional.

This is not a short overview. This is the ultimate guide. By the end of this article, you will be able to navigate the entire Linux file system, from top to bottom, with speed and confidence, all from your keyboard.

Let’s begin.

The Linux Filesystem Hierarchy Standard (FHS)

Before you can move, you need to understand the map.

In Windows, your map is fractured. You have a C: drive (for your OS) and maybe a D: drive (for your games) and an E: drive (your USB stick). It’s a “multi-root” system.

In Linux, the map is simple, elegant, and unified. There is only one root.

Everything—everything—on your computer starts from a single directory called / (the “root” directory).

Think of it as a giant, inverted tree. / is the trunk. Every other directory is a branch. Your USB stick? It doesn’t show up as an E: drive. Instead, it gets attached (or “mounted”) to a branch on this single tree (e.g., /media/yourname/USB-STICK).

This single-tree structure is the Filesystem Hierarchy Standard (FHS). It’s a set of rules that all Linux distros (Mint, Ubuntu, Fedora) agree to follow. This means the “map” is the same everywhere. The /etc directory in Ubuntu is in the same “place” and serves the same purpose as the /etc directory in Fedora.

This makes the system predictable and powerful.

But the real “Aha!” moment is this: In Linux, everything is a file.

• A text document? It’s a file.
• A directory? It’s just a special file that contains a list of other files.
• Your keyboard? It’s a “device file” in /dev/input/
• Your hard drive? It’s a “device file” at /dev/sda.
• Information about your CPU? It’s a virtual file at /proc/cpuinfo.

When you “read” that cpuinfo file, you’re not actually opening a file. You’re asking the kernel to tell you about the CPU, and it presents that information as if it were a file.

This is the core philosophy. Because “everything is a file,” you can use the same tools to interact with everything. You can use grep to search a log file, and you can also use grep to search the kernel’s real-time output.

Now, let’s walk through the “cities” on your new map. You don’t need to memorize them all, but you need to know the “big” ones.

The Deep-Dive Breakdown of the FHS

This is your guided tour of the “world.”

<b>/</b> (The Root)

• What it is: The trunk. The beginning. The top of the tree. Every single absolute path starts with this forward slash.
• Analogy: This is “Planet Earth.” All continents, countries, and cities exist within it.

<b>/home</b> (Home Directories)

• What it is: This is the only place you, as a normal user, should ever be. If the OS is the “city,” /home is the “suburbs.”
• Inside /home, every user gets their own private, protected directory. If your username is alice, your “house” is at /home/alice. If another user bob logs in, his house is at /home/bob.
• Your /home/alice directory is your space. You have full read/write/execute permissions here. You can’t (and shouldn’t!) write files in most other places. Your “Documents,” “Downloads,” “Music,” and “Desktop” folders are all inside /home/alice.
• This is the most important directory for you. 99% of your time in the CLI will be spent somewhere inside /home/yourname.

<b>/root</b> (The Root User’s Home)

• What it is: This is the administrator’s home directory. It is not inside /home for a critical security reason: separation.
• You (as alice) are a “standard user.” The “root” user is the super-administrator with God-like powers.
• If the /home directory (which might be on its own hard drive) fails, the root user must still be able to log in to fix the system. Their home directory is kept separate on the main partition.
• Rule: You should never, ever be in here.

<b>/etc</b> (Etcetera / Configuration)

• What it is: The “control panel” or “settings” folder for the entire operating system.
• This directory contains no programs. It contains only configuration files (.conf).
• If you install a web server, its settings file (nginx.conf) goes in here. The list of all users (passwd) is in here. The map of your hard drives (fstab) is in here.
• Analogy: If your OS is a car, /etc is the “engine control unit” (ECU). You don’t “drive” it, but you tweak it to change how the car behaves. You will be in here a lot as you become an advanced user.

<b>/bin</b> (User Binaries)

• What it is: “Binaries” means “programs.” This directory holds the absolute essential commands that all users need to use the system.
• Where does the ls command “live”? It lives here: /bin/ls.
• Where do cp (copy) and mv (move) live? /bin/cp and /bin/mv.
• These are the fundamental “tools” that must be available, even if nothing else is.

<b>/sbin</b> (System Binaries)

• What it is: System binaries. These are the “administrator” commands, the powerful tools for managing the system itself.
• Examples: reboot, fdisk (for partitioning drives), iptables (for managing the firewall).
• Normal users can’t (and shouldn’t) run these. They are for the root user.

<b>/var</b> (Variable Files)

• What it is: As the name implies, this directory is for files that change (or “vary”) a lot, and are expected to grow in size.
• This is one of the most important directories for a system administrator.
• <b>/var/log</b>: The Log Directory. This is the “black box” flight recorder for your entire OS. Everything that happens—a login, a failure, a web request—gets written to a log file in here. syslog, auth.log, kern.log… When something breaks, this is the first place you look.
• <b>/var/www</b>: A common default directory for web servers to “serve” their files from.
• <b>/var/spool</b>: “Spool” is an old term for a queue. This is where print jobs, email queues, and other “waiting-line” tasks live.

<b>/tmp</b> (Temporary Files)

• What it is: A “public scratchpad.” This is a directory where any user and any program has full permission to write files.
• It’s for “temporary” data. A program might save a temporary file here while it’s running.
• Rule: Do not put anything important in /tmp. Most systems are configured to wipe this entire directory clean every time the computer reboots.

<b>/usr</b> (Unix System Resources)

• What it is: This is the most confusing one. The name is a historical accident. It does not mean “user.” It means “Unix System Resources.”
• In the 1970s, the main hard drives were small, so they attached a second, larger drive at /usr to hold all the “non-essential” programs and data.
• Today’s meaning: This is where most of your user-installed software lives. When you run sudo apt install firefox, it doesn’t go into /bin. It goes into /usr/bin.
• <b>/usr/bin</b>: Binaries for most of your day-to-day applications (Firefox, GIMP, etc.).
• <b>/usr/lib</b>: The “libraries” (shared code, like .dll files in Windows) that those programs need.
• <b>/usr/share</b>: Architecture-independent data—icons, wallpapers, fonts, documentation.
• Simple version: /bin is for essential OS commands. /usr/bin is for all the other programs you install.

<b>/dev</b> (Devices)

• What it is: The “magic” directory. This is where the “everything is a file” philosophy comes to life.
• This directory doesn’t contain “real” files. It contains “device files.” They are portals to your hardware.
• <b>/dev/sda</b> or <b>/dev/nvme0n1</b>: Your actual hard drive.
• <b>/dev/input/mouse0</b>: Your mouse. (Yes, you can cat /dev/input/mouse0 and see a stream of gibberish as you move it).
• <b>/dev/tty1</b>: Your virtual console (from Day 3).
• <b>/dev/null</b>: The “black hole.” This is an extremely useful “pretend” device.
  • <b>/dev/null</b> accepts all input and instantly destroys it.
  • Why? Sometimes, a command is too noisy, printing thousands of lines of “OK” messages you don’t care about. You can redirect this “standard output” (more on that later) to the void:
  • noisy-command > /dev/null (This runs the command but all its normal output is silenced, letting you only see errors).

<b>/proc</b> & <b>/sys</b> (Process & System)

• What it is: More magic. These are “virtual file systems.” The files in here have zero bytes on your disk. They are “created” on-the-fly by the kernel.
• These are windows directly into the kernel’s brain.
• When you run cat /proc/cpuinfo, you are not “opening a file.” You are asking the kernel, “What’s the CPU?” and the kernel formats the answer as if it were a file.
• You don’t edit these files. You read them to get real-time system information.

<b>/mnt</b> & <b>/media</b> (Mount Points)

• What it is: These are the “docks” where you “attach” external storage.
• <b>/media</b>: The automatic dock. When you plug in a USB stick, your desktop environment will automatically “mount” it here, in a new folder like /media/alice/KINGSTON.
• <b>/mnt</b>: The manual dock. This is a generic, empty “mounting” point for system administrators to manually attach a network drive or another hard drive.

Phew. That’s the world. You don’t need to be a cartographer, but you now have the map. You know the “city” is at /etc and /var, and your “house” is at /home.

Now, let’s learn how to find ourselves on that map.

pwd (Print Working Directory)

This is the simplest command in all of Linux, but it’s your most important anchor. It answers one question: “Where am I right now?”

It has no options you need to care about. It has no arguments. You just type it.

Open your terminal. You’ve just logged in. Type: pwd

The shell will print: /home/yourname

That’s it. That is your “working directory.” More specifically, it is your “absolute path.”

This is the most critical concept for navigation, so let’s spend 1,000 words on it.

Absolute vs. Relative Paths: The Most Important Navigation Concept

This is the “Aha!” moment that separates beginners from intermediate users.

An Absolute Path is a Complete Address.

• It always starts from the root (/).
• It is a full, unambiguous “GPS coordinate” that works from anywhere in the system.
• It doesn’t matter if you are in /var/log or /tmp. If you ask for /home/alice/Documents/report.pdf, the system knows exactly where that is.
• Analogy: “1600 Pennsylvania Avenue, Washington D.C.”

A Relative Path is a Set of Directions.

• It never starts with a /. It starts from where you are right now.
• It is a shortcut that only works from a specific location.
• If you are in /home/alice, the relative path to your report is just Documents/report.pdf.
• If you are in /home/alice/Documents, the relative path is just report.pdf.
• If you are in /etc, the relative path Documents/report.pdf is meaningless. The system will look for /etc/Documents/report.pdf, which doesn’t exist.
• Analogy: “Go two blocks down and take a right.” (This only works if you’re standing on the right corner!)

pwd is your anchor. It always gives you your absolute path, so you always know where you are “standing” on the map. You will use it constantly when you get lost in a maze of directories.

(For the hyper-curious: pwd -L shows your “logical” path, which respects “symlinks,” or shortcuts. pwd -P shows the “physical” path, ignoring shortcuts. You won’t need this for a long time, but now you know.)

Now that you know where you are, it’s time to see what’s around you.

ls (List)

pwd is your GPS. ls is your “eyesight.” It answers, “Now that I’m standing in this directory, what’s in here?”

Type pwd. It says /home/yourname. Now type ls. The shell will print: Desktop Documents Downloads Music Pictures Public Templates Videos

It just listed the contents of your working directory. That’s it. It’s simple, but this is the most-used command in Linux, because it’s infinitely customizable.

Running ls with no arguments is… boring. It just gives you the names. The real power of ls comes from its options (the “adverbs” we learned about in Day 3).

Let’s master the “ls” command. This will be a 3,000-word deep dive, and it will be worth it.

ls -l (The “Long Format” / The “Pro” Command)

This is the superstar. This is the command you should build into your muscle memory. ls -l (or ll on some systems, which is an “alias” or shortcut for ls -l).

Let’s run it. ls -l

The output is no longer a simple list. It’s a detailed, information-rich report.

It will look like this:

total 32
drwxr-xr-x 2 alice alice 4096 Oct 30 09:15 Desktop
drwxr-xr-x 5 alice alice 4096 Oct 31 12:07 Documents
drwxr-xr-x 2 alice alice 4096 Oct 30 09:15 Downloads
drwxr-xr-x 2 alice alice 4096 Oct 30 09:15 Music
drwxr-xr-x 2 alice alice 4096 Oct 30 09:15 Pictures
-rw-r--r-- 1 alice alice 8980 Oct 29 14:00 my-report.pdf

Whoa. What is all this? This is the “File Explorer” in text form. Let’s break down that last line, column by column. This is one of the most important things you will learn.

<b>-rw-r--r--</b> <b>1</b> <b>alice</b> <b>alice</b> <b>8980</b> <b>Oct 29 14:00</b> <b>my-report.pdf</b>

• <b>-</b>rw-r--r-- (The Permissions): This 10-character block is the security model of Linux in a nutshell.
  • First character (-): File Type.
    • <b>-</b> means this is a regular file.
    • <b>d</b> (like on the Desktop line) means this is a directory.
    • <b>l</b> (you’ll see this later) means this is a symbolic link (a “shortcut”).
  • Next 9 characters (rw-r--r--): The Permissions. These are three groups of three.
    • Group 1 (rw-): The Owner’s permissions. The “Owner” (alice) can read and write this file, but cannot execute it (the - is a “no” for execute).
    • Group 2 (r--): The Group’s permissions. Other users in the “alice” group can read the file, but cannot write or execute it.
    • Group 3 (r--): “Other” permissions. Everyone else on the computer can read the file, but cannot write or execute it.
  • This is how Linux protects itself. Notice your Documents directory is drwxr-xr-x. This means “It’s a directory. The owner can read/write/execute. Everyone else can only read/execute.” “Execute” on a directory means “enter” it. This is why other users can’t delete your files: they don’t have the w (write) permission in your folder.
• <b>1</b> (Hard Links): This is the number of “hard links” to the file. For now, just know that for files, this is almost always 1. For directories, it’s the number of items inside it + 2. Don’t worry about it.
• <b>alice</b> (The Owner): The user who “owns” this file.
• <b>alice</b> (The Group): The user group that “owns” this file.
• <b>8980</b> (The Size): The size of the file in bytes. This is… not very useful. 8980? Is that big? Small? This brings us to our next flag.

ls -h (Human-Readable)

The -h flag is the essential partner to -l. It does one simple thing: it makes the file sizes “human-readable.”

Let’s combine them. The standard, go-to, “I want to see what’s really in here” command is: ls -lh

Now, the output looks like this:

total 32K
drwxr-xr-x 2 alice alice 4.0K Oct 30 09:15 Desktop
...
-rw-r--r-- 1 alice alice 8.8K Oct 29 14:00 my-report.pdf

Look at the size column. “4096” is now “4.0K”. “8980” is now “8.8K”. If you had a 5GB video file, it would say “5.0G,” not “5368709120”.

Rule: ls -l and ls -h should always be used together. Just type ls -lh.

ls -a (All)

You think you’re seeing everything with ls -lh? You’re not. You’re being protected from the “config files.”

Type ls -a (for “all”). Now you see: . .. .bash_history .bash_logout .bashrc Desktop Documents ...

Whoa. Where did .bash_history and .bashrc come from? These are hidden files. In Linux, any file or directory that starts with a dot (.) is automatically hidden from a normal ls.

Why? Because these are configuration files. .bashrc is a file that “runs” every time you open your shell. It’s where you put your settings. It’s “hidden” to prevent you from accidentally deleting it and to keep your home directory from looking cluttered.

ls -a is the “secret-finder.” It reveals everything.

You’ll also notice two new, weird entries:

• <b>.</b> (a single dot)
• <b>..</b> (a double dot)

These are not “files.” They are navigation shortcuts.

• <b>.</b> means “this current directory.”
• <b>..</b> means “the parent directory (one level up).”

These are so important that they get their own section in Part 4.

ls -A (Almost All)

ls -a is a bit too honest. Showing you . and .. every time is just clutter. So, we have ls -A (capital “A” for “Almost All”).

ls -A shows you all the dot-files (like .bashrc) but hides the useless . and .. entries.

This is why my personal, 20-year-vetted, go-to command is ls -lAh.

• -l: Long format
• -A: Almost All (show hidden config files)
• -h: Human-readable This command gives me the perfect report of everything I care about in a directory.

Other “Sorting” Flags

• <b>ls -t</b> (Time): By default, ls sorts alphabetically. ls -t sorts by modification time, with the newest file or folder at the top.
  • Pro-Tip: ls -lht
  • This is your “What did I just work on?” command. It’s incredibly useful.
• <b>ls -r</b> (Reverse): Reverses any sort.
  • ls -lr (sorts Z to A).
  • ls -lhtr (sorts by time, oldest at the top).
• <b>ls -S</b> (Size): Sorts by file size, biggest at the top.
  • ls -lSh
  • This is your “What is eating all my disk space?!” command.

The “Big One”: ls -R (Recursive)

The -R (capital “R”) flag is the “show me everything” command. It tells ls to list the current directory, and then go into every subdirectory and list its contents, and then go into their subdirectories, and so on, all the way down.

Run this in your home directory: ls -R

It will flood your screen, showing you:

.:
Desktop  Documents  Downloads

./Desktop:
(empty)

./Documents:
report.pdf  my-project

./Documents/my-project:
main.py   README.md

./Downloads:
...

This is a “tree” view of your entire home folder. It’s a bit messy, but you can combine it with our Day 3 superpower, the pipe: ls -R | grep "README.md" (Find all “README.md” files in all subfolders).

Or, even better, create a “snapshot” of your entire home directory: ls -lR ~ > all-my-files_snapshot.txt This runs the “long-format, recursive” list and, instead of printing it, > redirects it into a single, massive text file. You can now open this file, search it, or email it.

You now have “eyes.” You can stand anywhere (pwd), see everything around you (ls -lAh), and even see everything in the entire “building” (ls -lR).

Now, it’s time to move.

cd (Change Directory)

This is the final piece of the navigation puzzle. pwd tells you where you are, ls shows you what’s there, and cd… cd moves you. It is the “verb” of movement.

This is the core loop of the CLI. The Loop:

1. pwd (You are at /home/alice)
2. ls (You see Documents and Downloads)
3. cd Documents (You move into Documents)
4. pwd (You are now at /home/alice/Documents)
5. ls (You see my-project and report.pdf)
6. cd my-project (You move into my-project)
7. pwd (You are now at /home/alice/Documents/my-project)
8. …and so on.

cd is your “double-click.” But it’s so much more.

Let’s master it. We’ll start with the two paths: Absolute and Relative.

1. Moving with Absolute Paths This is easy. You just give cd the “full address” from the root (/). It works from anywhere. You are in /home/alice/Downloads. You want to go to the system log directory. cd /var/log pwd now shows /var/log. Simple.

2. Moving with Relative Paths This is using the “directions.” You are in /home/alice. ls shows Documents. cd Documents pwd now shows /home/alice/Documents. You moved relative to where you were.

But the real power of relative navigation comes from those two “secret” directories we saw with ls -a: . and ...

The Three “Magic” cd Shortcuts You Will Use Every Day

This is it. This is the 90% of cd usage that makes you fast.

Magic Shortcut 1: cd (The “Go Home” Button)

You are lost. You’ve been digging deep into /usr/share/doc/whatever… You have no idea where you are. pwd confirms you are 10 levels deep. You just want to go home.

Type cd with no arguments at all. cd Press Enter. pwd /home/yourname

You are instantly teleported back to your home directory. This is your “panic button.” No matter how lost you are, cd (by itself) takes you home.

Magic Shortcut 2: cd ~ (The “Tilde” Shortcut)

The ~ (tilde) character is a shortcut for your home directory’s absolute path. The shell instantly translates ~/Documents into /home/yourname/Documents.

This means you can use ~ as a “base” for your absolute paths, from anywhere. You are in /var/log. You want to copy my-report.pdf from your Documents folder into this log folder. cp ~/Documents/my-report.pdf . (Don’t forget, . means “this current directory”!)

cd ~ is the explicit version of cd. cd (by itself) and cd ~ do the exact same thing: they take you home.

Magic Shortcut 3: cd .. (The “Parent” / “Go Up” Button)

This is the one you’ll use constantly. .. (dot-dot) is a “relative path” that means “the directory one level above me.”

Let’s walk up the tree.

1. pwd /home/yourname/Documents/my-project
2. cd .. (Go up one level)
3. pwd /home/yourname/Documents
4. cd .. (Go up one level)
5. pwd /home/yourname
6. cd .. (Go up one level)
7. pwd /home
8. cd .. (Go up one level)
9. pwd / (The root)
10. cd .. (What happens now?)
11. pwd / (You can’t go “up” from the root. You just stay there.)

This is your “Back” button. But you can also chain it to build complex relative paths.

Let’s say you are in /home/yourname/Documents. You want to get to /home/yourname/Downloads. You could use an absolute path: cd /home/yourname/Downloads. You could go home and then down: cd ~ then cd Downloads.

Or, you can use a relative path: cd ../Downloads

Let’s trace this “set of directions”:

1. ../: “Go up one level” (from Documents to /home/yourname).
2. Downloads: “From there, go down into the Downloads directory.”

This is how pros fly through the file system. They are constantly “hopping” up, down, and sideways. “I’m in /usr/lib/python3.11. I need to get to /usr/share/doc.” cd ../../share/doc (Go up from python3.11, go up from lib, go down into share, go down into doc.)

The Final, Secret-Weapon Shortcut: cd - (The “Toggle”)

This one is a life-saver. The - (hyphen) is a shortcut for “the last directory I was in.”

It’s the “last channel” button on your TV remote. It toggles you between your two most recent locations.

Example:

1. You are in your home directory. pwd shows /home/yourname.
2. You go to check a log file: cd /var/log. pwd now shows /var/log.
3. You’re done. You want to go exactly back to where you were.
4. Type: cd -
5. The shell will print the path it’s taking you to (/home/yourname) and then drop you there.
6. pwd now shows /home/yourname.
7. You forgot one thing! You need to go back to the logs!
8. Type: cd -
9. The shell prints /var/log and toggles you right back.

You can bounce back and forth between two-deep, complex directories all day with this one simple command.

You Are Now a Navigator

If you’ve made it this far, you’ve just graduated from “Terminal tourist” to “Terminal navigator.”

The “scary black screen” is no longer a void. It’s a “world.” And you now have the three tools you need to explore it.

• You have the Map—the Filesystem Hierarchy Standard (FHS). You know /etc is the “control panel,” /var is the “log room,” and /home is your house.
• You have your GPS—the pwd command. You can never be truly lost, because you can always find your “absolute path.”
• You have your Eyes—the ls command. You’re not just “listing.” You are generating detailed reports with ls -lAh. You can see permissions, owners, file sizes, and hidden “dot-files.”
• You have your Legs—the cd command. You’re not just “changing.” You are teleporting home with cd, hopping “up” with cd .., and toggling with cd -.

This “core loop” of pwd, ls, and cd is the foundation for everything that comes next. You’ve mastered navigation.

In our next guide (Day 5), we’ll stop just looking and start doing. Now that you can move through the file system, it’s time to change it. You will become a “builder” and a “destroyer” with the five fundamental file manipulation commands: touch (create), cat (view), rm (remove), cp (copy), and mv (move/rename).