This beginner course teaches you to collect and interpret essential Linux system information from the terminal. Across five guided labs, you will examine system identity, memory and swap, filesystem and directory usage, CPU load trends, and continuously changing command output.
The final challenge turns these checks into a concise manual audit: you will append hostname, kernel, uptime, memory, and root-filesystem data to a single health_check.txt report.
What You Will Learn
- Identify the kernel with
unameand the Linux distribution through/etc/os-release - Read uptime and the 1-, 5-, and 15-minute load averages
- Compare load averages with the CPU count reported by
nproc - Interpret total, used, free, cached, and available memory with
free -h - Check configured swap space with
swapon --show - Compare filesystem capacity from
df -hwith directory and file usage fromdu - Re-run commands with
watch, highlight changes with-d, and stop monitoring with Ctrl+C - Assemble a system health report by appending command output with
>>
Who This Course Is For
This course is for Linux beginners, support technicians, and aspiring system or DevOps administrators who need a repeatable first-pass view of system identity and resource health.
Prerequisites: Basic terminal navigation, command execution, pipes, and output redirection; no prior monitoring experience is required.
Learning environment: A provided Ubuntu-based LabEx terminal with prepared log files and a project workspace for resource checks and the final audit report.
Frequently Asked Questions
How is the course structured?
Five labs provide guided practice. The sixth item is a final challenge where you create ~/project/health_check.txt and append system identity, uptime, memory, and root-filesystem output with less guidance.
Does a low value in the free memory column mean the system is out of RAM?
Not necessarily. Linux uses otherwise idle RAM for cache. The course teaches you to consider the available value, which better reflects memory that can be used without heavy swapping.
What is the difference between df and du?
df reports capacity and usage from the filesystem's perspective, while du measures the space consumed by directories and files. The labs use both to move from a full filesystem toward the content occupying it.
Is a load average above 1 always a problem?
No. Load must be interpreted relative to CPU core count and workload context. The course uses comparison with nproc as a beginner rule of thumb, not an absolute diagnosis.
