Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC][PATCH] Move udev cache creation after checkroot
Date: Sat, 23 Jan 2010 19:23:02 +0100	[thread overview]
Message-ID: <hjfeq5$8a3$1@ger.gmane.org> (raw)
In-Reply-To: <1264269339.3738.1.camel@gnutoo-desktop>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 23-01-10 18:55, gnutoo wrote:
> On Thu, 2010-01-14 at 16:08 +0100, Koen Kooi wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> It received 2 Acks, no NAKs, works well in the field: it's applied now
>>
>> On 12-01-10 14:54, Koen Kooi wrote:
>>> Hi,
>>>
>>> What's your opinion on attached (untested) patch? If there's some
>>> consensus that this is a step in the right direction I'll create a
>>> working & tested patch to commit.
>>>
>>> Nota bene: I'm not going to discuss the merits of udev caching, only the
>>> impact of this patch to the current situation.
>>>
>>> regards,
>>>
>>> Koen
> I tested it today(sorry for testing late)
> And boot still hang with udev + ro
> maybe it fixes a different issue then

This wasn't about hangs, this was about trying to write to a RO fs :)

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFLWz6GMkyGM64RGpERApVIAJ9GAr80qKR5ZlXfmOTK7byZEcxDiwCfYDi1
MIGa4OyxBXh5XZ9eXfLvNnQ=
=kIp/
-----END PGP SIGNATURE-----




      reply	other threads:[~2010-01-23 18:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-12 13:54 [RFC][PATCH] Move udev cache creation after checkroot Koen Kooi
2010-01-12 14:04 ` Graeme Gregory
2010-01-13  9:51 ` Koen Kooi
2010-01-13  9:58 ` Marcin Juszkiewicz
2010-01-14 15:08 ` Koen Kooi
2010-01-23 17:55   ` gnutoo
2010-01-23 18:23     ` Koen Kooi [this message]

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='hjfeq5$8a3$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --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