Kconfig 74 KB

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