From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: invalidating udev cache, how?
Date: Thu, 04 Dec 2008 18:41:50 +0100 [thread overview]
Message-ID: <gh94ov$rdk$1@ger.gmane.org> (raw)
In-Reply-To: <49380EAC.5020809@dls.net>
On 04-12-08 18:09, Mike (mwester) wrote:
> Mike (mwester) wrote:
>
>> A slight improvement would be to make the dev.tar file dependent upon
>> the bootargs; i.e. invalidate /etc/dev.tar file if the boot command line
>> doesn't match the current command line. This could be a very fast
>> operation, just "cmp /proc/cmdline /etc/dev_cmdline" or similar.
>
> As I consider this further, we could actually just save and compare
> /proc/atags if that's present on the device in question (falling back to
> /proc/cmdline if not present). That would catch *any* changes passed in
> to the kernel via the bootloader.
>
> Flashing a new kernel would seem to be another logical place to
> invalidate the cache, so adding a comparison of "uname -rv" would be a
> reasonable way to catch that.
That should indeed take care of bootargs and kernel version changes. I'm
still tempted to add option 2) to all that :)
regards,
Koen
next prev parent reply other threads:[~2008-12-04 17:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 16:05 invalidating udev cache, how? Koen Kooi
2008-12-04 16:15 ` Tom Rini
2008-12-04 17:35 ` Koen Kooi
2008-12-04 18:49 ` Tom Rini
2008-12-04 19:02 ` Koen Kooi
2008-12-04 19:17 ` Tom Rini
2008-12-04 16:35 ` Thomas Kunze
2008-12-04 17:03 ` Koen Kooi
2008-12-04 16:58 ` Mike (mwester)
2008-12-04 17:09 ` Mike (mwester)
2008-12-04 17:41 ` Koen Kooi [this message]
2008-12-04 18:50 ` Tom Rini
2009-03-03 5:11 ` Denys Dmytriyenko
2009-03-03 7:24 ` Koen Kooi
2009-03-03 15:16 ` Tom Rini
2008-12-04 17:11 ` 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='gh94ov$rdk$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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 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.