Kconfig 76 KB

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