From: ChenQi <Qi.Chen@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Zhenfeng.Zhao@windriver.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 12/12] dbus: inherit volatiles to support read-only rootfs
Date: Fri, 25 Jan 2013 11:05:27 +0800 [thread overview]
Message-ID: <5101F677.4040108@windriver.com> (raw)
In-Reply-To: <CAJTo0LYpPTLBFczuC-QiPNm7W5u5nwQHf48SO5BKB5S+nHjHUA@mail.gmail.com>
On 01/24/2013 06:45 PM, Burton, Ross wrote:
> On 24 January 2013 08:16, <Qi.Chen@windriver.com> wrote:
>> From: Chen Qi <Qi.Chen@windriver.com>
>>
>> Inherit volatiles.bbclass to support read-only rootfs.
> Please explain why DBus needs volatiles.bbclass to support a readonly
> rootfs. Presumably it's because the machine UUID is written to
> /var/lib, are there any other reasons?
>
> Ross
>
>
I added this patch because I encountered an error when starting the sato
image.
That is, the machine UUID needs to be written to /var/lib.
I'm not familiar with dbus. Is it not necessary?
Thanks,
Chen Qi
next prev parent reply other threads:[~2013-01-25 3:20 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 8:16 [PATCH 00/12] read-only rootfs support Qi.Chen
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 [this message]
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=5101F677.4040108@windriver.com \
--to=qi.chen@windriver.com \
--cc=Zhenfeng.Zhao@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@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 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.