What Is Linux and Why DevOps Engineers Need It?

1. Linux is a kernel—and an ecosystem

Strictly speaking, Linux is the kernel: the privileged core that manages CPU time, memory, devices, processes, filesystems, networking, and security boundaries. In everyday engineering language, “Linux” usually means a complete operating system assembled around that kernel.

flowchart TB
  U["Users and automation"] --> S["Shells, APIs, and applications"]
  S --> T["System tools, libraries, and services"]
  T --> K["Linux kernel"]
  K --> H["CPU, memory, disks, network, and devices"]
  P["Distribution packages and policies"] -. assemble .-> S
  P -. assemble .-> T
  P -. configure .-> K

2. Why Linux is foundational to DevOps

DevOps work crosses development, delivery, infrastructure, security, and operations. Linux appears at nearly every boundary:

You do not need to memorize every command. You need a repeatable operating method: inspect state → form a hypothesis → make one controlled change → verify the result → preserve evidence.

3. The anatomy of a Linux environment

4. Your first inspection commands

These commands are intentionally read-only. They establish identity, environment, kernel, distribution, location, and filesystem context.

# Who am I and where am I?
whoami
id
pwd

# Which kernel and operating-system release am I using?
uname -a
cat /etc/os-release

# Which shell is running, and what is available here?
printf 'Configured login shell: %s\n' "$SHELL"
ps -p $$ -o pid,ppid,comm,args

# What is in the current directory?
ls -lah

Interpret the output, do not merely collect it

• whoami prints the effective username.
• id shows numeric identity, primary group, and supplementary groups.
• uname -a describes the running kernel—not necessarily the distribution release.
• /etc/os-release identifies the distribution and version in a machine-readable format.
• ps -p $$ inspects the process represented by the current shell’s process ID.

5. Hands-on lab: produce a Linux environment report

Create a directory for course labs, capture a small environment report, and review it. The lab uses no elevated privileges.

mkdir -p "$HOME/devops-academy/linux/chapter01/lesson01"
cd "$HOME/devops-academy/linux/chapter01/lesson01"

{
  printf '=== identity ===\n'
  whoami
  id

  printf '\n=== kernel ===\n'
  uname -a

  printf '\n=== distribution ===\n'
  cat /etc/os-release

  printf '\n=== shell process ===\n'
  ps -p $$ -o pid,ppid,comm,args

  printf '\n=== location ===\n'
  pwd
} > environment-report.txt

less environment-report.txt

The output redirection operator > creates or replaces the report file. Later lessons will cover streams, redirection, permissions, and safe scripting in detail.

6. Choose your course lab environment

7. Common beginner misconceptions

8. Knowledge check

9. Summary

Linux is the operating foundation of much of the DevOps ecosystem. The kernel manages resources and isolation; distributions assemble a complete system; shells and utilities expose that system to humans and automation. Your goal is not command memorization—it is disciplined observation, controlled change, verification, and recovery.

10. Further reading

• The Linux Kernel documentation — architecture and subsystem references.
• The Linux man-pages project — system calls, library functions, commands, and file formats.
• Filesystem Hierarchy Standard — conventional Linux directory structure.
• GNU Bash Reference Manual — shell language and interactive behavior.
• systemd documentation — boot, services, logging, and system management.