🐧 Terminal Simulator Series

Linux Filesystem & Navigation

Master the 20% of commands that senior engineers use 80% of the time. Interactive terminal. Real-world scenarios. Zero risk.

Module Progress0/7 steps
STEP 1 / 7
ls

The Power of ls -la

Real-World Scenario

You have just SSH'd into a production server after receiving an alert. The first thing any senior engineer does is orient themselves: What files are here? Are there hidden config files? Who owns them?

Technical Breakdown

`ls` lists directory contents. But a bare `ls` hides critical info. Pros always use `ls -la`: `-l` gives permissions, owner, size, and date; `-a` reveals hidden dotfiles like `.env`, `.bashrc`, and `.ssh/`. In production, hidden files often hold secrets and configs.

-lLong format — shows permissions, owner, group, size, and modification date.
-aShow ALL files, including hidden ones starting with a dot (.)
-hHuman-readable sizes (1K, 234M, 2G instead of raw bytes).
-tSort by modification time, newest first.
-rReverse the sort order.

Your Task

List ALL files (including hidden) in long format. Type: ls -la

devops@prod-server — bash
devops@prod-server:~$

Quick Guide: Linux Filesystem

Understanding the basics in 30 seconds

How It Works

  • Everything in Linux is a file or directory
  • Paths start from / (root) — the top of the tree
  • Hidden files start with a dot (e.g., .env, .ssh)
  • Permissions control who can read, write, execute
  • Navigation uses absolute (/var/log) or relative (../logs) paths

Key Benefits

  • Faster incident response with ls -latr
  • Safer operations with pwd verification
  • Efficient workflow with cd - toggling
  • Clean project scaffolding with mkdir -p
  • Quick file search with find

Real-World Uses

  • Debugging production log files
  • Navigating Kubernetes node filesystems
  • Setting up CI/CD deployment directories
  • Auditing file permissions for security
  • Searching for recently changed configs

Why Senior Engineers Master These Commands First

The Pareto Principle of Linux

Out of hundreds of Linux commands, a surprisingly small set covers the vast majority of daily DevOps work. Commands like ls, cd, pwd, mkdir, touch, and find form the foundation that every senior engineer uses reflexively — often dozens of times per hour during incident response.

The difference between a junior and senior engineer isn't knowing MORE commands — it's knowing the right flags and combinations. For example, ls -latr is infinitely more useful than bare ls because it shows hidden files, permissions, and sorts by time with the newest at the bottom.

Navigation Commands

The essential commands for moving through the Linux filesystem quickly and safely.

  • ls -la — See everything, including hidden files.
  • ls -latr — Time-sorted, newest at bottom.
  • cd - — Toggle between two directories.
  • pwd — Always verify before destructive ops.

File Management

Create and organize directory structures like a professional.

  • mkdir -p — Create nested dirs in one shot.
  • touch — Scaffold multiple files instantly.
  • find -name -mmin — Locate changed configs.
  • Brace expansion — Batch creation with { }

Building Muscle Memory

The goal of this simulator is not just to teach you commands — it's to build muscle memory. When you're in the middle of a 3 AM production incident, you don't have time to Google "how to find recently modified files." These commands need to flow from your fingers automatically.

Pro Tip: Practice each step multiple times until the commands feel natural. Use the "reset" command to clear the terminal and try again. The goal is speed and accuracy — not just completion.

The Infinity

Weekly tech insights, programming tutorials, and the latest in software development. Join our community of developers and tech enthusiasts.

Connect With Us

Daily.dev

Follow us for the latest tech insights and updates

© 2026 The Infinity. All rights reserved.