Review
"The book you hold in your hand will hopefully help you understand the Linux operating system kernel better ... it really is a strange and wonderful world, full of subtle details ranging from how to control the physical hardware to how to manage multiple different users at the same time with limited resources ...", Linus Torvalds , , #

Product Description
'The book you hold in your hand will hopefully help you understand the Linux operating system kernel better. it really is a strange and wonderful world, full of subtle details ranging from how to control the physical hardware to how to manage multiple different users at the same time with limited resources.' Linus Torvalds the Linux Kernel book by Rémy Card, Éric Dumas, Franck Mével Translated by Chris Skrimshire Linux has the performance of many commercial Unix systems. It is stable, yet continues to evolve due to the many worldwide developers continually updating it and adding further functionality. As such, it can control the latest peripheral devices on the market such as flash memory and optical disks. Its power and flexibility and the fact that it is free has assured it an enthusiastic user base in academia, amongst home hobbyists, and increasingly in the business world. The Linux Kernel Book allows you to delve into the heart of this operating system by means of an in-depth treatment of the internal functioning of the kernel. Each chapter deals in detail with the system components, including:
* Process management
* Memory management
* IPC Systems V
* Signals
* Pipes
* POSIX tty
* File systems
* Loadable modules
* Administration
The first part of each chapter presents basic concepts and describes the associated system calls, illustrating these with examples written in C. The second part of the chapter extends to a more advanced treatment, showing how the concepts are implemented at the level of the kernel and presenting the data structures and the internal functions used in Linux. Visit our Website! http://www.wiley.com/compbooks/

See all Editorial Reviews

If you are a publisher or author and hold the digital rights to a book, you can make it available as an eBook on Amazon.com. Learn more

I own it Not rated Your rating Don't like it < > I love it! Save your rating    ? 1 2 3 4 5

7 Reviews 5 star:    (0) 4 star:    (0) 3 star:  (1) 2 star:  (5) 1 star:  (1)           Average Customer Review (7 customer reviews)		Share your thoughts with other customers:
Most Helpful Customer Reviews   9 of 10 people found the following review helpful: Regret, January 10, 2000 By  Raymond Mak,CCIE,CISSP (Hong Kong) - See all my reviews Before buying this book, I have bought another book - Linux Kernel Internals which is good but not up-to-date. So I buy this - The Linux Kernel Book for getting more up-to-date materials. I cannot get what I want in it. One of my disappointment is the index, the index is so messy, I cannot follow the structure of the index, so I can't find the materials quickly. Also, the content is organized in a mess also. I regret that I have bought this book, I waste my money and waste my time.  Comment | Permalink | Was this review helpful to you? (Report this)   16 of 18 people found the following review helpful: Better than cleaning your teeth with a bench grinder., October 29, 1999 By A Customer - Computer-related books are a vast wasteland. Most of my quibbles about the book would be irrelevant if it were titled "The Linux Kernel for Cretins." In that case I'd have had to give it two stars. But, it appears to be targeted at serious kernel programmers. In most places, the previously mentioned "poor translation from the French" wasn't perceptible to me. However, I _was_ disappointed with the technical content. Conditioned by things like the BSD book by McKusick et al, I expect discussion about interesting technical points instead of descriptions of kernel entry points. If I wanted to know what functions were available for signal management, I guess I'd read the man pages. However, all the user-level information does bulk the book up nicely, obscuring the fact that it doesn't have much fiber. For example, I wanted to know something about how _procfs_ was implemented. After eliminating the description of various files in /proc (which are documented better elsewhere) there are about two pages of description--mostly of the "Jeshua begat Shemtup" variety. I can use tags and glimpse as well as the next guy--what I'd like is a higher-level description. In summary, it has some interesting information, but a