Re: execution order involving the bootloader install

Gene Czarcinski <gczarcinski@xxxxxxxxx> · Fri, 23 May 2014 07:32:19 -0400



    On 05/22/2014 08:16 PM, Chris Murphy
      wrote:

    
      Observations with today's
        Rawhide: Fedora-Live-Workstation-x86_64-rawhide-20140522.iso
      

      First, the grub.cfg is hosed. The rescue boot entry is listed
      first, and is the default. It should be reversed.
      https://bugzilla.redhat.com/show_bug.cgi?id=1100504
      

      I don't know which component's bug this is, anaconda for
        calling grub2-mkconfig before the kernel and initrd have even
        been created, or grubby for not adding the entry in the right
        location. So before I file anymore bugs I'd like to know whether
        grub2-mkconfig is really supposed to be called before all
        kernels and initramfs's are in /boot, and the expectation is
        that grubby will fix all missing items in the grub.cfg.
      

    The change is in install.py and was done intentionally in support of
    OSTree.  I do not completely understand the reasoning.

    
    I am currently testing doing a forced extlinux as the bootloader
    situation.  I first installed into a virtual system with regular
    partitions using a Fedora 20 DVD iso and it successfully installed
    and rebooted.  I am now in the process of testing a forced extlinux
    bootloader for a simple network install.  I do know that some of my
    patches fixing/enhancing extlinux as the bootloader are screwed by
    the change.

    
    With grub2 and the latest grubby-8.25-1, you can reboot an install
    of a livecd system but, as you say, the default is the rescue system
    because the specified value in /boot/grub2/grubenv is not valid.

    
    I believe that the OSTree enhancement with respect to the bootloader
    needs to be explained,  discussed, and tested a bit more before
    deploying the implemention.  Yes, I know it is rawhide and thus
    can/will break things.  But, anything dealing with the bootloader is
    both complicated and mostly pretty fragile.

    
    Gene

  
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list