asseb@asseb-nunux:~/VMT/vmware-tools-distrib$ sudo /usr/bin/vmware-config-tools.pl
Stopping VMware Tools services in the virtual machine:   
Guest operating system daemon:                                      done   
Guest filesystem driver:                                            done
Trying to find a suitable vmhgfs module for your running kernel. None of the pre-built vmhgfs modules for VMware Tools is suitable for yourrunning kernel.  Do you want this program to try to build the vmhgfs module foryour system (you need to have a C compiler installed on your system)?
[yes]
Using compiler "/usr/bin/gcc". Use environment variable CC to override. What is the location of the directory of C header files that match your runningkernel?
[/lib/modules/2.6.15-26-386/build/include]
Extracting the sources of the vmhgfs module. Building the vmhgfs module. Using 2.6.x kernel build system.make: entrant dans le répertoire « /tmp/vmware-config0/vmhgfs-only »make -C /lib/modules/2.6.15-26-386/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modulesmake[1]: entrant dans le répertoire « /usr/src/linux-headers-2.6.15-26-386 » 
CC [M]  /tmp/vmware-config0/vmhgfs-only/cpName.o 
CC [M]  /tmp/vmware-config0/vmhgfs-only/cpNameLinux.o 
CC [M]  /tmp/vmware-config0/vmhgfs-only/dev.o 
CC [M]  /tmp/vmware-config0/vmhgfs-only/driver.o 
CC [M]  /tmp/vmware-config0/vmhgfs-only/hgfsUtil.o 
CC [M]  /tmp/vmware-config0/vmhgfs-only/main.o 
CC [M]  /tmp/vmware-config0/vmhgfs-only/staticEscape.o 
LD [M]  /tmp/vmware-config0/vmhgfs-only/vmhgfs.o 
Building modules, stage 2.
MODPOST 
CC      /tmp/vmware-config0/vmhgfs-only/vmhgfs.mod.o 
LD [M]  /tmp/vmware-config0/vmhgfs-only/vmhgfs.ko
make[1]: quittant le répertoire « /usr/src/linux-headers-2.6.15-26-386 »
cp -f vmhgfs.ko ./../vmhgfs.o
make: quittant le répertoire « /tmp/vmware-config0/vmhgfs-only »
The module loads perfectly in the running kernel.

Extracting the sources of the vmxnet module.

Building the vmxnet module.

Using 2.6.x kernel build system.
make: entrant dans le répertoire « /tmp/vmware-config0/vmxnet-only »
make -C /lib/modules/2.6.15-26-386/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: entrant dans le répertoire « /usr/src/linux-headers-2.6.15-26-386 »  CC [M]  /tmp/vmware-config0/vmxnet-only/vmxnet.o  Building modules, stage 2. 
MODPOST 
CC      /tmp/vmware-config0/vmxnet-only/vmxnet.mod.o 
LD [M]  /tmp/vmware-config0/vmxnet-only/vmxnet.ko
make[1]: quittant le répertoire « /usr/src/linux-headers-2.6.15-26-386 »
cp -f vmxnet.ko ./../vmxnet.o
make: quittant le répertoire « /tmp/vmware-config0/vmxnet-only »
The module loads perfectly in the running kernel.

No X install found.

Starting VMware Tools services in the virtual machine:   
Switching to guest configuration:                                   done   
Guest filesystem driver:                                            done   
DMA setup:                                                          done   
Guest operating system daemon:                                      done
The configuration of VMware Tools 5.5.1 build-19175 for Linux for this running
kernel completed successfully.
You must restart your X session before any mouse or graphics changes take
effect. You can now run VMware Tools by invoking the following command:
"/usr/bin/vmware-toolbox" during an XFree86 session.

To use the vmxnet driver, restart networking using the following commands:
/etc/init.d/networking stop
rmmod pcnet32
rmmod vmxnet
depmod -a
modprobe vmxnet/etc/init.d/networking start

Enjoy, --the VMware team

c'est surtout le "No X Install found" qui m"intrigue

quelqu'un a une idee ?