Linux System Administration for the 2020s The Modern Sysadmin Leaving Behind the Culture of Build and Maintain (Kenneth Hitchcock) (Z-Library)

# Linux System Administration for the 2020s — Reading Guide ## 【One-Line Pitch】 A practical field manual for modern Linux sysadmins who want to shift from the old "build and maintain" mindset to a culture of automation, redeployment, and minimal human intervention. Ideal for sysadmins, consultants, architects, and serious hobbyists managing anything from a handful of servers to large estates. ## 【Book Arc】 - **Opening (~0%–13%)**: The book opens with front matter and an introduction that frames the core argument—Linux administration has fundamentally changed over the last decade, and the old culture of manually building and maintaining servers is obsolete. The author sets up a four-part structure: foundations, modern tooling, platform health, and advanced troubleshooting. - **Early (~17%–33%)**: Part I covers the foundational blocks of Linux and the open source world, serving as a refresher for newcomers while establishing the vocabulary and concepts used throughout the rest of the book. This section also introduces the cultural shift toward treating infrastructure as disposable and reproducible rather than precious and hand-maintained. - **Middle (~38%–54%)**: Part II dives into strengthening core skills, with a heavy focus on task management—starting, visualizing, and killing processes, handling zombie processes, and managing background and time-consuming tasks. The section then transitions into automation with a substantial introduction to Ansible, covering installation, configuration, inventory management, playbooks, roles, and modules. - **Middle (~58%–63%)**: The book continues with estate management tooling, including web consoles like Cockpit and its alternatives, as well as text-based consoles. This portion emphasizes how modern tools reduce the cognitive load of managing many machines simultaneously. - **Late (~67%–83%)**: Part III addresses keeping platforms healthy through monitoring, logging, and security practices. The excerpts here are thin, but the structure suggests coverage of advanced tooling and techniques for identifying and resolving technical issues before they become outages. - **Ending (~88%–100%)**: The final part covers troubleshooting and advanced administration techniques, including less-known methods for resolving stubborn problems. The book closes with a summary that reinforces the central thesis: spend less time on routine sysadmin work and more time pushing the boundaries of your knowledge. ## 【Key Takeaways】 - **The "redeploy rather than fix" philosophy is the core cultural shift** (Opening): Instead of nursing a broken server back to health, modern sysadmins should treat infrastructure as disposable—rebuild, redeploy, and move on. This reduces downtime and eliminates the "snowflake server" problem where each machine has unique, undocumented quirks. - **Task management is the foundation of daily sysadmin work** (Middle): The book dedicates significant attention to process management—starting, visualizing, and killing processes, plus handling zombies and background tasks. Mastering these fundamentals is prerequisite to effective automation. - **Ansible is positioned as the primary automation tool** (Middle): The book walks through installation, configuration, inventory, playbooks, roles, and modules in sequence, treating Ansible not as an optional extra but as a core competency for the modern sysadmin. The emphasis on sharing your Ansible configurations suggests treating automation code as a first-class deliverable. - **Web consoles like Cockpit reduce the barrier to managing estates** (Middle): Modern web-based administration tools provide visibility and control without requiring SSH into every machine. The book covers Cockpit and alternatives, acknowledging that not every task needs a terminal. - **The book is structured as a progression from fundamentals to advanced practice** (Opening–Ending): Part I establishes Linux basics, Part II builds tooling skills, Part III covers monitoring and security, and Part IV tackles troubleshooting. This makes it usable both as a structured course and as a reference to dip into. - **Monitoring, logging, and security are treated as platform health concerns** (Late): Keeping a platform healthy requires proactive observation, not just reactive fixes. The book positions these as integrated practices rather than separate disciplines. - **Troubleshooting is a skill that can be systematized** (Ending): The final part promises advanced techniques and less-known methods for stubborn problems, suggesting that even troubleshooting—often seen as chaotic and experience-driven—can be approached methodically. ## 【Reading Tips】 - **Skim Part I if you're an experienced Linux user**: The foundational review is useful for newcomers but will be familiar territory for working sysadmins. Jump ahead to Part II where the modern tooling discussion begins. - **Deep-read the Ansible chapters**: This is the most concrete, actionable content in the book. Follow along with a test environment—install Ansible, build an inventory, write a playbook, and experiment with roles and modules. The value here is in doing, not just reading. - **Pay attention to the process management sections**: Zombie processes, background tasks, and time-consuming task handling are the kind of practical details that save real time in daily work. These sections reward careful reading even if they seem basic. - **Treat the book as a philosophy guide as much as a technical manual**: The cultural argument—redeploy rather than fix, automate rather than manually maintain—is the through-line. If you're managing infrastructure, consider how these principles apply to your own estate before diving into specific tools. - **Use the knowledge checks and summaries as self-assessment**: The book includes knowledge checks at the end of sections, which are useful for confirming you've absorbed the material before moving on. ## 【Coverage Limits】 The excerpted material is heavily front-loaded toward the table of contents and early chapters, so detailed coverage of Parts III and IV (monitoring, logging, security, and advanced troubleshooting) is limited in this guide. The actual book contains substantially more content on these topics than the excerpts reveal. ##