Hi Dominique,

Dominique Leuenberger wrote:
> Thank you very much. So it must be vmware-toolbox which shows something
> wrong. when first started up, it shows all the scripts as not being used

Yes, that is one of the bugs that were already fixed internally and will be out 
in the next update.

> /etc/vmware-tools/tools.conf (which, btw, is missing from the regular make
> install routine. And also on the packagers wiki it is now only mentioned in
> the file layout structure, but no information what should be in is mentioned.
> There used to be disable-tools-version=1 written there, no? Is this obsoleted
> by newer version?)

tools.conf is not necessary; no file, or an empty file, is good enough for 
Tools 
to work out of the box.

disable-tools-version=1 is not necessary anymore either; I made some changes to 
the code so that the option is "hardcoded" when compiling open-vm-tools, 
instead 
of relying on a config file to tell the code what to do.

-- 
- Marcelo

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
open-vm-tools-devel mailing list
open-vm-tools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/open-vm-tools-devel

Reply via email to