From: Warren Togami <wtogami-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Subodh Nijsure
<nijsure.subodh-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
initramfs <initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Adding ramdisk/initramfs data to kernel post build
Date: Wed, 22 Jul 2009 22:04:13 -0400 [thread overview]
Message-ID: <4A67C51D.40102@redhat.com> (raw)
In-Reply-To: <110c8b2e0907221029u1d0f2ad5jeadbf017cc2d2f7-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 07/22/2009 01:29 PM, Subodh Nijsure wrote:
> Hello,
>
> I am exploring ways to add combine kernel and ramdisk into single
> image on X86 platform.
>
> (Unfortunately) the way build system is working kernel is built before
> the modules that need to go into the ramdisk.
>
> I have been looking at addRmdisk.c found in arch/powerpc/boot/
> directory and see if I can use it.
>
> Within the initramfs infrastructure is there way to patch in the
> initrd/initramfs into kernel that has already been built?
For what purpose?
Tools like wraplinux will wrap a kernel and initrd image (like generated
by dracut) into a single image file, either NBI or ELF format.
Warren Togami
wtogami-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
--
To unsubscribe from this list: send the line "unsubscribe initramfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-07-23 2:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 17:29 Adding ramdisk/initramfs data to kernel post build Subodh Nijsure
[not found] ` <110c8b2e0907221029u1d0f2ad5jeadbf017cc2d2f7-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-07-23 2:04 ` Warren Togami [this message]
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=4A67C51D.40102@redhat.com \
--to=wtogami-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=nijsure.subodh-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.