From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Creating initrd
Date: Fri, 12 Oct 2012 09:10:43 +0200 [thread overview]
Message-ID: <20121012091043.746a65a1@skate> (raw)
In-Reply-To: <1349991931.14474.39.camel@Homeserver>
Dear Chris Wilkinson,
On Thu, 11 Oct 2012 17:45:31 -0400, Chris Wilkinson wrote:
> Clean/make on a stock v3.4.7 kernel gives the following
>
> -rw-r--r-- 1 chrisw chrisw 1.5M Oct 11 17:19 rootfs.cpio
> -rw-r--r-- 1 chrisw chrisw 718K Oct 11 17:19 rootfs.cpio.gz
> -rwxr-xr-x 1 chrisw chrisw 2.7M Oct 11 17:18 zImage
>
> So it seems that the size problem originates in my customized kernel.
> 2.7MB is still too big so I need to investigate the config settings in
> both my customized kernel and the stock one.
Ah, maybe your customized kernel configuration has gazillions of kernel
modules enabled, which make the size of the root filesystem enormous.
Could you pastebin your kernel config so we can confirm this?
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2012-10-12 7:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 14:05 [Buildroot] Creating initrd Chris Wilkinson
2012-10-11 14:48 ` Thomas Petazzoni
2012-10-11 15:16 ` Chris Wilkinson
2012-10-11 15:23 ` Thomas Petazzoni
2012-10-11 17:28 ` Chris Wilkinson
2012-10-11 18:53 ` Thomas Petazzoni
[not found] ` <1349988968.14474.34.camel@Homeserver>
[not found] ` <20121012091408.6184bb9f@skate>
[not found] ` <1350049738.14474.52.camel@Homeserver>
2012-10-12 14:12 ` Thomas Petazzoni
2012-10-12 15:19 ` Chris Wilkinson
2012-10-12 14:23 ` Thomas Petazzoni
2012-10-11 21:45 ` Chris Wilkinson
2012-10-12 7:10 ` Thomas Petazzoni [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=20121012091043.746a65a1@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