Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mike Looijmans <mike.looijmans@topic.nl>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Busybox mdev INITSCRIPT_PARAMS gets lost
Date: Wed, 10 Apr 2013 12:58:20 +0200	[thread overview]
Message-ID: <516545CC.6010605@topic.nl> (raw)
In-Reply-To: <CAJTo0LZuX0-EeAXzBa=_LzOPw3=0h=Am0tU50-7wkmxYnJHsog@mail.gmail.com>

On 04/10/2013 12:24 PM, Burton, Ross wrote:
> Hi Mike,
>
> On 10 April 2013 11:07, Burton, Ross <ross.burton@intel.com> wrote:
>>> This used to work just fine about a month ago, but it's suddenly broken. Has
>>> something changed in update-rc handling?
>>
>> Did you resolve this?  We just noticed the same thing is happening to
>> udev too.  I'm digging into it now but any leads (or a fix!) would be
>> appreciated.

Never found the cause, both work and home situations kept me from 
investigating further.

> My patch "update-rc.d: correctly look up the initscript params with
> overrides" fixes this for udev, and presumably mdev too.

Looks like a good catch. I will still post a patch for mdev starting too 
late (it should start at 03 just like udev does) when I find the time to 
spend a little time on it (either at work or as a hobby...)

Mike.




  reply	other threads:[~2013-04-10 11:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130228231551.3998F5022B@opal>
2013-03-06  6:23 ` [oe-commits] MiLo : util-linux: Add package for libmount Martin Jansa
2013-03-06  8:08   ` Mike Looijmans
2013-03-19 14:45     ` Busybox mdev INITSCRIPT_PARAMS gets lost Mike Looijmans
2013-04-10 10:07       ` Burton, Ross
2013-04-10 10:24         ` Burton, Ross
2013-04-10 10:58           ` Mike Looijmans [this message]
2013-03-22 11:37     ` [oe-commits] MiLo : util-linux: Add package for libmount Martin Jansa

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=516545CC.6010605@topic.nl \
    --to=mike.looijmans@topic.nl \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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