NEW TO THE TERMINAL?

Learn it from the ground up.

Plain-language guides, with pictures and tables, for anyone who has never used a shell. Read them in order, or pick the one you need.

Prefer your terminal? Run explain learn.

How a Computer Works, Just Enough

What happens between your keyboard and the screen.

  1. From Keypress to Screen

    Follow one command from your fingers, through the layers of the computer, to the text on your screen.

    About 5 minutes
  2. The Computer's Body: CPU, Memory, Disk

    Meet the three parts that do the work of every command, and see why a computer needs both memory and a disk.

    About 5 minutes
  3. Firmware, Kernel, Programs: Who Is the Boss?

    Follow a computer from the power button to a running system, and learn which layer starts which.

    About 5 minutes
  4. What an Operating System Really Does

    See the jobs the kernel does for every program, and why a program must ask it before it can open a file or use memory.

    About 5 minutes
  5. Programs That Are Awake: Processes

    Learn the difference between a program and a process, how the shell starts a process, and how to list the ones running now.

    About 5 minutes

Terminal, Shell and Commands

What you are typing into, and how it becomes a result.

  1. Terminal, Shell, Command: Three Things People Mix Up

    Tell the terminal, the shell and a command apart, and see how they work together every time you type a line.

    About 5 minutes
  2. Anatomy of a Command

    Take a command line apart into its name, options and arguments, and see why quoting changes how many arguments there are.

    About 6 minutes
  3. The Map Your Shell Walks: Files and Folders

    Learn how files and folders are arranged in a tree, how to read a path, and how absolute and relative paths differ.

    About 6 minutes
  4. Words or Wiring: Text Files and Binary Files

    Learn that every file is a row of bytes, what makes a file text, and why printing a binary file gives you gibberish.

    About 6 minutes
  5. Three Streams Every Program Has

    Learn the three channels that every program starts with, where each one goes by default, and why errors travel on their own channel instead of mixing with results.

    About 8 minutes
  6. Snapping Commands Together

    Learn the symbols that send output into files and connect small commands into a pipeline.

    About 6 minutes
  7. How a Command Says Yes or No

    Learn the number every command hands back when it ends, what zero means, and how to chain commands with and without conditions.

    About 5 minutes
  8. Why "Command Not Found" Happens

    Learn how the shell uses PATH to find a program by name, what environment variables are, and why command not found does not always mean the program is missing.

    About 6 minutes
  9. Who May Read, Write, Run

    Learn the three kinds of permission, the three groups of people they apply to, and how to read and change them.

    About 6 minutes

Why Are There So Many Versions?

Where Unix, BSD, GNU and Linux came from, and why one command differs from system to system.

  1. A Short History: Unix, BSD, GNU, Linux

    Follow the story from the first Unix to the systems on your computer today, and see why the same tools come in several versions.

    About 7 minutes
  2. Who's Who: What Each Name Really Means

    Sort Unix, POSIX, BSD, FreeBSD, Darwin, macOS, GNU, Linux and BusyBox into what each one actually is.

    About 6 minutes
  3. One Command, Many Versions

    See why one command name can stand for several different programs, what a standard does and does not promise, and how to write commands that work everywhere.

    About 7 minutes
  4. Ubuntu, Debian, Alpine: What Is a Distribution?

    Learn what a Linux distribution adds to the kernel, what a package manager does, and why the choices of one distribution decide which version of a command you get.

    About 7 minutes
  5. Which Tool Do I Have?

    Find out which program a command name starts and which implementation it is, using the shell, the version flag, the file itself and the system's own name.

    About 6 minutes

Getting Things Done

Start from the result you want and pick a route to it.

  1. Needle in a Haystack: Find a Word in Many Files

    Find the lines that contain a word in one file or in a whole folder of files, and choose between grep on its own, grep with a folder, and find with grep.

    About 6 minutes
  2. Count, Sort, Summarize: Build a Small Report

    Count lines and words, sort them, and build a small report of how often each item appears, using a pipeline of sort and uniq or a single awk program.

    About 7 minutes
  3. Tidy Up: Rename and Move Files Without Losing Any

    Rename one file, move files into a folder, rename many files with a loop, and avoid overwriting a file by accident, using mv and a shell loop.

    About 7 minutes
  4. Make a Backup You Can Trust

    Make a backup of a folder by copying it, or by packing it into one archive file with tar, then restore it somewhere else and check that it matches the original.

    About 7 minutes
  5. Ask a Web Service

    Ask a web service a question with curl, read the answer and its status code, and tell a failed request from a successful one. Practice on local files first, then on the public GitHub API.

    About 8 minutes

Words You Will See

Short definitions of the words beginners meet when they start using a terminal.