On 10 April 2013 17:42:28 Paul Eggleton <paul.eggle...@linux.intel.com> wrote:
Mount /var/volatile ourselves so that we can set up the writable area
first. This fixes the urandom service not starting properly when
read-only-rootfs is enabled.
Signed-off-by: Paul Eggleton <paul.eggle...@linux.intel.com>
---
.../initscripts/initscripts-1.0/read-only-rootfs-hook.sh | 1 +
meta/recipes-core/initscripts/initscripts_1.0.bb | 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git
a/meta/recipes-core/initscripts/initscripts-1.0/read-only-rootfs-hook.sh
b/meta/recipes-core/initscripts/initscripts-1.0/read-only-rootfs-hook.sh
index 4f3e0d9..9cf0921 100644
--- a/meta/recipes-core/initscripts/initscripts-1.0/read-only-rootfs-hook.sh
+++ b/meta/recipes-core/initscripts/initscripts-1.0/read-only-rootfs-hook.sh
@@ -5,6 +5,7 @@
[ "$ROOTFS_READ_ONLY" = "no" ] && exit 0
if [ "$1" = "start" ] ; then
+ grep -q "tmpfs /var/volatile" /proc/mounts || mount /var/volatile
Or just use mountpoint(1)?
Sent with AquaMail for Android
http://www.aqua-mail.com
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
