Re: Repairing a corrupted system

[Martin McCormick <martin@dc.cis.okstate.edu>]

Pigeon writes:
>It won't necessarily rebuild /lib/modules though. It won't if your
>kernel is not "built the Debian way", ie. if you've built it from a
>tarball and done make install and make modules_install, as dpkg won't
>know about it. If your kernel is "built the Debian way" but was=20
>installed by simply doing dpkg -i on the .deb rather than adding the=20
>=2Edeb to a repository, I think it still won't work because dpkg won't
>know where to find the .deb to reinstall from. I think you need to
>either reinstall the modules, or copy over your old /lib/modules (if
>it's really uncorrupted) and run depmod -a.

	That is what I had to do for the modules.  Fortunately, my
evil script stopped as soon as it shredded several files in /lib and
committed suicide more or less.  Judging from the modification times
in /modules/2.6.5, nothing there was touched or is it tourched;  I
just gingerly mv'd /lib/modules to another name and then un-tar'd my
old /lib/modules and the sound directory in
/lib/modules/2.6.5/kernel/sound was back home again and began to work
completely as before as nearly as I can tell.

	I did run the suggested commands to rebuild the libraries
based upon installed modules and had a somewhat surprising result.
Since it is somewhat of a different area of corruption, I will
continue this topic on the next message.

	Thanks to everyone for your help.

Martin McCormick WB5AGZ  Stillwater, OK 
OSU Information Technology Division Network Operations Group