This is bad UX. If I need to "fiddle with enough" on a problem that wasn't supposed to be a problem, it should be addressed.
By default, when using the automatic install process, /boot uses ext4 when it should be using btrfs instead, and when using the custom partitioning tool, it should allow me to use btrfs without it being a reason to failure.
On April 2, 2021 1:32:05 AM EDT, Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote:
On Thu, Apr 1, 2021 at 10:18 AM Proprietary Chrome-chan
<theevilskeleton@xxxxxxxxxxxxxxxxx> wrote:
Hi,
`/boot` can be used on btrfs. However, Anaconda forces me to use ext4 in that specific, when it shouldn't if you use btrfs.
I'd like to request allowing `/boot` to be used on btrfs.
You can do this in Custom partitioning, if you fiddle with it enough.
However... I recommend you create a 1-2G Btrfs boot outside of the
installer. The installer will let you assign it to the /boot mount
point without reformatting it.
The reason is it's better to use the 'mkfs.btrfs --mixed' option for
file systems of this size.
_______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
