请教这几句怎么理解

forx86

1、It is enough files stored in a ramdisk to store needed drivers .

2、Somewhere during the 2.5.x series，

3、A few drivers will need system.map to resolve symbols (since they're linked against the kernel headers instead of, say, glibc). They will not work correctly without the system.map created for the particular kernel you're currently running. This is NOT the same thing as a module not loading because of a kernel version mismatch. That has to do with the kernel version, not the kernel symbol table which changes between kernels of the same version!

4、Dynamic translation which is used with loadable modules,

5、What Does An oops Have To Do With system.map?

6、system.map is a "phone directory" list of function in a particular build of a kernel. It is typically a symlink to the system.map of the currently running kernel. If you use the wrong (or no) system.map， debugging crashes is harder， but has no other effects. Without system.map， you may face minor annoyance messages.

7、system.map is produced by 'nm vmlinux' and irrelevant or uninteresting symbols are grepped out，

8、Do NOT touch the system.map files.

9、the stock RH kernels

10、the same point release of RH kernels.