Multiboot with Win10, Ubuntu and Garuda?
by Snugbug from LinuxQuestions.org on (#5FHYE)
I would like to have a multi boot system with Win10, an Ubuntu or Debian based distro and Garuda Linux dr460nized (it is pronounced dragonized, just in case anybody is wondering).
All of them are 64bit on a UEFI computer.
Win10 and MX Linux ( = Debian based) are installed already and working fine.
Now I'd like to add Garuda Linux (see here, 1st picture), which is an Arch based distro with a customized KDE desktop.
But I'm not sure about the Grub installation, because I don't want to destroy anything that's already present on my computer, of course.
Where exactly does Garuda install Grub on a UEFI system, with an already existing EFI partition?
If Garuda creates its own folder, let's say /garuda or /arch or whatever it is called, I guess, it should be possible to boot into Garuda, delete the /garuda or /arch folder from the EFI partition and reinstall Grub by adding the following code to the Grub installation command, bacause, up to now, MX19.2 is the efi folder used by Grub:
Code:--bootloader-id=MX19.2Or I might use a SuperGrub stick, boot into MX Linux, delete the /MX19.2 folder from the EFI partition, reinstall Grub, creating a neutral folder (like this one for example: /linboot) by adding this code to the Grub install command:
Code:--bootloader-id=linbootMX Linux will be the default distro by then.
Then I boot into Garuda and reinstall Grub by adding the same bootloader-id code. Now Garuda is the default distro.
What are the chances for this to work like that? What do you think?
All of them are 64bit on a UEFI computer.
Win10 and MX Linux ( = Debian based) are installed already and working fine.
Now I'd like to add Garuda Linux (see here, 1st picture), which is an Arch based distro with a customized KDE desktop.
But I'm not sure about the Grub installation, because I don't want to destroy anything that's already present on my computer, of course.
Where exactly does Garuda install Grub on a UEFI system, with an already existing EFI partition?
If Garuda creates its own folder, let's say /garuda or /arch or whatever it is called, I guess, it should be possible to boot into Garuda, delete the /garuda or /arch folder from the EFI partition and reinstall Grub by adding the following code to the Grub installation command, bacause, up to now, MX19.2 is the efi folder used by Grub:
Code:--bootloader-id=MX19.2Or I might use a SuperGrub stick, boot into MX Linux, delete the /MX19.2 folder from the EFI partition, reinstall Grub, creating a neutral folder (like this one for example: /linboot) by adding this code to the Grub install command:
Code:--bootloader-id=linbootMX Linux will be the default distro by then.
Then I boot into Garuda and reinstall Grub by adding the same bootloader-id code. Now Garuda is the default distro.
What are the chances for this to work like that? What do you think?