Bug 7872

Summary: anaconda hangs, but I got past other bugs
Product: [Retired] Red Hat Linux Reporter: patrick.dowler
Component: installerAssignee: Jay Turner <jturner>
Status: CLOSED NOTABUG QA Contact:
Severity: high Docs Contact:
Priority: medium    
Version: 6.1CC: jorma.laaksonen, srevivo
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-02-22 19:19:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
how to hang anaconda none

Description patrick.dowler 1999-12-18 01:00:54 UTC 
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

Anything else?
Comment 1 patrick.dowler 1999-12-20 19:06:59 UTC 
Created attachment 41 [details]
how to hang anaconda