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:41:00 -0700	[thread overview]
Message-ID: <514332FC.2070805@windriver.com> (raw)
In-Reply-To: <CAFyqS9qmjLqMoXkqdFCvzHN_dMcZOd5yn0tgUR4iX5bGdvSSVQ@mail.gmail.com>

On 13-03-15 07:36 AM, Hans Beckérus wrote:
>
>
> On Fri, Mar 15, 2013 at 3:20 PM, Bruce Ashfield
> <bruce.ashfield@windriver.com <mailto:bruce.ashfield@windriver.com>> wrote:
>
>     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
>
>
> Thanks Bruce.How could I have missed that? I believe I scanned through
> the kernel.bbclass for something like this.
> Also got some good tip regarding /usr/share/terminfo? Guess I need to
> figure out what package drags it in ;)

Not off the top of my head. Hopefully someone else with experience in
that area will notice the traffic and jump in :)

I'm fairly certain that is is controllable, since in the past, I've
known it to be removed and tuned for small systems, so it's not a
completely uncommon thing to do.

Cheers,

Bruce

>
> Hans
>



  reply	other threads:[~2013-03-15 14:41 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
2013-03-15 14:36   ` Hans Beckérus
2013-03-15 14:41     ` Bruce Ashfield [this message]
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=514332FC.2070805@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.