> This is nothing new. From day one open-vm-tools has not been supported
> by VMware. What this means is that open-vm-tools doesn't go through
> VMware's normal QA and release cycle, and thus if you call up to VMware
> support with a problem with open-vm-tools, they won't help you.
>
> Howeve
>>> On 5/10/2010 at 15:43, Sean Dilda wrote:
> This is nothing new. From day one open-vm-tools has not been supported
> by VMware. What this means is that open-vm-tools doesn't go through
> VMware's normal QA and release cycle, and thus if you call up to VMware
> support with a problem with
This is nothing new. From day one open-vm-tools has not been supported
by VMware. What this means is that open-vm-tools doesn't go through
VMware's normal QA and release cycle, and thus if you call up to VMware
support with a problem with open-vm-tools, they won't help you.
However, VMware i
On Fri, May 7, 2010 at 4:27 AM, Dominique Leuenberger wrote:
> As this message is in a public tracker I do not see any reason why I should
> not be allowed to forward this message from vmware directly (original
> reference: https://bugzilla.novell.com/show_bug.cgi?id=591085 )
>
On 5/6/2010 at
Hi everybody,
As this message is in a public tracker I do not see any reason why I should not
be allowed to forward this message from vmware directly (original
reference: https://bugzilla.novell.com/show_bug.cgi?id=591085 )
>>> On 5/6/2010 at 20:34, wrote:
> --- Comment #4 from John Savanyo 2
