Bug 75541 - Installer hangs when file is "missing"...
Installer hangs when file is "missing"...
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Mike McLean
: FutureFeature
: 76067 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2002-10-09 15:01 EDT by Vesa Jääskeläinen
Modified: 2007-04-18 12:47 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-04-24 14:43:36 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:

Attachments (Terms of Use)

  None (edit)
Description Vesa Jääskeläinen 2002-10-09 15:01:06 EDT
Description of Problem:
Installer hangs when file it tries to access is missing. In CTRL-ALT-F3 
screen I can see:

* IOError 2 occured copying tftp-server-0.29-3.i386.rpm: No such file or 

It loops forever and displays that text at virtual console. If I go back to gfx 
mode, then screen has only couple of gray boxes...

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

How Reproducible:
Every time.

Steps to 
1. Burn CD's
2. media check them
3. try to install

Actual Results:

Step 2:

Step 3:
Failed, well... when I burned again that cd, unmounted it 
and switched disks then mounted it again... installer continued without anykinda 

Expected Results:
It could have asked what do you want to do now that file doesn't 
exists. And not to hang installation procedure to never ending loop.

Comment 1 Jeremy Katz 2002-10-16 17:57:18 EDT
*** Bug 76067 has been marked as a duplicate of this bug. ***
Comment 2 Jeremy Katz 2002-12-16 12:10:10 EST
This is fixed in CVS
Comment 3 Michael Fulbright 2002-12-20 12:38:25 EST
Time tracking values updated
Comment 4 Jeremy Katz 2006-04-24 14:43:36 EDT
Mass-closing lots of old bugs which are in MODIFIED (and thus presumed to be
fixed).  If any of these are still a problem, please reopen or file a new bug
against the release which they're occurring in so they can be properly tracked.

Note You need to log in before you can comment on or make changes to this bug.