Re: prelink breaks VMware 4.5.2 on FC2?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 14 Jun 2004 13:52:44 -0400, Jakub Jelinek wrote:

> 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.

Oops, my bad.

/mode overkill off

> I don't have vmware myself, but would be very interested to know what's
> the problem between vmware and prelink.

Well I'm still on 4.5.1, and from reports I've heard (here and on the
forums) I think I'll just wait for 4.5.3. Although 4.5.1 WorksForMe®
great.

> 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

WRT prelink on FC1, I haven't had a single issue for a long time. There
was some KDE stuff that got BØrked (kdepim, k3b, etc), but the next round
of updates fixed all that.

It's a point of contention when bending to accommodate proprietary
software like VMWare, especially when it's BØrked like v4.5.2. I think
for users of that version, prelink is the least of their problems.

IOW ... +WONTFIX +UPSTREAM should be the order of the day.

Although I can understand your frustration.

-
K.



[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux