Dumb partitioning by Calamares on a system with separate disks for Linux and Windows

[chewykernel]

GeckoLinux_ROLLING_Plasma.x86_64-999.210519.0

On a laptop with disk 0 for Linux and disk 1 for Windows, partitioning during a default installation uses the existing EFI partition for Windows instead of creating its own EFI on the separate Linux disk. If this is how Calamares normally works it's a really bad idea. If it's not by design it must be a bug.

Users not paying attention could end up defeating one of the primary purposes of having separate disks for Linux and Windows.

Anyone dual booting GeckoLinux with Windows on separate disks will want to manually override the default partitioning scheme.

To remove GeckoLinux cleanly the Windows EFI partition needs to be accessed with diskpart and assigned a drive letter in order to delete the geckolinux EFI directory.

[geckolinux]

That's a valid observation. You might want to re-post it here, which appears to be a similar request:
calamares/calamares#1111

[chewykernel]

That appears to be the same issue. Obviously there hasn't been a change since the subject came up two years ago. It's a minor shortcoming as long as users are aware of it and how to get around it. Thanks for your reply.

[Daasin]

Would definitely love easier or 'dumb' partitioning like lvm isn't the difficult part but wanting to use a smaller EXT4 partition for the main one wasn't really ...well I just wasn't able to do it, even harder now that I can't change that while booted. Like a GUI tool that lets people shrink down to what's already written in the partition by dragging the sides. Or drag the whole partition left to right to keep the free "hidden" space at the end of the part table. Needed to use two different partition tools to do that in Windows without a restart 😬

[chewykernel]

GeckoLinux_ROLLING_Plasma.x86_64-999.210526.0

A fresh installation of this newer build turned out differently. The plan was to manually partition EFI with Gparted but that wasn't necessary. By default, Calamares selected the Linux disk for EFI and that's how it finished.

My memory may be off, but I could have sworn Calamares put EFI on the Linux disk during a Manjaro installation a few months back. Maybe my earlier complaint was premature and Calamares using the Windows EFI was just a temporary lark or even buggy NVMe firmware. Or if not that was a temporary snafu that got fixed. Whatever is the case, Gecko installed as expected today on a laptop with separate Linux and Windows disks.

[geckolinux]

Honestly not sure... thanks a lot for the report at any rate, I appreciate it.