On Fri, 2013-09-06 at 11:35 +0300, Alexander Todorov wrote: > На 5.09.2013 19:37, David Lehman написа: > > I don't think anything you do in anaconda is going to have much (if any) > > effect on an upgrade. The bootloader configuration is going to be > > updated by grubby (via the kernel rpm %post), which anaconda has no > > control over. > > > > If you are trying to keep the older version of your bootloader package > > through the upgrade I expect that to be impossible. > > > > Hi David, > a broader question, also related to: > https://bugzilla.redhat.com/show_bug.cgi?id=883891#c13 > > When upgrading via anaconda there is a screen to update, skip or create new > bootloader and the description text implies that bootloader configuration is > affected while it seems this is not the case. > > What do exactly are these options control ? > > - whether or not boot loader package (and what is in MBR) is updated or not or > - whether or not boot loader config file is updated or not (which is handled in > kernel %post). Anaconda has no control over what is run by kernel %post. new - Start fresh with an anaconda-produced bootloader configuration. This is at least partly for the user who needs to upgrade from LILO to GRUB. update - Re-install the current bootloader to the MBR but do not alter the current configuration. skip - Do nothing. Remember that in all of these cases the kernel %post will probably run grubby, which will do whatever it sees fit based on the configuration it finds. _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
