Within architect, is it possible to use systemd-boot with an encrypted root partition? I tried a week ago, but architect warned me that I would be leaving the installer without a bootloader. So I went back and installed grub.
The mistake you and others make is that when talking about SystemD, you are actually talking about a collection of tools that are meant to work together.
SystemD is not a single executable, it is rather a set of separate utils whom all do one thing on their own 
Otherwise you could say that âLinuxâ does everything on itâs own also 
1 Like
Gummiboot 
1 Like
Thatâs just the name of the tool which sd-boot is derived from.
Gummiboot/sd-boot is only one tool from the total collection named SystemDâŚ
Mhm!
But I prefer saying Gummiboot as it is prettier , and more amusing! 
Systemd-boot is a project built on top of Gummiboot!
Oh! Have a sweet little hug! 
2 Likes
Youâre right ⌠I for one had been perceiving it that way. 
Meanwhile the OP lacked to backup this statements with links to proof unfortunately.
And as an NVIDIA-GPU owner Iâd glady have some proof.
Also there is a lot of fanboyism in this topic.
See my reply here:
The only fanboy-ism i have is towards âLinuxâ, the rest is just personal preference of usage.
I never âtrashâ anything without arguments why i think itâs badâŚ
Iâm not so sure about that i checked 2 systemd âexecutableâ bootctl and systemctl they both are linked to a systemd-share library (donât remember the exact name). So yes itâs a set of tools but Iâm not sure they are so âindependentâ. Anyway donât think Iâm against systemd as itâs not the case.
[quote=âTriMoon, post:68, topic:32550, full:trueâ]
See my reply here:
I can not find what the English name of the fallacy is which you use here, but âyouâre evading the burden of proofâ.
Also âmy replies on the internetâ. Are you for real?
Why should I dig in your complete internet activity to figure out the proof? Do it yourself!
@RoestVrijStaal i know it can be hard to fully understand another language, but if you prefer it in dutch thatâs no problem for me eitherâŚ
Ik gaf openlijk toe dat er geen officiele referenties zijn waar mensen die dat als bewijs willen zien voor mijn claim, en gaf hen een optie om mijn uitingen op het internet te gebruiken als bewijs indien ze perse een referentie voor die claim willen.
Ik heb ook uitgelegd waarom ik die claim doe met argumentenâŚ
Dus stap af van die hoge paard ok? (want de grond is erg hard)
I hope itâs ok to have a multi-language response to clear mis-understandingâŚ
Do we agree that most âexecutablesâ are linked to the stdlib and thus in your p.o.v. they would also not count as âso independentâ?
We can, but it depends which logic is implemented in the systemd libraries⌠it could be a monolithic library with small executable around it. But itâs off topic and i donât have the details. And as Iâm not against systemd but also not to push systemd to replace all other tools⌠for me grub do the job⌠systemd-boot seems interesting but my opinion is that its ecosystem is like as Wayland not yet ready for mass adoption.
And i donât know the future⌠with how ARM gain into servers and begin in desktop⌠how will be the future i donât knowâŚ
1 Like
Thatâs the beauty of FOSS: No one knows where it is headed exactly, but we can make educated guesses right?
Thatâs why i didnât phrase it as Linux should or needs to switch to sd-boot, but rather made an educated guess that it would be moving towards itâŚ
And yes the whole Linux âOperating systemâ is tied to each other piece that makes the whole, no matter which distro one uses.
In fact every binary executable is using the library of the CPU it is meant for on assembly level
So saying that systemd is not so âindependentâ because it uses x/y/z library is not fair to any piece of software and only pollutes the notion of that softwareâŚ
Maybe you are not aware of it, but most linux distroâs already use SystemD. (Manjaro incl.)
Some use more pieces of it as others, but their main system already starts with Systemd, note i say âstartsâ not âbootsâ
Yes. Just choose /boot as mount point for your efi partition. Thatâs the simplest way to do it.
I was facing an issue with systemd-boot during my last install, i had selected /boot as mount point and installed boot loader when i was trying to complete the installation it was giving me message that boot loader is not installed, it tried few times then finally gave up and installed grub
Oh, your boot partition were nor flagged as boor and ESP!
my boot partition was flagged as /boot and i tried sd-boot when it didnât work then i changed the boot partition flag to /boot/efi and installed grub
Flagged is appending a specific byte that tells the BIOS to boot from this partition. 
That was exactly the problem I had.