Thomas Halahan wrote: > > Hello, > > Thanks for your promt reply. Much appreciated. I didn't quite > understand this: > > > I fixed this with a link to a libdb?.so in /lib via /lib/libdb.so.3, > > and after that, the upgrade to a new libdb worked. > > Do I just install libdb and manually link libdb2.so.3 back to the new > libc6.so. Is this right?
The perl script for dpkg --preconfigure (called by dselect) bombed because libdb.so.3 was missing, due to a less-than-perfectly- organized package, I'm sure. I could start up dselect, but couldn't do anything, IIRC. So I symlinked the missing lib to a lib of a similar name, and finished my upgrade, which included, IIRC, libdb2.so.3 . I had to do this linking _before_ I could install the new libdb, or anything, for that matter. I'm sure my method is cheating, and may be considered heretical and/or dangerous, but it worked. > > LISTING-- > > [EMAIL PROTECTED] tom]$ ls /lib/libdb* -l > -rw-r--r-- ... /lib/libdb-2.1.94.so > lrwxrwxrwx ... /lib/libdb.so.2 -> libdb1-2.1.94.so > lrwxrwxrwx ... /lib/libdb.so.3 -> libdb-2.1.94.so ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ I don't remember that specific "-2.1.94.", but this is in the nature of what I did. I see '-2.1.94.' on the Debian/sparc host, which is my desktop, FWIW. > -rw-r--r-- ... /lib/libdb1-2.1.94.so > lrwxrwxrwx ... /lib/libdb1.so.2 -> libdb1-2.1.94.so > > > Thomas Halahan wrote: > > > > > > Hi, > > > > > > I have upgraded glibc to 2.1.94-3. During this process I have had > > > the same problems as many. i.e. > > > > > > * libdb.so.3 not found... -- Bolan Timothy Lewis Meek Unix Systems Administrator Romac/Sarcom/MCI-WorldCom: 972-729-5387 [EMAIL PROTECTED] Flying M Ranch: [EMAIL PROTECTED]