Hazel Russman wrote:
I've done a few further experiments on this, including building and testing a LFS-7.7-systemd with a skeleton X desktop. There are really two different problems:1) The spurious error messages at boot. These are associated with the rule SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", IMPORT{builtin}="usb_id", IMPORT{builtin}="hwdb --subsystem=usb" and can be prevented in systemd-udev-216 by bypassing this rule except for add events. In systemd-udev-217 they no longer occur at all. However in [e]udev-217 they do, and cannot be prevented by changing the rule. 2) The "evdev bug". This occurs only in [e]udev-217 and not in either of the two systemd-udevs. It is associated with the rule SUBSYSTEM=="input", ENV{ID_INPUT}=="", IMPORT{builtin}="input_id" If this rule is bypassed, xf86-input-evdev no longer works. So it's a bug in eudev, probably in the usb_id builtin function, since this is called in both the problematic rules. Maybe this should be reported upstream?
See https://github.com/gentoo/eudev/issues/110 -- Bruce -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
