| 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 | 
| Alexey Dobriyan | 97afe47 | 2009-01-22 11:07:41 +0300 | [diff] [blame] | 66 | 	help | 
 | 67 | 	  This option enables support for version 4 of the NFS protocol | 
 | 68 | 	  (RFC 3530) in the kernel's NFS client. | 
 | 69 |  | 
 | 70 | 	  To mount NFS servers using NFSv4, you also need to install user | 
 | 71 | 	  space programs which can be found in the Linux nfs-utils package, | 
 | 72 | 	  available from http://linux-nfs.org/. | 
 | 73 |  | 
| Trond Myklebust | b3edc2b | 2010-08-04 14:38:01 -0400 | [diff] [blame] | 74 | 	  If unsure, say Y. | 
| Alexey Dobriyan | 97afe47 | 2009-01-22 11:07:41 +0300 | [diff] [blame] | 75 |  | 
| Ricardo Labiaga | 1efae38 | 2009-04-01 09:21:46 -0400 | [diff] [blame] | 76 | config NFS_V4_1 | 
| Trond Myklebust | 3dce9a5 | 2010-08-04 14:39:16 -0400 | [diff] [blame] | 77 | 	bool "NFS client support for NFSv4.1 (EXPERIMENTAL)" | 
| Ricardo Labiaga | 1efae38 | 2009-04-01 09:21:46 -0400 | [diff] [blame] | 78 | 	depends on NFS_V4 && EXPERIMENTAL | 
 | 79 | 	help | 
 | 80 | 	  This option enables support for minor version 1 of the NFSv4 protocol | 
 | 81 | 	  (draft-ietf-nfsv4-minorversion1) in the kernel's NFS client. | 
 | 82 |  | 
| Trond Myklebust | 3dce9a5 | 2010-08-04 14:39:16 -0400 | [diff] [blame] | 83 | 	  If unsure, say N. | 
| Ricardo Labiaga | 1efae38 | 2009-04-01 09:21:46 -0400 | [diff] [blame] | 84 |  | 
| Alexey Dobriyan | 97afe47 | 2009-01-22 11:07:41 +0300 | [diff] [blame] | 85 | config ROOT_NFS | 
 | 86 | 	bool "Root file system on NFS" | 
 | 87 | 	depends on NFS_FS=y && IP_PNP | 
 | 88 | 	help | 
 | 89 | 	  If you want your system to mount its root file system via NFS, | 
 | 90 | 	  choose Y here.  This is common practice for managing systems | 
 | 91 | 	  without local permanent storage.  For details, read | 
| J. Bruce Fields | dc7a081 | 2009-10-27 14:41:35 -0400 | [diff] [blame] | 92 | 	  <file:Documentation/filesystems/nfs/nfsroot.txt>. | 
| Alexey Dobriyan | 97afe47 | 2009-01-22 11:07:41 +0300 | [diff] [blame] | 93 |  | 
 | 94 | 	  Most people say N here. | 
| David Howells | 3b9ce97 | 2009-04-03 16:42:42 +0100 | [diff] [blame] | 95 |  | 
 | 96 | config NFS_FSCACHE | 
| Christian Kujau | 4912002 | 2010-02-26 17:25:14 +0000 | [diff] [blame] | 97 | 	bool "Provide NFS client caching support" | 
| David Howells | 3b9ce97 | 2009-04-03 16:42:42 +0100 | [diff] [blame] | 98 | 	depends on NFS_FS=m && FSCACHE || NFS_FS=y && FSCACHE=y | 
 | 99 | 	help | 
 | 100 | 	  Say Y here if you want NFS data to be cached locally on disc through | 
 | 101 | 	  the general filesystem cache manager | 
| Bryan Schumaker | c2e8139 | 2010-08-11 09:37:53 +0100 | [diff] [blame] | 102 |  | 
 | 103 | config NFS_USE_LEGACY_DNS | 
 | 104 | 	bool "Use the legacy NFS DNS resolver" | 
 | 105 | 	depends on NFS_V4 | 
 | 106 | 	help | 
 | 107 | 	  The kernel now provides a method for translating a host name into an | 
 | 108 | 	  IP address.  Select Y here if you would rather use your own DNS | 
 | 109 | 	  resolver script. | 
 | 110 |  | 
 | 111 | 	  If unsure, say N | 
 | 112 |  | 
 | 113 | config NFS_USE_KERNEL_DNS | 
 | 114 | 	bool | 
 | 115 | 	depends on NFS_V4 && !NFS_USE_LEGACY_DNS | 
 | 116 | 	select DNS_RESOLVER | 
| Steve French | 3f43231 | 2010-08-12 18:16:45 +0000 | [diff] [blame] | 117 | 	select KEYS | 
| Bryan Schumaker | c2e8139 | 2010-08-11 09:37:53 +0100 | [diff] [blame] | 118 | 	default y | 
| Bryan Schumaker | 955a857 | 2010-09-29 15:41:49 -0400 | [diff] [blame^] | 119 |  | 
 | 120 | config NFS_USE_NEW_IDMAPPER | 
 | 121 | 	bool "Use the new idmapper upcall routine" | 
 | 122 | 	depends on NFS_V4 && KEYS | 
 | 123 | 	help | 
 | 124 | 	  Say Y here if you want NFS to use the new idmapper upcall functions. | 
 | 125 | 	  You will need /sbin/request-key (usually provided by the keyutils | 
 | 126 | 	  package).  For details, read | 
 | 127 | 	  <file:Documentation/filesystems/nfs/idmapper.txt>. | 
 | 128 |  | 
 | 129 | 	  If you are unsure, say N. |