{"action":"created","issue":{"url":"https://api.github.com/repos/jcnelson/vdev/issues/47","labels_url":"https://api.github.com/repos/jcnelson/vdev/issues/47/labels{/name}","comments_url":"https://api.github.com/repos/jcnelson/vdev/issues/47/comments","events_url":"https://api.github.com/repos/jcnelson/vdev/issues/47/events","html_url":"https://github.com/jcnelson/vdev/issues/47","id":102363010,"number":47,"title":"How to test on Gentoo?","user":{"login":"onimatrix81","id":9300278,"avatar_url":"https://avatars.githubusercontent.com/u/9300278?v=3","gravatar_id":"","url":"https://api.github.com/users/onimatrix81","html_url":"https://github.com/onimatrix81","followers_url":"https://api.github.com/users/onimatrix81/followers","following_url":"https://api.github.com/users/onimatrix81/following{/other_user}","gists_url":"https://api.github.com/users/onimatrix81/gists{/gist_id}","starred_url":"https://api.github.com/users/onimatrix81/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/onimatrix81/subscriptions","organizations_url":"https://api.github.com/users/onimatrix81/orgs","repos_url":"https://api.github.com/users/onimatrix81/repos","events_url":"https://api.github.com/users/onimatrix81/events{/privacy}","received_events_url":"https://api.github.com/users/onimatrix81/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":9,"created_at":"2015-08-21T11:59:35Z","updated_at":"2015-08-23T23:07:26Z","closed_at":null,"body":"Is there anybody who has got vdevd working on their gentoo systems? At the moment I have got vdevd, hwdb and udevlib-compat compiled fine and now I'm painfully slowly going to test not starting udev in sysinit and putting vdevd there.\r\nI don't use an initrd myself and I was wondering if I could just switch from udev to vdev on the fly and if it is so, how to do that? /etc/init.d/udev stop (stop udev) followed by make -C libudev-compat install (replace the libudev sos in /lib64) and vdevd -c /etc/vdev/vdevd.conf /dev  (start vdev) doesn't quite work, but I won't elaborate on the problems if I'm going all wrong about this."},"comment":{"url":"https://api.github.com/repos/jcnelson/vdev/issues/comments/133955013","html_url":"https://github.com/jcnelson/vdev/issues/47#issuecomment-133955013","issue_url":"https://api.github.com/repos/jcnelson/vdev/issues/47","id":133955013,"user":{"login":"jcnelson","id":459947,"avatar_url":"https://avatars.githubusercontent.com/u/459947?v=3","gravatar_id":"","url":"https://api.github.com/users/jcnelson","html_url":"https://github.com/jcnelson","followers_url":"https://api.github.com/users/jcnelson/followers","following_url":"https://api.github.com/users/jcnelson/following{/other_user}","gists_url":"https://api.github.com/users/jcnelson/gists{/gist_id}","starred_url":"https://api.github.com/users/jcnelson/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jcnelson/subscriptions","organizations_url":"https://api.github.com/users/jcnelson/orgs","repos_url":"https://api.github.com/users/jcnelson/repos","events_url":"https://api.github.com/users/jcnelson/events{/privacy}","received_events_url":"https://api.github.com/users/jcnelson/received_events","type":"User","site_admin":false},"created_at":"2015-08-23T23:07:26Z","updated_at":"2015-08-23T23:07:26Z","body":"@onimatrix81 Wow, your tests are quite extensive!  Thank you so much for your diligence!\r\n\r\n> Wife's digital camera on the other hand did not, but that's another story :).\r\n\r\nDoes your wife's digital camera usually show up as a removable USB disk, or as an MTP device?  I haven't added support for the latter yet, but it's a known issue (#36).\r\n\r\n> Yeah, I probably should've also included the info that i use evdev with xorg.\r\n\r\nIt shouldn't make a difference--it looks like your Xorg is set up to communicate with udev, as per the lines:\r\n\r\n```\r\n[ 55251.807] (II) The server relies on udev to provide the list of input devices.\r\n      If no devices become available, reconfigure udev or disable AutoAddDevices.\r\n```\r\n\r\n> Thought maybe it was the dbus acting up, so I tried again killing xorg, logging out, killing vdevd, stopping dbus, starting vdevd, starting dbus, starting xorg as normal user, but the results are still the same.\r\n\r\nDbus shouldn't be on the critical path for propagating input device events, but you never know, given how many services route messages through it these days...\r\n\r\n> Most of the /run/udev/links/ is missing =).\r\n\r\nThat *is* concerning.  Thank you for providing the /run/udev listings for both udev and vdev.\r\n\r\nThe code that generates everything in /dev/metadata/udev (which is symlinked to /run/udev) is in `vdevd/helpers/LINUX/udev-compat.sh`.  In particular, it generates the symlinks for device `$FOO` by parsing `/dev/metadata/dev/$FOO/links`, which contains the list of all other symlinks the other helper scripts have created thus far (i.e. the file is maintained by the `vdev_symlink` function in `vdevd/helpers/LINUX/subr.sh`).\r\n\r\nOne of three things can be happening here:  the helpers could be failing to create their symlinks (which can be confirmed by inspecting /dev for missing links), the links file is somehow being destroyed or corrupted, or `udev-compat.sh` is exiting before it processes the symlinks.\r\n\r\nThe third case is easy to verify:  if you remove the `async=true` line from `/etc/vdev/actions/zzz-udev-compat.act`, the `udev-compat.sh` script will run synchronously with vdevd, causing vdevd to capture all of its output.  Hopefully that will produce some useful error messages.  I'm currently working on a patch that will make this step unnecessary--vdevd should capture all error messages regardless of whether or not the helper runs asynchronously."}}