udev_base_dir (Modemmanager)

Thomas Schäfer tschaefer at t-online.de
Tue Mar 19 09:49:50 PDT 2013


Am 19.03.2013 15:47, schrieb Dan Williams:
> On Mon, 2013-03-18 at 23:14 +0100, Thomas Schäfer wrote:
>> Hello,
>>
>> it is little bit off topic. Today I spent 2 hours to get running qmi/mm again
>> after a distributionupdate. (opensuse 12.2 --> 12.3)
>>
>> The final reason was a change of the udev basedir from /lib/udev to
>> /usr/lib/udev.
>>
>> Does anybody know, if other distributors do the same?
>>
>> Could the default changed?
> That is probably it.  It changed between Fedora 17 and 18 too,
> now /lib/udev is a symlink to /usr/lib/udev.
>

On a fresh / new installed system it seems to be also a link.
  (at least at the "liveCD" it is)

By upgrade it is a nearly empty directory.


>> Or could it automatically recognized by some scripts?
> It might be able to be auto-recognized.  The reason it's not tied to
> $LIBDIR or something like  that is that multilib distributions (ie, ones
> with /usr/lib64) don't put udev into /usr/lib64/udev; it's still
> in /usr/lib/udev for some reason.  Ideally your distro would do the
> symlink thing too, but I guess not.
>
> In any case, can you think of any specific tests we could use?  Maybe we
> check for some well-known utilities like ata_id and cdrom_id and use
> that directory if those checks pass?
I don't know how much effort it is.
May be other testers and/or package-maintainer are more experienced to 
see such pitfalls earlier.
As long it is an easily to set option in ./configure it could be enough.
  May be some words in readme like:
"Find no devices? - Check udev-paths!" may help

Regards,
Thomas







More information about the libqmi-devel mailing list