Linux System Programming Techniques

Writing a Linux program that behaves well means understanding more than C syntax. It means knowing how programs communicate with the shell, how files and processes work, and how to respond when system calls fail. Linux System Programming Techniques approaches those challenges through practical recipes, connecting working examples with explanations of the system concepts behind them.

Start with the tools and the command line

The book begins with the development setup—GCC, GNU Make, GDB, and Valgrind—and moves into writing C programs for Linux. From there, it shows how to make programs useful in scripts: handling return values, working with standard input and output, using pipes, and reading environment variables.

Work confidently with files and errors

File operations form a substantial part of the book. Topics include file descriptors and streams, filesystem information, links, permissions, ownership, binary data, and moving through files. Alongside these techniques, dedicated recipes explore error handling and the use of errno, strerror(), and perror() to make failures easier to understand.

Understand processes, services, and communication

Persson moves from process creation, signals, and job control to creating daemons and managing them with systemd. Further chapters explore shared libraries, terminal behavior, and interprocess communication—including pipes, FIFOs, message queues, shared memory, and Unix sockets.

Build and debug more capable programs

The later material covers POSIX threads, race conditions, mutexes, condition variables, and debugging with GDB and Valgrind. Together, these subjects give the book a practical progression from a first Linux program toward tools and services that interact more deeply with the operating system.

A recipe-based reference for Linux C developers

Written for people developing system programs on Linux, this book also suits readers who want focused guidance on particular programming tasks. Keep it nearby when you need to understand a system call, trace a process, or work through the details of file and process behavior.