On Tue, Apr 12, 2016 at 11:44:01AM +0400, John Frankish wrote: > > > Ref: > > > Beyond LinuxR From Scratch - Version 2016-04-10 > > > Chapter 15. Networking Programs > > > > > > NFS-Utils-1.3.3 > > > > > > Compiling with "--disable-nfsv4" has no effect: > > > > > > $ sudo mount.nfs -v localhost:/mnt/nfs nfs_test > > > ... > > > mount.nfs: trying text-based options > > > 'vers=4.2,addr=127.0.0.1,clientaddr=127.0.0.1' > > > > > I have seen the need to specify the version when mounting from a > > distro, but on the BLFS 7.9 machine I am currently using I compiled > > with --disable-gss --disable-nfsv4 --without-tcp-wrappers > > --disable-ipv6 and my nfs v3 mounts work fine using just 'nfs' as > > the fstype in /etc/fstab (and variously _netdev or noauto or > > noauto,user in the options). > > > This was mounting a share on the server from the server as a test using > nfs-utils-1.3.3 compiled as per blfs > > If the first thing tried is "vers=4.2", something would seem to be wrong? > > John It sounds wrong, but I have never tried that - call me old-fashioned, but I mount from a separate machine.
The mount program has beem mount.nfs4 for some time, so it does not surprise me that passing --disable-nfsv4 does not disable all of it. After a quick test running configure *without* disabling nfsv4, the configure fails because libnfsidmap is not present. So arguably the explanation could be more specific. I see that we mention a lot of optional dependencies: of those, I only build sqlite. I think I used to build libevent, but have you installed any of the other optional deps ? If so, perhaps they change how much of nfs4 gets built. ĸen -- This email was written using 100% recycled letters. -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
