[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200706071208.04777.rob@landley.net>
Date: Thu, 7 Jun 2007 12:08:04 -0400
From: Rob Landley <rob@...dley.net>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: Jeremy Fitzhardinge <jeremy@...p.org>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Vivek Goyal <vgoyal@...ibm.com>,
Rusty Russell <rusty@...tcorp.com.au>, Andi Kleen <ak@...e.de>,
v12n <virtualization@...ts.linux-foundation.org>,
lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH RFC 6/7] i386: make the bzImage payload an ELF file
On Wednesday 06 June 2007 9:54 pm, H. Peter Anvin wrote:
> Rob Landley wrote:
> > On Wednesday 06 June 2007 7:41 pm, H. Peter Anvin wrote:
> >> This makes vmlinux (normally stripped) recoverable from the bzImage file
> >> and so anything that is currently booting vmlinux would be serviced by
> >> this scheme.
> >
> > Would this make it sane to strip the initramfs image out of vmlinux with
> > objdump and replace it with another one, or are there offsets resolved
during
> > the build that stop that for vmlinux?
> >
>
> There probably are offsets resolved during the build. However, that
> wouldn't be all that hard to fix. Still, one can argue whether or not
> it is sane under any definition to do this kind of unpacking-repacking
> of ELF files.
Er, make that objcopy, not objdump.
Sane, maybe not. Something people want to do (and under the mistaken
assumption I know more about initramfs then they do, have asked me how), yes.
It always boils down to "do you have a vmlinux image lying around? Doing
this with a bzImage _is_ brain surgery", and has yet to get beyond that
question. I had about half of a script worked out for this, once...
You can also supply an external initramfs image through the initrd mechanism,
but this is unpleasant to do with some bootloaders (or lack of bootloaders).
Plus it doesn't remove the old one, and wasting space makes embedded
developers itch.
Rob
--
The Google cluster became self-aware at 2:14am EDT August 29, 2007...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists