Bug 70478
Summary: | RFE: CD-booted network install should eject CD | ||
---|---|---|---|
Product: | [Retired] Red Hat Public Beta | Reporter: | Alexandre Oliva <aoliva> |
Component: | anaconda | Assignee: | Jeremy Katz <katzj> |
Status: | CLOSED WONTFIX | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | limbo | Keywords: | FutureFeature |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-02-26 18:01:42 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: | |||
Bug Depends On: | |||
Bug Blocks: | 67218 |
Description
Alexandre Oliva
2002-08-01 17:15:37 UTC
Jeremy do we know enough in stage 2 to do this? Unfortunately not. Also, just ejecting the CD won't do much good since most PCs will close the CD door on boot and thus the cycle would still be repeated. Defer to look at for a future release to see if there's anything we can do The point was not really about avoiding rebooting into the installer, but rather about knowing when it is safe to eject the CD to use it for something else. Presumably it's just a few seconds after installation starts, and not 30-60 minutes later when it's all done. Couldn't the installer just check for say root=/dev/cdrom in /proc/cmdline? The root isn't /dev/cdrom so there's no way to tell; as far as the kernel is concerned, it's a kernel + an initrd from "somewhere", it doesn't care where. And fwiw, it's safe to remove the CD as soon as the kernel has finished loading. How about arranging for the CD initrd to eject the CD if askmethod is given in the command line, then? Could this hurt in any way? Erhm... But this won't help my kickstart case... Oh, well... There's really no way to do this since we don't have any information about how the machine booted once the kernel starts. |