The bug is simple: VBoxCreateUSBNode.sh gets installed into /usr/lib/udev/ but 10-virtualbox.rules uses /lib/udev/VBoxCreateUSBNode.sh instead, so /dev/vboxusb doesn't get created. I made a workaround by changing all the paths in 10-virtualbox.rules to /usr/lib/udev/VBoxCreateUSBNode.sh. Note that the virtualbox ebuild installs VBoxCreateUSBNode.sh into ${udevdir} but virtualbox-bin installs into "${D}"/lib/udev. So Whats the correct one? For the record i am using sys-fs/udev-195. Reproducible: Always
+*virtualbox-4.2.4-r1 (12 Nov 2012) +*virtualbox-4.2.2-r1 (12 Nov 2012) + + 12 Nov 2012; Lars Wendler <polynomial-c@gentoo.org> + files/10-virtualbox.rules, -virtualbox-4.2.2.ebuild, + +virtualbox-4.2.2-r1.ebuild, -virtualbox-4.2.4.ebuild, + +virtualbox-4.2.4-r1.ebuild: + Fixed udevdir in rules file. Thanks to Cesar Garcia who reported this in bug + #442742. + (In reply to comment #0) > Note that the virtualbox ebuild installs VBoxCreateUSBNode.sh into > ${udevdir} but virtualbox-bin installs into "${D}"/lib/udev. So Whats the > correct one? The file from virtualbox ebuild is installed dynamically depending on the udev version being in use. So virtualbox-bin needs a fix for this (see bug #430424).
With this change I now get the following error messages during boot with stable virtualbox-4.1.22 and udev-171-r9. udevd[1396]: failed to execute '/lib/udev/%UDEVDIR%/VBoxCreateUSBNode.sh' '%UDEVDIR%/VBoxCreateUSBNode.sh 189 130 00': No such file or directory
+*virtualbox-4.1.22-r1 (13 Dec 2012) + + 13 Dec 2012; Lars Wendler <polynomial-c@gentoo.org> + -virtualbox-4.1.22.ebuild, +virtualbox-4.1.22-r1.ebuild: + Revbump so stable users don't get a broken udev rules file (bug #447112). + Sorry for that mess.
