From: <Qi.Chen@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Zhenfeng.Zhao@windriver.com
Subject: [PATCH V3 0/4] read-only rootfs support
Date: Thu, 27 Dec 2012 10:57:37 +0800 [thread overview]
Message-ID: <cover.1356576405.git.Qi.Chen@windriver.com> (raw)
From: Chen Qi <Qi.Chen@windriver.com>
The series of patches add support to read-only rootfs.
The main idea is to use symbolic links to create the illuion that some
directories are writable in case of a read-only rootfs.
This set of patches have been tested on minimal images with and without
'read-only-rootfs' image feature enabled. Everything is OK.
For sato images, everything is the same as before if 'read-only-rootfs' is not enabled.
With 'read-only-rootfs' enabled, sato image could work if graphic interface is diabled.
When all postinstall problems are resolved, sato image should work well (maybe with some
small changes in volatiles-readonly-sato conf file).
The following changes since commit 90c0eb29f0b41e4ac2d3d17ebad7295c2ebdc02a:
rootfs_rpm.bbclass: remove debug code (2012-12-19 21:43:55 +0000)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib ChenQi/readonly-rootfs
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=ChenQi/readonly-rootfs
Chen Qi (4):
sysvinit: add ROOTFS_READ_ONLY variable to rcS-default
image.bbclass: add two hook funtions to support read-only rootfs
core-image.bbclass: support read-only-rootfs image feature
initscripts: support read-only rootfs
meta/classes/core-image.bbclass | 7 +-
meta/classes/image.bbclass | 29 ++
.../initscripts/initscripts-1.0/bootmisc.sh | 9 +-
.../initscripts-1.0/populate-volatile.sh | 281 ++++++++++----------
.../initscripts/initscripts-1.0/volatiles | 1 +
.../initscripts-1.0/volatiles-readonly-minimal | 8 +
.../initscripts-1.0/volatiles-readonly-sato | 14 +
meta/recipes-core/initscripts/initscripts_1.0.bb | 11 +-
meta/recipes-core/sysvinit/sysvinit/rcS-default | 4 +
meta/recipes-core/sysvinit/sysvinit_2.88dsf.bb | 2 +-
10 files changed, 210 insertions(+), 156 deletions(-)
create mode 100644 meta/recipes-core/initscripts/initscripts-1.0/volatiles-readonly-minimal
create mode 100644 meta/recipes-core/initscripts/initscripts-1.0/volatiles-readonly-sato
--
1.7.9.5
next reply other threads:[~2012-12-27 3:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-27 2:57 Qi.Chen [this message]
2012-12-27 2:57 ` [PATCH 1/4] sysvinit: add ROOTFS_READ_ONLY variable to rcS-default Qi.Chen
2012-12-27 2:57 ` [PATCH 2/4] image.bbclass: add two hook funtions to support read-only rootfs Qi.Chen
2012-12-27 8:42 ` Martin Jansa
2012-12-27 8:51 ` ChenQi
2012-12-27 8:56 ` ChenQi
2012-12-27 18:22 ` Saul Wold
2012-12-28 2:16 ` ChenQi
2012-12-27 2:57 ` [PATCH 3/4] core-image.bbclass: support read-only-rootfs image feature Qi.Chen
2012-12-27 2:57 ` [PATCH 4/4] initscripts: support read-only rootfs Qi.Chen
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.1356576405.git.Qi.Chen@windriver.com \
--to=qi.chen@windriver.com \
--cc=Zhenfeng.Zhao@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