On Mon, 14 Jun 2004 16:00:10 +0100, D. D. Brierton wrote:
> On Mon, 2004-06-14 at 15:04, Jonathan Rawle wrote:
>> prelink -ua
>>
>> to un-prelink everything.
>>
>> If vmware works now, you'll know what the problem was.
> vmware does indeed work now, so that confirms that it is prelink which is
> breaking vmware.
> Rather than moving vmware's binaries I would much rather blacklist them in
> /etc/prelink.conf. However, I don't know which of the kazillion files
> VMware Workstation installs need to be blacklisted, and on top of that
> vmware-config.pl generates some kernel modules and I'm not sure where it
> puts them
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
###
Make sure you have a version of prelink that supports blacklists. I've
been rolling my own for a while now, so I haven't been keeping up with the
changelogs in the main release. Maybe this is already done, but just in
case, here's a link to the development version:
http://tinyurl.com/2efsx/prelink-0.3.2-3.i386.rpm (redhat.com)
> Ideally applications which don't work with prelink should have a
> post-install script in their RPM which adds the relevant blacklist lines
> to /etc/prelink.conf.
Good idea.
-
K.
