On Thu, 3 Jan 2002, mukund wrote: > But how come lilo loads a kernel2.4 when system map is pointing to map of > kerrnel2.2
> -----Original Message----- > From: Suresh Ramasubramanian <[EMAIL PROTECTED]> > >Everytime you compile a kernel, system.map is created to map the kernel > >address locations of assorted variables and functions to symbolic names. > >Something like you link a .o to an executable with gcc. the system.map is just the ldd dump of the kernel, its an ascii file listing all the symbols exported by the kernel, and does not do addresses or offsets. One can actually open it with any text editor. When loading a module, this file is looked up to match the exported names of the module and the kernel. So conflicts might arise Moreover, lilo doesnt deal with system.map, I used to copy it by hand to /boot and then symlink it, after each kernel compilation . Maybe make install does that. Lilo's map file however is an altogether a different thing, a table of different kernels it can boot and their raw locations ( i guess ) -- sreangsu _______________________________________________ linux-india-help mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/linux-india-help
