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 other important need is to have a find-like utility to reconstruct
an rpmdb
using only md5 digests of installed files for those people who are not
saving
a copy of Packages ;-)
73 de Jeff
------------------------------------------------------------------------
_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list
_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list
