From: <Qi.Chen@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Zhenfeng.Zhao@windriver.com
Subject: [PATCH 00/12] read-only rootfs support
Date: Thu, 24 Jan 2013 16:16:40 +0800 [thread overview]
Message-ID: <cover.1359014474.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.
We use a similar stragety to update-rc.d.bbclass to manage all the recipes
that need to tweak some specific directories to support a read-only rootfs.
These recipes inherit volatiles.bbclass and set VOLATILE_DIR, VOLATILE_LINK
and VOLATILE_PKGS properly.
The advantage of this strategy is that it deligates the task of supporting
read-only rootfs to the recipes, resulting in a better management scheme.
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.
The following changes since commit 37e025f6f9c410005e0f1dee0767e38eaec01cbd:
bitbake: hob: Hob should display warnings generated during parsing (2013-01-21 19:05:31 +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 (12):
sysvinit: add ROOTFS_READ_ONLY variable to rcS-default
image.bbclass: add a hook funtion to support readonly rootfs
core-image.bbclass: support read-only rootfs
package.bbclass: add VOLATILE_DIR and VOLATILE_LINK to PACKAGEVARS
volatiles.bbclass: add recipe
volatiles_sysvinit.bbclass: add recipe
populate-volatile.sh: improve this script
initscripts: let populate-volatile.sh create the /tmp link
initscripts: inherit volatiles to support read-only rootfs
dropbear: inherit volatiles to support read-only rootfs
nfs-utils: inherit volatiles to support read-only rootfs
dbus: inherit volatiles to support read-only rootfs
meta/classes/core-image.bbclass | 4 +
meta/classes/image.bbclass | 18 ++
meta/classes/package.bbclass | 4 +-
meta/classes/volatiles.bbclass | 11 +
meta/classes/volatiles_sysvinit.bbclass | 49 ++++
.../nfs-utils/nfs-utils_1.2.3.bb | 7 +-
meta/recipes-core/dbus/dbus.inc | 7 +-
meta/recipes-core/dropbear/dropbear.inc | 7 +-
.../initscripts/initscripts-1.0/bootmisc.sh | 9 +-
.../initscripts-1.0/populate-volatile.sh | 287 ++++++++++----------
.../initscripts/initscripts-1.0/volatiles | 1 +
meta/recipes-core/initscripts/initscripts_1.0.bb | 6 +-
meta/recipes-core/sysvinit/sysvinit/rcS-default | 4 +
meta/recipes-core/sysvinit/sysvinit_2.88dsf.bb | 2 +-
14 files changed, 255 insertions(+), 161 deletions(-)
create mode 100644 meta/classes/volatiles.bbclass
create mode 100644 meta/classes/volatiles_sysvinit.bbclass
--
1.7.9.5
next reply other threads:[~2013-01-24 8:32 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 8:16 Qi.Chen [this message]
2013-01-24 8:16 ` [PATCH 01/12] sysvinit: add ROOTFS_READ_ONLY variable to rcS-default Qi.Chen
2013-01-24 8:16 ` [PATCH 02/12] image.bbclass: add a hook funtion to support readonly rootfs Qi.Chen
2013-01-24 19:44 ` Mark Hatle
2013-01-25 2:49 ` ChenQi
2013-01-24 8:16 ` [PATCH 03/12] core-image.bbclass: support read-only rootfs Qi.Chen
2013-01-24 8:16 ` [PATCH 04/12] package.bbclass: add VOLATILE_DIR and VOLATILE_LINK to PACKAGEVARS Qi.Chen
2013-01-24 8:16 ` [PATCH 05/12] volatiles.bbclass: add recipe Qi.Chen
2013-01-24 10:31 ` Martin Jansa
2013-01-24 11:37 ` Richard Purdie
2013-01-24 11:45 ` Burton, Ross
2013-01-25 8:58 ` ChenQi
2013-01-25 14:05 ` Burton, Ross
2013-01-28 3:32 ` ChenQi
2013-01-24 8:16 ` [PATCH 06/12] volatiles_sysvinit.bbclass: " Qi.Chen
2013-01-24 8:16 ` [PATCH 07/12] populate-volatile.sh: improve this script Qi.Chen
2013-01-24 8:16 ` [PATCH 08/12] initscripts: let populate-volatile.sh create the /tmp link Qi.Chen
2013-01-24 16:11 ` Mark Hatle
2013-01-24 17:39 ` Mark Hatle
2013-01-25 6:17 ` ChenQi
2013-01-24 8:16 ` [PATCH 09/12] initscripts: inherit volatiles to support read-only rootfs Qi.Chen
2013-01-25 13:11 ` Burton, Ross
2013-01-25 14:14 ` Richard Purdie
2013-01-28 2:11 ` ChenQi
2013-01-28 1:45 ` ChenQi
2013-01-24 8:16 ` [PATCH 10/12] dropbear: " Qi.Chen
2013-01-24 8:16 ` [PATCH 11/12] nfs-utils: " Qi.Chen
2013-01-24 8:16 ` [PATCH 12/12] dbus: " Qi.Chen
2013-01-24 10:45 ` Burton, Ross
2013-01-25 3:05 ` ChenQi
2013-01-25 13:02 ` Burton, Ross
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.1359014474.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