fs/nfs/Kconfig v3.0-rc7

NFS_FS

NFS client support

Choose Y here if you want to access files residing on other
computers using Sun's Network File System protocol.  To compile
this file system support as a module, choose M here: the module
will be called nfs.

To mount file systems exported by NFS servers, you also need to
install the user space mount.nfs command which can be found in
the Linux nfs-utils package, available from http://linux-nfs.org/.
Information about using the mount command is available in the
mount(8) man page.  More detail about the Linux NFS client
implementation is available via the nfs(5) man page.

Below you can choose which versions of the NFS protocol are
available in the kernel to mount NFS servers.  Support for NFS
version 2 (RFC 1094) is always available when NFS_FS is selected.

To configure a system which mounts its root file system via NFS
at boot time, say Y here, select "Kernel level IP
autoconfiguration" in the NETWORK menu, and select "Root file
system on NFS" below.  You cannot compile this file system as a
module in this case.

If unsure, say N.

NFS_V3

NFS client support for NFS version 3

This option enables support for version 3 of the NFS protocol
(RFC 1813) in the kernel's NFS client.

If unsure, say Y.

NFS_V3_ACL

NFS client support for the NFSv3 ACL protocol extension

Some NFS servers support an auxiliary NFSv3 ACL protocol that
Sun added to Solaris but never became an official part of the
NFS version 3 protocol.  This protocol extension allows
applications on NFS clients to manipulate POSIX Access Control
Lists on files residing on NFS servers.  NFS servers enforce
ACLs on local files whether this protocol is available or not.

Choose Y here if your NFS server supports the Solaris NFSv3 ACL
protocol extension and you want your NFS client to allow
applications to access and modify ACLs on files on the server.

Most NFS servers don't support the Solaris NFSv3 ACL protocol
extension.  You can choose N here or specify the "noacl" mount
option to prevent your NFS client from trying to use the NFSv3
ACL protocol.

If unsure, say N.

NFS_V4

NFS client support for NFS version 4

This option enables support for version 4 of the NFS protocol
(RFC 3530) in the kernel's NFS client.

To mount NFS servers using NFSv4, you also need to install user
space programs which can be found in the Linux nfs-utils package,
available from http://linux-nfs.org/.

If unsure, say Y.

NFS_V4_1

NFS client support for NFSv4.1 (EXPERIMENTAL)

This option enables support for minor version 1 of the NFSv4 protocol
(RFC 5661) in the kernel's NFS client.

If unsure, say N.

PNFS_OBJLAYOUT

Provide support for the pNFS Objects Layout Driver for NFSv4.1 pNFS (EXPERIMENTAL)

Say M here if you want your pNFS client to support the Objects Layout Driver.
Requires the SCSI osd initiator library (SCSI_OSD_INITIATOR) and
upper level driver (SCSI_OSD_ULD).

If unsure, say N.

ROOT_NFS

Root file system on NFS

If you want your system to mount its root file system via NFS,
choose Y here.  This is common practice for managing systems
without local permanent storage.  For details, read
<file:Documentation/filesystems/nfs/nfsroot.txt>.

Most people say N here.

NFS_FSCACHE

Provide NFS client caching support

Say Y here if you want NFS data to be cached locally on disc through
the general filesystem cache manager

NFS_USE_LEGACY_DNS

Use the legacy NFS DNS resolver

The kernel now provides a method for translating a host name into an
IP address.  Select Y here if you would rather use your own DNS
resolver script.

If unsure, say N

NFS_USE_NEW_IDMAPPER

Use the new idmapper upcall routine

Say Y here if you want NFS to use the new idmapper upcall functions.
You will need /sbin/request-key (usually provided by the keyutils
package).  For details, read
<file:Documentation/filesystems/nfs/idmapper.txt>.

If you are unsure, say N.