Description of Problem:
Sometimes (human error, lack of media, lack of floppy drive, whatever) one
simply CANNOT get a copy of an anaconda traceback off a failing install
This actually provokes an idea on my part -- Why not 'tee' in all
instances anaconda tracebacks, in the case of install/upgrade failures,
into /tmp/anaconda-traceback.txt, and/or the install/upgrade log, so that
sysadmins, and indeed less experienced customers finding errors, can give
better reports, even if a proper floppy, with proper vfat modules, is not
See also bugzilla 30029
Marking to consider for next release, we're past our feature freeze.
Repoened after release of RH 7.2
Thi sstill seems like a useful helper for the Beta phase, and indeed for RH
support in debugging a failing install for retail install support.
Please consider inclusion of this as a SOP as we enter RH 8.0 beta testing. --
now is the time!
Deferring to future release.
We are now hopefully before feature freeze -- freezer burn here (smile); Reopen
as an RFE for post RHL 8.0 consideration in planning items for next release
I have fixed this so if /mnt/sysimage is mounted then the traceback will go into