Kconfig 27 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844
  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. config VXFS_FS
  173. tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
  174. depends on BLOCK
  175. help
  176. FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
  177. file system format. VERITAS VxFS(TM) is the standard file system
  178. of SCO UnixWare (and possibly others) and optionally available
  179. for Sunsoft Solaris, HP-UX and many other operating systems.
  180. Currently only readonly access is supported.
  181. NOTE: the file system type as used by mount(1), mount(2) and
  182. fstab(5) is 'vxfs' as it describes the file system format, not
  183. the actual driver.
  184. To compile this as a module, choose M here: the module will be
  185. called freevxfs. If unsure, say N.
  186. config MINIX_FS
  187. tristate "Minix file system support"
  188. depends on BLOCK
  189. help
  190. Minix is a simple operating system used in many classes about OS's.
  191. The minix file system (method to organize files on a hard disk
  192. partition or a floppy disk) was the original file system for Linux,
  193. but has been superseded by the second extended file system ext2fs.
  194. You don't want to use the minix file system on your hard disk
  195. because of certain built-in restrictions, but it is sometimes found
  196. on older Linux floppy disks. This option will enlarge your kernel
  197. by about 28 KB. If unsure, say N.
  198. To compile this file system support as a module, choose M here: the
  199. module will be called minix. Note that the file system of your root
  200. partition (the one containing the directory /) cannot be compiled as
  201. a module.
  202. config OMFS_FS
  203. tristate "SonicBlue Optimized MPEG File System support"
  204. depends on BLOCK
  205. select CRC_ITU_T
  206. help
  207. This is the proprietary file system used by the Rio Karma music
  208. player and ReplayTV DVR. Despite the name, this filesystem is not
  209. more efficient than a standard FS for MPEG files, in fact likely
  210. the opposite is true. Say Y if you have either of these devices
  211. and wish to mount its disk.
  212. To compile this file system support as a module, choose M here: the
  213. module will be called omfs. If unsure, say N.
  214. config HPFS_FS
  215. tristate "OS/2 HPFS file system support"
  216. depends on BLOCK
  217. help
  218. OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
  219. is the file system used for organizing files on OS/2 hard disk
  220. partitions. Say Y if you want to be able to read files from and
  221. write files to an OS/2 HPFS partition on your hard drive. OS/2
  222. floppies however are in regular MSDOS format, so you don't need this
  223. option in order to be able to read them. Read
  224. <file:Documentation/filesystems/hpfs.txt>.
  225. To compile this file system support as a module, choose M here: the
  226. module will be called hpfs. If unsure, say N.
  227. config QNX4FS_FS
  228. tristate "QNX4 file system support (read only)"
  229. depends on BLOCK
  230. help
  231. This is the file system used by the real-time operating systems
  232. QNX 4 and QNX 6 (the latter is also called QNX RTP).
  233. Further information is available at <http://www.qnx.com/>.
  234. Say Y if you intend to mount QNX hard disks or floppies.
  235. Unless you say Y to "QNX4FS read-write support" below, you will
  236. only be able to read these file systems.
  237. To compile this file system support as a module, choose M here: the
  238. module will be called qnx4.
  239. If you don't know whether you need it, then you don't need it:
  240. answer N.
  241. config QNX4FS_RW
  242. bool "QNX4FS write support (DANGEROUS)"
  243. depends on QNX4FS_FS && EXPERIMENTAL && BROKEN
  244. help
  245. Say Y if you want to test write support for QNX4 file systems.
  246. It's currently broken, so for now:
  247. answer N.
  248. config ROMFS_FS
  249. tristate "ROM file system support"
  250. depends on BLOCK
  251. ---help---
  252. This is a very small read-only file system mainly intended for
  253. initial ram disks of installation disks, but it could be used for
  254. other read-only media as well. Read
  255. <file:Documentation/filesystems/romfs.txt> for details.
  256. To compile this file system support as a module, choose M here: the
  257. module will be called romfs. Note that the file system of your
  258. root partition (the one containing the directory /) cannot be a
  259. module.
  260. If you don't know whether you need it, then you don't need it:
  261. answer N.
  262. config SYSV_FS
  263. tristate "System V/Xenix/V7/Coherent file system support"
  264. depends on BLOCK
  265. help
  266. SCO, Xenix and Coherent are commercial Unix systems for Intel
  267. machines, and Version 7 was used on the DEC PDP-11. Saying Y
  268. here would allow you to read from their floppies and hard disk
  269. partitions.
  270. If you have floppies or hard disk partitions like that, it is likely
  271. that they contain binaries from those other Unix systems; in order
  272. to run these binaries, you will want to install linux-abi which is
  273. a set of kernel modules that lets you run SCO, Xenix, Wyse,
  274. UnixWare, Dell Unix and System V programs under Linux. It is
  275. available via FTP (user: ftp) from
  276. <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
  277. NOTE: that will work only for binaries from Intel-based systems;
  278. PDP ones will have to wait until somebody ports Linux to -11 ;-)
  279. If you only intend to mount files from some other Unix over the
  280. network using NFS, you don't need the System V file system support
  281. (but you need NFS file system support obviously).
  282. Note that this option is generally not needed for floppies, since a
  283. good portable way to transport files and directories between unixes
  284. (and even other operating systems) is given by the tar program ("man
  285. tar" or preferably "info tar"). Note also that this option has
  286. nothing whatsoever to do with the option "System V IPC". Read about
  287. the System V file system in
  288. <file:Documentation/filesystems/sysv-fs.txt>.
  289. Saying Y here will enlarge your kernel by about 27 KB.
  290. To compile this as a module, choose M here: the module will be called
  291. sysv.
  292. If you haven't heard about all of this before, it's safe to say N.
  293. config UFS_FS
  294. tristate "UFS file system support (read only)"
  295. depends on BLOCK
  296. help
  297. BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
  298. OpenBSD and NeXTstep) use a file system called UFS. Some System V
  299. Unixes can create and mount hard disk partitions and diskettes using
  300. this file system as well. Saying Y here will allow you to read from
  301. these partitions; if you also want to write to them, say Y to the
  302. experimental "UFS file system write support", below. Please read the
  303. file <file:Documentation/filesystems/ufs.txt> for more information.
  304. The recently released UFS2 variant (used in FreeBSD 5.x) is
  305. READ-ONLY supported.
  306. Note that this option is generally not needed for floppies, since a
  307. good portable way to transport files and directories between unixes
  308. (and even other operating systems) is given by the tar program ("man
  309. tar" or preferably "info tar").
  310. When accessing NeXTstep files, you may need to convert them from the
  311. NeXT character set to the Latin1 character set; use the program
  312. recode ("info recode") for this purpose.
  313. To compile the UFS file system support as a module, choose M here: the
  314. module will be called ufs.
  315. If you haven't heard about all of this before, it's safe to say N.
  316. config UFS_FS_WRITE
  317. bool "UFS file system write support (DANGEROUS)"
  318. depends on UFS_FS && EXPERIMENTAL
  319. help
  320. Say Y here if you want to try writing to UFS partitions. This is
  321. experimental, so you should back up your UFS partitions beforehand.
  322. config UFS_DEBUG
  323. bool "UFS debugging"
  324. depends on UFS_FS
  325. help
  326. If you are experiencing any problems with the UFS filesystem, say
  327. Y here. This will result in _many_ additional debugging messages to be
  328. written to the system log.
  329. endif # MISC_FILESYSTEMS
  330. menuconfig NETWORK_FILESYSTEMS
  331. bool "Network File Systems"
  332. default y
  333. depends on NET
  334. ---help---
  335. Say Y here to get to see options for network filesystems and
  336. filesystem-related networking code, such as NFS daemon and
  337. RPCSEC security modules.
  338. This option alone does not add any kernel code.
  339. If you say N, all options in this submenu will be skipped and
  340. disabled; if unsure, say Y here.
  341. if NETWORK_FILESYSTEMS
  342. config NFS_FS
  343. tristate "NFS client support"
  344. depends on INET
  345. select LOCKD
  346. select SUNRPC
  347. select NFS_ACL_SUPPORT if NFS_V3_ACL
  348. help
  349. Choose Y here if you want to access files residing on other
  350. computers using Sun's Network File System protocol. To compile
  351. this file system support as a module, choose M here: the module
  352. will be called nfs.
  353. To mount file systems exported by NFS servers, you also need to
  354. install the user space mount.nfs command which can be found in
  355. the Linux nfs-utils package, available from http://linux-nfs.org/.
  356. Information about using the mount command is available in the
  357. mount(8) man page. More detail about the Linux NFS client
  358. implementation is available via the nfs(5) man page.
  359. Below you can choose which versions of the NFS protocol are
  360. available in the kernel to mount NFS servers. Support for NFS
  361. version 2 (RFC 1094) is always available when NFS_FS is selected.
  362. To configure a system which mounts its root file system via NFS
  363. at boot time, say Y here, select "Kernel level IP
  364. autoconfiguration" in the NETWORK menu, and select "Root file
  365. system on NFS" below. You cannot compile this file system as a
  366. module in this case.
  367. If unsure, say N.
  368. config NFS_V3
  369. bool "NFS client support for NFS version 3"
  370. depends on NFS_FS
  371. help
  372. This option enables support for version 3 of the NFS protocol
  373. (RFC 1813) in the kernel's NFS client.
  374. If unsure, say Y.
  375. config NFS_V3_ACL
  376. bool "NFS client support for the NFSv3 ACL protocol extension"
  377. depends on NFS_V3
  378. help
  379. Some NFS servers support an auxiliary NFSv3 ACL protocol that
  380. Sun added to Solaris but never became an official part of the
  381. NFS version 3 protocol. This protocol extension allows
  382. applications on NFS clients to manipulate POSIX Access Control
  383. Lists on files residing on NFS servers. NFS servers enforce
  384. ACLs on local files whether this protocol is available or not.
  385. Choose Y here if your NFS server supports the Solaris NFSv3 ACL
  386. protocol extension and you want your NFS client to allow
  387. applications to access and modify ACLs on files on the server.
  388. Most NFS servers don't support the Solaris NFSv3 ACL protocol
  389. extension. You can choose N here or specify the "noacl" mount
  390. option to prevent your NFS client from trying to use the NFSv3
  391. ACL protocol.
  392. If unsure, say N.
  393. config NFS_V4
  394. bool "NFS client support for NFS version 4 (EXPERIMENTAL)"
  395. depends on NFS_FS && EXPERIMENTAL
  396. select RPCSEC_GSS_KRB5
  397. help
  398. This option enables support for version 4 of the NFS protocol
  399. (RFC 3530) in the kernel's NFS client.
  400. To mount NFS servers using NFSv4, you also need to install user
  401. space programs which can be found in the Linux nfs-utils package,
  402. available from http://linux-nfs.org/.
  403. If unsure, say N.
  404. config ROOT_NFS
  405. bool "Root file system on NFS"
  406. depends on NFS_FS=y && IP_PNP
  407. help
  408. If you want your system to mount its root file system via NFS,
  409. choose Y here. This is common practice for managing systems
  410. without local permanent storage. For details, read
  411. <file:Documentation/filesystems/nfsroot.txt>.
  412. Most people say N here.
  413. config NFSD
  414. tristate "NFS server support"
  415. depends on INET
  416. select LOCKD
  417. select SUNRPC
  418. select EXPORTFS
  419. select NFS_ACL_SUPPORT if NFSD_V2_ACL
  420. help
  421. Choose Y here if you want to allow other computers to access
  422. files residing on this system using Sun's Network File System
  423. protocol. To compile the NFS server support as a module,
  424. choose M here: the module will be called nfsd.
  425. You may choose to use a user-space NFS server instead, in which
  426. case you can choose N here.
  427. To export local file systems using NFS, you also need to install
  428. user space programs which can be found in the Linux nfs-utils
  429. package, available from http://linux-nfs.org/. More detail about
  430. the Linux NFS server implementation is available via the
  431. exports(5) man page.
  432. Below you can choose which versions of the NFS protocol are
  433. available to clients mounting the NFS server on this system.
  434. Support for NFS version 2 (RFC 1094) is always available when
  435. CONFIG_NFSD is selected.
  436. If unsure, say N.
  437. config NFSD_V2_ACL
  438. bool
  439. depends on NFSD
  440. config NFSD_V3
  441. bool "NFS server support for NFS version 3"
  442. depends on NFSD
  443. help
  444. This option enables support in your system's NFS server for
  445. version 3 of the NFS protocol (RFC 1813).
  446. If unsure, say Y.
  447. config NFSD_V3_ACL
  448. bool "NFS server support for the NFSv3 ACL protocol extension"
  449. depends on NFSD_V3
  450. select NFSD_V2_ACL
  451. help
  452. Solaris NFS servers support an auxiliary NFSv3 ACL protocol that
  453. never became an official part of the NFS version 3 protocol.
  454. This protocol extension allows applications on NFS clients to
  455. manipulate POSIX Access Control Lists on files residing on NFS
  456. servers. NFS servers enforce POSIX ACLs on local files whether
  457. this protocol is available or not.
  458. This option enables support in your system's NFS server for the
  459. NFSv3 ACL protocol extension allowing NFS clients to manipulate
  460. POSIX ACLs on files exported by your system's NFS server. NFS
  461. clients which support the Solaris NFSv3 ACL protocol can then
  462. access and modify ACLs on your NFS server.
  463. To store ACLs on your NFS server, you also need to enable ACL-
  464. related CONFIG options for your local file systems of choice.
  465. If unsure, say N.
  466. config NFSD_V4
  467. bool "NFS server support for NFS version 4 (EXPERIMENTAL)"
  468. depends on NFSD && PROC_FS && EXPERIMENTAL
  469. select NFSD_V3
  470. select FS_POSIX_ACL
  471. select RPCSEC_GSS_KRB5
  472. help
  473. This option enables support in your system's NFS server for
  474. version 4 of the NFS protocol (RFC 3530).
  475. To export files using NFSv4, you need to install additional user
  476. space programs which can be found in the Linux nfs-utils package,
  477. available from http://linux-nfs.org/.
  478. If unsure, say N.
  479. config LOCKD
  480. tristate
  481. config LOCKD_V4
  482. bool
  483. depends on NFSD_V3 || NFS_V3
  484. default y
  485. config EXPORTFS
  486. tristate
  487. config NFS_ACL_SUPPORT
  488. tristate
  489. select FS_POSIX_ACL
  490. config NFS_COMMON
  491. bool
  492. depends on NFSD || NFS_FS
  493. default y
  494. config SUNRPC
  495. tristate
  496. config SUNRPC_GSS
  497. tristate
  498. config SUNRPC_XPRT_RDMA
  499. tristate
  500. depends on SUNRPC && INFINIBAND && EXPERIMENTAL
  501. default SUNRPC && INFINIBAND
  502. help
  503. This option enables an RPC client transport capability that
  504. allows the NFS client to mount servers via an RDMA-enabled
  505. transport.
  506. To compile RPC client RDMA transport support as a module,
  507. choose M here: the module will be called xprtrdma.
  508. If unsure, say N.
  509. config SUNRPC_REGISTER_V4
  510. bool "Register local RPC services via rpcbind v4 (EXPERIMENTAL)"
  511. depends on SUNRPC && EXPERIMENTAL
  512. default n
  513. help
  514. Sun added support for registering RPC services at an IPv6
  515. address by creating two new versions of the rpcbind protocol
  516. (RFC 1833).
  517. This option enables support in the kernel RPC server for
  518. registering kernel RPC services via version 4 of the rpcbind
  519. protocol. If you enable this option, you must run a portmapper
  520. daemon that supports rpcbind protocol version 4.
  521. Serving NFS over IPv6 from knfsd (the kernel's NFS server)
  522. requires that you enable this option and use a portmapper that
  523. supports rpcbind version 4.
  524. If unsure, say N to get traditional behavior (register kernel
  525. RPC services using only rpcbind version 2). Distributions
  526. using the legacy Linux portmapper daemon must say N here.
  527. config RPCSEC_GSS_KRB5
  528. tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
  529. depends on SUNRPC && EXPERIMENTAL
  530. select SUNRPC_GSS
  531. select CRYPTO
  532. select CRYPTO_MD5
  533. select CRYPTO_DES
  534. select CRYPTO_CBC
  535. help
  536. Choose Y here to enable Secure RPC using the Kerberos version 5
  537. GSS-API mechanism (RFC 1964).
  538. Secure RPC calls with Kerberos require an auxiliary user-space
  539. daemon which may be found in the Linux nfs-utils package
  540. available from http://linux-nfs.org/. In addition, user-space
  541. Kerberos support should be installed.
  542. If unsure, say N.
  543. config RPCSEC_GSS_SPKM3
  544. tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
  545. depends on SUNRPC && EXPERIMENTAL
  546. select SUNRPC_GSS
  547. select CRYPTO
  548. select CRYPTO_MD5
  549. select CRYPTO_DES
  550. select CRYPTO_CAST5
  551. select CRYPTO_CBC
  552. help
  553. Choose Y here to enable Secure RPC using the SPKM3 public key
  554. GSS-API mechansim (RFC 2025).
  555. Secure RPC calls with SPKM3 require an auxiliary userspace
  556. daemon which may be found in the Linux nfs-utils package
  557. available from http://linux-nfs.org/.
  558. If unsure, say N.
  559. config SMB_FS
  560. tristate "SMB file system support (OBSOLETE, please use CIFS)"
  561. depends on INET
  562. select NLS
  563. help
  564. SMB (Server Message Block) is the protocol Windows for Workgroups
  565. (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
  566. files and printers over local networks. Saying Y here allows you to
  567. mount their file systems (often called "shares" in this context) and
  568. access them just like any other Unix directory. Currently, this
  569. works only if the Windows machines use TCP/IP as the underlying
  570. transport protocol, and not NetBEUI. For details, read
  571. <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
  572. available from <http://www.tldp.org/docs.html#howto>.
  573. Note: if you just want your box to act as an SMB *server* and make
  574. files and printing services available to Windows clients (which need
  575. to have a TCP/IP stack), you don't need to say Y here; you can use
  576. the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
  577. for that.
  578. General information about how to connect Linux, Windows machines and
  579. Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
  580. To compile the SMB support as a module, choose M here:
  581. the module will be called smbfs. Most people say N, however.
  582. config SMB_NLS_DEFAULT
  583. bool "Use a default NLS"
  584. depends on SMB_FS
  585. help
  586. Enabling this will make smbfs use nls translations by default. You
  587. need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
  588. settings and you need to give the default nls for the SMB server as
  589. CONFIG_SMB_NLS_REMOTE.
  590. The nls settings can be changed at mount time, if your smbmount
  591. supports that, using the codepage and iocharset parameters.
  592. smbmount from samba 2.2.0 or later supports this.
  593. config SMB_NLS_REMOTE
  594. string "Default Remote NLS Option"
  595. depends on SMB_NLS_DEFAULT
  596. default "cp437"
  597. help
  598. This setting allows you to specify a default value for which
  599. codepage the server uses. If this field is left blank no
  600. translations will be done by default. The local codepage/charset
  601. default to CONFIG_NLS_DEFAULT.
  602. The nls settings can be changed at mount time, if your smbmount
  603. supports that, using the codepage and iocharset parameters.
  604. smbmount from samba 2.2.0 or later supports this.
  605. source "fs/cifs/Kconfig"
  606. config NCP_FS
  607. tristate "NCP file system support (to mount NetWare volumes)"
  608. depends on IPX!=n || INET
  609. help
  610. NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
  611. used by Novell NetWare clients to talk to file servers. It is to
  612. IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
  613. to mount NetWare file server volumes and to access them just like
  614. any other Unix directory. For details, please read the file
  615. <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
  616. the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
  617. You do not have to say Y here if you want your Linux box to act as a
  618. file *server* for Novell NetWare clients.
  619. General information about how to connect Linux, Windows machines and
  620. Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
  621. To compile this as a module, choose M here: the module will be called
  622. ncpfs. Say N unless you are connected to a Novell network.
  623. source "fs/ncpfs/Kconfig"
  624. config CODA_FS
  625. tristate "Coda file system support (advanced network fs)"
  626. depends on INET
  627. help
  628. Coda is an advanced network file system, similar to NFS in that it
  629. enables you to mount file systems of a remote server and access them
  630. with regular Unix commands as if they were sitting on your hard
  631. disk. Coda has several advantages over NFS: support for
  632. disconnected operation (e.g. for laptops), read/write server
  633. replication, security model for authentication and encryption,
  634. persistent client caches and write back caching.
  635. If you say Y here, your Linux box will be able to act as a Coda
  636. *client*. You will need user level code as well, both for the
  637. client and server. Servers are currently user level, i.e. they need
  638. no kernel support. Please read
  639. <file:Documentation/filesystems/coda.txt> and check out the Coda
  640. home page <http://www.coda.cs.cmu.edu/>.
  641. To compile the coda client support as a module, choose M here: the
  642. module will be called coda.
  643. config AFS_FS
  644. tristate "Andrew File System support (AFS) (EXPERIMENTAL)"
  645. depends on INET && EXPERIMENTAL
  646. select AF_RXRPC
  647. help
  648. If you say Y here, you will get an experimental Andrew File System
  649. driver. It currently only supports unsecured read-only AFS access.
  650. See <file:Documentation/filesystems/afs.txt> for more information.
  651. If unsure, say N.
  652. config AFS_DEBUG
  653. bool "AFS dynamic debugging"
  654. depends on AFS_FS
  655. help
  656. Say Y here to make runtime controllable debugging messages appear.
  657. See <file:Documentation/filesystems/afs.txt> for more information.
  658. If unsure, say N.
  659. config 9P_FS
  660. tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
  661. depends on INET && NET_9P && EXPERIMENTAL
  662. help
  663. If you say Y here, you will get experimental support for
  664. Plan 9 resource sharing via the 9P2000 protocol.
  665. See <http://v9fs.sf.net> for more information.
  666. If unsure, say N.
  667. endif # NETWORK_FILESYSTEMS
  668. if BLOCK
  669. menu "Partition Types"
  670. source "fs/partitions/Kconfig"
  671. endmenu
  672. endif
  673. source "fs/nls/Kconfig"
  674. source "fs/dlm/Kconfig"
  675. endmenu