Re: Problem with NON-STANDARD install
Pascal Hambourg composed on 2016-08-06 12:01 (UTC+0200):
...
If the boot image is in a PBR, the BIOS won't load it directly
It will if the PBR is on a primary partition on the same disk. It's how all
my systems boot if I'm not using IBM Boot Manager as the primary bootloader.
...
- or as a regular file in a filesystem appearing as
/boot/grub/i386-pc/core.img (or /boot/grub/core.img with older versions
of GRUB such as the one in Wheezy). This option is not recommended as
the filesystem may move the blocks around and the location of the core
image is hardcoded into the boot image.
This "not recommended" philosophy corresponds almost perfectly with the
practice universally complained about that Windows' installer replaces Grub
code that it finds in the MBR with its own legacy/generic boot code, code
which is just as capable of loading Grub code from a primary partition's PBR
as it is loading Windows code from a primary partition's PBR, which is how
Windows normally boots. When Grub is installed to a primary partition's PBR
in the first place, Windows "hijacking" the MBR is a non-issue.[1]
As a practical matter, moving core image blocks around is uncommon, and just
as easily fixed if and when it does occur as is reinstalling Grub to the MBR.
[1]
<http://old-en.opensuse.org/Bugs/grub#How_does_a_PC_boot_.2F_How_can_I_set_up_a_working_GRUB.3F>
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
Reply to: