Bug 111021
Summary: | Needed disks cause failure when disk inserted into /mnt/cdrom1 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Ed Belisle <ebelisle> |
Component: | redhat-config-packages | Assignee: | Jeremy Katz <katzj> |
Status: | CLOSED NEXTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 1 | CC: | tao |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-09-21 20:18:16 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ed Belisle
2003-11-26 15:26:30 UTC
I encountered the same problem and got around it. I have two drives, a Plextor writer on /dev/scd0 (/dev/cdrom1) and a Toshiba DVD drive on /dev/hdd (/dev/cdrom). Point to /mnt/cdrom1 and /mnt/cdrom respectively. 1. Started redhat-config-packages with disc in /mnt/cdrom1. If packages I selected are on current disc, everything is fine. If not, program prompts me to switch discs. I switch, let it spin up, then continue. Program exits with generic error message. Terminal debug info complains that it could not find file in /mnt/cdrom. Hmmmm. 2. Same as #1 except started with disc in /mnt/cdrom drive. If packages I select are already on current disc, it's fine. If not, prompts for different disc. I follow along and everything works great. 3. Start with disc in /mnt/cdrom1, install package on different disc. At prompt put requested disc into /mnt/cdrom instead. Worked fine. Probable cause: after a disc swap, program searches only /mnt/cdrom for the new disc, regardless in which drive it initially found a disc. This report is filed against a product which is no longer supported. It is very likely that the problem is resolved in the current version of Fedora Core or scheduled to be resolved with the new system-config-packages scheduled to land in Fedora Core 5. |