Kconfig 33 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192939495969798991001011021031041051061071081091101111121131141151161171181191201211221231241251261271281291301311321331341351361371381391401411421431441451461471481491501511521531541551561571581591601611621631641651661671681691701711721731741751761771781791801811821831841851861871881891901911921931941951961971981992002012022032042052062072082092102112122132142152162172182192202212222232242252262272282292302312322332342352362372382392402412422432442452462472482492502512522532542552562572582592602612622632642652662672682692702712722732742752762772782792802812822832842852862872882892902912922932942952962972982993003013023033043053063073083093103113123133143153163173183193203213223233243253263273283293303313323333343353363373383393403413423433443453463473483493503513523533543553563573583593603613623633643653663673683693703713723733743753763773783793803813823833843853863873883893903913923933943953963973983994004014024034044054064074084094104114124134144154164174184194204214224234244254264274284294304314324334344354364374384394404414424434444454464474484494504514524534544554564574584594604614624634644654664674684694704714724734744754764774784794804814824834844854864874884894904914924934944954964974984995005015025035045055065075085095105115125135145155165175185195205215225235245255265275285295305315325335345355365375385395405415425435445455465475485495505515525535545555565575585595605615625635645655665675685695705715725735745755765775785795805815825835845855865875885895905915925935945955965975985996006016026036046056066076086096106116126136146156166176186196206216226236246256266276286296306316326336346356366376386396406416426436446456466476486496506516526536546556566576586596606616626636646656666676686696706716726736746756766776786796806816826836846856866876886896906916926936946956966976986997007017027037047057067077087097107117127137147157167177187197207217227237247257267277287297307317327337347357367377387397407417427437447457467477487497507517527537547557567577587597607617627637647657667677687697707717727737747757767777787797807817827837847857867877887897907917927937947957967977987998008018028038048058068078088098108118128138148158168178188198208218228238248258268278288298308318328338348358368378388398408418428438448458468478488498508518528538548558568578588598608618628638648658668678688698708718728738748758768778788798808818828838848858868878888898908918928938948958968978988999009019029039049059069079089099109119129139149159169179189199209219229239249259269279289299309319329339349359369379389399409419429439449459469479489499509519529539549559569579589599609619629639649659669679689699709719729739749759769779789799809819829839849859869879889899909919929939949959969979989991000100110021003100410051006100710081009101010111012
  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. config ECRYPT_FS
  162. tristate "eCrypt filesystem layer support (EXPERIMENTAL)"
  163. depends on EXPERIMENTAL && KEYS && CRYPTO && NET
  164. help
  165. Encrypted filesystem that operates on the VFS layer. See
  166. <file:Documentation/filesystems/ecryptfs.txt> to learn more about
  167. eCryptfs. Userspace components are required and can be
  168. obtained from <http://ecryptfs.sf.net>.
  169. To compile this file system support as a module, choose M here: the
  170. module will be called ecryptfs.
  171. config HFS_FS
  172. tristate "Apple Macintosh file system support (EXPERIMENTAL)"
  173. depends on BLOCK && EXPERIMENTAL
  174. select NLS
  175. help
  176. If you say Y here, you will be able to mount Macintosh-formatted
  177. floppy disks and hard drive partitions with full read-write access.
  178. Please read <file:Documentation/filesystems/hfs.txt> to learn about
  179. the available mount options.
  180. To compile this file system support as a module, choose M here: the
  181. module will be called hfs.
  182. config HFSPLUS_FS
  183. tristate "Apple Extended HFS file system support"
  184. depends on BLOCK
  185. select NLS
  186. select NLS_UTF8
  187. help
  188. If you say Y here, you will be able to mount extended format
  189. Macintosh-formatted hard drive partitions with full read-write access.
  190. This file system is often called HFS+ and was introduced with
  191. MacOS 8. It includes all Mac specific filesystem data such as
  192. data forks and creator codes, but it also has several UNIX
  193. style features such as file ownership and permissions.
  194. config BEFS_FS
  195. tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)"
  196. depends on BLOCK && EXPERIMENTAL
  197. select NLS
  198. help
  199. The BeOS File System (BeFS) is the native file system of Be, Inc's
  200. BeOS. Notable features include support for arbitrary attributes
  201. on files and directories, and database-like indices on selected
  202. attributes. (Also note that this driver doesn't make those features
  203. available at this time). It is a 64 bit filesystem, so it supports
  204. extremely large volumes and files.
  205. If you use this filesystem, you should also say Y to at least one
  206. of the NLS (native language support) options below.
  207. If you don't know what this is about, say N.
  208. To compile this as a module, choose M here: the module will be
  209. called befs.
  210. config BEFS_DEBUG
  211. bool "Debug BeFS"
  212. depends on BEFS_FS
  213. help
  214. If you say Y here, you can use the 'debug' mount option to enable
  215. debugging output from the driver.
  216. config BFS_FS
  217. tristate "BFS file system support (EXPERIMENTAL)"
  218. depends on BLOCK && EXPERIMENTAL
  219. help
  220. Boot File System (BFS) is a file system used under SCO UnixWare to
  221. allow the bootloader access to the kernel image and other important
  222. files during the boot process. It is usually mounted under /stand
  223. and corresponds to the slice marked as "STAND" in the UnixWare
  224. partition. You should say Y if you want to read or write the files
  225. on your /stand slice from within Linux. You then also need to say Y
  226. to "UnixWare slices support", below. More information about the BFS
  227. file system is contained in the file
  228. <file:Documentation/filesystems/bfs.txt>.
  229. If you don't know what this is about, say N.
  230. To compile this as a module, choose M here: the module will be called
  231. bfs. Note that the file system of your root partition (the one
  232. containing the directory /) cannot be compiled as a module.
  233. config EFS_FS
  234. tristate "EFS file system support (read only) (EXPERIMENTAL)"
  235. depends on BLOCK && EXPERIMENTAL
  236. help
  237. EFS is an older file system used for non-ISO9660 CD-ROMs and hard
  238. disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
  239. uses the XFS file system for hard disk partitions however).
  240. This implementation only offers read-only access. If you don't know
  241. what all this is about, it's safe to say N. For more information
  242. about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
  243. To compile the EFS file system support as a module, choose M here: the
  244. module will be called efs.
  245. source "fs/jffs2/Kconfig"
  246. # UBIFS File system configuration
  247. source "fs/ubifs/Kconfig"
  248. config CRAMFS
  249. tristate "Compressed ROM file system support (cramfs)"
  250. depends on BLOCK
  251. select ZLIB_INFLATE
  252. help
  253. Saying Y here includes support for CramFs (Compressed ROM File
  254. System). CramFs is designed to be a simple, small, and compressed
  255. file system for ROM based embedded systems. CramFs is read-only,
  256. limited to 256MB file systems (with 16MB files), and doesn't support
  257. 16/32 bits uid/gid, hard links and timestamps.
  258. See <file:Documentation/filesystems/cramfs.txt> and
  259. <file:fs/cramfs/README> for further information.
  260. To compile this as a module, choose M here: the module will be called
  261. cramfs. Note that the root file system (the one containing the
  262. directory /) cannot be compiled as a module.
  263. If unsure, say N.
  264. config SQUASHFS
  265. tristate "SquashFS 4.0 - Squashed file system support"
  266. depends on BLOCK
  267. select ZLIB_INFLATE
  268. help
  269. Saying Y here includes support for SquashFS 4.0 (a Compressed
  270. Read-Only File System). Squashfs is a highly compressed read-only
  271. filesystem for Linux. It uses zlib compression to compress both
  272. files, inodes and directories. Inodes in the system are very small
  273. and all blocks are packed to minimise data overhead. Block sizes
  274. greater than 4K are supported up to a maximum of 1 Mbytes (default
  275. block size 128K). SquashFS 4.0 supports 64 bit filesystems and files
  276. (larger than 4GB), full uid/gid information, hard links and
  277. timestamps.
  278. Squashfs is intended for general read-only filesystem use, for
  279. archival use (i.e. in cases where a .tar.gz file may be used), and in
  280. embedded systems where low overhead is needed. Further information
  281. and tools are available from http://squashfs.sourceforge.net.
  282. If you want to compile this as a module ( = code which can be
  283. inserted in and removed from the running kernel whenever you want),
  284. say M here and read <file:Documentation/modules.txt>. The module
  285. will be called squashfs. Note that the root file system (the one
  286. containing the directory /) cannot be compiled as a module.
  287. If unsure, say N.
  288. config SQUASHFS_EMBEDDED
  289. bool "Additional option for memory-constrained systems"
  290. depends on SQUASHFS
  291. default n
  292. help
  293. Saying Y here allows you to specify cache size.
  294. If unsure, say N.
  295. config SQUASHFS_FRAGMENT_CACHE_SIZE
  296. int "Number of fragments cached" if SQUASHFS_EMBEDDED
  297. depends on SQUASHFS
  298. default "3"
  299. help
  300. By default SquashFS caches the last 3 fragments read from
  301. the filesystem. Increasing this amount may mean SquashFS
  302. has to re-read fragments less often from disk, at the expense
  303. of extra system memory. Decreasing this amount will mean
  304. SquashFS uses less memory at the expense of extra reads from disk.
  305. Note there must be at least one cached fragment. Anything
  306. much more than three will probably not make much difference.
  307. config VXFS_FS
  308. tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
  309. depends on BLOCK
  310. help
  311. FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
  312. file system format. VERITAS VxFS(TM) is the standard file system
  313. of SCO UnixWare (and possibly others) and optionally available
  314. for Sunsoft Solaris, HP-UX and many other operating systems.
  315. Currently only readonly access is supported.
  316. NOTE: the file system type as used by mount(1), mount(2) and
  317. fstab(5) is 'vxfs' as it describes the file system format, not
  318. the actual driver.
  319. To compile this as a module, choose M here: the module will be
  320. called freevxfs. If unsure, say N.
  321. config MINIX_FS
  322. tristate "Minix file system support"
  323. depends on BLOCK
  324. help
  325. Minix is a simple operating system used in many classes about OS's.
  326. The minix file system (method to organize files on a hard disk
  327. partition or a floppy disk) was the original file system for Linux,
  328. but has been superseded by the second extended file system ext2fs.
  329. You don't want to use the minix file system on your hard disk
  330. because of certain built-in restrictions, but it is sometimes found
  331. on older Linux floppy disks. This option will enlarge your kernel
  332. by about 28 KB. If unsure, say N.
  333. To compile this file system support as a module, choose M here: the
  334. module will be called minix. Note that the file system of your root
  335. partition (the one containing the directory /) cannot be compiled as
  336. a module.
  337. config OMFS_FS
  338. tristate "SonicBlue Optimized MPEG File System support"
  339. depends on BLOCK
  340. select CRC_ITU_T
  341. help
  342. This is the proprietary file system used by the Rio Karma music
  343. player and ReplayTV DVR. Despite the name, this filesystem is not
  344. more efficient than a standard FS for MPEG files, in fact likely
  345. the opposite is true. Say Y if you have either of these devices
  346. and wish to mount its disk.
  347. To compile this file system support as a module, choose M here: the
  348. module will be called omfs. If unsure, say N.
  349. config HPFS_FS
  350. tristate "OS/2 HPFS file system support"
  351. depends on BLOCK
  352. help
  353. OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
  354. is the file system used for organizing files on OS/2 hard disk
  355. partitions. Say Y if you want to be able to read files from and
  356. write files to an OS/2 HPFS partition on your hard drive. OS/2
  357. floppies however are in regular MSDOS format, so you don't need this
  358. option in order to be able to read them. Read
  359. <file:Documentation/filesystems/hpfs.txt>.
  360. To compile this file system support as a module, choose M here: the
  361. module will be called hpfs. If unsure, say N.
  362. config QNX4FS_FS
  363. tristate "QNX4 file system support (read only)"
  364. depends on BLOCK
  365. help
  366. This is the file system used by the real-time operating systems
  367. QNX 4 and QNX 6 (the latter is also called QNX RTP).
  368. Further information is available at <http://www.qnx.com/>.
  369. Say Y if you intend to mount QNX hard disks or floppies.
  370. Unless you say Y to "QNX4FS read-write support" below, you will
  371. only be able to read these file systems.
  372. To compile this file system support as a module, choose M here: the
  373. module will be called qnx4.
  374. If you don't know whether you need it, then you don't need it:
  375. answer N.
  376. config QNX4FS_RW
  377. bool "QNX4FS write support (DANGEROUS)"
  378. depends on QNX4FS_FS && EXPERIMENTAL && BROKEN
  379. help
  380. Say Y if you want to test write support for QNX4 file systems.
  381. It's currently broken, so for now:
  382. answer N.
  383. config ROMFS_FS
  384. tristate "ROM file system support"
  385. depends on BLOCK
  386. ---help---
  387. This is a very small read-only file system mainly intended for
  388. initial ram disks of installation disks, but it could be used for
  389. other read-only media as well. Read
  390. <file:Documentation/filesystems/romfs.txt> for details.
  391. To compile this file system support as a module, choose M here: the
  392. module will be called romfs. Note that the file system of your
  393. root partition (the one containing the directory /) cannot be a
  394. module.
  395. If you don't know whether you need it, then you don't need it:
  396. answer N.
  397. config SYSV_FS
  398. tristate "System V/Xenix/V7/Coherent file system support"
  399. depends on BLOCK
  400. help
  401. SCO, Xenix and Coherent are commercial Unix systems for Intel
  402. machines, and Version 7 was used on the DEC PDP-11. Saying Y
  403. here would allow you to read from their floppies and hard disk
  404. partitions.
  405. If you have floppies or hard disk partitions like that, it is likely
  406. that they contain binaries from those other Unix systems; in order
  407. to run these binaries, you will want to install linux-abi which is
  408. a set of kernel modules that lets you run SCO, Xenix, Wyse,
  409. UnixWare, Dell Unix and System V programs under Linux. It is
  410. available via FTP (user: ftp) from
  411. <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
  412. NOTE: that will work only for binaries from Intel-based systems;
  413. PDP ones will have to wait until somebody ports Linux to -11 ;-)
  414. If you only intend to mount files from some other Unix over the
  415. network using NFS, you don't need the System V file system support
  416. (but you need NFS file system support obviously).
  417. Note that this option is generally not needed for floppies, since a
  418. good portable way to transport files and directories between unixes
  419. (and even other operating systems) is given by the tar program ("man
  420. tar" or preferably "info tar"). Note also that this option has
  421. nothing whatsoever to do with the option "System V IPC". Read about
  422. the System V file system in
  423. <file:Documentation/filesystems/sysv-fs.txt>.
  424. Saying Y here will enlarge your kernel by about 27 KB.
  425. To compile this as a module, choose M here: the module will be called
  426. sysv.
  427. If you haven't heard about all of this before, it's safe to say N.
  428. config UFS_FS
  429. tristate "UFS file system support (read only)"
  430. depends on BLOCK
  431. help
  432. BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
  433. OpenBSD and NeXTstep) use a file system called UFS. Some System V
  434. Unixes can create and mount hard disk partitions and diskettes using
  435. this file system as well. Saying Y here will allow you to read from
  436. these partitions; if you also want to write to them, say Y to the
  437. experimental "UFS file system write support", below. Please read the
  438. file <file:Documentation/filesystems/ufs.txt> for more information.
  439. The recently released UFS2 variant (used in FreeBSD 5.x) is
  440. READ-ONLY supported.
  441. Note that this option is generally not needed for floppies, since a
  442. good portable way to transport files and directories between unixes
  443. (and even other operating systems) is given by the tar program ("man
  444. tar" or preferably "info tar").
  445. When accessing NeXTstep files, you may need to convert them from the
  446. NeXT character set to the Latin1 character set; use the program
  447. recode ("info recode") for this purpose.
  448. To compile the UFS file system support as a module, choose M here: the
  449. module will be called ufs.
  450. If you haven't heard about all of this before, it's safe to say N.
  451. config UFS_FS_WRITE
  452. bool "UFS file system write support (DANGEROUS)"
  453. depends on UFS_FS && EXPERIMENTAL
  454. help
  455. Say Y here if you want to try writing to UFS partitions. This is
  456. experimental, so you should back up your UFS partitions beforehand.
  457. config UFS_DEBUG
  458. bool "UFS debugging"
  459. depends on UFS_FS
  460. help
  461. If you are experiencing any problems with the UFS filesystem, say
  462. Y here. This will result in _many_ additional debugging messages to be
  463. written to the system log.
  464. endif # MISC_FILESYSTEMS
  465. menuconfig NETWORK_FILESYSTEMS
  466. bool "Network File Systems"
  467. default y
  468. depends on NET
  469. ---help---
  470. Say Y here to get to see options for network filesystems and
  471. filesystem-related networking code, such as NFS daemon and
  472. RPCSEC security modules.
  473. This option alone does not add any kernel code.
  474. If you say N, all options in this submenu will be skipped and
  475. disabled; if unsure, say Y here.
  476. if NETWORK_FILESYSTEMS
  477. config NFS_FS
  478. tristate "NFS client support"
  479. depends on INET
  480. select LOCKD
  481. select SUNRPC
  482. select NFS_ACL_SUPPORT if NFS_V3_ACL
  483. help
  484. Choose Y here if you want to access files residing on other
  485. computers using Sun's Network File System protocol. To compile
  486. this file system support as a module, choose M here: the module
  487. will be called nfs.
  488. To mount file systems exported by NFS servers, you also need to
  489. install the user space mount.nfs command which can be found in
  490. the Linux nfs-utils package, available from http://linux-nfs.org/.
  491. Information about using the mount command is available in the
  492. mount(8) man page. More detail about the Linux NFS client
  493. implementation is available via the nfs(5) man page.
  494. Below you can choose which versions of the NFS protocol are
  495. available in the kernel to mount NFS servers. Support for NFS
  496. version 2 (RFC 1094) is always available when NFS_FS is selected.
  497. To configure a system which mounts its root file system via NFS
  498. at boot time, say Y here, select "Kernel level IP
  499. autoconfiguration" in the NETWORK menu, and select "Root file
  500. system on NFS" below. You cannot compile this file system as a
  501. module in this case.
  502. If unsure, say N.
  503. config NFS_V3
  504. bool "NFS client support for NFS version 3"
  505. depends on NFS_FS
  506. help
  507. This option enables support for version 3 of the NFS protocol
  508. (RFC 1813) in the kernel's NFS client.
  509. If unsure, say Y.
  510. config NFS_V3_ACL
  511. bool "NFS client support for the NFSv3 ACL protocol extension"
  512. depends on NFS_V3
  513. help
  514. Some NFS servers support an auxiliary NFSv3 ACL protocol that
  515. Sun added to Solaris but never became an official part of the
  516. NFS version 3 protocol. This protocol extension allows
  517. applications on NFS clients to manipulate POSIX Access Control
  518. Lists on files residing on NFS servers. NFS servers enforce
  519. ACLs on local files whether this protocol is available or not.
  520. Choose Y here if your NFS server supports the Solaris NFSv3 ACL
  521. protocol extension and you want your NFS client to allow
  522. applications to access and modify ACLs on files on the server.
  523. Most NFS servers don't support the Solaris NFSv3 ACL protocol
  524. extension. You can choose N here or specify the "noacl" mount
  525. option to prevent your NFS client from trying to use the NFSv3
  526. ACL protocol.
  527. If unsure, say N.
  528. config NFS_V4
  529. bool "NFS client support for NFS version 4 (EXPERIMENTAL)"
  530. depends on NFS_FS && EXPERIMENTAL
  531. select RPCSEC_GSS_KRB5
  532. help
  533. This option enables support for version 4 of the NFS protocol
  534. (RFC 3530) in the kernel's NFS client.
  535. To mount NFS servers using NFSv4, you also need to install user
  536. space programs which can be found in the Linux nfs-utils package,
  537. available from http://linux-nfs.org/.
  538. If unsure, say N.
  539. config ROOT_NFS
  540. bool "Root file system on NFS"
  541. depends on NFS_FS=y && IP_PNP
  542. help
  543. If you want your system to mount its root file system via NFS,
  544. choose Y here. This is common practice for managing systems
  545. without local permanent storage. For details, read
  546. <file:Documentation/filesystems/nfsroot.txt>.
  547. Most people say N here.
  548. config NFSD
  549. tristate "NFS server support"
  550. depends on INET
  551. select LOCKD
  552. select SUNRPC
  553. select EXPORTFS
  554. select NFS_ACL_SUPPORT if NFSD_V2_ACL
  555. help
  556. Choose Y here if you want to allow other computers to access
  557. files residing on this system using Sun's Network File System
  558. protocol. To compile the NFS server support as a module,
  559. choose M here: the module will be called nfsd.
  560. You may choose to use a user-space NFS server instead, in which
  561. case you can choose N here.
  562. To export local file systems using NFS, you also need to install
  563. user space programs which can be found in the Linux nfs-utils
  564. package, available from http://linux-nfs.org/. More detail about
  565. the Linux NFS server implementation is available via the
  566. exports(5) man page.
  567. Below you can choose which versions of the NFS protocol are
  568. available to clients mounting the NFS server on this system.
  569. Support for NFS version 2 (RFC 1094) is always available when
  570. CONFIG_NFSD is selected.
  571. If unsure, say N.
  572. config NFSD_V2_ACL
  573. bool
  574. depends on NFSD
  575. config NFSD_V3
  576. bool "NFS server support for NFS version 3"
  577. depends on NFSD
  578. help
  579. This option enables support in your system's NFS server for
  580. version 3 of the NFS protocol (RFC 1813).
  581. If unsure, say Y.
  582. config NFSD_V3_ACL
  583. bool "NFS server support for the NFSv3 ACL protocol extension"
  584. depends on NFSD_V3
  585. select NFSD_V2_ACL
  586. help
  587. Solaris NFS servers support an auxiliary NFSv3 ACL protocol that
  588. never became an official part of the NFS version 3 protocol.
  589. This protocol extension allows applications on NFS clients to
  590. manipulate POSIX Access Control Lists on files residing on NFS
  591. servers. NFS servers enforce POSIX ACLs on local files whether
  592. this protocol is available or not.
  593. This option enables support in your system's NFS server for the
  594. NFSv3 ACL protocol extension allowing NFS clients to manipulate
  595. POSIX ACLs on files exported by your system's NFS server. NFS
  596. clients which support the Solaris NFSv3 ACL protocol can then
  597. access and modify ACLs on your NFS server.
  598. To store ACLs on your NFS server, you also need to enable ACL-
  599. related CONFIG options for your local file systems of choice.
  600. If unsure, say N.
  601. config NFSD_V4
  602. bool "NFS server support for NFS version 4 (EXPERIMENTAL)"
  603. depends on NFSD && PROC_FS && EXPERIMENTAL
  604. select NFSD_V3
  605. select FS_POSIX_ACL
  606. select RPCSEC_GSS_KRB5
  607. help
  608. This option enables support in your system's NFS server for
  609. version 4 of the NFS protocol (RFC 3530).
  610. To export files using NFSv4, you need to install additional user
  611. space programs which can be found in the Linux nfs-utils package,
  612. available from http://linux-nfs.org/.
  613. If unsure, say N.
  614. config LOCKD
  615. tristate
  616. config LOCKD_V4
  617. bool
  618. depends on NFSD_V3 || NFS_V3
  619. default y
  620. config EXPORTFS
  621. tristate
  622. config NFS_ACL_SUPPORT
  623. tristate
  624. select FS_POSIX_ACL
  625. config NFS_COMMON
  626. bool
  627. depends on NFSD || NFS_FS
  628. default y
  629. config SUNRPC
  630. tristate
  631. config SUNRPC_GSS
  632. tristate
  633. config SUNRPC_XPRT_RDMA
  634. tristate
  635. depends on SUNRPC && INFINIBAND && EXPERIMENTAL
  636. default SUNRPC && INFINIBAND
  637. help
  638. This option enables an RPC client transport capability that
  639. allows the NFS client to mount servers via an RDMA-enabled
  640. transport.
  641. To compile RPC client RDMA transport support as a module,
  642. choose M here: the module will be called xprtrdma.
  643. If unsure, say N.
  644. config SUNRPC_REGISTER_V4
  645. bool "Register local RPC services via rpcbind v4 (EXPERIMENTAL)"
  646. depends on SUNRPC && EXPERIMENTAL
  647. default n
  648. help
  649. Sun added support for registering RPC services at an IPv6
  650. address by creating two new versions of the rpcbind protocol
  651. (RFC 1833).
  652. This option enables support in the kernel RPC server for
  653. registering kernel RPC services via version 4 of the rpcbind
  654. protocol. If you enable this option, you must run a portmapper
  655. daemon that supports rpcbind protocol version 4.
  656. Serving NFS over IPv6 from knfsd (the kernel's NFS server)
  657. requires that you enable this option and use a portmapper that
  658. supports rpcbind version 4.
  659. If unsure, say N to get traditional behavior (register kernel
  660. RPC services using only rpcbind version 2). Distributions
  661. using the legacy Linux portmapper daemon must say N here.
  662. config RPCSEC_GSS_KRB5
  663. tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
  664. depends on SUNRPC && EXPERIMENTAL
  665. select SUNRPC_GSS
  666. select CRYPTO
  667. select CRYPTO_MD5
  668. select CRYPTO_DES
  669. select CRYPTO_CBC
  670. help
  671. Choose Y here to enable Secure RPC using the Kerberos version 5
  672. GSS-API mechanism (RFC 1964).
  673. Secure RPC calls with Kerberos require an auxiliary user-space
  674. daemon which may be found in the Linux nfs-utils package
  675. available from http://linux-nfs.org/. In addition, user-space
  676. Kerberos support should be installed.
  677. If unsure, say N.
  678. config RPCSEC_GSS_SPKM3
  679. tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
  680. depends on SUNRPC && EXPERIMENTAL
  681. select SUNRPC_GSS
  682. select CRYPTO
  683. select CRYPTO_MD5
  684. select CRYPTO_DES
  685. select CRYPTO_CAST5
  686. select CRYPTO_CBC
  687. help
  688. Choose Y here to enable Secure RPC using the SPKM3 public key
  689. GSS-API mechansim (RFC 2025).
  690. Secure RPC calls with SPKM3 require an auxiliary userspace
  691. daemon which may be found in the Linux nfs-utils package
  692. available from http://linux-nfs.org/.
  693. If unsure, say N.
  694. config SMB_FS
  695. tristate "SMB file system support (OBSOLETE, please use CIFS)"
  696. depends on INET
  697. select NLS
  698. help
  699. SMB (Server Message Block) is the protocol Windows for Workgroups
  700. (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
  701. files and printers over local networks. Saying Y here allows you to
  702. mount their file systems (often called "shares" in this context) and
  703. access them just like any other Unix directory. Currently, this
  704. works only if the Windows machines use TCP/IP as the underlying
  705. transport protocol, and not NetBEUI. For details, read
  706. <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
  707. available from <http://www.tldp.org/docs.html#howto>.
  708. Note: if you just want your box to act as an SMB *server* and make
  709. files and printing services available to Windows clients (which need
  710. to have a TCP/IP stack), you don't need to say Y here; you can use
  711. the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
  712. for that.
  713. General information about how to connect Linux, Windows machines and
  714. Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
  715. To compile the SMB support as a module, choose M here:
  716. the module will be called smbfs. Most people say N, however.
  717. config SMB_NLS_DEFAULT
  718. bool "Use a default NLS"
  719. depends on SMB_FS
  720. help
  721. Enabling this will make smbfs use nls translations by default. You
  722. need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
  723. settings and you need to give the default nls for the SMB server as
  724. CONFIG_SMB_NLS_REMOTE.
  725. The nls settings can be changed at mount time, if your smbmount
  726. supports that, using the codepage and iocharset parameters.
  727. smbmount from samba 2.2.0 or later supports this.
  728. config SMB_NLS_REMOTE
  729. string "Default Remote NLS Option"
  730. depends on SMB_NLS_DEFAULT
  731. default "cp437"
  732. help
  733. This setting allows you to specify a default value for which
  734. codepage the server uses. If this field is left blank no
  735. translations will be done by default. The local codepage/charset
  736. default to CONFIG_NLS_DEFAULT.
  737. The nls settings can be changed at mount time, if your smbmount
  738. supports that, using the codepage and iocharset parameters.
  739. smbmount from samba 2.2.0 or later supports this.
  740. source "fs/cifs/Kconfig"
  741. config NCP_FS
  742. tristate "NCP file system support (to mount NetWare volumes)"
  743. depends on IPX!=n || INET
  744. help
  745. NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
  746. used by Novell NetWare clients to talk to file servers. It is to
  747. IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
  748. to mount NetWare file server volumes and to access them just like
  749. any other Unix directory. For details, please read the file
  750. <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
  751. the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
  752. You do not have to say Y here if you want your Linux box to act as a
  753. file *server* for Novell NetWare clients.
  754. General information about how to connect Linux, Windows machines and
  755. Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
  756. To compile this as a module, choose M here: the module will be called
  757. ncpfs. Say N unless you are connected to a Novell network.
  758. source "fs/ncpfs/Kconfig"
  759. config CODA_FS
  760. tristate "Coda file system support (advanced network fs)"
  761. depends on INET
  762. help
  763. Coda is an advanced network file system, similar to NFS in that it
  764. enables you to mount file systems of a remote server and access them
  765. with regular Unix commands as if they were sitting on your hard
  766. disk. Coda has several advantages over NFS: support for
  767. disconnected operation (e.g. for laptops), read/write server
  768. replication, security model for authentication and encryption,
  769. persistent client caches and write back caching.
  770. If you say Y here, your Linux box will be able to act as a Coda
  771. *client*. You will need user level code as well, both for the
  772. client and server. Servers are currently user level, i.e. they need
  773. no kernel support. Please read
  774. <file:Documentation/filesystems/coda.txt> and check out the Coda
  775. home page <http://www.coda.cs.cmu.edu/>.
  776. To compile the coda client support as a module, choose M here: the
  777. module will be called coda.
  778. config AFS_FS
  779. tristate "Andrew File System support (AFS) (EXPERIMENTAL)"
  780. depends on INET && EXPERIMENTAL
  781. select AF_RXRPC
  782. help
  783. If you say Y here, you will get an experimental Andrew File System
  784. driver. It currently only supports unsecured read-only AFS access.
  785. See <file:Documentation/filesystems/afs.txt> for more information.
  786. If unsure, say N.
  787. config AFS_DEBUG
  788. bool "AFS dynamic debugging"
  789. depends on AFS_FS
  790. help
  791. Say Y here to make runtime controllable debugging messages appear.
  792. See <file:Documentation/filesystems/afs.txt> for more information.
  793. If unsure, say N.
  794. config 9P_FS
  795. tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
  796. depends on INET && NET_9P && EXPERIMENTAL
  797. help
  798. If you say Y here, you will get experimental support for
  799. Plan 9 resource sharing via the 9P2000 protocol.
  800. See <http://v9fs.sf.net> for more information.
  801. If unsure, say N.
  802. endif # NETWORK_FILESYSTEMS
  803. if BLOCK
  804. menu "Partition Types"
  805. source "fs/partitions/Kconfig"
  806. endmenu
  807. endif
  808. source "fs/nls/Kconfig"
  809. source "fs/dlm/Kconfig"
  810. endmenu