Practice Use drills for recall and labs for real operating judgment.

LAB-PROC-01 - The Process Lifecycle

Inspect running processes, identify PIDs, and connect a few basic commands to the process model without needing advanced process theory yet.

PS Process Management

The Process Lifecycle

Inspect running processes, identify PIDs, and connect a few basic commands to the process model without needing advanced process theory yet.

30 min BEGINNER LINUX Field-verified
Prerequisites
Lab LAB-FS-04 - Inside /proc and /sys - The Virtual Windows
Success criteria
  • List processes and identify a PID.
  • Explain what a parent process is in a simple example.
Safety notes
  • Do not stop random system processes while learning. This lab is read-first.

Part A: The Field Guide

Processes become easier to understand once you stop treating them as invisible background magic.

This lab keeps the goal simple:

  • list what is running
  • find a PID
  • observe a child process
  • connect the command output to the mental model

Safe Default

In this lab, observe first. You do not need to kill anything to understand what a process is.

Part B: The Drill Deck

Terminal required: this lab is mostly observational.

G
Guided Step by step - type exactly this and compare the result
>

Exercise G1: Look at your current shell context

  1. Run ps
  2. Notice that you usually see your current shell and the ps command itself
  3. Identify the PID column
  4. Identify the command names shown

Exercise G2: Take a wider snapshot

  1. Run ps aux | head -n 10
  2. Notice that the list includes many more processes than the simple ps output
  3. Find one line and identify the user, PID, and command fields

Exercise G3: Create one easy target

  1. Run sleep 120 &
  2. Run jobs
  3. Run pgrep sleep
  4. Run ps aux | grep sleep
  5. Notice that different tools help in different ways
S
Solo Task described, hints available - figure it out
>

Exercise S1: Parent and child reasoning

  1. Start from your shell process shown in ps
  2. Run a short command such as sleep 5
  3. Explain how your shell acts as the parent for the command it launched

Exercise S2: Optional tree view

If pstree is available:

  1. run pstree
  2. look for your shell in the hierarchy
  3. explain what the tree is showing in simple terms
M
Mission Real scenario - no hints, combine multiple skills
>

Mission M1: Find by name, then verify by snapshot

Create one easy background target such as sleep 180 &, then:

  1. find it with pgrep
  2. verify it in ps aux
  3. explain why names alone can be ambiguous when multiple similar processes exist

If you can move between those views calmly, the process model is becoming usable.