On Tue, Apr 27, 2010 at 11:29 AM, Gary Greene <ggreene at minervanetworks.com> wrote: >> -----Original Message----- >> From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On >> Behalf Of Brian Mathis >> Sent: Monday, April 26, 2010 7:06 PM >> To: CentOS mailing list >> Subject: Re: [CentOS] vmware-server-console not installed [...] >> >> You don't need to downgrade for the whole OS, you can just do it for >> VMware. See the procedure in the first comment in this bug >> http://bugs.centos.org/view.php?id=3884. I have done that and it >> works fine. Just remember that if you update vmware, the edits to >> vmware-hostd will be undone, so you need to redo them. > > I'm not "downgrading the whole OS" only GLibC, Timezone, and NSCD packages. Once I did that, the latest version of VMWare Server loads just fine. Seeing as glibc is one of the most used and most critical libraries in the system, downgrading to an older version of it most certainly has the effect of downgrading almost every package on the system. I'm not talking about whatever OS version (5.3, 5.4, etc...) you think you're running (that not a real thing anyway as packages all exist at different versions). If there's an update to glibc that's security related, by downgrading the system-wide version you're reintroducing the problem to all packages on the system. This is why it's better to isolate the downgraded library to just VMware until it gets fixed to use the updated The version number of any package or OS is arbitrary -- you need to understand the effect of what you're doing beyond the version number.