On Tue, 26 Nov 2013 20:24:32 -0700, Chris Murphy wrote:
> Well it's not a good recommendation to do what is explicitly not recommended
> by GRUB devs. grub-install spits out a warning if you try to do this, by the
> way. It requires the user pass --force for it to work.
>
No problem. So far I can live with it using blocklists.
# grep chain /etc/grub.d/40_custom
chainloader (hd0,6)+1
# chainloader (hd0,5)+1
# chainloader (hd0,4)+1
chainloader (hd0,1)+1
chainloader (hd0,2)+1
> And --force also isn't supported by anaconda for 4-5 Fedora releases now.
I'm not sure it ever really "supported" it. It had become a requirement
for various configurations with the introduction of GRUB2 (Fedora 16/17?),
since there has been quite a bit about that in bugzilla. OS Prober makes
it easy to adjust the boot loaders after a new installation without using
any rescue mode.
> It can't be used if /boot is on XFS or LVM or md RAID, all of which lack boot
> loader padding areas, so fewer configurations are supported.
>
Okay. I don't want to put separate /boot partitions on XFS, LVM or RAID.
Certainly not with a multi-boot desktop system (which uses LVM, though).
> You're better off using extlinux if you want something that supports
> installation to a partition.
It's good to have a fallback, at least. Grubby includes support for extlinux,
too.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
