From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [80.91.229.2] (helo=ciao.gmane.org) by linuxtogo.org with esmtp (Exim 4.69) (envelope-from ) id 1L8IJb-0008Mr-CP for openembedded-devel@openembedded.org; Thu, 04 Dec 2008 18:48:39 +0100 Received: from root by ciao.gmane.org with local (Exim 4.43) id 1L8IG7-0006RW-1R for openembedded-devel@openembedded.org; Thu, 04 Dec 2008 17:45:03 +0000 Received: from s55917625.adsl.wanadoo.nl ([85.145.118.37]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 04 Dec 2008 17:45:03 +0000 Received: from k.kooi by s55917625.adsl.wanadoo.nl with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 04 Dec 2008 17:45:03 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: openembedded-devel@openembedded.org From: Koen Kooi Date: Thu, 04 Dec 2008 18:41:50 +0100 Message-ID: References: <49380C4F.1050809@dls.net> <49380EAC.5020809@dls.net> Mime-Version: 1.0 X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: s55917625.adsl.wanadoo.nl User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b3pre) Gecko/20081130 Shredder/3.0b1pre In-Reply-To: <49380EAC.5020809@dls.net> Sender: news Subject: Re: invalidating udev cache, how? X-BeenThere: openembedded-devel@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: openembedded-devel@lists.openembedded.org List-Id: Using the OpenEmbedded metadata to build Distributions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Dec 2008 17:48:39 -0000 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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