Kconfig 75 KB

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