bsp doc bug

bsp doc bug

[Frans Meulenbroeks]

I was trying to create a bsp layer. In the doc I bumped into the
following example for layer.conf:

# We have a conf directory, add to BBPATH
BBPATH := "${BBPATH}${LAYERDIR}"

[...]

Isn't there a colon mssing here.
If I look at the layer.conf of meta-ememlow it does have a colon:

BBPATH := "${BBPATH}:${LAYERDIR}"

Guess this is a typo in the doc (both html and pdf have this)

Frans

rootfs image size

[Chris Tapp]

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 ;-)

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"

  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 !

Chris

Re: rootfs image size

[Tian, Kevin]

> 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

        log_check rootfs

Thanks
Kevin

Re: rootfs image size

[Diego Sueiro]

[-- Attachment #1: Type: text/plain, Size: 2834 bytes --]

Chris,

Take a look at your local.conf and see what is included
on EXTRA_IMAGE_FEATURES.
Removing them you will save lots of space too.

Regards,

--
*dS
Diego Sueiro

/*long live rock 'n roll*/


On Wed, Jan 26, 2011 at 9:58 PM, Tian, Kevin <kevin.tian@intel.com> 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
>
>        log_check rootfs
>
> Thanks
> Kevin
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>

[-- Attachment #2: Type: text/html, Size: 3830 bytes --]

Re: rootfs image size

[Aleksandr Koltsoff]

Chris Tapp wrote:
> 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 ;-)
> 
> Can I reduce the size of the image, or is it expected to be this size?

Hi there,

The rpm packaging version does has some issues (half-statically built
binaries, full SAT-solver which might be an overkill for a minimal
image, etc).

I got much better results by switching to PACKAGE_CLASSES ?=
"package_ipk" in local.conf.

This will not be an RPM based system, but the image size will be
significantly smaller (especially if you're trying to reduce minimal).

Also, some fixes (post 0.9) should drop the rpm size requirement a bit,
if you want to try git/master.

regards,

ak.
-- 
Best regards,

Aleksandr Koltsoff
Head of Software Development, EKE Building Technology Systems
+358 44 566 2030, Piispanportti 7, 02240 Espoo, Finland
-= Easy Home Control for Everyone @ www.ebts.fi =-

Re: rootfs image size

[Mark Hatle]

On 1/27/11 7:34 AM, Aleksandr Koltsoff wrote:
> Chris Tapp wrote:
>> 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 ;-)
>>
>> Can I reduce the size of the image, or is it expected to be this size?
> 
> Hi there,
> 
> The rpm packaging version does has some issues (half-statically built
> binaries, full SAT-solver which might be an overkill for a minimal
> image, etc).

Many of these items are resolved in the mhatle/rpm5 branch that is part of
poky-contrib.  I'm trying to get the work finished for inclusion in the next day
or so.

But for a minimal image, RPM likely is too big of a hammer for the filesystem
design you want and IPK is likely more useful to you.

The place where I see RPM being needed is in medium size to larger (CGL) style
systems.  Also places where a sat solver is necessary for field upgrades... even
though thats not quite working yet.

--Mark

> I got much better results by switching to PACKAGE_CLASSES ?=
> "package_ipk" in local.conf.
> 
> This will not be an RPM based system, but the image size will be
> significantly smaller (especially if you're trying to reduce minimal).
> 
> Also, some fixes (post 0.9) should drop the rpm size requirement a bit,
> if you want to try git/master.
> 
> regards,
> 
> ak.

Re: rootfs image size

[Darren Hart]

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

Re: rootfs image size

[Tian, Kevin]

> From: Darren Hart [mailto:dvhart@linux.intel.com]
> Sent: Friday, January 28, 2011 6:37 AM
> 
> 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
> 

Thanks for the catch-up. I do remember that you dig it out but not realize related here. :-)

Thanks
Kevin