Study guide · Topic overview

Linux CLI Fundamentals: everyday commands

A subject-based path for the Linux command line: how the shell works, how files and permissions fit together, and which command to reach for when you need to search, install, start a service, or check a disk.

Subject path · not a named certification5 study domainsReviewed October 2026

Scope notice: Linux CLI Fundamentals is an independent study topic, not CompTIA Linux+, LPIC-1, or RHCSA. The domains below organize everyday command-line skills. Items tagged Extra sit outside that everyday set. These pages do not include a terminal simulator; practice on a real shell.

What Linux CLI Fundamentals covers

The Linux command line is the text interface to the operating system. You type a command, the shell interprets it, and a program runs. This path focuses on the skills used every day on servers, developer workstations, and virtual machines: moving around the file system, reading and editing text, controlling who can change a file, watching processes, installing packages, talking to the network, and diagnosing a full disk or a failed service.

It is vendor-neutral in the sense that the same commands appear on Debian, Ubuntu, Fedora, and RHEL-family systems. Where families differ, the notes name both tools, such as apt versus dnf, instead of pretending there is only one package manager.

Who it is for

  • People new to Linux who need a working terminal vocabulary
  • Help-desk and junior admin learners moving on from Windows commands
  • Developers who can start an editor but cannot yet explain permissions or PATH

What this path is not

  • Not a named certification and not a substitute for official exam objectives
  • Not a kernel, C programming, or container-orchestration course
  • Not a command-line simulator; you still need a real shell to type on

Study domains and weighting

These weights organize the notes, flashcards, and 200 practice questions. They are not official exam weights.

  • 1.0 Shell, paths, and navigation20%
  • 2.0 Files, text, and I/O25%
  • 3.0 Permissions, users, and processes25%
  • 4.0 Packages, services, and networking20%
  • 5.0 Disks, logs, and troubleshooting10%
Domain 1.020%

Shell, paths, and navigation

How the shell finds programs and how you move around the tree.

  • Absolute vs. relative paths, ., .., and ~
  • pwd, cd, ls, tab completion, and command history
  • PATH, which, type, and man
  • The Filesystem Hierarchy Standard locations you will open every day
Domain 2.025%

Files, text, and I/O

Create, copy, search, and connect commands together.

  • cp, mv, rm, mkdir, ln, and find
  • cat, less, head, tail, grep, and nano
  • Pipes, >, >>, and 2> redirection
  • Archives with tar and gzip
Domain 3.025%

Permissions, users, and processes

Who can read a file, and what is running right now.

  • chmod octal math (755, 644, 700) and chown
  • sudo vs. su, /etc/passwd, and /etc/shadow
  • ps, top, kill, and background jobs
  • Sticky bit and SUID as Extra context for shared directories
Domain 4.020%

Packages, services, and networking

Install software, start services, and test connectivity.

  • apt on Debian/Ubuntu and dnf on Fedora/RHEL
  • systemctl start, stop, enable, and status
  • ip, ss, ping, dig, curl, and ssh
  • Prefer ip and ss over legacy ifconfig and netstat
Domain 5.010%

Disks, logs, and troubleshooting

Find space problems, failed mounts, and the right log.

  • df -h vs. du -sh, lsblk, mount, and /etc/fstab
  • journalctl, dmesg, and /var/log
  • Permission denied vs. command not found vs. no space left
  • Run fsck only on an unmounted file system

File-system layout you should recognize

Linux uses one tree. Knowing where configuration, logs, and home directories live saves time.

Common Filesystem Hierarchy Standard locations used throughout this study path.
PathWhat belongs there
/The root of the file system. Every other path hangs from here.
/homeUser home directories, such as /home/ada. Root's home is /root.
/etcSystem configuration: passwd, fstab, hosts, and service files.
/varData that changes while the system runs, including /var/log and caches.
/tmpShared temporary files. Often cleared on reboot. The sticky bit is common here.
/usrMost installed programs and shared libraries (/usr/bin, /usr/lib).
/bin, /sbinEssential user and administrator commands. On modern systems these are often links into /usr.
/optOptional third-party software installed outside the distribution packages.
/proc, /devKernel and process information, and device nodes such as disks and terminals.

