Bug 123093 - CDROM not ejected at end of installation
CDROM not ejected at end of installation
Status: CLOSED DUPLICATE of bug 116018
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
rawhide
All Linux
medium Severity low
: ---
: ---
Assigned To: Jeremy Katz
Mike McLean
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-05-12 07:37 EDT by Martin Braun
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 14:03:12 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
fix open of cdrom device (501 bytes, patch)
2004-05-12 07:38 EDT, Martin Braun
no flags Details | Diff

  None (edit)
Description Martin Braun 2004-05-12 07:37:27 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040112

Description of problem:
I created a DVD from the Fedora development tree
and did an installation using it. At the end of the
installation there was an error message (text console)
about being unable to eject the installation media.

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

How reproducible:
Always

Steps to Reproduce:
1. Install Fedora development from DVD
2.
3.
    

Actual Results:  DVD was not ejected before reboot

Expected Results:  DVD should have been ejected before reboot

Additional info:

I do not remember the exact message but it showed an obvious typo
(will attach patch).
Comment 1 Martin Braun 2004-05-12 07:38:47 EDT
Created attachment 100179 [details]
fix open of cdrom device
Comment 2 Martin Braun 2004-05-12 13:36:07 EDT
Might be a duplicate of #116018  
Comment 3 Martin Braun 2004-05-12 14:08:47 EDT

*** This bug has been marked as a duplicate of 116018 ***
Comment 4 Red Hat Bugzilla 2006-02-21 14:03:12 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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