> You might not have the kernel image, because you got it over the
> network. Or you might have several, but are not sure which was
> one corresponds to the running kernel.
Well, you could solve it by having a kernel checksum (MD5?) compiled
in and just comparing the checksums to be sure what kernel are you
running.
> > doesn't eat up precious kilobytes of kernel space.
> C'mon give the guy who implemented this a break.
> FYI, on my .config
> grep -v '^#' .config | gzip | wc -c
> gives 483. Add a couples of bytes for the code that implements
> /proc/config. And of course you could make it an option.
I don't expect /proc/config to give _gzipped_ answer, so you either have
to include ungzip code in the kernel or you cannot have the data compressed
in memory. _Runtime_ size of the kernel is more important than the on-disk
size.
Have a nice fortnight
-- Martin `MJ' Mares <mj@ucw.cz> http://atrey.karlin.mff.cuni.cz/~mj/ Faculty of Math and Physics, Charles University, Prague, Czech Rep., Earth "My computer isn't that nervous, it's just a bit ANSI."- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu