Kconfig 55 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192939495969798991001011021031041051061071081091101111121131141151161171181191201211221231241251261271281291301311321331341351361371381391401411421431441451461471481491501511521531541551561571581591601611621631641651661671681691701711721731741751761771781791801811821831841851861871881891901911921931941951961971981992002012022032042052062072082092102112122132142152162172182192202212222232242252262272282292302312322332342352362372382392402412422432442452462472482492502512522532542552562572582592602612622632642652662672682692702712722732742752762772782792802812822832842852862872882892902912922932942952962972982993003013023033043053063073083093103113123133143153163173183193203213223233243253263273283293303313323333343353363373383393403413423433443453463473483493503513523533543553563573583593603613623633643653663673683693703713723733743753763773783793803813823833843853863873883893903913923933943953963973983994004014024034044054064074084094104114124134144154164174184194204214224234244254264274284294304314324334344354364374384394404414424434444454464474484494504514524534544554564574584594604614624634644654664674684694704714724734744754764774784794804814824834844854864874884894904914924934944954964974984995005015025035045055065075085095105115125135145155165175185195205215225235245255265275285295305315325335345355365375385395405415425435445455465475485495505515525535545555565575585595605615625635645655665675685695705715725735745755765775785795805815825835845855865875885895905915925935945955965975985996006016026036046056066076086096106116126136146156166176186196206216226236246256266276286296306316326336346356366376386396406416426436446456466476486496506516526536546556566576586596606616626636646656666676686696706716726736746756766776786796806816826836846856866876886896906916926936946956966976986997007017027037047057067077087097107117127137147157167177187197207217227237247257267277287297307317327337347357367377387397407417427437447457467477487497507517527537547557567577587597607617627637647657667677687697707717727737747757767777787797807817827837847857867877887897907917927937947957967977987998008018028038048058068078088098108118128138148158168178188198208218228238248258268278288298308318328338348358368378388398408418428438448458468478488498508518528538548558568578588598608618628638648658668678688698708718728738748758768778788798808818828838848858868878888898908918928938948958968978988999009019029039049059069079089099109119129139149159169179189199209219229239249259269279289299309319329339349359369379389399409419429439449459469479489499509519529539549559569579589599609619629639649659669679689699709719729739749759769779789799809819829839849859869879889899909919929939949959969979989991000100110021003100410051006100710081009101010111012101310141015101610171018101910201021102210231024102510261027102810291030103110321033103410351036103710381039104010411042104310441045104610471048104910501051105210531054105510561057105810591060106110621063106410651066106710681069107010711072107310741075107610771078107910801081108210831084108510861087108810891090109110921093109410951096109710981099110011011102110311041105110611071108110911101111111211131114111511161117111811191120112111221123112411251126112711281129113011311132113311341135113611371138113911401141114211431144114511461147114811491150115111521153115411551156115711581159116011611162116311641165116611671168116911701171117211731174117511761177117811791180118111821183118411851186118711881189119011911192119311941195119611971198119912001201120212031204120512061207120812091210121112121213121412151216121712181219122012211222122312241225122612271228122912301231123212331234123512361237123812391240124112421243124412451246124712481249125012511252125312541255125612571258125912601261126212631264126512661267126812691270127112721273127412751276127712781279128012811282128312841285128612871288128912901291129212931294129512961297129812991300130113021303130413051306130713081309131013111312131313141315131613171318131913201321132213231324132513261327132813291330133113321333133413351336133713381339134013411342134313441345134613471348134913501351135213531354135513561357135813591360136113621363136413651366136713681369137013711372137313741375137613771378137913801381138213831384138513861387138813891390139113921393139413951396139713981399140014011402140314041405140614071408140914101411141214131414141514161417141814191420142114221423142414251426142714281429143014311432143314341435143614371438143914401441144214431444144514461447144814491450145114521453145414551456145714581459146014611462146314641465146614671468146914701471147214731474147514761477147814791480148114821483148414851486148714881489149014911492149314941495149614971498149915001501150215031504150515061507150815091510151115121513151415151516151715181519152015211522152315241525152615271528152915301531153215331534153515361537153815391540154115421543154415451546154715481549155015511552155315541555155615571558155915601561156215631564156515661567156815691570157115721573157415751576157715781579
  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. config REISERFS_FS
  24. tristate "Reiserfs support"
  25. help
  26. Stores not just filenames but the files themselves in a balanced
  27. tree. Uses journalling.
  28. Balanced trees are more efficient than traditional file system
  29. architectural foundations.
  30. In general, ReiserFS is as fast as ext2, but is very efficient with
  31. large directories and small files. Additional patches are needed
  32. for NFS and quotas, please see <http://www.namesys.com/> for links.
  33. It is more easily extended to have features currently found in
  34. database and keyword search systems than block allocation based file
  35. systems are. The next version will be so extended, and will support
  36. plugins consistent with our motto ``It takes more than a license to
  37. make source code open.''
  38. Read <http://www.namesys.com/> to learn more about reiserfs.
  39. Sponsored by Threshold Networks, Emusic.com, and Bigstorage.com.
  40. If you like it, you can pay us to add new features to it that you
  41. need, buy a support contract, or pay us to port it to another OS.
  42. config REISERFS_CHECK
  43. bool "Enable reiserfs debug mode"
  44. depends on REISERFS_FS
  45. help
  46. If you set this to Y, then ReiserFS will perform every check it can
  47. possibly imagine of its internal consistency throughout its
  48. operation. It will also go substantially slower. More than once we
  49. have forgotten that this was on, and then gone despondent over the
  50. latest benchmarks.:-) Use of this option allows our team to go all
  51. out in checking for consistency when debugging without fear of its
  52. effect on end users. If you are on the verge of sending in a bug
  53. report, say Y and you might get a useful error message. Almost
  54. everyone should say N.
  55. config REISERFS_PROC_INFO
  56. bool "Stats in /proc/fs/reiserfs"
  57. depends on REISERFS_FS && PROC_FS
  58. help
  59. Create under /proc/fs/reiserfs a hierarchy of files, displaying
  60. various ReiserFS statistics and internal data at the expense of
  61. making your kernel or module slightly larger (+8 KB). This also
  62. increases the amount of kernel memory required for each mount.
  63. Almost everyone but ReiserFS developers and people fine-tuning
  64. reiserfs or tracing problems should say N.
  65. config REISERFS_FS_XATTR
  66. bool "ReiserFS extended attributes"
  67. depends on REISERFS_FS
  68. help
  69. Extended attributes are name:value pairs associated with inodes by
  70. the kernel or by users (see the attr(5) manual page, or visit
  71. <http://acl.bestbits.at/> for details).
  72. If unsure, say N.
  73. config REISERFS_FS_POSIX_ACL
  74. bool "ReiserFS POSIX Access Control Lists"
  75. depends on REISERFS_FS_XATTR
  76. select FS_POSIX_ACL
  77. help
  78. Posix Access Control Lists (ACLs) support permissions for users and
  79. groups beyond the owner/group/world scheme.
  80. To learn more about Access Control Lists, visit the Posix ACLs for
  81. Linux website <http://acl.bestbits.at/>.
  82. If you don't know what Access Control Lists are, say N
  83. config REISERFS_FS_SECURITY
  84. bool "ReiserFS Security Labels"
  85. depends on REISERFS_FS_XATTR
  86. help
  87. Security labels support alternative access control models
  88. implemented by security modules like SELinux. This option
  89. enables an extended attribute handler for file security
  90. labels in the ReiserFS filesystem.
  91. If you are not using a security module that requires using
  92. extended attributes for file security labels, say N.
  93. config JFS_FS
  94. tristate "JFS filesystem support"
  95. select NLS
  96. help
  97. This is a port of IBM's Journaled Filesystem . More information is
  98. available in the file <file:Documentation/filesystems/jfs.txt>.
  99. If you do not intend to use the JFS filesystem, say N.
  100. config JFS_POSIX_ACL
  101. bool "JFS POSIX Access Control Lists"
  102. depends on JFS_FS
  103. select FS_POSIX_ACL
  104. help
  105. Posix Access Control Lists (ACLs) support permissions for users and
  106. groups beyond the owner/group/world scheme.
  107. To learn more about Access Control Lists, visit the Posix ACLs for
  108. Linux website <http://acl.bestbits.at/>.
  109. If you don't know what Access Control Lists are, say N
  110. config JFS_SECURITY
  111. bool "JFS Security Labels"
  112. depends on JFS_FS
  113. help
  114. Security labels support alternative access control models
  115. implemented by security modules like SELinux. This option
  116. enables an extended attribute handler for file security
  117. labels in the jfs filesystem.
  118. If you are not using a security module that requires using
  119. extended attributes for file security labels, say N.
  120. config JFS_DEBUG
  121. bool "JFS debugging"
  122. depends on JFS_FS
  123. help
  124. If you are experiencing any problems with the JFS filesystem, say
  125. Y here. This will result in additional debugging messages to be
  126. written to the system log. Under normal circumstances, this
  127. results in very little overhead.
  128. config JFS_STATISTICS
  129. bool "JFS statistics"
  130. depends on JFS_FS
  131. help
  132. Enabling this option will cause statistics from the JFS file system
  133. to be made available to the user in the /proc/fs/jfs/ directory.
  134. config FS_POSIX_ACL
  135. # Posix ACL utility routines (for now, only ext2/ext3/jfs/reiserfs/nfs4)
  136. #
  137. # NOTE: you can implement Posix ACLs without these helpers (XFS does).
  138. # Never use this symbol for ifdefs.
  139. #
  140. bool
  141. default n
  142. config FILE_LOCKING
  143. bool "Enable POSIX file locking API" if EMBEDDED
  144. default y
  145. help
  146. This option enables standard file locking support, required
  147. for filesystems like NFS and for the flock() system
  148. call. Disabling this option saves about 11k.
  149. source "fs/xfs/Kconfig"
  150. source "fs/gfs2/Kconfig"
  151. config OCFS2_FS
  152. tristate "OCFS2 file system support"
  153. depends on NET && SYSFS
  154. select CONFIGFS_FS
  155. select JBD2
  156. select CRC32
  157. help
  158. OCFS2 is a general purpose extent based shared disk cluster file
  159. system with many similarities to ext3. It supports 64 bit inode
  160. numbers, and has automatically extending metadata groups which may
  161. also make it attractive for non-clustered use.
  162. You'll want to install the ocfs2-tools package in order to at least
  163. get "mount.ocfs2".
  164. Project web page: http://oss.oracle.com/projects/ocfs2
  165. Tools web page: http://oss.oracle.com/projects/ocfs2-tools
  166. OCFS2 mailing lists: http://oss.oracle.com/projects/ocfs2/mailman/
  167. For more information on OCFS2, see the file
  168. <file:Documentation/filesystems/ocfs2.txt>.
  169. config OCFS2_FS_O2CB
  170. tristate "O2CB Kernelspace Clustering"
  171. depends on OCFS2_FS
  172. default y
  173. help
  174. OCFS2 includes a simple kernelspace clustering package, the OCFS2
  175. Cluster Base. It only requires a very small userspace component
  176. to configure it. This comes with the standard ocfs2-tools package.
  177. O2CB is limited to maintaining a cluster for OCFS2 file systems.
  178. It cannot manage any other cluster applications.
  179. It is always safe to say Y here, as the clustering method is
  180. run-time selectable.
  181. config OCFS2_FS_USERSPACE_CLUSTER
  182. tristate "OCFS2 Userspace Clustering"
  183. depends on OCFS2_FS && DLM
  184. default y
  185. help
  186. This option will allow OCFS2 to use userspace clustering services
  187. in conjunction with the DLM in fs/dlm. If you are using a
  188. userspace cluster manager, say Y here.
  189. It is safe to say Y, as the clustering method is run-time
  190. selectable.
  191. config OCFS2_FS_STATS
  192. bool "OCFS2 statistics"
  193. depends on OCFS2_FS
  194. default y
  195. help
  196. This option allows some fs statistics to be captured. Enabling
  197. this option may increase the memory consumption.
  198. config OCFS2_DEBUG_MASKLOG
  199. bool "OCFS2 logging support"
  200. depends on OCFS2_FS
  201. default y
  202. help
  203. The ocfs2 filesystem has an extensive logging system. The system
  204. allows selection of events to log via files in /sys/o2cb/logmask/.
  205. This option will enlarge your kernel, but it allows debugging of
  206. ocfs2 filesystem issues.
  207. config OCFS2_DEBUG_FS
  208. bool "OCFS2 expensive checks"
  209. depends on OCFS2_FS
  210. default n
  211. help
  212. This option will enable expensive consistency checks. Enable
  213. this option for debugging only as it is likely to decrease
  214. performance of the filesystem.
  215. config OCFS2_COMPAT_JBD
  216. bool "Use JBD for compatibility"
  217. depends on OCFS2_FS
  218. default n
  219. select JBD
  220. help
  221. The ocfs2 filesystem now uses JBD2 for its journalling. JBD2
  222. is backwards compatible with JBD. It is safe to say N here.
  223. However, if you really want to use the original JBD, say Y here.
  224. config BTRFS_FS
  225. tristate "Btrfs filesystem (EXPERIMENTAL) Unstable disk format"
  226. depends on EXPERIMENTAL
  227. select LIBCRC32C
  228. select ZLIB_INFLATE
  229. select ZLIB_DEFLATE
  230. help
  231. Btrfs is a new filesystem with extents, writable snapshotting,
  232. support for multiple devices and many more features.
  233. Btrfs is highly experimental, and THE DISK FORMAT IS NOT YET
  234. FINALIZED. You should say N here unless you are interested in
  235. testing Btrfs with non-critical data.
  236. To compile this file system support as a module, choose M here. The
  237. module will be called btrfs.
  238. If unsure, say N.
  239. endif # BLOCK
  240. config DNOTIFY
  241. bool "Dnotify support"
  242. default y
  243. help
  244. Dnotify is a directory-based per-fd file change notification system
  245. that uses signals to communicate events to user-space. There exist
  246. superior alternatives, but some applications may still rely on
  247. dnotify.
  248. If unsure, say Y.
  249. config INOTIFY
  250. bool "Inotify file change notification support"
  251. default y
  252. ---help---
  253. Say Y here to enable inotify support. Inotify is a file change
  254. notification system and a replacement for dnotify. Inotify fixes
  255. numerous shortcomings in dnotify and introduces several new features
  256. including multiple file events, one-shot support, and unmount
  257. notification.
  258. For more information, see <file:Documentation/filesystems/inotify.txt>
  259. If unsure, say Y.
  260. config INOTIFY_USER
  261. bool "Inotify support for userspace"
  262. depends on INOTIFY
  263. default y
  264. ---help---
  265. Say Y here to enable inotify support for userspace, including the
  266. associated system calls. Inotify allows monitoring of both files and
  267. directories via a single open fd. Events are read from the file
  268. descriptor, which is also select()- and poll()-able.
  269. For more information, see <file:Documentation/filesystems/inotify.txt>
  270. If unsure, say Y.
  271. config QUOTA
  272. bool "Quota support"
  273. help
  274. If you say Y here, you will be able to set per user limits for disk
  275. usage (also called disk quotas). Currently, it works for the
  276. ext2, ext3, and reiserfs file system. ext3 also supports journalled
  277. quotas for which you don't need to run quotacheck(8) after an unclean
  278. shutdown.
  279. For further details, read the Quota mini-HOWTO, available from
  280. <http://www.tldp.org/docs.html#howto>, or the documentation provided
  281. with the quota tools. Probably the quota support is only useful for
  282. multi user systems. If unsure, say N.
  283. config QUOTA_NETLINK_INTERFACE
  284. bool "Report quota messages through netlink interface"
  285. depends on QUOTA && NET
  286. help
  287. If you say Y here, quota warnings (about exceeding softlimit, reaching
  288. hardlimit, etc.) will be reported through netlink interface. If unsure,
  289. say Y.
  290. config PRINT_QUOTA_WARNING
  291. bool "Print quota warnings to console (OBSOLETE)"
  292. depends on QUOTA
  293. default y
  294. help
  295. If you say Y here, quota warnings (about exceeding softlimit, reaching
  296. hardlimit, etc.) will be printed to the process' controlling terminal.
  297. Note that this behavior is currently deprecated and may go away in
  298. future. Please use notification via netlink socket instead.
  299. config QFMT_V1
  300. tristate "Old quota format support"
  301. depends on QUOTA
  302. help
  303. This quota format was (is) used by kernels earlier than 2.4.22. If
  304. you have quota working and you don't want to convert to new quota
  305. format say Y here.
  306. config QFMT_V2
  307. tristate "Quota format v2 support"
  308. depends on QUOTA
  309. help
  310. This quota format allows using quotas with 32-bit UIDs/GIDs. If you
  311. need this functionality say Y here.
  312. config QUOTACTL
  313. bool
  314. depends on XFS_QUOTA || QUOTA
  315. default y
  316. config AUTOFS_FS
  317. tristate "Kernel automounter support"
  318. help
  319. The automounter is a tool to automatically mount remote file systems
  320. on demand. This implementation is partially kernel-based to reduce
  321. overhead in the already-mounted case; this is unlike the BSD
  322. automounter (amd), which is a pure user space daemon.
  323. To use the automounter you need the user-space tools from the autofs
  324. package; you can find the location in <file:Documentation/Changes>.
  325. You also want to answer Y to "NFS file system support", below.
  326. If you want to use the newer version of the automounter with more
  327. features, say N here and say Y to "Kernel automounter v4 support",
  328. below.
  329. To compile this support as a module, choose M here: the module will be
  330. called autofs.
  331. If you are not a part of a fairly large, distributed network, you
  332. probably do not need an automounter, and can say N here.
  333. config AUTOFS4_FS
  334. tristate "Kernel automounter version 4 support (also supports v3)"
  335. help
  336. The automounter is a tool to automatically mount remote file systems
  337. on demand. This implementation is partially kernel-based to reduce
  338. overhead in the already-mounted case; this is unlike the BSD
  339. automounter (amd), which is a pure user space daemon.
  340. To use the automounter you need the user-space tools from
  341. <ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4/>; you also
  342. want to answer Y to "NFS file system support", below.
  343. To compile this support as a module, choose M here: the module will be
  344. called autofs4. You will need to add "alias autofs autofs4" to your
  345. modules configuration file.
  346. If you are not a part of a fairly large, distributed network or
  347. don't have a laptop which needs to dynamically reconfigure to the
  348. local network, you probably do not need an automounter, and can say
  349. N here.
  350. config FUSE_FS
  351. tristate "FUSE (Filesystem in Userspace) support"
  352. help
  353. With FUSE it is possible to implement a fully functional filesystem
  354. in a userspace program.
  355. There's also companion library: libfuse. This library along with
  356. utilities is available from the FUSE homepage:
  357. <http://fuse.sourceforge.net/>
  358. See <file:Documentation/filesystems/fuse.txt> for more information.
  359. See <file:Documentation/Changes> for needed library/utility version.
  360. If you want to develop a userspace FS, or if you want to use
  361. a filesystem based on FUSE, answer Y or M.
  362. config GENERIC_ACL
  363. bool
  364. select FS_POSIX_ACL
  365. if BLOCK
  366. menu "CD-ROM/DVD Filesystems"
  367. config ISO9660_FS
  368. tristate "ISO 9660 CDROM file system support"
  369. help
  370. This is the standard file system used on CD-ROMs. It was previously
  371. known as "High Sierra File System" and is called "hsfs" on other
  372. Unix systems. The so-called Rock-Ridge extensions which allow for
  373. long Unix filenames and symbolic links are also supported by this
  374. driver. If you have a CD-ROM drive and want to do more with it than
  375. just listen to audio CDs and watch its LEDs, say Y (and read
  376. <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO,
  377. available from <http://www.tldp.org/docs.html#howto>), thereby
  378. enlarging your kernel by about 27 KB; otherwise say N.
  379. To compile this file system support as a module, choose M here: the
  380. module will be called isofs.
  381. config JOLIET
  382. bool "Microsoft Joliet CDROM extensions"
  383. depends on ISO9660_FS
  384. select NLS
  385. help
  386. Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system
  387. which allows for long filenames in unicode format (unicode is the
  388. new 16 bit character code, successor to ASCII, which encodes the
  389. characters of almost all languages of the world; see
  390. <http://www.unicode.org/> for more information). Say Y here if you
  391. want to be able to read Joliet CD-ROMs under Linux.
  392. config ZISOFS
  393. bool "Transparent decompression extension"
  394. depends on ISO9660_FS
  395. select ZLIB_INFLATE
  396. help
  397. This is a Linux-specific extension to RockRidge which lets you store
  398. data in compressed form on a CD-ROM and have it transparently
  399. decompressed when the CD-ROM is accessed. See
  400. <http://www.kernel.org/pub/linux/utils/fs/zisofs/> for the tools
  401. necessary to create such a filesystem. Say Y here if you want to be
  402. able to read such compressed CD-ROMs.
  403. config UDF_FS
  404. tristate "UDF file system support"
  405. select CRC_ITU_T
  406. help
  407. This is the new file system used on some CD-ROMs and DVDs. Say Y if
  408. you intend to mount DVD discs or CDRW's written in packet mode, or
  409. if written to by other UDF utilities, such as DirectCD.
  410. Please read <file:Documentation/filesystems/udf.txt>.
  411. To compile this file system support as a module, choose M here: the
  412. module will be called udf.
  413. If unsure, say N.
  414. config UDF_NLS
  415. bool
  416. default y
  417. depends on (UDF_FS=m && NLS) || (UDF_FS=y && NLS=y)
  418. endmenu
  419. endif # BLOCK
  420. if BLOCK
  421. menu "DOS/FAT/NT Filesystems"
  422. config FAT_FS
  423. tristate
  424. select NLS
  425. help
  426. If you want to use one of the FAT-based file systems (the MS-DOS and
  427. VFAT (Windows 95) file systems), then you must say Y or M here
  428. to include FAT support. You will then be able to mount partitions or
  429. diskettes with FAT-based file systems and transparently access the
  430. files on them, i.e. MSDOS files will look and behave just like all
  431. other Unix files.
  432. This FAT support is not a file system in itself, it only provides
  433. the foundation for the other file systems. You will have to say Y or
  434. M to at least one of "MSDOS fs support" or "VFAT fs support" in
  435. order to make use of it.
  436. Another way to read and write MSDOS floppies and hard drive
  437. partitions from within Linux (but not transparently) is with the
  438. mtools ("man mtools") program suite. You don't need to say Y here in
  439. order to do that.
  440. If you need to move large files on floppies between a DOS and a
  441. Linux box, say Y here, mount the floppy under Linux with an MSDOS
  442. file system and use GNU tar's M option. GNU tar is a program
  443. available for Unix and DOS ("man tar" or "info tar").
  444. The FAT support will enlarge your kernel by about 37 KB. If unsure,
  445. say Y.
  446. To compile this as a module, choose M here: the module will be called
  447. fat. Note that if you compile the FAT support as a module, you
  448. cannot compile any of the FAT-based file systems into the kernel
  449. -- they will have to be modules as well.
  450. config MSDOS_FS
  451. tristate "MSDOS fs support"
  452. select FAT_FS
  453. help
  454. This allows you to mount MSDOS partitions of your hard drive (unless
  455. they are compressed; to access compressed MSDOS partitions under
  456. Linux, you can either use the DOS emulator DOSEMU, described in the
  457. DOSEMU-HOWTO, available from
  458. <http://www.tldp.org/docs.html#howto>, or try dmsdosfs in
  459. <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you
  460. intend to use dosemu with a non-compressed MSDOS partition, say Y
  461. here) and MSDOS floppies. This means that file access becomes
  462. transparent, i.e. the MSDOS files look and behave just like all
  463. other Unix files.
  464. If you have Windows 95 or Windows NT installed on your MSDOS
  465. partitions, you should use the VFAT file system (say Y to "VFAT fs
  466. support" below), or you will not be able to see the long filenames
  467. generated by Windows 95 / Windows NT.
  468. This option will enlarge your kernel by about 7 KB. If unsure,
  469. answer Y. This will only work if you said Y to "DOS FAT fs support"
  470. as well. To compile this as a module, choose M here: the module will
  471. be called msdos.
  472. config VFAT_FS
  473. tristate "VFAT (Windows-95) fs support"
  474. select FAT_FS
  475. help
  476. This option provides support for normal Windows file systems with
  477. long filenames. That includes non-compressed FAT-based file systems
  478. used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
  479. programs from the mtools package.
  480. The VFAT support enlarges your kernel by about 10 KB and it only
  481. works if you said Y to the "DOS FAT fs support" above. Please read
  482. the file <file:Documentation/filesystems/vfat.txt> for details. If
  483. unsure, say Y.
  484. To compile this as a module, choose M here: the module will be called
  485. vfat.
  486. config FAT_DEFAULT_CODEPAGE
  487. int "Default codepage for FAT"
  488. depends on MSDOS_FS || VFAT_FS
  489. default 437
  490. help
  491. This option should be set to the codepage of your FAT filesystems.
  492. It can be overridden with the "codepage" mount option.
  493. See <file:Documentation/filesystems/vfat.txt> for more information.
  494. config FAT_DEFAULT_IOCHARSET
  495. string "Default iocharset for FAT"
  496. depends on VFAT_FS
  497. default "iso8859-1"
  498. help
  499. Set this to the default input/output character set you'd
  500. like FAT to use. It should probably match the character set
  501. that most of your FAT filesystems use, and can be overridden
  502. with the "iocharset" mount option for FAT filesystems.
  503. Note that "utf8" is not recommended for FAT filesystems.
  504. If unsure, you shouldn't set "utf8" here.
  505. See <file:Documentation/filesystems/vfat.txt> for more information.
  506. config NTFS_FS
  507. tristate "NTFS file system support"
  508. select NLS
  509. help
  510. NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003.
  511. Saying Y or M here enables read support. There is partial, but
  512. safe, write support available. For write support you must also
  513. say Y to "NTFS write support" below.
  514. There are also a number of user-space tools available, called
  515. ntfsprogs. These include ntfsundelete and ntfsresize, that work
  516. without NTFS support enabled in the kernel.
  517. This is a rewrite from scratch of Linux NTFS support and replaced
  518. the old NTFS code starting with Linux 2.5.11. A backport to
  519. the Linux 2.4 kernel series is separately available as a patch
  520. from the project web site.
  521. For more information see <file:Documentation/filesystems/ntfs.txt>
  522. and <http://www.linux-ntfs.org/>.
  523. To compile this file system support as a module, choose M here: the
  524. module will be called ntfs.
  525. If you are not using Windows NT, 2000, XP or 2003 in addition to
  526. Linux on your computer it is safe to say N.
  527. config NTFS_DEBUG
  528. bool "NTFS debugging support"
  529. depends on NTFS_FS
  530. help
  531. If you are experiencing any problems with the NTFS file system, say
  532. Y here. This will result in additional consistency checks to be
  533. performed by the driver as well as additional debugging messages to
  534. be written to the system log. Note that debugging messages are
  535. disabled by default. To enable them, supply the option debug_msgs=1
  536. at the kernel command line when booting the kernel or as an option
  537. to insmod when loading the ntfs module. Once the driver is active,
  538. you can enable debugging messages by doing (as root):
  539. echo 1 > /proc/sys/fs/ntfs-debug
  540. Replacing the "1" with "0" would disable debug messages.
  541. If you leave debugging messages disabled, this results in little
  542. overhead, but enabling debug messages results in very significant
  543. slowdown of the system.
  544. When reporting bugs, please try to have available a full dump of
  545. debugging messages while the misbehaviour was occurring.
  546. config NTFS_RW
  547. bool "NTFS write support"
  548. depends on NTFS_FS
  549. help
  550. This enables the partial, but safe, write support in the NTFS driver.
  551. The only supported operation is overwriting existing files, without
  552. changing the file length. No file or directory creation, deletion or
  553. renaming is possible. Note only non-resident files can be written to
  554. so you may find that some very small files (<500 bytes or so) cannot
  555. be written to.
  556. While we cannot guarantee that it will not damage any data, we have
  557. so far not received a single report where the driver would have
  558. damaged someones data so we assume it is perfectly safe to use.
  559. Note: While write support is safe in this version (a rewrite from
  560. scratch of the NTFS support), it should be noted that the old NTFS
  561. write support, included in Linux 2.5.10 and before (since 1997),
  562. is not safe.
  563. This is currently useful with TopologiLinux. TopologiLinux is run
  564. on top of any DOS/Microsoft Windows system without partitioning your
  565. hard disk. Unlike other Linux distributions TopologiLinux does not
  566. need its own partition. For more information see
  567. <http://topologi-linux.sourceforge.net/>
  568. It is perfectly safe to say N here.
  569. endmenu
  570. endif # BLOCK
  571. menu "Pseudo filesystems"
  572. source "fs/proc/Kconfig"
  573. config SYSFS
  574. bool "sysfs file system support" if EMBEDDED
  575. default y
  576. help
  577. The sysfs filesystem is a virtual filesystem that the kernel uses to
  578. export internal kernel objects, their attributes, and their
  579. relationships to one another.
  580. Users can use sysfs to ascertain useful information about the running
  581. kernel, such as the devices the kernel has discovered on each bus and
  582. which driver each is bound to. sysfs can also be used to tune devices
  583. and other kernel subsystems.
  584. Some system agents rely on the information in sysfs to operate.
  585. /sbin/hotplug uses device and object attributes in sysfs to assist in
  586. delegating policy decisions, like persistently naming devices.
  587. sysfs is currently used by the block subsystem to mount the root
  588. partition. If sysfs is disabled you must specify the boot device on
  589. the kernel boot command line via its major and minor numbers. For
  590. example, "root=03:01" for /dev/hda1.
  591. Designers of embedded systems may wish to say N here to conserve space.
  592. config TMPFS
  593. bool "Virtual memory file system support (former shm fs)"
  594. help
  595. Tmpfs is a file system which keeps all files in virtual memory.
  596. Everything in tmpfs is temporary in the sense that no files will be
  597. created on your hard drive. The files live in memory and swap
  598. space. If you unmount a tmpfs instance, everything stored therein is
  599. lost.
  600. See <file:Documentation/filesystems/tmpfs.txt> for details.
  601. config TMPFS_POSIX_ACL
  602. bool "Tmpfs POSIX Access Control Lists"
  603. depends on TMPFS
  604. select GENERIC_ACL
  605. help
  606. POSIX Access Control Lists (ACLs) support permissions for users and
  607. groups beyond the owner/group/world scheme.
  608. To learn more about Access Control Lists, visit the POSIX ACLs for
  609. Linux website <http://acl.bestbits.at/>.
  610. If you don't know what Access Control Lists are, say N.
  611. config HUGETLBFS
  612. bool "HugeTLB file system support"
  613. depends on X86 || IA64 || PPC64 || SPARC64 || (SUPERH && MMU) || \
  614. (S390 && 64BIT) || BROKEN
  615. help
  616. hugetlbfs is a filesystem backing for HugeTLB pages, based on
  617. ramfs. For architectures that support it, say Y here and read
  618. <file:Documentation/vm/hugetlbpage.txt> for details.
  619. If unsure, say N.
  620. config HUGETLB_PAGE
  621. def_bool HUGETLBFS
  622. config CONFIGFS_FS
  623. tristate "Userspace-driven configuration filesystem"
  624. depends on SYSFS
  625. help
  626. configfs is a ram-based filesystem that provides the converse
  627. of sysfs's functionality. Where sysfs is a filesystem-based
  628. view of kernel objects, configfs is a filesystem-based manager
  629. of kernel objects, or config_items.
  630. Both sysfs and configfs can and should exist together on the
  631. same system. One is not a replacement for the other.
  632. endmenu
  633. menu "Miscellaneous filesystems"
  634. config ADFS_FS
  635. tristate "ADFS file system support (EXPERIMENTAL)"
  636. depends on BLOCK && EXPERIMENTAL
  637. help
  638. The Acorn Disc Filing System is the standard file system of the
  639. RiscOS operating system which runs on Acorn's ARM-based Risc PC
  640. systems and the Acorn Archimedes range of machines. If you say Y
  641. here, Linux will be able to read from ADFS partitions on hard drives
  642. and from ADFS-formatted floppy discs. If you also want to be able to
  643. write to those devices, say Y to "ADFS write support" below.
  644. The ADFS partition should be the first partition (i.e.,
  645. /dev/[hs]d?1) on each of your drives. Please read the file
  646. <file:Documentation/filesystems/adfs.txt> for further details.
  647. To compile this code as a module, choose M here: the module will be
  648. called adfs.
  649. If unsure, say N.
  650. config ADFS_FS_RW
  651. bool "ADFS write support (DANGEROUS)"
  652. depends on ADFS_FS
  653. help
  654. If you say Y here, you will be able to write to ADFS partitions on
  655. hard drives and ADFS-formatted floppy disks. This is experimental
  656. codes, so if you're unsure, say N.
  657. config AFFS_FS
  658. tristate "Amiga FFS file system support (EXPERIMENTAL)"
  659. depends on BLOCK && EXPERIMENTAL
  660. help
  661. The Fast File System (FFS) is the common file system used on hard
  662. disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
  663. if you want to be able to read and write files from and to an Amiga
  664. FFS partition on your hard drive. Amiga floppies however cannot be
  665. read with this driver due to an incompatibility of the floppy
  666. controller used in an Amiga and the standard floppy controller in
  667. PCs and workstations. Read <file:Documentation/filesystems/affs.txt>
  668. and <file:fs/affs/Changes>.
  669. With this driver you can also mount disk files used by Bernd
  670. Schmidt's Un*X Amiga Emulator
  671. (<http://www.freiburg.linux.de/~uae/>).
  672. If you want to do this, you will also need to say Y or M to "Loop
  673. device support", above.
  674. To compile this file system support as a module, choose M here: the
  675. module will be called affs. If unsure, say N.
  676. config ECRYPT_FS
  677. tristate "eCrypt filesystem layer support (EXPERIMENTAL)"
  678. depends on EXPERIMENTAL && KEYS && CRYPTO && NET
  679. help
  680. Encrypted filesystem that operates on the VFS layer. See
  681. <file:Documentation/filesystems/ecryptfs.txt> to learn more about
  682. eCryptfs. Userspace components are required and can be
  683. obtained from <http://ecryptfs.sf.net>.
  684. To compile this file system support as a module, choose M here: the
  685. module will be called ecryptfs.
  686. config HFS_FS
  687. tristate "Apple Macintosh file system support (EXPERIMENTAL)"
  688. depends on BLOCK && EXPERIMENTAL
  689. select NLS
  690. help
  691. If you say Y here, you will be able to mount Macintosh-formatted
  692. floppy disks and hard drive partitions with full read-write access.
  693. Please read <file:Documentation/filesystems/hfs.txt> to learn about
  694. the available mount options.
  695. To compile this file system support as a module, choose M here: the
  696. module will be called hfs.
  697. config HFSPLUS_FS
  698. tristate "Apple Extended HFS file system support"
  699. depends on BLOCK
  700. select NLS
  701. select NLS_UTF8
  702. help
  703. If you say Y here, you will be able to mount extended format
  704. Macintosh-formatted hard drive partitions with full read-write access.
  705. This file system is often called HFS+ and was introduced with
  706. MacOS 8. It includes all Mac specific filesystem data such as
  707. data forks and creator codes, but it also has several UNIX
  708. style features such as file ownership and permissions.
  709. config BEFS_FS
  710. tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)"
  711. depends on BLOCK && EXPERIMENTAL
  712. select NLS
  713. help
  714. The BeOS File System (BeFS) is the native file system of Be, Inc's
  715. BeOS. Notable features include support for arbitrary attributes
  716. on files and directories, and database-like indices on selected
  717. attributes. (Also note that this driver doesn't make those features
  718. available at this time). It is a 64 bit filesystem, so it supports
  719. extremely large volumes and files.
  720. If you use this filesystem, you should also say Y to at least one
  721. of the NLS (native language support) options below.
  722. If you don't know what this is about, say N.
  723. To compile this as a module, choose M here: the module will be
  724. called befs.
  725. config BEFS_DEBUG
  726. bool "Debug BeFS"
  727. depends on BEFS_FS
  728. help
  729. If you say Y here, you can use the 'debug' mount option to enable
  730. debugging output from the driver.
  731. config BFS_FS
  732. tristate "BFS file system support (EXPERIMENTAL)"
  733. depends on BLOCK && EXPERIMENTAL
  734. help
  735. Boot File System (BFS) is a file system used under SCO UnixWare to
  736. allow the bootloader access to the kernel image and other important
  737. files during the boot process. It is usually mounted under /stand
  738. and corresponds to the slice marked as "STAND" in the UnixWare
  739. partition. You should say Y if you want to read or write the files
  740. on your /stand slice from within Linux. You then also need to say Y
  741. to "UnixWare slices support", below. More information about the BFS
  742. file system is contained in the file
  743. <file:Documentation/filesystems/bfs.txt>.
  744. If you don't know what this is about, say N.
  745. To compile this as a module, choose M here: the module will be called
  746. bfs. Note that the file system of your root partition (the one
  747. containing the directory /) cannot be compiled as a module.
  748. config EFS_FS
  749. tristate "EFS file system support (read only) (EXPERIMENTAL)"
  750. depends on BLOCK && EXPERIMENTAL
  751. help
  752. EFS is an older file system used for non-ISO9660 CD-ROMs and hard
  753. disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
  754. uses the XFS file system for hard disk partitions however).
  755. This implementation only offers read-only access. If you don't know
  756. what all this is about, it's safe to say N. For more information
  757. about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
  758. To compile the EFS file system support as a module, choose M here: the
  759. module will be called efs.
  760. source "fs/jffs2/Kconfig"
  761. # UBIFS File system configuration
  762. source "fs/ubifs/Kconfig"
  763. config CRAMFS
  764. tristate "Compressed ROM file system support (cramfs)"
  765. depends on BLOCK
  766. select ZLIB_INFLATE
  767. help
  768. Saying Y here includes support for CramFs (Compressed ROM File
  769. System). CramFs is designed to be a simple, small, and compressed
  770. file system for ROM based embedded systems. CramFs is read-only,
  771. limited to 256MB file systems (with 16MB files), and doesn't support
  772. 16/32 bits uid/gid, hard links and timestamps.
  773. See <file:Documentation/filesystems/cramfs.txt> and
  774. <file:fs/cramfs/README> for further information.
  775. To compile this as a module, choose M here: the module will be called
  776. cramfs. Note that the root file system (the one containing the
  777. directory /) cannot be compiled as a module.
  778. If unsure, say N.
  779. config VXFS_FS
  780. tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
  781. depends on BLOCK
  782. help
  783. FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
  784. file system format. VERITAS VxFS(TM) is the standard file system
  785. of SCO UnixWare (and possibly others) and optionally available
  786. for Sunsoft Solaris, HP-UX and many other operating systems.
  787. Currently only readonly access is supported.
  788. NOTE: the file system type as used by mount(1), mount(2) and
  789. fstab(5) is 'vxfs' as it describes the file system format, not
  790. the actual driver.
  791. To compile this as a module, choose M here: the module will be
  792. called freevxfs. If unsure, say N.
  793. config MINIX_FS
  794. tristate "Minix file system support"
  795. depends on BLOCK
  796. help
  797. Minix is a simple operating system used in many classes about OS's.
  798. The minix file system (method to organize files on a hard disk
  799. partition or a floppy disk) was the original file system for Linux,
  800. but has been superseded by the second extended file system ext2fs.
  801. You don't want to use the minix file system on your hard disk
  802. because of certain built-in restrictions, but it is sometimes found
  803. on older Linux floppy disks. This option will enlarge your kernel
  804. by about 28 KB. If unsure, say N.
  805. To compile this file system support as a module, choose M here: the
  806. module will be called minix. Note that the file system of your root
  807. partition (the one containing the directory /) cannot be compiled as
  808. a module.
  809. config OMFS_FS
  810. tristate "SonicBlue Optimized MPEG File System support"
  811. depends on BLOCK
  812. select CRC_ITU_T
  813. help
  814. This is the proprietary file system used by the Rio Karma music
  815. player and ReplayTV DVR. Despite the name, this filesystem is not
  816. more efficient than a standard FS for MPEG files, in fact likely
  817. the opposite is true. Say Y if you have either of these devices
  818. and wish to mount its disk.
  819. To compile this file system support as a module, choose M here: the
  820. module will be called omfs. If unsure, say N.
  821. config HPFS_FS
  822. tristate "OS/2 HPFS file system support"
  823. depends on BLOCK
  824. help
  825. OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
  826. is the file system used for organizing files on OS/2 hard disk
  827. partitions. Say Y if you want to be able to read files from and
  828. write files to an OS/2 HPFS partition on your hard drive. OS/2
  829. floppies however are in regular MSDOS format, so you don't need this
  830. option in order to be able to read them. Read
  831. <file:Documentation/filesystems/hpfs.txt>.
  832. To compile this file system support as a module, choose M here: the
  833. module will be called hpfs. If unsure, say N.
  834. config QNX4FS_FS
  835. tristate "QNX4 file system support (read only)"
  836. depends on BLOCK
  837. help
  838. This is the file system used by the real-time operating systems
  839. QNX 4 and QNX 6 (the latter is also called QNX RTP).
  840. Further information is available at <http://www.qnx.com/>.
  841. Say Y if you intend to mount QNX hard disks or floppies.
  842. Unless you say Y to "QNX4FS read-write support" below, you will
  843. only be able to read these file systems.
  844. To compile this file system support as a module, choose M here: the
  845. module will be called qnx4.
  846. If you don't know whether you need it, then you don't need it:
  847. answer N.
  848. config QNX4FS_RW
  849. bool "QNX4FS write support (DANGEROUS)"
  850. depends on QNX4FS_FS && EXPERIMENTAL && BROKEN
  851. help
  852. Say Y if you want to test write support for QNX4 file systems.
  853. It's currently broken, so for now:
  854. answer N.
  855. config ROMFS_FS
  856. tristate "ROM file system support"
  857. depends on BLOCK
  858. ---help---
  859. This is a very small read-only file system mainly intended for
  860. initial ram disks of installation disks, but it could be used for
  861. other read-only media as well. Read
  862. <file:Documentation/filesystems/romfs.txt> for details.
  863. To compile this file system support as a module, choose M here: the
  864. module will be called romfs. Note that the file system of your
  865. root partition (the one containing the directory /) cannot be a
  866. module.
  867. If you don't know whether you need it, then you don't need it:
  868. answer N.
  869. config SYSV_FS
  870. tristate "System V/Xenix/V7/Coherent file system support"
  871. depends on BLOCK
  872. help
  873. SCO, Xenix and Coherent are commercial Unix systems for Intel
  874. machines, and Version 7 was used on the DEC PDP-11. Saying Y
  875. here would allow you to read from their floppies and hard disk
  876. partitions.
  877. If you have floppies or hard disk partitions like that, it is likely
  878. that they contain binaries from those other Unix systems; in order
  879. to run these binaries, you will want to install linux-abi which is
  880. a set of kernel modules that lets you run SCO, Xenix, Wyse,
  881. UnixWare, Dell Unix and System V programs under Linux. It is
  882. available via FTP (user: ftp) from
  883. <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
  884. NOTE: that will work only for binaries from Intel-based systems;
  885. PDP ones will have to wait until somebody ports Linux to -11 ;-)
  886. If you only intend to mount files from some other Unix over the
  887. network using NFS, you don't need the System V file system support
  888. (but you need NFS file system support obviously).
  889. Note that this option is generally not needed for floppies, since a
  890. good portable way to transport files and directories between unixes
  891. (and even other operating systems) is given by the tar program ("man
  892. tar" or preferably "info tar"). Note also that this option has
  893. nothing whatsoever to do with the option "System V IPC". Read about
  894. the System V file system in
  895. <file:Documentation/filesystems/sysv-fs.txt>.
  896. Saying Y here will enlarge your kernel by about 27 KB.
  897. To compile this as a module, choose M here: the module will be called
  898. sysv.
  899. If you haven't heard about all of this before, it's safe to say N.
  900. config UFS_FS
  901. tristate "UFS file system support (read only)"
  902. depends on BLOCK
  903. help
  904. BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
  905. OpenBSD and NeXTstep) use a file system called UFS. Some System V
  906. Unixes can create and mount hard disk partitions and diskettes using
  907. this file system as well. Saying Y here will allow you to read from
  908. these partitions; if you also want to write to them, say Y to the
  909. experimental "UFS file system write support", below. Please read the
  910. file <file:Documentation/filesystems/ufs.txt> for more information.
  911. The recently released UFS2 variant (used in FreeBSD 5.x) is
  912. READ-ONLY supported.
  913. Note that this option is generally not needed for floppies, since a
  914. good portable way to transport files and directories between unixes
  915. (and even other operating systems) is given by the tar program ("man
  916. tar" or preferably "info tar").
  917. When accessing NeXTstep files, you may need to convert them from the
  918. NeXT character set to the Latin1 character set; use the program
  919. recode ("info recode") for this purpose.
  920. To compile the UFS file system support as a module, choose M here: the
  921. module will be called ufs.
  922. If you haven't heard about all of this before, it's safe to say N.
  923. config UFS_FS_WRITE
  924. bool "UFS file system write support (DANGEROUS)"
  925. depends on UFS_FS && EXPERIMENTAL
  926. help
  927. Say Y here if you want to try writing to UFS partitions. This is
  928. experimental, so you should back up your UFS partitions beforehand.
  929. config UFS_DEBUG
  930. bool "UFS debugging"
  931. depends on UFS_FS
  932. help
  933. If you are experiencing any problems with the UFS filesystem, say
  934. Y here. This will result in _many_ additional debugging messages to be
  935. written to the system log.
  936. endmenu
  937. menuconfig NETWORK_FILESYSTEMS
  938. bool "Network File Systems"
  939. default y
  940. depends on NET
  941. ---help---
  942. Say Y here to get to see options for network filesystems and
  943. filesystem-related networking code, such as NFS daemon and
  944. RPCSEC security modules.
  945. This option alone does not add any kernel code.
  946. If you say N, all options in this submenu will be skipped and
  947. disabled; if unsure, say Y here.
  948. if NETWORK_FILESYSTEMS
  949. config NFS_FS
  950. tristate "NFS client support"
  951. depends on INET
  952. select LOCKD
  953. select SUNRPC
  954. select NFS_ACL_SUPPORT if NFS_V3_ACL
  955. help
  956. Choose Y here if you want to access files residing on other
  957. computers using Sun's Network File System protocol. To compile
  958. this file system support as a module, choose M here: the module
  959. will be called nfs.
  960. To mount file systems exported by NFS servers, you also need to
  961. install the user space mount.nfs command which can be found in
  962. the Linux nfs-utils package, available from http://linux-nfs.org/.
  963. Information about using the mount command is available in the
  964. mount(8) man page. More detail about the Linux NFS client
  965. implementation is available via the nfs(5) man page.
  966. Below you can choose which versions of the NFS protocol are
  967. available in the kernel to mount NFS servers. Support for NFS
  968. version 2 (RFC 1094) is always available when NFS_FS is selected.
  969. To configure a system which mounts its root file system via NFS
  970. at boot time, say Y here, select "Kernel level IP
  971. autoconfiguration" in the NETWORK menu, and select "Root file
  972. system on NFS" below. You cannot compile this file system as a
  973. module in this case.
  974. If unsure, say N.
  975. config NFS_V3
  976. bool "NFS client support for NFS version 3"
  977. depends on NFS_FS
  978. help
  979. This option enables support for version 3 of the NFS protocol
  980. (RFC 1813) in the kernel's NFS client.
  981. If unsure, say Y.
  982. config NFS_V3_ACL
  983. bool "NFS client support for the NFSv3 ACL protocol extension"
  984. depends on NFS_V3
  985. help
  986. Some NFS servers support an auxiliary NFSv3 ACL protocol that
  987. Sun added to Solaris but never became an official part of the
  988. NFS version 3 protocol. This protocol extension allows
  989. applications on NFS clients to manipulate POSIX Access Control
  990. Lists on files residing on NFS servers. NFS servers enforce
  991. ACLs on local files whether this protocol is available or not.
  992. Choose Y here if your NFS server supports the Solaris NFSv3 ACL
  993. protocol extension and you want your NFS client to allow
  994. applications to access and modify ACLs on files on the server.
  995. Most NFS servers don't support the Solaris NFSv3 ACL protocol
  996. extension. You can choose N here or specify the "noacl" mount
  997. option to prevent your NFS client from trying to use the NFSv3
  998. ACL protocol.
  999. If unsure, say N.
  1000. config NFS_V4
  1001. bool "NFS client support for NFS version 4 (EXPERIMENTAL)"
  1002. depends on NFS_FS && EXPERIMENTAL
  1003. select RPCSEC_GSS_KRB5
  1004. help
  1005. This option enables support for version 4 of the NFS protocol
  1006. (RFC 3530) in the kernel's NFS client.
  1007. To mount NFS servers using NFSv4, you also need to install user
  1008. space programs which can be found in the Linux nfs-utils package,
  1009. available from http://linux-nfs.org/.
  1010. If unsure, say N.
  1011. config ROOT_NFS
  1012. bool "Root file system on NFS"
  1013. depends on NFS_FS=y && IP_PNP
  1014. help
  1015. If you want your system to mount its root file system via NFS,
  1016. choose Y here. This is common practice for managing systems
  1017. without local permanent storage. For details, read
  1018. <file:Documentation/filesystems/nfsroot.txt>.
  1019. Most people say N here.
  1020. config NFSD
  1021. tristate "NFS server support"
  1022. depends on INET
  1023. select LOCKD
  1024. select SUNRPC
  1025. select EXPORTFS
  1026. select NFS_ACL_SUPPORT if NFSD_V2_ACL
  1027. help
  1028. Choose Y here if you want to allow other computers to access
  1029. files residing on this system using Sun's Network File System
  1030. protocol. To compile the NFS server support as a module,
  1031. choose M here: the module will be called nfsd.
  1032. You may choose to use a user-space NFS server instead, in which
  1033. case you can choose N here.
  1034. To export local file systems using NFS, you also need to install
  1035. user space programs which can be found in the Linux nfs-utils
  1036. package, available from http://linux-nfs.org/. More detail about
  1037. the Linux NFS server implementation is available via the
  1038. exports(5) man page.
  1039. Below you can choose which versions of the NFS protocol are
  1040. available to clients mounting the NFS server on this system.
  1041. Support for NFS version 2 (RFC 1094) is always available when
  1042. CONFIG_NFSD is selected.
  1043. If unsure, say N.
  1044. config NFSD_V2_ACL
  1045. bool
  1046. depends on NFSD
  1047. config NFSD_V3
  1048. bool "NFS server support for NFS version 3"
  1049. depends on NFSD
  1050. help
  1051. This option enables support in your system's NFS server for
  1052. version 3 of the NFS protocol (RFC 1813).
  1053. If unsure, say Y.
  1054. config NFSD_V3_ACL
  1055. bool "NFS server support for the NFSv3 ACL protocol extension"
  1056. depends on NFSD_V3
  1057. select NFSD_V2_ACL
  1058. help
  1059. Solaris NFS servers support an auxiliary NFSv3 ACL protocol that
  1060. never became an official part of the NFS version 3 protocol.
  1061. This protocol extension allows applications on NFS clients to
  1062. manipulate POSIX Access Control Lists on files residing on NFS
  1063. servers. NFS servers enforce POSIX ACLs on local files whether
  1064. this protocol is available or not.
  1065. This option enables support in your system's NFS server for the
  1066. NFSv3 ACL protocol extension allowing NFS clients to manipulate
  1067. POSIX ACLs on files exported by your system's NFS server. NFS
  1068. clients which support the Solaris NFSv3 ACL protocol can then
  1069. access and modify ACLs on your NFS server.
  1070. To store ACLs on your NFS server, you also need to enable ACL-
  1071. related CONFIG options for your local file systems of choice.
  1072. If unsure, say N.
  1073. config NFSD_V4
  1074. bool "NFS server support for NFS version 4 (EXPERIMENTAL)"
  1075. depends on NFSD && PROC_FS && EXPERIMENTAL
  1076. select NFSD_V3
  1077. select FS_POSIX_ACL
  1078. select RPCSEC_GSS_KRB5
  1079. help
  1080. This option enables support in your system's NFS server for
  1081. version 4 of the NFS protocol (RFC 3530).
  1082. To export files using NFSv4, you need to install additional user
  1083. space programs which can be found in the Linux nfs-utils package,
  1084. available from http://linux-nfs.org/.
  1085. If unsure, say N.
  1086. config LOCKD
  1087. tristate
  1088. config LOCKD_V4
  1089. bool
  1090. depends on NFSD_V3 || NFS_V3
  1091. default y
  1092. config EXPORTFS
  1093. tristate
  1094. config NFS_ACL_SUPPORT
  1095. tristate
  1096. select FS_POSIX_ACL
  1097. config NFS_COMMON
  1098. bool
  1099. depends on NFSD || NFS_FS
  1100. default y
  1101. config SUNRPC
  1102. tristate
  1103. config SUNRPC_GSS
  1104. tristate
  1105. config SUNRPC_XPRT_RDMA
  1106. tristate
  1107. depends on SUNRPC && INFINIBAND && EXPERIMENTAL
  1108. default SUNRPC && INFINIBAND
  1109. help
  1110. This option enables an RPC client transport capability that
  1111. allows the NFS client to mount servers via an RDMA-enabled
  1112. transport.
  1113. To compile RPC client RDMA transport support as a module,
  1114. choose M here: the module will be called xprtrdma.
  1115. If unsure, say N.
  1116. config SUNRPC_REGISTER_V4
  1117. bool "Register local RPC services via rpcbind v4 (EXPERIMENTAL)"
  1118. depends on SUNRPC && EXPERIMENTAL
  1119. default n
  1120. help
  1121. Sun added support for registering RPC services at an IPv6
  1122. address by creating two new versions of the rpcbind protocol
  1123. (RFC 1833).
  1124. This option enables support in the kernel RPC server for
  1125. registering kernel RPC services via version 4 of the rpcbind
  1126. protocol. If you enable this option, you must run a portmapper
  1127. daemon that supports rpcbind protocol version 4.
  1128. Serving NFS over IPv6 from knfsd (the kernel's NFS server)
  1129. requires that you enable this option and use a portmapper that
  1130. supports rpcbind version 4.
  1131. If unsure, say N to get traditional behavior (register kernel
  1132. RPC services using only rpcbind version 2). Distributions
  1133. using the legacy Linux portmapper daemon must say N here.
  1134. config RPCSEC_GSS_KRB5
  1135. tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
  1136. depends on SUNRPC && EXPERIMENTAL
  1137. select SUNRPC_GSS
  1138. select CRYPTO
  1139. select CRYPTO_MD5
  1140. select CRYPTO_DES
  1141. select CRYPTO_CBC
  1142. help
  1143. Choose Y here to enable Secure RPC using the Kerberos version 5
  1144. GSS-API mechanism (RFC 1964).
  1145. Secure RPC calls with Kerberos require an auxiliary user-space
  1146. daemon which may be found in the Linux nfs-utils package
  1147. available from http://linux-nfs.org/. In addition, user-space
  1148. Kerberos support should be installed.
  1149. If unsure, say N.
  1150. config RPCSEC_GSS_SPKM3
  1151. tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
  1152. depends on SUNRPC && EXPERIMENTAL
  1153. select SUNRPC_GSS
  1154. select CRYPTO
  1155. select CRYPTO_MD5
  1156. select CRYPTO_DES
  1157. select CRYPTO_CAST5
  1158. select CRYPTO_CBC
  1159. help
  1160. Choose Y here to enable Secure RPC using the SPKM3 public key
  1161. GSS-API mechansim (RFC 2025).
  1162. Secure RPC calls with SPKM3 require an auxiliary userspace
  1163. daemon which may be found in the Linux nfs-utils package
  1164. available from http://linux-nfs.org/.
  1165. If unsure, say N.
  1166. config SMB_FS
  1167. tristate "SMB file system support (OBSOLETE, please use CIFS)"
  1168. depends on INET
  1169. select NLS
  1170. help
  1171. SMB (Server Message Block) is the protocol Windows for Workgroups
  1172. (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
  1173. files and printers over local networks. Saying Y here allows you to
  1174. mount their file systems (often called "shares" in this context) and
  1175. access them just like any other Unix directory. Currently, this
  1176. works only if the Windows machines use TCP/IP as the underlying
  1177. transport protocol, and not NetBEUI. For details, read
  1178. <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
  1179. available from <http://www.tldp.org/docs.html#howto>.
  1180. Note: if you just want your box to act as an SMB *server* and make
  1181. files and printing services available to Windows clients (which need
  1182. to have a TCP/IP stack), you don't need to say Y here; you can use
  1183. the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
  1184. for that.
  1185. General information about how to connect Linux, Windows machines and
  1186. Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
  1187. To compile the SMB support as a module, choose M here:
  1188. the module will be called smbfs. Most people say N, however.
  1189. config SMB_NLS_DEFAULT
  1190. bool "Use a default NLS"
  1191. depends on SMB_FS
  1192. help
  1193. Enabling this will make smbfs use nls translations by default. You
  1194. need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
  1195. settings and you need to give the default nls for the SMB server as
  1196. CONFIG_SMB_NLS_REMOTE.
  1197. The nls settings can be changed at mount time, if your smbmount
  1198. supports that, using the codepage and iocharset parameters.
  1199. smbmount from samba 2.2.0 or later supports this.
  1200. config SMB_NLS_REMOTE
  1201. string "Default Remote NLS Option"
  1202. depends on SMB_NLS_DEFAULT
  1203. default "cp437"
  1204. help
  1205. This setting allows you to specify a default value for which
  1206. codepage the server uses. If this field is left blank no
  1207. translations will be done by default. The local codepage/charset
  1208. default to CONFIG_NLS_DEFAULT.
  1209. The nls settings can be changed at mount time, if your smbmount
  1210. supports that, using the codepage and iocharset parameters.
  1211. smbmount from samba 2.2.0 or later supports this.
  1212. source "fs/cifs/Kconfig"
  1213. config NCP_FS
  1214. tristate "NCP file system support (to mount NetWare volumes)"
  1215. depends on IPX!=n || INET
  1216. help
  1217. NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
  1218. used by Novell NetWare clients to talk to file servers. It is to
  1219. IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
  1220. to mount NetWare file server volumes and to access them just like
  1221. any other Unix directory. For details, please read the file
  1222. <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
  1223. the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
  1224. You do not have to say Y here if you want your Linux box to act as a
  1225. file *server* for Novell NetWare clients.
  1226. General information about how to connect Linux, Windows machines and
  1227. Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
  1228. To compile this as a module, choose M here: the module will be called
  1229. ncpfs. Say N unless you are connected to a Novell network.
  1230. source "fs/ncpfs/Kconfig"
  1231. config CODA_FS
  1232. tristate "Coda file system support (advanced network fs)"
  1233. depends on INET
  1234. help
  1235. Coda is an advanced network file system, similar to NFS in that it
  1236. enables you to mount file systems of a remote server and access them
  1237. with regular Unix commands as if they were sitting on your hard
  1238. disk. Coda has several advantages over NFS: support for
  1239. disconnected operation (e.g. for laptops), read/write server
  1240. replication, security model for authentication and encryption,
  1241. persistent client caches and write back caching.
  1242. If you say Y here, your Linux box will be able to act as a Coda
  1243. *client*. You will need user level code as well, both for the
  1244. client and server. Servers are currently user level, i.e. they need
  1245. no kernel support. Please read
  1246. <file:Documentation/filesystems/coda.txt> and check out the Coda
  1247. home page <http://www.coda.cs.cmu.edu/>.
  1248. To compile the coda client support as a module, choose M here: the
  1249. module will be called coda.
  1250. config AFS_FS
  1251. tristate "Andrew File System support (AFS) (EXPERIMENTAL)"
  1252. depends on INET && EXPERIMENTAL
  1253. select AF_RXRPC
  1254. help
  1255. If you say Y here, you will get an experimental Andrew File System
  1256. driver. It currently only supports unsecured read-only AFS access.
  1257. See <file:Documentation/filesystems/afs.txt> for more information.
  1258. If unsure, say N.
  1259. config AFS_DEBUG
  1260. bool "AFS dynamic debugging"
  1261. depends on AFS_FS
  1262. help
  1263. Say Y here to make runtime controllable debugging messages appear.
  1264. See <file:Documentation/filesystems/afs.txt> for more information.
  1265. If unsure, say N.
  1266. config 9P_FS
  1267. tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
  1268. depends on INET && NET_9P && EXPERIMENTAL
  1269. help
  1270. If you say Y here, you will get experimental support for
  1271. Plan 9 resource sharing via the 9P2000 protocol.
  1272. See <http://v9fs.sf.net> for more information.
  1273. If unsure, say N.
  1274. endif # NETWORK_FILESYSTEMS
  1275. if BLOCK
  1276. menu "Partition Types"
  1277. source "fs/partitions/Kconfig"
  1278. endmenu
  1279. endif
  1280. source "fs/nls/Kconfig"
  1281. source "fs/dlm/Kconfig"
  1282. endmenu