View Categories

Linux Must-Knows for Infrastructure Engineers

1 min read

Modern tools are masterpieces of abstraction. With a single command, we can deploy global applications in seconds. However, this convenience comes with a dangerous trade-off, it blinds us to the operating system beneath.

This article is not a cheat sheet of basic commands like cd or ls for you to blindly memorize. Instead, i will strip away the modern abstraction layers to examine the foundational Linux concepts that power everything.

Chapter 1: The Foundations & Architecture #

This section covers how the operating system splits its power and boots up.

  • User Space vs. Kernel Space: The fundamental separation between safe user applications and the privileged core OS.
  • Boot & Init: How the Linux kernel takes control of hardware and triggers the very first process.
  • Systemd & Services: Modern Linux initialization, service management, and dependency tracking.

Chapter 2: Compute, Processes & Lifecycle #

This section explains how Linux executes code and manages application lifecycles.

  • Threads vs. Processes: The structural difference between independent memory isolation (processes) and shared execution spaces (threads).
  • Signals: The communication events (like SIGTERM and SIGKILL) used to control processes from the outside.

Chapter 3: Storage, Filesystems & I/O #

In Linux, everything is a file. This section handles data persistence and stream boundaries.

  • File System (UFS): The underlying structure and hierarchy used to layout data permanently on physical disks.
  • File Descriptors (Sockets, Stdin/Stdout/Stderr): The standard integer handlers Linux uses to track all active data streams, input/output pipelines, and open files.
  • Mounts: How external storage drives or virtual file systems are attached to the main directory tree.
  • Disk I/O: The performance metrics, queues, and constraints of reading from and writing to hardware storage.

Chapter 4: Cloud Native Virtualization #

The exact underlying kernel technologies that make containerization (Docker/Kubernetes) possible.

  • Namespaces: The isolation mechanism that hides system resources (Network, PID, Mounts) per process to create a virtual firewall between containers.
  • Cgroups (Control Groups): The resource allocation engine used to strictly limit and meter CPU, Memory, and Disk access for a given container.
  • UnionFS & OverlayFS: The copy-on-write storage engines that allow Docker to stack immutable image layers on top of each other, creating a lightweight, unified filesystem for every running container.

Chapter 5: System Resources & Networking #

The pipes and memory management driving raw application performance.

Linux Memory & Memory Management #

How the kernel handles RAM allocation, swap space, caching, and protects processes from stepping on each other’s memory.

Networking #

Here, we look at how the Linux kernel implements transport and routing protocols, and how it maps applications to network sockets. I previously covered the high-level networking theory in my Computer Networking 101 and Understanding HTTPS & SSL Certificates articles.

Powered by BetterDocs

Leave a Reply