Hi,
b). My custom 2.4.30 kernel size is about 750K uncompressed. With setting the options to remove support for hardware
that I don't have and features that I don't need, I still came up with a kernel of 2.7M. The goal is to have the
smallest footprint kernel possible.
My amiga kernel, which is not optimized for size, has ipv6 and lots of stuff,, is 2170192 bytes, stripped. I suspect
you have not stripped yours?
Point of clarification: I was changing the .config to remove support for hardware (don't even make as a module) and
features that I don't need in the kernel. Was there another method being referred to with the term 'stripped' above?
The 'strip' command (part of binutils) does remove symbol tables from the kernel
image file. This does reduce the image file size. I am not sure that it does
reduce the memory footprint.
Part of the kernel code is now stored in sections of the image that are later
freed if the corresponding code is no longer used. You should not expect a
simple 1:1 correlation between kernel image file and memory footprint.
Michael
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
