Tham khảo tài liệu 'linux device drivers-chapter 16 :physical layout of the kernel source', công nghệ thông tin, hệ điều hành phục vụ nhu cầu học tập, nghiên cứu và làm việc hiệu quả | Chapter 16 Physical Layout of the Kernel Source So far we ve talked about the Linux kernel from the perspective of writing device drivers. Once you begin playing with the kernel however you may find that you want to understand it all. In fact you may find yourself passing whole days navigating through the source code and grepping your way through the source tree to uncover the relationships among the different parts of the kernel. This kind of heavy grepping is one of the tasks your authors perform quite often and it is an efficient way to retrieve information from the source code. Nowadays you can even exploit Internet resources to understand the kernel source tree some of them are listed in the Preface. But despite Internet resources wise use of grep 62 less and possibly ctags or etagscan still be the best way to extract information from the kernel sources. 62 Usually find and xargsare needed to build a command line for grep. Although not trivial proficient use of Unix tools is outside of the scope of this book. In our opinion acquiring a bit of a knowledge base before sitting down in front of your preferred shell prompt can be helpful. Therefore this chapter presents a quick overview of the Linux kernel source files based on version . If you re interested in other versions some of the descriptions may not apply literally. Whole sections may be missing like the drivers media directory that was introduced in by moving various preexisting drivers to this new directory . We hope the following information is useful even if not authoritative for browsing other versions of the kernel. Every pathname is given relative to the source root usually usr src linux while filenames with no directory component are assumed to reside in the current directory -- the one being discussed. Header files when named with and angle brackets are given relative to the includedirectory of the source tree. We won t dissect the Documentation directory as its role is .
