| On Wed, 6 Feb 2002, Randy.Dunlap wrote:
| > I still prefer your suggestion to append it to the kernel image
| > as __initdata so that it's discarded from memory but can be
| > read with some tool(s).
| The problem is that it make the kernel image larger, which lives in /boot
| on many systems. Putting it in a module directory, even if not a module,
| would be a better place for creative boot methods, of which there are
Yes, it can add a few KB to a kernel image.
Some people could think that it's worth it...especially
if it's a build option.
I prefer this to using /proc/config.gz (which SuSE currently does),
since the config data won't be in permanent memory, and it's
attached to a kernel image on disk -- the kernel doesn't have to
be loaded in memory to view it. (or maybe there's a way to
view config.gz in a SuSE kernel image ?)
I don't see how making it a binary module (living in
/lib/modules/version/kernel/configs.o e.g.) has any advantages
over kbuild (?) just copying the .config file to
Does anyone recall if kbuild already does something like this?
I spent a little time this weekend making .config live in an
__initdata array, and I can see it in 'vmlinux',
but I can't see it in the (compressed) 'bzImage' file.
I expect that this is just a tools problem, due to the
compressed kernel image. Does anyone know how to grep
for a string in 'bzImage', or how to expand 'bzImage'
so that grep can find strings in it?
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/