When that new distro has a kernel change, most distros will automatically update its own grub.cfg file anyway. I can remove the backup custom entry when I next boot into Manjaro. Now that grub.cfg has been generated, when you next reboot, the custom entry in Manjaro boot for the new distro should be able to find and boot from grub.cfg file of that distro. If the grub package was not preinstalled, of course I install it first.
If grub package is already installed, I use the sudo update-grub or sudo grub-mkconfig -o /boot/grub/grub.cfg commands to generate the grub.cfg file in that distro.
I then examine the generated grub entry and copy it into my custom.cfg file as a backup initial entry, at the same time also creating the custom entry to seek out the grub.cfg file of that new distro. That will seek out and generate a grub menu entry for that distro in Manjaro's grub menu to enable me to boot into that new distro. For those, the first step after installation is to boot into Manjaro to update-grub. This does not mean that the grub package is not found on that distro, it just means it's not written onto its PBR. If you label each distro's partition with its own name, it's easy to have a custom entry to search for a distro by label instead of UUID number.įor those distros that don't allow you to install grub onto its PBR, I choose not to install grub as bootloader at all.
However, whenever any of my non-Manjaro installs has a kernel change/update, I don't have to boot into Manjaro to then update its grub, because in Manjaro I have custom grub entries (in /boot/grub/custom.cfg) that either chainload into the grub found on the PBR, or seek out the /boot/grub/grub.cfg file, of each of the other distros. Because I'm using MBR boot with Manjaro controlling grub, for MX and other distros that permit grub to be installed onto the partition boot record of the root partition, I install grub on the root of the distro in question.
0 kommentar(er)
