https://bugzilla.suse.com/show_bug.cgi?id=1203027 https://bugzilla.suse.com/show_bug.cgi?id=1203027#c6 --- Comment #6 from Richard Brown <rbrown@suse.com> --- (In reply to Ancor Gonzalez Sosa from comment #4)

With the current implementation of libstorage-ng, the mount point of a subvolume is always auto-calculated from the mount point of the file-system and the path of the subvolume.

Am I totally mis-remembering stuff but isn't there a general over-arching philosophy with YaST that when there is something auto-calculated or auto-decided by YaST, there should be some way of correcting any mistakes/unwanted decisions made there? Isn't that why the Installation Summary screen lets you review everything YaST is doing before the install starts? The fact that YaST is auto-calculating mount points for subvolumes and not giving users a chance to correct any mistakes and/or set mount points for any additional subvolumes sure still feels like a bug to me that runs counter to how we typically do everything else in YaST... -- You are receiving this mail because: You are on the CC list for the bug.