On 2011-02-02 15:54, Sean Dague wrote:
I don't think it actually matters.
It /shouldn't/ matter, but unfortunately it does. (See below)
The only reason MBR is special is
because the bios can find it without knowing about filesystems. A
chainloader can point to wherever and grub can go and read partitions
once it's loaded assuming you aren't using some really odd filesystem.
On 02/02/2011 03:44 PM, James E. LaBarre wrote:
I'd like to set up a system to "chainload" Grub2 from the XP boot menu.
The thing is, I have a separate /boot partition, and I can't tell from
any of the sites I've visited if I should be installing Grub to the
/boot partition, or to "/".
My layout is:
/dev/sda1 XP
/dev/sda2 /boot
/dev/sda5 swap
/dev/sda6 /
/dev/sdb1 /home
There are several situations where you'd want to install GRUB2 into a
/boot partition -- however, unfortunately installing GRUB2 onto a
partition rather than the MBR isn't officially supported AFAIK. Doing
so requires using "blocklists" (that means a list of disk blocks), which
is the complaint you'll get from GRUB2. I'm using this configuration on
one Desktop box, and over time I've found it to be a bit buggy and
problematic, because upon upgrades sometimes GRUB2 installs itself into
the MBR instead of /boot, which causing the bootup to endlessly restart.
So if you have the choice, install GRUB2 into the MBR.
--
-- Chris
--
Chris Knadle
[email protected]
_______________________________________________
Mid-Hudson Valley Linux Users Group http://mhvlug.org
http://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug
Upcoming Meetings (6pm - 8pm) MHVLS Auditorium
Feb 2 - Zimbra
Mar 2 - MHVLUG 8th Anniversary - Show and Tell
Apr 6 - Introduction to IPv6
