Book Image

Linux System Programming Techniques

By : Jack-Benny Persson
Book Image

Linux System Programming Techniques

By: Jack-Benny Persson

Overview of this book

Linux is the world's most popular open source operating system (OS). Linux System Programming Techniques will enable you to extend the Linux OS with your own system programs and communicate with other programs on the system. The book begins by exploring the Linux filesystem, its basic commands, built-in manual pages, the GNU compiler collection (GCC), and Linux system calls. You'll then discover how to handle errors in your programs and will learn to catch errors and print relevant information about them. The book takes you through multiple recipes on how to read and write files on the system, using both streams and file descriptors. As you advance, you'll delve into forking, creating zombie processes, and daemons, along with recipes on how to handle daemons using systemd. After this, you'll find out how to create shared libraries and start exploring different types of interprocess communication (IPC). In the later chapters, recipes on how to write programs using POSIX threads and how to debug your programs using the GNU debugger (GDB) and Valgrind will also be covered. By the end of this Linux book, you will be able to develop your own system programs for Linux, including daemons, tools, clients, and filters.
Table of Contents (14 chapters)

Compiling a statically linked program

Now that we have such a deep understanding of libraries and linking, we can create a statically linked program—that is, a program with all dependencies compiled into it. This makes the program—more or less—dependency-free. Making statically linked programs isn't common but sometimes it can be desirable—for example, if you for some reason need to distribute a single precompiled binary to many computers without worrying about installing all the libraries. But please note: it's not always possible to create completely dependency-free programs. If a program uses a library that depends on another library, this is not easily accomplished.

The downside of making and using statically linked programs is that they get a lot bigger in size. Also, it's no longer possible to update the program's libraries without recompiling the entire program. So, bear in mind that this is only used in rare cases.

But,...