In article <0C01A29FBAE24448A792F5C68F5EA47D217218@nasdaq.ms.ensim.com>,
you write:
>The reason you need all of these config options (which don't end up
>making the code much more complex) is because, for example, if you
>are netbooting your kernel, you do not have access to any external
>data or even the original kernel image on that system. If it is
>in-memory
>you use 15kB of RAM (5kB in the compressed image) for a fully-configured
>vendor kernel, but you have the config options for THIS kernel and not
>any "maybe it is right, maybe not" external file.
How about having the MD5 sum of the config printed during boot time,
just after (or on) the "Linux version" line - then at least you'd be
able to verify that the .config file in your hands was indeed the one
that was used to compile the kernel.
Paul
-
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