Hello Tim, On 10.01.2022 18:57, tbier@posteo.de wrote:
Hi Markus
On 10.01.2022 18:20, Markus Heinz wrote: [...]
https://crux.nu/bugs/?do=details&task_id=1857
I am still using lilo for booting my Crux installation. It fits perfectly for me as I invoke lilo as secondary boot loader from the boot loader of another OS (chain loading). So each OS on my PC has its own boot loader and I do not need to boot the other OS e.g. after updating the kernel on my Crux installation to configure the new kernel. I then just run lilo to update my Crux boot configuration and everything is fine.
But.. why?
The other OS is Ubuntu Mate with grub as boot loader in the MBR. Of course I could use that grub to also boot Crux directly. But then I had to boot Ubuntu every time once I have updated my kernel on Crux and run update-grub on it to just boot Crux again to try the new kernel. With the setup I have now (grub chainloading lilo) I just run lilo on Crux and reboot directly into Crux again. So I do not need to boot Ubuntu meanwhile for updating the boot loader.
So I was sad if there was no more Lilo port in the next Crux version.
If upstream doesn't solve uefi issues or whatever it was that broke it for modern CRUX deployments I don't see the point of holding onto a port for its sentimental value. You are always free to fork it and maintain it yourself.
Having my own lilo port was not a problem. But it would make fresh installations more complex for me in case I have a new PC at some time.
But for me, grub works perfectly fine on all my deployments. On my desktop it dualboots CRUX and Windows 10. I need to use grub-mkconfig after updating a kernel, so what?
AFAIK grub does not like to be installed elsewhere as in the MBR. So it seems the Ubuntu grub chainloading the Crux grub (in the Crux partition) is not an option. I did not try grub chainloading another grub. But in the past I made the observation that there were issues with grub not being installed in the MBR. I do not know if with recent grub versions this has changed.
Just mind that Windows will try to install its own Bootloader, but we don't need to let it.
No Windows on my PC :-)
Best regards, Tim
Best regards Markus Heinz