From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.1b1; Mac_PowerPC)

Description of problem:
If the install of the i686 glibc (or other vital packages) fails for some 
reason anaconda ignores the problem and proceeds with the install, 
giving no feedback to the user that it is encountering problems.

In my particular case, I am trying to install RedHat 7.x on Connectix's 
Virtual PC 4.x.  Their appears to be a problem related to the 
Connectix i686 emulation, since the i383 glibc seems to run, but the 
i686 optimized one runs into serious problems, with ldconfig 
segfaulting (very bad!).  However, it is far from obvious to a naive user 
that this is indeed the problem.  Usenet newsgroups and Connectix 
support forums show people complaining that the RedHat installer 
couldn't write their boot sector -- this being the first indication of the 
problem (the dev package fails to install, so /dev/hda doesn't exist in 
the new filesystem).

Although the "install.log" file reveals the extent of the problem (huge 
numbers packages which didn't install because their (or their 
dependencies) %pre scripts couldn't run, and huge numbers of 
packages whose %post or %trigger scripts didn't run), there is no 
indication that these package installs are failing.

Perhaps some of the blame lies with rpm, rather than anaconda, but 
it certainly is not okay for users to be told that the install has 
completed successfully when the log shows numerous errors.  (Of 
course, some of the blame must also surely rest with Connectix 
whose buggy emulation appears to be the root cause of the problem 
-- of course, they may say that since Windows runs fine, they don't 
care).

Sadly, even once I had diagnosed the problem, there seemed to be 
no way for me to tell the installer that it should ignore the fact that the 
processor appears to be an i686 and that it should actually install the 
more generic i386 packages.  (If there is a way to do this, let me 
know and I'll give the installer another shot).

It would be cool if we could get this problem fixed for 7.2.


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Start Virtual PC 4.x (either on Mac OS 9, Mac OS X)
2. Attempt to install RH 7.x
3. Watch for first report of errors and compare to /tmp/install.log
	

Actual Results:  Mondo badness, unbootable install.

Expected Results:  Happiness and joy.

Additional info: