Anyone know a source for such a beast? Is that planned?
Thanks!
You can install from the VI client. RT click Install upgrade vmware tools.
There are also OSP packages.
http://www.vmware.com/download/packages.html
You can install from the VI client. RT click Install upgrade vmware tools.
There are also OSP packages.
http://www.vmware.com/download/packages.html
There is rpm on standard .iso that automatically mounts on VMware Tools installation.
---
VMware vExpert '2009
You are probably looking for the OSP
Add repository and update with YUM
The iso only has a tar file...
The repo at packages.vmware.com is what I was looking for! Whats the diff between "open-vm-tools" and "vmware-tools"?
Thanks!
Looks like contents of this iso depends on OS type. I definitely saw .rpm here many times.
---
VMware vExpert '2009
Open tools don't contain VMware specific services like host communications. They only relate to the video, network, disk drivers. I would refer to the dos for specifics like setting up the repo getting gpg keys etc.
The tar and RPM files in the ISO may build code against the kernel sources. These are just the drivers ready to go for each supported kernel. If you build your own kernel you want to use the sources.
Hello,
Moved to VMware Tools OS-Specific Packaging
Best regards, Edward L. Haletky VMware Communities User Moderator, VMware vExpert 2009
Now Available on Rough-Cuts: 'VMware vSphere(TM) and Virtual Infrastructure Security: Securing ESX and the Virtual Environment'[/url]
Also available 'VMWare ESX Server in the Enterprise'[/url]
[url=http://www.astroarch.com/wiki/index.php/Blog_Roll]SearchVMware Pro[/url]|Blue Gears[/url]|Top Virtualization Security Links[/url]|Virtualization Security Round Table Podcast[/url]
Even though the gpg key is installed and imported, I get the follwoing error from yum?
Public key for vmware-tools-8.0.0-164009.165940.el5.i686.rpm is not installed
Seen that before?
Did you add a specific location in your repo file for the gpg key. Did you import it from the same location. Since you probably trust vmware you could use --nogpgcheck or disable it in the repo file.
Yeah, it was setup right, I just disabled it...
Thanks!