A notebook for understanding the systems underneath
A starting point for connecting Linux, operating systems, and networking through hands-on learning.
Starter content: an introductory example for this new notebook, not a record of completed personal work.
Start with a question
What happens after you type a command and press Enter? The shell interprets the command, the operating system manages its execution, and the program may interact with files, memory, or the network. Each layer offers a new question to investigate.
This notebook starts with those questions. The aim is to connect an explanation to something observable: a process tree, a system call trace, a request, or a small program.
A repeatable learning loop
- Describe what you expect to happen.
- Try the smallest experiment that can test that expectation.
- Record the environment, commands, and output.
- Explain where the observation matches or changes your model.
- Leave the next question visible.
Build a body of evidence
A useful engineering profile can grow from a collection of careful explanations and reproducible work. An experiment that failed, with a clear diagnosis, can be as informative as one that worked immediately.
The proposed twelve-week journey provides structure. The notebook provides space to slow down when a concept deserves more attention.