From: ChenQi <Qi.Chen@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH V8 2/6] image.bbclass: add a hook funtion to support readonly rootfs
Date: Wed, 23 Jan 2013 14:07:20 +0800 [thread overview]
Message-ID: <50FF7E18.4020803@windriver.com> (raw)
In-Reply-To: <50FED7A0.1060200@topic.nl>
On 01/23/2013 02:17 AM, Mike Looijmans wrote:
> On 01/22/2013 07:36 AM, 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.
>
> To me, it seems running populate-volatile at rootfs is a good thing
> for writable rootfs as well, it reduces the writing at first boot. Why
> not ALWAYS do this?
>
Hi Mike,
The reason I didn't make it *always* run at rootfs is that it's not
*necessary*.
Besides, I want to encapsulate all all necessary tweaks at rootfs time
into one function -- read-only-rootfs-hook.
In this way, I can ensure that it doesn't mess up with other components.
Thanks,
Chen Qi
next prev parent reply other threads:[~2013-01-23 6:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 6:36 [PATCH V8 0/6] read-only rootfs support Qi.Chen
2013-01-22 6:36 ` [PATCH V8 1/6] sysvinit: add ROOTFS_READ_ONLY variable to rcS-default Qi.Chen
2013-01-22 6:36 ` [PATCH V8 2/6] image.bbclass: add a hook funtion to support readonly rootfs Qi.Chen
2013-01-22 18:17 ` Mike Looijmans
2013-01-23 6:07 ` ChenQi [this message]
2013-01-22 6:36 ` [PATCH V8 3/6] core-image.bbclass: support read-only rootfs Qi.Chen
2013-01-22 6:36 ` [PATCH V8 4/6] initscripts: " Qi.Chen
2013-01-22 6:36 ` [PATCH V8 5/6] volatile-conf-minimal: add recipe Qi.Chen
2013-01-22 22:57 ` Saul Wold
2013-01-23 3:24 ` ChenQi
2013-01-23 4:20 ` Saul Wold
2013-01-23 4:52 ` ChenQi
2013-01-22 6:36 ` [PATCH V8 6/6] volatile-conf-sato: " 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=50FF7E18.4020803@windriver.com \
--to=qi.chen@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