Comment 26 for bug 776103

Thanks in advance for putting up with the observations of a clueless outsider ;-)

* The transitional-package approach, which I think is what you used for open-vm-toolbox in ppa15, worked nicely.

* The conflicting-package approach, which I think is what you are using for open-vm-toolbox in ppa19, achieves the same result, although with benign errors that can be ignored. This is probably just due to the way I had to install (using dpkg rather than apt or Synaptic).

* The most important thing, that DKMS actually works, has been true since the earliest ppa's and continues. GOD BLESS YOU!!

* Anything I said about initialization scripts or mounting is completely inappropriate and beyond the scope of this bug report and its resolution. I just didn't know who else would be listening to me ;-)

* I couldn't agree more that it is confusing to read documentation about vmmemctl and vmware-user that even *I* suspect are just no longer true. But I think the point about DnD is still valid because I've played with it. In other words, the observations are uninformed by knowledge, but empirical. I still suspect something is rotten in Denmark because a force-reload of my modified open-vm-tools script frequently fails (mount: mount point /proc/fs/vmblock/mountPoint does not exist). Loading vmblock is *supposed* to create /proc/fs/vmblock (it does) and two nodes therein (dev and mountPoint). The former it always does; the latter, not always.