The compile of VMware Tools did not produce the same errors as in the install scrip[t as Debian in Sparky however there still is something wrong with the vmblocking file system. When Sparky is booting vmblock throws some errors to fast for me to me to see and marks thke service [failed] But when I shutdown the system all the modules are marked [done]. I don't quite know how that works
I've only used the /usr/bin/vmware-toolbox-cmd timesync enable function in the past but this time I used the device shrink / which is supposed to wipe and then shrink the device (in this case I only had /.) Both these operation claimed they succeeded and very interestingly the shrink process appeared as a with a GUI progress bar which it used in the past when there was a GUI for all the tools. Silly me, since I actually expected the command to fail I neglected to do a before and after df.
Since I certainly am not privy to nuts and bolts of the tools development but I'm hopeful that a a full GUI will emerge when WS 10 is released this fall.
I just rebooted the Sparky system and there appeared other messages from the tools which went bi to fast to see. Subjectively the boot seemed faster.
As time permits I could go through more though terstinig of tools - including looking a dmesg logs but it seems a lot of work for marginal gain to me.