----
If you'll note the text above carefully, you'll note ldconfig is trying to
unlic directories. This is becuase the older libraries (and ldconfig) had
a different way of recording the "soname" (Which I have deduced is an
itnernal "name" of a library, irrelevant of what its filename is, that is
used for making the symlink). "version 1.7.3" is the older version, and he
is trying to isntall newer libraries.
I know what is causing this becuase I've had it happen myself. version
1.7.14 of ld.so (and ldconfig) properly recognize the new sonames (and
apparently the old ones as well).
It does however, appear that version 1.8.3 recognizes only the new names,
and goes on trying to unlink directories (unsuccessfuly) when it tries to
process the old libraries.
----
On 12 Nov 1996, I.R. wrote:
> Date: 12 Nov 1996 07:54:26 GMT
> From: "I.R." <s_redeke@ira.uka.de>
> To: submit-linux-dev-kernel@ratatosk.yggdrasil.com
> Newsgroups: linux.dev.kernel
> Subject: Re: Linux-2.0.25 and 2.1.8
>
> Joerg Pommnitz (joerg@raleigh.ibm.com) wrote:
> : According to Linus Torvalds:
> : > 2.1.8 also contains various other patches:
> : > - ide code cleanups
>
> : 2.1.8 panics for me at boot time. It detects my hda drive, but later
> : at the partition check it complains something like
> : hda: no device for 3:6
> : This is not the exact error message, but it's probably very close.
>
>
> I had exactly the same problem (about the same HW).
>
> So I have rebuilt the basic-kernel and later on got 2.0.25, which now
> produces a warning with the "ldconfig" in the boot-sequence, saying
> that "/usr/lib" cannot be unlinked. Attempts to do ldconfig manually
> cause this warning with some "libvgaXX.so" and the like.
>
> see yas
>
>
> I.R.
>
> --
> ....................................._______________________________________
> | Tea, Earl Grey, stirred not shaken.| Ingo Redeke ... s_redeke@ira.uka.de...|
> |<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<............uk3i@rz.uni-karlsruhe.de...|
>