On Wed, Dec 01, 2004 at 08:23:51AM -0500, Brian Long wrote: > To make Linux more user-friendly, it shouldn't retry forever. :) It > should keep a retry count per RPM and if the user retries 3 times, it > pops up a dialog saying the installation has failed and they should > restart. I kinda want it to retry forever on a network install. > Or even better, it could offer the option to skip the RPM. Depending on > the groups selected for installation, a corrupt -devel RPM not getting > installed is not a big deal. In fact, any RPM not "mandatory" in > comps.xml could be skipped (I imagine). The rest of the install would > proceed as normal and maybe populate a file that firstboot could read > and try to install the corrupt RPMs once networking is enabled. Just an > idea. The whole RPM transaction set would need to be recomputed.... -- Matthew Miller mattdm@xxxxxxxxxx <http://www.mattdm.org/> Boston University Linux ------> <http://linux.bu.edu/>
