I have just installed app-emulation/vmware-workstation but got stuck when following the instruction to run: /opt/vmware/bin/vmware-config.pl After a bit of investigation I found that it was unpacking files into /tmp then executing them. I have /tmp mounted as not executable for security reasons. If the ebuild could check this it could give a warning to anyone else who may be in the same situation.
I concur with this. Seeing how many users have /tmp as non-executable for security reasons, scripts should NOT assume to be able to execute code on /tmp.
This isn't just a gentoo thing, Ubuntu suffors from it as well. The security packagers obviously aren't talking to the rest.
This is still an issue. Please make script should work with a noexec mounted /tmp. I propose using /var/tmp/portage instead. make: execvp: ./getversion.pl: Permission denied make: Entering directory `/tmp/vmware-config2/vmmon-only' Using 2.6.x kernel build system. make -C /lib/modules/2.6.16-gentoo-r7/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/linux-2.6.16-gentoo-r7' make[2]: execvp: /tmp/vmware-config2/vmmon-only/./getversion.pl: Permission denied CC [M] /tmp/vmware-config2/vmmon-only/linux/driver.o /tmp/vmware-config2/vmmon-only/linux/driver.c:107: error: syntax error before ';' token make[2]: *** [/tmp/vmware-config2/vmmon-only/linux/driver.o] Error 1 make[1]: *** [_module_/tmp/vmware-config2/vmmon-only] Error 2 make[1]: Leaving directory `/usr/src/linux-2.6.16-gentoo-r7' make: *** [vmmon.ko] Error 2 make: Leaving directory `/tmp/vmware-config2/vmmon-only' Unable to build the vmmon module. For more information on how to troubleshoot module-related problems, please visit our Web site at "http://www.vmware.com/download/modules/modules.html" and "http://www.vmware.com/support/reference/linux/prebuilt_modules_linux.html". Execution aborted.
This should be fixed (as least partially) by the upcoming vmware-*-module ebuilds, which are being worked on at the moment. The idea is to strip the modules out into their own ebuild, so that they old get rebuilt when required. That will stop the various "copy to a temporary directory and rebuild" steps that are causing issues at the moment, however until the configure script is completely removed, there may still be other temporary configuration files that might get run in that location...
(In reply to comment #4) > This should be fixed (as least partially) by the upcoming vmware-*-module > ebuilds. Nice. Was thinking about solving it this way as well. :)
Well, now that the vmware-modules ebuilds as well as the vmware-* packages that require them are stable, is this still valid? Can it be closed?
Can't comment, I'm testing out arch linux at the moment.
Works fine here, thanks guys.
Thanks... marking FIXED.
