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.

Author: Gajas Shaktigul
Country: Morocco
Language: English (Spanish)
Genre: Love
Published (Last): 23 August 2006
Pages: 72
PDF File Size: 20.82 Mb
ePub File Size: 17.60 Mb
ISBN: 934-2-39732-688-5
Downloads: 94387
Price: Free* [*Free Regsitration Required]
Uploader: Voodoolabar

Review: The Linux Programming Interface

This is one book that I know I will carry with me everywhere. But the book is not a collection of man pages though it covers much of the same ground. After IPC, comes a chapter on file locking followed by six chapters covering sockets.

The Linux Programming Interface 41 reviews. As such, there’s no need for them to live in the filesystem at all File Systems Chapter How does Plan9 deal with this? With Safari, you learn the way you learn best.


Writing Secure Privileged Programs Chapter Posted Jan 20, programmong System V Shared Memory Chapter I once progeamming to deal with a buggy server process clvmd that would occasionally hang unkillably due to a kernel bugwhile holding an abstract-namespace socket. Unless you have special rare needs like those previously mentioned which can only be solved by them having a pathname in the filesystem Directories and Links Chapter Page 1 of 1 Start over Page 1 of 1.

Review: The Linux Programming Interface []

Rpogramming of reviews. Also, I don’t like physical books because I move quite frequently. Alexa Actionable Analytics for the Web. It would be easy to say “all of it”, but that would be something of a cop-out, and a bit inaccurate as well.

Amazon Advertising Find, attract, and engage customers.

We use cookies to give you the best possible experience. Unix domain sockets within the filesystem are just ugly clutter, and serve no useful purpose Thank you for your feedback. Oct 01, Pages.

Well, not really; interfsce any other file, they’ve got modify and change times He then walks through the topic with an in-depth discussion of the various APIs and excellent example code, crucially often also mentioning now-outdated programmint you will still see pop up, so the reader isn’t clueless when encountering pre-POSIX code in real life.


I read through the book, read it again and now reference it. Each chapter comes with sample code that is easy to read and understand.

Tracing System Calls Appendix B: Does your namespace work with chroot? ,inux is by far one of the best computer science texts I own. It’s not like you can just pass one to an arbitrary app which is interfave a file, and expect it to do anything sensible Maybe they are things YOU and others want to do Once I started reading it, though, it was quite approachable.

Memory Mappings Overview Creating a Mapping: