132990 not WSOD, maybe fixed

[David Kimdon <David_Kimdon@alumni.hmc.edu>]

retitle 132990 dbootstrap segfaults after base install
quit

> c) someone may find the reason for randomly appearing WSOD problem

I think the WSOD is fixed, it happenned with bf2.4 on system without
cdrom, at least it did for me and the reporter in Bug#134802.
Ben reported the WSOD and IIRC he had no cdrom either.  A quick google
search indicates that the IBM 560x in the original bug report has no
internal cdrom either.

The remaining issue is dbootstrap segfaulting at the end of the base
install (see the end of the bug report). That may be newt/slang
related (the last bug like that was).  newt/slang have gone through a
bunch of changes since that was reported.  Perhaps if a few people
complete an install with CVS b-f then this bug can be marked pending,
maybe.

-David