Opens in a new tab
All learning paths

Path 02 / Learning syllabus

Linux basics

Learn to operate a Linux system by building, running and troubleshooting a small service in a disposable practice environment.

13 lessons planned1 available guide
Explore the syllabus
Inside the syllabus / first three lessons
  1. 01
  2. 02
    Read commands and find helpComing soon
  3. 03
    Navigate, edit and manage filesComing soon
First exerciseCreate a small lab record, stop the machine and verify that the record survives a restart.

Your course project

A working Linux service

Use one disposable Ubuntu lab throughout the path. Start with a lab record, then build and troubleshoot a small HTTP service. Learn editing, backup and rollback before changing service configuration.

Before you begin

Start with the foundations.

For technically curious beginners. No prior Linux or command-line experience is required.

Each exercise states what you need and how to check its result. Use practice data and a disposable lab.

The ordered path

What you will learn

Follow the order, or open the guide that answers your question. Lessons marked Coming soon are not available yet.

  1. 01
    Available guide · 6 min read

    Set up a safe Linux lab

    Use a disposable environment and identify the distribution, shell and current user.

    What you will try

    Create a small lab record, stop the machine and verify that the record survives a restart.

  2. 02
    Coming soon

    Read commands and find help

    Understand arguments, options, quoting, globbing, command history and manual pages before running unfamiliar commands.

    What you will try

    Explain a command before executing it and find its documented behavior.

  3. 03
    Coming soon

    Navigate, edit and manage files

    Work with paths, directories, files and links; edit a small file, keep a backup and understand deletion.

    What you will try

    Edit the project’s sample configuration, compare it with its backup and restore the original.

  4. 04
    Coming soon

    Read, search and transform text

    Use pipes, redirection, filters and search to answer a concrete question.

    What you will try

    Extract failed requests from the project’s synthetic request log.

  5. 05
    Coming soon

    Users, groups and permissions

    Explain ownership, access checks, sudo and executable permissions.

    What you will try

    Diagnose a deliberately unreadable project file without making it world-writable.

  6. 06
    Coming soon

    Processes, signals and the shell

    Find running work, inspect exit codes and environment variables, and stop a process deliberately.

    What you will try

    Locate the project process, explain its environment and observe a failed command’s exit status.

  7. 07
    Coming soon

    Install and configure software

    Connect packages, versions, configuration files and supported update methods.

    What you will try

    Record the installed package version and preserve a configuration before changing it.

  8. 08
    Coming soon

    Services and logs

    Start a service, inspect its configuration and explain a startup failure.

    What you will try

    Repair a sample service configuration, roll it back and verify its behavior from logs and a request.

  9. 09
    Coming soon

    Storage and filesystems

    Distinguish filesystem layout, mounts, capacity, inodes and open deleted files.

    What you will try

    Explain a space problem using filesystem and process evidence.

  10. 10
    Coming soon

    Networking and DNS

    Follow a request through name resolution, routing, listening ports and connectivity.

    What you will try

    Separate a failed name lookup from a service that is not listening.

  11. 11
    Coming soon

    Connect securely with SSH

    Understand keys, host verification, remote commands and common connection failures when the project moves to a remote lab.

    What you will try

    Verify the lab’s host identity and establish a connection using a dedicated practice key.

  12. 12
    Coming soon

    Diagnose resource pressure

    Identify CPU, memory, disk I/O and capacity constraints using evidence.

    What you will try

    Use a bounded lab workload to explain which resource is constrained.

  13. 13
    Coming soon

    Investigate a broken service

    Diagnose and repair a failure, then verify recovery and preserve a useful investigation record.

    What you will try

    Recover the project service, demonstrate a successful request and explain the evidence behind the fix.