On Sat, 17 Dec 2016 04:54:21 +0100 =?UTF-8?Q?Rapha=c3=abl_Halimi?= <raphael.hal...@gmail.com> wrote: > Please explain exactly in what way would my patch introduce > *incompatible* changes. It's *trivial*, it only adds a single option, > and a comment to hint that NFSv4 must be disabled in rpc.nfsd in > addition of rpc.mountd. Why do you deem this change as "incompatible"? > Just because of a single conffile prompt that would affect a minority > of users ?
Even worse, NFSv2 was silently disabled by default: http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commitdiff;h=6b4e4965a6b82e8d49cea1c0316b951ba4e9e83e Which broke every single one of my clients that require NFSv2. The RPCNFSDOPTS has STILL (inexplicably) not been implemented, despite the availability of a (working) patch: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738063 And don't even get me started on the systemd folly of wanting to get rid of /etc/defaults. The whole thing is getting ridiculous.
