Kconfig 53 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091929394959697989910010110210310410510610710810911011111211311411511611711811912012112212312412512612712812913013113213313413513613713813914014114214314414514614714814915015115215315415515615715815916016116216316416516616716816917017117217317417517617717817918018118218318418518618718818919019119219319419519619719819920020120220320420520620720820921021121221321421521621721821922022122222322422522622722822923023123223323423523623723823924024124224324424524624724824925025125225325425525625725825926026126226326426526626726826927027127227327427527627727827928028128228328428528628728828929029129229329429529629729829930030130230330430530630730830931031131231331431531631731831932032132232332432532632732832933033133233333433533633733833934034134234334434534634734834935035135235335435535635735835936036136236336436536636736836937037137237337437537637737837938038138238338438538638738838939039139239339439539639739839940040140240340440540640740840941041141241341441541641741841942042142242342442542642742842943043143243343443543643743843944044144244344444544644744844945045145245345445545645745845946046146246346446546646746846947047147247347447547647747847948048148248348448548648748848949049149249349449549649749849950050150250350450550650750850951051151251351451551651751851952052152252352452552652752852953053153253353453553653753853954054154254354454554654754854955055155255355455555655755855956056156256356456556656756856957057157257357457557657757857958058158258358458558658758858959059159259359459559659759859960060160260360460560660760860961061161261361461561661761861962062162262362462562662762862963063163263363463563663763863964064164264364464564664764864965065165265365465565665765865966066166266366466566666766866967067167267367467567667767867968068168268368468568668768868969069169269369469569669769869970070170270370470570670770870971071171271371471571671771871972072172272372472572672772872973073173273373473573673773873974074174274374474574674774874975075175275375475575675775875976076176276376476576676776876977077177277377477577677777877978078178278378478578678778878979079179279379479579679779879980080180280380480580680780880981081181281381481581681781881982082182282382482582682782882983083183283383483583683783883984084184284384484584684784884985085185285385485585685785885986086186286386486586686786886987087187287387487587687787887988088188288388488588688788888989089189289389489589689789889990090190290390490590690790890991091191291391491591691791891992092192292392492592692792892993093193293393493593693793893994094194294394494594694794894995095195295395495595695795895996096196296396496596696796896997097197297397497597697797897998098198298398498598698798898999099199299399499599699799899910001001100210031004100510061007100810091010101110121013101410151016101710181019102010211022102310241025102610271028102910301031103210331034103510361037103810391040104110421043104410451046104710481049105010511052105310541055105610571058105910601061106210631064106510661067106810691070107110721073107410751076107710781079108010811082108310841085108610871088108910901091109210931094109510961097109810991100110111021103110411051106110711081109111011111112111311141115111611171118111911201121112211231124112511261127112811291130113111321133113411351136113711381139114011411142114311441145114611471148114911501151115211531154115511561157115811591160116111621163116411651166116711681169117011711172117311741175117611771178117911801181118211831184118511861187118811891190119111921193119411951196119711981199120012011202120312041205120612071208120912101211121212131214121512161217121812191220122112221223122412251226122712281229123012311232123312341235123612371238123912401241124212431244124512461247124812491250125112521253125412551256125712581259126012611262126312641265126612671268126912701271127212731274127512761277127812791280128112821283128412851286128712881289129012911292129312941295129612971298129913001301130213031304130513061307130813091310131113121313131413151316131713181319132013211322132313241325132613271328132913301331133213331334133513361337133813391340134113421343134413451346134713481349135013511352135313541355135613571358135913601361136213631364136513661367136813691370137113721373137413751376137713781379138013811382138313841385138613871388138913901391139213931394139513961397139813991400140114021403140414051406140714081409141014111412141314141415141614171418141914201421142214231424142514261427142814291430143114321433143414351436143714381439144014411442144314441445144614471448144914501451145214531454145514561457145814591460146114621463146414651466146714681469147014711472147314741475147614771478147914801481148214831484148514861487148814891490149114921493149414951496149714981499150015011502150315041505150615071508150915101511151215131514151515161517151815191520152115221523
  1. #
  2. # File system configuration
  3. #
  4. menu "File systems"
  5. if BLOCK
  6. source "fs/ext2/Kconfig"
  7. source "fs/ext3/Kconfig"
  8. source "fs/ext4/Kconfig"
  9. config FS_XIP
  10. # execute in place
  11. bool
  12. depends on EXT2_FS_XIP
  13. default y
  14. source "fs/jbd/Kconfig"
  15. source "fs/jbd2/Kconfig"
  16. config FS_MBCACHE
  17. # Meta block cache for Extended Attributes (ext2/ext3/ext4)
  18. tristate
  19. default y if EXT2_FS=y && EXT2_FS_XATTR
  20. default y if EXT3_FS=y && EXT3_FS_XATTR
  21. default y if EXT4_FS=y && EXT4_FS_XATTR
  22. default m if EXT2_FS_XATTR || EXT3_FS_XATTR || EXT4_FS_XATTR
  23. config REISERFS_FS
  24. tristate "Reiserfs support"
  25. help
  26. Stores not just filenames but the files themselves in a balanced
  27. tree. Uses journalling.
  28. Balanced trees are more efficient than traditional file system
  29. architectural foundations.
  30. In general, ReiserFS is as fast as ext2, but is very efficient with
  31. large directories and small files. Additional patches are needed
  32. for NFS and quotas, please see <http://www.namesys.com/> for links.
  33. It is more easily extended to have features currently found in
  34. database and keyword search systems than block allocation based file
  35. systems are. The next version will be so extended, and will support
  36. plugins consistent with our motto ``It takes more than a license to
  37. make source code open.''
  38. Read <http://www.namesys.com/> to learn more about reiserfs.
  39. Sponsored by Threshold Networks, Emusic.com, and Bigstorage.com.
  40. If you like it, you can pay us to add new features to it that you
  41. need, buy a support contract, or pay us to port it to another OS.
  42. config REISERFS_CHECK
  43. bool "Enable reiserfs debug mode"
  44. depends on REISERFS_FS
  45. help
  46. If you set this to Y, then ReiserFS will perform every check it can
  47. possibly imagine of its internal consistency throughout its
  48. operation. It will also go substantially slower. More than once we
  49. have forgotten that this was on, and then gone despondent over the
  50. latest benchmarks.:-) Use of this option allows our team to go all
  51. out in checking for consistency when debugging without fear of its
  52. effect on end users. If you are on the verge of sending in a bug
  53. report, say Y and you might get a useful error message. Almost
  54. everyone should say N.
  55. config REISERFS_PROC_INFO
  56. bool "Stats in /proc/fs/reiserfs"
  57. depends on REISERFS_FS && PROC_FS
  58. help
  59. Create under /proc/fs/reiserfs a hierarchy of files, displaying
  60. various ReiserFS statistics and internal data at the expense of
  61. making your kernel or module slightly larger (+8 KB). This also
  62. increases the amount of kernel memory required for each mount.
  63. Almost everyone but ReiserFS developers and people fine-tuning
  64. reiserfs or tracing problems should say N.
  65. config REISERFS_FS_XATTR
  66. bool "ReiserFS extended attributes"
  67. depends on REISERFS_FS
  68. help
  69. Extended attributes are name:value pairs associated with inodes by
  70. the kernel or by users (see the attr(5) manual page, or visit
  71. <http://acl.bestbits.at/> for details).
  72. If unsure, say N.
  73. config REISERFS_FS_POSIX_ACL
  74. bool "ReiserFS POSIX Access Control Lists"
  75. depends on REISERFS_FS_XATTR
  76. select FS_POSIX_ACL
  77. help
  78. Posix Access Control Lists (ACLs) support permissions for users and
  79. groups beyond the owner/group/world scheme.
  80. To learn more about Access Control Lists, visit the Posix ACLs for
  81. Linux website <http://acl.bestbits.at/>.
  82. If you don't know what Access Control Lists are, say N
  83. config REISERFS_FS_SECURITY
  84. bool "ReiserFS Security Labels"
  85. depends on REISERFS_FS_XATTR
  86. help
  87. Security labels support alternative access control models
  88. implemented by security modules like SELinux. This option
  89. enables an extended attribute handler for file security
  90. labels in the ReiserFS filesystem.
  91. If you are not using a security module that requires using
  92. extended attributes for file security labels, say N.
  93. config JFS_FS
  94. tristate "JFS filesystem support"
  95. select NLS
  96. help
  97. This is a port of IBM's Journaled Filesystem . More information is
  98. available in the file <file:Documentation/filesystems/jfs.txt>.
  99. If you do not intend to use the JFS filesystem, say N.
  100. config JFS_POSIX_ACL
  101. bool "JFS POSIX Access Control Lists"
  102. depends on JFS_FS
  103. select FS_POSIX_ACL
  104. help
  105. Posix Access Control Lists (ACLs) support permissions for users and
  106. groups beyond the owner/group/world scheme.
  107. To learn more about Access Control Lists, visit the Posix ACLs for
  108. Linux website <http://acl.bestbits.at/>.
  109. If you don't know what Access Control Lists are, say N
  110. config JFS_SECURITY
  111. bool "JFS Security Labels"
  112. depends on JFS_FS
  113. help
  114. Security labels support alternative access control models
  115. implemented by security modules like SELinux. This option
  116. enables an extended attribute handler for file security
  117. labels in the jfs filesystem.
  118. If you are not using a security module that requires using
  119. extended attributes for file security labels, say N.
  120. config JFS_DEBUG
  121. bool "JFS debugging"
  122. depends on JFS_FS
  123. help
  124. If you are experiencing any problems with the JFS filesystem, say
  125. Y here. This will result in additional debugging messages to be
  126. written to the system log. Under normal circumstances, this
  127. results in very little overhead.
  128. config JFS_STATISTICS
  129. bool "JFS statistics"
  130. depends on JFS_FS
  131. help
  132. Enabling this option will cause statistics from the JFS file system
  133. to be made available to the user in the /proc/fs/jfs/ directory.
  134. config FS_POSIX_ACL
  135. # Posix ACL utility routines (for now, only ext2/ext3/jfs/reiserfs/nfs4)
  136. #
  137. # NOTE: you can implement Posix ACLs without these helpers (XFS does).
  138. # Never use this symbol for ifdefs.
  139. #
  140. bool
  141. default n
  142. config FILE_LOCKING
  143. bool "Enable POSIX file locking API" if EMBEDDED
  144. default y
  145. help
  146. This option enables standard file locking support, required
  147. for filesystems like NFS and for the flock() system
  148. call. Disabling this option saves about 11k.
  149. source "fs/xfs/Kconfig"
  150. source "fs/gfs2/Kconfig"
  151. config OCFS2_FS
  152. tristate "OCFS2 file system support"
  153. depends on NET && SYSFS
  154. select CONFIGFS_FS
  155. select JBD2
  156. select CRC32
  157. help
  158. OCFS2 is a general purpose extent based shared disk cluster file
  159. system with many similarities to ext3. It supports 64 bit inode
  160. numbers, and has automatically extending metadata groups which may
  161. also make it attractive for non-clustered use.
  162. You'll want to install the ocfs2-tools package in order to at least
  163. get "mount.ocfs2".
  164. Project web page: http://oss.oracle.com/projects/ocfs2
  165. Tools web page: http://oss.oracle.com/projects/ocfs2-tools
  166. OCFS2 mailing lists: http://oss.oracle.com/projects/ocfs2/mailman/
  167. For more information on OCFS2, see the file
  168. <file:Documentation/filesystems/ocfs2.txt>.
  169. config OCFS2_FS_O2CB
  170. tristate "O2CB Kernelspace Clustering"
  171. depends on OCFS2_FS
  172. default y
  173. help
  174. OCFS2 includes a simple kernelspace clustering package, the OCFS2
  175. Cluster Base. It only requires a very small userspace component
  176. to configure it. This comes with the standard ocfs2-tools package.
  177. O2CB is limited to maintaining a cluster for OCFS2 file systems.
  178. It cannot manage any other cluster applications.
  179. It is always safe to say Y here, as the clustering method is
  180. run-time selectable.
  181. config OCFS2_FS_USERSPACE_CLUSTER
  182. tristate "OCFS2 Userspace Clustering"
  183. depends on OCFS2_FS && DLM
  184. default y
  185. help
  186. This option will allow OCFS2 to use userspace clustering services
  187. in conjunction with the DLM in fs/dlm. If you are using a
  188. userspace cluster manager, say Y here.
  189. It is safe to say Y, as the clustering method is run-time
  190. selectable.
  191. config OCFS2_FS_STATS
  192. bool "OCFS2 statistics"
  193. depends on OCFS2_FS
  194. default y
  195. help
  196. This option allows some fs statistics to be captured. Enabling
  197. this option may increase the memory consumption.
  198. config OCFS2_DEBUG_MASKLOG
  199. bool "OCFS2 logging support"
  200. depends on OCFS2_FS
  201. default y
  202. help
  203. The ocfs2 filesystem has an extensive logging system. The system
  204. allows selection of events to log via files in /sys/o2cb/logmask/.
  205. This option will enlarge your kernel, but it allows debugging of
  206. ocfs2 filesystem issues.
  207. config OCFS2_DEBUG_FS
  208. bool "OCFS2 expensive checks"
  209. depends on OCFS2_FS
  210. default n
  211. help
  212. This option will enable expensive consistency checks. Enable
  213. this option for debugging only as it is likely to decrease
  214. performance of the filesystem.
  215. config OCFS2_COMPAT_JBD
  216. bool "Use JBD for compatibility"
  217. depends on OCFS2_FS
  218. default n
  219. select JBD
  220. help
  221. The ocfs2 filesystem now uses JBD2 for its journalling. JBD2
  222. is backwards compatible with JBD. It is safe to say N here.
  223. However, if you really want to use the original JBD, say Y here.
  224. endif # BLOCK
  225. source "fs/notify/Kconfig"
  226. config QUOTA
  227. bool "Quota support"
  228. help
  229. If you say Y here, you will be able to set per user limits for disk
  230. usage (also called disk quotas). Currently, it works for the
  231. ext2, ext3, and reiserfs file system. ext3 also supports journalled
  232. quotas for which you don't need to run quotacheck(8) after an unclean
  233. shutdown.
  234. For further details, read the Quota mini-HOWTO, available from
  235. <http://www.tldp.org/docs.html#howto>, or the documentation provided
  236. with the quota tools. Probably the quota support is only useful for
  237. multi user systems. If unsure, say N.
  238. config QUOTA_NETLINK_INTERFACE
  239. bool "Report quota messages through netlink interface"
  240. depends on QUOTA && NET
  241. help
  242. If you say Y here, quota warnings (about exceeding softlimit, reaching
  243. hardlimit, etc.) will be reported through netlink interface. If unsure,
  244. say Y.
  245. config PRINT_QUOTA_WARNING
  246. bool "Print quota warnings to console (OBSOLETE)"
  247. depends on QUOTA
  248. default y
  249. help
  250. If you say Y here, quota warnings (about exceeding softlimit, reaching
  251. hardlimit, etc.) will be printed to the process' controlling terminal.
  252. Note that this behavior is currently deprecated and may go away in
  253. future. Please use notification via netlink socket instead.
  254. config QFMT_V1
  255. tristate "Old quota format support"
  256. depends on QUOTA
  257. help
  258. This quota format was (is) used by kernels earlier than 2.4.22. If
  259. you have quota working and you don't want to convert to new quota
  260. format say Y here.
  261. config QFMT_V2
  262. tristate "Quota format v2 support"
  263. depends on QUOTA
  264. help
  265. This quota format allows using quotas with 32-bit UIDs/GIDs. If you
  266. need this functionality say Y here.
  267. config QUOTACTL
  268. bool
  269. depends on XFS_QUOTA || QUOTA
  270. default y
  271. config AUTOFS_FS
  272. tristate "Kernel automounter support"
  273. help
  274. The automounter is a tool to automatically mount remote file systems
  275. on demand. This implementation is partially kernel-based to reduce
  276. overhead in the already-mounted case; this is unlike the BSD
  277. automounter (amd), which is a pure user space daemon.
  278. To use the automounter you need the user-space tools from the autofs
  279. package; you can find the location in <file:Documentation/Changes>.
  280. You also want to answer Y to "NFS file system support", below.
  281. If you want to use the newer version of the automounter with more
  282. features, say N here and say Y to "Kernel automounter v4 support",
  283. below.
  284. To compile this support as a module, choose M here: the module will be
  285. called autofs.
  286. If you are not a part of a fairly large, distributed network, you
  287. probably do not need an automounter, and can say N here.
  288. config AUTOFS4_FS
  289. tristate "Kernel automounter version 4 support (also supports v3)"
  290. help
  291. The automounter is a tool to automatically mount remote file systems
  292. on demand. This implementation is partially kernel-based to reduce
  293. overhead in the already-mounted case; this is unlike the BSD
  294. automounter (amd), which is a pure user space daemon.
  295. To use the automounter you need the user-space tools from
  296. <ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4/>; you also
  297. want to answer Y to "NFS file system support", below.
  298. To compile this support as a module, choose M here: the module will be
  299. called autofs4. You will need to add "alias autofs autofs4" to your
  300. modules configuration file.
  301. If you are not a part of a fairly large, distributed network or
  302. don't have a laptop which needs to dynamically reconfigure to the
  303. local network, you probably do not need an automounter, and can say
  304. N here.
  305. config FUSE_FS
  306. tristate "FUSE (Filesystem in Userspace) support"
  307. help
  308. With FUSE it is possible to implement a fully functional filesystem
  309. in a userspace program.
  310. There's also companion library: libfuse. This library along with
  311. utilities is available from the FUSE homepage:
  312. <http://fuse.sourceforge.net/>
  313. See <file:Documentation/filesystems/fuse.txt> for more information.
  314. See <file:Documentation/Changes> for needed library/utility version.
  315. If you want to develop a userspace FS, or if you want to use
  316. a filesystem based on FUSE, answer Y or M.
  317. config GENERIC_ACL
  318. bool
  319. select FS_POSIX_ACL
  320. if BLOCK
  321. menu "CD-ROM/DVD Filesystems"
  322. config ISO9660_FS
  323. tristate "ISO 9660 CDROM file system support"
  324. help
  325. This is the standard file system used on CD-ROMs. It was previously
  326. known as "High Sierra File System" and is called "hsfs" on other
  327. Unix systems. The so-called Rock-Ridge extensions which allow for
  328. long Unix filenames and symbolic links are also supported by this
  329. driver. If you have a CD-ROM drive and want to do more with it than
  330. just listen to audio CDs and watch its LEDs, say Y (and read
  331. <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO,
  332. available from <http://www.tldp.org/docs.html#howto>), thereby
  333. enlarging your kernel by about 27 KB; otherwise say N.
  334. To compile this file system support as a module, choose M here: the
  335. module will be called isofs.
  336. config JOLIET
  337. bool "Microsoft Joliet CDROM extensions"
  338. depends on ISO9660_FS
  339. select NLS
  340. help
  341. Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system
  342. which allows for long filenames in unicode format (unicode is the
  343. new 16 bit character code, successor to ASCII, which encodes the
  344. characters of almost all languages of the world; see
  345. <http://www.unicode.org/> for more information). Say Y here if you
  346. want to be able to read Joliet CD-ROMs under Linux.
  347. config ZISOFS
  348. bool "Transparent decompression extension"
  349. depends on ISO9660_FS
  350. select ZLIB_INFLATE
  351. help
  352. This is a Linux-specific extension to RockRidge which lets you store
  353. data in compressed form on a CD-ROM and have it transparently
  354. decompressed when the CD-ROM is accessed. See
  355. <http://www.kernel.org/pub/linux/utils/fs/zisofs/> for the tools
  356. necessary to create such a filesystem. Say Y here if you want to be
  357. able to read such compressed CD-ROMs.
  358. config UDF_FS
  359. tristate "UDF file system support"
  360. select CRC_ITU_T
  361. help
  362. This is the new file system used on some CD-ROMs and DVDs. Say Y if
  363. you intend to mount DVD discs or CDRW's written in packet mode, or
  364. if written to by other UDF utilities, such as DirectCD.
  365. Please read <file:Documentation/filesystems/udf.txt>.
  366. To compile this file system support as a module, choose M here: the
  367. module will be called udf.
  368. If unsure, say N.
  369. config UDF_NLS
  370. bool
  371. default y
  372. depends on (UDF_FS=m && NLS) || (UDF_FS=y && NLS=y)
  373. endmenu
  374. endif # BLOCK
  375. if BLOCK
  376. menu "DOS/FAT/NT Filesystems"
  377. config FAT_FS
  378. tristate
  379. select NLS
  380. help
  381. If you want to use one of the FAT-based file systems (the MS-DOS and
  382. VFAT (Windows 95) file systems), then you must say Y or M here
  383. to include FAT support. You will then be able to mount partitions or
  384. diskettes with FAT-based file systems and transparently access the
  385. files on them, i.e. MSDOS files will look and behave just like all
  386. other Unix files.
  387. This FAT support is not a file system in itself, it only provides
  388. the foundation for the other file systems. You will have to say Y or
  389. M to at least one of "MSDOS fs support" or "VFAT fs support" in
  390. order to make use of it.
  391. Another way to read and write MSDOS floppies and hard drive
  392. partitions from within Linux (but not transparently) is with the
  393. mtools ("man mtools") program suite. You don't need to say Y here in
  394. order to do that.
  395. If you need to move large files on floppies between a DOS and a
  396. Linux box, say Y here, mount the floppy under Linux with an MSDOS
  397. file system and use GNU tar's M option. GNU tar is a program
  398. available for Unix and DOS ("man tar" or "info tar").
  399. The FAT support will enlarge your kernel by about 37 KB. If unsure,
  400. say Y.
  401. To compile this as a module, choose M here: the module will be called
  402. fat. Note that if you compile the FAT support as a module, you
  403. cannot compile any of the FAT-based file systems into the kernel
  404. -- they will have to be modules as well.
  405. config MSDOS_FS
  406. tristate "MSDOS fs support"
  407. select FAT_FS
  408. help
  409. This allows you to mount MSDOS partitions of your hard drive (unless
  410. they are compressed; to access compressed MSDOS partitions under
  411. Linux, you can either use the DOS emulator DOSEMU, described in the
  412. DOSEMU-HOWTO, available from
  413. <http://www.tldp.org/docs.html#howto>, or try dmsdosfs in
  414. <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you
  415. intend to use dosemu with a non-compressed MSDOS partition, say Y
  416. here) and MSDOS floppies. This means that file access becomes
  417. transparent, i.e. the MSDOS files look and behave just like all
  418. other Unix files.
  419. If you have Windows 95 or Windows NT installed on your MSDOS
  420. partitions, you should use the VFAT file system (say Y to "VFAT fs
  421. support" below), or you will not be able to see the long filenames
  422. generated by Windows 95 / Windows NT.
  423. This option will enlarge your kernel by about 7 KB. If unsure,
  424. answer Y. This will only work if you said Y to "DOS FAT fs support"
  425. as well. To compile this as a module, choose M here: the module will
  426. be called msdos.
  427. config VFAT_FS
  428. tristate "VFAT (Windows-95) fs support"
  429. select FAT_FS
  430. help
  431. This option provides support for normal Windows file systems with
  432. long filenames. That includes non-compressed FAT-based file systems
  433. used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
  434. programs from the mtools package.
  435. The VFAT support enlarges your kernel by about 10 KB and it only
  436. works if you said Y to the "DOS FAT fs support" above. Please read
  437. the file <file:Documentation/filesystems/vfat.txt> for details. If
  438. unsure, say Y.
  439. To compile this as a module, choose M here: the module will be called
  440. vfat.
  441. config FAT_DEFAULT_CODEPAGE
  442. int "Default codepage for FAT"
  443. depends on MSDOS_FS || VFAT_FS
  444. default 437
  445. help
  446. This option should be set to the codepage of your FAT filesystems.
  447. It can be overridden with the "codepage" mount option.
  448. See <file:Documentation/filesystems/vfat.txt> for more information.
  449. config FAT_DEFAULT_IOCHARSET
  450. string "Default iocharset for FAT"
  451. depends on VFAT_FS
  452. default "iso8859-1"
  453. help
  454. Set this to the default input/output character set you'd
  455. like FAT to use. It should probably match the character set
  456. that most of your FAT filesystems use, and can be overridden
  457. with the "iocharset" mount option for FAT filesystems.
  458. Note that "utf8" is not recommended for FAT filesystems.
  459. If unsure, you shouldn't set "utf8" here.
  460. See <file:Documentation/filesystems/vfat.txt> for more information.
  461. config NTFS_FS
  462. tristate "NTFS file system support"
  463. select NLS
  464. help
  465. NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003.
  466. Saying Y or M here enables read support. There is partial, but
  467. safe, write support available. For write support you must also
  468. say Y to "NTFS write support" below.
  469. There are also a number of user-space tools available, called
  470. ntfsprogs. These include ntfsundelete and ntfsresize, that work
  471. without NTFS support enabled in the kernel.
  472. This is a rewrite from scratch of Linux NTFS support and replaced
  473. the old NTFS code starting with Linux 2.5.11. A backport to
  474. the Linux 2.4 kernel series is separately available as a patch
  475. from the project web site.
  476. For more information see <file:Documentation/filesystems/ntfs.txt>
  477. and <http://www.linux-ntfs.org/>.
  478. To compile this file system support as a module, choose M here: the
  479. module will be called ntfs.
  480. If you are not using Windows NT, 2000, XP or 2003 in addition to
  481. Linux on your computer it is safe to say N.
  482. config NTFS_DEBUG
  483. bool "NTFS debugging support"
  484. depends on NTFS_FS
  485. help
  486. If you are experiencing any problems with the NTFS file system, say
  487. Y here. This will result in additional consistency checks to be
  488. performed by the driver as well as additional debugging messages to
  489. be written to the system log. Note that debugging messages are
  490. disabled by default. To enable them, supply the option debug_msgs=1
  491. at the kernel command line when booting the kernel or as an option
  492. to insmod when loading the ntfs module. Once the driver is active,
  493. you can enable debugging messages by doing (as root):
  494. echo 1 > /proc/sys/fs/ntfs-debug
  495. Replacing the "1" with "0" would disable debug messages.
  496. If you leave debugging messages disabled, this results in little
  497. overhead, but enabling debug messages results in very significant
  498. slowdown of the system.
  499. When reporting bugs, please try to have available a full dump of
  500. debugging messages while the misbehaviour was occurring.
  501. config NTFS_RW
  502. bool "NTFS write support"
  503. depends on NTFS_FS
  504. help
  505. This enables the partial, but safe, write support in the NTFS driver.
  506. The only supported operation is overwriting existing files, without
  507. changing the file length. No file or directory creation, deletion or
  508. renaming is possible. Note only non-resident files can be written to
  509. so you may find that some very small files (<500 bytes or so) cannot
  510. be written to.
  511. While we cannot guarantee that it will not damage any data, we have
  512. so far not received a single report where the driver would have
  513. damaged someones data so we assume it is perfectly safe to use.
  514. Note: While write support is safe in this version (a rewrite from
  515. scratch of the NTFS support), it should be noted that the old NTFS
  516. write support, included in Linux 2.5.10 and before (since 1997),
  517. is not safe.
  518. This is currently useful with TopologiLinux. TopologiLinux is run
  519. on top of any DOS/Microsoft Windows system without partitioning your
  520. hard disk. Unlike other Linux distributions TopologiLinux does not
  521. need its own partition. For more information see
  522. <http://topologi-linux.sourceforge.net/>
  523. It is perfectly safe to say N here.
  524. endmenu
  525. endif # BLOCK
  526. menu "Pseudo filesystems"
  527. source "fs/proc/Kconfig"
  528. config SYSFS
  529. bool "sysfs file system support" if EMBEDDED
  530. default y
  531. help
  532. The sysfs filesystem is a virtual filesystem that the kernel uses to
  533. export internal kernel objects, their attributes, and their
  534. relationships to one another.
  535. Users can use sysfs to ascertain useful information about the running
  536. kernel, such as the devices the kernel has discovered on each bus and
  537. which driver each is bound to. sysfs can also be used to tune devices
  538. and other kernel subsystems.
  539. Some system agents rely on the information in sysfs to operate.
  540. /sbin/hotplug uses device and object attributes in sysfs to assist in
  541. delegating policy decisions, like persistently naming devices.
  542. sysfs is currently used by the block subsystem to mount the root
  543. partition. If sysfs is disabled you must specify the boot device on
  544. the kernel boot command line via its major and minor numbers. For
  545. example, "root=03:01" for /dev/hda1.
  546. Designers of embedded systems may wish to say N here to conserve space.
  547. config TMPFS
  548. bool "Virtual memory file system support (former shm fs)"
  549. help
  550. Tmpfs is a file system which keeps all files in virtual memory.
  551. Everything in tmpfs is temporary in the sense that no files will be
  552. created on your hard drive. The files live in memory and swap
  553. space. If you unmount a tmpfs instance, everything stored therein is
  554. lost.
  555. See <file:Documentation/filesystems/tmpfs.txt> for details.
  556. config TMPFS_POSIX_ACL
  557. bool "Tmpfs POSIX Access Control Lists"
  558. depends on TMPFS
  559. select GENERIC_ACL
  560. help
  561. POSIX Access Control Lists (ACLs) support permissions for users and
  562. groups beyond the owner/group/world scheme.
  563. To learn more about Access Control Lists, visit the POSIX ACLs for
  564. Linux website <http://acl.bestbits.at/>.
  565. If you don't know what Access Control Lists are, say N.
  566. config HUGETLBFS
  567. bool "HugeTLB file system support"
  568. depends on X86 || IA64 || PPC64 || SPARC64 || (SUPERH && MMU) || \
  569. (S390 && 64BIT) || BROKEN
  570. help
  571. hugetlbfs is a filesystem backing for HugeTLB pages, based on
  572. ramfs. For architectures that support it, say Y here and read
  573. <file:Documentation/vm/hugetlbpage.txt> for details.
  574. If unsure, say N.
  575. config HUGETLB_PAGE
  576. def_bool HUGETLBFS
  577. config CONFIGFS_FS
  578. tristate "Userspace-driven configuration filesystem"
  579. depends on SYSFS
  580. help
  581. configfs is a ram-based filesystem that provides the converse
  582. of sysfs's functionality. Where sysfs is a filesystem-based
  583. view of kernel objects, configfs is a filesystem-based manager
  584. of kernel objects, or config_items.
  585. Both sysfs and configfs can and should exist together on the
  586. same system. One is not a replacement for the other.
  587. endmenu
  588. menu "Miscellaneous filesystems"
  589. config ADFS_FS
  590. tristate "ADFS file system support (EXPERIMENTAL)"
  591. depends on BLOCK && EXPERIMENTAL
  592. help
  593. The Acorn Disc Filing System is the standard file system of the
  594. RiscOS operating system which runs on Acorn's ARM-based Risc PC
  595. systems and the Acorn Archimedes range of machines. If you say Y
  596. here, Linux will be able to read from ADFS partitions on hard drives
  597. and from ADFS-formatted floppy discs. If you also want to be able to
  598. write to those devices, say Y to "ADFS write support" below.
  599. The ADFS partition should be the first partition (i.e.,
  600. /dev/[hs]d?1) on each of your drives. Please read the file
  601. <file:Documentation/filesystems/adfs.txt> for further details.
  602. To compile this code as a module, choose M here: the module will be
  603. called adfs.
  604. If unsure, say N.
  605. config ADFS_FS_RW
  606. bool "ADFS write support (DANGEROUS)"
  607. depends on ADFS_FS
  608. help
  609. If you say Y here, you will be able to write to ADFS partitions on
  610. hard drives and ADFS-formatted floppy disks. This is experimental
  611. codes, so if you're unsure, say N.
  612. config AFFS_FS
  613. tristate "Amiga FFS file system support (EXPERIMENTAL)"
  614. depends on BLOCK && EXPERIMENTAL
  615. help
  616. The Fast File System (FFS) is the common file system used on hard
  617. disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
  618. if you want to be able to read and write files from and to an Amiga
  619. FFS partition on your hard drive. Amiga floppies however cannot be
  620. read with this driver due to an incompatibility of the floppy
  621. controller used in an Amiga and the standard floppy controller in
  622. PCs and workstations. Read <file:Documentation/filesystems/affs.txt>
  623. and <file:fs/affs/Changes>.
  624. With this driver you can also mount disk files used by Bernd
  625. Schmidt's Un*X Amiga Emulator
  626. (<http://www.freiburg.linux.de/~uae/>).
  627. If you want to do this, you will also need to say Y or M to "Loop
  628. device support", above.
  629. To compile this file system support as a module, choose M here: the
  630. module will be called affs. If unsure, say N.
  631. config ECRYPT_FS
  632. tristate "eCrypt filesystem layer support (EXPERIMENTAL)"
  633. depends on EXPERIMENTAL && KEYS && CRYPTO && NET
  634. help
  635. Encrypted filesystem that operates on the VFS layer. See
  636. <file:Documentation/filesystems/ecryptfs.txt> to learn more about
  637. eCryptfs. Userspace components are required and can be
  638. obtained from <http://ecryptfs.sf.net>.
  639. To compile this file system support as a module, choose M here: the
  640. module will be called ecryptfs.
  641. config HFS_FS
  642. tristate "Apple Macintosh file system support (EXPERIMENTAL)"
  643. depends on BLOCK && EXPERIMENTAL
  644. select NLS
  645. help
  646. If you say Y here, you will be able to mount Macintosh-formatted
  647. floppy disks and hard drive partitions with full read-write access.
  648. Please read <file:Documentation/filesystems/hfs.txt> to learn about
  649. the available mount options.
  650. To compile this file system support as a module, choose M here: the
  651. module will be called hfs.
  652. config HFSPLUS_FS
  653. tristate "Apple Extended HFS file system support"
  654. depends on BLOCK
  655. select NLS
  656. select NLS_UTF8
  657. help
  658. If you say Y here, you will be able to mount extended format
  659. Macintosh-formatted hard drive partitions with full read-write access.
  660. This file system is often called HFS+ and was introduced with
  661. MacOS 8. It includes all Mac specific filesystem data such as
  662. data forks and creator codes, but it also has several UNIX
  663. style features such as file ownership and permissions.
  664. config BEFS_FS
  665. tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)"
  666. depends on BLOCK && EXPERIMENTAL
  667. select NLS
  668. help
  669. The BeOS File System (BeFS) is the native file system of Be, Inc's
  670. BeOS. Notable features include support for arbitrary attributes
  671. on files and directories, and database-like indices on selected
  672. attributes. (Also note that this driver doesn't make those features
  673. available at this time). It is a 64 bit filesystem, so it supports
  674. extremely large volumes and files.
  675. If you use this filesystem, you should also say Y to at least one
  676. of the NLS (native language support) options below.
  677. If you don't know what this is about, say N.
  678. To compile this as a module, choose M here: the module will be
  679. called befs.
  680. config BEFS_DEBUG
  681. bool "Debug BeFS"
  682. depends on BEFS_FS
  683. help
  684. If you say Y here, you can use the 'debug' mount option to enable
  685. debugging output from the driver.
  686. config BFS_FS
  687. tristate "BFS file system support (EXPERIMENTAL)"
  688. depends on BLOCK && EXPERIMENTAL
  689. help
  690. Boot File System (BFS) is a file system used under SCO UnixWare to
  691. allow the bootloader access to the kernel image and other important
  692. files during the boot process. It is usually mounted under /stand
  693. and corresponds to the slice marked as "STAND" in the UnixWare
  694. partition. You should say Y if you want to read or write the files
  695. on your /stand slice from within Linux. You then also need to say Y
  696. to "UnixWare slices support", below. More information about the BFS
  697. file system is contained in the file
  698. <file:Documentation/filesystems/bfs.txt>.
  699. If you don't know what this is about, say N.
  700. To compile this as a module, choose M here: the module will be called
  701. bfs. Note that the file system of your root partition (the one
  702. containing the directory /) cannot be compiled as a module.
  703. config EFS_FS
  704. tristate "EFS file system support (read only) (EXPERIMENTAL)"
  705. depends on BLOCK && EXPERIMENTAL
  706. help
  707. EFS is an older file system used for non-ISO9660 CD-ROMs and hard
  708. disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
  709. uses the XFS file system for hard disk partitions however).
  710. This implementation only offers read-only access. If you don't know
  711. what all this is about, it's safe to say N. For more information
  712. about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
  713. To compile the EFS file system support as a module, choose M here: the
  714. module will be called efs.
  715. source "fs/jffs2/Kconfig"
  716. # UBIFS File system configuration
  717. source "fs/ubifs/Kconfig"
  718. config CRAMFS
  719. tristate "Compressed ROM file system support (cramfs)"
  720. depends on BLOCK
  721. select ZLIB_INFLATE
  722. help
  723. Saying Y here includes support for CramFs (Compressed ROM File
  724. System). CramFs is designed to be a simple, small, and compressed
  725. file system for ROM based embedded systems. CramFs is read-only,
  726. limited to 256MB file systems (with 16MB files), and doesn't support
  727. 16/32 bits uid/gid, hard links and timestamps.
  728. See <file:Documentation/filesystems/cramfs.txt> and
  729. <file:fs/cramfs/README> for further information.
  730. To compile this as a module, choose M here: the module will be called
  731. cramfs. Note that the root file system (the one containing the
  732. directory /) cannot be compiled as a module.
  733. If unsure, say N.
  734. config VXFS_FS
  735. tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
  736. depends on BLOCK
  737. help
  738. FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
  739. file system format. VERITAS VxFS(TM) is the standard file system
  740. of SCO UnixWare (and possibly others) and optionally available
  741. for Sunsoft Solaris, HP-UX and many other operating systems.
  742. Currently only readonly access is supported.
  743. NOTE: the file system type as used by mount(1), mount(2) and
  744. fstab(5) is 'vxfs' as it describes the file system format, not
  745. the actual driver.
  746. To compile this as a module, choose M here: the module will be
  747. called freevxfs. If unsure, say N.
  748. config MINIX_FS
  749. tristate "Minix file system support"
  750. depends on BLOCK
  751. help
  752. Minix is a simple operating system used in many classes about OS's.
  753. The minix file system (method to organize files on a hard disk
  754. partition or a floppy disk) was the original file system for Linux,
  755. but has been superseded by the second extended file system ext2fs.
  756. You don't want to use the minix file system on your hard disk
  757. because of certain built-in restrictions, but it is sometimes found
  758. on older Linux floppy disks. This option will enlarge your kernel
  759. by about 28 KB. If unsure, say N.
  760. To compile this file system support as a module, choose M here: the
  761. module will be called minix. Note that the file system of your root
  762. partition (the one containing the directory /) cannot be compiled as
  763. a module.
  764. config OMFS_FS
  765. tristate "SonicBlue Optimized MPEG File System support"
  766. depends on BLOCK
  767. select CRC_ITU_T
  768. help
  769. This is the proprietary file system used by the Rio Karma music
  770. player and ReplayTV DVR. Despite the name, this filesystem is not
  771. more efficient than a standard FS for MPEG files, in fact likely
  772. the opposite is true. Say Y if you have either of these devices
  773. and wish to mount its disk.
  774. To compile this file system support as a module, choose M here: the
  775. module will be called omfs. If unsure, say N.
  776. config HPFS_FS
  777. tristate "OS/2 HPFS file system support"
  778. depends on BLOCK
  779. help
  780. OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
  781. is the file system used for organizing files on OS/2 hard disk
  782. partitions. Say Y if you want to be able to read files from and
  783. write files to an OS/2 HPFS partition on your hard drive. OS/2
  784. floppies however are in regular MSDOS format, so you don't need this
  785. option in order to be able to read them. Read
  786. <file:Documentation/filesystems/hpfs.txt>.
  787. To compile this file system support as a module, choose M here: the
  788. module will be called hpfs. If unsure, say N.
  789. config QNX4FS_FS
  790. tristate "QNX4 file system support (read only)"
  791. depends on BLOCK
  792. help
  793. This is the file system used by the real-time operating systems
  794. QNX 4 and QNX 6 (the latter is also called QNX RTP).
  795. Further information is available at <http://www.qnx.com/>.
  796. Say Y if you intend to mount QNX hard disks or floppies.
  797. Unless you say Y to "QNX4FS read-write support" below, you will
  798. only be able to read these file systems.
  799. To compile this file system support as a module, choose M here: the
  800. module will be called qnx4.
  801. If you don't know whether you need it, then you don't need it:
  802. answer N.
  803. config QNX4FS_RW
  804. bool "QNX4FS write support (DANGEROUS)"
  805. depends on QNX4FS_FS && EXPERIMENTAL && BROKEN
  806. help
  807. Say Y if you want to test write support for QNX4 file systems.
  808. It's currently broken, so for now:
  809. answer N.
  810. config ROMFS_FS
  811. tristate "ROM file system support"
  812. depends on BLOCK
  813. ---help---
  814. This is a very small read-only file system mainly intended for
  815. initial ram disks of installation disks, but it could be used for
  816. other read-only media as well. Read
  817. <file:Documentation/filesystems/romfs.txt> for details.
  818. To compile this file system support as a module, choose M here: the
  819. module will be called romfs. Note that the file system of your
  820. root partition (the one containing the directory /) cannot be a
  821. module.
  822. If you don't know whether you need it, then you don't need it:
  823. answer N.
  824. config SYSV_FS
  825. tristate "System V/Xenix/V7/Coherent file system support"
  826. depends on BLOCK
  827. help
  828. SCO, Xenix and Coherent are commercial Unix systems for Intel
  829. machines, and Version 7 was used on the DEC PDP-11. Saying Y
  830. here would allow you to read from their floppies and hard disk
  831. partitions.
  832. If you have floppies or hard disk partitions like that, it is likely
  833. that they contain binaries from those other Unix systems; in order
  834. to run these binaries, you will want to install linux-abi which is
  835. a set of kernel modules that lets you run SCO, Xenix, Wyse,
  836. UnixWare, Dell Unix and System V programs under Linux. It is
  837. available via FTP (user: ftp) from
  838. <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
  839. NOTE: that will work only for binaries from Intel-based systems;
  840. PDP ones will have to wait until somebody ports Linux to -11 ;-)
  841. If you only intend to mount files from some other Unix over the
  842. network using NFS, you don't need the System V file system support
  843. (but you need NFS file system support obviously).
  844. Note that this option is generally not needed for floppies, since a
  845. good portable way to transport files and directories between unixes
  846. (and even other operating systems) is given by the tar program ("man
  847. tar" or preferably "info tar"). Note also that this option has
  848. nothing whatsoever to do with the option "System V IPC". Read about
  849. the System V file system in
  850. <file:Documentation/filesystems/sysv-fs.txt>.
  851. Saying Y here will enlarge your kernel by about 27 KB.
  852. To compile this as a module, choose M here: the module will be called
  853. sysv.
  854. If you haven't heard about all of this before, it's safe to say N.
  855. config UFS_FS
  856. tristate "UFS file system support (read only)"
  857. depends on BLOCK
  858. help
  859. BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
  860. OpenBSD and NeXTstep) use a file system called UFS. Some System V
  861. Unixes can create and mount hard disk partitions and diskettes using
  862. this file system as well. Saying Y here will allow you to read from
  863. these partitions; if you also want to write to them, say Y to the
  864. experimental "UFS file system write support", below. Please read the
  865. file <file:Documentation/filesystems/ufs.txt> for more information.
  866. The recently released UFS2 variant (used in FreeBSD 5.x) is
  867. READ-ONLY supported.
  868. Note that this option is generally not needed for floppies, since a
  869. good portable way to transport files and directories between unixes
  870. (and even other operating systems) is given by the tar program ("man
  871. tar" or preferably "info tar").
  872. When accessing NeXTstep files, you may need to convert them from the
  873. NeXT character set to the Latin1 character set; use the program
  874. recode ("info recode") for this purpose.
  875. To compile the UFS file system support as a module, choose M here: the
  876. module will be called ufs.
  877. If you haven't heard about all of this before, it's safe to say N.
  878. config UFS_FS_WRITE
  879. bool "UFS file system write support (DANGEROUS)"
  880. depends on UFS_FS && EXPERIMENTAL
  881. help
  882. Say Y here if you want to try writing to UFS partitions. This is
  883. experimental, so you should back up your UFS partitions beforehand.
  884. config UFS_DEBUG
  885. bool "UFS debugging"
  886. depends on UFS_FS
  887. help
  888. If you are experiencing any problems with the UFS filesystem, say
  889. Y here. This will result in _many_ additional debugging messages to be
  890. written to the system log.
  891. endmenu
  892. menuconfig NETWORK_FILESYSTEMS
  893. bool "Network File Systems"
  894. default y
  895. depends on NET
  896. ---help---
  897. Say Y here to get to see options for network filesystems and
  898. filesystem-related networking code, such as NFS daemon and
  899. RPCSEC security modules.
  900. This option alone does not add any kernel code.
  901. If you say N, all options in this submenu will be skipped and
  902. disabled; if unsure, say Y here.
  903. if NETWORK_FILESYSTEMS
  904. config NFS_FS
  905. tristate "NFS client support"
  906. depends on INET
  907. select LOCKD
  908. select SUNRPC
  909. select NFS_ACL_SUPPORT if NFS_V3_ACL
  910. help
  911. Choose Y here if you want to access files residing on other
  912. computers using Sun's Network File System protocol. To compile
  913. this file system support as a module, choose M here: the module
  914. will be called nfs.
  915. To mount file systems exported by NFS servers, you also need to
  916. install the user space mount.nfs command which can be found in
  917. the Linux nfs-utils package, available from http://linux-nfs.org/.
  918. Information about using the mount command is available in the
  919. mount(8) man page. More detail about the Linux NFS client
  920. implementation is available via the nfs(5) man page.
  921. Below you can choose which versions of the NFS protocol are
  922. available in the kernel to mount NFS servers. Support for NFS
  923. version 2 (RFC 1094) is always available when NFS_FS is selected.
  924. To configure a system which mounts its root file system via NFS
  925. at boot time, say Y here, select "Kernel level IP
  926. autoconfiguration" in the NETWORK menu, and select "Root file
  927. system on NFS" below. You cannot compile this file system as a
  928. module in this case.
  929. If unsure, say N.
  930. config NFS_V3
  931. bool "NFS client support for NFS version 3"
  932. depends on NFS_FS
  933. help
  934. This option enables support for version 3 of the NFS protocol
  935. (RFC 1813) in the kernel's NFS client.
  936. If unsure, say Y.
  937. config NFS_V3_ACL
  938. bool "NFS client support for the NFSv3 ACL protocol extension"
  939. depends on NFS_V3
  940. help
  941. Some NFS servers support an auxiliary NFSv3 ACL protocol that
  942. Sun added to Solaris but never became an official part of the
  943. NFS version 3 protocol. This protocol extension allows
  944. applications on NFS clients to manipulate POSIX Access Control
  945. Lists on files residing on NFS servers. NFS servers enforce
  946. ACLs on local files whether this protocol is available or not.
  947. Choose Y here if your NFS server supports the Solaris NFSv3 ACL
  948. protocol extension and you want your NFS client to allow
  949. applications to access and modify ACLs on files on the server.
  950. Most NFS servers don't support the Solaris NFSv3 ACL protocol
  951. extension. You can choose N here or specify the "noacl" mount
  952. option to prevent your NFS client from trying to use the NFSv3
  953. ACL protocol.
  954. If unsure, say N.
  955. config NFS_V4
  956. bool "NFS client support for NFS version 4 (EXPERIMENTAL)"
  957. depends on NFS_FS && EXPERIMENTAL
  958. select RPCSEC_GSS_KRB5
  959. help
  960. This option enables support for version 4 of the NFS protocol
  961. (RFC 3530) in the kernel's NFS client.
  962. To mount NFS servers using NFSv4, you also need to install user
  963. space programs which can be found in the Linux nfs-utils package,
  964. available from http://linux-nfs.org/.
  965. If unsure, say N.
  966. config ROOT_NFS
  967. bool "Root file system on NFS"
  968. depends on NFS_FS=y && IP_PNP
  969. help
  970. If you want your system to mount its root file system via NFS,
  971. choose Y here. This is common practice for managing systems
  972. without local permanent storage. For details, read
  973. <file:Documentation/filesystems/nfsroot.txt>.
  974. Most people say N here.
  975. config NFSD
  976. tristate "NFS server support"
  977. depends on INET
  978. select LOCKD
  979. select SUNRPC
  980. select EXPORTFS
  981. select NFS_ACL_SUPPORT if NFSD_V2_ACL
  982. help
  983. Choose Y here if you want to allow other computers to access
  984. files residing on this system using Sun's Network File System
  985. protocol. To compile the NFS server support as a module,
  986. choose M here: the module will be called nfsd.
  987. You may choose to use a user-space NFS server instead, in which
  988. case you can choose N here.
  989. To export local file systems using NFS, you also need to install
  990. user space programs which can be found in the Linux nfs-utils
  991. package, available from http://linux-nfs.org/. More detail about
  992. the Linux NFS server implementation is available via the
  993. exports(5) man page.
  994. Below you can choose which versions of the NFS protocol are
  995. available to clients mounting the NFS server on this system.
  996. Support for NFS version 2 (RFC 1094) is always available when
  997. CONFIG_NFSD is selected.
  998. If unsure, say N.
  999. config NFSD_V2_ACL
  1000. bool
  1001. depends on NFSD
  1002. config NFSD_V3
  1003. bool "NFS server support for NFS version 3"
  1004. depends on NFSD
  1005. help
  1006. This option enables support in your system's NFS server for
  1007. version 3 of the NFS protocol (RFC 1813).
  1008. If unsure, say Y.
  1009. config NFSD_V3_ACL
  1010. bool "NFS server support for the NFSv3 ACL protocol extension"
  1011. depends on NFSD_V3
  1012. select NFSD_V2_ACL
  1013. help
  1014. Solaris NFS servers support an auxiliary NFSv3 ACL protocol that
  1015. never became an official part of the NFS version 3 protocol.
  1016. This protocol extension allows applications on NFS clients to
  1017. manipulate POSIX Access Control Lists on files residing on NFS
  1018. servers. NFS servers enforce POSIX ACLs on local files whether
  1019. this protocol is available or not.
  1020. This option enables support in your system's NFS server for the
  1021. NFSv3 ACL protocol extension allowing NFS clients to manipulate
  1022. POSIX ACLs on files exported by your system's NFS server. NFS
  1023. clients which support the Solaris NFSv3 ACL protocol can then
  1024. access and modify ACLs on your NFS server.
  1025. To store ACLs on your NFS server, you also need to enable ACL-
  1026. related CONFIG options for your local file systems of choice.
  1027. If unsure, say N.
  1028. config NFSD_V4
  1029. bool "NFS server support for NFS version 4 (EXPERIMENTAL)"
  1030. depends on NFSD && PROC_FS && EXPERIMENTAL
  1031. select NFSD_V3
  1032. select FS_POSIX_ACL
  1033. select RPCSEC_GSS_KRB5
  1034. help
  1035. This option enables support in your system's NFS server for
  1036. version 4 of the NFS protocol (RFC 3530).
  1037. To export files using NFSv4, you need to install additional user
  1038. space programs which can be found in the Linux nfs-utils package,
  1039. available from http://linux-nfs.org/.
  1040. If unsure, say N.
  1041. config LOCKD
  1042. tristate
  1043. config LOCKD_V4
  1044. bool
  1045. depends on NFSD_V3 || NFS_V3
  1046. default y
  1047. config EXPORTFS
  1048. tristate
  1049. config NFS_ACL_SUPPORT
  1050. tristate
  1051. select FS_POSIX_ACL
  1052. config NFS_COMMON
  1053. bool
  1054. depends on NFSD || NFS_FS
  1055. default y
  1056. config SUNRPC
  1057. tristate
  1058. config SUNRPC_GSS
  1059. tristate
  1060. config SUNRPC_XPRT_RDMA
  1061. tristate
  1062. depends on SUNRPC && INFINIBAND && EXPERIMENTAL
  1063. default SUNRPC && INFINIBAND
  1064. help
  1065. This option enables an RPC client transport capability that
  1066. allows the NFS client to mount servers via an RDMA-enabled
  1067. transport.
  1068. To compile RPC client RDMA transport support as a module,
  1069. choose M here: the module will be called xprtrdma.
  1070. If unsure, say N.
  1071. config SUNRPC_REGISTER_V4
  1072. bool "Register local RPC services via rpcbind v4 (EXPERIMENTAL)"
  1073. depends on SUNRPC && EXPERIMENTAL
  1074. default n
  1075. help
  1076. Sun added support for registering RPC services at an IPv6
  1077. address by creating two new versions of the rpcbind protocol
  1078. (RFC 1833).
  1079. This option enables support in the kernel RPC server for
  1080. registering kernel RPC services via version 4 of the rpcbind
  1081. protocol. If you enable this option, you must run a portmapper
  1082. daemon that supports rpcbind protocol version 4.
  1083. Serving NFS over IPv6 from knfsd (the kernel's NFS server)
  1084. requires that you enable this option and use a portmapper that
  1085. supports rpcbind version 4.
  1086. If unsure, say N to get traditional behavior (register kernel
  1087. RPC services using only rpcbind version 2). Distributions
  1088. using the legacy Linux portmapper daemon must say N here.
  1089. config RPCSEC_GSS_KRB5
  1090. tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
  1091. depends on SUNRPC && EXPERIMENTAL
  1092. select SUNRPC_GSS
  1093. select CRYPTO
  1094. select CRYPTO_MD5
  1095. select CRYPTO_DES
  1096. select CRYPTO_CBC
  1097. help
  1098. Choose Y here to enable Secure RPC using the Kerberos version 5
  1099. GSS-API mechanism (RFC 1964).
  1100. Secure RPC calls with Kerberos require an auxiliary user-space
  1101. daemon which may be found in the Linux nfs-utils package
  1102. available from http://linux-nfs.org/. In addition, user-space
  1103. Kerberos support should be installed.
  1104. If unsure, say N.
  1105. config RPCSEC_GSS_SPKM3
  1106. tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
  1107. depends on SUNRPC && EXPERIMENTAL
  1108. select SUNRPC_GSS
  1109. select CRYPTO
  1110. select CRYPTO_MD5
  1111. select CRYPTO_DES
  1112. select CRYPTO_CAST5
  1113. select CRYPTO_CBC
  1114. help
  1115. Choose Y here to enable Secure RPC using the SPKM3 public key
  1116. GSS-API mechansim (RFC 2025).
  1117. Secure RPC calls with SPKM3 require an auxiliary userspace
  1118. daemon which may be found in the Linux nfs-utils package
  1119. available from http://linux-nfs.org/.
  1120. If unsure, say N.
  1121. config SMB_FS
  1122. tristate "SMB file system support (OBSOLETE, please use CIFS)"
  1123. depends on INET
  1124. select NLS
  1125. help
  1126. SMB (Server Message Block) is the protocol Windows for Workgroups
  1127. (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
  1128. files and printers over local networks. Saying Y here allows you to
  1129. mount their file systems (often called "shares" in this context) and
  1130. access them just like any other Unix directory. Currently, this
  1131. works only if the Windows machines use TCP/IP as the underlying
  1132. transport protocol, and not NetBEUI. For details, read
  1133. <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
  1134. available from <http://www.tldp.org/docs.html#howto>.
  1135. Note: if you just want your box to act as an SMB *server* and make
  1136. files and printing services available to Windows clients (which need
  1137. to have a TCP/IP stack), you don't need to say Y here; you can use
  1138. the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
  1139. for that.
  1140. General information about how to connect Linux, Windows machines and
  1141. Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
  1142. To compile the SMB support as a module, choose M here:
  1143. the module will be called smbfs. Most people say N, however.
  1144. config SMB_NLS_DEFAULT
  1145. bool "Use a default NLS"
  1146. depends on SMB_FS
  1147. help
  1148. Enabling this will make smbfs use nls translations by default. You
  1149. need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
  1150. settings and you need to give the default nls for the SMB server as
  1151. CONFIG_SMB_NLS_REMOTE.
  1152. The nls settings can be changed at mount time, if your smbmount
  1153. supports that, using the codepage and iocharset parameters.
  1154. smbmount from samba 2.2.0 or later supports this.
  1155. config SMB_NLS_REMOTE
  1156. string "Default Remote NLS Option"
  1157. depends on SMB_NLS_DEFAULT
  1158. default "cp437"
  1159. help
  1160. This setting allows you to specify a default value for which
  1161. codepage the server uses. If this field is left blank no
  1162. translations will be done by default. The local codepage/charset
  1163. default to CONFIG_NLS_DEFAULT.
  1164. The nls settings can be changed at mount time, if your smbmount
  1165. supports that, using the codepage and iocharset parameters.
  1166. smbmount from samba 2.2.0 or later supports this.
  1167. source "fs/cifs/Kconfig"
  1168. config NCP_FS
  1169. tristate "NCP file system support (to mount NetWare volumes)"
  1170. depends on IPX!=n || INET
  1171. help
  1172. NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
  1173. used by Novell NetWare clients to talk to file servers. It is to
  1174. IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
  1175. to mount NetWare file server volumes and to access them just like
  1176. any other Unix directory. For details, please read the file
  1177. <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
  1178. the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
  1179. You do not have to say Y here if you want your Linux box to act as a
  1180. file *server* for Novell NetWare clients.
  1181. General information about how to connect Linux, Windows machines and
  1182. Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
  1183. To compile this as a module, choose M here: the module will be called
  1184. ncpfs. Say N unless you are connected to a Novell network.
  1185. source "fs/ncpfs/Kconfig"
  1186. config CODA_FS
  1187. tristate "Coda file system support (advanced network fs)"
  1188. depends on INET
  1189. help
  1190. Coda is an advanced network file system, similar to NFS in that it
  1191. enables you to mount file systems of a remote server and access them
  1192. with regular Unix commands as if they were sitting on your hard
  1193. disk. Coda has several advantages over NFS: support for
  1194. disconnected operation (e.g. for laptops), read/write server
  1195. replication, security model for authentication and encryption,
  1196. persistent client caches and write back caching.
  1197. If you say Y here, your Linux box will be able to act as a Coda
  1198. *client*. You will need user level code as well, both for the
  1199. client and server. Servers are currently user level, i.e. they need
  1200. no kernel support. Please read
  1201. <file:Documentation/filesystems/coda.txt> and check out the Coda
  1202. home page <http://www.coda.cs.cmu.edu/>.
  1203. To compile the coda client support as a module, choose M here: the
  1204. module will be called coda.
  1205. config AFS_FS
  1206. tristate "Andrew File System support (AFS) (EXPERIMENTAL)"
  1207. depends on INET && EXPERIMENTAL
  1208. select AF_RXRPC
  1209. help
  1210. If you say Y here, you will get an experimental Andrew File System
  1211. driver. It currently only supports unsecured read-only AFS access.
  1212. See <file:Documentation/filesystems/afs.txt> for more information.
  1213. If unsure, say N.
  1214. config AFS_DEBUG
  1215. bool "AFS dynamic debugging"
  1216. depends on AFS_FS
  1217. help
  1218. Say Y here to make runtime controllable debugging messages appear.
  1219. See <file:Documentation/filesystems/afs.txt> for more information.
  1220. If unsure, say N.
  1221. config 9P_FS
  1222. tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
  1223. depends on INET && NET_9P && EXPERIMENTAL
  1224. help
  1225. If you say Y here, you will get experimental support for
  1226. Plan 9 resource sharing via the 9P2000 protocol.
  1227. See <http://v9fs.sf.net> for more information.
  1228. If unsure, say N.
  1229. endif # NETWORK_FILESYSTEMS
  1230. if BLOCK
  1231. menu "Partition Types"
  1232. source "fs/partitions/Kconfig"
  1233. endmenu
  1234. endif
  1235. source "fs/nls/Kconfig"
  1236. source "fs/dlm/Kconfig"
  1237. endmenu