Config.in.fsnet 6.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179
  1. config ADK_KERNEL_FILE_LOCKING
  2. boolean
  3. config ADK_KERNEL_FS_POSIX_ACL
  4. boolean
  5. default y
  6. config ADK_KPACKAGE_KMOD_CIFS
  7. prompt "CIFS support"
  8. tristate
  9. select ADK_KPACKAGE_KMOD_NLS if !ADK_KERNEL_NLS
  10. select ADK_KERNEL_NETWORK_FILESYSTEMS
  11. select ADK_KPACKAGE_KMOD_CRYPTO_MD4
  12. select ADK_KPACKAGE_KMOD_CRYPTO_MD5
  13. select ADK_KPACKAGE_KMOD_CRYPTO_HMAC
  14. select ADK_KPACKAGE_KMOD_CRYPTO_ARC4
  15. select ADK_KPACKAGE_KMOD_CRYPTO_ECB
  16. select ADK_KPACKAGE_KMOD_CRYPTO_DES
  17. select ADK_KPACKAGE_KMOD_CRYPTO_SHA256
  18. default n
  19. help
  20. This is the client VFS module for the Common Internet File System
  21. (CIFS) protocol which is the successor to the Server Message Block
  22. (SMB) protocol, the native file sharing mechanism for most early
  23. PC operating systems. The CIFS protocol is fully supported by
  24. file servers such as Windows 2000 (including Windows 2003, NT 4
  25. and Windows XP) as well by Samba (which provides excellent CIFS
  26. server support for Linux and many other operating systems). Limited
  27. support for Windows ME and similar servers is provided as well.
  28. You must use the smbfs client filesystem to access older SMB servers
  29. such as OS/2 and DOS.
  30. The intent of the cifs module is to provide an advanced
  31. network file system client for mounting to CIFS compliant servers,
  32. including support for dfs (hierarchical name space), secure per-user
  33. session establishment, safe distributed caching (oplock), optional
  34. packet signing, Unicode and other internationalization improvements,
  35. and optional Winbind (nsswitch) integration. You do not need to enable
  36. cifs if running only a (Samba) server. It is possible to enable both
  37. smbfs and cifs (e.g. if you are using CIFS for accessing Windows 2003
  38. and Samba 3 servers, and smbfs for accessing old servers). If you need
  39. to mount to Samba or Windows from this machine, say Y.
  40. config ADK_KPACKAGE_KMOD_CODA_FS
  41. prompt "Support for CODA filesystem"
  42. tristate
  43. select ADK_KERNEL_NETWORK_FILESYSTEMS
  44. default n
  45. help
  46. This is the kernel part of the client for the CODA filesystem.
  47. config ADK_KERNEL_NFS_V4
  48. boolean
  49. depends on !ADK_TARGET_ROOTFS_NFSROOT
  50. select ADK_KERNEL_NETWORK_FILESYSTEMS
  51. default n
  52. config ADK_KERNEL_RPCSEC_GSS_KRB5
  53. boolean
  54. default n
  55. config ADK_KPACKAGE_KMOD_NFS_FS
  56. prompt "NFS client support (includes V3 support)"
  57. tristate
  58. default n
  59. select ADK_KERNEL_NFS_V3
  60. select ADK_KERNEL_NFS_V4
  61. select ADK_KERNEL_FILE_LOCKING
  62. select ADK_KERNEL_DNOTIFY
  63. select ADK_KPACKAGE_KMOD_SUNRPC
  64. select ADK_KPACKAGE_KMOD_LOCKD
  65. select ADK_KERNEL_NETWORK_FILESYSTEMS
  66. depends on !ADK_TARGET_ROOTFS_NFSROOT
  67. help
  68. If you are connected to some other (usually local) Unix computer
  69. (using SLIP, PLIP, PPP or Ethernet) and want to mount files residing
  70. on that computer (the NFS server) using the Network File Sharing
  71. protocol, say Y. "Mounting files" means that the client can access
  72. the files with usual UNIX commands as if they were sitting on the
  73. client's hard disk. For this to work, the server must run the
  74. programs nfsd and mountd (but does not need to have NFS file system
  75. support enabled in its kernel). NFS is explained in the Network
  76. Administrator's Guide, available from
  77. <http://www.tldp.org/docs.html#guide>, on its man page: "man
  78. nfs", and in the NFS-HOWTO.
  79. A superior but less widely used alternative to NFS is provided by
  80. the Coda file system; see "Coda file system support" below.
  81. If you say Y here, you should have said Y to TCP/IP networking also.
  82. This option would enlarge your kernel by about 27 KB.
  83. To compile this file system support as a module, choose M here: the
  84. module will be called nfs.
  85. If you are configuring a diskless machine which will mount its root
  86. file system over NFS at boot time, say Y here and to "Kernel
  87. level IP autoconfiguration" above and to "Root file system on NFS"
  88. below. You cannot compile this driver as a module in this case.
  89. There are two packages designed for booting diskless machines over
  90. the net: netboot, available from
  91. <http://ftp1.sourceforge.net/netboot/>, and Etherboot,
  92. available from <http://ftp1.sourceforge.net/etherboot/>.
  93. If you don't know what all this is about, say N.
  94. Kernel modules for NFS client support
  95. config ADK_KERNEL_NFSD_V3
  96. boolean
  97. default n
  98. config ADK_KERNEL_NFSD_V4
  99. boolean
  100. default n
  101. config ADK_KPACKAGE_KMOD_NFSD
  102. prompt "NFS server support"
  103. tristate
  104. default n
  105. select ADK_KERNEL_EXPORTFS
  106. select ADK_KERNEL_NFSD_V3
  107. select ADK_KERNEL_NFSD_V4
  108. select ADK_KERNEL_DNOTIFY
  109. select ADK_KERNEL_FILE_LOCKING
  110. select ADK_KPACKAGE_KMOD_SUNRPC
  111. select ADK_KPACKAGE_KMOD_SUNRPC_GSS
  112. select ADK_KPACKAGE_KMOD_LOCKD
  113. select ADK_KERNEL_NETWORK_FILESYSTEMS
  114. depends on !ADK_TARGET_ROOTFS_NFSROOT
  115. help
  116. If you want your Linux box to act as an NFS *server*, so that other
  117. computers on your local network which support NFS can access certain
  118. directories on your box transparently, you have two options: you can
  119. use the self-contained user space program nfsd, in which case you
  120. should say N here, or you can say Y and use the kernel based NFS
  121. server. The advantage of the kernel based solution is that it is
  122. faster.
  123. In either case, you will need support software; the respective
  124. locations are given in the file <file:Documentation/Changes> in the
  125. NFS section.
  126. If you say Y here, you will get support for version 2 of the NFS
  127. protocol (NFSv2). If you also want NFSv3, say Y to the next question
  128. as well.
  129. Please read the NFS-HOWTO, available from
  130. <http://www.tldp.org/docs.html#howto>.
  131. config ADK_KPACKAGE_KMOD_LOCKD
  132. tristate
  133. default n
  134. config ADK_KPACKAGE_KMOD_SUNRPC
  135. tristate
  136. depends on !ADK_KERNEL_SUNRPC
  137. default n
  138. config ADK_KPACKAGE_KMOD_SUNRPC_GSS
  139. tristate
  140. select ADK_KPACKAGE_KMOD_SUNRPC
  141. default n
  142. config ADK_KPACKAGE_KMOD_RPCSEC_GSS_KRB5
  143. tristate
  144. select ADK_KERNEL_NETWORK_FILESYSTEMS
  145. select ADK_KPACKAGE_KMOD_SUNRPC_GSS
  146. select ADK_KPACKAGE_KMOD_SUNRPC
  147. select ADK_KPACKAGE_KMOD_CRYPTO
  148. select ADK_KPACKAGE_KMOD_CRYPTO_MD5
  149. select ADK_KPACKAGE_KMOD_CRYPTO_DES
  150. select ADK_KPACKAGE_KMOD_CRYPTO_CBC
  151. select ADK_KPACKAGE_KMOD_CRYPTO_CTS
  152. select ADK_KPACKAGE_KMOD_CRYPTO_ECB
  153. select ADK_KPACKAGE_KMOD_CRYPTO_HMAC
  154. select ADK_KPACKAGE_KMOD_CRYPTO_SHA1
  155. select ADK_KPACKAGE_KMOD_CRYPTO_AES
  156. select ADK_KPACKAGE_KMOD_CRYPTO_ARC4
  157. default n