apt-get system reinstallation

sktsee sktsee at tulsaconnect.com
Thu Jul 10 17:09:54 BST 2008


On Thu, 2008-07-10 at 11:54 -0400, Bart Silverstrim wrote:
> NoOp wrote:
> > On 07/10/2008 05:51 AM, Bart Silverstrim wrote:
> > 
> >> Seems to be a good way to do the verification! I was running this on the 
> >> "firefox flash working" system to test (it has less software installed 
> >> so wouldn't take as long), running in one terminal and getting:
> >>>  sudo md5sum -c /var/lib/dpkg/info/*.md5sums > /home/bsilver/results.txt
> >>> [sudo] password for bsilver: 
> >>> md5sum: WARNING: 9 of 1938 computed checksums did NOT match
> >>> md5sum: WARNING: 9 of 1938 computed checksums did NOT match
> >>> md5sum: WARNING: 9 of 1938 computed checksums did NOT match
> >>> md5sum: WARNING: 9 of 1938 computed checksums did NOT match
> >> I was guessing they're config files of some kind, but running
> >>> cat results.txt |grep -i " OK "
> >> (yes, I know this isn't as elegant as it could be...) yielded *no* 
> >> results...so only the OK's are being redirected into results.txt?
> > 
> > Try:
> > 
> > cat /home/bsilver/results.txt | grep "FAILED"
> 
> Quoted below were the results, by the way...they weren't config files. I 
> thought it was interesting...? Wonder why these modules would have 
> failed, unless they're regenerated during the installation procedure to 
> compile on your particular system.
> 
> > lib/modules/2.6.24-16-generic/modules.pcimap: FAILED
> > lib/modules/2.6.24-16-generic/modules.dep: FAILED
> > lib/modules/2.6.24-16-generic/modules.ieee1394map: FAILED
> > lib/modules/2.6.24-16-generic/modules.usbmap: FAILED
> > lib/modules/2.6.24-16-generic/modules.isapnpmap: FAILED
> > lib/modules/2.6.24-16-generic/modules.inputmap: FAILED
> > lib/modules/2.6.24-16-generic/modules.seriomap: FAILED
> > lib/modules/2.6.24-16-generic/modules.alias: FAILED
> > lib/modules/2.6.24-16-generic/modules.symbols: FAILED
> > lib/modules/2.6.24-17-generic/modules.pcimap: FAILED
> > lib/modules/2.6.24-17-generic/modules.dep: FAILED
> > lib/modules/2.6.24-17-generic/modules.ieee1394map: FAILED
> > lib/modules/2.6.24-17-generic/modules.usbmap: FAILED
> > lib/modules/2.6.24-17-generic/modules.isapnpmap: FAILED
> > lib/modules/2.6.24-17-generic/modules.inputmap: FAILED
> > lib/modules/2.6.24-17-generic/modules.seriomap: FAILED
> > lib/modules/2.6.24-17-generic/modules.alias: FAILED
> > lib/modules/2.6.24-17-generic/modules.symbols: FAILED
> > lib/modules/2.6.24-18-generic/modules.pcimap: FAILED
> > lib/modules/2.6.24-18-generic/modules.dep: FAILED
> > lib/modules/2.6.24-18-generic/modules.ieee1394map: FAILED
> > lib/modules/2.6.24-18-generic/modules.usbmap: FAILED
> > lib/modules/2.6.24-18-generic/modules.isapnpmap: FAILED
> > lib/modules/2.6.24-18-generic/modules.inputmap: FAILED
> > lib/modules/2.6.24-18-generic/modules.seriomap: FAILED
> > lib/modules/2.6.24-18-generic/modules.alias: FAILED
> > lib/modules/2.6.24-18-generic/modules.symbols: FAILED
> > lib/modules/2.6.24-19-generic/modules.pcimap: FAILED
> > lib/modules/2.6.24-19-generic/modules.dep: FAILED
> > lib/modules/2.6.24-19-generic/modules.ieee1394map: FAILED
> > lib/modules/2.6.24-19-generic/modules.usbmap: FAILED
> > lib/modules/2.6.24-19-generic/modules.isapnpmap: FAILED
> > lib/modules/2.6.24-19-generic/modules.inputmap: FAILED
> > lib/modules/2.6.24-19-generic/modules.seriomap: FAILED
> > lib/modules/2.6.24-19-generic/modules.alias: FAILED
> > lib/modules/2.6.24-19-generic/modules.symbols: FAILED
> 
You may want to double-check your results by running your command
individually for that package. I noticed some flakiness when I ran
md5sum with the *.md5sum wildcard on the /var/lib/dpkg/info/ directory.
A few files had failed to match sums from various packages. Yet, when I
ran md5sum on an individual <packagename>.md5sum file, all the files
listed there checked out OK. Evidently, there's a bug lurking somewhere.

-- 
sktsee





More information about the ubuntu-users mailing list