]> code.ossystems Code Review - openembedded-core.git/commit
init-live.sh: distinguish between a read-only image and a read-write image
authorChen Qi <Qi.Chen@windriver.com>
Wed, 11 Sep 2013 05:01:55 +0000 (13:01 +0800)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Wed, 11 Sep 2013 10:04:05 +0000 (11:04 +0100)
commit29f869b68a9017502f75915784a924f0fe9d4be1
tree3d50b86d1d9179ba7cd1e34297f555246dbee6b2
parent1b0602b5933b3ee8e4ae36d447bf881308528a47
init-live.sh: distinguish between a read-only image and a read-write image

The iso and hddimg share a common concept of 'live image', and they
use the same initramfs and thus the same init. However, that init
script in initramfs made a wrong assumption that the rootfs image
was read-only by itself. This is apparently not true for hddimg.

To make things work as expected, this init script should at least
distinguish between a read-only rootfs image and a read-write one.

This patch adds this ability to the init script. After this change,
the init script would be able to check whether the rootfs image is
read-only or not. If the rootfs image is read-write, the image will
be mounted and then booted directly. No union mounts will be attempted
in this case.

[YOCTO #5164]

Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meta/recipes-core/initrdscripts/files/init-live.sh