that is sick. they should take the rpm/database component out of the installation business. just write some script and note the packages installed in a flat file then after the system is up, build the complete rpm database? hmm
On 11/2/06, Andy Green <andy@xxxxxxxxxxx> wrote:
Tom Horsley wrote:
>> I always get
>>
>> "db4 error run database recovery"
>>
>> this happens in various places.
>
> My first reaction would be to blame the hardware :-). If you are installing from
> DVD or CD, you should be able to just type "memtest" (or maybe it is "memtest86")
> at the prompt when you boot from CD and have it run the memory test for you
> to eliminate (or confirm) one possible hardware problem.
There seems to be a real fault somwhere. Joachim Frieben wrote this
earlier in fedora-devel:
''The "rpm" problems reported in my previous post:
https://www.redhat.com/archives/fedora-devel-list/2006-October/msg00870.html
have also been observed by other users and have made their appearance in
Red Hat Bugzilla as bug #211917:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=211917 .
System freezes, corrupted rpmdb ... this is a very serious issue which makes
"FC6" and current "rawhide" essentially unusable on the affected systems.
Any ideas? ''
-Andy
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
-- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
