VMWare Beta 5: Problems installing VMWare Tools on Linux VM

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Probably Ryan will the the one to answer this but anybody can take a crack at it. The instructions for installing VMWare Tools on a Linux VM for VMWare versions 4 and 4.5 no longer seem to be valid.

Once I cd into the vmware-tools-distrib directory and execute the command ./vmware-install.pl, I'm asked a series of questions about where I want to install the various configurations files. Then I get to the end of the install and receive the following message:


Before running VMware Tools for the first time, you need to configure it by
invoking the following command: "/etc/vmware-config-tools.pl". Do you want this
program to invoke the command for you now? [yes] y

sh: line 1: /sbin/vmware-checkvm: Permission denied
sh: line 1: /sbin/vmware-checkvm: Permission denied
sh: line 1: /sbin/vmware-checkvm: Permission denied
This configuration program is to be executed in a virtual machine.

Execution aborted.

Previously, I received the "Execution aborted" command because /sbin/vmware-checkvm did not exist. I created a file by that name in the /sbin directory as root and now am getting the permission denied message.

I've checked both the instructions in the VMWare manual and online and can't find anything that helps me. What am I missing?

Oh...and I've also posted the same info on the VMWare Beta 5 Discussion Board.

 

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Problem was the tools had been installed in the root directory instead of /usr/bin. Once I moved the tools and ran them, it went like clock work.