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):||16 March 2004|
|PDF File Size:||7.54 Mb|
|ePub File Size:||20.67 Mb|
|Price:||Free* [*Free Regsitration Required]|
Not when it comes to sockets, it doesn’t Withoutabox Submit to Inteface Festivals. Developers The Linux Programming Interface kernel. Alexa Actionable Analytics for the Web. There is something to learn for everyone in this book, regardless of how many years or decades of experience you have.
System and Process Information Chapter Just like it should be taught how to do with Linux’s abstract Unix domain namespace The coverage of the Linux system call interface is encyclopedic, but the writing style is very approachable.
Extended Attributes Chapter System and Process Information Chapter I’m delighted to see this listed in the table of contents Process Creation Chapter It also points out some of the warts and historical cruft that is carried along in that API. There are two chapters on shared libraries, the first of which is more about the ideas underlying interfacr and shared libraries along with how to build them, rather than the dlopen system call and friendswhich is covered in the second.
The Linux Programming Interface – Wikipedia
Then everything is in a predictable place in the filesystem, and you have all the HUGE advantages that they are in the same namespace you can search with existing tools. The book starts with a bit of history, going all the way back to Ken Kergisk and Dennis Ritchie and then moving forward to the present, looking at the various branches of the Unix tree. It provides many samples of code written in the C programming language, and provides learning exercises at prorgamming end of many chapters.
The Linux Command Line: Monitoring File Events Chapter Linux Kernel Development 3rd Edition Paperback. Each chapter also has a handful of exercises for the reader, some of which have answers in one of the appendices. But, yeah, both will generally reflect creation time Kernel Configuration Appendix E: Posted Jan 20, 0: Dispatched from the UK in 3 business days When will my order arrive? If you are a seller for this product, would you like to suggest updates through seller support?
The Linux Programming Interface
If they were designed such that you could pass one to an otherwise unsuspecting app, which just open ‘d it normally, and that magically 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 This book is over pages and each page is jam packed with information.
Please try again later. That’s a case where existing in the filesystem is actually useful But trust me, there isn’t a page wasted in here–even if you’re experienced in the area, walking through each chapter and digesting Kerrisk’s explanations will serve you well.
The ideas that “everything is programminng file” and that files are just streams of bytes are described in ways that will quickly get a system programmer up to speed on the “Unix way”.
Views Read Edit View history. They just go away when you exit or close the listening socket 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.
Is it really a lot?
Review: The Linux Programming Interface
Once you do, does this process-specific socket exist as a separate file for others to see and interact with? Advanced Features of Shared Libraries Chapter That book is a few years older kerrsik obviously less encyclopedic but nonetheless a wonderful and more portable reference. Not talking about directories or symlinks to themI assume? Right, it has to deal with a separate namespace It’s not like it’s hard: But the book is not a collection of man pages though it covers much of the same ground.
But, no, you can’t kerisk that Goodreads is the world’s largest site for readers with over 50 intefface reviews. Amazon Drive Cloud storage from Amazon.
Also, I don’t like physical books because I move quite frequently.
He has written or co-written more than of the manual pages and is kerriwk involved in the testing and design review of new Linux kernel-userspace interfaces. This is one book that I know I will carry with me everywhere. Sincehe has maintained the man-pages project http: Should it unlink it and try to bind it itself?