All of lore.kernel.org
 help / color / mirror / Atom feed
From: ChenQi <Qi.Chen@windriver.com>
To: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
Cc: Zhenfeng.Zhao@windriver.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/4] image.bbclass: add a hook funtion to support readonly rootfs
Date: Wed, 20 Feb 2013 13:56:23 +0800	[thread overview]
Message-ID: <51246587.2040502@windriver.com> (raw)
In-Reply-To: <CAC1BbcQHHs+La4h=0GaHWWWsFzpe8EffJKHNyMdPWzNb+0znWw@mail.gmail.com>

On 02/19/2013 07:39 PM, Bernhard Reutner-Fischer wrote:
> On 19 February 2013 08:38,  <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.
>>
>> For now, it has real effect only if the init system is sysvinit.
>>
>> [YOCTO #3406]
>>
>> Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
>> ---
>>   meta/classes/image.bbclass |   18 ++++++++++++++++++
>>   1 file changed, 18 insertions(+)
>>
>> diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
>> index dd78acb..7d533b6 100644
>> --- a/meta/classes/image.bbclass
>> +++ b/meta/classes/image.bbclass
>> @@ -233,6 +233,24 @@ run_intercept_scriptlets () {
>>          fi
>>   }
>>
>> +# A hook function to support read-only-rootfs IMAGE_FEATURES
>> +# Currently, it only supports sysvinit system.
>> +read_only_rootfs_hook () {
>> +       if ${@base_contains("DISTRO_FEATURES", "sysvinit", "true", "false", d)}; then
>> +               # Tweak the mount option in fstab
>> +               sed -i '/rootfs/ s/defaults/ro/' ${IMAGE_ROOTFS}/etc/fstab
> to be cautious i would say
> sed -i -e '/^[#[:space:]]*rootfs/s/defaults/ro/' ${IMAGE_ROOTFS}/etc/fstab
> for ro rootfs fs_passno should be set to 0, too, imo:
> sed -i -e '/^[#[:space:]]*rootfs/{s/defaults/ro/;s/\([[:space:]]*[[:digit:]]\)\([[:space:]]*\)[[:digit:]]$/\1\20/}'
> ${IMAGE_ROOTFS}/etc/fstab

Thank you for your suggestion.

Version 2 has been sent out.

Best Regards,
Chen Qi

>> +               # Change the value of ROOTFS_READ_ONLY in /etc/default/rcS to yes
>> +               if [ -e ${IMAGE_ROOTFS}/etc/default/rcS ]; then
>> +                       sed -i 's/ROOTFS_READ_ONLY=no/ROOTFS_READ_ONLY=yes/' ${IMAGE_ROOTFS}/etc/default/rcS
>> +               fi
>> +               # 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
> -x if you want to execute it below.
>> +                       ${IMAGE_ROOTFS}/etc/init.d/populate-volatile.sh
>> +               fi
>> +       fi
>> +}
>> +
>>   fakeroot do_rootfs () {
>>          #set -x
>>          # When use the rpm incremental image generation, don't remove the rootfs
>




  reply	other threads:[~2013-02-20  6:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-19  7:38 [PATCH 0/4] Read-only rootfs followup patches Qi.Chen
2013-02-19  7:38 ` [PATCH 1/4] image.bbclass: add a hook funtion to support readonly rootfs Qi.Chen
2013-02-19 11:39   ` Bernhard Reutner-Fischer
2013-02-20  5:56     ` ChenQi [this message]
2013-02-19  7:38 ` [PATCH 2/4] core-image.bbclass: support read-only rootfs Qi.Chen
2013-02-19  7:38 ` [PATCH 3/4] populate-volatile.sh: add ROOT_DIR variable to support running at rootfs time Qi.Chen
2013-02-19 11:56   ` Bernhard Reutner-Fischer
2013-02-20  5:57     ` ChenQi
2013-02-19  7:38 ` [PATCH 4/4] populate-volatile.sh: improve the handling of link config items 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=51246587.2040502@windriver.com \
    --to=qi.chen@windriver.com \
    --cc=Zhenfeng.Zhao@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=rep.dot.nop@gmail.com \
    /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.