From: Saul Wold <sgw@linux.intel.com>
To: Qi.Chen@windriver.com
Cc: Zhenfeng.Zhao@windriver.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/4] image.bbclass: add two hook funtions to support read-only rootfs
Date: Thu, 27 Dec 2012 10:22:15 -0800 [thread overview]
Message-ID: <50DC91D7.10306@linux.intel.com> (raw)
In-Reply-To: <819997e2cad5d6a4bf2621fb7cc443105ca0fc87.1356576405.git.Qi.Chen@windriver.com>
On 12/26/2012 06:57 PM, Qi.Chen@windriver.com wrote:
> From: Chen Qi <Qi.Chen@windriver.com>
>
> read_only_rootfs_hook: this funtion is invoked only if 'read-only-rootfs'
> is in IMAGE_FEATURES. It tweaks some basic files and makes populate-
> volatile.sh script run at rootfs time.
>
> choose_volatile_conf_file: this function properly chooses the right
> conf file for volatile storage handling according to the IMAGE_FEATURES.
>
> [YOCTO #3406]
>
> Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
> ---
> meta/classes/image.bbclass | 29 +++++++++++++++++++++++++++++
> 1 file changed, 29 insertions(+)
>
> diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
> index 8bf718a..15d42d0 100644
> --- a/meta/classes/image.bbclass
> +++ b/meta/classes/image.bbclass
> @@ -394,6 +394,35 @@ zap_root_password () {
> mv ${IMAGE_ROOTFS}/etc/passwd.new ${IMAGE_ROOTFS}/etc/passwd
> }
>
> +# A hook function to support read-only-rootfs IMAGE_FEATURES
> +read_only_rootfs_hook () {
> + # Tweak the mount option in fstab
> + sed '/rootfs/ s/defaults/ro/' < ${IMAGE_ROOTFS}/etc/fstab > ${IMAGE_ROOTFS}/etc/fstab.new
> + mv ${IMAGE_ROOTFS}/etc/fstab.new ${IMAGE_ROOTFS}/etc/fstab
> + # Change the value of ROOTFS_READ_ONLY in /etc/default/rcS to yes
> + sed 's/ROOTFS_READ_ONLY=no/ROOTFS_READ_ONLY=yes/' < ${IMAGE_ROOTFS}/etc/default/rcS > ${IMAGE_ROOTFS}/etc/default/rcS.new
> + mv ${IMAGE_ROOTFS}/etc/default/rcS.new ${IMAGE_ROOTFS}/etc/default/rcS
For the above 2 sed/mv, can't you use sed -i instead, cuts down on the
exec overhead.
Sau!
> + # Run populate-volatile.sh at rootfs time to set up basic files
> + # and directories to support read-only rootfs.
> + if [ ! -e ${IMAGE_ROOTFS}/etc/init.d/populate-volatile.sh ]; then
> + echo "${IMAGE_ROOTFS}/etc/init.d/populate-volatile.sh doesn't exist."
> + exit 1
> + else
> + ${IMAGE_ROOTFS}/etc/init.d/populate-volatile.sh
> + fi
> +}
> +
> +# Choose the correct config file for volatile storage handling according to the image type
> +choose_volatile_conf_file () {
> + if ${@base_contains("IMAGE_FEATURES", "x11-sato", "true", "false" ,d)}; then
> + cp ${IMAGE_ROOTFS}/etc/default/volatiles_stage/volatiles-readonly-sato \
> + ${IMAGE_ROOTFS}/etc/default/volatiles/00_core_readonly
> + else
> + cp ${IMAGE_ROOTFS}/etc/default/volatiles_stage/volatiles-readonly-minimal \
> + ${IMAGE_ROOTFS}/etc/default/volatiles/00_core_readonly
> + fi
> +}
> +
> # allow openssh accept login with empty password string
> openssh_allow_empty_password () {
> if [ -e ${IMAGE_ROOTFS}${sysconfdir}/ssh/sshd_config ]; then
>
next prev parent reply other threads:[~2012-12-27 18:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-27 2:57 [PATCH V3 0/4] read-only rootfs support Qi.Chen
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 [this message]
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=50DC91D7.10306@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.