Linux-UNIX系统编程手册（上、下册） (Michael Kerrisk)（Z-Library）

【One-Line Pitch】 A definitive, example-driven reference to the Linux/UNIX system programming interface—the system calls and library functions every program ultimately relies on. Best for working developers, porters, and advanced students who already read C and want both Linux-specific depth and POSIX portability in one place. 【Book Arc】 - **Opening (~0%–12%)**: Front matter and orientation—what the programming interface is, who the book serves, and how it is organized into eight thematic parts spanning 64 chapters. - **Early (~13%–31%)**: Background and fundamentals—UNIX/C/Linux history, UNIX standards (POSIX, SUS), core concepts, then basic interface features: file I/O, processes, memory allocation, users/groups, credentials, time, limits, and system/process information. - **Early–Middle (~25%–37%)**: Advanced interface features—I/O buffering, filesystems, file attributes, extended attributes, ACLs, directories and links, file-event monitoring, signals, and timers. - **Middle (~38%–56%)**: Processes, programs, and threads—process creation/termination, monitoring children, exec, POSIX threads, plus advanced topics: process groups/sessions/job control, scheduling, resources, daemons, secure privileged programs, capabilities, login accounting, and shared libraries. - **Late (~56%–69%)**: Interprocess communication—pipes and FIFOs, System V and POSIX message queues/semaphores/shared memory, memory mapping, virtual memory operations, and file locking. - **Ending (~69%+)**: Sockets and network programming, then advanced I/O topics—terminals, alternative I/O models, and pseudoterminals. (Excerpts do not cover the detailed content of these final chapters.) 【Key Takeaways】 - **The book documents the interface layer, not just APIs** (Early): it explains the system calls and library functions that virtually every Linux/UNIX application uses, directly or indirectly. - **Linux-specific features and UNIX standards are treated together** (Early): epoll, inotify, capabilities, /proc, and other Linux extensions sit alongside POSIX/SUS portability discussion—the book's stated standout strength. - **Examples are the teaching method** (Early): roughly 200 programs and about 15,000 lines of C and shell sessions let you run and modify code rather than only read prose. - **It works as both tutorial and reference** (Early): chapters build on prior material for sequential reading, while cross-references and an index support random lookup. - **Portability is a first-class concern** (Early): the text distinguishes standardized behavior from implementation differences and notes where examples were tested on other UNIX systems. - **Version awareness is explicit** (Early): coverage centers on Linux 2.6.x and glibc 2, with kernel/glibc version notes and SUSv3-to-SUSv4 changes flagged. - **Exercises reinforce concepts** (Early): most chapters end with exercises, some answered in an appendix, encouraging hands-on experimentation. - **The author's authority comes from man-pages maintenance** (Early): Kerrisk's long stewardship of the Linux man-pages project shapes the book's precision and bug-level detail. 【Reading Tips】 - Read the opening background chapters quickly if you already know UNIX basics, then slow down at file I/O, processes, and signals—these underpin everything later. - Treat the book as a reference after a first pass: use the index and cross-references when you hit a specific API in real work. - Actually compile and run the example programs; the author explicitly recommends modifying them or writing new code to consolidate understanding. - Pay attention to the small-print annotations—they carry rationale, implementation details, and historical context that clarify why interfaces behave as they do. - For portability work, note the standard-versus-Linux distinction markers; for Linux-only work, deep-read the epoll, inotify, capabilities, and /proc material. 【Coverage Limits】 The excerpts cover front matter, preface, table of contents, and acknowledgments; they do not include the actual technical chapters, so this guide describes the book's scope and approach rather than its detailed API content.