Operating Systems

Featured post

2026.04.04 17 min read 🎯Docs 📚 Complete Guide to Linux Shell Execution Linux Shell Operating Systems

Complete Guide to fork and exec in Linux — How the Shell Executes Programs

This post explains how a shell actually runs commands through fork and exec. Instead of executing programs directly, the shell creates a new process, replaces it with the target program, and keeps itself alive to continue controlling execution.

Latest posts

2026.03.30 15 min read 🎯Docs 📚 Complete Guide to Linux Shell Execution Linux Operating Systems DevOps

Complete Guide to Linux Signals — SIGINT, SIGTERM, and the Principles of Process Control

Signals are not just a way to kill processes. They are the core mechanism for controlling process lifecycle in Linux. This article explains how SIGINT, SIGTERM, and SIGKILL differ, and why graceful shutdown matters in real systems.

2026.03.28 17 min read 🎯Docs 📚 Complete Guide to Linux Shell Execution Linux Shell Operating Systems

Complete Guide to Linux Shell Execution — How Programs Are Executed and Controlled

The Linux shell is not just a simple command executor. This article organizes the entire execution flow—from interpreter resolution and process creation to foreground/background execution, job control, signals, PATH, and environment variables—into a single, cohesive structure.

2026.03.27 7 min read 🎯Docs 📚 Linux I/O and Data Flow — From Streams to Pipelines Linux Shell Operating Systems

Linux Everything is a file Meaning — What “Everything is a file” Really Means with Examples

“Everything is a file” is not a metaphor but a core design principle in Linux. This post explains how files, devices, processes, and streams are unified under a single interface, with practical examples that reveal how redirection and pipes actually work.

2026.03.22 15 min read ⚙ Essays 📚 The Unix Design Story Behind Small Commands Unix Operating Systems Unix Philosophy

Everything Is a File — Why Unix Turned the World into Files

Unix has a famous philosophy: **“Everything is a file.”** Not only disk files, but terminals, pipes, and network sockets are treated the same way. This simple design shaped the entire Unix system. This article explores why Unix adopted this model and how it still influences modern software.