Question: What is the suggested method to multiboot Linux distributions on the same disk with Limine?

[sinayion]

Hi all,

Since Limine will not support a XBOOTLDR partition what is the correct way to have multiple Linux distributions on the same disk, all handled by Limine? Assume one /boot partition and the rest of the disk is for the root partitions of the distributions.

I ask this, since I believe having every distribution touch the same /boot partition is dangerous, since they may overwrite each others key files, such as the kernels.

[Zesko]

You are looking for limine-entry-tool as an extra tool that manages multiple boot entries across different distros.
It helps you create non-conflicting entries for each system.

BLS auto-parsing is planned.

[sinayion]

You are looking for limine-entry-tool as an extra tool that manages multiple boot entries across different distros. It helps you create non-conflicting entries for each system.

BLS auto-parsing is planned.

But that doesn't stop a random distribution update from overwriting another distro's kernel, especially if by default they both use vmlinuz as the name.

[Zesko]

As far as I know, limine-entry-tool supports using the machine-ID to isolate each distro. This helps avoid conflicts like overwriting kernels with the same name.

[sinayion]

As far as I know, limine-entry-tool supports using the machine-ID to isolate each distro. This helps avoid conflicts like overwriting kernels with the same name.

I just read the tool documentation, and it looks like it simply manages the boot entries that Limine shows on boot. This will not stop a new distro being installed from overwriting another distro's kernel. As in, there is no way this tool would stop the opnsuse Tumbleweed installer from doing so, for example, when booting an iso and installing the distro.

[Zesko]

Each systemd-based distro installer should generate a unique machine-id for every new installation.
This machine-id is used to isolate kernels and avoid conflicts.

If an OS installer runs limine-entry-tool --add, the tool will automatically generate a /etc/machine-id if not available before copying new kernel to $esp/$machine-id/$kernel-version/. AFAIK

This mechanism prevents file conflicts between different OS installations. This is the same as behavior as kernel-install for systemd-boot if you're familiar with how it works.