@alamahant,
Thks 4 ur support.
To my understanding [nfsv4] has strong implication because CONFIG_RPCSEC_GSS_KRB5 gets forced.
Since I want an off the shelf easy and quick solution for home network, I currently switched to nfsv3.
Code: Select all
emerge -pv net-fs/nfs-utils
These are the packages that would be merged, in reverse order:
Calculating dependencies.... done!
Dependency resolution took 14.68 s (backtrack: 0/20).
[ebuild R ] net-fs/nfs-utils-2.7.1::gentoo USE="-caps -junction -kerberos -ldap libmount nfsv3 -nfsv4 -sasl (-selinux) -tcpd uuid" 0 KiB
Code: Select all
rc-service nfs start
* Executing: /lib/rc/sh/openrc-run.sh /lib/rc/sh/openrc-run.sh /etc/init.d/nfs start
* Exporting NFS directories ... [ ok ]
* Starting NFS mountd ...
rpc.mountd: svc_tli_create: could not open connection for udp6
rpc.mountd: svc_tli_create: could not open connection for tcp6
rpc.mountd: svc_tli_create: could not open connection for udp6
rpc.mountd: svc_tli_create: could not open connection for tcp6
rpc.mountd: svc_tli_create: could not open connection for udp6
rpc.mountd: svc_tli_create: could not open connection for tcp6 [ ok ]
* Starting NFS daemon ... [ ok ]
* Starting NFS smnotify ... [ ok ]
Would be nice to get rid of these
Code: Select all
pc.mountd: svc_tli_create: could not open connection for [tp/ud]p6
Could be I later come back to [nfsv4] aiming to figure out how to have it working in a minimalist approach.
Thks 4 ur attention, interest & support
USE="-* ..." in /etc/portage/make.conf here, i.e. a countermeasure to portage implicit braces, belt & diaper paradigm
LT: "I've been doing a passable imitation of the Fontana di Trevi, except my medium is mucus. Sooo much mucus. "