Is it a better option *NOT* to include /etc/ld.so.conf into glibc main
package, and only create it inside %pre script *IF* it isn't a glibc
upgrade? In that way upgrading glibc will never damage ld.so.conf!
Abel Cheung
On Fri, 16 Mar 2001, Jose wrote:
> I've also have had the same problem when upgrading glibc. I found out after
> programs were unable to find libraries (in my mind, rebooting was not a option
> until i resolve the problem), I recreated the links manually. If I recall it did
> not make a backup of the existing ld.so.conf. It happened on both of my boxes (I
> was prepared for the second). This happened a few months ago when I had a 7.2 box
> and was upgrading glibc from the cooker ( i think glibc2.2.1-xxmdk) I also
> remember both times the glibc rpm complained about it needing ldconfig (did not
> mention newer version), even though it was allready installed (rpm -V ldconfig),
> on one box I installed the version of the 7.2 cdrom, on the other I downloaded the
> cooker ver. Didn't seem to make a difference though.
--
É£ã÷Îû, ʼØøħ...
ʼØøÉù, É£ÞóÄÑ...
É£ÄÑÎû, ʼÊÑħ...
ʼÊÑÉù, ɣĴÉï...
É£ÉïÉù, ʼèñħ...
ʼèñÆÊ, É£Þóè÷...
