Going back to this discussion, On Mon, Nov 30, 2015 at 01:46:15PM +0800, Qu Wenruo wrote: > To be honest, how many guys really unhappy with current default features > behavior *except* you?
Me too. Anand's summary matches my view of how we should do it: ". Do it at run time for the running kernel. Current. In the order of priority .. check sysfs, if not check kernel-version, if not use progs-version-based-defaults (original)." I understand that the the kernel version is not always reliable, but when we use it only as a fallback we know that at least kernel of this upstream version can mount the filesystem. And becase we can turn on additional features later this should not be a blocker. I disagree with your view that the weight should be put on the distro integrators. I've been packaging btrfs-progs for the SLES and openSUSE, several product lines with different kernels (upstream and backports). Keeping the features in sync with kernel started to be an issue with the first incompat feature that was different among the kernels. And we want change the defaults further. The main user bases that I take into account: * upstream community, ie. the latest stable version or the git version * older stable trees, ie. 3.2, 3.14 up to 4.1 * heavy backports to enterprise kernels, arbitrary base version My idea of the default behaviour is to be able to use latest btrfs-progs (released or git) on any of them and minimize possible damage. Ie. respect the running kernel and try to best detect the features. Besides ancient kernels and the 3.2 that's still in use, the sysfs based detection should work. > Or how many bug report in maillist/bugzilla is about that? > > Introducing a new feature matrix only to change the behavior to your flavor? > Isn't this what you called "bloated intelligence"? I'm not sure why you see the feature matrix getting more complicated. The testeres and developers know what features to turn on if desired, testing recent kernel with recent progs will do the right thing on itself. The rest of the user are supposed to just install and use it. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
