Bug 9263 - Draklive-install - Installing grub 1 to a partition on dual boot system doesn't add a chainload to grub1 in MBR
Summary: Draklive-install - Installing grub 1 to a partition on dual boot system doesn...
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard: 3beta3
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-05 16:51 CET by claire robinson
Modified: 2013-03-06 02:36 CET (History)
2 users (show)

See Also:
Source RPM: draklive-install
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description claire robinson 2013-03-05 16:51:16 CET 
Installing Grub (Legacy) to a partition doesn't add a chainload into the
mbr grub. Leaves it unable to boot the dual boot install without manual
configuration.

The classic installer has an extra step where it asks which drive you
boot from and IINM adds an entry.


Reproducible: 

Steps to Reproduce:
claire robinson 2013-03-05 16:51:53 CET

CC: (none) => tmb
Whiteboard: (none) => 3beta3

Comment 1 Dave Hodgins 2013-03-06 02:36:36 CET 
Claire, I'm going to close this bug as invalid, as this is normal.

When installing the boot manager to a partition, it's expected for
the user to manually add the chain loading of the partition boot
manager to what ever boot manager is in the mbr.

It may be grub, lilo, smart boot manager, Graphical Boot Manager (gag),
uefi, or someother boot manager.  The config file could be on an
encrypted filesystem, or other (network) filesystem, that is not
available to the installer.

The asking about which drive the system will be booted from, is to
ensure the correct hard drive number is specifed in /boot/grub/device.map
and /boot/grub/menu.lst.

Status: NEW => RESOLVED
CC: (none) => davidwhodgins
Resolution: (none) => INVALID
Note You need to log in before you can comment on or make changes to this bug.