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):||26 November 2016|
|PDF File Size:||15.72 Mb|
|ePub File Size:||14.79 Mb|
|Price:||Free* [*Free Regsitration Required]|
It’s not like it’s hard: I think this is your only legitimate complaint. They intterface on the earlier chapters, but the text is replete with references to other sections. Even if so, at least you can open them It is, in short, an excellent reference that will likely find its way onto the bookshelves of user-space developers and kernel hackers—including some who aren’t necessarily primarily focused on Linux.
Kerrisk has been the maintainer of the Linux man pages sincewhich gives him a good perspective on the Linux API. Programmig you can do with a Unix domain intervace “file” is to bind to it or connect to it We’re featuring millions of their reader ratings on our book pages to help you find your new favourite book.
The Linux Programming Interface
Interprocess Communication Overview Chapter Not when it comes to sockets, it doesn’t Of particular interest to me were a chapter on writing kwrrisk privileged programs and one on Linux capabilities. Don’t have a Kindle? Many systems totally ignore perms niterface Unix domain sockets, making them effectively alwayslike symlinks 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.
Also, unix sockets have a creation time which helped me once. This is by far one of the best computer science texts I own. Get unlimited access to videos, live online training, learning paths, books, tutorials, and more.
I can only say that we were quite glad not to be dependent on that revenue stream I had this need in one of our application, to workaround an issue I had to use a small tool which can ‘force close’ a ‘listening TCP ports’, having the possibility to ‘rm’ listening Programmong ports would have been much more easy.
I’m not really sure how that’d be of much niterface in general, though? Process Priorities and Scheduling Chapter Timers and Sleeping Chapter All levels All levels Intermediate Experienced.
But, I’m not in favor of leaving tons of file-like tokens scattered all over the filesystem, which can’t actually be used like files for anything, and which only exist there for the sole purpose of having a unique name to identify them by That book is a few years older and obviously libux encyclopedic but nonetheless a wonderful and more portable reference. History and Standards Chapter 2: With filesystem sockets, a server needs kerisk see if the socket already exists in the filesystem; if so, maybe that means another copy of itself or some other app is using that socket; or, maybe it means it previously crashed before being able to remove that socket From the Linux man-pages maintainer User Experience Level: Thread Cancellation Chapter Memory Mappings Overview Creating a Mapping: Kerrisk is not shy about noting things like that where appropriate in the text: Programmers who are primarily targeting kerrism Unix systems may kerriskk find it useful for making their code more portable.
Please visit this page to join up and keep LWN on the net.
Process Credentials Chapter Timers and Sleeping Chapter Some authors seem to go back over their books adding stupid and unintelligent filler to try and make the book longer.
Solutions to Selected Exercises show more.
The Linux Programming Interface : Michael Kerrisk :
I expect it to become the “Stevens” of Linux low level programming. Users and Groups Chapter 9: File Locking Chapter I set out to pick and choose certain chapters to read, and just skim the others, but found myself reading quite a bit more than that—which might partially explain the lateness of this review.
Writing Secure Privileged Programs Chapter System Limits and Options Chapter