D. D. Brierton wrote: > which never had any replies. Unfortunately, in my case running > vmware-config.pl doesn't help. However the only thing that happened to > my system between me using VMware last night and trying to use it this > morning was the running of the cron jobs. As I can't imaging that > updatedb or logrotate could have effected VMware I can only assume it > was prelink. > Edit /etc/sysconfig/prelink to say: PRELINKING=no then run prelink -ua to un-prelink everything. If vmware works now, you'll know what the problem was. A work-around is to stop prelink from prelinking the vmware binaries. I don't know where vmware stores its files, but they must be in a directory listed in /etc/prelink.conf. I suggest moving them to a different directory not listed in prelink.conf, then symlinking them from their old location. (prelink won't follow symlinks if the directory is prefixed with -l in prelink.conf, which they all seem to be by default). Is there a list of binaries to exclude from prelinking somewhere? I can't remember, but if there is that would be an easier way to do it. Jonathan
