> Does it seem a good idea? The problem is clearly with loadable modules...
I think it's a good idea. Here is my implementation idea: add a
CONFIG_RECORD_CONFIG option. If CONFIG_RECORD_CONFIG is enabled,
then use the linker to read .config and output its contents in a .o
file, in an initdata section with a name. Then reference that name
in init/main.c to drag it in at link time.
Someone could enhance this to have a three-way choice:
CONFIG_RECORD_CONFIG=none
The default, same as the existing kernel.
CONFIG_RECORD_CONFIG=disk image
As described above, .config file goes into disk image,
but is discarded at boot time.
CONFIG_RECORD_CONFIG=memory image
.config file goes into disk image in an ordinary data section,
not an .initdata section. Plus some code in the /proc file system
makes it available as /proc/config.
Regards,
Michael Chastain
<mailto:mec@shout.net>
"love without fear"
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu