Arch Linux

Description:
I'm just curious what the rationale is for passing "--no-nfs-version 2" to mountd by default (see [1]). I'm guessing that someone thought that meant NFS2 shares, but it really refers to the NFS MOUNT protocol, used by NFSv2 [2] and NFSv3 [3]. (I don't think NFSv4 uses the MOUNT protocol [4], but I could be wrong).

Not supporting MOUNT v2 prevents some stupid clients (like my Boxee Box) from being able to mount NFS shares, and as far as I can tell it doesn't break compatibility with newer versions of NFS (v4) to turn it on.

Additional info:
* package version(s): nfs-utils 1.2.5-1
* config file: /etc/conf.d/nfs-server.conf

Steps to reproduce:

0) Install nfs-utils with the default configuration
1) start mountd by starting nfs-server
# rc.d start nfs-server
2) observe that the only supported "program number", as advertised by rpcbind, for mountd is `3'
# rpcinfo -p
3) On a remote host, mount some NFS shares exported by this server (even some NFS4 shares)
4) Remove "--no-nfs-version 2" from MOUNTD_OPTS in /etc/conf.d/nfs-server.conf
5) Restart mountd by restarting nfs-server
# rc.d restart nfs-server
6) Repeat step 2, observing that we're now supporting NFS MOUNTD version 2 in addition to version 3
7) Repeat step 3. Note that you are still able to mount NFS4 shares

Possible Fixes:
- Explain to me why that option is there :).
- Remove it

[1] http://projects.archlinux.org/svntogit/packages.git/tree/trunk/nfs-server.conf?h=packages/nfs-utils#n21
[2] http://tools.ietf.org/html/rfc1094#page-23
[3] http://tools.ietf.org/html/rfc1813#page-106
[4] http://tools.ietf.org/html/rfc3530#section-4.1