Bug 8033 - Anaconda bombs out on PCMCIA ftp install
Anaconda bombs out on PCMCIA ftp install
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Jay Turner
Depends On:
  Show dependency treegraph
Reported: 1999-12-28 18:45 EST by wearl
Modified: 2015-01-07 18:40 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-02-09 22:10:48 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description wearl 1999-12-28 18:45:06 EST
When installing Red Hat 6.1 on a Dell Inspiron 3500 laptop using the
updated pcmcia + updates disks, anaconda bombs out consistantly right
before package selection with an error.

I've found this to occur with the original pcmcia image as well.

I've found that this occurs with both a local mirror of the Red Hat 6.1 cd,
as well as remote mirrors.

Note that while it bombs out on an ftp install, the http install works
Comment 1 Jay Turner 2000-02-09 22:10:59 EST
My guess would be that this is the result of either A) losing the connection to
your FTP server or B> performing the install against a FTP server running
wu-ftpd-2.6 (this is from memory, so don't quote me on this one)

In the first case, the installer did not handle timeouts really well, and since
the FTP installer creates a new FTP session for every package that it downloads
(the behavior has been improved in the latest installer) there is a good chance
that your FTP server is timing out at some time.

In the second case, there is a known conflict between the installer and wu-ftpd
which results in very bad things (tm).

The HTTP install actually used the exact same code that the FTP installation
method does, so I would have to assume that since the HTTP installer is working,
it is not a code problem.  Reopen this bug if you are continuing to have
problems after the above notes.

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