On 9/3/13 11:13 AM, Cristian Rodríguez wrote:
El 03/09/13 10:32, Jeff Mahoney escribió:
In practice, all that's required for those users to continue uninterrupted is to add the 'allow_unsupported=1' option to the btrfs module either on the kernel command line or /etc/modprobe.d. There is nothing inherently limiting to any openSUSE user with this practice. The features are all still in the code and available immediately just by setting a flag. It can even be done safely after module load or even after file systems that don't use the unsupported features have been mounted. I intend to introduce this functionality into openSUSE soon.
That's not gonna fly, I will fight that to death, please do not add enterprise crippling module parameters to openSUSE, it *really* does not belong there at all. that's absolutely insane.
That's not really the reaction I got when I posted exactly this question a few weeks ago. The reaction was, in fact, pretty split with a bunch of people appreciating that we share our opinion on the maturity of particular features so that they don't have to do the research themselves. As I said then, the point isn't to take away functionality from anyone. If we have the ability to enable it in YaST (with a warning) or do it automatically (with a warning) if the features are already enabled on an older file system, nobody's lost anything. The point is that it will prevent users from losing their file systems using a feature set that hasn't been well tested. It's great that you want to try features out that we don't consider safe yet. That's how we get bug reports that we can use to improve and further gauge the quality of a particular feature set. I just don't think that /all/ openSUSE users want to have that particular experience without knowing what's up beforehand. -Jeff -- Jeff Mahoney SUSE Labs