The Linux Programming Interface: A Linux and UNIX System Programming Handbook [Kerrisk, Michael] on desertcart.com. *FREE* shipping on qualifying offers. The Linux Programming Interface: A Linux and UNIX System Programming Handbook Review: I've never seen a book rated so high. After starting to read it, If I could give it 10 stars, I would! Wow! - What an incredible resource for the Linux community! I'm an Oracle DBA, that has always been interested in the lower-level stuff (I/O, system calls, etc.). I was researching Oracle ASM (Oracle's own volume manager), but feeling the need to get more insight into the Linux I/O subsystem. So, I went to desertcart, started searching for relevant resources, and came across this book. I've bought thousands of dollars of technical books on desertcart, and read lots of desertcart reviews. When I bought this book, it had 61 reviews. 60 rated the book a 5 star, and 1 rated the book a 4-star. I have *never* seen a book rated so highly on desertcart before. A book, with incredible ratings like that, was simply unheard of. I'm now reading the book, and thoroughly enjoying the care, the attention to detail, the comprehensiveness, the technical accuracy, the methodology, the extremely well-written English, the clear explanations, and the well-written code. For example, on page 246, where Michael discusses Direct I/O, he says: "If a file is opened with O_DIRECT by one process, and opened normally (i.e. so that the buffer cache is used) by another process, then there is no coherency between the contents of the buffer cache and the data read or written via direct I/O. Such scenarios should be avoided." Wow. In just one sentence, Michael tells us one of the fundamental issues with concurrent I/O, and that by simultaneously using different I/O mechanisms, you can corrupt your files. Another example: on page 249, Michael writes: "When using the stdio library functions in conjunction with I/O system calls to perform I/O on disk files, we must keep buffering issues in mind. I/O system calls transfer data directly to the kernel buffer cache, while the stdio library waits until the stream's user-space buffer is full before calling write() to transfer the buffer to the kernel buffer cache." Wow. It makes sense, when you know as much about the Linux kernel as Michael does. Need to insert an fflush() between the stdio write and the system call write. Another "Aha!" moment, just a couple of pages later. And the pages in between had one of the clearest examples of code for Direct I/O that I have ever seen. Michael even writes about the memory alignment challenges of Direct I/O. It's simply incredible! How in the world could anyone write so much high-quality technical stuff? It's 1500+ pages of awe inspiring, amazing technical blessing. It is a fabulous example to everyone in the I.T. industry, and a very high bar for any technical books to come. Thank you, Michael, for your incredible book. Review: If you're the kind of person to find this page, just buy it - This is without a doubt the best written technical book I've ever read; it's honestly hard to believe only one person wrote and organized it. In an era where you can often get a better answer from a highly voted Stack Overflow question than you'll find most books, TLPI is 100% an exception. 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. Kerrisk often opens with a code-light "overview" chapter on the more dense topics (e.g. networking), and his descriptions are as elegant and well-written as anything you'll find on SO or by googling. 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 real life. It's the rare book indeed which can serve as both an excellently written (and illustrated!) introduction and reference. If you're a student looking to get into linux systems programming (or been assigned some less than high quality reading), pick this up. if you're a programmer of the type who often finds himself typing "man 2 somethingsomething...", absolutely 100% pick this up. The fact that the author is also in charge of the man pages project for linux shows in his encyclopedic knowledge--what makes this book so outstanding is his ability to present that knowledge in an easily-digested form with tight, well-written examples. Yes, it's massive. 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. And to any professors or teachers out there who are curious: yes, please use this as your textbook. 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. Without this book, there's no way I couldn't have learned as much as I did in a fairly short period of time; more importantly, it made me come to appreciate and enjoy systems programming. It combines the readability/working examples of the best Stack Overflow answers, the comprehensiveness of man pages, and logical progression for new learners in one amazingly tight (if not light) package.
| Best Sellers Rank | #39,729 in Books ( See Top 100 in Books ) #1 in Unix Programming #3 in Linux Programming #6 in Linux Networking & System Administration |
| Customer Reviews | 4.8 4.8 out of 5 stars (756) |
| Dimensions | 7.25 x 2.25 x 9.5 inches |
| Edition | 1st |
| ISBN-10 | 1593272200 |
| ISBN-13 | 978-1593272203 |
| Item Weight | 5.37 pounds |
| Language | English |
| Print length | 1552 pages |
| Publication date | October 28, 2010 |
| Publisher | No Starch Press |
J**R
I've never seen a book rated so high. After starting to read it, If I could give it 10 stars, I would! Wow!
What an incredible resource for the Linux community! I'm an Oracle DBA, that has always been interested in the lower-level stuff (I/O, system calls, etc.). I was researching Oracle ASM (Oracle's own volume manager), but feeling the need to get more insight into the Linux I/O subsystem. So, I went to Amazon, started searching for relevant resources, and came across this book. I've bought thousands of dollars of technical books on Amazon, and read lots of Amazon reviews. When I bought this book, it had 61 reviews. 60 rated the book a 5 star, and 1 rated the book a 4-star. I have *never* seen a book rated so highly on Amazon before. A book, with incredible ratings like that, was simply unheard of. I'm now reading the book, and thoroughly enjoying the care, the attention to detail, the comprehensiveness, the technical accuracy, the methodology, the extremely well-written English, the clear explanations, and the well-written code. For example, on page 246, where Michael discusses Direct I/O, he says: "If a file is opened with O_DIRECT by one process, and opened normally (i.e. so that the buffer cache is used) by another process, then there is no coherency between the contents of the buffer cache and the data read or written via direct I/O. Such scenarios should be avoided." Wow. In just one sentence, Michael tells us one of the fundamental issues with concurrent I/O, and that by simultaneously using different I/O mechanisms, you can corrupt your files. Another example: on page 249, Michael writes: "When using the stdio library functions in conjunction with I/O system calls to perform I/O on disk files, we must keep buffering issues in mind. I/O system calls transfer data directly to the kernel buffer cache, while the stdio library waits until the stream's user-space buffer is full before calling write() to transfer the buffer to the kernel buffer cache." Wow. It makes sense, when you know as much about the Linux kernel as Michael does. Need to insert an fflush() between the stdio write and the system call write. Another "Aha!" moment, just a couple of pages later. And the pages in between had one of the clearest examples of code for Direct I/O that I have ever seen. Michael even writes about the memory alignment challenges of Direct I/O. It's simply incredible! How in the world could anyone write so much high-quality technical stuff? It's 1500+ pages of awe inspiring, amazing technical blessing. It is a fabulous example to everyone in the I.T. industry, and a very high bar for any technical books to come. Thank you, Michael, for your incredible book.
B**H
If you're the kind of person to find this page, just buy it
This is without a doubt the best written technical book I've ever read; it's honestly hard to believe only one person wrote and organized it. In an era where you can often get a better answer from a highly voted Stack Overflow question than you'll find most books, TLPI is 100% an exception. 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. Kerrisk often opens with a code-light "overview" chapter on the more dense topics (e.g. networking), and his descriptions are as elegant and well-written as anything you'll find on SO or by googling. 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 real life. It's the rare book indeed which can serve as both an excellently written (and illustrated!) introduction and reference. If you're a student looking to get into linux systems programming (or been assigned some less than high quality reading), pick this up. if you're a programmer of the type who often finds himself typing "man 2 somethingsomething...", absolutely 100% pick this up. The fact that the author is also in charge of the man pages project for linux shows in his encyclopedic knowledge--what makes this book so outstanding is his ability to present that knowledge in an easily-digested form with tight, well-written examples. Yes, it's massive. 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. And to any professors or teachers out there who are curious: yes, please use this as your textbook. 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. Without this book, there's no way I couldn't have learned as much as I did in a fairly short period of time; more importantly, it made me come to appreciate and enjoy systems programming. It combines the readability/working examples of the best Stack Overflow answers, the comprehensiveness of man pages, and logical progression for new learners in one amazingly tight (if not light) package.
T**O
Perfeito! Produto chegou 14 antes do prazo dado pela Amazon. Sem qualquer avaria.
R**K
I have read a lot of technical books (principally windows and c++ related) and really I have NEVER seen a technical book as well written as this one. The book has all the quality I always wanted: 1) it must be thorough: after reading you shouldn't need to read other book or search the web to complete your comprehension: every info you need must be there. 2) it must be clear: there should never be any ambiguity in expressions or situation that requires you to test the info on specific example. You must be able to understand it on first the first reading 3) it must be a pleasant journey: the order of the information should match the normal flow of your thinking and interrogations. The author should guide you so that when you think: "I wonder what would happen in this different situation", the next paragraphs do address that interrogation you have. Again this book does all this extremely well. There is simply no equivalent in the windows world. It makes me learning linux a very pleasant experience. Many many thanks Mr Kerrisk
T**D
East to read and comprehensive.
K**R
This is the most comprehensive and authoritative book on Linux Application programming.. Covers every detail of Linux API interface .. You won't need any other reference book .. Excellent !!!
C**I
Vraiment complet, je trouve toujours tout ce que j'ai besoin, et rapidement
Trustpilot
2 weeks ago
5 days ago
