Quote:
|
I used the locate command after running updatedb. Here is some more info:[/b]
|
Please, I'm no expert with grep, but maybe someone with more linux knowlege than I can explain why that grep output confirms the packages are there? Could that simply be showing a link to non-existant packags?
EDIT: OK - understand now. But I don't think grep is enough. Its the rpm database you need be concerned about.
Here is what I get on my SuSE-9.3. Notice the difference when you compare your output to my output:
Quote:
oldcpu@linux:/lib> ls -al | grep libdl.; ls -al | grep libc.; ls -al | grep libpthread.; ls -al | grep librt
-rwxr-xr-x 1 root root 13814 2005-06-14 17:36 libdl.so.2
-rwxr-xr-x 1 root root 1383527 2005-06-14 17:36 libc.so.6
-rwxr-xr-x 1 root root 90392 2005-06-14 17:36 libpthread.so.0
-rwxr-xr-x 1 root root 41084 2005-06-14 17:36 librt.so.1[/b]
|
[Note - I deleted selected lines of packages that are not libdl, libc, libpthread, or librt] .... I'll check my SuSE-10.0 pc next.
Why not go to YaST > SOFTWARE > SOFTWARE MANAGEMENT, select "provides" as part of the filter (might be a slightlydifferent filter name on SuSE-10.1) and then check if "glibc" is installed?
Quote:
|
I'll check my SuSE-10.0 pc next.[/b]
|
OK, I got something a bit similar to what you got on my SuSE-10.0.
Quote:
oldcpu@linuxmini:/lib> ls -al | grep libdl.; ls -al | grep libc.; ls -al | grep libpthread.; ls -al | grep librt
-rwxr-xr-x 1 root root 13830 2005-09-09 19:36 libdl-2.3.5.so
lrwxrwxrwx 1 root root 14 2005-10-22 10:06 libdl.so.2 -> libdl-2.3.5.so
-rwxr-xr-x 1 root root 1405291 2005-09-09 19:36 libc-2.3.5.so
lrwxrwxrwx 1 root root 13 2005-10-22 10:06 libc.so.6 -> libc-2.3.5.so
-rwxr-xr-x 1 root root 90473 2005-09-09 19:36 libpthread-0.10.so
lrwxrwxrwx 1 root root 18 2005-10-22 10:06 libpthread.so.0 -> libpthread-0.10.so
-rwxr-xr-x 1 root root 45340 2005-09-09 19:36 librt-2.3.5.so
lrwxrwxrwx 1 root root 14 2005-10-22 10:06 librt.so.1 -> librt-2.3.5.so[/b]
|
Does an rpm package manager do a "grep" or does it look in an rpm database?
While grep may show the libraries are there, maybe the rpm database has a "different perspective". I still think it best to go to YaST > SOFTWARE > SOFTWARE MANAGEMENT, select "provides" as part of the filter (might be a slightlydifferent filter name on SuSE-10.1) and then check if "glibc" is installed.