Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Ming Liu <ming.liu@windriver.com>
To: <openembedded-core@lists.openembedded.org>,
	Saul Wold <sgw@linux.intel.com>
Subject: Re: [PATCH V1] initscripts/urandom: create directory before staging into it
Date: Fri, 7 Dec 2012 13:33:16 +0800	[thread overview]
Message-ID: <50C17F9C.2090200@windriver.com> (raw)
In-Reply-To: <50C00182.3070102@windriver.com>

On 12/06/2012 10:22 AM, ChenQi wrote:
> On 12/06/2012 03:30 AM, Saul Wold wrote:
>> On 12/04/2012 11:57 PM, Ming Liu 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 creating /var/lib/urandom at do_install time.
>>>
>>> Signed-off-by: Ming Liu <ming.liu@windriver.com>
>>> ---
>>>   meta/recipes-core/initscripts/initscripts_1.0.bb | 4 +++-
>>>   1 file changed, 3 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/meta/recipes-core/initscripts/initscripts_1.0.bb 
>>> b/meta/recipes-core/initscripts/initscripts_1.0.bb
>>> index d25838b..39be9a8 100644
>>> --- a/meta/recipes-core/initscripts/initscripts_1.0.bb
>>> +++ b/meta/recipes-core/initscripts/initscripts_1.0.bb
>>> @@ -3,7 +3,7 @@ DESCRIPTION = "Initscripts provide the basic system 
>>> startup initialization scrip
>>>   SECTION = "base"
>>>   LICENSE = "GPLv2"
>>>   LIC_FILES_CHKSUM = 
>>> "file://COPYING;md5=751419260aa954499f7abaabaa882bbe"
>>> -PR = "r137"
>>> +PR = "r138"
>>>
>>>   INHIBIT_DEFAULT_DEPS = "1"
>>>
>>> @@ -133,4 +133,6 @@ do_install () {
>>>       fi
>>>
>>>       install -m 0755 ${WORKDIR}/device_table.txt 
>>> ${D}${sysconfdir}/device_table
>>> +    # Holds state information pertaining to urandom
>>> +    install -d ${D}/var/lib/urandom
>>
>> I thought this would go in volatiles, not here.
>>
>> Sau!
>>
> Hi Saul,
>
> From my understanding, volatiles is a configuration file which deals 
> with files related with volatile storage.
> Files, directories and links related to volatile storage should be in 
> this file, as it's a final method to check and make sure they are 
> created properly. But files under /var/lib should not there.

Hi, Saul:

Any comments? Should I send the V2 (put it into volatiles)?

the best,
thank you

>
> So in my option, this patch is ok.
>
> Thanks,
> Chen Qi
>
>>>   }
>>>
>>
>> _______________________________________________
>> 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
>
>




      reply	other threads:[~2012-12-07  5:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-05  7:57 [PATCH V1] initscripts/urandom: create directory before staging into it Ming Liu
2012-12-05 19:30 ` Saul Wold
2012-12-06  1:41   ` Ming Liu
2012-12-06  2:22   ` ChenQi
2012-12-07  5:33     ` Ming Liu [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=50C17F9C.2090200@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox