Openembedded Core Discussions
 help / color / mirror / Atom feed
From: ChenQi <Qi.Chen@windriver.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH V5 00/10] Make read-only rootfs work with live images
Date: Mon, 19 Aug 2013 10:15:50 +0800	[thread overview]
Message-ID: <52117FD6.20002@windriver.com> (raw)
In-Reply-To: <520E64A8.2000206@linux.intel.com>

On 08/17/2013 01:43 AM, Saul Wold wrote:
> On 08/07/2013 11:15 PM, Qi.Chen@windriver.com wrote:
>> From: Chen Qi <Qi.Chen@windriver.com>
>>
>> Changes from V4:
>> 1. Fix the error of 'read -f' in populate-volatile.sh. The '-f' 
>> should should not be there.
>> 2. Fix the error of missing colon in populate-volatile.sh.
>>
>> Changes from V3:
>> 1. Take hidden directories and files into consideration when copying 
>> before bind mounting.
>> 2. Use 'cp -a' in populate-volatile.sh to avoid potential problems
>>
>> Change from V2:
>> 1. modify the irda init script so that it doesn't necessarily need to 
>> write to /etc/sysconfig/irda
>> 2. drop the lighttpd patch
>> 3. modify the logic for openssh in case of a read-only rootfs
>>
>> Change from V1:
>> 1. Disable the generating of ssh keys at rootfs time
>> 2. Add a mechanism to read-only-rootfs-hook.sh to check whether a 
>> directory is on a read-only partition.
>> 3. Fix a new bug#4937 
>> (https://bugzilla.yoctoproject.org/show_bug.cgi?id=4937)
>>
>> The following changes since commit 
>> f63e7f4323368c0d6fe7a1d44393a7e15652d4f2:
>>
>>    subversion: Add patch to use neon 0.30 (2013-08-07 07:43:47 +0100)
>>
>> are available in the git repository at:
>>
>>    git://git.pokylinux.org/poky-contrib 
>> ChenQi/read-only-rootfs-in-live-images
>> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=ChenQi/read-only-rootfs-in-live-images
>>
>> Chen Qi (10):
>>    init-live.sh: make $ROOT_MOUNT/media writable when necessary
>>    use a uiform way to determine whether rootfs is read-only
>
> Qi,
>
> Richard noted in the Consolidated Pull that he did not take this patch 
> along with the initscripts patch due to too many processes being 
> spawned at boot time, can you find a better way to handle this?
>
> Sau!
>
Yes.

I'll try to come up with a better solution.

Best Regards,
Chen Qi

>>    udev: remove implicit dependency on initscripts
>>    populate-volatile.sh: use $ROOT_DIR/var/volatile/tmp as TMPDIR
>>    populate-volatile.sh: don't spawn background process at rootfs time
>>    runqemu-internal: fix to start X correctly in live images
>>    initscripts: use a uniform way to handle directories in read-only
>>      rootfs
>>    populate-volatile.sh: use 'cp -a' to avoid potential problem
>>    irda-utils: fix for read-only rootfs
>>    openssh: fix for read-only rootfs
>>
>>   meta/classes/image.bbclass                         |   16 +++++--
>>   .../irda-utils/irda-utils-0.9.18/init              |   13 +-----
>>   .../openssh/openssh-6.2p2/init                     |   22 ++++++---
>>   meta/recipes-connectivity/openssh/openssh_6.2p2.bb |    9 +++-
>>   meta/recipes-core/initrdscripts/files/init-live.sh |    2 +
>>   .../initscripts/initscripts-1.0/functions          |   14 ++++++
>>   .../initscripts-1.0/populate-volatile.sh           |   15 ++++--
>>   .../initscripts-1.0/read-only-rootfs-hook.sh       |   48 
>> ++++++++++++++++++--
>>   meta/recipes-core/initscripts/initscripts_1.0.bb   |    5 ++
>>   meta/recipes-core/sysvinit/sysvinit/rcS-default    |    4 --
>>   meta/recipes-core/udev/udev/init                   |   21 +++++++--
>>   meta/recipes-core/udev/udev/udev-cache             |    5 ++
>>   .../0001-add-is_rootfs_readonly-to-functions.patch |   37 
>> +++++++++++++++
>>   meta/recipes-extended/lsb/lsbinitscripts_9.48.bb   |    1 +
>>   scripts/runqemu-internal                           |    2 +-
>>   15 files changed, 172 insertions(+), 42 deletions(-)
>>   create mode 100644 
>> meta/recipes-extended/lsb/lsbinitscripts/0001-add-is_rootfs_readonly-to-functions.patch
>>
>
>



      reply	other threads:[~2013-08-19  2:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-08  6:15 [PATCH V5 00/10] Make read-only rootfs work with live images Qi.Chen
2013-08-08  6:15 ` [PATCH V5 01/10] init-live.sh: make $ROOT_MOUNT/media writable when necessary Qi.Chen
2013-08-08  6:15 ` [PATCH V5 02/10] use a uniform way to determine whether rootfs is read-only Qi.Chen
2013-08-08  6:16 ` [PATCH V5 03/10] udev: remove implicit dependency on initscripts Qi.Chen
2013-08-08  6:16 ` [PATCH V5 04/10] populate-volatile.sh: use $ROOT_DIR/var/volatile/tmp as TMPDIR Qi.Chen
2013-08-09 21:34   ` Saul Wold
2013-08-08  6:16 ` [PATCH V5 05/10] populate-volatile.sh: don't spawn background process at rootfs time Qi.Chen
2013-08-08  6:16 ` [PATCH V5 06/10] runqemu-internal: fix to start X correctly in live images Qi.Chen
2013-08-08  6:16 ` [PATCH V5 07/10] initscripts: use a uniform way to handle directories in read-only rootfs Qi.Chen
2013-08-08  6:16 ` [PATCH V5 08/10] populate-volatile.sh: use 'cp -a' to avoid potential problem Qi.Chen
2013-08-08  6:16 ` [PATCH V5 09/10] irda-utils: fix for read-only rootfs Qi.Chen
2013-08-08  6:16 ` [PATCH V5 10/10] openssh: " Qi.Chen
2013-08-16 17:43 ` [PATCH V5 00/10] Make read-only rootfs work with live images Saul Wold
2013-08-19  2:15   ` ChenQi [this message]

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=52117FD6.20002@windriver.com \
    --to=qi.chen@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sgw@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox