From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Troubles with initramfs
Date: Tue, 31 Jul 2012 20:26:29 +0200 [thread overview]
Message-ID: <20120731202629.0b748b41@skate> (raw)
In-Reply-To: <CAE9DZUQ+QfGcX+K_Byf1p_E2bvkP48-7CQ9Kn3jC6Vs1FepuAg@mail.gmail.com>
Hello,
Le Tue, 31 Jul 2012 10:59:39 -0500,
Dallas Clement <dallas.a.clement@gmail.com> a ?crit :
> [dallasc /development/dallasc/buildroot-2011.05-sdk6.0] ls -l output/images/
> total 76116
> -rw-r--r-- 1 dallasc dallasc 514194 Jul 31 15:30 rootfs.initramfs
> -rw-r--r-- 1 dallasc dallasc 77424640 Jul 31 15:16 rootfs.tar
How can you get a rootfs.initramfs file? I don't think it's possible to
get such an image with the default Buildroot.
With the default Buildroot, when you enable the initramfs file format,
it's the entire root filesystem that gets included as an initramfs into
the kernel.
If you decided to follow Avery's suggestion (creating a separate
initramfs that includes selected parts of the real root filesystem),
then you should probably not use Buildroot initramfs capabilities, and
simply configure your kernel to point CONFIG_INITRAMFS_SOURCE to your
special initramfs.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-07-31 18:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 15:59 [Buildroot] Troubles with initramfs Dallas Clement
2012-07-31 18:26 ` Thomas Petazzoni [this message]
2012-07-31 18:44 ` Dallas Clement
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=20120731202629.0b748b41@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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