Bug 893106

Summary:	RFE: add additional multiboot support
Product:	[Fedora] Fedora	Reporter:	Gene Czarcinski <gczarcinski>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	anaconda-maint-list, dshea, g.kaviyarasu, jonathan, sbueno, vanmeeuwen+fedora
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-03-13 19:09:52 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Gene Czarcinski 2013-01-08 15:31:50 UTC

Description of problem:
I understand that syslinux is being considered as an alternete bootloader for F19.  It would be nice if a little additional support was added for GRUB2 multiboot.

I am not referring to the multiboot support provided through the use of os-prober by the grub2 scripts.  No, I plan/assume that the individually/separately installed releases and/or distributions will the right grub.cfg files but will not have a bootloader installed in with the MBR or partition.  A separate system (or just a grub2 partition) will be installed in the MBR and add menuentry definitions pointing to the grub.cfg files for the other systems.

In kickstart, I currently have the choice of mbr, partition, or none.  None is almost the right answer in that no bootloader is installed into the MBR or partition, but it does not complete the configuration files /etc/default/grub and /boot/grub2/grub.cfg ... the RFE is to do this.

Comment 1 Chris Lumens 2013-01-14 15:11:11 UTC

Is this basically the same as bug 886502?

Comment 2 Gene Czarcinski 2013-01-14 16:40:17 UTC

It probably is but it is not just grub.cfg.

When location=none is specified (this is a kickstart), not only was grub.cfg not created but neither was /etc/default/grub.

Right now I get around this problem by specifying location=partition and then ignoring it.  What I want is that everything be the same except the grub2-install is not run.

I took another look at bug 886502 and I am not  sure.

This is what I want to be able to do:

1. After the system is installed and I somehow boot into it, disable use of os-prober.

2. The run grub2-mkconfig -o /boot/grub2/grub.cfg

3. I have a grub2 partition and the MBR points to it (it actually is a very small F18 system).  I then add entries in /etc/grub.d/40_custom pointing to the grub.cfg files on the real systems to be booted.

If the result of dealing with bug 886502 result in my ability to do what I want, this close this as a dup.

Comment 3 David Shea 2014-03-13 19:09:52 UTC

886502 mentions /etc/default/grub now, so I think it's fair to consider this one a duplicate

*** This bug has been marked as a duplicate of bug 886502 ***