Start here

A little preparation.
A much better way to learn.

You do not need to be a system administrator to begin. You need a Linux terminal, a space to practise and a willingness to check your results.

1. Choose a place to practise

Use a disposable Linux virtual machine for the broadest course experience. Keep it separate from work servers and take a snapshot before administration experiments. Use a normal user account; the core labs do not require root.

On Windows, WSL can provide a Linux terminal for the foundations exercises. Work inside its Linux home directory so file permissions behave as expected. Service-manager exercises depend on the actual WSL configuration; where systemd is unavailable, use the included offline evidence instead. WAMP is suitable for hosting this PHP website, but Windows Command Prompt is not a Bash terminal.

Already using Linux? A dedicated practice directory in your home folder is enough for most lessons. The networking, SSH and mail case studies include fictional evidence so you can learn the diagnostic method without deploying real servers.

2. Know which environment you have

Open your Linux terminal and run these read-only checks. Type only the command, without a leading prompt marker.

pwd
id
uname -s
cat /etc/os-release

Record your distribution and version. Package managers and service tools differ: do not run every distribution example as one script. The lesson environment note tells you when Bash, procps, iproute2, systemd or OpenRC is relevant.

3. Use the learning loop

  1. Understand: read the explanation and say what the command is meant to achieve.
  2. Observe: work through the example and explain the output.
  3. Practise: run the supplied setup in your own lab, then attempt the task before opening the hint.
  4. Check: compare your work with the stated success criteria. Different valid approaches are welcome.
  5. Recall: answer the quiz, review the explanations and save your reading and practical checklist.

The website does not run terminal commands or verify your computer remotely. Your practical checklist is your own confirmation; quiz answers are marked on the server.

4. Pick your starting point

“I am new to the terminal.”

Start with safe navigation, files, text streams and permissions.

Linux Foundations →

“I know the basics, but want to manage a machine.”

Learn package inspection, processes, services and a verified backup workflow.

Everyday Administration →

“I want to diagnose service problems.”

Practise collecting evidence across networking, DNS, SSH and mail.

Network & Service Troubleshooting →

5. Choose a specialist path when you are ready

After the foundations, follow the task you want to practise: use Git & Version Control for repeatable changes; Performance & Capacity Troubleshooting for slow systems; Storage & Filesystems for mount and capacity questions; Users, Permissions & Access Control for access reviews; Logging, Monitoring & Observability for incident evidence; Networking & Firewalls for packet-path reasoning; Database Operations Fundamentals for safe data handling; or Infrastructure as Code & Configuration Automation for repeatable deployments. You can browse all paths from the learning library without completing them in a fixed order.

When an example behaves differently

Check your current directory, quoting, spelling and distribution first. Read the error message instead of immediately adding sudo. Check whether the required utility is installed and consult its local manual. BusyBox tools may provide fewer options than their GNU counterparts.

Where a lesson uses fictional evidence, analyse the supplied file rather than trying to connect to its example addresses. Never enter a real password or private key into a lesson or progress form.

For installation details, use your distribution’s official documentation or the Microsoft WSL installation guide.