+ btrfs driver is now built-in to the kernel, rather than as a module
Classic .. from frying pan to open fire.
Why the heck dist kernel cannot be without ANY fs support? I've been using such a kernel (sic!) 15y ago !!!
Why is it still automonter hardcoded into the kernel even if it is completely useless on a typical single workstation?
(which is still probably most of the cases when Fedora is used now).
Currently dracut can generate initrd with loading correct root fs module and even block layer (nvme/sata) or network layer network card module if boot is done with loading by grub kernel and initrd over network on using NFS on root fs.
Why do people who choose other FSess like xfs or ext4 or even f2fs for some embedded systems are forced to have wasted available small memory footprint by things which can be loaded as modules on demand?
Only because with such a kernel it could not be possible to say that Fedora is supporting btrfs as default fs? (and buy this it would make all those talks about default fs obsolete?).
Why Fedora cannot have only btrfs as default proposed by anaconda/kickstart FS?
kloczek
--