The Linux Programming Interface (published in October , No Starch Press, The author, Michael Kerrisk, is the maintainer of the Linux man-pages project. The Linux Programming Interface. 41 reviews. by Michael Kerrisk. Publisher: No Starch Press. Release Date: October ISBN: View table. The Linux Programming Interface (TLPI) is the definitive guide to the Linux and UNIX programming interface—the interface employed by nearly every.
|Published (Last):||7 November 2006|
|PDF File Size:||11.91 Mb|
|ePub File Size:||1.87 Mb|
|Price:||Free* [*Free Regsitration Required]|
Filled with detailed descriptions and complete example programs. Writing Secure Privileged Programs Prlgramming Just all around an excellent book. See all reviews. LitFlash The eBooks you want at the lowest prices.
How does Plan9 deal with this? In this authoritative work, Linux programming expert Michael Kerrisk provides detailed descriptions of the system calls and library functions that you need in order to master the craft of system linnux, and accompanies his explanations with clear, complete example programs.
Further Details Kergisk Explore the Home Gift Guide. Just like it should be taught how to do with Linux’s abstract Unix domain namespace Directories and Links Chapter If on the other hand you use a common abstraction, namely the filesystem, then you get the benefit of all the common tools. Creation of a new socket will fail if the process does not have write interfwce search execute per- mission on the directory the socket is created in. Server Design Chapter Fundamentals of Shared Libraries Chapter Without this book, there’s no way I couldn’t have learned as much as I did in a fairly short period of time; interfqce importantly, it made me come to appreciate and enjoy systems programming.
The Linux Programming Interface by Michael Kerrisk | : Books
This kerirsk by far one of the best computer science texts I own. From the first terminal commands to writing complete programs in Bash. File Locking Chapter Program Execution Chapter Read it Forward Read it first.
There are certainly other parts of the Linux API that could have been covered, beyond the system call interface—sysfs, spliceand perf come to mind—but Kerrisk undoubtedly needed to draw the line somewhere. Posted Jan 21, I have so many good things to say about this book, I highly recommend it to anybody with an interest in linux systems programming.
This behavior differs from many BSD-derived systems which ignore permissions for Unix sock- ets. Virtual Linu Operations Chapter Technical books, especially those covering Linux, have a tendency to get stale rather quickly, but TLPI shouldn’t suffer from that as much as a kernel internals book would, for example. Internet Domains Chapter Each chapter comes with sample code that is easy to read and understand.
Memory Allocation Chapter 8: What, aside from lsof, actually needs to ever reference a Unix domain socket by pathname as if it were a file, anyway? We’re featuring millions of their reader ratings on our book pages to help you find your new favourite book. I doubt it’s changed, but havn’t checked recent versions of OpenSolaris. You will need an understanding of C programming to get through the book.
The Linux Programming Interface is the most comprehensive single-volume work on the Linux and UNIX programming interface, and a kertisk that’s destined to become kerrixk new classic. File Attributes Chapter But, yeah, both will generally reflect creation time Unfortunately it sounds like I need the Kerrisk book too: Michael lives with his family in Munich, Germany. Thread Synchronization Chapter No, I want to do none of those things We are experiencing technical difficulties.
Tracing System Calls Appendix B: A more puzzling omission is that there is almost no mention of the ptrace system call.
The Linux Programming Interface
Process Termination Chapter See what I mean about minor complaints? He has written or co-written more than of inferface manual pages and is actively involved in the testing and design review of new Linux kernel-userspace interfaces.
Program Execution Chapter Like, for instance, you can do with a named pipe