Linux Pocket Guide (Daniel Barrett)（Z-Library）

【One-Line Pitch】 A compact, task-organized reference to the Linux commands you actually reach for at work, from file wrangling to networking and sysadmin basics. Best for beginners who need a map of the command line and experienced users who want a fast lookup desk companion. 【Book Arc】 - **Opening (~0%–10%)**: Establishes the mental model — what Linux is, how a command line is structured, who users and superusers are, and how the filesystem is laid out (absolute vs. relative paths, dot and dot-dot, home directories). Solves the "where am I and what does this syntax mean" problem before any command is used. - **Early (~10%–32%)**: Covers permissions and ownership, then moves into shell craft — environment variables, quoting, command-line editing, job control (fg, disown), and startup files like .bash_profile and .bashrc. This is the layer that makes every later command usable rather than memorized. - **Early–Middle (~29%–48%)**: The file-command core: copying, directories, viewing files (tail, strings, file, mimetype), editing with Emacs/Nano/Vim, locating files (type, whereis), and manipulating text (grep, cut, expand, sort, shuf, diff). Solves the daily reality that most Linux work is moving and reshaping text. - **Middle (~48%–60%)**: Compression, packaging, and encryption, plus conversion and comparison workflows (diff formats, pandoc-style format conversion). This is where the book shifts from single commands to small pipelines that accomplish a task. - **Late (~60%–85%)**: Sysadmin territory — superuser operations, processes, user and group management, software installation and package management, then filesystem maintenance: disks, RAID, logical volumes, and backups. The excerpts do not cover the detailed chapter contents here. - **Ending (~85%–100%)**: Networking commands (hosts, connections, email, web) and a "getting stuff done" grab bag spanning math, version control, graphics, and audio. The excerpts do not cover these chapters in detail. 【Key Takeaways】 - **Commands are documented with a consistent anatomy** (Opening): each entry shows syntax, stdin/stdout behavior, and whether it works on files, options, or both — learn this pattern once and every page becomes readable. - **The filesystem is the spine of Linux literacy** (Opening): absolute vs. relative paths, `.` and `..`, and home directory conventions explain most "why did that command go there" confusion. - **Permissions answer two questions** (Early): who has access (owner, group, world) and what kind (read, write, execute) — and the same logic applies to directories, where execute means "enter." - **Bash is a programmable environment, not just a prompt** (Early): environment variables, quoting, command-line editing, job control, and startup files are what separate a user who types commands from one who controls a session. - **Text manipulation is the real daily workload** (Middle): grep, cut, sort, tr, expand, and diff turn messy files into usable data — including fixing Windows/macOS line endings with `tr -d '\r'`. - **Diff output formats matter beyond comparison** (Middle): unified and context formats feed directly into patch and git, so choosing the right format is a workflow decision, not a cosmetic one. - **Sysadmin and filesystem maintenance are their own tier** (Late): superusers, processes, users, package installation, disks, RAID, LVM, and backups — the excerpts only sketch this territory. - **Networking and "getting stuff done" close the loop** (Ending): hosts, connections, email, web, plus math, version control, graphics, and audio — the excerpts do not cover these in detail. 【Reading Tips】 - Read Chapter 1 (Essential Concepts) end to end; it is short and everything else assumes it. Skim the command chapters on first pass and return by task. - Deep-read the file and text-manipulation sections — that is where the book earns its keep, and where pipelines are built. - Treat the command headings as a lookup grammar: syntax line, stdin/stdout flags, then options. Once internalized, you can read any entry in seconds. - Keep it next to the terminal, not on a shelf. The value is in-task retrieval, not linear completion. - For sysadmin, networking, and the final "getting stuff done" chapters, use the book as an index into manpages rather than expecting full tutorials. 【Coverage Limits】 This guide is based on stratified excerpts covering roughly the first half of the book in detail; the sysadmin, filesystem maintenance, networking, and "getting stuff done" chapters are only summarized from the table of contents and blurb, so their specific commands and examples are not covered here.