Red Hat Bugzilla – Bug 184220
Installer does not create grub.conf if selected to not be installed on MBR
Last modified: 2008-03-10 21:12:09 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:220.127.116.11) Gecko/20060111 Firefox/18.104.22.168
Description of problem:
When installing the system, if Grub is told NOT to install to the MBR, it doesn't appear to make a grub.conf either. Therefore you cannot simply boot into Linux rescue and grub-install to make the system work, you have to make a grub.conf by hand or something along those lines.
I was hoping to make a boot CD and not install GRUB to the MBR of a test machine, so I didn't install MBR. When I couldn't find mkbootdisk, I decided to install grub, and found that the config files didn't exist.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Run installer
2. Chose not to install GRUB to MBR.
3. Look at /etc/grub when finished
4. Note that grub.conf/menu.lst/etc does not exist.
Actual Results: No grub.conf, unable to install grub without manual creation of files.
Expected Results: The config files should all be there ready for the user to run grub-install if they want to later.
Fedora Core 5 and Fedora Core 6 are, as we're sure you've noticed, no longer
test releases. We're cleaning up the bug database and making sure important bug
reports filed against these test releases don't get lost. It would be helpful if
you could test this issue with a released version of Fedora or with the latest
development / test release. Thanks for your help and for your patience.
[This is a bulk message for all open FC5/FC6 test release bugs. I'm adding
myself to the CC list for each bug, so I'll see any comments you make after this
and do my best to make sure every issue gets proper attention.]
The information we've requested above is required in order
to review this problem report further and diagnose/fix the
issue if it is still present. Since there have not been any
updates to the report since thirty (30) days or more since we
requested additional information, we're assuming the problem
is either no longer present in the current Fedora release, or
that there is no longer any interest in tracking the problem.
Setting status to "INSUFFICIENT_DATA". If you still
experience this problem after updating to our latest Fedora
release and can provide the information previously requested,
please feel free to reopen the bug report.
Thank you in advance.