| Alexey Dobriyan | 97afe47 | 2009-01-22 11:07:41 +0300 | [diff] [blame^] | 1 | config NFS_FS |
| 2 | tristate "NFS client support" |
| 3 | depends on INET |
| 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 |
| 64 | bool "NFS client support for NFS version 4 (EXPERIMENTAL)" |
| 65 | depends on NFS_FS && EXPERIMENTAL |
| 66 | select RPCSEC_GSS_KRB5 |
| 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 | |
| 75 | If unsure, say N. |
| 76 | |
| 77 | config ROOT_NFS |
| 78 | bool "Root file system on NFS" |
| 79 | depends on NFS_FS=y && IP_PNP |
| 80 | help |
| 81 | If you want your system to mount its root file system via NFS, |
| 82 | choose Y here. This is common practice for managing systems |
| 83 | without local permanent storage. For details, read |
| 84 | <file:Documentation/filesystems/nfsroot.txt>. |
| 85 | |
| 86 | Most people say N here. |