Linux Kernel Internals
Authors: Beck, Böhme, Dziadzka, Kunitz, Magnus, Verworner
Price: $45.14 (includes CD)
Reviewer: Phil Hughes
Linux Kernel Internals is an English translation of a book originally written in German and published in early 1994. I was immediately concerned since I have read literal translations from German to English that were very hard to understand.
Fortunately, my fears were unfounded. The translation job is excellent and the content of the book fulfills expectations based on the book title.
If you intend to write kernel code, or a kernel module, or just want to know how the kernel of a Linux system works, this book is an excellent source of information. Also, if you want to know how to build a kernel and understand what you are doing, understand file systems, networking, or even just how a system boots, this book will answer your questions.
As I was reading the book to write this review, I found myself slowing down to carefully understand all the Linux kernel structures. The information is there, and by reading the book cover to cover, you will learn all about the kernel.
On the other hand, if you just want to know about some specific feature—like how timer interrupts work or how to debug a kernel module—that information is included as well, and presented in an easy-to-find, easy-to-understand fashion. But, not too easy. That is, if you don't know C, you are not going to understand most of the book. The information presented is at the code level with snippets of code scattered throughout the book.
After a brief introduction covering Linux in general and compiling the kernel, the book covers important data structures, like the process table, followed by inodes, memory management and timers. Next, how signals, interrupts, booting, the scheduler and system calls work are presented. There is even a section on how to implement a new system call.
The next five chapters deal with specific pieces of the system: memory management, inter-process communication, the file system, device drivers and network implementation. This information is presented in enough detail to clarify the process and enable the reader to write compatible code. The chapter on the file system includes the proc and ext2 file systems.
The final chapter in the main part of the book is on modules, describing what modules are and how they are implemented. The text presents an example module (the PCMCIA card handler), and explains how to debug modules.
The book ends with five appendices. The first details the system calls in much the same way as Section 2 of the man pages, but the calls are sorted by area (processes, file system, etc.) rather than alphabetically. It also tells you where the file with the code to implement the function is located.
The second appendix discusses what the authors call “kernel-related commands”. These include free, ps, rdev, top, init, shutdown, strace and mount as well as network, serial and parallel interface configuration.
The third appendix discusses the proc file system. Many people don't realize how important the proc file system is. This short (ten page) chapter explains it and the important information that can be secured from it.
The final appendix explains the boot process, including the MS-DOS boot sector and partition table, and discusses LILO with an explanation of the LILO startup errors (e.g., when you just get LI and the system dies).
The final appendix presents “useful kernel functions”. This is an explanation of functions, such as printk(), available to users writing kernel code.
Very little. I think it does an excellent job of covering the material. It doesn't attempt to cover subjects outside its primary focus, and I find that a plus.
The only shortcoming I see is that it covers version 1.2 kernels, not 2.0. Of course, at this time, it would be very difficult to have a book that covers 2.0. Addison-Wesley may decide to update the book before the next printing.
Bottom line, I highly recommend this book for anyone who is serious about writing kernel code or who wants to know what is in the Linux kernel.
Phil Hughes is the publisher of Linux Journal.
|Chemistry on the Desktop||Mar 23, 2017|
|Five HPC Cost Considerations to Maximize ROI||Mar 23, 2017|
|Two Ways GDPR Will Change Your Data Storage Solution||Mar 22, 2017|
|Android Candy: That App Is for the Birds!||Mar 22, 2017|
|Hodge Podge||Mar 21, 2017|
|William Rothwell and Nick Garner's Certified Ethical Hacker Complete Video Course (Pearson IT Certification)||Mar 20, 2017|
- Two Ways GDPR Will Change Your Data Storage Solution
- Five HPC Cost Considerations to Maximize ROI
- Hodge Podge
- William Rothwell and Nick Garner's Certified Ethical Hacker Complete Video Course (Pearson IT Certification)
- Preseeding Full Disk Encryption
- Chemistry on the Desktop
- Returning Values from Bash Functions
- Two Factors Are Better Than One
- Android Candy: That App Is for the Birds!
- GRUB Boot from ISO
Pick up any e-commerce web or mobile app today, and you’ll be holding a mashup of interconnected applications and services from a variety of different providers. For instance, when you connect to Amazon’s e-commerce app, cookies, tags and pixels that are monitored by solutions like Exact Target, BazaarVoice, Bing, Shopzilla, Liveramp and Google Tag Manager track every action you take. You’re presented with special offers and coupons based on your viewing and buying patterns. If you find something you want for your birthday, a third party manages your wish list, which you can share through multiple social- media outlets or email to a friend. When you select something to buy, you find yourself presented with similar items as kind suggestions. And when you finally check out, you’re offered the ability to pay with promo codes, gifts cards, PayPal or a variety of credit cards.Get the Guide