Book Image

Hands-On System Programming with Linux

By : Kaiwan N. Billimoria, Tigran Aivazian
Book Image

Hands-On System Programming with Linux

By: Kaiwan N. Billimoria, Tigran Aivazian

Overview of this book

The Linux OS and its embedded and server applications are critical components of today’s software infrastructure in a decentralized, networked universe. The industry's demand for proficient Linux developers is only rising with time. Hands-On System Programming with Linux gives you a solid theoretical base and practical industry-relevant descriptions, and covers the Linux system programming domain. It delves into the art and science of Linux application programming— system architecture, process memory and management, signaling, timers, pthreads, and file IO. This book goes beyond the use API X to do Y approach; it explains the concepts and theories required to understand programming interfaces and design decisions, the tradeoffs made by experienced developers when using them, and the rationale behind them. Troubleshooting tips and techniques are included in the concluding chapter. By the end of this book, you will have gained essential conceptual design knowledge and hands-on experience working with Linux system programming interfaces.
Table of Contents (21 chapters)

The traditional Unix permissions model

Right from the early 1970, the Unix OS had, as usual, an elegant and powerful system in place for managing the security of shared objects on the system. These objects included files and directories—perhaps the most commonly thought of ones. Files, directories, and symbolic links are filesystem objects; there are several others, including memory objects (tasks, pipes, shared memory regions, message queues, semaphores, keys, sockets) and pseudo filesystems (proc, sysfs, debugfs, cgroupfs, and so on) and their objects. The point is all these objects are shared in some manner or other, and thus they require a protection mechanism of some sort, to protect them from abuse; this mechanism is called the Unix permission model.

You probably don't want others to read, write, and delete your files; the Unix permission model makes this possible...