[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: SUG: Automatic RPM database verification and repair



I haven't seen this come through.

At 3:19 PM +0800 11/27/06, Nerazzurri wrote:
>>
>> None of the above should be considered criticism, just history.
>>
>> There are two needs if one wants to protect against rpmdb data loss.
>>
>> The most important is saving a copy of /var/lib/rpm/Packages routinely.
>> All other information in an rpmdb can be regenerated from a reasonably
>> recent copy of Packages. And in most cases a depsolver like
>> yum/smart/apt/poldek
>> will reinstall the packages that have changed since the last copy of
>> Packages
>> was saved.
>>
>
>but how can i know which version of "/var/lib/rpm/Packages" is correct
>and work well, if i backup a corrupted "Packages", the backup work will
>be senseless, isnt it?  :-)

The "right" way would be to make a copy of the Packages file, check it, and
only save it if the check passes.  According to Jeff, the proper check is
to do a "rpm --rebuilddb" with that Packages file and see if it works, but
I haven't tried that method.
-- 
____________________________________________________________________
TonyN.:'    The Great Writ     <mailto:tonynelson georgeanelson com>
      '      is no more.             <http://www.georgeanelson.com/>


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]