Hi again,
David Baron wrote:
> (I do not want to unnecessarily try to boot up the errant Sid /lib because of
> possible file system damage.)
It occurs to me that you might have another partition with another
operating system, or a rescue CD. Is that the case? Would you be
able to look around at the broken system?
I would be interested to see:
- the content of /etc/ld.so.conf and the files in /etc/ld.so.conf.d/*
- what files and symlinks match the pattern "/lib/ld-*", and their
timestamps
- the content of /var/log/dpkg.log, /var/log/kern.log, and
/var/log/syslog
- a listing for /lib/i386-linux-gnu/ and /lib/i486-linux-gnu/.
in other words:
{
grep . $root/etc/ld.so.conf $root/etc/ld.so.conf.d/*
ls -ld $root/lib/ld-*
printf '\ndpkg.log:\n'
cat $root/var/log/dpkg.log
printf '\nkern.log:\n'
cat $root/var/log/kern.log
printf '\nsyslog:\n'
cat $root/var/log/syslog
ls -l /lib/i[34]86-linux-gnu/
} >logs.txt
Sorry for the trouble, and hope that helps.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
