Bug 76802 - More logic to "Completed"-message
More logic to "Completed"-message
Product: Fedora
Classification: Fedora
Component: anaconda-help (Show other bugs)
All Linux
high Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Mike McLean
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2002-10-26 19:04 EDT by Petri T. Koistinen
Modified: 2007-11-30 17:10 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-04-05 10:23:19 EDT
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 Petri T. Koistinen 2002-10-26 19:04:06 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
There is odd logic in "Complete"-message which appears after (text mode)

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

How reproducible:

Steps to Reproduce:
1. Install Red Hat. =)

Actual Results:
Messages after installation:


Congratulations (for installing Red Hat Linux x.y ...)

Please, remove all floppies from drive.

If you made boot floppy, insert it...

(See the bad logic: first remove all floppies, then insert boot floppy again.)

Expected Results:


If you created boot floppy, please leave it to drive so it can be tested,
you don't need to use it in further boots.

In case you didn't create boot floppy, please make sure floppy drive is
empty before booting.

Additional info:
Comment 1 Jeremy Katz 2003-01-10 02:29:33 EST
This looks to be clearer in our current codebase
Comment 2 Petri T. Koistinen 2003-04-05 16:18:05 EST
Does it?
Comment 3 Petri T. Koistinen 2003-05-17 11:40:35 EDT
What kind of completed installation successfully message you have now?
Comment 4 Petri T. Koistinen 2004-01-27 10:04:39 EST
What does Fedora say?
Comment 5 Petri T. Koistinen 2004-04-05 10:23:19 EDT
I guess it's fixed.

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