Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: [PATCH] udev 124: add cache invalidation logic on kernel change or its bootargs/cmdline
Date: Thu, 16 Apr 2009 15:04:39 +0200	[thread overview]
Message-ID: <gs7ad8$jre$1@ger.gmane.org> (raw)
In-Reply-To: <be7a9f3d0904160534s3f0c87fep88051546f0184af5@mail.gmail.com>

On 16-04-09 14:34, Otavio Salvador wrote:
> On Wed, Apr 15, 2009 at 9:06 PM, Denys Dmytriyenko<denis@denix.org>  wrote:
>> On Wed, Apr 15, 2009 at 08:54:04AM +0200, Holger Schurig wrote:
>>>> On 15-04-09 01:49, Denys Dmytriyenko wrote:
>>>>> +                 mv /tmp/uname /etc/uname
>>>>> +                 mv /tmp/cmdline /etc/cmdline
>>>>
>>>> I think we should put those in /etc/udev or /var/lib/udev if
>>>> udev will be the only consumer.
>>>
>>> +1, e.g.
>>>
>>> /etc/udev/saved.uname
>>> /etc/udev/saved.cmdline
>>
>> Good point, I'll be sending the update. Are there any other
>> comments/suggestions?
>
> It would be nice to, while on that, evaluate the possibility
> of updating udev; 0.141 fixes a serious security whole
> and even if most embedded systems usually runs as root,
> there're many that doesn't.

Also 141 will allow us to reduce the recipe to something like 'inherit 
autotools_stage' :)

regards,

Koen





  reply	other threads:[~2009-04-16 13:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-14 23:46 [RFC] Invalidating udev cache Denys Dmytriyenko
2009-04-14 23:49 ` [PATCH] udev 124: add cache invalidation logic on kernel change or its bootargs/cmdline Denys Dmytriyenko
2009-04-15  6:47   ` Koen Kooi
2009-04-15  6:54     ` Holger Schurig
2009-04-16  0:06       ` Denys Dmytriyenko
2009-04-16 12:34         ` Otavio Salvador
2009-04-16 13:04           ` Koen Kooi [this message]
2009-04-16 16:33   ` Tom Rini
2009-04-18  9:31     ` Koen Kooi
2009-04-18 17:56       ` Tom Rini
2009-04-18 18:56         ` Mike (mwester)

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='gs7ad8$jre$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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox