On Wed, 13 Feb 2002, Bill Davidsen wrote:
| On Wed, 13 Feb 2002, Ben Greear wrote:
|
[snippage]
|
| No, but there's no reason to have it part of the kernel image as the only
| solution. It works as a module, it works as a flat text data file in the
| modules directory (except for those who can't match kernel to modules),
| and ther's no reason why this can't exist somewhere which has no impact on
| the size of the kernel image.
I agree, if I understand you correctly.
I don't see a need for a CONFIG_SAVE_CONFIG option with value 'm'.
kbuild in 2.5 (or any script like 'installkernel') can do that by
copying the current .config file to the modules install directory
or the /boot directory.
I was hoping that (e)grep could search a (b)zImage file for
a binary pattern like the gzip header, but I couldn't make it
work. I ended up writing a binary pattern search tool that
returns the offset of the located pattern, and then I feed
that value to tail | gunzip > strings | grep to get the
CONFIG text that was saved by the code that I posted yesterday.
I still plan to make this a config/build option (y/n) and
remove the leading "CONFIG_" parts of the strings.
binoffset.c and extract-config (script) attached.
-- ~Randy
This archive was generated by hypermail 2b29 : Fri Feb 15 2002 - 21:01:03 EST