From: <Qi.Chen@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Zhangle.Yang@windriver.com
Subject: [PATCH 0/9] Make read-only rootfs work well with live images
Date: Fri, 26 Jul 2013 15:39:27 +0800 [thread overview]
Message-ID: <cover.1374642547.git.Qi.Chen@windriver.com> (raw)
From: Chen Qi <Qi.Chen@windriver.com>
Previously, if no unification filesystem mechanism is compiled into kernel
and we are booting a live image, it's very likely the image cannot run correctly.
Now if we have 'read-only-rootfs' in IMAGE_FEATURES, the live image could start
correctly even if there's no unionfs like feature compiled in kernel.
//Chen Qi
The following changes since commit dc198141f6d158250bc13ad1130eb57975043270:
initrdscripts: mount / as read-only when live-booting (2013-07-23 10:23:37 +0800)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib ChenQi/read-only-rootfs-in-live-images
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=ChenQi/read-only-rootfs-in-live-images
Chen Qi (9):
init-live.sh: make $ROOT_MOUNT/media writable when necessary
use a uniform way to determine whether rootfs is read-only
udev: remove implicit dependency on initscripts
populate-volatile.sh: use $ROOT_DIR/var/volatile/tmp as TMPDIR
runqemu-internal: fix to start X correctly in live images
initscripts: use a uniform way to handle directories in read-only
rootfs
irda-utils: make /etc/sysconfig writable in read-only rootfs
lighttpd: make /www diretory writable in read-only rootfs
Generate ssh keys at rootfs creation time in case of a read-only
rootfs
meta/classes/image.bbclass | 19 +++++++---
.../irda-utils/irda-utils_0.9.18.bb | 4 +++
meta/recipes-connectivity/openssh/openssh_6.2p2.bb | 10 ++++--
meta/recipes-core/dropbear/dropbear.inc | 6 +++-
meta/recipes-core/dropbear/dropbear/init | 19 ++--------
meta/recipes-core/initrdscripts/files/init-live.sh | 2 ++
.../initscripts/initscripts-1.0/functions | 14 ++++++++
.../initscripts-1.0/populate-volatile.sh | 6 +++-
.../initscripts-1.0/read-only-rootfs-hook.sh | 21 ++++++++---
meta/recipes-core/initscripts/initscripts_1.0.bb | 5 +++
meta/recipes-core/sysvinit/sysvinit/rcS-default | 4 ---
meta/recipes-core/udev/udev/init | 21 ++++++++---
meta/recipes-core/udev/udev/udev-cache | 5 +++
meta/recipes-extended/lighttpd/lighttpd_1.4.32.bb | 3 ++
.../0001-add-is_rootfs_readonly-to-functions.patch | 37 ++++++++++++++++++++
meta/recipes-extended/lsb/lsbinitscripts_9.48.bb | 1 +
scripts/runqemu-internal | 2 +-
17 files changed, 140 insertions(+), 39 deletions(-)
create mode 100644 meta/recipes-extended/lsb/lsbinitscripts/0001-add-is_rootfs_readonly-to-functions.patch
--
1.7.9.5
next reply other threads:[~2013-07-26 7:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 7:39 Qi.Chen [this message]
2013-07-26 7:39 ` [PATCH 1/9] init-live.sh: make $ROOT_MOUNT/media writable when necessary Qi.Chen
2013-07-26 7:39 ` [PATCH 2/9] use a uniform way to determine whether rootfs is read-only Qi.Chen
2013-07-26 7:39 ` [PATCH 3/9] udev: remove implicit dependency on initscripts Qi.Chen
2013-07-26 7:39 ` [PATCH 4/9] populate-volatile.sh: use $ROOT_DIR/var/volatile/tmp as TMPDIR Qi.Chen
2013-07-26 7:39 ` [PATCH 5/9] runqemu-internal: fix to start X correctly in live images Qi.Chen
2013-07-26 7:39 ` [PATCH 6/9] initscripts: use a uniform way to handle directories in read-only rootfs Qi.Chen
2013-07-26 7:39 ` [PATCH 7/9] irda-utils: make /etc/sysconfig writable " Qi.Chen
2013-07-26 7:39 ` [PATCH 8/9] lighttpd: make /www diretory " Qi.Chen
2013-07-26 7:39 ` [PATCH 9/9] Generate ssh keys at rootfs creation time in case of a " Qi.Chen
2013-07-26 9:28 ` Martin Jansa
2013-07-26 9:52 ` Phil Blundell
2013-07-26 11:08 ` Mike Looijmans
2013-07-26 11:22 ` Burton, Ross
2013-07-26 10:39 ` Enrico Scholz
2013-07-29 1:55 ` ChenQi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1374642547.git.Qi.Chen@windriver.com \
--to=qi.chen@windriver.com \
--cc=Zhangle.Yang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox