From: ChenQi <Qi.Chen@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org, Zhenfeng.Zhao@windriver.com
Subject: Re: [PATCH 09/12] initscripts: inherit volatiles to support read-only rootfs
Date: Mon, 28 Jan 2013 10:11:03 +0800 [thread overview]
Message-ID: <5105DE37.2090309@windriver.com> (raw)
In-Reply-To: <1359123271.13917.1.camel@ted>
On 01/25/2013 10:14 PM, Richard Purdie wrote:
> On Fri, 2013-01-25 at 13:11 +0000, Burton, Ross wrote:
>> On 24 January 2013 08:16, <Qi.Chen@windriver.com> wrote:
>>> +VOLATILE_DIR = "/var/volatile/lib/urandom"
>>> +VOLATILE_LINK = "/var/lib/urandom"
>> A better solution would be to not attempt to save and restore a seed
>> value that is intended to persist across reboots when it's on a tmpfs.
>> Putting the urandom seed into tmpfs is just a waste of time.
> I have to wonder why we don't put a union mount tmpfs over /var/lib to
> be honest...
>
> or if we don't want to depend on unionfs, a tmpfs over /var/lib...
>
> Cheers,
>
> Richard
>
>
>
A union mount tmpfs over /var/lib (and maybe /etc) was the first
solution that came into my mind. Then I saw a bug related to unionfs
about getcwd() call, and I saw the unionfs was still disabled for live
images. So I thought "maybe I should not use unionfs".
A tmpfs over /var/lib.
Hmm... I thought about that too. The reason that I didn't use this
method was that I thought that some directories under /etc might also
need to be written to.
It turns out that this concern seems unnecessary.
Anyway, I'll try out the tmpfs-over-var-lib method and let you know the
result.
Thanks,
Chen Qi
next prev parent reply other threads:[~2013-01-28 2:26 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 [this message]
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
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=5105DE37.2090309@windriver.com \
--to=qi.chen@windriver.com \
--cc=Zhenfeng.Zhao@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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