Bug 28511 - installation of Wolverine does not auto eject CD
Summary: installation of Wolverine does not auto eject CD
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 7.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Erik Troan
QA Contact: Brock Organ
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-02-20 22:47 UTC by Suhaib Siddiqi
Modified: 2007-04-18 16:31 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2001-03-13 17:09:24 UTC


Attachments (Terms of Use)

Description Suhaib Siddiqi 2001-02-20 22:47:16 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.4.1-0.1.9 i686)


Installation of Wolverine on Dell PowerEdhe 1300 prompted for CD2 but did
not auto eject CD.  At the end of installation it rebooted, but did not
auto eject CD.

Reproducible: Always
Steps to Reproduce:
1. install of a fresh Dell PowerEdge 1300  (clean installation)
2.
3.
	

Actual Results:  Installation of Wolverine on Dell PowerEdhe 1300 prompted
for CD2 but did not auto eject CD.  At the end of installation it rebooted,
but did not auto eject CD.

Comment 1 Erik Troan 2001-02-22 02:53:38 UTC
Does the 'eject' program work after reboot?

Comment 2 Suhaib Siddiqi 2001-02-22 11:54:44 UTC
Yes!  Eject program works after installation.
Suhaib

Comment 3 Erik Troan 2001-02-23 18:16:36 UTC
Can you install again, and when it's complete (right before the system reboots)
cat /tmp/cleanup? There should be a line at the end which says "eject
/tmp/cdrom". If that exists, tell me what "ls -l /tmp/cdrom" says. Also, try
running this:

PYTHONPATH=/usr/lib/anaconda python -c "import isys; isys.ejectCdrom("hdf")

where "hdf" is the right device name for the cdrom on your system.

Comment 4 Matt Wilson 2001-03-13 17:08:56 UTC
Suhaib, we really need your input if we are to go forward with finding the
problem.


Comment 5 Erik Troan 2001-03-16 14:02:45 UTC
Closing because of lack of response.


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