From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Why can't I see any effects by different rootfs compression methods ??
Date: Thu, 06 Feb 2014 18:11:04 +0100 [thread overview]
Message-ID: <52F3C228.2080002@mind.be> (raw)
In-Reply-To: <52F361B10200004600049F5D@gwia2.rz.hs-offenburg.de>
On 06/02/14 10:19, Frank Ihle wrote:
> Hi,
>
> I'm using Buildroot to generate a uImage with a kernel, which in the end
> starts busybox. I tried the different compression modes (kernel
> compression, built-in initramfs compression and the rootfs compression).
> The first 2 options worked quiet well but when it comes to apply
> different compression methodes (e.g. LZMA, bzip2) on rootfs in make
> menuconfig nothing changes, neither size nor decompress time.
>
> Why is it like that ? And how can I extract files of the generated
> uImage, so that i can see what really has been compressed ?
The rootfs compression only affects the rootfs image that is generated
in output/images, not the initramfs that is linked into the kernel. The
latter is purely controlled by kernel options (which you did).
Note that built-in initramfs compression is pointless, because it will
be compressed again with the kernel compression method - and that usually
increases the size rather than decreasing it.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2014-02-06 17:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 9:19 [Buildroot] Why can't I see any effects by different rootfs compression methods ?? Frank Ihle
2014-02-06 17:11 ` Arnout Vandecappelle [this message]
2014-02-07 7:14 ` [Buildroot] Antw: " Frank Ihle
2014-02-07 9:15 ` Arnout Vandecappelle
2014-02-07 14:14 ` Mike Zick
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=52F3C228.2080002@mind.be \
--to=arnout@mind.be \
--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 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.