Kconfig 48 KB

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