On Tue, 12 Feb 2002, Andreas Dilger wrote:
| On Feb 12, 2002 13:32 -0500, Bill Davidsen wrote:
| > On Tue, 12 Feb 2002, Padraig Brady wrote:
| > > I'd go for tacking it on at the end of the bzImage. Advantages would be
| > > that it can be read even when the kernel isn't loaded, and also there
| > > is no danger of loading a module in another kernel.
| >
| > There are several problems with that:
| > 1 - built into the kernel it is compressed and needs a tool to read
| > 2 - the reason kernels are compressed is to make them fit in small boot
| > media, so adding something to the image is not to be done lightly.
| > 3 - modules are NOT compressed, and can be read with the strings command.
| > 4 - other files in the modules directory are pure text and if the config
| > was just text it could be read with `cat.'
|
| My thought on this is to make it a tristate [y/m/n] and have it print
| output via /dev/kconfig or similar. There could be a dep_bool which
| keeps it in-core, or puts it in an init function which is discarded
| after boot. If you don't want to have it at all, you turn it off.
| If you want it in the kernel, but not in memory all the time, it can
| be in an init function (maybe printk'ing it before startup is done?).
| It can be in a module and you can get the original plain-text config
| back with "cat /dev/kconfig" and if it is a module it will be auto-loaded
| from wherever it is.
|
| You can also extract it from an uncompressed kernel (vmlinux) or the
| module with "strings <file> | grep '[A-Z]*=[ym]$'". It is simple
| enough to search for the gzip magic (1f 8b 08 00 at about 16-18kB)
| in a zImage or bzImage, and then pipe it to gunzip and strings as above.
Thanks for the info.
Yes, I can see the gzip header, using 'od'.
What's an existing tool to strip (delete) bootsect and setup
from the beginning of [b]zImage, up to the gzip header, so
that the rest of the file can be piped to gunzip ?
Otherwise I can write one.
Thanks,
-- ~Randy- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Feb 15 2002 - 21:00:51 EST