linux-kernel - Re: Way to combine kernel and initrd on x86 platform?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <4A68DFC4.5070809@zytor.com>
Date:	Thu, 23 Jul 2009 15:10:12 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Subodh Nijsure <nijsure.subodh@...il.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: Way to combine kernel and initrd on x86 platform?

Subodh Nijsure wrote:
> 
> Sorry if I am not being very smart  here, confused by the remark "
> bzImage support would not be possible"
> 
> I was able create wrapped image using command
> 
> wraplinux -p "console=ttyS0,115200" -i initrd.gz -o
> vmlinux.initrd.wrap arch/i386/boot/bzImage
> 
> I am using wraplinux version 1.6
> 
> if I use any other image  wraplinux doesn't find the version
> information and initrd image doesn't get attached.
> 
> What file should I be specifying as the 'kernel' when I execute
> wrapimage  if not the bzImage?
> 
> ( I am working with 2.6.23 kernel)
> 
> On my board I can boot the standard bzImage, but not able to load the
> wrapped image produced by wraplinux command. Would very much
> appreciate hints...
> 

What I mean is that Wraplinux accepts bzImage as input and outputs ELF,
NBI or Multiboot.  Depending on the bootloader on your board, you may
need to select one or the other of these formats, or might not be able
to at all.  It does not *output* bzImage, and it isn't 100% trivial to
make it do so.

	-hpa

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