Okay, here’s a point I want to modify about the installation.
Right now the only main detail I want to correct is how it’s auto partitioning on Erase Disk, and with Encryption enabled. This, currently, with btrfs and grub as the choices involved in the actual disk setup, causes encryption to do even /boot which requires grub2 itself to decrypt the LUKS volume before even presenting a boot loader menu from grub.
I… don’t want grub to have to decrypt the bootloader, which is very slow, but instead, to decrypt as it’s booting the system itself.
I don’t believe Calamares supports this via automatic partitioning. It either encrypts everything or nothing. You need to use manual partitioning which is what you are probably trying to avoid.
Yeah, manual partitioning doesn’t allow the proper setup of btrfs volumes as Calamares doesn’t support it. But I swear I’ve seen Calamares installations before where /boot itself was not encrypted with everything, I’m 100% certain of this.
What do you mean? This should be supported in manual partitioning.
The only way that is possible in Calamares is to mount the ESP on /boot. However, our fork of Calamares doesn’t support that. At least, not easily.(It is technically possible if you inject custom python modules)
What do you mean? This should be supported in manual partitioning.
Calamares doesn’t support the creation, modification, or deletion of any subvolumes, or mounting these subvolumes where they belong. Never has, to-date.
Okay! Now THAT I did not know! So my previous work, despite being different, still applies to the subvolume structure itself! This is great actually. I tried it. It did not get the endeavouros grub theme applied, but… I am quite okay with the results!
