git://bbs.cooldavid.org / net-next-2.6.git / blame
| Commit | Line | Data |
|---|---|---|
| 97afe47a AD |
1 | config NFS_FS |
| 2 | tristate "NFS client support" | |
| dd4dc82d | 3 | depends on INET && FILE_LOCKING |
| 97afe47a AD |
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 | |
| b3edc2bc TM |
64 | bool "NFS client support for NFS version 4" |
| 65 | depends on NFS_FS | |
| 827e3457 | 66 | select SUNRPC_GSS |
| 97afe47a AD |
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 | ||
| b3edc2bc | 75 | If unsure, say Y. |
| 97afe47a | 76 | |
| 1efae381 | 77 | config NFS_V4_1 |
| 3dce9a5c | 78 | bool "NFS client support for NFSv4.1 (EXPERIMENTAL)" |
| 1efae381 RL |
79 | depends on NFS_V4 && EXPERIMENTAL |
| 80 | help | |
| 81 | This option enables support for minor version 1 of the NFSv4 protocol | |
| 82 | (draft-ietf-nfsv4-minorversion1) in the kernel's NFS client. | |
| 83 | ||
| 3dce9a5c | 84 | If unsure, say N. |
| 1efae381 | 85 | |
| 97afe47a AD |
86 | config ROOT_NFS |
| 87 | bool "Root file system on NFS" | |
| 88 | depends on NFS_FS=y && IP_PNP | |
| 89 | help | |
| 90 | If you want your system to mount its root file system via NFS, | |
| 91 | choose Y here. This is common practice for managing systems | |
| 92 | without local permanent storage. For details, read | |
| dc7a0816 | 93 | <file:Documentation/filesystems/nfs/nfsroot.txt>. |
| 97afe47a AD |
94 | |
| 95 | Most people say N here. | |
| 3b9ce977 DH |
96 | |
| 97 | config NFS_FSCACHE | |
| 4912002f | 98 | bool "Provide NFS client caching support" |
| 3b9ce977 DH |
99 | depends on NFS_FS=m && FSCACHE || NFS_FS=y && FSCACHE=y |
| 100 | help | |
| 101 | Say Y here if you want NFS data to be cached locally on disc through | |
| 102 | the general filesystem cache manager | |
| c2e8139c BS |
103 | |
| 104 | config NFS_USE_LEGACY_DNS | |
| 105 | bool "Use the legacy NFS DNS resolver" | |
| 106 | depends on NFS_V4 | |
| 107 | help | |
| 108 | The kernel now provides a method for translating a host name into an | |
| 109 | IP address. Select Y here if you would rather use your own DNS | |
| 110 | resolver script. | |
| 111 | ||
| 112 | If unsure, say N | |
| 113 | ||
| 114 | config NFS_USE_KERNEL_DNS | |
| 115 | bool | |
| 116 | depends on NFS_V4 && !NFS_USE_LEGACY_DNS | |
| 117 | select DNS_RESOLVER | |
| 3f432312 | 118 | select KEYS |
| c2e8139c | 119 | default y |