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
> ###
Wow, thanks Keith. I will try that out later today and let you know how
I get on.
> Make sure you have a version of prelink that supports blacklists.
I'm fairly certain the one that comes with FC2 does because
/etc/prelink.conf has lines like
# Directories or files with `-b ' prefix will be blacklisted.
-b /lib/modules
-b /usr/lib/locale
-b /usr/X11R6/lib{,64}/X11/xfig
in it.
> Good idea.
Yep. I've suggested it in the support ticket I opened with VMware. Sadly
my support options have expired so I had to post the ticket under
"Entitlement: No Response Service Request". If I'm lucky they might
respond anyway, but I'm not entitled to a response. They do claim that
the ticket looked at by their engineers though.
Best, Darren
--
=====================================================================
D. D. Brierton darren@xxxxxxxxxxx www.dzr-web.com
Trying is the first step towards failure (Homer Simpson)
=====================================================================
