Kconfig 24 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758
  1. #
  2. # File system configuration
  3. #
  4. menu "File systems"
  5. if BLOCK
  6. source "fs/ext2/Kconfig"
  7. source "fs/ext3/Kconfig"
  8. source "fs/ext4/Kconfig"
  9. config FS_XIP
  10. # execute in place
  11. bool
  12. depends on EXT2_FS_XIP
  13. default y
  14. source "fs/jbd/Kconfig"
  15. source "fs/jbd2/Kconfig"
  16. config FS_MBCACHE
  17. # Meta block cache for Extended Attributes (ext2/ext3/ext4)
  18. tristate
  19. default y if EXT2_FS=y && EXT2_FS_XATTR
  20. default y if EXT3_FS=y && EXT3_FS_XATTR
  21. default y if EXT4_FS=y && EXT4_FS_XATTR
  22. default m if EXT2_FS_XATTR || EXT3_FS_XATTR || EXT4_FS_XATTR
  23. source "fs/reiserfs/Kconfig"
  24. source "fs/jfs/Kconfig"
  25. config FS_POSIX_ACL
  26. # Posix ACL utility routines (for now, only ext2/ext3/jfs/reiserfs/nfs4)
  27. #
  28. # NOTE: you can implement Posix ACLs without these helpers (XFS does).
  29. # Never use this symbol for ifdefs.
  30. #
  31. bool
  32. default n
  33. config FILE_LOCKING
  34. bool "Enable POSIX file locking API" if EMBEDDED
  35. default y
  36. help
  37. This option enables standard file locking support, required
  38. for filesystems like NFS and for the flock() system
  39. call. Disabling this option saves about 11k.
  40. source "fs/xfs/Kconfig"
  41. source "fs/gfs2/Kconfig"
  42. source "fs/ocfs2/Kconfig"
  43. source "fs/btrfs/Kconfig"
  44. endif # BLOCK
  45. source "fs/notify/Kconfig"
  46. config QUOTA
  47. bool "Quota support"
  48. help
  49. If you say Y here, you will be able to set per user limits for disk
  50. usage (also called disk quotas). Currently, it works for the
  51. ext2, ext3, and reiserfs file system. ext3 also supports journalled
  52. quotas for which you don't need to run quotacheck(8) after an unclean
  53. shutdown.
  54. For further details, read the Quota mini-HOWTO, available from
  55. <http://www.tldp.org/docs.html#howto>, or the documentation provided
  56. with the quota tools. Probably the quota support is only useful for
  57. multi user systems. If unsure, say N.
  58. config QUOTA_NETLINK_INTERFACE
  59. bool "Report quota messages through netlink interface"
  60. depends on QUOTA && NET
  61. help
  62. If you say Y here, quota warnings (about exceeding softlimit, reaching
  63. hardlimit, etc.) will be reported through netlink interface. If unsure,
  64. say Y.
  65. config PRINT_QUOTA_WARNING
  66. bool "Print quota warnings to console (OBSOLETE)"
  67. depends on QUOTA
  68. default y
  69. help
  70. If you say Y here, quota warnings (about exceeding softlimit, reaching
  71. hardlimit, etc.) will be printed to the process' controlling terminal.
  72. Note that this behavior is currently deprecated and may go away in
  73. future. Please use notification via netlink socket instead.
  74. # Generic support for tree structured quota files. Seleted when needed.
  75. config QUOTA_TREE
  76. tristate
  77. config QFMT_V1
  78. tristate "Old quota format support"
  79. depends on QUOTA
  80. help
  81. This quota format was (is) used by kernels earlier than 2.4.22. If
  82. you have quota working and you don't want to convert to new quota
  83. format say Y here.
  84. config QFMT_V2
  85. tristate "Quota format v2 support"
  86. depends on QUOTA
  87. select QUOTA_TREE
  88. help
  89. This quota format allows using quotas with 32-bit UIDs/GIDs. If you
  90. need this functionality say Y here.
  91. config QUOTACTL
  92. bool
  93. depends on XFS_QUOTA || QUOTA
  94. default y
  95. source "fs/autofs/Kconfig"
  96. source "fs/autofs4/Kconfig"
  97. source "fs/fuse/Kconfig"
  98. config GENERIC_ACL
  99. bool
  100. select FS_POSIX_ACL
  101. if BLOCK
  102. menu "CD-ROM/DVD Filesystems"
  103. source "fs/isofs/Kconfig"
  104. source "fs/udf/Kconfig"
  105. endmenu
  106. endif # BLOCK
  107. if BLOCK
  108. menu "DOS/FAT/NT Filesystems"
  109. source "fs/fat/Kconfig"
  110. source "fs/ntfs/Kconfig"
  111. endmenu
  112. endif # BLOCK
  113. menu "Pseudo filesystems"
  114. source "fs/proc/Kconfig"
  115. source "fs/sysfs/Kconfig"
  116. config TMPFS
  117. bool "Virtual memory file system support (former shm fs)"
  118. help
  119. Tmpfs is a file system which keeps all files in virtual memory.
  120. Everything in tmpfs is temporary in the sense that no files will be
  121. created on your hard drive. The files live in memory and swap
  122. space. If you unmount a tmpfs instance, everything stored therein is
  123. lost.
  124. See <file:Documentation/filesystems/tmpfs.txt> for details.
  125. config TMPFS_POSIX_ACL
  126. bool "Tmpfs POSIX Access Control Lists"
  127. depends on TMPFS
  128. select GENERIC_ACL
  129. help
  130. POSIX Access Control Lists (ACLs) support permissions for users and
  131. groups beyond the owner/group/world scheme.
  132. To learn more about Access Control Lists, visit the POSIX ACLs for
  133. Linux website <http://acl.bestbits.at/>.
  134. If you don't know what Access Control Lists are, say N.
  135. config HUGETLBFS
  136. bool "HugeTLB file system support"
  137. depends on X86 || IA64 || PPC64 || SPARC64 || (SUPERH && MMU) || \
  138. (S390 && 64BIT) || BROKEN
  139. help
  140. hugetlbfs is a filesystem backing for HugeTLB pages, based on
  141. ramfs. For architectures that support it, say Y here and read
  142. <file:Documentation/vm/hugetlbpage.txt> for details.
  143. If unsure, say N.
  144. config HUGETLB_PAGE
  145. def_bool HUGETLBFS
  146. source "fs/configfs/Kconfig"
  147. endmenu
  148. menuconfig MISC_FILESYSTEMS
  149. bool "Miscellaneous filesystems"
  150. default y
  151. ---help---
  152. Say Y here to get to see options for various miscellaneous
  153. filesystems, such as filesystems that came from other
  154. operating systems.
  155. This option alone does not add any kernel code.
  156. If you say N, all options in this submenu will be skipped and
  157. disabled; if unsure, say Y here.
  158. if MISC_FILESYSTEMS
  159. source "fs/adfs/Kconfig"
  160. source "fs/affs/Kconfig"
  161. source "fs/ecryptfs/Kconfig"
  162. source "fs/hfs/Kconfig"
  163. source "fs/hfsplus/Kconfig"
  164. source "fs/befs/Kconfig"
  165. source "fs/bfs/Kconfig"
  166. source "fs/efs/Kconfig"
  167. source "fs/jffs2/Kconfig"
  168. # UBIFS File system configuration
  169. source "fs/ubifs/Kconfig"
  170. source "fs/cramfs/Kconfig"
  171. source "fs/squashfs/Kconfig"
  172. source "fs/freevxfs/Kconfig"
  173. source "fs/minix/Kconfig"
  174. source "fs/omfs/Kconfig"
  175. source "fs/hpfs/Kconfig"
  176. source "fs/qnx4/Kconfig"
  177. config ROMFS_FS
  178. tristate "ROM file system support"
  179. depends on BLOCK
  180. ---help---
  181. This is a very small read-only file system mainly intended for
  182. initial ram disks of installation disks, but it could be used for
  183. other read-only media as well. Read
  184. <file:Documentation/filesystems/romfs.txt> for details.
  185. To compile this file system support as a module, choose M here: the
  186. module will be called romfs. Note that the file system of your
  187. root partition (the one containing the directory /) cannot be a
  188. module.
  189. If you don't know whether you need it, then you don't need it:
  190. answer N.
  191. config SYSV_FS
  192. tristate "System V/Xenix/V7/Coherent file system support"
  193. depends on BLOCK
  194. help
  195. SCO, Xenix and Coherent are commercial Unix systems for Intel
  196. machines, and Version 7 was used on the DEC PDP-11. Saying Y
  197. here would allow you to read from their floppies and hard disk
  198. partitions.
  199. If you have floppies or hard disk partitions like that, it is likely
  200. that they contain binaries from those other Unix systems; in order
  201. to run these binaries, you will want to install linux-abi which is
  202. a set of kernel modules that lets you run SCO, Xenix, Wyse,
  203. UnixWare, Dell Unix and System V programs under Linux. It is
  204. available via FTP (user: ftp) from
  205. <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
  206. NOTE: that will work only for binaries from Intel-based systems;
  207. PDP ones will have to wait until somebody ports Linux to -11 ;-)
  208. If you only intend to mount files from some other Unix over the
  209. network using NFS, you don't need the System V file system support
  210. (but you need NFS file system support obviously).
  211. Note that this option is generally not needed for floppies, since a
  212. good portable way to transport files and directories between unixes
  213. (and even other operating systems) is given by the tar program ("man
  214. tar" or preferably "info tar"). Note also that this option has
  215. nothing whatsoever to do with the option "System V IPC". Read about
  216. the System V file system in
  217. <file:Documentation/filesystems/sysv-fs.txt>.
  218. Saying Y here will enlarge your kernel by about 27 KB.
  219. To compile this as a module, choose M here: the module will be called
  220. sysv.
  221. If you haven't heard about all of this before, it's safe to say N.
  222. config UFS_FS
  223. tristate "UFS file system support (read only)"
  224. depends on BLOCK
  225. help
  226. BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
  227. OpenBSD and NeXTstep) use a file system called UFS. Some System V
  228. Unixes can create and mount hard disk partitions and diskettes using
  229. this file system as well. Saying Y here will allow you to read from
  230. these partitions; if you also want to write to them, say Y to the
  231. experimental "UFS file system write support", below. Please read the
  232. file <file:Documentation/filesystems/ufs.txt> for more information.
  233. The recently released UFS2 variant (used in FreeBSD 5.x) is
  234. READ-ONLY supported.
  235. Note that this option is generally not needed for floppies, since a
  236. good portable way to transport files and directories between unixes
  237. (and even other operating systems) is given by the tar program ("man
  238. tar" or preferably "info tar").
  239. When accessing NeXTstep files, you may need to convert them from the
  240. NeXT character set to the Latin1 character set; use the program
  241. recode ("info recode") for this purpose.
  242. To compile the UFS file system support as a module, choose M here: the
  243. module will be called ufs.
  244. If you haven't heard about all of this before, it's safe to say N.
  245. config UFS_FS_WRITE
  246. bool "UFS file system write support (DANGEROUS)"
  247. depends on UFS_FS && EXPERIMENTAL
  248. help
  249. Say Y here if you want to try writing to UFS partitions. This is
  250. experimental, so you should back up your UFS partitions beforehand.
  251. config UFS_DEBUG
  252. bool "UFS debugging"
  253. depends on UFS_FS
  254. help
  255. If you are experiencing any problems with the UFS filesystem, say
  256. Y here. This will result in _many_ additional debugging messages to be
  257. written to the system log.
  258. endif # MISC_FILESYSTEMS
  259. menuconfig NETWORK_FILESYSTEMS
  260. bool "Network File Systems"
  261. default y
  262. depends on NET
  263. ---help---
  264. Say Y here to get to see options for network filesystems and
  265. filesystem-related networking code, such as NFS daemon and
  266. RPCSEC security modules.
  267. This option alone does not add any kernel code.
  268. If you say N, all options in this submenu will be skipped and
  269. disabled; if unsure, say Y here.
  270. if NETWORK_FILESYSTEMS
  271. config NFS_FS
  272. tristate "NFS client support"
  273. depends on INET
  274. select LOCKD
  275. select SUNRPC
  276. select NFS_ACL_SUPPORT if NFS_V3_ACL
  277. help
  278. Choose Y here if you want to access files residing on other
  279. computers using Sun's Network File System protocol. To compile
  280. this file system support as a module, choose M here: the module
  281. will be called nfs.
  282. To mount file systems exported by NFS servers, you also need to
  283. install the user space mount.nfs command which can be found in
  284. the Linux nfs-utils package, available from http://linux-nfs.org/.
  285. Information about using the mount command is available in the
  286. mount(8) man page. More detail about the Linux NFS client
  287. implementation is available via the nfs(5) man page.
  288. Below you can choose which versions of the NFS protocol are
  289. available in the kernel to mount NFS servers. Support for NFS
  290. version 2 (RFC 1094) is always available when NFS_FS is selected.
  291. To configure a system which mounts its root file system via NFS
  292. at boot time, say Y here, select "Kernel level IP
  293. autoconfiguration" in the NETWORK menu, and select "Root file
  294. system on NFS" below. You cannot compile this file system as a
  295. module in this case.
  296. If unsure, say N.
  297. config NFS_V3
  298. bool "NFS client support for NFS version 3"
  299. depends on NFS_FS
  300. help
  301. This option enables support for version 3 of the NFS protocol
  302. (RFC 1813) in the kernel's NFS client.
  303. If unsure, say Y.
  304. config NFS_V3_ACL
  305. bool "NFS client support for the NFSv3 ACL protocol extension"
  306. depends on NFS_V3
  307. help
  308. Some NFS servers support an auxiliary NFSv3 ACL protocol that
  309. Sun added to Solaris but never became an official part of the
  310. NFS version 3 protocol. This protocol extension allows
  311. applications on NFS clients to manipulate POSIX Access Control
  312. Lists on files residing on NFS servers. NFS servers enforce
  313. ACLs on local files whether this protocol is available or not.
  314. Choose Y here if your NFS server supports the Solaris NFSv3 ACL
  315. protocol extension and you want your NFS client to allow
  316. applications to access and modify ACLs on files on the server.
  317. Most NFS servers don't support the Solaris NFSv3 ACL protocol
  318. extension. You can choose N here or specify the "noacl" mount
  319. option to prevent your NFS client from trying to use the NFSv3
  320. ACL protocol.
  321. If unsure, say N.
  322. config NFS_V4
  323. bool "NFS client support for NFS version 4 (EXPERIMENTAL)"
  324. depends on NFS_FS && EXPERIMENTAL
  325. select RPCSEC_GSS_KRB5
  326. help
  327. This option enables support for version 4 of the NFS protocol
  328. (RFC 3530) in the kernel's NFS client.
  329. To mount NFS servers using NFSv4, you also need to install user
  330. space programs which can be found in the Linux nfs-utils package,
  331. available from http://linux-nfs.org/.
  332. If unsure, say N.
  333. config ROOT_NFS
  334. bool "Root file system on NFS"
  335. depends on NFS_FS=y && IP_PNP
  336. help
  337. If you want your system to mount its root file system via NFS,
  338. choose Y here. This is common practice for managing systems
  339. without local permanent storage. For details, read
  340. <file:Documentation/filesystems/nfsroot.txt>.
  341. Most people say N here.
  342. config NFSD
  343. tristate "NFS server support"
  344. depends on INET
  345. select LOCKD
  346. select SUNRPC
  347. select EXPORTFS
  348. select NFS_ACL_SUPPORT if NFSD_V2_ACL
  349. help
  350. Choose Y here if you want to allow other computers to access
  351. files residing on this system using Sun's Network File System
  352. protocol. To compile the NFS server support as a module,
  353. choose M here: the module will be called nfsd.
  354. You may choose to use a user-space NFS server instead, in which
  355. case you can choose N here.
  356. To export local file systems using NFS, you also need to install
  357. user space programs which can be found in the Linux nfs-utils
  358. package, available from http://linux-nfs.org/. More detail about
  359. the Linux NFS server implementation is available via the
  360. exports(5) man page.
  361. Below you can choose which versions of the NFS protocol are
  362. available to clients mounting the NFS server on this system.
  363. Support for NFS version 2 (RFC 1094) is always available when
  364. CONFIG_NFSD is selected.
  365. If unsure, say N.
  366. config NFSD_V2_ACL
  367. bool
  368. depends on NFSD
  369. config NFSD_V3
  370. bool "NFS server support for NFS version 3"
  371. depends on NFSD
  372. help
  373. This option enables support in your system's NFS server for
  374. version 3 of the NFS protocol (RFC 1813).
  375. If unsure, say Y.
  376. config NFSD_V3_ACL
  377. bool "NFS server support for the NFSv3 ACL protocol extension"
  378. depends on NFSD_V3
  379. select NFSD_V2_ACL
  380. help
  381. Solaris NFS servers support an auxiliary NFSv3 ACL protocol that
  382. never became an official part of the NFS version 3 protocol.
  383. This protocol extension allows applications on NFS clients to
  384. manipulate POSIX Access Control Lists on files residing on NFS
  385. servers. NFS servers enforce POSIX ACLs on local files whether
  386. this protocol is available or not.
  387. This option enables support in your system's NFS server for the
  388. NFSv3 ACL protocol extension allowing NFS clients to manipulate
  389. POSIX ACLs on files exported by your system's NFS server. NFS
  390. clients which support the Solaris NFSv3 ACL protocol can then
  391. access and modify ACLs on your NFS server.
  392. To store ACLs on your NFS server, you also need to enable ACL-
  393. related CONFIG options for your local file systems of choice.
  394. If unsure, say N.
  395. config NFSD_V4
  396. bool "NFS server support for NFS version 4 (EXPERIMENTAL)"
  397. depends on NFSD && PROC_FS && EXPERIMENTAL
  398. select NFSD_V3
  399. select FS_POSIX_ACL
  400. select RPCSEC_GSS_KRB5
  401. help
  402. This option enables support in your system's NFS server for
  403. version 4 of the NFS protocol (RFC 3530).
  404. To export files using NFSv4, you need to install additional user
  405. space programs which can be found in the Linux nfs-utils package,
  406. available from http://linux-nfs.org/.
  407. If unsure, say N.
  408. config LOCKD
  409. tristate
  410. config LOCKD_V4
  411. bool
  412. depends on NFSD_V3 || NFS_V3
  413. default y
  414. config EXPORTFS
  415. tristate
  416. config NFS_ACL_SUPPORT
  417. tristate
  418. select FS_POSIX_ACL
  419. config NFS_COMMON
  420. bool
  421. depends on NFSD || NFS_FS
  422. default y
  423. config SUNRPC
  424. tristate
  425. config SUNRPC_GSS
  426. tristate
  427. config SUNRPC_XPRT_RDMA
  428. tristate
  429. depends on SUNRPC && INFINIBAND && EXPERIMENTAL
  430. default SUNRPC && INFINIBAND
  431. help
  432. This option enables an RPC client transport capability that
  433. allows the NFS client to mount servers via an RDMA-enabled
  434. transport.
  435. To compile RPC client RDMA transport support as a module,
  436. choose M here: the module will be called xprtrdma.
  437. If unsure, say N.
  438. config SUNRPC_REGISTER_V4
  439. bool "Register local RPC services via rpcbind v4 (EXPERIMENTAL)"
  440. depends on SUNRPC && EXPERIMENTAL
  441. default n
  442. help
  443. Sun added support for registering RPC services at an IPv6
  444. address by creating two new versions of the rpcbind protocol
  445. (RFC 1833).
  446. This option enables support in the kernel RPC server for
  447. registering kernel RPC services via version 4 of the rpcbind
  448. protocol. If you enable this option, you must run a portmapper
  449. daemon that supports rpcbind protocol version 4.
  450. Serving NFS over IPv6 from knfsd (the kernel's NFS server)
  451. requires that you enable this option and use a portmapper that
  452. supports rpcbind version 4.
  453. If unsure, say N to get traditional behavior (register kernel
  454. RPC services using only rpcbind version 2). Distributions
  455. using the legacy Linux portmapper daemon must say N here.
  456. config RPCSEC_GSS_KRB5
  457. tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
  458. depends on SUNRPC && EXPERIMENTAL
  459. select SUNRPC_GSS
  460. select CRYPTO
  461. select CRYPTO_MD5
  462. select CRYPTO_DES
  463. select CRYPTO_CBC
  464. help
  465. Choose Y here to enable Secure RPC using the Kerberos version 5
  466. GSS-API mechanism (RFC 1964).
  467. Secure RPC calls with Kerberos require an auxiliary user-space
  468. daemon which may be found in the Linux nfs-utils package
  469. available from http://linux-nfs.org/. In addition, user-space
  470. Kerberos support should be installed.
  471. If unsure, say N.
  472. config RPCSEC_GSS_SPKM3
  473. tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
  474. depends on SUNRPC && EXPERIMENTAL
  475. select SUNRPC_GSS
  476. select CRYPTO
  477. select CRYPTO_MD5
  478. select CRYPTO_DES
  479. select CRYPTO_CAST5
  480. select CRYPTO_CBC
  481. help
  482. Choose Y here to enable Secure RPC using the SPKM3 public key
  483. GSS-API mechansim (RFC 2025).
  484. Secure RPC calls with SPKM3 require an auxiliary userspace
  485. daemon which may be found in the Linux nfs-utils package
  486. available from http://linux-nfs.org/.
  487. If unsure, say N.
  488. config SMB_FS
  489. tristate "SMB file system support (OBSOLETE, please use CIFS)"
  490. depends on INET
  491. select NLS
  492. help
  493. SMB (Server Message Block) is the protocol Windows for Workgroups
  494. (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
  495. files and printers over local networks. Saying Y here allows you to
  496. mount their file systems (often called "shares" in this context) and
  497. access them just like any other Unix directory. Currently, this
  498. works only if the Windows machines use TCP/IP as the underlying
  499. transport protocol, and not NetBEUI. For details, read
  500. <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
  501. available from <http://www.tldp.org/docs.html#howto>.
  502. Note: if you just want your box to act as an SMB *server* and make
  503. files and printing services available to Windows clients (which need
  504. to have a TCP/IP stack), you don't need to say Y here; you can use
  505. the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
  506. for that.
  507. General information about how to connect Linux, Windows machines and
  508. Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
  509. To compile the SMB support as a module, choose M here:
  510. the module will be called smbfs. Most people say N, however.
  511. config SMB_NLS_DEFAULT
  512. bool "Use a default NLS"
  513. depends on SMB_FS
  514. help
  515. Enabling this will make smbfs use nls translations by default. You
  516. need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
  517. settings and you need to give the default nls for the SMB server as
  518. CONFIG_SMB_NLS_REMOTE.
  519. The nls settings can be changed at mount time, if your smbmount
  520. supports that, using the codepage and iocharset parameters.
  521. smbmount from samba 2.2.0 or later supports this.
  522. config SMB_NLS_REMOTE
  523. string "Default Remote NLS Option"
  524. depends on SMB_NLS_DEFAULT
  525. default "cp437"
  526. help
  527. This setting allows you to specify a default value for which
  528. codepage the server uses. If this field is left blank no
  529. translations will be done by default. The local codepage/charset
  530. default to CONFIG_NLS_DEFAULT.
  531. The nls settings can be changed at mount time, if your smbmount
  532. supports that, using the codepage and iocharset parameters.
  533. smbmount from samba 2.2.0 or later supports this.
  534. source "fs/cifs/Kconfig"
  535. config NCP_FS
  536. tristate "NCP file system support (to mount NetWare volumes)"
  537. depends on IPX!=n || INET
  538. help
  539. NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
  540. used by Novell NetWare clients to talk to file servers. It is to
  541. IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
  542. to mount NetWare file server volumes and to access them just like
  543. any other Unix directory. For details, please read the file
  544. <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
  545. the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
  546. You do not have to say Y here if you want your Linux box to act as a
  547. file *server* for Novell NetWare clients.
  548. General information about how to connect Linux, Windows machines and
  549. Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
  550. To compile this as a module, choose M here: the module will be called
  551. ncpfs. Say N unless you are connected to a Novell network.
  552. source "fs/ncpfs/Kconfig"
  553. config CODA_FS
  554. tristate "Coda file system support (advanced network fs)"
  555. depends on INET
  556. help
  557. Coda is an advanced network file system, similar to NFS in that it
  558. enables you to mount file systems of a remote server and access them
  559. with regular Unix commands as if they were sitting on your hard
  560. disk. Coda has several advantages over NFS: support for
  561. disconnected operation (e.g. for laptops), read/write server
  562. replication, security model for authentication and encryption,
  563. persistent client caches and write back caching.
  564. If you say Y here, your Linux box will be able to act as a Coda
  565. *client*. You will need user level code as well, both for the
  566. client and server. Servers are currently user level, i.e. they need
  567. no kernel support. Please read
  568. <file:Documentation/filesystems/coda.txt> and check out the Coda
  569. home page <http://www.coda.cs.cmu.edu/>.
  570. To compile the coda client support as a module, choose M here: the
  571. module will be called coda.
  572. config AFS_FS
  573. tristate "Andrew File System support (AFS) (EXPERIMENTAL)"
  574. depends on INET && EXPERIMENTAL
  575. select AF_RXRPC
  576. help
  577. If you say Y here, you will get an experimental Andrew File System
  578. driver. It currently only supports unsecured read-only AFS access.
  579. See <file:Documentation/filesystems/afs.txt> for more information.
  580. If unsure, say N.
  581. config AFS_DEBUG
  582. bool "AFS dynamic debugging"
  583. depends on AFS_FS
  584. help
  585. Say Y here to make runtime controllable debugging messages appear.
  586. See <file:Documentation/filesystems/afs.txt> for more information.
  587. If unsure, say N.
  588. config 9P_FS
  589. tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
  590. depends on INET && NET_9P && EXPERIMENTAL
  591. help
  592. If you say Y here, you will get experimental support for
  593. Plan 9 resource sharing via the 9P2000 protocol.
  594. See <http://v9fs.sf.net> for more information.
  595. If unsure, say N.
  596. endif # NETWORK_FILESYSTEMS
  597. if BLOCK
  598. menu "Partition Types"
  599. source "fs/partitions/Kconfig"
  600. endmenu
  601. endif
  602. source "fs/nls/Kconfig"
  603. source "fs/dlm/Kconfig"
  604. endmenu