Hi Saul,
On 26.07.2013 21:52, Saul Wold wrote:
On 07/26/2013 05:35 AM, Jukka Rissanen wrote:
oFono test scripts are very useful so enable those by default.
Signed-off-by: Jukka Rissanen
---
meta/recipes-connectivity/ofono/ofono.inc | 3 ++-
meta/recipes-connectivity/ofono/ofono_1.12.bb
OK, thanks, will handle it this week.
Regards,
/Cristian
-Original Message-
From: Saul Wold [mailto:s...@linux.intel.com]
Sent: Monday, July 29, 2013 9:40 AM
To: Iorga, Cristian; 'Patches and discussions about the oe-core layer'
Cc: Burton, Ross
Subject: Re: Thoughts about bluez4 and blue
On 07/28/2013 11:34 PM, Iorga, Cristian wrote:
Back from the past!!
-Original Message-
From: Iorga, Cristian
Sent: Friday, July 26, 2013 8:51 AM
To: 'Saul Wold'; 'Patches and discussions about the oe-core layer'; Burton, Ross
Subject: RE: Thoughts about bluez4 and bluez5
Hi Saul, Ross,
Op 26 jul. 2013, om 11:35 heeft "Burton, Ross" het
volgende geschreven:
> On 26 July 2013 08:14, Saul Wold wrote:
>> Emilia Ciobanu (12):
>> babeltrace: fix recipe name
>> build-appliance-image: fix recipe name add GIT revision to PV variable
>> chkconfig-alternatives-native: fix recipe nam
qemuarm.conf: provide a common qemuarm machine configuration,
so developer/distributor can customize their specific one.
Although, we can modify the meta/conf/machine/qemuarm.conf to customize our
configuration,but it's uncomfortable for developer/distributor maintaining
their branch.
After applyi
qemuxmips64.conf: provide a common qemumips64 machine configuration,
so developer/distributor can customize their specific one.
Although, we can modify the meta/conf/machine/qemuxmips64.conf to customize our
configuration, but it's uncomfortable for developer/distributor maintaining
their branch.
qemumips.conf: provide a common qemumips machine configuration,
so developer/distributor can customize their specific one.
Although, we can modify the meta/conf/machine/qemumips.conf to customize our
configuration, but it's uncomfortable for developer/distributor maintaining
their branch.
After ap
qemuppc.conf: provide a common qemuppc machine configuration,
so developer/distributor can customize their specific one.
Although, we can modify the meta/conf/machine/qemuppc.conf to customize our
configuration, but it's uncomfortable for developer/distributor maintaining
their branch.
After apply
qemux86-64.conf: provide a common qemux86-64 machine configuration,
so developer/distributor can customize their specific one.
Although, we can modify the meta/conf/machine/qemux86-64.conf to customize our
configuration, but it's uncomfortable for developer/distributor maintaining
their branch.
A
qemux86.conf: provide a common qemux86 machine configuration,
so developer/distributor can customize their specific one.
Although, we can modify the meta/conf/machine/qemux86.conf to customize our
configuration, but it's uncomfortable for developer/distributor maintaining
their branch.
After app
The main purposes are following.
- make it possible for developers/distributor to customize their specific
machine
based common machine configurations such as meta/conf/machine/inc/qemuxx.inc
- make our specific machine compatible with bb file which depends on
COMPATIBLE_MACHINE="qemuxx|..."
From: Chen Qi
If we're building a read-only rootfs, we'll get the following error now
and then.
tar: .: file changed as we read it
The root cause is that we spawn background process at rootfs time.
When the tar command is running, it's possible that files under rootfs
are changed by backgro
From: Chen Qi
This directory needs to be writable for system to work correctly.
[YOCTO #4103]
[YOCTO #4885]
Signed-off-by: Chen Qi
---
meta/recipes-extended/lighttpd/lighttpd_1.4.32.bb |3 +++
1 file changed, 3 insertions(+)
diff --git a/meta/recipes-extended/lighttpd/lighttpd_1.4.32.bb
From: Chen Qi
At some point, the udev was modified to source the functions from
initscripts or lsbinitscripts. This dependency is actually not needed.
If we use udev in a system where initscripts from oe-core is not available,
there will be errors.
This patch fixes this problem by removing the i
From: Chen Qi
It's possible that a 'No such directory' error occurs when doing
check_requirement in populate-volatile.sh at rootfs time. This is
because the $ROOT_DIR/var/tmp might be a dead link.
Use $ROOT_DIR/var/volatile/tmp as the TMPDIR instead to avoid this
error.
[YOCTO #4883]
[YOCTO #41
From: Chen Qi
Previously, we had two ways to check whether the rootfs was read-only.
In some part of the system, we determined whether the rootfs is read-only
by checking the fstab or /proc/mounts; in other part of the system, we
used the value of ROOTFS_READ_ONLY in /etc/default/rcS as a criteri
From: Chen Qi
Change from V1:
1. Disable the generating of ssh keys at rootfs time
2. Add a mechanism to read-only-rootfs-hook.sh to check whether a directory is
on a read-only partition.
3. Fix a new bug#4937 (https://bugzilla.yoctoproject.org/show_bug.cgi?id=4937)
The following changes since
From: Chen Qi
If the live image is mounted as read-only, we cannot make necessary
directories under $ROOT_MOUNT/media, so trying to move the mount points
lead to errors.
So in case that no unification filesystem mechanism is available in kernel
and the rootfs is mounted as read-only, we mount tm
From: Chen Qi
The QEMUOPTIONS for ISOFS was not complete, leading to failures when
trying to start X in live images.
This patch fixes this problem.
[YOCTO #4103]
[YOCTO #4884]
Signed-off-by: Chen Qi
---
scripts/runqemu-internal |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -
From: Chen Qi
Packages in our system may need to write to some directories to function
correctly. In read-only rootfs, these directories should be made writable.
This patch uses a convenient and uniform way to handle such situations.
The read-only-rootfs-hook.sh script searches the /etc/default/
From: Chen Qi
If the rootfs is read-only and the ssh keys are not available at system
start-up, the init script will generate ssh keys into /etc/ssh, thus
causing a 'read-only file system' error.
Make this directory writable in case of a read-only rootfs.
Note that if the ssh keys are pregenerat
From: Chen Qi
This diretory needs to be writable, the following error will appear
at system start-up.
/etc/rc5.d/S20irattach: /etc/sysconfig/irda: Read-only file system
[YOCTO #4103]
[YOCTO #4886]
Signed-off-by: Chen Qi
---
.../irda-utils/irda-utils_0.9.18.bb|4
1
Thanks for all the reviews and comments.
I'll drop this patch and send out a version 2 of this patchset.
Best Regards,
Chen Qi
On 07/26/2013 03:39 PM, qi.c...@windriver.com wrote:
From: Chen Qi
To avoid generating ssh keys every time a system with read-only rootfs
starts, we generate ssh keys
opensslconf.h conflicts between 32-bit and 64-bit versions.
Signed-off-by: Ming Liu
---
meta/recipes-connectivity/openssl/openssl.inc |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/meta/recipes-connectivity/openssl/openssl.inc
b/meta/recipes-connectivity/openssl/open
On 07/27/2013 02:10 AM, Saul Wold wrote:
On 07/16/2013 10:15 PM, Ming Liu wrote:
opensslconf.h conflicts between 32-bit and 64-bit versions.
Signed-off-by: Ming Liu
---
meta/recipes-connectivity/openssl/openssl.inc |5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a
This is necessary to get the build going, for instance with older Code Sourcery
compilers.
It is also disabled in upstream due to this very reason. The details can be
found on the following links:
http://comments.gmane.org/gmane.linux.busybox/30999
http://git.busybox.net/busybox/commit/?h=1_21_st
On 07/28/2013 03:48 AM, Paul Eggleton wrote:
On Saturday 27 July 2013 23:30:50 Saul Wold wrote:
Paul, Ross, Richard:
This is part 2 of the C-Pull, part one was reviewed and ACK'ed on Friday,
these where some changes that have come in since, there are some additional
changes that I still need to
On Saturday 27 July 2013 23:30:50 Saul Wold wrote:
> Paul, Ross, Richard:
>
> This is part 2 of the C-Pull, part one was reviewed and ACK'ed on Friday,
> these where some changes that have come in since, there are some additional
> changes that I still need to review (Read-Only Rootfs specificly).
28 matches
Mail list logo
