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):||1 March 2010|
|PDF File Size:||7.89 Mb|
|ePub File Size:||19.6 Mb|
|Price:||Free* [*Free Regsitration Required]|
After IPC, comes a chapter on file locking followed by six chapters covering sockets. Even if you want to skip the C and just get a great understanding of Linux; this book if for you. As a grad student who hasn’t been in CS for very long, I was extremely fortunate to be assigned this as a textbook for a systems programming class.
This is by far one of the best inteeface science texts I own. None of this is needed with abstract Unix domain sockets In the Linux implementation, sockets lihux are visible in the filesys- tem honour the permissions of the directory they are in. Process Resources Chapter Definitely a book you want at home, at the office, on keerisk plain, in the car, in the bathroom, or anywhere else you can think of reading!
Review: The Linux Programming Interface 
Anyone who has an interest in programming for Linux will likely feel the same way. Kerrisk is a former writer for the Linux Weekly News  and the current maintainer for the Linux man pages project,  “The Linux Programming Interface” is widely regarded  as the definitive work on Linux kerrosk programming and has been translated into several languages.
Table of contents Preface Chapter 1: For reasons other than permissions? Posted Jan 20, 0: File Locking Chapter A Complete Introduction Paperback. Further Details Chapter I doubt it’s changed, but interfface checked recent versions of OpenSolaris. Besides I use inotify, flock and tmpfs to cover my current IPC needs. Book ratings by Goodreads. I’m not sure I can really conceive of a real-world use for such a thing, however You’ll learn how to: Unless you have special rare needs like those previously mentioned which can only be solved by them having a pathname in the filesystem The book starts with a history of Unix, Linux, and standards, and then progresses into the kerrisk detail the inner linu of linux and unix.
Check out the top books of the year on our page Best Books of Those you can at least readlink like a real symlink Program Execution Chapter The material is presented in such a fashion that pretty much anyone with a working knowledge of C can pick it up, sit down, and understand any of its topics.
Which is intergace shortcoming of Unix design which was fixed in 9p, btw.
Retrieved from ” ptogramming But, personally, I have no need for any of them, and they mostly seem like stretches and grasping at straws to justify them existing in a place they certainly don’t belong the filesystem You’ll learn how to: There were two specific topics that I looked forward to reading about but were only marginally covered by the book. Users and Groups Chapter 9: This means that when I tried to restart it, the new process would immediately fail because the socket was already bound.
System and Kerriks Information Chapter If they were designed such that you could pass one to an otherwise unsuspecting app, which just open ‘d it normally, and that intrface let that app talk to whoever is listening on the other end of the socket a la a named pipethen I’d be all in favor of them It’s the rare book indeed which can serve as both an excellently written and illustrated!
Review: The Linux Programming Interface
Importantly, the examples also do a good job of demonstrating the topic at hand and some of them could be adapted into useful utilities. How does Plan9 deal with this? Book Description The Linux Programming Interface describes the Linux API application programming interface —the system calls, library functions, and other low-level interfaces that are used, directly or indirectly, by every program that runs on Linux.
There was a problem filtering reviews right linjx. 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 programming, and accompanies his explanations with clear, complete example programs.
There is a chapter covering directories and links, as well as one that looks at the inotify file event notification call. Kerrisk has been the maintainer of the Linux man pages sincewhich gives him a good perspective on the Linux API. However, ability to use AppArmor to restrict access to sockets somehow makes me feel more secure. They build on the earlier chapters, but the text is replete with references to other sections. But, no, provramming can’t do that Process Creation Chapter Linux Linux kernel features Portal: The program should have used sockets in the filesystem.
In my experience, though, many of them might best have interfae worked into the main text. This book won’t disappoint you if you libux to know more about Linux, C programming, Unix operating systems, and much more. Get to Know Us.
Shopbop Designer Fashion Brands. Looking for beautiful books?
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 approaches you will still see pop up, so the reader isn’t clueless when encountering pre-POSIX code in kertisk life. They’re just special creatures that happen to be identified via a pathname