rpcbind and nfs4
rpcbind and nfs4
Posted Sep 27, 2016 14:48 UTC (Tue) by josh (subscriber, #17465)Parent article: Systemd programming, 30 months later
Would it make sense to have separate distribution packages, one for nfs4 (which doesn't depend on the rpcbind package) and one for older versions of NFS (which does depend on rpcbind)? That would avoid needing to install rpcbind and its unit file and then mask them.
rpcbind and nfs4
Posted Sep 30, 2016 8:24 UTC (Fri)
by neilbrown (subscriber, #359)
[Link]
Posted Sep 30, 2016 8:24 UTC (Fri) by neilbrown (subscriber, #359) [Link]
It might, but think it solves a separate problem.
It important to be able to install a package but not activate it, so the ability to mask (or otherwise disable) and unwanted service that is nevertheless installed should remain.
It would be possible to have an 'nfsv4' package which provides most of the current NFS and doesn't require rpcbind, and then an 'nfs' package which requires 'nfsv4' and 'rpcbind' and adds rpc.statd and showmount (and maybe the nfsv3.ko and nfsv2.ko kernel modules). That should work, but I don't know how practically useful it would be.