Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 80543 - total and remainding times too low in anaconda
total and remainding times too low in anaconda
Product: Red Hat Public Beta
Classification: Retired
Component: anaconda (Show other bugs)
i386 Linux
low Severity low
: ---
: ---
Assigned To: Michael Fulbright
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2002-12-27 15:19 EST by Féliciano Matias
Modified: 2005-10-31 17:00 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-01-02 18:08:46 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 Féliciano Matias 2002-12-27 15:19:40 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.6 (X11; Linux i686; U;) Gecko/20020830

Description of problem:
The total and remainding times are too low in anaconda at the beginning of the
package installation process.

I only try installation from cd-rom.

Example :
fists extimations : 4 min.
final time : 10 min.

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

How reproducible:

Steps to Reproduce:
1. Install Phoebe

Actual Results:  Estimate time too low.

Expected Results:  Better estimated time.

Additional info:

There is the same problem in RH8.0.
Comment 1 Michael Fulbright 2003-01-02 18:08:46 EST
Well known issue.

Not clear how to improve at this point.  Things like running ldconfig after alot
of package installations take more and more time as install progresses.

Comment 2 Miloslav Trmac 2003-01-09 14:13:29 EST
Another data point: At the very start, the estimate is ~16 minutes.
After glibc-common is installed, it is reduced to only 2 minutes,
presumably because glibc-common actually installs much less than
the 186 MB of all locales.

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