public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Vivek Goyal <vgoyal@in.ibm.com>,
	Rusty Russell <rusty@rustcorp.com.au>, Andi Kleen <ak@suse.de>,
	v12n <virtualization@lists.linux-foundation.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC 6/7] i386: make the bzImage payload an ELF file
Date: Thu, 7 Jun 2007 12:08:04 -0400	[thread overview]
Message-ID: <200706071208.04777.rob@landley.net> (raw)
In-Reply-To: <46676552.4060308@zytor.com>

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...

  reply	other threads:[~2007-06-07 16:08 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-06 22:58 [PATCH RFC 0/7] proposed updates to boot protocol and paravirt booting Jeremy Fitzhardinge
2007-06-06 22:58 ` [PATCH RFC 1/7] update boot spec to 2.07 Jeremy Fitzhardinge
2007-06-06 22:58 ` [PATCH RFC 2/7] add WEAK() for creating weak asm labels Jeremy Fitzhardinge
2007-06-06 22:58 ` [PATCH RFC 3/7] allow linux/elf.h to be included in assembler Jeremy Fitzhardinge
2007-06-06 22:58 ` [PATCH RFC 4/7] define ELF notes for adding to a boot image Jeremy Fitzhardinge
2007-06-06 22:58 ` [PATCH RFC 5/7] i386: clean up bzImage generation Jeremy Fitzhardinge
2007-06-06 22:58 ` [PATCH RFC 6/7] i386: make the bzImage payload an ELF file Jeremy Fitzhardinge
2007-06-06 23:41   ` H. Peter Anvin
2007-06-06 23:56     ` Jeremy Fitzhardinge
2007-06-07  0:08       ` H. Peter Anvin
2007-06-07  0:20         ` Jeremy Fitzhardinge
2007-06-07  0:42           ` H. Peter Anvin
2007-06-07  1:01             ` Jeremy Fitzhardinge
2007-06-08  3:49             ` Vivek Goyal
2007-06-08  4:01               ` H. Peter Anvin
2007-06-07  1:47     ` Rob Landley
2007-06-07  1:54       ` H. Peter Anvin
2007-06-07 16:08         ` Rob Landley [this message]
2007-06-07 16:14           ` H. Peter Anvin
2007-06-06 22:58 ` [PATCH RFC 7/7] i386: paravirt boot sequence Jeremy Fitzhardinge

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200706071208.04777.rob@landley.net \
    --to=rob@landley.net \
    --cc=ak@suse.de \
    --cc=ebiederm@xmission.com \
    --cc=hpa@zytor.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=vgoyal@in.ibm.com \
    --cc=virtualization@lists.linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox