跟老男孩学Linux运维：Web集群实战 (老男孩)（Z-Library）

【One-Line Pitch】 A hands-on field guide to building and running Linux web clusters the way Chinese internet companies actually do it: start from a clean CentOS box, harden it, then assemble Nginx, MySQL, and PHP into a working LNMP stack. Best for junior-to-mid ops engineers, sysadmins moving into internet operations, and anyone who learns best by typing commands rather than reading theory. 【Book Arc】 - **Opening (~0%–10%)**: Grounds you in what Linux is, why it dominates server rooms, and the licensing history (GNU/GPL/LGPL) behind it; then walks through choosing 64-bit systems, installing VMware, and getting a CentOS machine online — including NAT vs. bridged networking and the classic "no IP after cloning" trap. - **Early (~10%–30%)**: Moves from first login to daily administration: user accounts, `su` vs. `su -`, prompt variables, SSH client tools, and server hardening (changing the default port, disabling root login, hiding version banners, firewall rules). Then pivots to web fundamentals — HTTP status codes, static vs. dynamic resources, concurrency, and why Nginx wins on static traffic. - **Middle (~30%–55%)**: The core build phase. You configure name-based virtual hosts, error logs, `location` matching rules, and password-protected sites in Nginx, then install MySQL (binary method shown) as the database layer of the LNMP stack. - **Late (~55%+ of book)**: Excerpts thin out here; the remaining material appears to continue into PHP integration, deeper MySQL operations, and cluster-level concerns, but the sampled chunks do not cover those stages in detail. - **Ending**: Excerpts do not cover the closing chapters, so no summary of the final stage can be given. 【Key Takeaways】 - **Linux's server dominance is structural, not accidental** (Opening): open source, UNIX compatibility, and no licensing constraints made it the default platform for large internet companies — context that explains why the rest of the book targets CentOS on x86 servers. - **Environment setup is where beginners actually fail** (Opening): the book spends real space on VMware networking modes, DNS resolution order, and the cloned-VM MAC/UUID conflict — practical traps that block every later exercise if unresolved. - **Security hardening is a checklist, not an afterthought** (Early): change SSH port 22, forbid root remote login, disable empty passwords, strip version info from `/etc/issue`, and restrict access by source subnet — each is a concrete command, not a principle. - **HTTP status codes are diagnostic vocabulary** (Early): knowing the five classes and the handful that appear in production lets you read `curl -I` output and locate faults fast; the book stresses simulating each code yourself. - **Static beats dynamic by 10–30x** (Early): dynamic pages consume CPU, memory, and database I/O, so "dynamic-to-static" conversion is presented as a standard high-concurrency architecture move — with the caveat that frequently updated sites risk stale content. - **Concurrency means connections, not requests** (Early): the author explicitly rejects the common "requests per second" definition in favor of maximum simultaneous connections handled per unit time. - **Choose web software by workload, then by your own skill** (Early): Nginx for static and mixed traffic, Apache acceptable when concurrency is low and you know it well — the warning against blindly adopting unfamiliar software is a recurring theme. - **Config changes require syntax check, reload, and verification** (Middle): `nginx -t`, `nginx -s reload`, then checking processes, ports, and actual responses — a disciplined loop the book repeats for every change. 【Reading Tips】 - **Deep-read the opening networking and SSH chapters** even if you think you know them; the NAT/bridged decision tree and the cloned-VM fix save hours of debugging later. - **Skim the licensing and history sections** (GPL, UNIX lineage) on a first pass — they build context but are not operationally load-bearing. - **Type every command rather than copying**, especially the Nginx virtual host walkthrough; the value is in seeing `nginx -t` fail and fixing it. - **Treat the hardening chapter as a reusable checklist** for any new server you provision, not as one-time reading. - **Note where the excerpts stop**: if you need PHP-FPM tuning, MySQL replication, or load-balancing clusters, verify those chapters exist in your copy before relying on this guide. 【Coverage Limits】 This guide is based on 22 sampled chunks concentrated in the first half of the book; the later cluster, PHP, and advanced MySQL material is only partially represented, so claims about the book's second half are deliberately cautious.