From: Darren Hart <dvhart@linux.intel.com>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: rootfs image size
Date: Thu, 27 Jan 2011 14:37:14 -0800 [thread overview]
Message-ID: <4D41F39A.5030001@linux.intel.com> (raw)
In-Reply-To: <625BA99ED14B2D499DC4E29D8138F1504DB5BB7593@shsmsx502.ccr.corp.intel.com>
On 01/26/2011 03:58 PM, Tian, Kevin wrote:
>> From: Chris Tapp
>> Sent: Wednesday, January 26, 2011 9:09 PM
>>
>> I know this is probably a basic question, but I'm not having much luck !
>>
>> I've built poky-image-minimal for atom-pc using the 0.9 Poky release.
>>
>> This gives me an ext3 rootfs of over 80MB, which doesn't sound minimal
>> to me ;-)
>
> This is a known issue in 0.9. the switch from ipk to rpm leaves some temporary files
> in the final ext3 rootfs, which results the large size.
>
>>
>> Can I reduce the size of the image, or is it expected to be this size?
>>
>> I've tried changing
>>
>> IMAGE_ROOTFS_SIZE_ext3 = "500000"
>
> This configuration option only works when it exceeds the size of generated rootfs,
> or else it will be changed implicitly to the actual size plus some extra buffer
>
>>
>> in atom-pc.conf to another value, but this didn't make any
>> difference to the image that gets created (by re-running bitbake poky-
>> image-minimal after making the above change).
>>
>> I've also tried using
>>
>> ROOT_FLASH_SIZE = "64"
>>
>> also without any luck.
>>
>> Any help would be much appreciated !
>>
>
> I'd suggest you to use the master to see whether it works for you.
>
> The alternative is to apply below commit to your 0.9 code:
>
> commit 5e384038cbd5035377d61a1b77ad23ab69e0cac0
> Author: Richard Purdie<richard.purdie@linuxfoundation.org>
> Date: Wed Jan 5 18:56:47 2011 +0000
>
> rootfs_rpm.bbclass: Remove temporary work files in install directory, saving work files in install directory, saving the manifests as logfiles into ${T}
>
> Signed-off-by: Richard Purdie<richard.purdie@linuxfoundation.org>
>
> diff --git a/meta/classes/rootfs_rpm.bbclass b/meta/classes/rootfs_rpm.bbclass
> index 33abe96..2f7d691 100644
> --- a/meta/classes/rootfs_rpm.bbclass
> +++ b/meta/classes/rootfs_rpm.bbclass
> @@ -202,8 +202,11 @@ EOF
> # remove lock files
> rm -f ${IMAGE_ROOTFS}${rpmlibdir}/__db.*
>
> - # remove resolver files and manifests
> - rm -f ${IMAGE_ROOTFS}/install/install.manifest
> + # Move manifests into the directory with the logs
> + mv ${IMAGE_ROOTFS}/install/*.manifest ${T}/
> +
> + # Remove all remaining resolver files
> + rm -f ${IMAGE_ROOTFS}/install
This needs to be "rm -rf", there is another patch in master that takes
care of this: 21fafc889e81411735de7d04ffe504e5cff4830d
--
Darren
>
> log_check rootfs
>
> Thanks
> Kevin
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2011-01-27 22:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-27 16:30 bsp doc bug Frans Meulenbroeks
2011-01-26 13:08 ` rootfs image size Chris Tapp
2011-01-26 23:58 ` Tian, Kevin
2011-01-27 9:50 ` Diego Sueiro
2011-01-27 22:37 ` Darren Hart [this message]
2011-01-28 0:20 ` Tian, Kevin
2011-01-27 13:34 ` Aleksandr Koltsoff
2011-01-27 15:22 ` Mark Hatle
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=4D41F39A.5030001@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=kevin.tian@intel.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.