| Summary: | sys-apps/hwids: udev hwdb in wrong location | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Randolph Maaßen <gaireg+bgo> |
| Component: | [OLD] Core system | Assignee: | Gentoo systemd Team <systemd> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Randolph Maaßen
2015-08-28 00:35:26 UTC
What does this command output on your system? pkg-config --variable=udevdir udev Also, what does strace show when you run that udevadm hwdb command? I get the following.
# strace -e file udevadm hwdb -u
...
open("/lib/udev/hwdb.d/20-OUI.hwdb", O_RDONLY|O_CLOEXEC) = 3
open("/lib/udev/hwdb.d/20-acpi-vendor.hwdb", O_RDONLY|O_CLOEXEC) = 3
open("/lib/udev/hwdb.d/20-bluetooth-vendor-product.hwdb", O_RDONLY|O_CLOEXEC) = 3
open("/lib/udev/hwdb.d/20-net-ifname.hwdb", O_RDONLY|O_CLOEXEC) = 3
open("/lib/udev/hwdb.d/20-pci-classes.hwdb", O_RDONLY|O_CLOEXEC) = 3
open("/lib/udev/hwdb.d/20-pci-vendor-model.hwdb", O_RDONLY|O_CLOEXEC) = 3
open("/lib/udev/hwdb.d/20-sdio-classes.hwdb", O_RDONLY|O_CLOEXEC) = 3
open("/lib/udev/hwdb.d/20-sdio-vendor-model.hwdb", O_RDONLY|O_CLOEXEC) = 3
open("/lib/udev/hwdb.d/20-usb-classes.hwdb", O_RDONLY|O_CLOEXEC) = 3
open("/lib/udev/hwdb.d/20-usb-media-players.hwdb", O_RDONLY|O_CLOEXEC) = 3
open("/lib/udev/hwdb.d/20-usb-vendor-model.hwdb", O_RDONLY|O_CLOEXEC) = 3
open("/lib/udev/hwdb.d/60-evdev.hwdb", O_RDONLY|O_CLOEXEC) = 3
open("/lib/udev/hwdb.d/60-keyboard.hwdb", O_RDONLY|O_CLOEXEC) = 3
open("/lib/udev/hwdb.d/61-oldkeyboard.hwdb", O_RDONLY|O_CLOEXEC) = 3
open("/lib/udev/hwdb.d/69-libmtp.hwdb", O_RDONLY|O_CLOEXEC) = 3
open("/lib/udev/hwdb.d/70-mouse.hwdb", O_RDONLY|O_CLOEXEC) = 3
open("/lib/udev/hwdb.d/70-pointingstick.hwdb", O_RDONLY|O_CLOEXEC) = 3
So it certainly seems to be looking at /lib/udev/hwdb.d on my system.
pkg-config --variable=udevdir udev gives /lib/udev and strace is accessing the files. After a reboot without the symlink everything works. It looks like bug chasing at 4:00am is not a good idea. Sorry for the noise |