Bug 231829 - [Anaconda Custom Installation] Block device for the CDROM unavailable for the postinst operation
[Anaconda Custom Installation] Block device for the CDROM unavailable for the...
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: Anaconda Maintenance Team
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-03-12 08:53 EDT by Olivier BONHOMME
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-03-23 14:25:30 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Olivier BONHOMME 2007-03-12 08:53:53 EDT
Description of problem:

When the CD-ROM is mounted in the beginning of the installation, the block
device is deleted in the /tmp directory. Then, it is impossible to mount again
the CD-ROM while the postinst stage.

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

Fedora Core 6 - Anaconda 11

How reproducible:

Making a custom installer and try to access the CD-ROM from a shell while the
installation

Steps to Reproduce:
1. Make a custom installer using buildinstall from anaconda-runtime package.
2. Burn an iso image
3. Try to install the system
4 .When anaconda is started (after the CD-ROM detection), open a shell and list
the /tmp directory
  
Actual results:

The /tmp/cdrom device is not present.

Expected results:

The /tmp/cdrom should be already present.

Additional info:

N/A
Comment 1 Jeremy Katz 2007-03-23 14:25:30 EDT
It's mountable, but you have to find and mount the actual device node.  This is
intentional
Comment 2 Olivier BONHOMME 2007-03-28 09:49:21 EDT
(In reply to comment #1)
> It's mountable, but you have to find and mount the actual device n

Do you mean by looking in the /proc filesystem ? (That's the way I did)

Anyway, I think that this case should be documented in the official anaconda
documentation. On all documentations I found, people suppose that the device
node is still available

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