From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: Koen Kooi <koen@dominion.thruhere.net>,
Patches,
the oe-core layer <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2] udev: Move udevd back to /sbin
Date: Mon, 08 Apr 2013 22:17:18 +0100 [thread overview]
Message-ID: <1365455838.12407.58.camel@ted> (raw)
In-Reply-To: <CAP9ODKpRz1VtMewDO92D2XdbZS5DF+s8pURJt6x=SmX8trKhdQ@mail.gmail.com>
On Mon, 2013-04-08 at 17:40 -0300, Otavio Salvador wrote:
> On Mon, Apr 8, 2013 at 5:32 PM, Koen Kooi <koen@dominion.thruhere.net> wrote:
> >
> > Op 8 apr. 2013, om 18:29 heeft Radu Moisan <radu.moisan@intel.com> het volgende geschreven:
> >
> >> Along with v182 upgrade udevd was moved to ${base_libdir}
> >
> > By upstream, yes
> >
> >> making scripts like init-live.sh to fail in finding udevd
> >
> > So you should fix those scripts, not mess around with udev.
> >
> >> Fixes [Yocto #4046]
> >>
> >> Signed-off-by: Radu Moisan <radu.moisan@intel.com>
>
> This move has been done long time ago so I agree with Koen here: the
> scripts needs to be fixed. Another thing, it should also be tested
> with systemd feature enabled as udev will be called systemd-udevd in
> this case, IIRC.
It is not the scripts, see the previous discussion that was sent out and
Koen at least replied to. The scripts are the least of the problems.
Yes, the commit message here could be more accurate but that doesn't
change the problem of the issue reported in #4046 and previously
discussed.
Cheers,
Richard
next prev parent reply other threads:[~2013-04-08 21:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 16:29 [PATCH v2] udev: Move udevd back to /sbin Radu Moisan
2013-04-08 20:32 ` Koen Kooi
2013-04-08 20:40 ` Otavio Salvador
2013-04-08 21:17 ` Richard Purdie [this message]
2013-04-09 12:35 ` Richard Purdie
2013-04-09 14:36 ` Otavio Salvador
2013-04-09 14:41 ` Koen Kooi
2013-04-09 14:44 ` Koen Kooi
2013-04-09 15:07 ` Richard Purdie
2013-04-09 15:49 ` Mark Hatle
2013-04-09 16:31 ` Otavio Salvador
2013-04-09 16:28 ` Otavio Salvador
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=1365455838.12407.58.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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.