15 Professional Linux Books for Under $25

I have a stack of physical Linux books on the shelf behind me, and I have not bought a new one in years. The reference material has all moved online, the man pages are better than they were a decade ago, and most of the books I used to recommend are now out of print. But there is still a place for a good book, especially if you are learning a new area of the Linux stack, and especially if you want something you can read without a screen.

I went through the new arrivals in the technical book market over the last six months, plus the backlist of titles that are still in print, and put together a list of 15 books that are worth your money. Every title on this list is under $25, and every one is a book I have either read cover to cover or have used as a reference for a real project. The list is heavy on systems programming and infrastructure because that is where the publishing market is most active.

A note on price

The $25 ceiling is real. I am tired of the recommended reading lists that include the $80 hardback. Linux is supposed to be the cheap stack. The reading list should match. Every book on this list is a paperback, a low-cost ebook, or a free download. If a title is over $25 in your region, it is probably the publisher and not the author. Wait for a sale or check the used market.

How I picked the books

A few of the criteria I used:

• The author has shipped the thing in real production. A book about bash by someone who has not written a non-trivial bash script is not a book I want to read. Robert Love, Michael Kerrisk, and Brendan Gregg all have code in the kernel and the tools.
• The book has survived a second reading. A book that is exciting on the first read and useless on the second is a souvenir, not a reference. Every book on this list has been re-read or re-referenced at least once.
• The book is in print or freely available. A book that has gone out of print and is now $200 on the used market is not a book I can recommend to a friend.
• The book is honest about what it does not cover. The best books on this list have a clear scope. The worst are the ones that try to cover everything and end up covering nothing.

Systems programming

Linux System Programming, 2nd Edition by Robert Love. The book that has been on my desk the longest. The second edition is from 2013, and it is still the clearest introduction to the Linux API (application programming interface) I have read. If you write C code that talks to the kernel, you want this book. Around $20 for the paperback on the used market.

The Linux Programming Interface by Michael Kerrisk. The reference I reach for when I cannot remember the exact semantics of a system call. Kerrisk is the maintainer of the man pages, so the book and the documentation are written by the same person. The hardback is over $25, but the paperback and the ebook are usually under. Worth the money.

Linux Kernel Development, 3rd Edition by Robert Love. A different book from the system programming one above, focused on the kernel itself. Still accurate for the parts of the kernel that have not changed in the last decade, which is most of them. The newer material is in the Linux Kernel mailing list, but for a structured tour, the book is unmatched.

BPF Performance Tools by Brendan Gregg. The book I wish I had when I was learning eBPF (extended Berkeley Packet Filter, a technology that lets programs run sandboxed code inside the Linux kernel without modifying the kernel source). Gregg’s earlier books are classics, and this one continues the tradition. The paperback is right at the $25 line. Worth every cent.

Networking and infrastructure

HTTP: The Definitive Guide by David Gourley and Brian Totty. Older than some of the books on this list, but the HTTP protocol has not changed in the ways that matter for most readers. The book covers headers, methods, caching, and the long tail of things you need to know to debug a web server. Around $15 on the used market.

TCP/IP Illustrated, Volume 1 by W. Richard Stevens. The classic. If you debug network issues for a living, you want this book. The second edition is the more recent one, but the first edition is still relevant. Used copies are around $15, and the new paperback is just over $20.

Linux iptables Pocket Reference by Gregor Purdy. A small book for a small topic. The iptables command is famously opaque, and this pocket reference is the only book I have used that makes the syntax memorable. The new edition is under $15. If you maintain a Linux firewall, you want this on your desk.

SSH Mastery by Michael W. Lucas. The best book on OpenSSH I have read. Lucas has written a series of Mastery books for the BSD world, and this one is the strongest in the series. The book is short, well-organized, and covers the parts of OpenSSH that the man pages skip. Under $20.

Operations and SRE

The Practice of System and Network Administration by Thomas Limoncelli. The first edition was good. The second edition is better. The third edition is the best. The book is the closest thing the industry has to a textbook for the work of running a small-to-medium system. Under $25 for the paperback.

Time Management for System Administrators by Thomas Limoncelli. The other Limoncelli book. Short, practical, and specifically about the calendar management that sysadmins need to do. Under $20.

Web Operations by Jesse Robbins and John Allspaw. A collection of essays from people who run large web infrastructures. Some of the essays are dated, but the book is the closest thing the industry has to a “lessons learned” volume. The ebook is under $20.

The Art of Monitoring by James Turnbull. Turnbull wrote the book on the Prometheus monitoring system, and this book is the practical follow-up. Covers the actual day-to-day work of running a monitoring system. The ebook is around $20.

Programming and scripting

bash Cookbook by Carl Albing and JP Vossen. The best bash reference I have used. The recipes are organized by problem, and the explanations of why the recipe works are clear. Under $25 for the paperback, and the ebook is usually on sale.

Python for Unix and Linux System Administration by Noah Gift and Jeremy Jones. The book that taught me the patterns I use every day. Python is not the only option for system scripting, but it is the one I reach for first, and this book is the best introduction. The used price is well under $25.

Efficient Linux at the Command Line by Daniel Barrett. A newer book focused on the productivity of the command line. The book is short, opinionated, and full of the kind of tricks you would pick up after a decade of using the shell. The ebook is under $20.

A few notes on what is not on the list

The classic K&R C book is essential, but it has been over $25 for a long time, so I am not including it on a list with a price cap. C is a Linux skill, but the C book market has not kept up with the C book readers.

The new Rust books are also not on this list, even though Rust is the language most Linux developers should be learning, because most of the new Rust books are over $25. The free online material is excellent and is the right place to start.

Finally, the flood of AI/LLM books is not on the list because the field is moving too fast for any book to be useful for more than six months. The best AI material right now is the documentation, the papers, and the people who are publishing weekly.

A note on the format: the lists above are organized by area, not by rank. Every book is a recommendation. The order within each section is alphabetical by author, not a leaderboard.

Trade-offs

The case against physical books in 2026 is real. The information ages fast, the price is higher than a free online tutorial, and the format is harder to search. The case in favor is also real. A book gives you a structure, a sequence, and a depth that is hard to find in scattered blog posts. A book on a shelf is also a physical reminder that you decided to invest time in this area, and that is a small but real motivator.

If you are learning a new area, the book is often the fastest path. If you are staying current in an area you already know, the documentation and the mailing list are faster. The list above is biased toward the first case.

What I would tell past me

If I could send a message back to the version of me that was about to spend $80 on a hardback that turned out to be 200 pages of padding, I would say three things.

• The price is not a proxy for quality. Some of the best books I have read were the cheapest. Some of the worst were the most expensive.
• The used market is your friend. Most technical books have a long tail of used copies. The book you want for $20 today was $80 five years ago.
• Read the table of contents before you buy. If the table of contents is not organized the way you think, no amount of money will make the book useful.

Bottom line

The reading list above is the short list of books I would recommend to a friend who is learning Linux in 2026. None of them is essential, and all of them are good. The Linux documentation, the mailing lists, and the project wikis are still the primary sources. The books are the secondary sources, the ones you read when you want a structured tour, a portable reference, or a physical reminder of a topic you are investing in.