On Fri, Sep 01, 2000 at 01:28:08PM +0100, Alan Cox wrote:
> > On Fri, Sep 01, 2000 at 02:23:57PM +0200, firstname.lastname@example.org wrote:
> > > I don't see the advantage over Alan's proposal of simply adding the
> > > config data to the bzImage or whatever is the most common format on
> > > the respective platform. You still have the same fundamental problem
> > > to solve (i.e. accessing the file), plus you may need to extend the
> > > boot loader(s) to support a new format ...
> My goal would be to ensure that the bootloader didnt need to be modified.
> It seems to work fine if you blindly tack junk on the end of a bzImage
We still load it into memory during boot then but overwrite it with the
uncompressed kernel. This means it might not be a great idea for 16 MB
of additional data but for .config it souhld be fine.
> As to the tool argument - looking for a 16byte magic key sequence and printing
> the rest is not hard.
in fact you can do
cat .config.gz >> bzImage
echo >> bzImage
echo $(wc -c .config.gz) >> bzImage
and seek to the right offset directly.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Sep 07 2000 - 21:00:13 EST