Kconfig 77 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868869870871872873874875876877878879880881882883884885886887888889890891892893894895896897898899900901902903904905906907908909910911912913914915916917918919920921922923924925926927928929930931932933934935936937938939940941942943944945946947948949950951952953954955956957958959960961962963964965966967968969970971972973974975976977978979980981982983984985986987988989990991992993994995996997998999100010011002100310041005100610071008100910101011101210131014101510161017101810191020102110221023102410251026102710281029103010311032103310341035103610371038103910401041104210431044104510461047104810491050105110521053105410551056105710581059106010611062106310641065106610671068106910701071107210731074107510761077107810791080108110821083108410851086108710881089109010911092109310941095109610971098109911001101110211031104110511061107110811091110111111121113111411151116111711181119112011211122112311241125112611271128112911301131113211331134113511361137113811391140114111421143114411451146114711481149115011511152115311541155115611571158115911601161116211631164116511661167116811691170117111721173117411751176117711781179118011811182118311841185118611871188118911901191119211931194119511961197119811991200120112021203120412051206120712081209121012111212121312141215121612171218121912201221122212231224122512261227122812291230123112321233123412351236123712381239124012411242124312441245124612471248124912501251125212531254125512561257125812591260126112621263126412651266126712681269127012711272127312741275127612771278127912801281128212831284128512861287128812891290129112921293129412951296129712981299130013011302130313041305130613071308130913101311131213131314131513161317131813191320132113221323132413251326132713281329133013311332133313341335133613371338133913401341134213431344134513461347134813491350135113521353135413551356135713581359136013611362136313641365136613671368136913701371137213731374137513761377137813791380138113821383138413851386138713881389139013911392139313941395139613971398139914001401140214031404140514061407140814091410141114121413141414151416141714181419142014211422142314241425142614271428142914301431143214331434143514361437143814391440144114421443144414451446144714481449145014511452145314541455145614571458145914601461146214631464146514661467146814691470147114721473147414751476147714781479148014811482148314841485148614871488148914901491149214931494149514961497149814991500150115021503150415051506150715081509151015111512151315141515151615171518151915201521152215231524152515261527152815291530153115321533153415351536153715381539154015411542154315441545154615471548154915501551155215531554155515561557155815591560156115621563156415651566156715681569157015711572157315741575157615771578157915801581158215831584158515861587158815891590159115921593159415951596159715981599160016011602160316041605160616071608160916101611161216131614161516161617161816191620162116221623162416251626162716281629163016311632163316341635163616371638163916401641164216431644164516461647164816491650165116521653165416551656165716581659166016611662166316641665166616671668166916701671167216731674167516761677167816791680168116821683168416851686168716881689169016911692169316941695169616971698169917001701170217031704170517061707170817091710171117121713171417151716171717181719172017211722172317241725172617271728172917301731173217331734173517361737173817391740174117421743174417451746174717481749175017511752175317541755175617571758175917601761176217631764176517661767176817691770177117721773177417751776177717781779178017811782178317841785178617871788178917901791179217931794179517961797179817991800180118021803180418051806180718081809181018111812181318141815181618171818181918201821182218231824182518261827182818291830183118321833183418351836183718381839184018411842184318441845184618471848184918501851185218531854185518561857185818591860186118621863186418651866186718681869187018711872187318741875187618771878187918801881188218831884188518861887188818891890189118921893189418951896189718981899190019011902190319041905190619071908190919101911191219131914191519161917191819191920192119221923192419251926192719281929193019311932193319341935193619371938193919401941194219431944194519461947194819491950195119521953195419551956195719581959196019611962196319641965196619671968196919701971197219731974197519761977197819791980198119821983198419851986198719881989199019911992199319941995199619971998199920002001200220032004200520062007200820092010201120122013201420152016201720182019202020212022202320242025202620272028202920302031203220332034203520362037203820392040204120422043204420452046204720482049205020512052205320542055205620572058205920602061206220632064206520662067206820692070207120722073207420752076207720782079208020812082208320842085208620872088208920902091209220932094209520962097209820992100210121022103210421052106210721082109211021112112211321142115211621172118211921202121212221232124212521262127212821292130213121322133213421352136213721382139214021412142214321442145214621472148214921502151215221532154215521562157215821592160216121622163216421652166
  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_DEBUG_MASKLOG
  386. bool "OCFS2 logging support"
  387. depends on OCFS2_FS
  388. default y
  389. help
  390. The ocfs2 filesystem has an extensive logging system. The system
  391. allows selection of events to log via files in /sys/o2cb/logmask/.
  392. This option will enlarge your kernel, but it allows debugging of
  393. ocfs2 filesystem issues.
  394. config OCFS2_DEBUG_FS
  395. bool "OCFS2 expensive checks"
  396. depends on OCFS2_FS
  397. default n
  398. help
  399. This option will enable expensive consistency checks. Enable
  400. this option for debugging only as it is likely to decrease
  401. performance of the filesystem.
  402. endif # BLOCK
  403. config DNOTIFY
  404. bool "Dnotify support"
  405. default y
  406. help
  407. Dnotify is a directory-based per-fd file change notification system
  408. that uses signals to communicate events to user-space. There exist
  409. superior alternatives, but some applications may still rely on
  410. dnotify.
  411. If unsure, say Y.
  412. config INOTIFY
  413. bool "Inotify file change notification support"
  414. default y
  415. ---help---
  416. Say Y here to enable inotify support. Inotify is a file change
  417. notification system and a replacement for dnotify. Inotify fixes
  418. numerous shortcomings in dnotify and introduces several new features
  419. including multiple file events, one-shot support, and unmount
  420. notification.
  421. For more information, see <file:Documentation/filesystems/inotify.txt>
  422. If unsure, say Y.
  423. config INOTIFY_USER
  424. bool "Inotify support for userspace"
  425. depends on INOTIFY
  426. default y
  427. ---help---
  428. Say Y here to enable inotify support for userspace, including the
  429. associated system calls. Inotify allows monitoring of both files and
  430. directories via a single open fd. Events are read from the file
  431. descriptor, which is also select()- and poll()-able.
  432. For more information, see <file:Documentation/filesystems/inotify.txt>
  433. If unsure, say Y.
  434. config QUOTA
  435. bool "Quota support"
  436. help
  437. If you say Y here, you will be able to set per user limits for disk
  438. usage (also called disk quotas). Currently, it works for the
  439. ext2, ext3, and reiserfs file system. ext3 also supports journalled
  440. quotas for which you don't need to run quotacheck(8) after an unclean
  441. shutdown.
  442. For further details, read the Quota mini-HOWTO, available from
  443. <http://www.tldp.org/docs.html#howto>, or the documentation provided
  444. with the quota tools. Probably the quota support is only useful for
  445. multi user systems. If unsure, say N.
  446. config QUOTA_NETLINK_INTERFACE
  447. bool "Report quota messages through netlink interface"
  448. depends on QUOTA && NET
  449. help
  450. If you say Y here, quota warnings (about exceeding softlimit, reaching
  451. hardlimit, etc.) will be reported through netlink interface. If unsure,
  452. say Y.
  453. config PRINT_QUOTA_WARNING
  454. bool "Print quota warnings to console (OBSOLETE)"
  455. depends on QUOTA
  456. default y
  457. help
  458. If you say Y here, quota warnings (about exceeding softlimit, reaching
  459. hardlimit, etc.) will be printed to the process' controlling terminal.
  460. Note that this behavior is currently deprecated and may go away in
  461. future. Please use notification via netlink socket instead.
  462. config QFMT_V1
  463. tristate "Old quota format support"
  464. depends on QUOTA
  465. help
  466. This quota format was (is) used by kernels earlier than 2.4.22. If
  467. you have quota working and you don't want to convert to new quota
  468. format say Y here.
  469. config QFMT_V2
  470. tristate "Quota format v2 support"
  471. depends on QUOTA
  472. help
  473. This quota format allows using quotas with 32-bit UIDs/GIDs. If you
  474. need this functionality say Y here.
  475. config QUOTACTL
  476. bool
  477. depends on XFS_QUOTA || QUOTA
  478. default y
  479. config AUTOFS_FS
  480. tristate "Kernel automounter support"
  481. help
  482. The automounter is a tool to automatically mount remote file systems
  483. on demand. This implementation is partially kernel-based to reduce
  484. overhead in the already-mounted case; this is unlike the BSD
  485. automounter (amd), which is a pure user space daemon.
  486. To use the automounter you need the user-space tools from the autofs
  487. package; you can find the location in <file:Documentation/Changes>.
  488. You also want to answer Y to "NFS file system support", below.
  489. If you want to use the newer version of the automounter with more
  490. features, say N here and say Y to "Kernel automounter v4 support",
  491. below.
  492. To compile this support as a module, choose M here: the module will be
  493. called autofs.
  494. If you are not a part of a fairly large, distributed network, you
  495. probably do not need an automounter, and can say N here.
  496. config AUTOFS4_FS
  497. tristate "Kernel automounter version 4 support (also supports v3)"
  498. help
  499. The automounter is a tool to automatically mount remote file systems
  500. on demand. This implementation is partially kernel-based to reduce
  501. overhead in the already-mounted case; this is unlike the BSD
  502. automounter (amd), which is a pure user space daemon.
  503. To use the automounter you need the user-space tools from
  504. <ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4/>; you also
  505. want to answer Y to "NFS file system support", below.
  506. To compile this support as a module, choose M here: the module will be
  507. called autofs4. You will need to add "alias autofs autofs4" to your
  508. modules configuration file.
  509. If you are not a part of a fairly large, distributed network or
  510. don't have a laptop which needs to dynamically reconfigure to the
  511. local network, you probably do not need an automounter, and can say
  512. N here.
  513. config FUSE_FS
  514. tristate "Filesystem in Userspace support"
  515. help
  516. With FUSE it is possible to implement a fully functional filesystem
  517. in a userspace program.
  518. There's also companion library: libfuse. This library along with
  519. utilities is available from the FUSE homepage:
  520. <http://fuse.sourceforge.net/>
  521. See <file:Documentation/filesystems/fuse.txt> for more information.
  522. See <file:Documentation/Changes> for needed library/utility version.
  523. If you want to develop a userspace FS, or if you want to use
  524. a filesystem based on FUSE, answer Y or M.
  525. config GENERIC_ACL
  526. bool
  527. select FS_POSIX_ACL
  528. if BLOCK
  529. menu "CD-ROM/DVD Filesystems"
  530. config ISO9660_FS
  531. tristate "ISO 9660 CDROM file system support"
  532. help
  533. This is the standard file system used on CD-ROMs. It was previously
  534. known as "High Sierra File System" and is called "hsfs" on other
  535. Unix systems. The so-called Rock-Ridge extensions which allow for
  536. long Unix filenames and symbolic links are also supported by this
  537. driver. If you have a CD-ROM drive and want to do more with it than
  538. just listen to audio CDs and watch its LEDs, say Y (and read
  539. <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO,
  540. available from <http://www.tldp.org/docs.html#howto>), thereby
  541. enlarging your kernel by about 27 KB; otherwise say N.
  542. To compile this file system support as a module, choose M here: the
  543. module will be called isofs.
  544. config JOLIET
  545. bool "Microsoft Joliet CDROM extensions"
  546. depends on ISO9660_FS
  547. select NLS
  548. help
  549. Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system
  550. which allows for long filenames in unicode format (unicode is the
  551. new 16 bit character code, successor to ASCII, which encodes the
  552. characters of almost all languages of the world; see
  553. <http://www.unicode.org/> for more information). Say Y here if you
  554. want to be able to read Joliet CD-ROMs under Linux.
  555. config ZISOFS
  556. bool "Transparent decompression extension"
  557. depends on ISO9660_FS
  558. select ZLIB_INFLATE
  559. help
  560. This is a Linux-specific extension to RockRidge which lets you store
  561. data in compressed form on a CD-ROM and have it transparently
  562. decompressed when the CD-ROM is accessed. See
  563. <http://www.kernel.org/pub/linux/utils/fs/zisofs/> for the tools
  564. necessary to create such a filesystem. Say Y here if you want to be
  565. able to read such compressed CD-ROMs.
  566. config UDF_FS
  567. tristate "UDF file system support"
  568. select CRC_ITU_T
  569. help
  570. This is the new file system used on some CD-ROMs and DVDs. Say Y if
  571. you intend to mount DVD discs or CDRW's written in packet mode, or
  572. if written to by other UDF utilities, such as DirectCD.
  573. Please read <file:Documentation/filesystems/udf.txt>.
  574. To compile this file system support as a module, choose M here: the
  575. module will be called udf.
  576. If unsure, say N.
  577. config UDF_NLS
  578. bool
  579. default y
  580. depends on (UDF_FS=m && NLS) || (UDF_FS=y && NLS=y)
  581. endmenu
  582. endif # BLOCK
  583. if BLOCK
  584. menu "DOS/FAT/NT Filesystems"
  585. config FAT_FS
  586. tristate
  587. select NLS
  588. help
  589. If you want to use one of the FAT-based file systems (the MS-DOS and
  590. VFAT (Windows 95) file systems), then you must say Y or M here
  591. to include FAT support. You will then be able to mount partitions or
  592. diskettes with FAT-based file systems and transparently access the
  593. files on them, i.e. MSDOS files will look and behave just like all
  594. other Unix files.
  595. This FAT support is not a file system in itself, it only provides
  596. the foundation for the other file systems. You will have to say Y or
  597. M to at least one of "MSDOS fs support" or "VFAT fs support" in
  598. order to make use of it.
  599. Another way to read and write MSDOS floppies and hard drive
  600. partitions from within Linux (but not transparently) is with the
  601. mtools ("man mtools") program suite. You don't need to say Y here in
  602. order to do that.
  603. If you need to move large files on floppies between a DOS and a
  604. Linux box, say Y here, mount the floppy under Linux with an MSDOS
  605. file system and use GNU tar's M option. GNU tar is a program
  606. available for Unix and DOS ("man tar" or "info tar").
  607. The FAT support will enlarge your kernel by about 37 KB. If unsure,
  608. say Y.
  609. To compile this as a module, choose M here: the module will be called
  610. fat. Note that if you compile the FAT support as a module, you
  611. cannot compile any of the FAT-based file systems into the kernel
  612. -- they will have to be modules as well.
  613. config MSDOS_FS
  614. tristate "MSDOS fs support"
  615. select FAT_FS
  616. help
  617. This allows you to mount MSDOS partitions of your hard drive (unless
  618. they are compressed; to access compressed MSDOS partitions under
  619. Linux, you can either use the DOS emulator DOSEMU, described in the
  620. DOSEMU-HOWTO, available from
  621. <http://www.tldp.org/docs.html#howto>, or try dmsdosfs in
  622. <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you
  623. intend to use dosemu with a non-compressed MSDOS partition, say Y
  624. here) and MSDOS floppies. This means that file access becomes
  625. transparent, i.e. the MSDOS files look and behave just like all
  626. other Unix files.
  627. If you have Windows 95 or Windows NT installed on your MSDOS
  628. partitions, you should use the VFAT file system (say Y to "VFAT fs
  629. support" below), or you will not be able to see the long filenames
  630. generated by Windows 95 / Windows NT.
  631. This option will enlarge your kernel by about 7 KB. If unsure,
  632. answer Y. This will only work if you said Y to "DOS FAT fs support"
  633. as well. To compile this as a module, choose M here: the module will
  634. be called msdos.
  635. config VFAT_FS
  636. tristate "VFAT (Windows-95) fs support"
  637. select FAT_FS
  638. help
  639. This option provides support for normal Windows file systems with
  640. long filenames. That includes non-compressed FAT-based file systems
  641. used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
  642. programs from the mtools package.
  643. The VFAT support enlarges your kernel by about 10 KB and it only
  644. works if you said Y to the "DOS FAT fs support" above. Please read
  645. the file <file:Documentation/filesystems/vfat.txt> for details. If
  646. unsure, say Y.
  647. To compile this as a module, choose M here: the module will be called
  648. vfat.
  649. config FAT_DEFAULT_CODEPAGE
  650. int "Default codepage for FAT"
  651. depends on MSDOS_FS || VFAT_FS
  652. default 437
  653. help
  654. This option should be set to the codepage of your FAT filesystems.
  655. It can be overridden with the "codepage" mount option.
  656. See <file:Documentation/filesystems/vfat.txt> for more information.
  657. config FAT_DEFAULT_IOCHARSET
  658. string "Default iocharset for FAT"
  659. depends on VFAT_FS
  660. default "iso8859-1"
  661. help
  662. Set this to the default input/output character set you'd
  663. like FAT to use. It should probably match the character set
  664. that most of your FAT filesystems use, and can be overridden
  665. with the "iocharset" mount option for FAT filesystems.
  666. Note that "utf8" is not recommended for FAT filesystems.
  667. If unsure, you shouldn't set "utf8" here.
  668. See <file:Documentation/filesystems/vfat.txt> for more information.
  669. config NTFS_FS
  670. tristate "NTFS file system support"
  671. select NLS
  672. help
  673. NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003.
  674. Saying Y or M here enables read support. There is partial, but
  675. safe, write support available. For write support you must also
  676. say Y to "NTFS write support" below.
  677. There are also a number of user-space tools available, called
  678. ntfsprogs. These include ntfsundelete and ntfsresize, that work
  679. without NTFS support enabled in the kernel.
  680. This is a rewrite from scratch of Linux NTFS support and replaced
  681. the old NTFS code starting with Linux 2.5.11. A backport to
  682. the Linux 2.4 kernel series is separately available as a patch
  683. from the project web site.
  684. For more information see <file:Documentation/filesystems/ntfs.txt>
  685. and <http://linux-ntfs.sourceforge.net/>.
  686. To compile this file system support as a module, choose M here: the
  687. module will be called ntfs.
  688. If you are not using Windows NT, 2000, XP or 2003 in addition to
  689. Linux on your computer it is safe to say N.
  690. config NTFS_DEBUG
  691. bool "NTFS debugging support"
  692. depends on NTFS_FS
  693. help
  694. If you are experiencing any problems with the NTFS file system, say
  695. Y here. This will result in additional consistency checks to be
  696. performed by the driver as well as additional debugging messages to
  697. be written to the system log. Note that debugging messages are
  698. disabled by default. To enable them, supply the option debug_msgs=1
  699. at the kernel command line when booting the kernel or as an option
  700. to insmod when loading the ntfs module. Once the driver is active,
  701. you can enable debugging messages by doing (as root):
  702. echo 1 > /proc/sys/fs/ntfs-debug
  703. Replacing the "1" with "0" would disable debug messages.
  704. If you leave debugging messages disabled, this results in little
  705. overhead, but enabling debug messages results in very significant
  706. slowdown of the system.
  707. When reporting bugs, please try to have available a full dump of
  708. debugging messages while the misbehaviour was occurring.
  709. config NTFS_RW
  710. bool "NTFS write support"
  711. depends on NTFS_FS
  712. help
  713. This enables the partial, but safe, write support in the NTFS driver.
  714. The only supported operation is overwriting existing files, without
  715. changing the file length. No file or directory creation, deletion or
  716. renaming is possible. Note only non-resident files can be written to
  717. so you may find that some very small files (<500 bytes or so) cannot
  718. be written to.
  719. While we cannot guarantee that it will not damage any data, we have
  720. so far not received a single report where the driver would have
  721. damaged someones data so we assume it is perfectly safe to use.
  722. Note: While write support is safe in this version (a rewrite from
  723. scratch of the NTFS support), it should be noted that the old NTFS
  724. write support, included in Linux 2.5.10 and before (since 1997),
  725. is not safe.
  726. This is currently useful with TopologiLinux. TopologiLinux is run
  727. on top of any DOS/Microsoft Windows system without partitioning your
  728. hard disk. Unlike other Linux distributions TopologiLinux does not
  729. need its own partition. For more information see
  730. <http://topologi-linux.sourceforge.net/>
  731. It is perfectly safe to say N here.
  732. endmenu
  733. endif # BLOCK
  734. menu "Pseudo filesystems"
  735. config PROC_FS
  736. bool "/proc file system support" if EMBEDDED
  737. default y
  738. help
  739. This is a virtual file system providing information about the status
  740. of the system. "Virtual" means that it doesn't take up any space on
  741. your hard disk: the files are created on the fly by the kernel when
  742. you try to access them. Also, you cannot read the files with older
  743. version of the program less: you need to use more or cat.
  744. It's totally cool; for example, "cat /proc/interrupts" gives
  745. information about what the different IRQs are used for at the moment
  746. (there is a small number of Interrupt ReQuest lines in your computer
  747. that are used by the attached devices to gain the CPU's attention --
  748. often a source of trouble if two devices are mistakenly configured
  749. to use the same IRQ). The program procinfo to display some
  750. information about your system gathered from the /proc file system.
  751. Before you can use the /proc file system, it has to be mounted,
  752. meaning it has to be given a location in the directory hierarchy.
  753. That location should be /proc. A command such as "mount -t proc proc
  754. /proc" or the equivalent line in /etc/fstab does the job.
  755. The /proc file system is explained in the file
  756. <file:Documentation/filesystems/proc.txt> and on the proc(5) manpage
  757. ("man 5 proc").
  758. This option will enlarge your kernel by about 67 KB. Several
  759. programs depend on this, so everyone should say Y here.
  760. config PROC_KCORE
  761. bool "/proc/kcore support" if !ARM
  762. depends on PROC_FS && MMU
  763. config PROC_VMCORE
  764. bool "/proc/vmcore support (EXPERIMENTAL)"
  765. depends on PROC_FS && EXPERIMENTAL && CRASH_DUMP
  766. default y
  767. help
  768. Exports the dump image of crashed kernel in ELF format.
  769. config PROC_SYSCTL
  770. bool "Sysctl support (/proc/sys)" if EMBEDDED
  771. depends on PROC_FS
  772. select SYSCTL
  773. default y
  774. ---help---
  775. The sysctl interface provides a means of dynamically changing
  776. certain kernel parameters and variables on the fly without requiring
  777. a recompile of the kernel or reboot of the system. The primary
  778. interface is through /proc/sys. If you say Y here a tree of
  779. modifiable sysctl entries will be generated beneath the
  780. /proc/sys directory. They are explained in the files
  781. in <file:Documentation/sysctl/>. Note that enabling this
  782. option will enlarge the kernel by at least 8 KB.
  783. As it is generally a good thing, you should say Y here unless
  784. building a kernel for install/rescue disks or your system is very
  785. limited in memory.
  786. config SYSFS
  787. bool "sysfs file system support" if EMBEDDED
  788. default y
  789. help
  790. The sysfs filesystem is a virtual filesystem that the kernel uses to
  791. export internal kernel objects, their attributes, and their
  792. relationships to one another.
  793. Users can use sysfs to ascertain useful information about the running
  794. kernel, such as the devices the kernel has discovered on each bus and
  795. which driver each is bound to. sysfs can also be used to tune devices
  796. and other kernel subsystems.
  797. Some system agents rely on the information in sysfs to operate.
  798. /sbin/hotplug uses device and object attributes in sysfs to assist in
  799. delegating policy decisions, like persistently naming devices.
  800. sysfs is currently used by the block subsystem to mount the root
  801. partition. If sysfs is disabled you must specify the boot device on
  802. the kernel boot command line via its major and minor numbers. For
  803. example, "root=03:01" for /dev/hda1.
  804. Designers of embedded systems may wish to say N here to conserve space.
  805. config TMPFS
  806. bool "Virtual memory file system support (former shm fs)"
  807. help
  808. Tmpfs is a file system which keeps all files in virtual memory.
  809. Everything in tmpfs is temporary in the sense that no files will be
  810. created on your hard drive. The files live in memory and swap
  811. space. If you unmount a tmpfs instance, everything stored therein is
  812. lost.
  813. See <file:Documentation/filesystems/tmpfs.txt> for details.
  814. config TMPFS_POSIX_ACL
  815. bool "Tmpfs POSIX Access Control Lists"
  816. depends on TMPFS
  817. select GENERIC_ACL
  818. help
  819. POSIX Access Control Lists (ACLs) support permissions for users and
  820. groups beyond the owner/group/world scheme.
  821. To learn more about Access Control Lists, visit the POSIX ACLs for
  822. Linux website <http://acl.bestbits.at/>.
  823. If you don't know what Access Control Lists are, say N.
  824. config HUGETLBFS
  825. bool "HugeTLB file system support"
  826. depends on X86 || IA64 || PPC64 || SPARC64 || (SUPERH && MMU) || BROKEN
  827. help
  828. hugetlbfs is a filesystem backing for HugeTLB pages, based on
  829. ramfs. For architectures that support it, say Y here and read
  830. <file:Documentation/vm/hugetlbpage.txt> for details.
  831. If unsure, say N.
  832. config HUGETLB_PAGE
  833. def_bool HUGETLBFS
  834. config CONFIGFS_FS
  835. tristate "Userspace-driven configuration filesystem"
  836. depends on SYSFS
  837. help
  838. configfs is a ram-based filesystem that provides the converse
  839. of sysfs's functionality. Where sysfs is a filesystem-based
  840. view of kernel objects, configfs is a filesystem-based manager
  841. of kernel objects, or config_items.
  842. Both sysfs and configfs can and should exist together on the
  843. same system. One is not a replacement for the other.
  844. endmenu
  845. menu "Miscellaneous filesystems"
  846. config ADFS_FS
  847. tristate "ADFS file system support (EXPERIMENTAL)"
  848. depends on BLOCK && EXPERIMENTAL
  849. help
  850. The Acorn Disc Filing System is the standard file system of the
  851. RiscOS operating system which runs on Acorn's ARM-based Risc PC
  852. systems and the Acorn Archimedes range of machines. If you say Y
  853. here, Linux will be able to read from ADFS partitions on hard drives
  854. and from ADFS-formatted floppy discs. If you also want to be able to
  855. write to those devices, say Y to "ADFS write support" below.
  856. The ADFS partition should be the first partition (i.e.,
  857. /dev/[hs]d?1) on each of your drives. Please read the file
  858. <file:Documentation/filesystems/adfs.txt> for further details.
  859. To compile this code as a module, choose M here: the module will be
  860. called adfs.
  861. If unsure, say N.
  862. config ADFS_FS_RW
  863. bool "ADFS write support (DANGEROUS)"
  864. depends on ADFS_FS
  865. help
  866. If you say Y here, you will be able to write to ADFS partitions on
  867. hard drives and ADFS-formatted floppy disks. This is experimental
  868. codes, so if you're unsure, say N.
  869. config AFFS_FS
  870. tristate "Amiga FFS file system support (EXPERIMENTAL)"
  871. depends on BLOCK && EXPERIMENTAL
  872. help
  873. The Fast File System (FFS) is the common file system used on hard
  874. disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
  875. if you want to be able to read and write files from and to an Amiga
  876. FFS partition on your hard drive. Amiga floppies however cannot be
  877. read with this driver due to an incompatibility of the floppy
  878. controller used in an Amiga and the standard floppy controller in
  879. PCs and workstations. Read <file:Documentation/filesystems/affs.txt>
  880. and <file:fs/affs/Changes>.
  881. With this driver you can also mount disk files used by Bernd
  882. Schmidt's Un*X Amiga Emulator
  883. (<http://www.freiburg.linux.de/~uae/>).
  884. If you want to do this, you will also need to say Y or M to "Loop
  885. device support", above.
  886. To compile this file system support as a module, choose M here: the
  887. module will be called affs. If unsure, say N.
  888. config ECRYPT_FS
  889. tristate "eCrypt filesystem layer support (EXPERIMENTAL)"
  890. depends on EXPERIMENTAL && KEYS && CRYPTO && NET
  891. help
  892. Encrypted filesystem that operates on the VFS layer. See
  893. <file:Documentation/filesystems/ecryptfs.txt> to learn more about
  894. eCryptfs. Userspace components are required and can be
  895. obtained from <http://ecryptfs.sf.net>.
  896. To compile this file system support as a module, choose M here: the
  897. module will be called ecryptfs.
  898. config HFS_FS
  899. tristate "Apple Macintosh file system support (EXPERIMENTAL)"
  900. depends on BLOCK && EXPERIMENTAL
  901. select NLS
  902. help
  903. If you say Y here, you will be able to mount Macintosh-formatted
  904. floppy disks and hard drive partitions with full read-write access.
  905. Please read <file:Documentation/filesystems/hfs.txt> to learn about
  906. the available mount options.
  907. To compile this file system support as a module, choose M here: the
  908. module will be called hfs.
  909. config HFSPLUS_FS
  910. tristate "Apple Extended HFS file system support"
  911. depends on BLOCK
  912. select NLS
  913. select NLS_UTF8
  914. help
  915. If you say Y here, you will be able to mount extended format
  916. Macintosh-formatted hard drive partitions with full read-write access.
  917. This file system is often called HFS+ and was introduced with
  918. MacOS 8. It includes all Mac specific filesystem data such as
  919. data forks and creator codes, but it also has several UNIX
  920. style features such as file ownership and permissions.
  921. config BEFS_FS
  922. tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)"
  923. depends on BLOCK && EXPERIMENTAL
  924. select NLS
  925. help
  926. The BeOS File System (BeFS) is the native file system of Be, Inc's
  927. BeOS. Notable features include support for arbitrary attributes
  928. on files and directories, and database-like indices on selected
  929. attributes. (Also note that this driver doesn't make those features
  930. available at this time). It is a 64 bit filesystem, so it supports
  931. extremely large volumes and files.
  932. If you use this filesystem, you should also say Y to at least one
  933. of the NLS (native language support) options below.
  934. If you don't know what this is about, say N.
  935. To compile this as a module, choose M here: the module will be
  936. called befs.
  937. config BEFS_DEBUG
  938. bool "Debug BeFS"
  939. depends on BEFS_FS
  940. help
  941. If you say Y here, you can use the 'debug' mount option to enable
  942. debugging output from the driver.
  943. config BFS_FS
  944. tristate "BFS file system support (EXPERIMENTAL)"
  945. depends on BLOCK && EXPERIMENTAL
  946. help
  947. Boot File System (BFS) is a file system used under SCO UnixWare to
  948. allow the bootloader access to the kernel image and other important
  949. files during the boot process. It is usually mounted under /stand
  950. and corresponds to the slice marked as "STAND" in the UnixWare
  951. partition. You should say Y if you want to read or write the files
  952. on your /stand slice from within Linux. You then also need to say Y
  953. to "UnixWare slices support", below. More information about the BFS
  954. file system is contained in the file
  955. <file:Documentation/filesystems/bfs.txt>.
  956. If you don't know what this is about, say N.
  957. To compile this as a module, choose M here: the module will be called
  958. bfs. Note that the file system of your root partition (the one
  959. containing the directory /) cannot be compiled as a module.
  960. config EFS_FS
  961. tristate "EFS file system support (read only) (EXPERIMENTAL)"
  962. depends on BLOCK && EXPERIMENTAL
  963. help
  964. EFS is an older file system used for non-ISO9660 CD-ROMs and hard
  965. disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
  966. uses the XFS file system for hard disk partitions however).
  967. This implementation only offers read-only access. If you don't know
  968. what all this is about, it's safe to say N. For more information
  969. about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
  970. To compile the EFS file system support as a module, choose M here: the
  971. module will be called efs.
  972. config JFFS2_FS
  973. tristate "Journalling Flash File System v2 (JFFS2) support"
  974. select CRC32
  975. depends on MTD
  976. help
  977. JFFS2 is the second generation of the Journalling Flash File System
  978. for use on diskless embedded devices. It provides improved wear
  979. levelling, compression and support for hard links. You cannot use
  980. this on normal block devices, only on 'MTD' devices.
  981. Further information on the design and implementation of JFFS2 is
  982. available at <http://sources.redhat.com/jffs2/>.
  983. config JFFS2_FS_DEBUG
  984. int "JFFS2 debugging verbosity (0 = quiet, 2 = noisy)"
  985. depends on JFFS2_FS
  986. default "0"
  987. help
  988. This controls the amount of debugging messages produced by the JFFS2
  989. code. Set it to zero for use in production systems. For evaluation,
  990. testing and debugging, it's advisable to set it to one. This will
  991. enable a few assertions and will print debugging messages at the
  992. KERN_DEBUG loglevel, where they won't normally be visible. Level 2
  993. is unlikely to be useful - it enables extra debugging in certain
  994. areas which at one point needed debugging, but when the bugs were
  995. located and fixed, the detailed messages were relegated to level 2.
  996. If reporting bugs, please try to have available a full dump of the
  997. messages at debug level 1 while the misbehaviour was occurring.
  998. config JFFS2_FS_WRITEBUFFER
  999. bool "JFFS2 write-buffering support"
  1000. depends on JFFS2_FS
  1001. default y
  1002. help
  1003. This enables the write-buffering support in JFFS2.
  1004. This functionality is required to support JFFS2 on the following
  1005. types of flash devices:
  1006. - NAND flash
  1007. - NOR flash with transparent ECC
  1008. - DataFlash
  1009. config JFFS2_FS_WBUF_VERIFY
  1010. bool "Verify JFFS2 write-buffer reads"
  1011. depends on JFFS2_FS_WRITEBUFFER
  1012. default n
  1013. help
  1014. This causes JFFS2 to read back every page written through the
  1015. write-buffer, and check for errors.
  1016. config JFFS2_SUMMARY
  1017. bool "JFFS2 summary support (EXPERIMENTAL)"
  1018. depends on JFFS2_FS && EXPERIMENTAL
  1019. default n
  1020. help
  1021. This feature makes it possible to use summary information
  1022. for faster filesystem mount.
  1023. The summary information can be inserted into a filesystem image
  1024. by the utility 'sumtool'.
  1025. If unsure, say 'N'.
  1026. config JFFS2_FS_XATTR
  1027. bool "JFFS2 XATTR support (EXPERIMENTAL)"
  1028. depends on JFFS2_FS && EXPERIMENTAL
  1029. default n
  1030. help
  1031. Extended attributes are name:value pairs associated with inodes by
  1032. the kernel or by users (see the attr(5) manual page, or visit
  1033. <http://acl.bestbits.at/> for details).
  1034. If unsure, say N.
  1035. config JFFS2_FS_POSIX_ACL
  1036. bool "JFFS2 POSIX Access Control Lists"
  1037. depends on JFFS2_FS_XATTR
  1038. default y
  1039. select FS_POSIX_ACL
  1040. help
  1041. Posix Access Control Lists (ACLs) support permissions for users and
  1042. groups beyond the owner/group/world scheme.
  1043. To learn more about Access Control Lists, visit the Posix ACLs for
  1044. Linux website <http://acl.bestbits.at/>.
  1045. If you don't know what Access Control Lists are, say N
  1046. config JFFS2_FS_SECURITY
  1047. bool "JFFS2 Security Labels"
  1048. depends on JFFS2_FS_XATTR
  1049. default y
  1050. help
  1051. Security labels support alternative access control models
  1052. implemented by security modules like SELinux. This option
  1053. enables an extended attribute handler for file security
  1054. labels in the jffs2 filesystem.
  1055. If you are not using a security module that requires using
  1056. extended attributes for file security labels, say N.
  1057. config JFFS2_COMPRESSION_OPTIONS
  1058. bool "Advanced compression options for JFFS2"
  1059. depends on JFFS2_FS
  1060. default n
  1061. help
  1062. Enabling this option allows you to explicitly choose which
  1063. compression modules, if any, are enabled in JFFS2. Removing
  1064. compressors can mean you cannot read existing file systems,
  1065. and enabling experimental compressors can mean that you
  1066. write a file system which cannot be read by a standard kernel.
  1067. If unsure, you should _definitely_ say 'N'.
  1068. config JFFS2_ZLIB
  1069. bool "JFFS2 ZLIB compression support" if JFFS2_COMPRESSION_OPTIONS
  1070. select ZLIB_INFLATE
  1071. select ZLIB_DEFLATE
  1072. depends on JFFS2_FS
  1073. default y
  1074. help
  1075. Zlib is designed to be a free, general-purpose, legally unencumbered,
  1076. lossless data-compression library for use on virtually any computer
  1077. hardware and operating system. See <http://www.gzip.org/zlib/> for
  1078. further information.
  1079. Say 'Y' if unsure.
  1080. config JFFS2_LZO
  1081. bool "JFFS2 LZO compression support" if JFFS2_COMPRESSION_OPTIONS
  1082. select LZO_COMPRESS
  1083. select LZO_DECOMPRESS
  1084. depends on JFFS2_FS
  1085. default n
  1086. help
  1087. minilzo-based compression. Generally works better than Zlib.
  1088. This feature was added in July, 2007. Say 'N' if you need
  1089. compatibility with older bootloaders or kernels.
  1090. config JFFS2_RTIME
  1091. bool "JFFS2 RTIME compression support" if JFFS2_COMPRESSION_OPTIONS
  1092. depends on JFFS2_FS
  1093. default y
  1094. help
  1095. Rtime does manage to recompress already-compressed data. Say 'Y' if unsure.
  1096. config JFFS2_RUBIN
  1097. bool "JFFS2 RUBIN compression support" if JFFS2_COMPRESSION_OPTIONS
  1098. depends on JFFS2_FS
  1099. default n
  1100. help
  1101. RUBINMIPS and DYNRUBIN compressors. Say 'N' if unsure.
  1102. choice
  1103. prompt "JFFS2 default compression mode" if JFFS2_COMPRESSION_OPTIONS
  1104. default JFFS2_CMODE_PRIORITY
  1105. depends on JFFS2_FS
  1106. help
  1107. You can set here the default compression mode of JFFS2 from
  1108. the available compression modes. Don't touch if unsure.
  1109. config JFFS2_CMODE_NONE
  1110. bool "no compression"
  1111. help
  1112. Uses no compression.
  1113. config JFFS2_CMODE_PRIORITY
  1114. bool "priority"
  1115. help
  1116. Tries the compressors in a predefined order and chooses the first
  1117. successful one.
  1118. config JFFS2_CMODE_SIZE
  1119. bool "size (EXPERIMENTAL)"
  1120. help
  1121. Tries all compressors and chooses the one which has the smallest
  1122. result.
  1123. config JFFS2_CMODE_FAVOURLZO
  1124. bool "Favour LZO"
  1125. help
  1126. Tries all compressors and chooses the one which has the smallest
  1127. result but gives some preference to LZO (which has faster
  1128. decompression) at the expense of size.
  1129. endchoice
  1130. config CRAMFS
  1131. tristate "Compressed ROM file system support (cramfs)"
  1132. depends on BLOCK
  1133. select ZLIB_INFLATE
  1134. help
  1135. Saying Y here includes support for CramFs (Compressed ROM File
  1136. System). CramFs is designed to be a simple, small, and compressed
  1137. file system for ROM based embedded systems. CramFs is read-only,
  1138. limited to 256MB file systems (with 16MB files), and doesn't support
  1139. 16/32 bits uid/gid, hard links and timestamps.
  1140. See <file:Documentation/filesystems/cramfs.txt> and
  1141. <file:fs/cramfs/README> for further information.
  1142. To compile this as a module, choose M here: the module will be called
  1143. cramfs. Note that the root file system (the one containing the
  1144. directory /) cannot be compiled as a module.
  1145. If unsure, say N.
  1146. config VXFS_FS
  1147. tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
  1148. depends on BLOCK
  1149. help
  1150. FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
  1151. file system format. VERITAS VxFS(TM) is the standard file system
  1152. of SCO UnixWare (and possibly others) and optionally available
  1153. for Sunsoft Solaris, HP-UX and many other operating systems.
  1154. Currently only readonly access is supported.
  1155. NOTE: the file system type as used by mount(1), mount(2) and
  1156. fstab(5) is 'vxfs' as it describes the file system format, not
  1157. the actual driver.
  1158. To compile this as a module, choose M here: the module will be
  1159. called freevxfs. If unsure, say N.
  1160. config MINIX_FS
  1161. tristate "Minix file system support"
  1162. depends on BLOCK
  1163. help
  1164. Minix is a simple operating system used in many classes about OS's.
  1165. The minix file system (method to organize files on a hard disk
  1166. partition or a floppy disk) was the original file system for Linux,
  1167. but has been superseded by the second extended file system ext2fs.
  1168. You don't want to use the minix file system on your hard disk
  1169. because of certain built-in restrictions, but it is sometimes found
  1170. on older Linux floppy disks. This option will enlarge your kernel
  1171. by about 28 KB. If unsure, say N.
  1172. To compile this file system support as a module, choose M here: the
  1173. module will be called minix. Note that the file system of your root
  1174. partition (the one containing the directory /) cannot be compiled as
  1175. a module.
  1176. config HPFS_FS
  1177. tristate "OS/2 HPFS file system support"
  1178. depends on BLOCK
  1179. help
  1180. OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
  1181. is the file system used for organizing files on OS/2 hard disk
  1182. partitions. Say Y if you want to be able to read files from and
  1183. write files to an OS/2 HPFS partition on your hard drive. OS/2
  1184. floppies however are in regular MSDOS format, so you don't need this
  1185. option in order to be able to read them. Read
  1186. <file:Documentation/filesystems/hpfs.txt>.
  1187. To compile this file system support as a module, choose M here: the
  1188. module will be called hpfs. If unsure, say N.
  1189. config QNX4FS_FS
  1190. tristate "QNX4 file system support (read only)"
  1191. depends on BLOCK
  1192. help
  1193. This is the file system used by the real-time operating systems
  1194. QNX 4 and QNX 6 (the latter is also called QNX RTP).
  1195. Further information is available at <http://www.qnx.com/>.
  1196. Say Y if you intend to mount QNX hard disks or floppies.
  1197. Unless you say Y to "QNX4FS read-write support" below, you will
  1198. only be able to read these file systems.
  1199. To compile this file system support as a module, choose M here: the
  1200. module will be called qnx4.
  1201. If you don't know whether you need it, then you don't need it:
  1202. answer N.
  1203. config QNX4FS_RW
  1204. bool "QNX4FS write support (DANGEROUS)"
  1205. depends on QNX4FS_FS && EXPERIMENTAL && BROKEN
  1206. help
  1207. Say Y if you want to test write support for QNX4 file systems.
  1208. It's currently broken, so for now:
  1209. answer N.
  1210. config ROMFS_FS
  1211. tristate "ROM file system support"
  1212. depends on BLOCK
  1213. ---help---
  1214. This is a very small read-only file system mainly intended for
  1215. initial ram disks of installation disks, but it could be used for
  1216. other read-only media as well. Read
  1217. <file:Documentation/filesystems/romfs.txt> for details.
  1218. To compile this file system support as a module, choose M here: the
  1219. module will be called romfs. Note that the file system of your
  1220. root partition (the one containing the directory /) cannot be a
  1221. module.
  1222. If you don't know whether you need it, then you don't need it:
  1223. answer N.
  1224. config SYSV_FS
  1225. tristate "System V/Xenix/V7/Coherent file system support"
  1226. depends on BLOCK
  1227. help
  1228. SCO, Xenix and Coherent are commercial Unix systems for Intel
  1229. machines, and Version 7 was used on the DEC PDP-11. Saying Y
  1230. here would allow you to read from their floppies and hard disk
  1231. partitions.
  1232. If you have floppies or hard disk partitions like that, it is likely
  1233. that they contain binaries from those other Unix systems; in order
  1234. to run these binaries, you will want to install linux-abi which is
  1235. a set of kernel modules that lets you run SCO, Xenix, Wyse,
  1236. UnixWare, Dell Unix and System V programs under Linux. It is
  1237. available via FTP (user: ftp) from
  1238. <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
  1239. NOTE: that will work only for binaries from Intel-based systems;
  1240. PDP ones will have to wait until somebody ports Linux to -11 ;-)
  1241. If you only intend to mount files from some other Unix over the
  1242. network using NFS, you don't need the System V file system support
  1243. (but you need NFS file system support obviously).
  1244. Note that this option is generally not needed for floppies, since a
  1245. good portable way to transport files and directories between unixes
  1246. (and even other operating systems) is given by the tar program ("man
  1247. tar" or preferably "info tar"). Note also that this option has
  1248. nothing whatsoever to do with the option "System V IPC". Read about
  1249. the System V file system in
  1250. <file:Documentation/filesystems/sysv-fs.txt>.
  1251. Saying Y here will enlarge your kernel by about 27 KB.
  1252. To compile this as a module, choose M here: the module will be called
  1253. sysv.
  1254. If you haven't heard about all of this before, it's safe to say N.
  1255. config UFS_FS
  1256. tristate "UFS file system support (read only)"
  1257. depends on BLOCK
  1258. help
  1259. BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
  1260. OpenBSD and NeXTstep) use a file system called UFS. Some System V
  1261. Unixes can create and mount hard disk partitions and diskettes using
  1262. this file system as well. Saying Y here will allow you to read from
  1263. these partitions; if you also want to write to them, say Y to the
  1264. experimental "UFS file system write support", below. Please read the
  1265. file <file:Documentation/filesystems/ufs.txt> for more information.
  1266. The recently released UFS2 variant (used in FreeBSD 5.x) is
  1267. READ-ONLY supported.
  1268. If you only intend to mount files from some other Unix over the
  1269. network using NFS, you don't need the UFS file system support (but
  1270. you need NFS file system support obviously).
  1271. Note that this option is generally not needed for floppies, since a
  1272. good portable way to transport files and directories between unixes
  1273. (and even other operating systems) is given by the tar program ("man
  1274. tar" or preferably "info tar").
  1275. When accessing NeXTstep files, you may need to convert them from the
  1276. NeXT character set to the Latin1 character set; use the program
  1277. recode ("info recode") for this purpose.
  1278. To compile the UFS file system support as a module, choose M here: the
  1279. module will be called ufs.
  1280. If you haven't heard about all of this before, it's safe to say N.
  1281. config UFS_FS_WRITE
  1282. bool "UFS file system write support (DANGEROUS)"
  1283. depends on UFS_FS && EXPERIMENTAL
  1284. help
  1285. Say Y here if you want to try writing to UFS partitions. This is
  1286. experimental, so you should back up your UFS partitions beforehand.
  1287. config UFS_DEBUG
  1288. bool "UFS debugging"
  1289. depends on UFS_FS
  1290. help
  1291. If you are experiencing any problems with the UFS filesystem, say
  1292. Y here. This will result in _many_ additional debugging messages to be
  1293. written to the system log.
  1294. endmenu
  1295. menuconfig NETWORK_FILESYSTEMS
  1296. bool "Network File Systems"
  1297. default y
  1298. depends on NET
  1299. ---help---
  1300. Say Y here to get to see options for network filesystems and
  1301. filesystem-related networking code, such as NFS daemon and
  1302. RPCSEC security modules.
  1303. This option alone does not add any kernel code.
  1304. If you say N, all options in this submenu will be skipped and
  1305. disabled; if unsure, say Y here.
  1306. if NETWORK_FILESYSTEMS
  1307. config NFS_FS
  1308. tristate "NFS file system support"
  1309. depends on INET
  1310. select LOCKD
  1311. select SUNRPC
  1312. select NFS_ACL_SUPPORT if NFS_V3_ACL
  1313. help
  1314. If you are connected to some other (usually local) Unix computer
  1315. (using SLIP, PLIP, PPP or Ethernet) and want to mount files residing
  1316. on that computer (the NFS server) using the Network File Sharing
  1317. protocol, say Y. "Mounting files" means that the client can access
  1318. the files with usual UNIX commands as if they were sitting on the
  1319. client's hard disk. For this to work, the server must run the
  1320. programs nfsd and mountd (but does not need to have NFS file system
  1321. support enabled in its kernel). NFS is explained in the Network
  1322. Administrator's Guide, available from
  1323. <http://www.tldp.org/docs.html#guide>, on its man page: "man
  1324. nfs", and in the NFS-HOWTO.
  1325. A superior but less widely used alternative to NFS is provided by
  1326. the Coda file system; see "Coda file system support" below.
  1327. If you say Y here, you should have said Y to TCP/IP networking also.
  1328. This option would enlarge your kernel by about 27 KB.
  1329. To compile this file system support as a module, choose M here: the
  1330. module will be called nfs.
  1331. If you are configuring a diskless machine which will mount its root
  1332. file system over NFS at boot time, say Y here and to "Kernel
  1333. level IP autoconfiguration" above and to "Root file system on NFS"
  1334. below. You cannot compile this driver as a module in this case.
  1335. There are two packages designed for booting diskless machines over
  1336. the net: netboot, available from
  1337. <http://ftp1.sourceforge.net/netboot/>, and Etherboot,
  1338. available from <http://ftp1.sourceforge.net/etherboot/>.
  1339. If you don't know what all this is about, say N.
  1340. config NFS_V3
  1341. bool "Provide NFSv3 client support"
  1342. depends on NFS_FS
  1343. help
  1344. Say Y here if you want your NFS client to be able to speak version
  1345. 3 of the NFS protocol.
  1346. If unsure, say Y.
  1347. config NFS_V3_ACL
  1348. bool "Provide client support for the NFSv3 ACL protocol extension"
  1349. depends on NFS_V3
  1350. help
  1351. Implement the NFSv3 ACL protocol extension for manipulating POSIX
  1352. Access Control Lists. The server should also be compiled with
  1353. the NFSv3 ACL protocol extension; see the CONFIG_NFSD_V3_ACL option.
  1354. If unsure, say N.
  1355. config NFS_V4
  1356. bool "Provide NFSv4 client support (EXPERIMENTAL)"
  1357. depends on NFS_FS && EXPERIMENTAL
  1358. select RPCSEC_GSS_KRB5
  1359. help
  1360. Say Y here if you want your NFS client to be able to speak the newer
  1361. version 4 of the NFS protocol.
  1362. Note: Requires auxiliary userspace daemons which may be found on
  1363. http://www.citi.umich.edu/projects/nfsv4/
  1364. If unsure, say N.
  1365. config NFSD
  1366. tristate "NFS server support"
  1367. depends on INET
  1368. select LOCKD
  1369. select SUNRPC
  1370. select EXPORTFS
  1371. select NFS_ACL_SUPPORT if NFSD_V2_ACL
  1372. help
  1373. Choose Y here if you want to allow other computers to access
  1374. files residing on this system using Sun's Network File System
  1375. protocol. To compile the NFS server support as a module,
  1376. choose M here: the module will be called nfsd.
  1377. You may choose to use a user-space NFS server instead, in which
  1378. case you can choose N here.
  1379. To export local file systems using NFS, you also need to install
  1380. user space programs which can be found in the Linux nfs-utils
  1381. package, available from http://linux-nfs.org/. More detail about
  1382. the Linux NFS server implementation is available via the
  1383. exports(5) man page.
  1384. Below you can choose which versions of the NFS protocol are
  1385. available to clients mounting the NFS server on this system.
  1386. Support for NFS version 2 (RFC 1094) is always available when
  1387. CONFIG_NFSD is selected.
  1388. If unsure, say N.
  1389. config NFSD_V2_ACL
  1390. bool
  1391. depends on NFSD
  1392. config NFSD_V3
  1393. bool "NFS server support for NFS version 3"
  1394. depends on NFSD
  1395. help
  1396. This option enables support in your system's NFS server for
  1397. version 3 of the NFS protocol (RFC 1813).
  1398. If unsure, say Y.
  1399. config NFSD_V3_ACL
  1400. bool "NFS server support for the NFSv3 ACL protocol extension"
  1401. depends on NFSD_V3
  1402. select NFSD_V2_ACL
  1403. help
  1404. Solaris NFS servers support an auxiliary NFSv3 ACL protocol that
  1405. never became an official part of the NFS version 3 protocol.
  1406. This protocol extension allows applications on NFS clients to
  1407. manipulate POSIX Access Control Lists on files residing on NFS
  1408. servers. NFS servers enforce POSIX ACLs on local files whether
  1409. this protocol is available or not.
  1410. This option enables support in your system's NFS server for the
  1411. NFSv3 ACL protocol extension allowing NFS clients to manipulate
  1412. POSIX ACLs on files exported by your system's NFS server. NFS
  1413. clients which support the Solaris NFSv3 ACL protocol can then
  1414. access and modify ACLs on your NFS server.
  1415. To store ACLs on your NFS server, you also need to enable ACL-
  1416. related CONFIG options for your local file systems of choice.
  1417. If unsure, say N.
  1418. config NFSD_V4
  1419. bool "NFS server support for NFS version 4 (EXPERIMENTAL)"
  1420. depends on NFSD && PROC_FS && EXPERIMENTAL
  1421. select NFSD_V3
  1422. select FS_POSIX_ACL
  1423. select RPCSEC_GSS_KRB5
  1424. help
  1425. This option enables support in your system's NFS server for
  1426. version 4 of the NFS protocol (RFC 3530).
  1427. To export files using NFSv4, you need to install additional user
  1428. space programs which can be found in the Linux nfs-utils package,
  1429. available from http://linux-nfs.org/.
  1430. If unsure, say N.
  1431. config ROOT_NFS
  1432. bool "Root file system on NFS"
  1433. depends on NFS_FS=y && IP_PNP
  1434. help
  1435. If you want your Linux box to mount its whole root file system (the
  1436. one containing the directory /) from some other computer over the
  1437. net via NFS (presumably because your box doesn't have a hard disk),
  1438. say Y. Read <file:Documentation/filesystems/nfsroot.txt> for
  1439. details. It is likely that in this case, you also want to say Y to
  1440. "Kernel level IP autoconfiguration" so that your box can discover
  1441. its network address at boot time.
  1442. Most people say N here.
  1443. config LOCKD
  1444. tristate
  1445. config LOCKD_V4
  1446. bool
  1447. depends on NFSD_V3 || NFS_V3
  1448. default y
  1449. config EXPORTFS
  1450. tristate
  1451. config NFS_ACL_SUPPORT
  1452. tristate
  1453. select FS_POSIX_ACL
  1454. config NFS_COMMON
  1455. bool
  1456. depends on NFSD || NFS_FS
  1457. default y
  1458. config SUNRPC
  1459. tristate
  1460. config SUNRPC_GSS
  1461. tristate
  1462. config SUNRPC_XPRT_RDMA
  1463. tristate
  1464. depends on SUNRPC && INFINIBAND && EXPERIMENTAL
  1465. default SUNRPC && INFINIBAND
  1466. help
  1467. This option enables an RPC client transport capability that
  1468. allows the NFS client to mount servers via an RDMA-enabled
  1469. transport.
  1470. To compile RPC client RDMA transport support as a module,
  1471. choose M here: the module will be called xprtrdma.
  1472. If unsure, say N.
  1473. config SUNRPC_BIND34
  1474. bool "Support for rpcbind versions 3 & 4 (EXPERIMENTAL)"
  1475. depends on SUNRPC && EXPERIMENTAL
  1476. default n
  1477. help
  1478. RPC requests over IPv6 networks require support for larger
  1479. addresses when performing an RPC bind. Sun added support for
  1480. IPv6 addressing by creating two new versions of the rpcbind
  1481. protocol (RFC 1833).
  1482. This option enables support in the kernel RPC client for
  1483. querying rpcbind servers via versions 3 and 4 of the rpcbind
  1484. protocol. The kernel automatically falls back to version 2
  1485. if a remote rpcbind service does not support versions 3 or 4.
  1486. By themselves, these new versions do not provide support for
  1487. RPC over IPv6, but the new protocol versions are necessary to
  1488. support it.
  1489. If unsure, say N to get traditional behavior (version 2 rpcbind
  1490. requests only).
  1491. config RPCSEC_GSS_KRB5
  1492. tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
  1493. depends on SUNRPC && EXPERIMENTAL
  1494. select SUNRPC_GSS
  1495. select CRYPTO
  1496. select CRYPTO_MD5
  1497. select CRYPTO_DES
  1498. select CRYPTO_CBC
  1499. help
  1500. Choose Y here to enable Secure RPC using the Kerberos version 5
  1501. GSS-API mechanism (RFC 1964).
  1502. Secure RPC calls with Kerberos require an auxiliary user-space
  1503. daemon which may be found in the Linux nfs-utils package
  1504. available from http://linux-nfs.org/. In addition, user-space
  1505. Kerberos support should be installed.
  1506. If unsure, say N.
  1507. config RPCSEC_GSS_SPKM3
  1508. tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
  1509. depends on SUNRPC && EXPERIMENTAL
  1510. select SUNRPC_GSS
  1511. select CRYPTO
  1512. select CRYPTO_MD5
  1513. select CRYPTO_DES
  1514. select CRYPTO_CAST5
  1515. select CRYPTO_CBC
  1516. help
  1517. Choose Y here to enable Secure RPC using the SPKM3 public key
  1518. GSS-API mechansim (RFC 2025).
  1519. Secure RPC calls with SPKM3 require an auxiliary userspace
  1520. daemon which may be found in the Linux nfs-utils package
  1521. available from http://linux-nfs.org/.
  1522. If unsure, say N.
  1523. config SMB_FS
  1524. tristate "SMB file system support (OBSOLETE, please use CIFS)"
  1525. depends on INET
  1526. select NLS
  1527. help
  1528. SMB (Server Message Block) is the protocol Windows for Workgroups
  1529. (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
  1530. files and printers over local networks. Saying Y here allows you to
  1531. mount their file systems (often called "shares" in this context) and
  1532. access them just like any other Unix directory. Currently, this
  1533. works only if the Windows machines use TCP/IP as the underlying
  1534. transport protocol, and not NetBEUI. For details, read
  1535. <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
  1536. available from <http://www.tldp.org/docs.html#howto>.
  1537. Note: if you just want your box to act as an SMB *server* and make
  1538. files and printing services available to Windows clients (which need
  1539. to have a TCP/IP stack), you don't need to say Y here; you can use
  1540. the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
  1541. for that.
  1542. General information about how to connect Linux, Windows machines and
  1543. Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
  1544. To compile the SMB support as a module, choose M here:
  1545. the module will be called smbfs. Most people say N, however.
  1546. config SMB_NLS_DEFAULT
  1547. bool "Use a default NLS"
  1548. depends on SMB_FS
  1549. help
  1550. Enabling this will make smbfs use nls translations by default. You
  1551. need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
  1552. settings and you need to give the default nls for the SMB server as
  1553. CONFIG_SMB_NLS_REMOTE.
  1554. The nls settings can be changed at mount time, if your smbmount
  1555. supports that, using the codepage and iocharset parameters.
  1556. smbmount from samba 2.2.0 or later supports this.
  1557. config SMB_NLS_REMOTE
  1558. string "Default Remote NLS Option"
  1559. depends on SMB_NLS_DEFAULT
  1560. default "cp437"
  1561. help
  1562. This setting allows you to specify a default value for which
  1563. codepage the server uses. If this field is left blank no
  1564. translations will be done by default. The local codepage/charset
  1565. default to CONFIG_NLS_DEFAULT.
  1566. The nls settings can be changed at mount time, if your smbmount
  1567. supports that, using the codepage and iocharset parameters.
  1568. smbmount from samba 2.2.0 or later supports this.
  1569. config CIFS
  1570. tristate "CIFS support (advanced network filesystem, SMBFS successor)"
  1571. depends on INET
  1572. select NLS
  1573. help
  1574. This is the client VFS module for the Common Internet File System
  1575. (CIFS) protocol which is the successor to the Server Message Block
  1576. (SMB) protocol, the native file sharing mechanism for most early
  1577. PC operating systems. The CIFS protocol is fully supported by
  1578. file servers such as Windows 2000 (including Windows 2003, NT 4
  1579. and Windows XP) as well by Samba (which provides excellent CIFS
  1580. server support for Linux and many other operating systems). Limited
  1581. support for OS/2 and Windows ME and similar servers is provided as
  1582. well.
  1583. The cifs module provides an advanced network file system
  1584. client for mounting to CIFS compliant servers. It includes
  1585. support for DFS (hierarchical name space), secure per-user
  1586. session establishment via Kerberos or NTLM or NTLMv2,
  1587. safe distributed caching (oplock), optional packet
  1588. signing, Unicode and other internationalization improvements.
  1589. If you need to mount to Samba or Windows from this machine, say Y.
  1590. config CIFS_STATS
  1591. bool "CIFS statistics"
  1592. depends on CIFS
  1593. help
  1594. Enabling this option will cause statistics for each server share
  1595. mounted by the cifs client to be displayed in /proc/fs/cifs/Stats
  1596. config CIFS_STATS2
  1597. bool "Extended statistics"
  1598. depends on CIFS_STATS
  1599. help
  1600. Enabling this option will allow more detailed statistics on SMB
  1601. request timing to be displayed in /proc/fs/cifs/DebugData and also
  1602. allow optional logging of slow responses to dmesg (depending on the
  1603. value of /proc/fs/cifs/cifsFYI, see fs/cifs/README for more details).
  1604. These additional statistics may have a minor effect on performance
  1605. and memory utilization.
  1606. Unless you are a developer or are doing network performance analysis
  1607. or tuning, say N.
  1608. config CIFS_WEAK_PW_HASH
  1609. bool "Support legacy servers which use weaker LANMAN security"
  1610. depends on CIFS
  1611. help
  1612. Modern CIFS servers including Samba and most Windows versions
  1613. (since 1997) support stronger NTLM (and even NTLMv2 and Kerberos)
  1614. security mechanisms. These hash the password more securely
  1615. than the mechanisms used in the older LANMAN version of the
  1616. SMB protocol but LANMAN based authentication is needed to
  1617. establish sessions with some old SMB servers.
  1618. Enabling this option allows the cifs module to mount to older
  1619. LANMAN based servers such as OS/2 and Windows 95, but such
  1620. mounts may be less secure than mounts using NTLM or more recent
  1621. security mechanisms if you are on a public network. Unless you
  1622. have a need to access old SMB servers (and are on a private
  1623. network) you probably want to say N. Even if this support
  1624. is enabled in the kernel build, LANMAN authentication will not be
  1625. used automatically. At runtime LANMAN mounts are disabled but
  1626. can be set to required (or optional) either in
  1627. /proc/fs/cifs (see fs/cifs/README for more detail) or via an
  1628. option on the mount command. This support is disabled by
  1629. default in order to reduce the possibility of a downgrade
  1630. attack.
  1631. If unsure, say N.
  1632. config CIFS_XATTR
  1633. bool "CIFS extended attributes"
  1634. depends on CIFS
  1635. help
  1636. Extended attributes are name:value pairs associated with inodes by
  1637. the kernel or by users (see the attr(5) manual page, or visit
  1638. <http://acl.bestbits.at/> for details). CIFS maps the name of
  1639. extended attributes beginning with the user namespace prefix
  1640. to SMB/CIFS EAs. EAs are stored on Windows servers without the
  1641. user namespace prefix, but their names are seen by Linux cifs clients
  1642. prefaced by the user namespace prefix. The system namespace
  1643. (used by some filesystems to store ACLs) is not supported at
  1644. this time.
  1645. If unsure, say N.
  1646. config CIFS_POSIX
  1647. bool "CIFS POSIX Extensions"
  1648. depends on CIFS_XATTR
  1649. help
  1650. Enabling this option will cause the cifs client to attempt to
  1651. negotiate a newer dialect with servers, such as Samba 3.0.5
  1652. or later, that optionally can handle more POSIX like (rather
  1653. than Windows like) file behavior. It also enables
  1654. support for POSIX ACLs (getfacl and setfacl) to servers
  1655. (such as Samba 3.10 and later) which can negotiate
  1656. CIFS POSIX ACL support. If unsure, say N.
  1657. config CIFS_DEBUG2
  1658. bool "Enable additional CIFS debugging routines"
  1659. depends on CIFS
  1660. help
  1661. Enabling this option adds a few more debugging routines
  1662. to the cifs code which slightly increases the size of
  1663. the cifs module and can cause additional logging of debug
  1664. messages in some error paths, slowing performance. This
  1665. option can be turned off unless you are debugging
  1666. cifs problems. If unsure, say N.
  1667. config CIFS_EXPERIMENTAL
  1668. bool "CIFS Experimental Features (EXPERIMENTAL)"
  1669. depends on CIFS && EXPERIMENTAL
  1670. help
  1671. Enables cifs features under testing. These features are
  1672. experimental and currently include DFS support and directory
  1673. change notification ie fcntl(F_DNOTIFY), as well as the upcall
  1674. mechanism which will be used for Kerberos session negotiation
  1675. and uid remapping. Some of these features also may depend on
  1676. setting a value of 1 to the pseudo-file /proc/fs/cifs/Experimental
  1677. (which is disabled by default). See the file fs/cifs/README
  1678. for more details. If unsure, say N.
  1679. config CIFS_UPCALL
  1680. bool "Kerberos/SPNEGO advanced session setup (EXPERIMENTAL)"
  1681. depends on CIFS_EXPERIMENTAL
  1682. depends on KEYS
  1683. help
  1684. Enables an upcall mechanism for CIFS which accesses
  1685. userspace helper utilities to provide SPNEGO packaged (RFC 4178)
  1686. Kerberos tickets which are needed to mount to certain secure servers
  1687. (for which more secure Kerberos authentication is required). If
  1688. unsure, say N.
  1689. config CIFS_DFS_UPCALL
  1690. bool "DFS feature support (EXPERIMENTAL)"
  1691. depends on CIFS_EXPERIMENTAL
  1692. depends on KEYS
  1693. help
  1694. Enables an upcall mechanism for CIFS which contacts userspace
  1695. helper utilities to provide server name resolution (host names to
  1696. IP addresses) which is needed for implicit mounts of DFS junction
  1697. points. If unsure, say N.
  1698. config NCP_FS
  1699. tristate "NCP file system support (to mount NetWare volumes)"
  1700. depends on IPX!=n || INET
  1701. help
  1702. NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
  1703. used by Novell NetWare clients to talk to file servers. It is to
  1704. IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
  1705. to mount NetWare file server volumes and to access them just like
  1706. any other Unix directory. For details, please read the file
  1707. <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
  1708. the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
  1709. You do not have to say Y here if you want your Linux box to act as a
  1710. file *server* for Novell NetWare clients.
  1711. General information about how to connect Linux, Windows machines and
  1712. Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
  1713. To compile this as a module, choose M here: the module will be called
  1714. ncpfs. Say N unless you are connected to a Novell network.
  1715. source "fs/ncpfs/Kconfig"
  1716. config CODA_FS
  1717. tristate "Coda file system support (advanced network fs)"
  1718. depends on INET
  1719. help
  1720. Coda is an advanced network file system, similar to NFS in that it
  1721. enables you to mount file systems of a remote server and access them
  1722. with regular Unix commands as if they were sitting on your hard
  1723. disk. Coda has several advantages over NFS: support for
  1724. disconnected operation (e.g. for laptops), read/write server
  1725. replication, security model for authentication and encryption,
  1726. persistent client caches and write back caching.
  1727. If you say Y here, your Linux box will be able to act as a Coda
  1728. *client*. You will need user level code as well, both for the
  1729. client and server. Servers are currently user level, i.e. they need
  1730. no kernel support. Please read
  1731. <file:Documentation/filesystems/coda.txt> and check out the Coda
  1732. home page <http://www.coda.cs.cmu.edu/>.
  1733. To compile the coda client support as a module, choose M here: the
  1734. module will be called coda.
  1735. config CODA_FS_OLD_API
  1736. bool "Use 96-bit Coda file identifiers"
  1737. depends on CODA_FS
  1738. help
  1739. A new kernel-userspace API had to be introduced for Coda v6.0
  1740. to support larger 128-bit file identifiers as needed by the
  1741. new realms implementation.
  1742. However this new API is not backward compatible with older
  1743. clients. If you really need to run the old Coda userspace
  1744. cache manager then say Y.
  1745. For most cases you probably want to say N.
  1746. config AFS_FS
  1747. tristate "Andrew File System support (AFS) (EXPERIMENTAL)"
  1748. depends on INET && EXPERIMENTAL
  1749. select AF_RXRPC
  1750. help
  1751. If you say Y here, you will get an experimental Andrew File System
  1752. driver. It currently only supports unsecured read-only AFS access.
  1753. See <file:Documentation/filesystems/afs.txt> for more information.
  1754. If unsure, say N.
  1755. config AFS_DEBUG
  1756. bool "AFS dynamic debugging"
  1757. depends on AFS_FS
  1758. help
  1759. Say Y here to make runtime controllable debugging messages appear.
  1760. See <file:Documentation/filesystems/afs.txt> for more information.
  1761. If unsure, say N.
  1762. config 9P_FS
  1763. tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
  1764. depends on INET && NET_9P && EXPERIMENTAL
  1765. help
  1766. If you say Y here, you will get experimental support for
  1767. Plan 9 resource sharing via the 9P2000 protocol.
  1768. See <http://v9fs.sf.net> for more information.
  1769. If unsure, say N.
  1770. endif # NETWORK_FILESYSTEMS
  1771. if BLOCK
  1772. menu "Partition Types"
  1773. source "fs/partitions/Kconfig"
  1774. endmenu
  1775. endif
  1776. source "fs/nls/Kconfig"
  1777. source "fs/dlm/Kconfig"
  1778. endmenu