You are not logged in.

#1 2016-04-16 17:18:39

teppergin
Member
Registered: 2016-04-16
Posts: 2

systemd-boot --> grub?

I'm UEFI and x86_64, and I'm sure there's an easy way to do this, but I'm scared.

I want to change my bootloader from systemd-boot to GRUB in order to make it easier to do a dual-boot of gentoo.

Am I going to have to dig out my arch install USB to do this, or can I do it right from my actual system?

How would I go about switching over?

Sorry if I'm being too "gimme answers now" for this forum. I can supply more info if needed, but I would imagine there is an easy and universal way to do this; I just can't find it anywhere.

Last edited by teppergin (2016-04-16 17:27:58)

Offline

#2 2016-04-16 18:05:03

stoatally
Member
Registered: 2016-04-15
Posts: 19

Re: systemd-boot --> grub?

If you're nervous about it, you can always recover your system using the arch install USB and reinstall systemd-boot. But to answer your question, you should just be able to uninstall systemd-boot and then follow the wiki for installing GRUB.

Offline

#3 2016-04-16 18:16:01

Scimmia
Fellow
Registered: 2012-09-01
Posts: 12,815

Re: systemd-boot --> grub?

No real need to uninstall systemd-boot. Just install grub and select it from the firmware's boot menu or set it as default.

Offline

#4 2016-04-16 18:46:32

teppergin
Member
Registered: 2016-04-16
Posts: 2

Re: systemd-boot --> grub?

Oh. The reason I was so scared was because I didn't realize how nicely GRUB and systemd-boot would play together. I thought maybe there would be fun bits where GRUB would overwrite systemd-boot, etc. I guess I didn't expect GRUB to be really friendly and confine itself to its own little spot in the ESP. Yet another example of how things "justwerk".

Thanks for giving me the nerve.

Offline

#5 2016-04-16 18:50:41

Scimmia
Fellow
Registered: 2012-09-01
Posts: 12,815

Re: systemd-boot --> grub?

People tend to overthink things with UEFI. It's really pretty straight forward, things like grub or systemd-boot are just programs. You tell the firmware which program to run, and it runs it.

It only starts being a problem when you have really bad implementations that decide to run what they want to regardless of what you tell them.

Offline

Board footer

Powered by FluxBB