Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Qi.Chen@windriver.com
Cc: qingtao.cao@windriver.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] core-image-sato.bb: increase free space size
Date: Wed, 03 Apr 2013 08:28:37 -0700	[thread overview]
Message-ID: <515C4AA5.4040501@linux.intel.com> (raw)
In-Reply-To: <3d56b617bac180023326d302a14d675710d4380d.1364969701.git.Qi.Chen@windriver.com>

On 04/02/2013 11:16 PM, Qi.Chen@windriver.com wrote:
> From: Chen Qi <Qi.Chen@windriver.com>
>
> Sato images, by default, have about 100M free space. This is not enough
> and it blocks automatic testing.
>
> This patch fixes this problem by setting the default value of
> IMAGE_OVERHEAD_FACTOR to "2.0" in the sato image recipe.
>
We need to think hard about this one, we have a couple of conflicting 
interests here with the amount of space.

The Poky distro and core-image-sato are examples of for the community 
and developers to use, we want to set good examples where ever possible. 
One of the intentions of core-image-sato is to show a compact image with 
a graphical user interface, so having a minimal, but usable amount of 
free space is important. We don't want someone new to look at this and 
see a large image as it might put them off the project without 
understanding the tune-ability. This is an embedded environment, not a 
desktop with a large disk, we want to share that message.

Another goal of the Poky distro is to create something that is testable 
and automated testing is important part of this.  I read the bug report 
and commented on it as well.  Is there a way to clean-up after the 
tests?  Are single tests consuming the 100M available? Is it slowly 
accumulating tmp space?

What other options can we do here?  Do we need to consider a different 
image for testing?  Or build 2 images similarly one with extra space?

We need to think about the different scenarios and usage.

Thanks
	Sau!


> [YOCTO #4109]
>
> Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
> ---
>   meta/recipes-sato/images/core-image-sato.bb |    4 ++++
>   1 file changed, 4 insertions(+)
>
> diff --git a/meta/recipes-sato/images/core-image-sato.bb b/meta/recipes-sato/images/core-image-sato.bb
> index e3246d2..4b4e595 100644
> --- a/meta/recipes-sato/images/core-image-sato.bb
> +++ b/meta/recipes-sato/images/core-image-sato.bb
> @@ -9,3 +9,7 @@ LICENSE = "MIT"
>   inherit core-image
>
>   IMAGE_INSTALL += "packagegroup-core-x11-sato-games"
> +
> +# Increase the default value of IMAGE_OVERHEAD_FACTOR from "1.3" to "2.0"
> +# to increase the free space size in sato images.
> +IMAGE_OVERHEAD_FACTOR ?= "2.0"
>



      reply	other threads:[~2013-04-03 15:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-03  6:16 [PATCH 0/2] Increase free space size on sato images Qi.Chen
2013-04-03  6:16 ` [PATCH 1/2] bitbake.conf: use weaker assignment for IMAGE_OVERHEAD_FACTOR Qi.Chen
2013-04-03  6:16 ` [PATCH 2/2] core-image-sato.bb: increase free space size Qi.Chen
2013-04-03 15:28   ` Saul Wold [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=515C4AA5.4040501@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=Qi.Chen@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=qingtao.cao@windriver.com \
    /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