1config NFS_FS 2 tristate "NFS client support" 3 depends on INET && FILE_LOCKING 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 32config NFS_V2 33 tristate "NFS client support for NFS version 2" 34 depends on NFS_FS 35 default y 36 help 37 This option enables support for version 2 of the NFS protocol 38 (RFC 1094) in the kernel's NFS client. 39 40 If unsure, say Y. 41 42config NFS_V3 43 tristate "NFS client support for NFS version 3" 44 depends on NFS_FS 45 default y 46 help 47 This option enables support for version 3 of the NFS protocol 48 (RFC 1813) in the kernel's NFS client. 49 50 If unsure, say Y. 51 52config NFS_V3_ACL 53 bool "NFS client support for the NFSv3 ACL protocol extension" 54 depends on NFS_V3 55 help 56 Some NFS servers support an auxiliary NFSv3 ACL protocol that 57 Sun added to Solaris but never became an official part of the 58 NFS version 3 protocol. This protocol extension allows 59 applications on NFS clients to manipulate POSIX Access Control 60 Lists on files residing on NFS servers. NFS servers enforce 61 ACLs on local files whether this protocol is available or not. 62 63 Choose Y here if your NFS server supports the Solaris NFSv3 ACL 64 protocol extension and you want your NFS client to allow 65 applications to access and modify ACLs on files on the server. 66 67 Most NFS servers don't support the Solaris NFSv3 ACL protocol 68 extension. You can choose N here or specify the "noacl" mount 69 option to prevent your NFS client from trying to use the NFSv3 70 ACL protocol. 71 72 If unsure, say N. 73 74config NFS_V4 75 tristate "NFS client support for NFS version 4" 76 depends on NFS_FS 77 select SUNRPC_GSS 78 select KEYS 79 help 80 This option enables support for version 4 of the NFS protocol 81 (RFC 3530) in the kernel's NFS client. 82 83 To mount NFS servers using NFSv4, you also need to install user 84 space programs which can be found in the Linux nfs-utils package, 85 available from http://linux-nfs.org/. 86 87 If unsure, say Y. 88 89config NFS_SWAP 90 bool "Provide swap over NFS support" 91 default n 92 depends on NFS_FS 93 select SUNRPC_SWAP 94 help 95 This option enables swapon to work on files located on NFS mounts. 96 97config NFS_V4_1 98 bool "NFS client support for NFSv4.1" 99 depends on NFS_V4 100 select SUNRPC_BACKCHANNEL 101 help 102 This option enables support for minor version 1 of the NFSv4 protocol 103 (RFC 5661) in the kernel's NFS client. 104 105 If unsure, say N. 106 107config NFS_V4_2 108 bool "NFS client support for NFSv4.2" 109 depends on NFS_V4_1 110 help 111 This option enables support for minor version 2 of the NFSv4 protocol 112 in the kernel's NFS client. 113 114 If unsure, say N. 115 116config PNFS_FILE_LAYOUT 117 tristate 118 depends on NFS_V4_1 119 default m 120 121config PNFS_BLOCK 122 tristate 123 depends on NFS_V4_1 && BLK_DEV_DM 124 default m 125 126config PNFS_OBJLAYOUT 127 tristate 128 depends on NFS_V4_1 && SCSI_OSD_ULD 129 default m 130 131config NFS_V4_1_IMPLEMENTATION_ID_DOMAIN 132 string "NFSv4.1 Implementation ID Domain" 133 depends on NFS_V4_1 134 default "kernel.org" 135 help 136 This option defines the domain portion of the implementation ID that 137 may be sent in the NFS exchange_id operation. The value must be in 138 the format of a DNS domain name and should be set to the DNS domain 139 name of the distribution. 140 If the NFS client is unchanged from the upstream kernel, this 141 option should be set to the default "kernel.org". 142 143config NFS_V4_SECURITY_LABEL 144 bool 145 depends on NFS_V4_2 && SECURITY 146 default y 147 148config ROOT_NFS 149 bool "Root file system on NFS" 150 depends on NFS_FS=y && IP_PNP 151 help 152 If you want your system to mount its root file system via NFS, 153 choose Y here. This is common practice for managing systems 154 without local permanent storage. For details, read 155 <file:Documentation/filesystems/nfs/nfsroot.txt>. 156 157 Most people say N here. 158 159config NFS_FSCACHE 160 bool "Provide NFS client caching support" 161 depends on NFS_FS=m && FSCACHE || NFS_FS=y && FSCACHE=y 162 help 163 Say Y here if you want NFS data to be cached locally on disc through 164 the general filesystem cache manager 165 166config NFS_USE_LEGACY_DNS 167 bool "Use the legacy NFS DNS resolver" 168 depends on NFS_V4 169 help 170 The kernel now provides a method for translating a host name into an 171 IP address. Select Y here if you would rather use your own DNS 172 resolver script. 173 174 If unsure, say N 175 176config NFS_USE_KERNEL_DNS 177 bool 178 depends on NFS_V4 && !NFS_USE_LEGACY_DNS 179 select DNS_RESOLVER 180 default y 181 182config NFS_DEBUG 183 bool 184 depends on NFS_FS && SUNRPC_DEBUG 185 select CRC32 186 default y 187