Kconfig 76 KB

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