Book · 2010
The Linux Programming Interface
by Michael Kerrisk
A 1,500-page tour of every Linux system call, written by the man who maintains the manual pages.
What does Reddit think of The Linux Programming Interface?
That divide is described as a career fact, not a compliment. r/learnprogramming and r/AskProgramming are neutral, occasionally pointing newcomers here as a C companion rather than a primary resource. Nobody calls it optional for systems work.
Community feedback & reader fit
Themes
- · Linux system calls and POSIX interfaces
- · Process management: fork, exec, signals, and IPC
- · File I/O, pipes, and filesystem internals
- · Memory management and the C runtime
- · Concurrency and the gap between theory and production systems
Common praise
- + The process and syscall chapters close the gap between knowing Linux commands and understanding what the kernel is actually doing.
- + r/devops commenters reach for it specifically when a job requires real IO, memory, network, and filesystem depth — not just shell fluency.
- + The book teaches you what open() flags do, and experienced devs on Reddit say that alone separates two distinct cohorts of engineers.
- + Works as a reference you crack mid-project, not just a cover-to-cover commitment.
Common criticism
- − At over 1,500 pages it is not a book you finish; it is a book you survive, which r/compsci treats as a structural flaw rather than a feature.
- − Mention volume dropped sharply after 2023 — 1 mention in 2024, 1 in 2025 — suggesting newer systems programmers are routing around it.
Who it's for
You already write C and you want to stop pretending you understand what happens below malloc. Backend engineers who keep hitting walls with signals, file descriptors, or process lifecycle will find this fills the exact holes. If you work in devops and your company distinguishes between 'good with the command line' and 'understands how Linux actually works,' this is the book that crosses that line. Not useful as a first programming book, and r/learnprogramming treats it that way — it appears there mostly as a pointer for people who already know they need it.
Mentions over time
Top subreddits
Which Reddit comments matter for The Linux Programming Interface?
Top-upvoted quotes across the subreddits where this book is mentioned. Click through to read the full thread.
“How processes work (fork/exec, io, pipes, proc, etc). It took a while for it to really click. It's one of those things that divides developers into two camps I'll also throw really basic syscalls in here. Like learning the flags to open and read. Even just learning them once can be eyeopening. I sh…
“1. How "good Linux knowledge" is defined? If it's good with hands-on command line knowledge, that's one thing, but if the company requires real deep understanding of Linux kernel, how does it work with IO, memory, network, filesystems, users, I can definitely recommend "Linux Programming Interfaces"…
“Learning C is about getting to know the machine, OS at a deeper level. It is about how the execution environment, networking, etc have been modeled? Once you know those things, learning higher level stuff becomes easier. A lot of people, like myself, get hung up on the abstractions being used at th…
“I can't speak to the book you're talking about (I assume you mean this one). But, if you want to learn both the theory and the practice of Unix systems programming, from assembly language to memory management (including how to implement your own version of `mall…
“One benefit of being a linux kernel developer is that your code will be used by many people. There is personal satisfaction in such having contributed in such a way. ​ On a more direct level, being a linux kernel developer will mean you most likely understand how the linux programming inter…
“Looks like it has an answer here::-) >What prerequisite knowledge do I need to read TLPI? > The following will suffice: > A reading knowledge of C (or C++). I tend to avoid esoteric features of C in my code examples, so it is not nece…
“books are great. read outside of your skillset too. look for the ones with implementation details over the purely theoretical. most importantly try to implement the ideas you encounter, use docker to load up system components locally etc. *software application design:* evolutionary architecture …
“From a programmer’s perspective, the books from W. Richard Stevens are great. “Advanced Programming in the Unix Environment” covers traditional Unix systems programming, extending to networking. “Unix …
Convinced? Pick up The Linux Programming Interface
What else does r/ExperiencedDevs read?
Other books mentioned in the same sub, ranked. Shared-sub overlap with this title breaks ties.
Designing Data-Intensive Applications
Martin Kleppmann
A backend engineer's field guide to the tradeoffs behind every database, queue, and distributed system you will ever touch.
The Pragmatic Programmer
Andy Hunt
Two veterans hand you a checklist for the craft: don't write code you don't need, own your tools, and fix the broken window before someone else does.
The Mythical Man-Month
Frederick P. Brooks Jr.
Fred Brooks spent the 1960s building IBM's OS/360 and wrote down everything that went wrong — in 1975, and it still lands.
A Philosophy of Software Design
John Ousterhout
A Stanford professor's 200-page rebuttal to Clean Code, built on interface depth rather than method length.
The Manager's Path
Camille Fournier
A software engineer picks up a management role and finds out — via 142 Reddit mentions — that nobody told them about the crying, the firings, or the 90-day onboarding clock.
The Phoenix Project
Gene Kim
An IT manager inherits a failing project, a mutinous ops team, and a CEO deadline — and has to ship before the company does.
The Linux Programming Interface — frequently asked
Is The Linux Programming Interface still relevant in 2026?+
Mostly yes, with caveats. The POSIX interfaces it covers have not changed materially, and r/devops commenters as recently as 2023 recommended it for roles requiring kernel-level Linux knowledge. The mention curve has flattened — 1 mention each in 2024 and 2025 after 6 in 2022 — which suggests it is less discovered by newcomers but still cited by practitioners who know what they need.
What does Reddit actually think of The Linux Programming Interface?+
Depends which subreddit. r/devops is the most positive of the five tracked communities, recommending it when deep IO, memory, and filesystem understanding is the job requirement. r/ExperiencedDevs cites it matter-of-factly as the book that explains why fork/exec knowledge divides developer cohorts.
Do I need to know C before reading The Linux Programming Interface?+
Yes. The book's own FAQ says a reading knowledge of C suffices, and r/compsci commenters who bounced off it confirm the assumption is real. r/learnprogramming mentions it as a destination, not a starting point — something to come back to after C is comfortable. Trying to learn C and TLPI simultaneously is not a strategy the Reddit data supports.
How does The Linux Programming Interface compare to just reading man pages?+
The man pages are what the author maintains; the book is the explanation behind them. r/ExperiencedDevs commenters describe it as the resource that makes the flags to open() and read() suddenly click — the kind of thing, one ↑64 comment notes, that you only need to learn once but that divides developers permanently. Man pages tell you what; this tells you why.