On 02/27/2018 03:49 PM, NeilBrown wrote: > On Tue, Feb 27 2018, Steve Dickson wrote: >> Question, do packages like glibc have these types of policies? > > glibc documents in README the minimum kernel version. > In Apr 2014 it was raised to 2.6.32. > In Map 2017 it was raised to 3.2 > Though some archs have different rules > git grep arch_minimum_kernel sysdeps > in the glibc source. > > systemd also sets a minimum, currently: > REQUIREMENTS: > Linux kernel >= 3.13 > Linux kernel >= 4.2 for unified cgroup hierarchy support > > according to README. > > So if we want to require 3.5 or later, then I have not problem with > that. > I just think it should be clearly announced in the git commit, and > documented in a README or similar. Thanks for pointing this out... I'm thinking we should probably create this kernel requirement once the option is deprecated... Since the precedent has already been set to check the kernel version in the mounting code, I'm going to use that to fix the bug, so I can back port the fix to other releases... Again, thanks for the info and the suggestions! steved. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
