On Sunday 20 December 2009, ken wrote: > On 12/18/2009 10:53 AM Peter Kjellstrom wrote: > > On Friday 18 December 2009, ken wrote: ... > >> To ensure that a file hasn't been corrupted or tampered with, you can > >> use rpm to verify the package it came from. Well, I found this: > >> > >> rpm -Vv util-linux > >> .... > >> ........ /usr/bin/cal > >> S.?..... /usr/bin/chfn ... > > S means size differs from rpmdb entry, ? means the md5sum test could not > > be done. I'm guessing interference from prelink. If you can, turn it > > off(*) and re-run the test. ... > Thanks, Peter! I don't understand why prelink would affect the rpm > database, I'm quite sure that the database only stores the original "un-prelinked" checksum and the it's up to the -V command to compensate if it finds a prelinked binary (which apparently doesn't always work...). > but turning prelink off and then back on cleared those flags. Great :-) /Peter > Yes, mine was an upgrade from 5.3.
Attachment:
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos
