VMWARE TOOLS necessary to install ?

[Vagabond]

Hi !
Thanks for this sexy-looking release !
I´m using it in VM-Ware Fusion and noticed, that VM-Ware-Tools seem not to
be installed. I tried to do it, gunzipped and untared the package, but the
vmware-install.py is giving me an error.

Is it necessary to install VMWARE-TOOLS ?

If so, how ?

Thank you very much !

[Array]

What system and VM package are you using? (i.e. Windows 7 with VMPlayer...)

[Gi0tis]

Since its Fusion, i m guessing he's on osx

[Array]

Since its Fusion, i m guessing he's on osx

Cheers for that... Im of no use then ;-) .... Don't know about OSX.
But... if installing VMware tools you may need to check out this link .... http://www.backtrack-linux.org/forum...ivers-etc.html

Array

[Gi0tis]

Cheers for that... Im of no use then ;-) .... Don't know about OSX.
But... if installing VMware tools you may need to check out this link .... http://www.backtrack-linux.org/forum...ivers-etc.html

Array

Indeed. Tried that myself while trying to install kde 64bit on fusion. Got a headache looking like this, after typing prepare-kernel-sources


Any idea whats going on?



Edit: To answer my own stupid (to put it gently) question, in the above pic i used prepare-kernel-sources before i installed BT. Which i shouldnt have:P

[socialcred]

Did you get the vmware tools to work in a fusion vm? Even after preparing the kernel sources I get errors on installation and the tools don't work.

Here are the error messages when I try to configure the tools, I prepend additional information showing that gcc and the kernel headers seem to be in their proper places:

[INDENT]Before you can compile modules, you need to have the following installed...

make
gcc
kernel headers of the running kernel


Searching for GCC...
Detected GCC binary at "/usr/bin/gcc".
The path "/usr/bin/gcc" appears to be a valid path to the gcc binary.
Would you like to change it? [no]

Searching for a valid kernel header path...
Detected the kernel headers of the running kernel at
"/lib/modules/2.6.38/build/include".
The path "/lib/modules/2.6.38/build/include" appears to be a valid path to the
kernel headers of the running kernel.
Would you like to change it? [no]




using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmhgfs-only'
make -C /lib/modules/2.6.38/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-source-2.6.38'

WARNING: Symbol version dump /usr/src/linux-source-2.6.38/Module.symvers
is missing; modules will have no dependencies and modversions.

CC [M] /tmp/vmware-root/modules/vmhgfs-only/backdoor.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/backdoorGcc32.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/bdhandler.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/cpName.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/cpNameLinux.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/cpNameLite.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/dentry.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/dir.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/file.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/filesystem.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/fsutil.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/hgfsBd.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/hgfsEscape.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/hgfsUtil.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/inode.o
/tmp/vmware-root/modules/vmhgfs-only/inode.c:159: warning: initialization from incompatible pointer type
/tmp/vmware-root/modules/vmhgfs-only/inode.c:173: warning: initialization from incompatible pointer type
/tmp/vmware-root/modules/vmhgfs-only/inode.c: In function ‘HgfsPermission’:
/tmp/vmware-root/modules/vmhgfs-only/inode.c:1867: warning: passing argument 1 of ‘atomic_read’ from incompatible pointer type
/usr/src/linux-source-2.6.38/arch/x86/include/asm/atomic.h:23: note: expected ‘const struct atomic_t *’ but argument is of type ‘unsigned int *’
CC [M] /tmp/vmware-root/modules/vmhgfs-only/kernelStubsLinux.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/link.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/message.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/messageBackdoor.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/module.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/page.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/request.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/rpcout.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/stubs.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/super.o
/tmp/vmware-root/modules/vmhgfs-only/super.c:73: error: unknown field ‘clear_inode’ specified in initializer
make[2]: *** [/tmp/vmware-root/modules/vmhgfs-only/super.o] Error 1
make[1]: *** [_module_/tmp/vmware-root/modules/vmhgfs-only] Error 2
make[1]: Leaving directory `/usr/src/linux-source-2.6.38'
make: *** [vmhgfs.ko] Error 2
make: Leaving directory `/tmp/vmware-root/modules/vmhgfs-only'

The filesystem driver (vmhgfs module) is used only for the shared folder
feature. The rest of the software provided by VMware Tools is designed to work
independently of this feature.

If you wish to have the shared folders feature, you can install the driver by
running vmware-config-tools.pl again after making sure that gcc, binutils, make
and the kernel sources for your running kernel are installed on your machine.
These packages are available on your distribution's installation CD.

+++++The rest of the tool modules fail in the same manner++++++++/INDENT]


*****UPDATE****
For the solution to the errors identified, see my post at:
http://www.backtrack-linux.org/forum...se-bt5-vm.html