Exactly. AFAICS, it is sufficient to modify the group/owner or permissions of all VirtualBox-installed files to run it, with the noted exception of /dev/vboxdrv.Sasquatch wrote:I think the TS can already use VB, else he won't post here with questions on how to get USB working.
BTW: The latters does not seem to react to my GROUP/MODE fiddlings in /etc/udev/rules.d/60-virtualbox.rules, so I resorted to a chmod in a boot-time script.
With USB now, I had additional problems because it does not seem to be enough to just give myself r/w permissions on the relevant /proc/bus/usb entries.
Oh, and BTW: Since I am member of multiple groups already, I could of course just chgrp everything to one of these groups. However, this would defeat the purpose of these groups, and as I tried to make clear above, my question is exactly which other files except the ones I described could need such treatment, since I already have permissions on all relevant files I know of. (AFAICS, it should not matter whether I have permissions because of being the right user, the right group - be it vboxusers or any other - or because the files simply have mode 666/777).