On 11 August 2014 15:13, Josef Reidinger
Hi geekos, I plan to implement https://features.opensuse.org/317700. What it is and why we need it? In general grub1 and grub2 configuration is almost completely different, which makes yast2-bootloader life hard as it contain two almost separated parts, which we need to maintain and we have a lot of bug reports which we cannot handle about various misconfiguration. We focused on fixing stuff for grub2 to work for everyone, but grub1 stuff still make quite a lot of mess in code. So I plan to do some cleaning in yast2-bootloader and also simplify how it works to make maintenance and new features easier to born ( like quite nice direct boot from encrypted LVM ). Such simplify should contain also complete drop of grub1 support. Of course we allow usage of such bootloader, just you cannot use yast2-bootloader to configure it. In installation you can simply choose "none" bootloader and configure it manually as you want, same way as you can use old lilo or anything else.
Our goal for yast2-bootloader is to have tool that create working boot configuration for everyone ( everyone from technical side of view, for different storage configuration and different hardware, not to support all personal requirements ). So I would like to ask if anyone have troubles with grub2, that grub2 cannot be used for his hardware or storage setup, so we can handle it before I did it.
If anyone is interested in maintaining yast2-bootloader for grub1, I can create splitted package, that handle only grub1 configuration ( but I do not do it unless there is serious maintainer as it is additional work for me ).
Josef --
FWIW - I have only used Grub2 since it's become an option in openSUSE. It's worked without issue on all my hardware, including some pretty exotic stuff. So, from my perspective, +1 to the idea of dropping Grub1 support from yast-bootloader -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org