It would appear that on Dec 4, deano ferrari did say:
> jtwdyp;2508369 Wrote:
> > why grub legacy have grub2 core.img “title”?
> >
> > I use grub legacy. Yet my grub menu includes:
-snipped. . . . . . . . . .stuff
> > And I’m not sure why???
> >
> > Especially since: the location of “core.img” isn’t quite right…
> >
> You’re correct about the core.img location. I edited mine to reflect
> reality
>
> Code:
> --------------------
> kernel /boot/grub2/i386-pc/core.img
> --------------------
>
> I then chainloaded grub2 (successfully), and after I was happy, I
> decided to make the move to grub2 completely.
You mean chainloaded to grub2’s command shell right?
At least that’s what I got when I tried it…
I’m wondering how independent of the root partition that is?
In my case, I’m decidedly NOT happy with grub2.
It takes too much work to get it to use ONLY LABEL= rather than the
UUID= (which actually offends me for it’s lack of human readability)
That plus I’m stubborn about the appearance of my boot menu.
I can’t stand any kind of background image what so ever.
I insist on plain text. (in a font I can actually read without a microscope)
I strongly prefer to only enhance that plain text with the kind
of color control afforded by something like:
Pretty colours
color green/blue black/magenta
Also a LONG time ago I created a separate boot partition by way of making a
small ext2 partition, using mc to replicate /boot there, then temporarily
mounting it on top of /boot, and using the grub shell to install it to the
MBR. Then All I had to do was edit it as necessary to boot all the assorted
distributions that I’ve installed ever since. I also included chainloader menu
choices for each of the partitions on which I install whatever Linux I’m
currently using. Thus I can instruct each installer to install it’s bootloader
to the root partition involved so that I can fall back on the distro’s standard
bootloader anytime I fail to find the time to update mine.
The grub legacy I so installed kept working even after I reformatted the root
partition of the “no longer installed” distribution I used to create it. I’m
not so sure a grub2 boot partition would…
Because I only use the distribution maintained boot loaders occasionally I only
really care about getting them to use grub legacy because every now and then
an installer succeeds in concealing the choice to NOT molest my MBR with
it’s bootloader, and if none of my installed Linux still use grub legacy, then
it’s going to be harder to restore my grub menu to the MBR…
Still I kind of like the idea of having a grub shell available as a grub
menu choice, even if it’s a grub2 shell.
Well in any case, thanks for the info…
–
JtWdyP
