Public deck

Linux and the Command Line for Engineers

The Linux that cloud, DevOps and security engineers use every day on a modern systemd and bash system: files and permissions, processes and services, shell scripts, text tools, disks and finding performance problems.

Engineering

AShared by Alex Chen

0 Play Sign in to clone

You’re reading a free preview. Sign up to see every topic and question — and to play this deck as games.

See the whole deck

Suggested order

Arrows point from what to learn first. Topics side by side can be studied in any order — and cloning the deck brings this order with it.

Topics

Open a topic to read through its content, then play just that topic.

The Filesystem: Hierarchy, Paths and Links

Where things live on a Linux system, how absolute and relative paths work, and how inodes, hard links and symbolic links relate to each other.

Users, Groups and File Permissions

How Linux decides who can read, write and run a file: users and groups, rwx and octal modes, umask, ownership, the special bits and sudo.

Processes, Signals and Job Control

How Linux runs and tracks programs: process IDs, parents and children, signals such as SIGTERM and SIGKILL, background jobs, zombies and orphans.

Locked · 43 questions inside

systemd, Services and Logs

How systemd starts and supervises services on a modern Linux system: units and unit files, systemctl, dependencies, timers and reading logs with journalctl.

Locked · 43 questions inside

Shell Scripting: Variables, Quoting, Exit Codes and Redirection

Writing bash scripts that behave predictably: quoting, exit statuses, strict mode with set -euo pipefail, redirection, here-documents, tests and loops.

Locked · 43 questions inside

Text Processing: grep, sed, awk, sort, cut and xargs

The standard tools for searching, editing, slicing and counting text on the command line, and how to chain them with pipes.

Locked · 43 questions inside

Packages, Disks and Filesystems

Installing software with apt and dnf, and how disks, partitions, filesystems, mounts, /etc/fstab and LVM fit together.

Locked · 43 questions inside

Performance and Troubleshooting

Finding out why a Linux server is slow or failing: CPU, memory and disk tools, load average, the page cache, the OOM killer and tracing tools such as strace and lsof.

Locked · 43 questions inside

6 more topics in this deck

Create a free account to open every topic — and play the whole deck without copying it.