that patch is already in thud branch of poky i'm using ... yes, that seems to have solved things for now: INHERIT_remove = "uninative" moving on to the next head-scratcher ... rday --

Signed-off-by: Armin Kuster <akuster808@...> --- meta-cgl-common/recipes-kernel/linux/files/cfg/00004-kgdb.cfg | 1 - meta-cgl-common/recipes-kernel/linux/files/cfg/00005-quota.cfg

Maybe just as a "metadata collection repo"? IMHO from a OE perspective, a "layer" is a metadata set which provides its own layer.conf file (which, as you say, means you can add it to your project's

yes, to both questions. if you need example from other recipes, have a look at meta-openembedded and run: git grep ".*install.*cron"

Hi, I try to figure out how to build cron job in Yocto image, my current image does not have /etc/cron.d, is it correct I need to install the cronie package

Only on a Raspberry Pi 3 so far (uboot supported is already present for it). ________________________________________ Sent: Friday, May 03, 2019 11:16 To: Jaquier Cyril Cc: Yocto discussion

the more i think about it, the more i'm nervous about the phrase "container layer", as it suggests a "layer" of some kind in the context of OE. the one distinction i think worth making is that a

Hey, We’ve a product group with different devices, each having their machine-conf, eg Device_a Device_a_mini Device_b Device_b_mini <- Upcoming Device_c <- Upcoming Since device_a and

That list needs updating as there's a few more available now such as Balena and UpdateHub, but both Mendor and swupdate are both still going strong and have supported integration. I've heard good

Thanks Jaquier, did you run mender in an embedded system?

Accidentally I made this a private discussion - make it public again so others with similar issues might not need to ask again :) Andreas

Hi, I've been experimenting with mender a bit lately. Works great so far and it's fully integrated into yocto: https://mender.io/ There are a few other solutions available for

Hi Gabriele, use your custom image recipe as before to just produce your root- filesystem which results in a (compressed) tar-file in ${DEPLOY_DIR_ IMAGE}. It will be referenced from the genimage

This is not something Yocto comes with out of the box, but both rauc and swupdate provides a meta layer you could use. https://github.com/rauc/meta-rauc https://github.com/sbabic/meta-swupdate

Hi, Are there any Yocto recipes to support dual version control for firmware image upgrade and boot? The scenario is to make 2 partitions, one partition to install a work version of image, say v1.0,

Signed-off-by: Armin Kuster <akuster808@...> --- recipes-kernel/linux/linux-yocto-5.0/apparmor.cfg | 6 ------ 1 file changed, 6 deletions(-) diff --git

bug fix release. Signed-off-by: Armin Kuster <akuster808@...> --- .../libseccomp/{libseccomp_2.4.0.bb => libseccomp_2.4.1.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename

Signed-off-by: Armin Kuster <akuster808@...> --- meta-cgl-common/packagegroups/packagegroup-cgl-middleware.bb | 1 - 1 file changed, 1 deletion(-) diff --git

corosync 2.x can replace corosync 1.x + openais. openais is no longer maintainted and shutdown. https://github.com/corosync/openais/commit/f2bc4445a7c4ba5d17a218af855dc19d55ed2803 Signed-off-by:

corosync 1.x have removed from meta-cgl, and use corosync under meta-networking. corosync 2.x can replace corosync 1.x + openais (in meta-cgl), so remove depend on openais Signed-off-by: Armin