Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Mark Hatle <mark.hatle@windriver.com>,
	 "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] base-files: Add /run/lock as a standard directory
Date: Fri, 09 May 2014 08:31:31 -0700	[thread overview]
Message-ID: <536CF4D3.6020701@linux.intel.com> (raw)
In-Reply-To: <536CF0E6.9060800@windriver.com>

On 05/09/2014 08:14 AM, Mark Hatle wrote:
> On 5/9/14, 4:16 AM, Burton, Ross wrote:
>> On 9 May 2014 00:24, Mark Hatle <mark.hatle@windriver.com> wrote:
>>> The /run/lock directory was being dynamically created during package
>>> install,
>>> but should have been owned by the base-files package.
>>
>> Doesn't do_install generate the /var/run/lock -> /run/lock symlink, as
>> /run is always a tmpfs so has to be populated on boot?
>>
>
> The /var/run/lock -> /run/lock symlink is generated, but the /run/lock
> is never created by anything that I could find.
>
> /run is not always a tmpfs...  We've got configurations where it's
> persistent.
>
> With that said, the fix may be incorrect though if something is
> generally used to create this as a tmpfs, which package would normally
> create the directory and populate it?  the volatiles code?
>

Ross is almost correct here, there is a link generated from via the 
volatiles file in initscripts recipe, which will be created during 
package install time.

Sau!

> --Mark
>
>> Ross
>>
>


  reply	other threads:[~2014-05-09 15:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-08 23:24 [PATCH] base-files: Add /run/lock as a standard directory Mark Hatle
2014-05-09  9:16 ` Burton, Ross
2014-05-09 15:14   ` Mark Hatle
2014-05-09 15:31     ` Saul Wold [this message]
2014-05-09 15:50       ` Mark Hatle
2014-05-09 19:41     ` Colin Walters
2014-05-09 20:35       ` Mark Hatle
2014-05-09 20:50         ` Colin Walters

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=536CF4D3.6020701@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=mark.hatle@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox