On Tue, Feb 11, 2003 at 08:59:45PM -0500, Matthew Schibler wrote:
My desktop system had a recent filesystem corruption problem. After
running fsck I discovered I am now missing a few binaries. For example
perl was missing, which I temporarily recovered by copying a working
binary from another debian system. This allowed me to run apt-get (some
portion of dpkg is perl based I think). I recovered a few things. Atleast
what I am aware of. I still have a problem though. I need to know what is
not complete, what files are missing or corrupted.
Is coreutils (specifically, the md5sum binary) good?
Is there some way I can check my installed packages against those
available and install what is missing/corrupted?
Is /var/lib/dpkg/info/ intact? Each installed package has its md5sums in
there. You can run (from /):
for PACKAGE in /var/lib/dpkg/info/*.md5sums;
do md5sum -c $PACKAGE;
done
This will output whenever a file cannot be opened (don't worry about not
having locales that you didn't generate) or when the md5sum didn't
match. One non-corruption cause of non-matching md5sums is diversions,
so you should watch for them. You can find out about diversions and
missing files with dpkg -S foo, where foo is the file that you are
looking for the owner of.
After determining which packages are missing files, just reinstall the
damaged packages (apt-get install --reinstall foo).
--
Seneca
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
