Kconfig 53 KB

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