Hi all
I just upgraded from 13.1 to 13.2 and all seems well, the system boots normally (and very quickly!)
My question relates though to YAST2 bootloader management. When I start YAST’s bootloader module, all the fields are blank and the main drop-down option shows “Do Not Install Any Bootloader”. Does this mean YAST no longer maintains my bootloader? Although I don’t need to change anything just now, I don’t understand what’s going on and I feel uncomfortable in that situation! 
Thanks
Fred
Yes. The boot loader installation will not be touched at all by the system.
Which boot loader are you using? Did you install it manually?
Is this a multiboot system, or do you only have openSUSE installed?
Normally, you should change that option to “GRUB2” and everything would be ok.
Probably you used a different boot loader in 13.1 (grub legacy maybe?) and that’s the reason why it is set to “None” now. Support for everything else except grub2 has been removed (in YaST).
Thanks. Well I’ve barely touched the bootloader since I first started using Suse in 2006 with whatever bootloader it installed then (Suse 10.1), so I guess that is legacy!
Is there any good reason to change it now to grub 2? It was dual boot with an old version of Windows but I don’t use that any more so losing that option isn’t an issue for me.
Should not lose any options. Grub legacy is being phased out in favour of grub 2. The doping of grub legacy (1) in Yast seems to be a hint 
Yes it does look that way. 
So I would just switch to Grub 2 in YAST and accept the default options it shows?
I would say though that I don’t really see any merit in changing something that works where the only apparent benefit is to enable maintenance via YAST.
Yes.
grub2 should be installed by default, if not YaST will probably try to install it automatically.
I would say though that I don’t really see any merit in changing something that works where the only apparent benefit is to enable maintenance via YAST.
Well, grub2 is the only version that is maintained upstream by the grub developers, and it has additional features, file system support and so on.
But in the end it’s your decision. If grub legacy works, it will continue to work and there’s no need to change (at the moment at least).
Your point about maintenance is a good one. I’ll have a think about it!
On 2015-05-31 17:56, gogalthorp wrote:
>
> Should not lose any options. Grub legacy is being phased out in favour
> of grub 2. The doping of grub legacy (1) in Yast seems to be a hint
Well, in that case, the upgrade process should have handled the change
automatically, or warned the used that he has to do the migration
himself before proceeding.
If the upgrade was made using the “boot dvd, choose upgrade method”
(offline upgrade), it might have done this. I have seen similar things
in the past. On the other hand, the online upgrade procedure (zypper
dup) would not do it.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Minas Tirith))
On 2015-05-31 18:16, wolfi323 wrote:
> But in the end it’s your decision. If grub legacy works, it will
> continue to work and there’s no need to change (at the moment at least).
Some people still use lilo, which is even older.
Me, I prefer grub 1. With its penguins
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Minas Tirith))
Yes, it was done by zipper dup.