Command map: pick the tool for the job

Learn what each command solves, not only its name. The same facts appear in the core notes and flashcards. They also match the Linux command list used in the CompTIA A+ Linux notes.

Everyday Linux commands grouped by task. Prefer the modern networking tools unless a system only has the legacy names.
JobCommands
Move and listpwd cd ls -l man
Create and change filescp mv rm mkdir touch ln -s nano
Read and searchcat less head tail grep find
Permissionschmod chown sudo su
Processesps aux top kill
Packagesapt (Debian/Ubuntu) dnf (Fedora/RHEL)
Services and logssystemctl journalctl
Networkip ss ping dig curl traceroute ssh
Disksdf -h du -sh lsblk mount fsck

Key files: /etc/passwd stores user accounts, /etc/shadow stores password hashes, /etc/hosts maps names to IPs locally, /etc/fstab defines file systems mounted at boot, and /etc/resolv.conf lists DNS servers.

How to practice without a simulator

Typing on a real shell is the point of this topic.

A safe place to type

Use a Linux virtual machine, a cloud instance you can rebuild, or Windows Subsystem for Linux. Avoid practicing destructive commands such as rm -rf or fsck on a machine you cannot restore.

Read the error, then the man page

When a command fails, read the exact message. command not found is a PATH or package problem. Permission denied is ownership or mode. Then run man command and jump to the EXAMPLES section.

Build small pipelines

Connect two tools before you memorize flags in isolation: ps aux | grep ssh, du -sh * | sort -h, or journalctl -u ssh | tail. Pipes are how daily work actually looks.

How to plan your Linux CLI study

A practical sequence that works if you are new to the terminal.

01

Learn the tree and the prompt

Practice pwd, cd, and ls -l until absolute and relative paths feel automatic. Open /etc, /var/log, and your home directory on purpose.

02

Read files before you change them

Use less, head, tail, and grep on log files. Add pipes and redirection only after you can find text without them.

03

Master permission math

Memorize read = 4, write = 2, execute = 1, then explain 755, 644, and 700 out loud. Practice chmod and chown on files you created.

04

Install something and start a service

On a disposable VM, install a package with apt or dnf, then use systemctl status and journalctl to see whether it is running.

05

Drill the high-yield facts

Use the flashcards for PATH, permissions, sudo vs. su, df vs. du, and the five key files in /etc.

06

Take timed practice exams

Work through original questions, review every explanation, and return to the notes on domains below 75%.

The NodnWebTools Linux CLI study path

The overview, core notes, flashcards, and practice exams are all published.

Linux CLI hub →
Available · You are here

Overview

Scope, domains, command map, file-system layout, and a study plan for everyday Linux CLI.

Available

Core Notes

Technical reference notes for the shell, files, permissions, packages, services, and networking.

Available

Practice Exams

200 original questions with custom exams, explanations, and a score report by domain.

Frequently asked questions

Is Linux CLI Fundamentals a certification exam?

No. This is a subject-based learning path for everyday Linux command-line skills. It is not CompTIA Linux+, LPIC-1, or RHCSA, and it does not award a credential.

Which Linux distributions do these notes assume?

The notes cover commands that work on common GNU/Linux systems. Package examples use apt on Debian and Ubuntu, and dnf on Fedora and RHEL-family systems. Service examples use systemd.

Do I need a Linux computer to study?

A virtual machine, a cloud instance, or Windows Subsystem for Linux is enough. The pages do not include a command-line simulator, so type the commands on a real shell.

What does Extra mean on these pages?

Items tagged Extra are useful on the job but sit outside the everyday command set this path emphasizes, such as legacy tools like ifconfig and netstat.

How is the practice exam scored?

Scores are unofficial percentages. There is no scaled 100–900 score because this is not a named certification exam. Domains below 75% are marked as focus areas.

Command flags and default paths can differ by distribution and version. Confirm behavior with man on the system you are using.

Related Tools

Useful companions while you study.

All study topics →