I always thought too many choices makes it harder? 
1 Like
4 Likes
We are not talking about offering 15 different filesystem choices. The difference between 2 and 3 choices does not seem to complicate matters. If eliminating complication were the primary goal, take away all choice. I cannot foresee needing anything more than ext4 can provide, so to me, why offer anything else? But some seem to think btrfs justifies adding a choice. By that logic, adding xfs as a choice makes just as much sense.
It probably depends who you are.
I have never really understood the âI want less optionsâ crowd but there are definitely a portion of the population that feel that way.
2 Likes
Perhaps a good idea 
A Poll, Soviet style:
- ext4
- btrfs (really, just another vote for ext4)
- xfs (really, just another vote for ext4)
- jfs (really, just another vote for ext4)
- f2fs (really, just another vote for ext4)
- reiserfs (just ext4, but gets you a first class ticket to Siberia)
3 Likes
My only objection is that XFS needs some specialist setup IF grub is not used - other than that it makes no difference. As grub is our default, I wonât complain that much 
Just an extra step to add to the wiki entries on rEFInd and systemd boot etcâŚ
Afaik, Calamares only allows grub anyway, right?
AFAIK, true. It is certainly setup that way ATM. This is only for those planning to dump it later - or that wonder about the alternatives⌠it could mean a re-install to make the changes, as most wonât have broken /boot out separately on the original install. Shouldnât come up that often, thoughâŚ
systemd-boot doesnât have any special requirements for xfs or any other filesystem as far as I know.
I think what you are thinking about is the fact that refind needs a driver for it. But that is a limitation of refind as far as I know.
No. Calamares supports grub and systemd-boot in the bootloader module and I believe there is support for refind in an extramodule.
1 Like
I havenât done enough with systemd-boot to be sure - but how would it read the boot files? No drivers loaded at that point, right? Wouldnât go on f2fs it seems⌠but insufficient experience here!
It appears that grub is the only option for legacy mbr booting, but for EFI, systemd-boot is available.
Even so, for any choice in bootloaders would require multiple possible partition.conf files to support whichever choice is made by the user and adjust the ESP mount point.
With systemd-boot, the kernels and initram must be in the efi partition so it will never be anything except vfat/fat32.
When you donât have a choice thatâs the same as giving one option. Not a choice as itâs already made for you. Having a second option is a choice. Have 3 options is another choice. Having too many choices is also a problem. Iâm not suggesting 3 is too many choices. Iâm just saying too many choices for some people doesnât help.
Edit: Iâm okay with having xfs. But i also say itâs just as easy to have xfs using manual partitioning or setting the default in Calamares to xfs.
There is always the choice to do manual partitioning and have ultimate control 
That was interesting!
Is it just to change:
efiBootLoader: "grub"
to:
efiBootLoader: "systemd-boot"
in
bootloader.conf ?
# SPDX-FileCopyrightText: no
# SPDX-License-Identifier: CC0-1.0
#
# bootloader configurations
---
efiBootLoader: "grub"
kernel: "/vmlinuz-linux"
img: "/initramfs-linux.img"
fallback: "/initramfs-linux-fallback.img"
timeout: "5"
efiBootloaderId: "endeavouros"
grubInstall: "grub-install"
grubMkconfig: "grub-mkconfig"
grubCfg: "/boot/grub/grub.cfg"
grubProbe: "grub-probe"
efiBootMgr: "efibootmgr"
installEFIFallback: true
Do the other lines related to grub need to be commented out as well?
I suspect that there is more to this but I think itâs nice option to get a systemd-boot right at the outset.
Edit: These lines also seem to be related to systemd-boot in Calamaresâ bootloader.conf:
# systemd-boot configuration files settings, set kernel and initramfs file names
# and amount of time before default selection boots
kernel: "/vmlinuz-linux"
img: "/initramfs-linux.img"
fallback: "/initramfs-linux-fallback.img"
timeout: "10"
A few things more than that.
In the current version of Calamares you also need to change the kernel and initramfs locations in bootloader.conf. You also need to change efiSystemPartition and probably efiSystemPartitionSize in partition.conf
2 Likes
I suspected so 
Thanks for the hints! It feels to be a bit out of my reach but I will definitely will have a look at it.
Just having a look at the Calamaresâ bootloader over at Github I couldnât see immediately where I could specify the location of the kernels and initramfs. Are the lines I posted above related to this by any chance?
Already scheduled a fresh install!
