From: Ming Liu <ming.liu@windriver.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH V2] initscripts: add urandom directory into volatiles
Date: Wed, 19 Dec 2012 09:44:48 +0800 [thread overview]
Message-ID: <50D11C10.5090204@windriver.com> (raw)
In-Reply-To: <50D0C461.7010901@linux.intel.com>
On 12/19/2012 03:30 AM, Saul Wold wrote:
> On 12/18/2012 03:23 AM, Burton, Ross wrote:
>> On 18 December 2012 06:23, Ming Liu <ming.liu@windriver.com> wrote:
>>> /etc/init.d/urandom fails to start/stop because it tries to save
>>> random-seed into /var/lib/urandom folder which does not exist in the
>>> file system.
>>>
>>> Fixed by adding /var/lib/urandom into volatiles.
>>
>> Doesn't this mean that the persistent state of urandom will be saved
>> to a ramdisk?
>>
>> Mixing up persistent and transient state in /var is exactly why /run
>> exists, and why we should switch to support /run as soon as
>> possible...
>>
> Sorry, this was my suggestion, It actually is creating
> /var/lib/urandom which should be a persistent sub-dir of /var
>
> I was bouncing back and for about it being in the the recipe's
> do_install vs populate volaties file, I did not see any other
> /var/lib/<dir> being created so I leaned toward this solution. This
> was on the list a week or so ago, we could go back to itbeing created
> in the do_install()
OK, so I will resend the patch creating it in do_install() as V3 since
it's a bit long time ago.
the best,
thank you
>
> Sau!
>
>
>> Ross
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>
>>
>
>
next prev parent reply other threads:[~2012-12-19 1:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-18 6:23 [PATCH V2] initscripts: add urandom directory into volatiles Ming Liu
2012-12-18 11:23 ` Burton, Ross
2012-12-18 19:30 ` Saul Wold
2012-12-19 1:44 ` Ming Liu [this message]
2012-12-19 2:20 ` ChenQi
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=50D11C10.5090204@windriver.com \
--to=ming.liu@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 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.