Registration for Crux bug tracker / Issue 1857: Lilo usage
Hello, I just wanted to register for the Crux bug tracker. But I cannot find a registration form. Did I miss it or is there none? What is the procedure for registration for the Crux bug tracker? I wanted to register for commenting on this issue: 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. So I was sad if there was no more Lilo port in the next Crux version. Regards Markus Heinz
Hi Markus On 10.01.2022 18:20, Markus Heinz wrote:
Hello,
I just wanted to register for the Crux bug tracker. But I cannot find a registration form. Did I miss it or is there none? What is the procedure for registration for the Crux bug tracker?
Sorry, this is a wip I guess.
I wanted to register for commenting on this issue:
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?
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. 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? Just mind that Windows will try to install its own Bootloader, but we don't need to let it. Best regards, Tim
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
-----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 -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEE3p92iMrPBP64GmxZCu7JB1Xae1oFAmHclt4ACgkQCu7JB1Xa e1qMBQ/8CkS+OGAzXUGpnXoMyfI8BX+OwOeqhGh+R1ev8fXcZ1nScmH9mmtpY7zF zg05qjOCDdRnFTbx0jQ21AJirGsfiBRsOm8s2mEw5qUImJTEVR/OawEit9xlanbP Qe1sE2xQxhFo1O+YDnoycX0CkoKa0dNNYVk5HydFIMdmOeAyK0Rsa8m4YrNVNn94 TlDXU/60iP365nikopBJNeaBuErXTQAF++GkgBe5t8goRd5Sc5GWw+9jyirhuzQX ikHANUrWZ3UhGL9VLSb07Mo0pK72Xo+H8+5Z9YXeDZNEL0Sg4I+EXe/3OHhRI6se kCiLC00YP/GOJ61GTnAWJiZovlk8bGl4fWjhZK3ZooXdEmBQZUafzQhdgt678m3I FGFPVivzTs7mMbO7P3hTljeeb362afSeoz0ClHbW7gA+nvilvZk90DT4czR4k3Fd 1mSUA419mrFpOWHgKYS9KFWCJbL8tkvBgFKdN00vkn9BbPRmL5G5Arw8wgfICE1A jySiGMMO48UXS1VbBZlgI47darCVc0A67AbzQCvcVPM71MzS5vAr2bOsFdTBh0pc ktNUlx4gz8hE5xtwFxxRYg4C7U2vZaZEj0FbEEpttty6SfPB4hfeyPKqjDyLT8sL hl9NJ77Le0s+Z+E01AZdejtn5WJ2fYb6baCFMSZpFxiD0VrmpaI= =DGhc -----END PGP SIGNATURE-----
On 10.01.2022 21:28, Erich Eckner wrote:
Maybe it would work to update the grub.cfg from crux?
I was going to say the same thing there.
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.
That should certainly work as well with grub.
Am 10.01.2022 21:33, schrieb tbier@posteo.de:
On 10.01.2022 21:28, Erich Eckner wrote:
Maybe it would work to update the grub.cfg from crux?
I was going to say the same thing there.
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.
That should certainly work as well with grub.
Thanks for pointing me in the right direction. I have now appended these lines to /etc/grub.d/40_custom (on Ubuntu) which will be assembled to grub.cfg: menuentry "Crux Linux (no LILO)" { set root=(hd0,3) linux /boot/vmlinuz ro root=/dev/sda3 init=/sbin/init initrd /boot/early-ucode.cpio } Like this I can boot Crux from the Ubuntu grub as long as I name the kernel file always the same. It evens boots much faster than with Lilo in between :-) Lilo took several seconds to load the kernel into RAM whereas with grub it nearly starts to boot the kernel immediately. Best regards Markus Heinz
participants (3)
-
Erich Eckner -
Markus Heinz -
tbier＠posteo.de