On Mon, 2004-06-14 at 18:47, Keith G. Robertson-Turner wrote:
> su -
> ### save this to plbl-vmware.sh
> ### then sh plbl-vmware.sh
> export vmpath=`which vmware | xargs dirname` &&\
> echo "#VMWare blacklist" >>/etc/prelink.conf &&\
> file $vmpath/vm{net*,ware*} |\
> grep ELF |\
> sed -e "s/:.*//g" |\
> sed -e "s/^/-b /g" >>/etc/prelink.conf && \
> find /lib/modules/`uname -r` -name vmmon.o |\
> sed -e "s/^/-b /g" >>/etc/prelink.conf &&\
> find /lib/modules/`uname -r` -name vmnet.o |\
> sed -e "s/^/-b /g" >>/etc/prelink.conf
> exit
> ###
So I was just looking at this in more detail, and looking over the files
in /usr/bin/vm*. Firstly, /lib/modules is already blacklisted in my
/etc/prelink.conf and so I guess the last four lines before exit are
unnecessary. But whilst some of the files /usr/bin/vm* are ELF binaries,
some of them are shell scripts. And looking at those shell scripts in
more details I can see that a couple of them, notably /usr/bin/vmware,
point to binaries in /usr/lib/vmware/bin. I think this may be too
complicated to second-guess. The output of rpm -ql VMwareWorkstation is
mind-boggling. I just hope VMware either fix the prelinking or release a
new RPM with the appropriate lines for /etc/prelink.conf.
Thanks again Keith.
Best, Darren
--
=====================================================================
D. D. Brierton darren@xxxxxxxxxxx www.dzr-web.com
Trying is the first step towards failure (Homer Simpson)
=====================================================================
