to experiment, make sure you have:
- a recent 2.6 kernel on both client and server; newer is better. You might even
- want to use CITI's patch set from http://www.citi.umich.edu/projects/nfsv4/linux/ .
+ want to use CITI's patch set from http://www.citi.umich.edu/projects/nfsv4/linux/
+ on the server, and/or Trond Myklebust's patch set from http://client.linux-nfs.org/ .
- a recent enough version of nfs-utils on both client and server (you probably
have on at least one of them, since you're reading this file!).
- enabled idmapd on both sides (see /etc/default/nfs-common).
+ - The following lines in /etc/services on the client (if not, you will receive
+ the message "broken /etc/services" when starting rpc.gssd; this will usually
+ only happen if you upgrade netbase without letting it replace /etc/services
+ with the new version):
+
+ nfs 2049/tcp # Network File System
+ nfs 2049/udp # Network File System
The export structure might be a bit confusing if you're already familiar with
NFSv2 or NFSv3. The biggest difference is that you will need to export an explicit
autodetection fails).
If you use "gss/krb5i", you will also get integrity (ie. authentication), and
-with "gss/krb5p", you'll also get privacy (ie. encryption). Make sure your
+with "gss/krb5p", you'll also get privacy (ie. encryption). Make sure your
kernel supports this; not all kernels do.
- -- Steinar H. Gunderson <sesse@debian.org>, Wed, 06 Sep 2006 00:32:38 +0200
+ -- Steinar H. Gunderson <sesse@debian.org>, Wed, 11 Oct 2006 15:18:03 +0200