Why Learn Linux? Kernel Internals, Unix Philosophy, and a Production Rescue Story

The Production Incident: Zombie Processes and a Stopped Init

Several years ago, the author joined an operations team managing thousands of physical and virtual machines. One night, servers began crashing in batches. Colleagues spent the night rebooting machines, but they kept crashing again. The author arrived next morning to find the whole company — ops, dev, security, QA, and leadership — gathered in conference rooms.

Chat logs revealed a clue: massive numbers of Salt (configuration management) zombie processes. Since Salt was managed by ops, the blame fell on the ops team. The author recognized the pattern: zombie processes persist until their parent calls wait() to collect the exit status and release the PID. If the parent dies first, the orphan is reaped by init (PID 1).

Checking a surviving server with ps, the author saw all zombie processes had init as parent — but init was in T (stopped) state, meaning someone had sent it SIGSTOP. On the ancient CentOS 6 (kernel 2.6.32), SIGSTOP could indeed stop init. With init paused, no one reaped zombies; Salt's frequent data collection caused zombies to accumulate until the PID space exhausted, crashing the system.

The fix was simple: sudo kill -s SIGCONT 1 to resume init. The author tested on a few machines; zombies vanished immediately. The boss verified, then rolled out the command fleet-wide, stabilizing the cluster. Post-incident review traced the SIGSTOP to a security scanner update deployed the previous day — the scanner was stopping init during scans.

Philosophical Interlude: The Pygmalion Effect and OS Assumptions

The author shifts to a reflective essay, citing the 1963 Rosenthal–Jacobson Oak School experiment (

@book{pygmalion, title={Pygmalion in the Classroom: Teacher Expectation and Pupils' Intellectual Development}, author={Rosenthal, R. and Jacobson, L.}, year={1968}, publisher={Holt, Rinehart and Winston}}

). The "Pygmalion effect" shows expectations shape behavior.

Linux assumes users know what they want, understand their actions, and take responsibility. Windows assumes the opposite. This isn't a value judgment — it's a design premise. If the Pygmalion effect holds, Linux users gradually learn to think independently, act deliberately, and own outcomes. That is the "free" in free software: freedom as responsibility.

Linux is user-friendly, it's just very selective about who its friends are.

The author dismisses the idea that switching OS brings instant career success (a humorous suitor-laptop anecdote) and argues the "which OS is better" debate is meaningless — like arguing sweet vs salty tofu pudding. The right tool fits the user. Linux users will remain a minority because "freedom is a burden most dread" (George Bernard Shaw) and "unless a man has talents to make something of himself, freedom is an irksome burden" (Eric Hoffer).

Pragmatic Criteria for an OS

The author, a self-described reformed zealot, now evaluates OSes by three practical criteria:

User autonomy : The user decides how the system works, not vice versa. No forced updates or mandatory reboots. The OS is a hired assistant; the user is the owner. This implies deep customizability.

User informed : The user can inspect any system detail, not just be told "processing something."

System efficiency : Tools are readily available and composable for complex workflows.

Linux satisfies all three; Windows satisfies none.

Why Linux Is Unavoidable for Engineers

An analogy: if a car has stable performance, excellent design, open technical specs, and countless detailed teardown guides, any automotive engineer must study it. Linux is that car.

Free, stable, vast open-source ecosystem.

Inherits Unix philosophy: each tool does one thing well (sort, filter, count). Complex tasks are built by piping tools together ( |) and I/O redirection, unlike monolithic Windows apps.

Transparent filesystem hierarchy: /tmp for temporaries, /etc/hosts for local IP mapping, /usr/bin for executables, /usr/lib for libraries. Package managers handle install/uninstall.

Organized man pages: one command documents tools, syscalls, library functions, drastically reducing search time.

Using Unix will change how you think, and for the better. I believe that if you learn how to read Shakespeare, listen to Mozart, or appreciate the paintings of Van Gogh, you will, in some sense, be a better person. The same is true for learning how to use Unix. 使用 Unix 可以改变你的思考方式, 很可能是改进。我相信如果你阅读莎士比亚的戏剧，听莫扎特的音乐，听梵高的画作，会让你从某种意义上讲变成一个更好的人。学习 Unix 也同样如此。

Source: Zhihu question 20117703