Bug 98511 - ftp error message has wrong pathname
Summary: ftp error message has wrong pathname
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: installer
Version: 9
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-07-03 02:51 UTC by Stephen Samuel
Modified: 2007-04-18 16:55 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-07-09 05:23:11 UTC


Attachments (Terms of Use)

Description Stephen Samuel 2003-07-03 02:51:34 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624

Description of problem:
When installing via ftp, if the net installer cannot download the stage2 file,
it will complain that the wrong file is unavailable.

If you specify 
ftp.my.com  /redhat9
it will complain that it can't access
ftp://ftp.my.com//redhat9/RedHat/base/netstg2.img
checking the output from a ethereal capture, it's actually 
requesting
RETR /redhat/disc1/RedHat/base/netstg2.img

I'm guessing that the error message is inherited from the old installers that
expected all of the install CD's copied into one mamoth directory instead of
split by ISO image.

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

How reproducible:
Always

Steps to Reproduce:
1.Start installation without the files properly available on the FTP server
2. Put FTP files where the error message says it wants them.
3. Retry download
4. Compare error message with output from ethereal capture
    

Actual Results:  Message: cannot access
ftp://ftp.my.com//redhat9/RedHat/base/netstg2.img

Expected Results:  Message: cannot access
ftp://ftp.my.com//redhat9/disc1/RedHat/base/netstg2.img

Additional info:

Comment 1 Jeremy Katz 2003-07-09 05:23:11 UTC
Fixed in CVS and the update disk is at http://people.redhat.com/~katzj/9-updates.img


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