Unless somebody's created an /etc/nfs.conf file, we should assume they're still using /etc/sysconfig/nfs. That shouldn't be difficult, and I don't see why we can't do that indefinitely. The goal should definitely be not to break any working setups on upgrade. --b. On Mon, Jan 16, 2017 at 03:11:38PM -0500, Steve Dickson wrote: > Hello, > > The latest nfs-utils release drastically changes how the NFS > servers are configured, for the good IMHO... > > All daemon configuration now goes through /etc/nfs.conf. > See nfs.conf(5) for details. > > The command line interfaces in the systemd services files > have been removed. Which means all your current configures > will break, because the variables in /etc/sysconfig/nfs are > no longer used. > > Again, I think is a move in the right direction and I know > you might find this surprising 8-) but I really don't want to > break all the current server configuration. So I'm trying t > o figure out how to do this with least amount of impact. > > Here is what I see as the options > > 1) Upgrade rawhide w/out a backward compatible patch > (since it is so early in the release cycle) > Upgrade f25 with an backwards compatible patch > > 2) Upgrade rawhide and f25 with the backward compatible > patch... but we have to ween ourselves of the command > line interface at some point... > > 3) Do nothing and push everything into f27, which is the least > favorite option. > > I'm leaning toward option 1... but I'm asking... so I'm listening. :-) > > Also, how do I documented something like this? > > tia, > > steved. > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
