Per Jessen wrote:
Cristian Rodríguez wrote:
On Thu, May 12, 2016 at 10:09 AM, Per Jessen
wrote: Please keep lilo. That's the only boot-manager we use. LILO development is finished and it will probably bitrot quickly. please use GRUB2 or systemd-boot (this one is just for UEFI though)
Guys, I'm not really up to a discussion about why and why not, Tomas only asked if there were any lilo users left. If there is an easy solution to the build issue, I would like keep lilo in factory.
I've tried grub before -- didn't work. lilo worked reliably during the year or two that grub couldn't handle journal'd file systems. It works in alot more situations than grub does and uses the same nomenclature as the kernel (/dev/sda1 or /dev/mapper/....). Grub has a non-consistent grammar w/the rest of the system. Lilo is also documented in how it works and as the default loader in the kernel documentation. It seems keeping the kernel defaults would make for being a good community member. Also if I remember correctly, doesn't grub require booting from an already running system like a ram-disk-img? Lilo doesn't and still allows the user the option of booting directly from disk -- which is what systemd recommends for boot speed. Getting from start of kernel execution to user-login prompt on a server (no GUI) in 30 seconds is still pretty much a constant, w/o SSD's. I also was regularly able to use grub with an attached serial cable as the console, vs. w/grub insisting on a GUI boot at the time and showing only a blank screen while one wondered what the machine was doing. Note: the server, w/12 cores, doesn't even have a graphics card slot (but does support on-board VGA). It's weird how bugs develop in other parts of the distro, so people use that as reasoning to get rid of packages that use them -- just like xfs was "dissed" as a boot-partition when grub was broken -- if people were using lilo -- there never was any problem -- and no need to switch root partitions. Last I looked, lilo was the only boot loader with it's source hosted and kept in sync with the kernel. Before removing lilo, you might want to check on the lkml about usage -- you might get a very different answer... -l -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org