Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Linux System Programming Techniques
  • Toc
  • feedback
Linux System Programming Techniques

Linux System Programming Techniques

By : Jack-Benny Persson
4.8 (8)
close
Linux System Programming Techniques

Linux System Programming Techniques

4.8 (8)
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)
close

Conventions used

There are a number of text conventions used throughout this book.

Code in text: Indicates code words in the text, directories, filenames, file extensions, pathnames, dummy URLs, user input, and so on. Here is an example: "Copy the libprime.so.1 file to /usr/local/lib."

A block of code is set as follows:

#include <stdio.h>
int main(void)
{
    printf("Hello, world!\n");
    return 0;
}

When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:

#include <stdio.h>
int main(void)
{
    printf("Hello, world!\n");
    return 0;
}

Any command-line input or output is written as follows:

$> mkdir cube
$> cd cube

In numbered listings, command-line input is set in bold. The $> characters indicate the prompt and aren't something you should write.

  1. This is an example of a numbered listing:
    $> ./a.out
    Hello, world!

Long command lines that don't fit on a single line are broken up using the \ character. This is the same character as you use to break long lines in the Linux shell. The line under it has a > character to indicate that the line is a continuation of the previous line. The > character is not something you should write; the Linux shell will automatically put this character on a new line where the last line was broken up with a \ character. For example:

$> ./exist.sh /asdf &> /dev/null; \
> if [ $? -eq 3 ]; then echo "That doesn't exist"; fi 
That doesn't exist

Key combinations are written in italics. Here is an example: "Press Ctrl + C to exit the program."

Bold: Indicates a new term, an important word, or words that you see onscreen.

Tips or important notes

Appear like this.

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech
bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete