Description of problem: Context is Manual Partitioning > "Click here to create them automatically"; for both Btrfs and LVM Thin Provisioning partitioning schemes. Currently root mount point combines /var, /etc, /usr. This lacks sufficient granularity for snapshot and rollback. A rollback of root forces discontinuity in system settings and especially the journal and logs which probably should never be rolled back. By splitting out usr, it can be deployed, snapshot/rolled back independently of var and etc. It's also useful for improving statelessness of systems to enable "refresh" and "reset" type operations; and for read-only usr. Version-Release number of selected component (if applicable): anaconda-22.20.4 How reproducible: Always Additional info: - The suggested enhancement applies Btrfs and LVM thin partition schemes. The main (only?) disadvantage applying it to other schemes is some wasted space. - yum, dnf and systemd-offline updates (via GNOME Software) succeed with this configuration; tested on F21 and F22. - fedup upgrades need more testing once other bugs are fixed https://bugzilla.redhat.com/show_bug.cgi?id=1185604 https://bugzilla.redhat.com/show_bug.cgi?id=1185726 - Will post this bug on the ostree list.
This isn't useful to do for an ostree-based install, but no objections from me to supporting it for BTRFS. I'd say LVM-thin is a separate discussion though, because making /usr a separate volume is a major change for the admin experience from non-thin LVM. (Whereas we know btrfs is a major change regardless, so defaulting to /usr subvolume there, eh...it's just another change).
Users are free to create the layouts they need, doing so automatically could lead to confusion. Use custom or kickstart to create the layout you want.