On Wed, Feb 06, 2002 at 02:16:27PM +0000, you [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
What is even harder to find out given a binary kernel is which patches (if
any) have been applied to it. What if there was one file (say,
/usr/src/linux/patches) to which each (well-behaved) patch would append a
line or two (patch name, version, author, url), and then you could later
extract that information the same way you extract .config?
Figuring out what patches have been applied can be hard even given a source
tree, so this could be useful even without the data-in-bzImage thing.
-- v --
v@iki.fi
-
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