Randy.Dunlap wrote:
> On Wed, 6 Feb 2002, Alan Cox wrote:
>
> | > > If you are going to cat it onto the end of the kernel image just
> | > > mark it __initdata and shove a known symbol name on it. It'll get
> | > > dumped out of memory and you can find it trivially by using tools on
> | > > the binary
> | >
> | > What about putting such info into a (swappable) tmpfs file with
> | > shmem_file_setup?
> |
> | That is indeed an extremely cunning plan. Paticularly as /proc/config can
> | be a symlink to it
> | -
>
> 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).
>
>
I aggree. You shouldn't need the kernel running to be able
to read it's config settings from it. You could do the
equivalent of the following at the end of the build.
<.config sed -e '/^#/d' -e '/^[ ]*$/d' | gzip -9 >> image
The sed scripts strip comments and blank lines.
Padraig.
-
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 : Thu Feb 07 2002 - 21:00:51 EST