Re: python 2.4

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> > When I installed FC3 from burned ISO's, I had bad media (didn't run
> > media check).  When anaconda ran across a corrupt RPM on CD 3, it asked
> > me over and over if I wanted to retry, but it never offered me an option
> > to reboot or retrieve said RPM via HTTP so the rest of the install could
> > proceed.  I hit Ctrl-Alt-F1, Ctrl-Alt-Del to reboot until I could get
> > the media fixed.  I would like to see a more user-friendly approach when
> > corrupt RPMs are found.
> 
> We only set up the network on network installs.  Doing more than that
> makes things quite a bit more complicated.  Retrying is about the only
> option you have.  Adding "abort installation" is an option but you're no
> better off then than if you hit the reset button, so I'm not sure what
> the real advantage is.

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.

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.

/Brian/



[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux