All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Urban <urban@unix-beratung.de>
To: buildroot@busybox.net
Subject: [Buildroot] (apparently) HUGE kernel
Date: Fri, 06 Mar 2009 00:35:05 +0100	[thread overview]
Message-ID: <49B061A9.7020404@unix-beratung.de> (raw)

Hi Folks,

I'm trying to build a modest linux-2.6.28.7 kernel for a VIA C3 based
router/firewall which will boot from CF-card.

I've removed everything I can think of that is superfluous for my
application, things like virtualization, various things to support SMP,
almost all debug options, etc.  I've only left the IPV4 networking,
netfilter, QoS, a bit of USB support, etc.

Still the kernel (bzImage) is 12MB large.  gah.  On my Fedora10 system the
kernel is 2.5MB large.  A 12MB kernel isn't the end of the world, but it
just seems too large.

I would be grateful if someone could have a look at my config-file and
possibly offer an explanation.  The config file is here:

	http://www.spielwiese.de/rob/Buildroot/linux-config

cheers,

Rob Urban

             reply	other threads:[~2009-03-05 23:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-05 23:35 Robert Urban [this message]
2009-03-06  0:19 ` [Buildroot] (apparently) HUGE kernel Robert Urban

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=49B061A9.7020404@unix-beratung.de \
    --to=urban@unix-beratung.de \
    --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.