Red Hat Bugzilla – Bug 70478
RFE: CD-booted network install should eject CD
Last modified: 2007-03-26 23:55:25 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1b) Gecko/20020722
Description of problem:
It would be nice if an NFS install started by booting the CD with askmethod
would eject the CD as soon as it's no longer necessary. Currently, the CD is
not ejected at all, so the system ends up rebooting the installer after
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Boot the CD with `askmethod' and, optionally, a kickstart file
2.Choose NFS install
Actual Results: CD is never ejected, and after installation is complete, the
installer boots up again unless the CD is removed.
Expected Results: It should be ejected as soon as it's no longer necessary.
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.