Kconfig 68 KB

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