All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Yocto Project <yocto@yoctoproject.org>
Subject: udev breakage
Date: Mon, 22 Apr 2013 17:09:33 -0600	[thread overview]
Message-ID: <5175C32D.8030304@mlbassoc.com> (raw)

I've found that Poky/Yocto images built after this commit have
a broken udev:

commit c71d1f446c734954dceba0666c4f074047864b87
Author: Richard Purdie <richard.purdie@linuxfoundation.org>
Date:   Wed Apr 17 14:53:21 2013 +0000

     udev: Effectively revert the move to /sbin

     This effectively reverts the changes made in b49ddeb11c0319b7ece278fd7cef6b0223114ca9
     to move udev's libexecdir to sbin. The changes caused too many issues in
     other places and were not well enough tested this close to a release.

     Rather than use base_libdir, the nonarch version is used to try and give some
     chance of multilib not being totally broken in the release.

     (From OE-Core rev: c50e50fdafad378d75b7b74259a3d55ca0fe3d18)

     Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

Prior to this commit, the X server finds my input devices and works
perfectly.  After this commit, something breaks and X can't find any
keyboard/mouse/touch.

It seems like the path '/sbin/udev' has crept in some way that the
recipe configuration does not affect.  After the failing commit, all
of the udev files should be in ${nonarch_base_libdir}, not /sbin.
However, that doesn't seem to be the case in libudev

root@sabrelite:~# strings /lib/libudev.so.0 | grep /udev
/etc/udev/udev.conf
/run/udev
/sbin/udev/rules.d
/etc/udev/rules.d

I believe that this is why X is failing since it uses libudev to
search for devices.

I've not found where/how this mixup is happening, perhaps someone more
familiar with the udev code can spot it quickly.

Thanks

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


             reply	other threads:[~2013-04-22 23:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-22 23:09 Gary Thomas [this message]
2013-04-23 10:34 ` udev breakage Gary Thomas
2013-04-23 17:31   ` Gary Thomas
2013-04-24 11:00     ` Gary Thomas

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=5175C32D.8030304@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=yocto@yoctoproject.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 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.