Description of problem:

I was trying to do an NFS install of RHEL3U2, and every time I entered
the information of the server/directory (using linux askmethod) when I
installed, it would say something like "installer exited with signal
11" and I would have to reboot.

After a while I realized that I had rebooted the machine that had the
install images available over NFS, and I hadn't restarted nfs on that
machine.

The bug here is that if nfsd isn't running on the machine name
entered, the installer should re-prompt or give an error message to
that effect rather than crash with only signal 11 as the output, since
that offers no real debugging information to the user.


Version-Release number of selected component (if applicable):
rhel3u2

How reproducible:
always -- try installing via NFS when the machine that you enter as
the nfs host isn't running nfsd

Steps to Reproduce:
1. see description
2.
3.
  
Actual results:

anaconda crashes

Expected results:

non-crash, more informative error message

Additional info: