> Perhaps the system map (and .config too) could be stuck onto to kernel in
> such a fashion that they dont get loaded into memory. Lilo would prob then
> need to be modified to pass to the kernel 'who it is'. Then there could be
> a sysctl to request the filename of the currently running kernel..
>
That's the way, I think. Expect a patch soon (in days, since just right
now I don't feel very well ... an inflammation to the throat :) that will
extend the saved data. I will save system.map and .config, and a patch to
have a file in /proc/sys/kernel/boot_image_path to read and set the boot
image ... and as much of you noted, we could discard the kernel space
/proc/ksyms_internal and the like, since they are not needed if we know
the position of the booted image. Anyway I think it will stay into the
kernel for the reasons explained in another e-mail.
Ciao,
Riccardo.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu