[OE-core] [PATCH 0/1] init-live.sh: avoid duplicate mount points

2012-12-30 Thread Qi.Chen
From: Chen Qi The following changes since commit 4a36a32567ecfbc7ce7b967803e6e23314953ef5: libpng: fix packaging (2012-12-26 11:34:09 +) are available in the git repository at: git://git.pokylinux.org/poky-contrib ChenQi/live-image http://git.pokylinux.org/cgit.cgi/poky-contrib/log/

[OE-core] [PATCH 1/1] init-live.sh: avoid duplicate mount points for the same filesystem

2012-12-30 Thread Qi.Chen
From: Chen Qi A live system had duplicate mount points for the same filesystem in the output of 'mount' command. That was because we didn't handle the temporary mounts properly before switch_root. This patch fixes this problem by moving the mount points of some filesystems to the corresponding d

[OE-core] [PATCH V5 1/4] sysvinit: add ROOTFS_READ_ONLY variable to rcS-default

2012-12-30 Thread Qi.Chen
From: Chen Qi This variable indicates whether the rootfs is intended to be read-only or not. Changing this value from 'no' to 'yes' on a currently running system with read-write rootfs and rebooting will give the user a working system with read-only rootfs. However, it is not suggested to change

[OE-core] [PATCH V5 4/4] initscripts: support read-only rootfs

2012-12-30 Thread Qi.Chen
From: Chen Qi To support a read-only rootfs, we use symbolic links which point to volatile storage to create the illusion that some directories are writable. Improve populate-volatile.sh script to support read-only rootfs. Add two default config files specific to read-only-rootfs image. [YOCTO

[OE-core] [PATCH V5 2/4] image.bbclass: add two hook funtions

2012-12-30 Thread Qi.Chen
From: Chen Qi read_only_rootfs_hook: this funtion is invoked only if 'read-only-rootfs' is in IMAGE_FEATURES. It tweaks some basic files and makes populate- volatile.sh script run at rootfs time. choose_volatile_conf_file: this function is invoked no matter 'read-only-rootfs' is in IMAGE_FEATURE

[OE-core] [PATCH V5 3/4] core-image.bbclass: support read-only-rootfs image feature

2012-12-30 Thread Qi.Chen
From: Chen Qi Two hook functions are appended to ROOTFS_POSTPROCESS_COMMAND properly to support the 'read-only-rootfs' image feature. [YOCTO #3406] Signed-off-by: Chen Qi --- meta/classes/core-image.bbclass |7 +-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/meta/cla

[OE-core] some inconsistencies with valgrind support in recipe vs packagegroup-core-tools-profile.bb

2012-12-30 Thread Robert P. J. Day
from poking around in packagegroup files, the following observation. first, there's the valgrind recipe itself, which suggests at least armv7a support: COMPATIBLE_HOST = '(i.86|x86_64|powerpc|powerpc64).*-linux' COMPATIBLE_HOST_armv7a = 'arm.*-linux' inherit autotools EXTRA_OECONF = "--enable

[OE-core] any objection to my cleaning up some packagegroup files in oe-core?

2012-12-30 Thread Robert P. J. Day
specifically, in cases like this in packagegroup-core-sdk.bb: RDEPENDS_packagegroup-core-sdk could more cleanly be expressed as: RDEPENDS_${PN} could it not? there are quite a few of those unnecessarily verbose constructs, anyone mind if i submit a patch to make that change? rday -- ===

Re: [OE-core] disk space problem

2012-12-30 Thread Yi Qingliang
On Saturday, December 29, 2012 06:07:27 PM Otavio Salvador wrote: > On Sat, Dec 29, 2012 at 1:09 PM, Yi Qingliang wrote: > > When using poky, I got following problem: > > > > WARNING: The free inode of /dev/md127 is running low (0.000K left) > > ERROR: Immediately abort since the disk space mon

[OE-core] packagegroups: equally referenced as recipe or with IMAGE_FEATURES?

2012-12-30 Thread Robert P. J. Day
simple question re: packagegroups -- are they equally included in a build, or image, or whatever, using either of the two techniques: 1) as a basic recipe file 2) using IMAGE_FEATURES if it's mentioned in core-image.bbclass? rday -- ==