| Alexey Dobriyan | 97afe47 | 2009-01-22 11:07:41 +0300 | [diff] [blame] | 1 | config NFS_FS |
| 2 | tristate "NFS client support" |
| Randy Dunlap | dd4dc82 | 2009-05-12 13:28:09 -0700 | [diff] [blame] | 3 | depends on INET && FILE_LOCKING |
| Alexey Dobriyan | 97afe47 | 2009-01-22 11:07:41 +0300 | [diff] [blame] | 4 | select LOCKD |
| 5 | select SUNRPC |
| 6 | select NFS_ACL_SUPPORT if NFS_V3_ACL |
| 7 | help |
| 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 |
| 11 | will be called nfs. |
| 12 | |
| 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. |
| 19 | |
| 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. |
| 23 | |
| 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 |
| 28 | module in this case. |
| 29 | |
| 30 | If unsure, say N. |
| 31 | |
| 32 | config NFS_V3 |
| 33 | bool "NFS client support for NFS version 3" |
| 34 | depends on NFS_FS |
| 35 | help |
| 36 | This option enables support for version 3 of the NFS protocol |
| 37 | (RFC 1813) in the kernel's NFS client. |
| 38 | |
| 39 | If unsure, say Y. |
| 40 | |
| 41 | config NFS_V3_ACL |
| 42 | bool "NFS client support for the NFSv3 ACL protocol extension" |
| 43 | depends on NFS_V3 |
| 44 | help |
| 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. |
| 51 | |
| 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. |
| 55 | |
| 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 |
| 59 | ACL protocol. |
| 60 | |
| 61 | If unsure, say N. |
| 62 | |
| 63 | config NFS_V4 |
| Trond Myklebust | b3edc2b | 2010-08-04 14:38:01 -0400 | [diff] [blame] | 64 | bool "NFS client support for NFS version 4" |
| 65 | depends on NFS_FS |
| Trond Myklebust | 827e345 | 2010-09-12 19:57:50 -0400 | [diff] [blame] | 66 | select SUNRPC_GSS |
| Alexey Dobriyan | 97afe47 | 2009-01-22 11:07:41 +0300 | [diff] [blame] | 67 | help |
| 68 | This option enables support for version 4 of the NFS protocol |
| 69 | (RFC 3530) in the kernel's NFS client. |
| 70 | |
| 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/. |
| 74 | |
| Trond Myklebust | b3edc2b | 2010-08-04 14:38:01 -0400 | [diff] [blame] | 75 | If unsure, say Y. |
| Alexey Dobriyan | 97afe47 | 2009-01-22 11:07:41 +0300 | [diff] [blame] | 76 | |
| Ricardo Labiaga | 1efae38 | 2009-04-01 09:21:46 -0400 | [diff] [blame] | 77 | config NFS_V4_1 |
| Trond Myklebust | 3dce9a5 | 2010-08-04 14:39:16 -0400 | [diff] [blame] | 78 | bool "NFS client support for NFSv4.1 (EXPERIMENTAL)" |
| Fred Isaman | 02c35fc | 2010-10-20 00:17:59 -0400 | [diff] [blame] | 79 | depends on NFS_FS && NFS_V4 && EXPERIMENTAL |
| 80 | select PNFS_FILE_LAYOUT |
| Ricardo Labiaga | 1efae38 | 2009-04-01 09:21:46 -0400 | [diff] [blame] | 81 | help |
| 82 | This option enables support for minor version 1 of the NFSv4 protocol |
| Fred Isaman | 02c35fc | 2010-10-20 00:17:59 -0400 | [diff] [blame] | 83 | (RFC 5661) in the kernel's NFS client. |
| Ricardo Labiaga | 1efae38 | 2009-04-01 09:21:46 -0400 | [diff] [blame] | 84 | |
| Trond Myklebust | 3dce9a5 | 2010-08-04 14:39:16 -0400 | [diff] [blame] | 85 | If unsure, say N. |
| Ricardo Labiaga | 1efae38 | 2009-04-01 09:21:46 -0400 | [diff] [blame] | 86 | |
| Fred Isaman | 02c35fc | 2010-10-20 00:17:59 -0400 | [diff] [blame] | 87 | config PNFS_FILE_LAYOUT |
| 88 | tristate |
| 89 | |
| Alexey Dobriyan | 97afe47 | 2009-01-22 11:07:41 +0300 | [diff] [blame] | 90 | config ROOT_NFS |
| 91 | bool "Root file system on NFS" |
| 92 | depends on NFS_FS=y && IP_PNP |
| 93 | help |
| 94 | If you want your system to mount its root file system via NFS, |
| 95 | choose Y here. This is common practice for managing systems |
| 96 | without local permanent storage. For details, read |
| J. Bruce Fields | dc7a081 | 2009-10-27 14:41:35 -0400 | [diff] [blame] | 97 | <file:Documentation/filesystems/nfs/nfsroot.txt>. |
| Alexey Dobriyan | 97afe47 | 2009-01-22 11:07:41 +0300 | [diff] [blame] | 98 | |
| 99 | Most people say N here. |
| David Howells | 3b9ce97 | 2009-04-03 16:42:42 +0100 | [diff] [blame] | 100 | |
| 101 | config NFS_FSCACHE |
| Christian Kujau | 4912002 | 2010-02-26 17:25:14 +0000 | [diff] [blame] | 102 | bool "Provide NFS client caching support" |
| David Howells | 3b9ce97 | 2009-04-03 16:42:42 +0100 | [diff] [blame] | 103 | depends on NFS_FS=m && FSCACHE || NFS_FS=y && FSCACHE=y |
| 104 | help |
| 105 | Say Y here if you want NFS data to be cached locally on disc through |
| 106 | the general filesystem cache manager |
| Bryan Schumaker | c2e8139 | 2010-08-11 09:37:53 +0100 | [diff] [blame] | 107 | |
| 108 | config NFS_USE_LEGACY_DNS |
| 109 | bool "Use the legacy NFS DNS resolver" |
| 110 | depends on NFS_V4 |
| 111 | help |
| 112 | The kernel now provides a method for translating a host name into an |
| 113 | IP address. Select Y here if you would rather use your own DNS |
| 114 | resolver script. |
| 115 | |
| 116 | If unsure, say N |
| 117 | |
| 118 | config NFS_USE_KERNEL_DNS |
| 119 | bool |
| 120 | depends on NFS_V4 && !NFS_USE_LEGACY_DNS |
| 121 | select DNS_RESOLVER |
| Steve French | 3f43231 | 2010-08-12 18:16:45 +0000 | [diff] [blame] | 122 | select KEYS |
| Bryan Schumaker | c2e8139 | 2010-08-11 09:37:53 +0100 | [diff] [blame] | 123 | default y |
| Bryan Schumaker | 955a857 | 2010-09-29 15:41:49 -0400 | [diff] [blame] | 124 | |
| 125 | config NFS_USE_NEW_IDMAPPER |
| 126 | bool "Use the new idmapper upcall routine" |
| 127 | depends on NFS_V4 && KEYS |
| 128 | help |
| 129 | Say Y here if you want NFS to use the new idmapper upcall functions. |
| 130 | You will need /sbin/request-key (usually provided by the keyutils |
| 131 | package). For details, read |
| 132 | <file:Documentation/filesystems/nfs/idmapper.txt>. |
| 133 | |
| 134 | If you are unsure, say N. |