From: Tom Rini <tom_rini@mentor.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: udev 171 caching working propely?
Date: Tue, 21 Jun 2011 14:31:45 -0700 [thread overview]
Message-ID: <4E010DC1.1090600@mentor.com> (raw)
In-Reply-To: <4DFFCE1D.1070507@mentor.com>
On 06/20/2011 03:47 PM, Tom Rini wrote:
> On 06/20/2011 02:16 PM, Andreas Mueller wrote:
>> Dear OE-folks,
>>
>> Working with lastest classic oe master and angstrom it seems udev caching is not
>> working as expected. On *every* boot I get:
>>
>>> Remounting root file system...
>>> Caching udev devnodes
>>> Populating dev cachemv: can't rename '/dev/shm/uname': No such file or directory
>>
>> I don't know why this change came in but there was a change of storage location
>> in Tom's commit few days ago [1]. To me it seems that
>>
>> 1. The files created by udev (init) get lost at remount so udev-cache (cache) is
>> unable to find
>> 2. Since this error occures not only at first boot the recipe's
>> pkg_postinst_udev_append() seems never being executed. To check I added a simple
>> echo 'foo text'
>> in this function but 'foo text' is not found in log of first boot.
>>
>> Suggestions welcome
>
> Did udev change behaviors at some point then? I've been using an older
> udev and didn't run into that problem. I changed from /tmp to /dev/shm
> since we don't know that /tmp is writable at that point so we were
> instead getting errors there. I wonder if we should just switch to
> re-creating the contents for that step?
I've gone with this change and some quick testing on a board.
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2011-06-21 21:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 21:16 udev 171 caching working propely? Andreas Mueller
2011-06-20 22:47 ` Tom Rini
2011-06-21 21:31 ` Tom Rini [this message]
2011-06-23 20:58 ` Andreas Mueller
2011-06-23 21:58 ` Koen Kooi
2011-06-23 22:52 ` Andreas Mueller
2011-06-24 6:49 ` Koen Kooi
2011-06-24 14:49 ` Andreas Mueller
2011-06-24 15:43 ` Koen Kooi
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=4E010DC1.1090600@mentor.com \
--to=tom_rini@mentor.com \
--cc=openembedded-devel@lists.openembedded.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