Arch Linux

It seems necessary also to mount rpc_pipefs on /var/lib/nfs/rpc_pipefs. Doing this, then starting idmapd makes NFSv4 work here!

please add the correct files here

Thanks Abel for your work because some months ago i try the same and have no success. My question is could it be that you have installed some other own packages too? On http://www.citi.umich.edu/projects/nfsv4/linux ther be listed libgssglue and librpcsecgss as requirements and without them ./configure (i '--disable-gss' with '--enable-nfsv4') fails with 'checking for RPCSECGSS... no'. After making my own packages for them both ./configure fails with 'checking for GSSAPI... configure: error: Package requirements (libgssapi >= 0.11)'. There is a big patch for nfs-utils but i don't know if it will helps.

Tthe packages are present but not the headers and all, so I indeed had to compile them myself.
I will to upload the needed packages to AUR, add the init scripts and a patch for the netfs init script (nfs4 is not in the list of mounted FSes) and add a howto on the wiki.
I compiled:
libgssglue, libgssapi, librpcsecgss and nfs-utils with --enable-gss.

When the work is done, I'll comment here again.

Your plan looks very nice, thanks again.
I found a way to compile nfs-utils by including this lines in the PKGBUILD first after 'build() {':
export GSSAPI_CFLAGS='-I/usr/include/gssglue'
export GSSAPI_LIBS='-lgssapi -ldl'
The problem is that the heimdal package has the libs and the gssapi.h but no pkgconfig file for it.

I've uploaded librpcsecgss, libgssglue and nfs4-utils to AUR.
I included an /etc/rc.d/nfs4-common init script in nfs4-utils starting the idmap and gss daemons.
I filed a bug for the netfs init script, for nfs4 is not in the list of automounted filesystems there.
A very minimal HOWTO is now on the wiki: http://wiki.archlinux.org/index.php/NFSv4.

To be continued.

Everything seems to be working now, except for the netfs init script that has yet to be fixed (http://bugs.archlinux.org/task/8509)
The wiki is improved as are the packages on AUR. Attila, would you be willing to test it?

It might even be a good idea to just add those features to nfs-utils: the nfs4-common init script, the /etc/idmapd.conf, the /etc/gssapi_mech.conf (from http://aur.archlinux.org/packages.php?do_Details=1&ID=13625) and rpc.gssd (with two additional dependencies, though:
libgssglue (http://aur.archlinux.org/packages.php?do_Details=1&ID=13629) and
librpcsecgss (http://aur.archlinux.org/packages.php?do_Details=1&ID=13630).
(And as the GSSAPI provided by heimdal includes no pkg-config entries, either those need to be added, or something similar to
export GSSAPI_CFLAGS='-I/usr/include/gssapi'
export GSSAPI_LIBS='-lgssapi -ldl'
to the PKGBUILD in order for nfs-utils to compile with GSS).

It seems rational to add NFSv4 support to ArchLinux by default, because of the advantages NFSv4 has over NFSv3: strong authentication and integrity via Kerberos and SPKM-3, improved performance, safe file caching, lock migration, ACLs and better support for Windows file sharing semantics.

Oh, if forgot to say that i have tested it with arch as client and opensuse 10.3 (in qemu) as server which works as described in your wiki. Perhaps another one could test arch as an nfs4 server. From my view, i don't see a reason which speak against to put the packages to community (or to core) and to append the suggested files to nfs-utils because nfs4 is optional so it shouldn't disturb in environments which wants to stay with nfs3.

What's the status of this issue?

It would be fine if NFSv4 was supported. It's boring to compile all the libgss stuff manually, then recompile nfs-utils and so forth...