On Jun 11, 2013, at 9:06 AM, Tom Horsley <[email protected]> wrote:

> Anyone know if there are plans to provide an option to
> anaconda so I can have it install all the needed files
> in /boot, but don't screw with the MBR?

No current plans, the --force option for grub2-install was removed in anaconda 
18.x for F18. The option to install to /boot partition could safely be done to 
/boot on Btrfs since it has such a large boot loader pad. But I think this is a 
feature request down the road once /boot is no longer ext4 by default.

> 
> I have just setup a nice stand alone grub2 partition
> where I can do stuff like this:
> 
> menuentry 'Fedora 19 via multiboot' {
>       insmod part_msdos
>       insmod ext2
>       set root='hd0,msdos2'
>       multiboot /boot/grub2/i386-pc/core.img
> }

If this configuration file is to get GRUB Legacy to chain load GRUB 2, I'll 
briefly wonder why you don't just bite the bullet and move to GRUB 2 and drop 
an unmaintained boot loader.

If this configuration file is for GRUB 2 to chain load another instance of 
GRUB2, I'll think you don't understand that a core.img has already been loaded 
in order to understand the grub.cfg above in the first place.


> 
> With just the right stuff in /boot and no screwing
> around with MBRs or partition boot sectors, I can boot
> multiple versions of fedora this way,

The easier way to do this is to use one instance of GRUB 2 in the MBR gap, and 
then use configfile to load the grub.cfg for each distribution. Each 
distribution updates its respective grub.cfg when there are kernel updates, 
while static "master" grub.cfg uses configfile to forward to those distribution 
specific grub.cfg files.


> but the way
> anaconda works (as near as I can tell, anyway) it
> will trash my stand-alone grub2 when I install a
> new fedora version.



Well it's fakaked in that if you install a boot loader, it will break the 
function of the current boot loader. If you don't install a boot loader, then 
it fails to create core.img, grub.cfg, and the various *.mod files in 
/boot/grub2/i386. So yes, it's not very elegant.


Chris Murphy
-- 
test mailing list
[email protected]
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Reply via email to