On 12/18/2012 03:23 AM, Burton, Ross wrote:
On 18 December 2012 06:23, Ming Liu <ming....@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()
Sau!
Ross
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
