Kconfig 4.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153
  1. config 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. To mount file systems exported by NFS servers, you also need to
  13. install the user space mount.nfs command which can be found in
  14. the Linux nfs-utils package, available from http://linux-nfs.org/.
  15. Information about using the mount command is available in the
  16. mount(8) man page. More detail about the Linux NFS client
  17. implementation is available via the nfs(5) man page.
  18. Below you can choose which versions of the NFS protocol are
  19. available in the kernel to mount NFS servers. Support for NFS
  20. version 2 (RFC 1094) is always available when NFS_FS is selected.
  21. To configure a system which mounts its root file system via NFS
  22. at boot time, say Y here, select "Kernel level IP
  23. autoconfiguration" in the NETWORK menu, and select "Root file
  24. system on NFS" below. You cannot compile this file system as a
  25. module in this case.
  26. If unsure, say N.
  27. config NFS_V3
  28. bool "NFS client support for NFS version 3"
  29. depends on NFS_FS
  30. help
  31. This option enables support for version 3 of the NFS protocol
  32. (RFC 1813) in the kernel's NFS client.
  33. If unsure, say Y.
  34. config NFS_V3_ACL
  35. bool "NFS client support for the NFSv3 ACL protocol extension"
  36. depends on NFS_V3
  37. help
  38. Some NFS servers support an auxiliary NFSv3 ACL protocol that
  39. Sun added to Solaris but never became an official part of the
  40. NFS version 3 protocol. This protocol extension allows
  41. applications on NFS clients to manipulate POSIX Access Control
  42. Lists on files residing on NFS servers. NFS servers enforce
  43. ACLs on local files whether this protocol is available or not.
  44. Choose Y here if your NFS server supports the Solaris NFSv3 ACL
  45. protocol extension and you want your NFS client to allow
  46. applications to access and modify ACLs on files on the server.
  47. Most NFS servers don't support the Solaris NFSv3 ACL protocol
  48. extension. You can choose N here or specify the "noacl" mount
  49. option to prevent your NFS client from trying to use the NFSv3
  50. ACL protocol.
  51. If unsure, say N.
  52. config NFS_V4
  53. bool "NFS client support for NFS version 4"
  54. depends on NFS_FS
  55. select SUNRPC_GSS
  56. select KEYS
  57. help
  58. This option enables support for version 4 of the NFS protocol
  59. (RFC 3530) in the kernel's NFS client.
  60. To mount NFS servers using NFSv4, you also need to install user
  61. space programs which can be found in the Linux nfs-utils package,
  62. available from http://linux-nfs.org/.
  63. If unsure, say Y.
  64. config NFS_V4_1
  65. bool "NFS client support for NFSv4.1 (EXPERIMENTAL)"
  66. depends on NFS_FS && NFS_V4 && EXPERIMENTAL
  67. select SUNRPC_BACKCHANNEL
  68. select PNFS_FILE_LAYOUT
  69. help
  70. This option enables support for minor version 1 of the NFSv4 protocol
  71. (RFC 5661) in the kernel's NFS client.
  72. If unsure, say N.
  73. config PNFS_FILE_LAYOUT
  74. tristate
  75. config PNFS_BLOCK
  76. tristate
  77. depends on NFS_FS && NFS_V4_1 && BLK_DEV_DM
  78. default m
  79. config PNFS_OBJLAYOUT
  80. tristate
  81. depends on NFS_FS && NFS_V4_1 && SCSI_OSD_ULD
  82. default m
  83. config NFS_V4_1_IMPLEMENTATION_ID_DOMAIN
  84. string "NFSv4.1 Implementation ID Domain"
  85. depends on NFS_V4_1
  86. default "kernel.org"
  87. help
  88. This option defines the domain portion of the implementation ID that
  89. may be sent in the NFS exchange_id operation. The value must be in
  90. the format of a DNS domain name and should be set to the DNS domain
  91. name of the distribution.
  92. If the NFS client is unchanged from the upstream kernel, this
  93. option should be set to the default "kernel.org".
  94. config ROOT_NFS
  95. bool "Root file system on NFS"
  96. depends on NFS_FS=y && IP_PNP
  97. help
  98. If you want your system to mount its root file system via NFS,
  99. choose Y here. This is common practice for managing systems
  100. without local permanent storage. For details, read
  101. <file:Documentation/filesystems/nfs/nfsroot.txt>.
  102. Most people say N here.
  103. config NFS_FSCACHE
  104. bool "Provide NFS client caching support"
  105. depends on NFS_FS=m && FSCACHE || NFS_FS=y && FSCACHE=y
  106. help
  107. Say Y here if you want NFS data to be cached locally on disc through
  108. the general filesystem cache manager
  109. config NFS_USE_LEGACY_DNS
  110. bool "Use the legacy NFS DNS resolver"
  111. depends on NFS_V4
  112. help
  113. The kernel now provides a method for translating a host name into an
  114. IP address. Select Y here if you would rather use your own DNS
  115. resolver script.
  116. If unsure, say N
  117. config NFS_USE_KERNEL_DNS
  118. bool
  119. depends on NFS_V4 && !NFS_USE_LEGACY_DNS
  120. select DNS_RESOLVER
  121. default y
  122. config NFS_DEBUG
  123. bool
  124. depends on NFS_FS && SUNRPC_DEBUG
  125. select CRC32
  126. default y