All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: "Hans Beckérus" <hans.beckerus@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: remove /boot/uImage and /usr/share/terminfo
Date: Fri, 15 Mar 2013 07:20:51 -0700	[thread overview]
Message-ID: <51432E43.7060708@windriver.com> (raw)
In-Reply-To: <CAFyqS9rzC5ueHXBKnzt7JnfWKKSvBkXBEL3px3vh3itEXaRWqg@mail.gmail.com>

On 13-03-15 06:33 AM, Hans Beckérus wrote:
> Hi. In an effort to shrink our rootfs by some major numbers we found two
> low-hanging fruits that we would like to address before cherry picking
> and removing lots of good linux functionality. We have no need for the
> uImage (3MB) stored in /boot and also we can leave out the terminfo tree
> (2.5MB).
> My question here now is if the build system provide functionality to
> actually tell the image builder not to include these specific components?

 From kernel.bbclass, you just need to clear RDEPENDS_kernel-base
in your .conf files:

# Allow machines to override this dependency if kernel image files are
# not wanted in images as standard
RDEPENDS_kernel-base ?= "kernel-image"

You'll still get your kernel modules installed after making this change.

Bruce

> Or do we need to write some post installer for our rootfs that mounts
> the image, removes the files, and then umount it?
> If we remove inclusion of any kernel modules it seems that /boot is
> never populated? But we need the modules. Also, what package brings in
> terminfo?
> Is it as simple as writing a .bbappend to remove it att deploy time?
>
> Hans
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>



  reply	other threads:[~2013-03-15 14:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-15 13:33 remove /boot/uImage and /usr/share/terminfo Hans Beckérus
2013-03-15 14:20 ` Bruce Ashfield [this message]
2013-03-15 14:36   ` Hans Beckérus
2013-03-15 14:41     ` Bruce Ashfield
2013-03-15 15:36       ` Hans Beckérus

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=51432E43.7060708@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=hans.beckerus@gmail.com \
    --cc=yocto@yoctoproject.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.