Kconfig 63 KB

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