First, I managed to get past the other bugs using RH 6.1 and updated
bootnet and updates disks when trying to do a kickstart installation
via NFS using static IP. So farm this has not been pleasant.
So, I am booting with "linux updates ks=floppy". The location
I specify with "nfs --server <ip> --dir <dir>" is mounted and
"python /usr/bin/anaconda" starts (well, ps shows that there are
2 such process). It looks like anaconda is running with args
of "-m dir://mnt/source/. --kick" (couldn't see anymore).
At that point, I only have the blue screen on console F1. It's actually
worse than the BSOD because I can't look at it for a while and pretend
the information is meaningful :-(
This is holding up a largish installation effort and I'd be happy to
try anything you might suggest to see this get fixed.
So far, I have:
- fixed the perms on stuff in instimage/usr/bin and
instimage/usr/X11R6/bin to be executable
- removed all traces of the ftp site (ls-lR files, eg)
from the mounted redhat dist
Created attachment 41 [details]
how to hang anaconda