2 tristate "NFS client support"
3 depends on INET && FILE_LOCKING
6 select NFS_ACL_SUPPORT if NFS_V3_ACL
8 Choose Y here if you want to access files residing on other
9 computers using Sun's Network File System protocol. To compile
10 this file system support as a module, choose M here: the module
13 To mount file systems exported by NFS servers, you also need to
14 install the user space mount.nfs command which can be found in
15 the Linux nfs-utils package, available from http://linux-nfs.org/.
16 Information about using the mount command is available in the
17 mount(8) man page. More detail about the Linux NFS client
18 implementation is available via the nfs(5) man page.
20 Below you can choose which versions of the NFS protocol are
21 available in the kernel to mount NFS servers. Support for NFS
22 version 2 (RFC 1094) is always available when NFS_FS is selected.
24 To configure a system which mounts its root file system via NFS
25 at boot time, say Y here, select "Kernel level IP
26 autoconfiguration" in the NETWORK menu, and select "Root file
27 system on NFS" below. You cannot compile this file system as a
33 bool "NFS client support for NFS version 3"
36 This option enables support for version 3 of the NFS protocol
37 (RFC 1813) in the kernel's NFS client.
42 bool "NFS client support for the NFSv3 ACL protocol extension"
45 Some NFS servers support an auxiliary NFSv3 ACL protocol that
46 Sun added to Solaris but never became an official part of the
47 NFS version 3 protocol. This protocol extension allows
48 applications on NFS clients to manipulate POSIX Access Control
49 Lists on files residing on NFS servers. NFS servers enforce
50 ACLs on local files whether this protocol is available or not.
52 Choose Y here if your NFS server supports the Solaris NFSv3 ACL
53 protocol extension and you want your NFS client to allow
54 applications to access and modify ACLs on files on the server.
56 Most NFS servers don't support the Solaris NFSv3 ACL protocol
57 extension. You can choose N here or specify the "noacl" mount
58 option to prevent your NFS client from trying to use the NFSv3
64 bool "NFS client support for NFS version 4"
68 This option enables support for version 4 of the NFS protocol
69 (RFC 3530) in the kernel's NFS client.
71 To mount NFS servers using NFSv4, you also need to install user
72 space programs which can be found in the Linux nfs-utils package,
73 available from http://linux-nfs.org/.
78 bool "NFS client support for NFSv4.1 (EXPERIMENTAL)"
79 depends on NFS_FS && NFS_V4 && EXPERIMENTAL
80 select SUNRPC_BACKCHANNEL
81 select PNFS_FILE_LAYOUT
83 This option enables support for minor version 1 of the NFSv4 protocol
84 (RFC 5661) in the kernel's NFS client.
88 config PNFS_FILE_LAYOUT
93 depends on NFS_FS && NFS_V4_1 && BLK_DEV_DM
98 depends on NFS_FS && NFS_V4_1 && SCSI_OSD_ULD
102 bool "Root file system on NFS"
103 depends on NFS_FS=y && IP_PNP
105 If you want your system to mount its root file system via NFS,
106 choose Y here. This is common practice for managing systems
107 without local permanent storage. For details, read
108 <file:Documentation/filesystems/nfs/nfsroot.txt>.
110 Most people say N here.
113 bool "Provide NFS client caching support"
114 depends on NFS_FS=m && FSCACHE || NFS_FS=y && FSCACHE=y
116 Say Y here if you want NFS data to be cached locally on disc through
117 the general filesystem cache manager
119 config NFS_USE_LEGACY_DNS
120 bool "Use the legacy NFS DNS resolver"
123 The kernel now provides a method for translating a host name into an
124 IP address. Select Y here if you would rather use your own DNS
129 config NFS_USE_KERNEL_DNS
131 depends on NFS_V4 && !NFS_USE_LEGACY_DNS
136 config NFS_USE_NEW_IDMAPPER
137 bool "Use the new idmapper upcall routine"
138 depends on NFS_V4 && KEYS
140 Say Y here if you want NFS to use the new idmapper upcall functions.
141 You will need /sbin/request-key (usually provided by the keyutils
142 package). For details, read
143 <file:Documentation/filesystems/nfs/idmapper.txt>.
145 If you are unsure, say N.