Linuxlab

Linux

A Linux textbook for engineers

Linux from system calls to production. It reads like a book, not a course.

Checking your access

Who it's for

For engineers learning or leveling up Linux for sysadmin, DevOps, SRE, or backend work. You can start from an empty terminal: no experience needed.

What you'll be able to do

  • Move around the filesystem and work with files
  • Read and edit text, and chain commands into pipelines
  • Manage users, permissions, and processes
  • Run and fix services with systemd, set up networking and SSH
  • Handle disks, filesystems, and backups
  • Understand the kernel, /proc, and performance

The four parts

From an empty terminal to senior administration. Each part opens and reads on its own.

  1. Part I. Foundations
  2. Part II. Junior administration
  3. Part III. Mid level
  4. Part IV. Senior administration

Short references for individual commands: ls, grep, find, chmod, sudo, sed, awk

How it works

You read it in the browser. Free chapters open without an account. Payment is one-time: one payment per course, with no time limit. You practice by hand in a real throwaway Linux terminal.

free chapters and pricing · the in-browser sandbox

Questions

Do I need any Linux experience to start?

No. The textbook starts from an empty terminal and asks for nothing beforehand.

Is it a one-time payment or a subscription?

One-time. One payment per course, and access to every chapter stays with no time limit.

Can I read it in the browser, and are any chapters free?

Yes. The textbook reads in the browser, and some chapters are open without an account.

What is the sandbox?

A real throwaway Linux terminal in the browser. You run the commands yourself, and the container is deleted when you leave.

Is this for DevOps, SRE, or sysadmin work?

Yes. The parts go from the basics to senior administration, which is what those roles need.

What do I need to follow along?

Any Linux system: a virtual machine, WSL2 on Windows, or a container. Or the built-in sandbox.

Who wrote it

Written by Sergei Kulnev, with input from more than ten actively working DevOps and SRE engineers.