On Tue, 5 Sep 2000, Chris Garrigues wrote:
> In particular, it gives ugly backtraces if you have a kickstart file that
> worked just fine with RedHat 6.2.
>
> Incompatible changes are bad enough, but these failures should be more
> graceful and give more clue what's wrong.
I second that motion; more liberal use of try exceptions would make
anaconda behave better:
o More understandable for the end user (ie, you're out of space on the
root drive instead of my.long.stactrace.from.hell.which.confuses
the.novice.user)
o Easier to debug for RedHat developers
o A clear separation from *real* bugs as opposed to operating
environment bugs (bad ISO image, dropped FTP connection during
install, etc.) A stack trace would always be a bug, instead
of WORKSFORME or NOTABUG "solutions".
--
The wheel is turning but the hamster is dead.
Craig Kelley -- [EMAIL PROTECTED]
http://www.isu.edu/~kellcrai finger [EMAIL PROTECTED] for PGP block
_______________________________________________
Redhat-devel-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-devel-list
