Or systemd-boot as boot manager (not bootloader) to chainload the grubx64-efi for both of the installations.
Not sure, if it has a fs-driver for btrfs. - found it: wiki.archlinux.org/title/REFInd
I’m all set!! Once I reinstalled EOS with grub, I was able to enable the os-prober and it found my Kubuntu install. Time to get going! The hardest part will be remembering to log into Kubuntu once in a while to keep it up to date…
2 Likes
Sounds great!
I suggest to block your Kubuntu to update his grub! Kernel updates etc. included.
Don’t know for sure, how does it work there. Else you loose your EOS-config.
Good suggestion, I’ll look into how to do that although my BIOS saw Kubuntu and EOS separately, so I think maybe the grubs are totally independent?
I’m afraid, they are not independent.
In my Debian I use Synaptic and there I set everyting havin grub inside the name to ‘blocked’ - bang.
I have an SSD drive with 4 partitions, all ext4. sda1 (AntiX) handles all the Grub work, as its not going anywhere. To be honest, my EOS installs aren’t going anywhere either. I’ve had such a good time learning Arch. I was very appreciative during the EOS install it actually asked me if I wanted to install grub … that is awesome!
Sure, if ONLY ONE of the grub’s is the master, then it may work.
But all the others have to be quiet - very quiet…
Edit:
That’s the reason, I use refind and nothing else. But if it will handle btrfs?
2 Likes
Most probably, when the Grub in your Kubuntu gets an update, it will put itself on top of boot priority in BIOS. You would need to go in there and change back to EOS.
That is the ‘cheapest’ case.
In the past I have had sometimes overwritten and badly destroyed configs. They wrote across each other to absolute nonsense…
Thats the reason, I escaped from grub 
Sorry to hear that!
I have never had the experience of one Linux distro overwriting another ones boot files.
Dualbooting with Ubuntu, the “worst” thing happening was that it had the bad habit to change the boot priority in BIOS. Never overwriting things.
That’s at least in my experience. Every setup, every config and every person between keyboard and chair are different.
Well, I’ve grown more careful then. And it is some time gone now, maybe newer versions work better.
But if some hickups occur and I get bumped to the grub commandline and the friendly ‘e’ - I am not amused…
Now every machine here starts using rEFInd, it uses simple text-configs, well documented.
And if the whole boot-machine has gotten scrambled, I can use a rEFInd-boot-stick to bring it up again and put it back onto the feet.
I think, the grub-dev’s have Win + 1x Linux in mind, that may work well. But here is no Win, therfore 2-5 differnt Linux per machine and the rEFInd works very well, all in ext4.
I’ll have to look into it to see if it supports btrfs. Then maybe I’ll try to switch if I feel like I can do it without ruining my new setup lol
This is how I multiboot my systems, each with its own Grub.
Look at the ArchWiki article. Simple set up with no extra piece of software involved. systemd-boot is already part of the systemd.
1 Like
You don’t need to touch anything.
If you really find support for btrfs (fs-driver for reading the partition), you may build an usb-stick and try a simple boot. Should work without anything else.
If you really like it - install from EOS via pacman.
Welcome to the community!
I started using Linux with Ubuntu 8.04, and used it as my daily driver until 2019 when I switched back to Windows for a time (work stuff). Around last year I gave EndeavourOS a try and have been happy since.
Why did I change?
I found that Ubuntu really got “in the way”. I was an experienced enough user and had my own preferences and found that I just spent more and more time re-configuring my system after each LTS release.
I had used Arch before, and was happy with pacman, but for some reason I never wanted to make the switch. I gave Endeavour a try, and was beyond pleased with the performance of my old laptop, and with how easy it was to customize. I look at Endeavour as using Arch without the hassle, and have been happy using it across my laptop and desktop for the past year and a half.
I have rarely had any issues at all, and when I have I have been comfortable asking the community for support. No more broken PPAs, no more snapd, no more replacing the DE,
1 Like