--- Comment #15 from Denis Leroy <denis(a)poolshark.org> 2008-10-28 11:01:53 ---
Orcan, thanks for the help.
I made some simple changes to only include the vmci_socket header file
Btw, you didn't answer/address my previous question about
vmware-user-suid-wrapper permissions yet.
This is what is recommended by
and I know for a fact that drag'n'drop won't work without it. The other suid
used to launch the vmware-user desktop daemon. I can't really go into more
technical details without asking upstream, but the nfs mount tool for example
also has suid set. For vmware-user, possibly it could use PolicyKit but that
would require some heavy patching. I can file a bug upstream and ask them to
consider that approach instead of suid.
As far as the "on by default", I do think it makes a lot of sense considering
what open-vm-tools is. This package only makes sense for people using VMWare's
linux guest OSes, and for those you expect the package to indeed just work
For the development package, the installed header file is used to using VMCI
sockets, but using them requires the vsock kernel module (it's loaded by the
init script), so in a way, the development package also needs the init script
to be started...
Configure bugmail: http://bugzilla.rpmfusion.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.