Re: Registration for Crux bug tracker / Issue 1857: Lilo usage

10 Jan 2022

      -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi Markus,

On Mon, 10 Jan 2022, Markus Heinz wrote:
...
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.
Maybe it would work to update the grub.cfg from crux?
...
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.
Maybe grub allows for having include files (I have not checked), then you 
could have two include files: one for crux and one for ubuntu - and just 
update the one of the currently-running system.
...
...
Best regards,
Tim
Best regards
Markus Heinz
regards,
Erich

Re: Registration for Crux bug tracker / Issue 1857: Lilo usage

Erich Eckner