At 10:43 AM -0500 11/27/06, Tony Nelson wrote: >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. Great. /Now/ these messages come through. Three messages to rpm-list seem to have been stuck at my server (?). No other messages to other places appear to have had this issue. >Received: from dc2-web23.assortedinternet.com (dc2-web23.assortedinternet.com > [66.36.233.11]) > by mx3.redhat.com (8.13.1/8.13.1) with ESMTP id kATMrqQo020733 > for <rpm-list@xxxxxxxxxx>; Wed, 29 Nov 2006 17:54:02 -0500 >Received: from pool-68-239-53-64.bos.east.verizon.net ([68.239.53.64] > helo=[192.168.123.162]) > by dc2-web23.assortedinternet.com with esmtpa (Exim 4.52) > id 1GoicC-00031b-H0 > for rpm-list@xxxxxxxxxx; Mon, 27 Nov 2006 10:41:52 -0500 -- ____________________________________________________________________ TonyN.:' The Great Writ <mailto:tonynelson@xxxxxxxxxxxxxxxxx> ' is no more. <http://www.georgeanelson.com/> _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
