>>> /lib/modules/KVER heirarchy. It would be a much easier way
>>> to boot various kernels and be assured the correct map file
>>
>> This _is_ already possible. Just do the following:
>>
>> Rename your System.map file to System.map-2.2.10
>> Rename your bzImage or whatever to vmlinuz-2.2.10
OK. These all work for ps and top:
/boot/System.map-2.2.10
/boot/System.map
/lib/modules/2.2.10/System.map
/usr/src/linux/System.map
/System.map
$PS_SYSMAP
$PS_SYSTEM_MAP
There might be other requirements set by klogd.
>> Adjust lilo.conf.
No, don't touch that.
>> No more need for a System.map file: when booting, the kernel
>> will understand System.map-2.2.10 is the companion of
>> vmlinuz-2.2.10 and use it. This way you can use any number of
>> kernel versions with the correct map file.
The kernel doesn't need this. (it ought to provide it, to avoid
all these problems)
> Is this done with the lilo "map=..." option?
Nope, that is about as relevant as a Civ II game map file.
I wrote these two popular error messages:
"Warning: %s not parseable as a System.map\n"
"Warning: %s has an incorrect kernel version.\n"
They are finding problems that were being ignored. Older procps
versions (like 1.x.x) will generate garbage when you have the
wrong System.map file. Your bogus "ps axl" output is likely to
waste kernel developer time when you report bugs.
Note that you can still get bogus data! I can only check the
kernel version number. There isn't a unique ID for the kernel.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/