Kconfig 53 KB

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