On Mon, Jun 14, 2004 at 06:47:37PM +0100, 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
Prelink certainly shouldn't be changing kernel modules, it works on binaries
and shared libraries.
I don't have vmware myself, but would be very interested to know what's
the problem between vmware and prelink.
It might do some kind of checksum of its executable, or append data at
the end of the executable, or whether it is due to some prelink bug
(but in that case it would be more likely to crash than exit with an error).
Jakub
