Kconfig 37 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868869870871872873874875876877878879880881882883884885886887888889890891892893894895896897898899900901902903904905906907908909910911912913914915916917918919920921922923924925926927928929930931932933934935936937938939940941942943944945946947948949950951952953954955956957958959960961962963964965966967968969970971972973974975976977978979980981982983984985986987988989990991992993994995996997998999100010011002100310041005100610071008100910101011101210131014101510161017101810191020102110221023102410251026102710281029103010311032103310341035103610371038103910401041104210431044104510461047104810491050105110521053105410551056105710581059106010611062106310641065106610671068106910701071107210731074107510761077107810791080108110821083108410851086108710881089109010911092
  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. source "fs/autofs/Kconfig"
  96. source "fs/autofs4/Kconfig"
  97. source "fs/fuse/Kconfig"
  98. config GENERIC_ACL
  99. bool
  100. select FS_POSIX_ACL
  101. if BLOCK
  102. menu "CD-ROM/DVD Filesystems"
  103. source "fs/isofs/Kconfig"
  104. source "fs/udf/Kconfig"
  105. endmenu
  106. endif # BLOCK
  107. if BLOCK
  108. menu "DOS/FAT/NT Filesystems"
  109. source "fs/fat/Kconfig"
  110. source "fs/ntfs/Kconfig"
  111. endmenu
  112. endif # BLOCK
  113. menu "Pseudo filesystems"
  114. source "fs/proc/Kconfig"
  115. config SYSFS
  116. bool "sysfs file system support" if EMBEDDED
  117. default y
  118. help
  119. The sysfs filesystem is a virtual filesystem that the kernel uses to
  120. export internal kernel objects, their attributes, and their
  121. relationships to one another.
  122. Users can use sysfs to ascertain useful information about the running
  123. kernel, such as the devices the kernel has discovered on each bus and
  124. which driver each is bound to. sysfs can also be used to tune devices
  125. and other kernel subsystems.
  126. Some system agents rely on the information in sysfs to operate.
  127. /sbin/hotplug uses device and object attributes in sysfs to assist in
  128. delegating policy decisions, like persistently naming devices.
  129. sysfs is currently used by the block subsystem to mount the root
  130. partition. If sysfs is disabled you must specify the boot device on
  131. the kernel boot command line via its major and minor numbers. For
  132. example, "root=03:01" for /dev/hda1.
  133. Designers of embedded systems may wish to say N here to conserve space.
  134. config TMPFS
  135. bool "Virtual memory file system support (former shm fs)"
  136. help
  137. Tmpfs is a file system which keeps all files in virtual memory.
  138. Everything in tmpfs is temporary in the sense that no files will be
  139. created on your hard drive. The files live in memory and swap
  140. space. If you unmount a tmpfs instance, everything stored therein is
  141. lost.
  142. See <file:Documentation/filesystems/tmpfs.txt> for details.
  143. config TMPFS_POSIX_ACL
  144. bool "Tmpfs POSIX Access Control Lists"
  145. depends on TMPFS
  146. select GENERIC_ACL
  147. help
  148. POSIX Access Control Lists (ACLs) support permissions for users and
  149. groups beyond the owner/group/world scheme.
  150. To learn more about Access Control Lists, visit the POSIX ACLs for
  151. Linux website <http://acl.bestbits.at/>.
  152. If you don't know what Access Control Lists are, say N.
  153. config HUGETLBFS
  154. bool "HugeTLB file system support"
  155. depends on X86 || IA64 || PPC64 || SPARC64 || (SUPERH && MMU) || \
  156. (S390 && 64BIT) || BROKEN
  157. help
  158. hugetlbfs is a filesystem backing for HugeTLB pages, based on
  159. ramfs. For architectures that support it, say Y here and read
  160. <file:Documentation/vm/hugetlbpage.txt> for details.
  161. If unsure, say N.
  162. config HUGETLB_PAGE
  163. def_bool HUGETLBFS
  164. config CONFIGFS_FS
  165. tristate "Userspace-driven configuration filesystem"
  166. depends on SYSFS
  167. help
  168. configfs is a ram-based filesystem that provides the converse
  169. of sysfs's functionality. Where sysfs is a filesystem-based
  170. view of kernel objects, configfs is a filesystem-based manager
  171. of kernel objects, or config_items.
  172. Both sysfs and configfs can and should exist together on the
  173. same system. One is not a replacement for the other.
  174. endmenu
  175. menuconfig MISC_FILESYSTEMS
  176. bool "Miscellaneous filesystems"
  177. default y
  178. ---help---
  179. Say Y here to get to see options for various miscellaneous
  180. filesystems, such as filesystems that came from other
  181. operating systems.
  182. This option alone does not add any kernel code.
  183. If you say N, all options in this submenu will be skipped and
  184. disabled; if unsure, say Y here.
  185. if MISC_FILESYSTEMS
  186. config ADFS_FS
  187. tristate "ADFS file system support (EXPERIMENTAL)"
  188. depends on BLOCK && EXPERIMENTAL
  189. help
  190. The Acorn Disc Filing System is the standard file system of the
  191. RiscOS operating system which runs on Acorn's ARM-based Risc PC
  192. systems and the Acorn Archimedes range of machines. If you say Y
  193. here, Linux will be able to read from ADFS partitions on hard drives
  194. and from ADFS-formatted floppy discs. If you also want to be able to
  195. write to those devices, say Y to "ADFS write support" below.
  196. The ADFS partition should be the first partition (i.e.,
  197. /dev/[hs]d?1) on each of your drives. Please read the file
  198. <file:Documentation/filesystems/adfs.txt> for further details.
  199. To compile this code as a module, choose M here: the module will be
  200. called adfs.
  201. If unsure, say N.
  202. config ADFS_FS_RW
  203. bool "ADFS write support (DANGEROUS)"
  204. depends on ADFS_FS
  205. help
  206. If you say Y here, you will be able to write to ADFS partitions on
  207. hard drives and ADFS-formatted floppy disks. This is experimental
  208. codes, so if you're unsure, say N.
  209. config AFFS_FS
  210. tristate "Amiga FFS file system support (EXPERIMENTAL)"
  211. depends on BLOCK && EXPERIMENTAL
  212. help
  213. The Fast File System (FFS) is the common file system used on hard
  214. disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
  215. if you want to be able to read and write files from and to an Amiga
  216. FFS partition on your hard drive. Amiga floppies however cannot be
  217. read with this driver due to an incompatibility of the floppy
  218. controller used in an Amiga and the standard floppy controller in
  219. PCs and workstations. Read <file:Documentation/filesystems/affs.txt>
  220. and <file:fs/affs/Changes>.
  221. With this driver you can also mount disk files used by Bernd
  222. Schmidt's Un*X Amiga Emulator
  223. (<http://www.freiburg.linux.de/~uae/>).
  224. If you want to do this, you will also need to say Y or M to "Loop
  225. device support", above.
  226. To compile this file system support as a module, choose M here: the
  227. module will be called affs. If unsure, say N.
  228. config ECRYPT_FS
  229. tristate "eCrypt filesystem layer support (EXPERIMENTAL)"
  230. depends on EXPERIMENTAL && KEYS && CRYPTO && NET
  231. help
  232. Encrypted filesystem that operates on the VFS layer. See
  233. <file:Documentation/filesystems/ecryptfs.txt> to learn more about
  234. eCryptfs. Userspace components are required and can be
  235. obtained from <http://ecryptfs.sf.net>.
  236. To compile this file system support as a module, choose M here: the
  237. module will be called ecryptfs.
  238. config HFS_FS
  239. tristate "Apple Macintosh file system support (EXPERIMENTAL)"
  240. depends on BLOCK && EXPERIMENTAL
  241. select NLS
  242. help
  243. If you say Y here, you will be able to mount Macintosh-formatted
  244. floppy disks and hard drive partitions with full read-write access.
  245. Please read <file:Documentation/filesystems/hfs.txt> to learn about
  246. the available mount options.
  247. To compile this file system support as a module, choose M here: the
  248. module will be called hfs.
  249. config HFSPLUS_FS
  250. tristate "Apple Extended HFS file system support"
  251. depends on BLOCK
  252. select NLS
  253. select NLS_UTF8
  254. help
  255. If you say Y here, you will be able to mount extended format
  256. Macintosh-formatted hard drive partitions with full read-write access.
  257. This file system is often called HFS+ and was introduced with
  258. MacOS 8. It includes all Mac specific filesystem data such as
  259. data forks and creator codes, but it also has several UNIX
  260. style features such as file ownership and permissions.
  261. config BEFS_FS
  262. tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)"
  263. depends on BLOCK && EXPERIMENTAL
  264. select NLS
  265. help
  266. The BeOS File System (BeFS) is the native file system of Be, Inc's
  267. BeOS. Notable features include support for arbitrary attributes
  268. on files and directories, and database-like indices on selected
  269. attributes. (Also note that this driver doesn't make those features
  270. available at this time). It is a 64 bit filesystem, so it supports
  271. extremely large volumes and files.
  272. If you use this filesystem, you should also say Y to at least one
  273. of the NLS (native language support) options below.
  274. If you don't know what this is about, say N.
  275. To compile this as a module, choose M here: the module will be
  276. called befs.
  277. config BEFS_DEBUG
  278. bool "Debug BeFS"
  279. depends on BEFS_FS
  280. help
  281. If you say Y here, you can use the 'debug' mount option to enable
  282. debugging output from the driver.
  283. config BFS_FS
  284. tristate "BFS file system support (EXPERIMENTAL)"
  285. depends on BLOCK && EXPERIMENTAL
  286. help
  287. Boot File System (BFS) is a file system used under SCO UnixWare to
  288. allow the bootloader access to the kernel image and other important
  289. files during the boot process. It is usually mounted under /stand
  290. and corresponds to the slice marked as "STAND" in the UnixWare
  291. partition. You should say Y if you want to read or write the files
  292. on your /stand slice from within Linux. You then also need to say Y
  293. to "UnixWare slices support", below. More information about the BFS
  294. file system is contained in the file
  295. <file:Documentation/filesystems/bfs.txt>.
  296. If you don't know what this is about, say N.
  297. To compile this as a module, choose M here: the module will be called
  298. bfs. Note that the file system of your root partition (the one
  299. containing the directory /) cannot be compiled as a module.
  300. config EFS_FS
  301. tristate "EFS file system support (read only) (EXPERIMENTAL)"
  302. depends on BLOCK && EXPERIMENTAL
  303. help
  304. EFS is an older file system used for non-ISO9660 CD-ROMs and hard
  305. disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
  306. uses the XFS file system for hard disk partitions however).
  307. This implementation only offers read-only access. If you don't know
  308. what all this is about, it's safe to say N. For more information
  309. about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
  310. To compile the EFS file system support as a module, choose M here: the
  311. module will be called efs.
  312. source "fs/jffs2/Kconfig"
  313. # UBIFS File system configuration
  314. source "fs/ubifs/Kconfig"
  315. config CRAMFS
  316. tristate "Compressed ROM file system support (cramfs)"
  317. depends on BLOCK
  318. select ZLIB_INFLATE
  319. help
  320. Saying Y here includes support for CramFs (Compressed ROM File
  321. System). CramFs is designed to be a simple, small, and compressed
  322. file system for ROM based embedded systems. CramFs is read-only,
  323. limited to 256MB file systems (with 16MB files), and doesn't support
  324. 16/32 bits uid/gid, hard links and timestamps.
  325. See <file:Documentation/filesystems/cramfs.txt> and
  326. <file:fs/cramfs/README> for further information.
  327. To compile this as a module, choose M here: the module will be called
  328. cramfs. Note that the root file system (the one containing the
  329. directory /) cannot be compiled as a module.
  330. If unsure, say N.
  331. config SQUASHFS
  332. tristate "SquashFS 4.0 - Squashed file system support"
  333. depends on BLOCK
  334. select ZLIB_INFLATE
  335. help
  336. Saying Y here includes support for SquashFS 4.0 (a Compressed
  337. Read-Only File System). Squashfs is a highly compressed read-only
  338. filesystem for Linux. It uses zlib compression to compress both
  339. files, inodes and directories. Inodes in the system are very small
  340. and all blocks are packed to minimise data overhead. Block sizes
  341. greater than 4K are supported up to a maximum of 1 Mbytes (default
  342. block size 128K). SquashFS 4.0 supports 64 bit filesystems and files
  343. (larger than 4GB), full uid/gid information, hard links and
  344. timestamps.
  345. Squashfs is intended for general read-only filesystem use, for
  346. archival use (i.e. in cases where a .tar.gz file may be used), and in
  347. embedded systems where low overhead is needed. Further information
  348. and tools are available from http://squashfs.sourceforge.net.
  349. If you want to compile this as a module ( = code which can be
  350. inserted in and removed from the running kernel whenever you want),
  351. say M here and read <file:Documentation/modules.txt>. The module
  352. will be called squashfs. Note that the root file system (the one
  353. containing the directory /) cannot be compiled as a module.
  354. If unsure, say N.
  355. config SQUASHFS_EMBEDDED
  356. bool "Additional option for memory-constrained systems"
  357. depends on SQUASHFS
  358. default n
  359. help
  360. Saying Y here allows you to specify cache size.
  361. If unsure, say N.
  362. config SQUASHFS_FRAGMENT_CACHE_SIZE
  363. int "Number of fragments cached" if SQUASHFS_EMBEDDED
  364. depends on SQUASHFS
  365. default "3"
  366. help
  367. By default SquashFS caches the last 3 fragments read from
  368. the filesystem. Increasing this amount may mean SquashFS
  369. has to re-read fragments less often from disk, at the expense
  370. of extra system memory. Decreasing this amount will mean
  371. SquashFS uses less memory at the expense of extra reads from disk.
  372. Note there must be at least one cached fragment. Anything
  373. much more than three will probably not make much difference.
  374. config VXFS_FS
  375. tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
  376. depends on BLOCK
  377. help
  378. FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
  379. file system format. VERITAS VxFS(TM) is the standard file system
  380. of SCO UnixWare (and possibly others) and optionally available
  381. for Sunsoft Solaris, HP-UX and many other operating systems.
  382. Currently only readonly access is supported.
  383. NOTE: the file system type as used by mount(1), mount(2) and
  384. fstab(5) is 'vxfs' as it describes the file system format, not
  385. the actual driver.
  386. To compile this as a module, choose M here: the module will be
  387. called freevxfs. If unsure, say N.
  388. config MINIX_FS
  389. tristate "Minix file system support"
  390. depends on BLOCK
  391. help
  392. Minix is a simple operating system used in many classes about OS's.
  393. The minix file system (method to organize files on a hard disk
  394. partition or a floppy disk) was the original file system for Linux,
  395. but has been superseded by the second extended file system ext2fs.
  396. You don't want to use the minix file system on your hard disk
  397. because of certain built-in restrictions, but it is sometimes found
  398. on older Linux floppy disks. This option will enlarge your kernel
  399. by about 28 KB. If unsure, say N.
  400. To compile this file system support as a module, choose M here: the
  401. module will be called minix. Note that the file system of your root
  402. partition (the one containing the directory /) cannot be compiled as
  403. a module.
  404. config OMFS_FS
  405. tristate "SonicBlue Optimized MPEG File System support"
  406. depends on BLOCK
  407. select CRC_ITU_T
  408. help
  409. This is the proprietary file system used by the Rio Karma music
  410. player and ReplayTV DVR. Despite the name, this filesystem is not
  411. more efficient than a standard FS for MPEG files, in fact likely
  412. the opposite is true. Say Y if you have either of these devices
  413. and wish to mount its disk.
  414. To compile this file system support as a module, choose M here: the
  415. module will be called omfs. If unsure, say N.
  416. config HPFS_FS
  417. tristate "OS/2 HPFS file system support"
  418. depends on BLOCK
  419. help
  420. OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
  421. is the file system used for organizing files on OS/2 hard disk
  422. partitions. Say Y if you want to be able to read files from and
  423. write files to an OS/2 HPFS partition on your hard drive. OS/2
  424. floppies however are in regular MSDOS format, so you don't need this
  425. option in order to be able to read them. Read
  426. <file:Documentation/filesystems/hpfs.txt>.
  427. To compile this file system support as a module, choose M here: the
  428. module will be called hpfs. If unsure, say N.
  429. config QNX4FS_FS
  430. tristate "QNX4 file system support (read only)"
  431. depends on BLOCK
  432. help
  433. This is the file system used by the real-time operating systems
  434. QNX 4 and QNX 6 (the latter is also called QNX RTP).
  435. Further information is available at <http://www.qnx.com/>.
  436. Say Y if you intend to mount QNX hard disks or floppies.
  437. Unless you say Y to "QNX4FS read-write support" below, you will
  438. only be able to read these file systems.
  439. To compile this file system support as a module, choose M here: the
  440. module will be called qnx4.
  441. If you don't know whether you need it, then you don't need it:
  442. answer N.
  443. config QNX4FS_RW
  444. bool "QNX4FS write support (DANGEROUS)"
  445. depends on QNX4FS_FS && EXPERIMENTAL && BROKEN
  446. help
  447. Say Y if you want to test write support for QNX4 file systems.
  448. It's currently broken, so for now:
  449. answer N.
  450. config ROMFS_FS
  451. tristate "ROM file system support"
  452. depends on BLOCK
  453. ---help---
  454. This is a very small read-only file system mainly intended for
  455. initial ram disks of installation disks, but it could be used for
  456. other read-only media as well. Read
  457. <file:Documentation/filesystems/romfs.txt> for details.
  458. To compile this file system support as a module, choose M here: the
  459. module will be called romfs. Note that the file system of your
  460. root partition (the one containing the directory /) cannot be a
  461. module.
  462. If you don't know whether you need it, then you don't need it:
  463. answer N.
  464. config SYSV_FS
  465. tristate "System V/Xenix/V7/Coherent file system support"
  466. depends on BLOCK
  467. help
  468. SCO, Xenix and Coherent are commercial Unix systems for Intel
  469. machines, and Version 7 was used on the DEC PDP-11. Saying Y
  470. here would allow you to read from their floppies and hard disk
  471. partitions.
  472. If you have floppies or hard disk partitions like that, it is likely
  473. that they contain binaries from those other Unix systems; in order
  474. to run these binaries, you will want to install linux-abi which is
  475. a set of kernel modules that lets you run SCO, Xenix, Wyse,
  476. UnixWare, Dell Unix and System V programs under Linux. It is
  477. available via FTP (user: ftp) from
  478. <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
  479. NOTE: that will work only for binaries from Intel-based systems;
  480. PDP ones will have to wait until somebody ports Linux to -11 ;-)
  481. If you only intend to mount files from some other Unix over the
  482. network using NFS, you don't need the System V file system support
  483. (but you need NFS file system support obviously).
  484. Note that this option is generally not needed for floppies, since a
  485. good portable way to transport files and directories between unixes
  486. (and even other operating systems) is given by the tar program ("man
  487. tar" or preferably "info tar"). Note also that this option has
  488. nothing whatsoever to do with the option "System V IPC". Read about
  489. the System V file system in
  490. <file:Documentation/filesystems/sysv-fs.txt>.
  491. Saying Y here will enlarge your kernel by about 27 KB.
  492. To compile this as a module, choose M here: the module will be called
  493. sysv.
  494. If you haven't heard about all of this before, it's safe to say N.
  495. config UFS_FS
  496. tristate "UFS file system support (read only)"
  497. depends on BLOCK
  498. help
  499. BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
  500. OpenBSD and NeXTstep) use a file system called UFS. Some System V
  501. Unixes can create and mount hard disk partitions and diskettes using
  502. this file system as well. Saying Y here will allow you to read from
  503. these partitions; if you also want to write to them, say Y to the
  504. experimental "UFS file system write support", below. Please read the
  505. file <file:Documentation/filesystems/ufs.txt> for more information.
  506. The recently released UFS2 variant (used in FreeBSD 5.x) is
  507. READ-ONLY supported.
  508. Note that this option is generally not needed for floppies, since a
  509. good portable way to transport files and directories between unixes
  510. (and even other operating systems) is given by the tar program ("man
  511. tar" or preferably "info tar").
  512. When accessing NeXTstep files, you may need to convert them from the
  513. NeXT character set to the Latin1 character set; use the program
  514. recode ("info recode") for this purpose.
  515. To compile the UFS file system support as a module, choose M here: the
  516. module will be called ufs.
  517. If you haven't heard about all of this before, it's safe to say N.
  518. config UFS_FS_WRITE
  519. bool "UFS file system write support (DANGEROUS)"
  520. depends on UFS_FS && EXPERIMENTAL
  521. help
  522. Say Y here if you want to try writing to UFS partitions. This is
  523. experimental, so you should back up your UFS partitions beforehand.
  524. config UFS_DEBUG
  525. bool "UFS debugging"
  526. depends on UFS_FS
  527. help
  528. If you are experiencing any problems with the UFS filesystem, say
  529. Y here. This will result in _many_ additional debugging messages to be
  530. written to the system log.
  531. endif # MISC_FILESYSTEMS
  532. menuconfig NETWORK_FILESYSTEMS
  533. bool "Network File Systems"
  534. default y
  535. depends on NET
  536. ---help---
  537. Say Y here to get to see options for network filesystems and
  538. filesystem-related networking code, such as NFS daemon and
  539. RPCSEC security modules.
  540. This option alone does not add any kernel code.
  541. If you say N, all options in this submenu will be skipped and
  542. disabled; if unsure, say Y here.
  543. if NETWORK_FILESYSTEMS
  544. config NFS_FS
  545. tristate "NFS client support"
  546. depends on INET
  547. select LOCKD
  548. select SUNRPC
  549. select NFS_ACL_SUPPORT if NFS_V3_ACL
  550. help
  551. Choose Y here if you want to access files residing on other
  552. computers using Sun's Network File System protocol. To compile
  553. this file system support as a module, choose M here: the module
  554. will be called nfs.
  555. To mount file systems exported by NFS servers, you also need to
  556. install the user space mount.nfs command which can be found in
  557. the Linux nfs-utils package, available from http://linux-nfs.org/.
  558. Information about using the mount command is available in the
  559. mount(8) man page. More detail about the Linux NFS client
  560. implementation is available via the nfs(5) man page.
  561. Below you can choose which versions of the NFS protocol are
  562. available in the kernel to mount NFS servers. Support for NFS
  563. version 2 (RFC 1094) is always available when NFS_FS is selected.
  564. To configure a system which mounts its root file system via NFS
  565. at boot time, say Y here, select "Kernel level IP
  566. autoconfiguration" in the NETWORK menu, and select "Root file
  567. system on NFS" below. You cannot compile this file system as a
  568. module in this case.
  569. If unsure, say N.
  570. config NFS_V3
  571. bool "NFS client support for NFS version 3"
  572. depends on NFS_FS
  573. help
  574. This option enables support for version 3 of the NFS protocol
  575. (RFC 1813) in the kernel's NFS client.
  576. If unsure, say Y.
  577. config NFS_V3_ACL
  578. bool "NFS client support for the NFSv3 ACL protocol extension"
  579. depends on NFS_V3
  580. help
  581. Some NFS servers support an auxiliary NFSv3 ACL protocol that
  582. Sun added to Solaris but never became an official part of the
  583. NFS version 3 protocol. This protocol extension allows
  584. applications on NFS clients to manipulate POSIX Access Control
  585. Lists on files residing on NFS servers. NFS servers enforce
  586. ACLs on local files whether this protocol is available or not.
  587. Choose Y here if your NFS server supports the Solaris NFSv3 ACL
  588. protocol extension and you want your NFS client to allow
  589. applications to access and modify ACLs on files on the server.
  590. Most NFS servers don't support the Solaris NFSv3 ACL protocol
  591. extension. You can choose N here or specify the "noacl" mount
  592. option to prevent your NFS client from trying to use the NFSv3
  593. ACL protocol.
  594. If unsure, say N.
  595. config NFS_V4
  596. bool "NFS client support for NFS version 4 (EXPERIMENTAL)"
  597. depends on NFS_FS && EXPERIMENTAL
  598. select RPCSEC_GSS_KRB5
  599. help
  600. This option enables support for version 4 of the NFS protocol
  601. (RFC 3530) in the kernel's NFS client.
  602. To mount NFS servers using NFSv4, you also need to install user
  603. space programs which can be found in the Linux nfs-utils package,
  604. available from http://linux-nfs.org/.
  605. If unsure, say N.
  606. config ROOT_NFS
  607. bool "Root file system on NFS"
  608. depends on NFS_FS=y && IP_PNP
  609. help
  610. If you want your system to mount its root file system via NFS,
  611. choose Y here. This is common practice for managing systems
  612. without local permanent storage. For details, read
  613. <file:Documentation/filesystems/nfsroot.txt>.
  614. Most people say N here.
  615. config NFSD
  616. tristate "NFS server support"
  617. depends on INET
  618. select LOCKD
  619. select SUNRPC
  620. select EXPORTFS
  621. select NFS_ACL_SUPPORT if NFSD_V2_ACL
  622. help
  623. Choose Y here if you want to allow other computers to access
  624. files residing on this system using Sun's Network File System
  625. protocol. To compile the NFS server support as a module,
  626. choose M here: the module will be called nfsd.
  627. You may choose to use a user-space NFS server instead, in which
  628. case you can choose N here.
  629. To export local file systems using NFS, you also need to install
  630. user space programs which can be found in the Linux nfs-utils
  631. package, available from http://linux-nfs.org/. More detail about
  632. the Linux NFS server implementation is available via the
  633. exports(5) man page.
  634. Below you can choose which versions of the NFS protocol are
  635. available to clients mounting the NFS server on this system.
  636. Support for NFS version 2 (RFC 1094) is always available when
  637. CONFIG_NFSD is selected.
  638. If unsure, say N.
  639. config NFSD_V2_ACL
  640. bool
  641. depends on NFSD
  642. config NFSD_V3
  643. bool "NFS server support for NFS version 3"
  644. depends on NFSD
  645. help
  646. This option enables support in your system's NFS server for
  647. version 3 of the NFS protocol (RFC 1813).
  648. If unsure, say Y.
  649. config NFSD_V3_ACL
  650. bool "NFS server support for the NFSv3 ACL protocol extension"
  651. depends on NFSD_V3
  652. select NFSD_V2_ACL
  653. help
  654. Solaris NFS servers support an auxiliary NFSv3 ACL protocol that
  655. never became an official part of the NFS version 3 protocol.
  656. This protocol extension allows applications on NFS clients to
  657. manipulate POSIX Access Control Lists on files residing on NFS
  658. servers. NFS servers enforce POSIX ACLs on local files whether
  659. this protocol is available or not.
  660. This option enables support in your system's NFS server for the
  661. NFSv3 ACL protocol extension allowing NFS clients to manipulate
  662. POSIX ACLs on files exported by your system's NFS server. NFS
  663. clients which support the Solaris NFSv3 ACL protocol can then
  664. access and modify ACLs on your NFS server.
  665. To store ACLs on your NFS server, you also need to enable ACL-
  666. related CONFIG options for your local file systems of choice.
  667. If unsure, say N.
  668. config NFSD_V4
  669. bool "NFS server support for NFS version 4 (EXPERIMENTAL)"
  670. depends on NFSD && PROC_FS && EXPERIMENTAL
  671. select NFSD_V3
  672. select FS_POSIX_ACL
  673. select RPCSEC_GSS_KRB5
  674. help
  675. This option enables support in your system's NFS server for
  676. version 4 of the NFS protocol (RFC 3530).
  677. To export files using NFSv4, you need to install additional user
  678. space programs which can be found in the Linux nfs-utils package,
  679. available from http://linux-nfs.org/.
  680. If unsure, say N.
  681. config LOCKD
  682. tristate
  683. config LOCKD_V4
  684. bool
  685. depends on NFSD_V3 || NFS_V3
  686. default y
  687. config EXPORTFS
  688. tristate
  689. config NFS_ACL_SUPPORT
  690. tristate
  691. select FS_POSIX_ACL
  692. config NFS_COMMON
  693. bool
  694. depends on NFSD || NFS_FS
  695. default y
  696. config SUNRPC
  697. tristate
  698. config SUNRPC_GSS
  699. tristate
  700. config SUNRPC_XPRT_RDMA
  701. tristate
  702. depends on SUNRPC && INFINIBAND && EXPERIMENTAL
  703. default SUNRPC && INFINIBAND
  704. help
  705. This option enables an RPC client transport capability that
  706. allows the NFS client to mount servers via an RDMA-enabled
  707. transport.
  708. To compile RPC client RDMA transport support as a module,
  709. choose M here: the module will be called xprtrdma.
  710. If unsure, say N.
  711. config SUNRPC_REGISTER_V4
  712. bool "Register local RPC services via rpcbind v4 (EXPERIMENTAL)"
  713. depends on SUNRPC && EXPERIMENTAL
  714. default n
  715. help
  716. Sun added support for registering RPC services at an IPv6
  717. address by creating two new versions of the rpcbind protocol
  718. (RFC 1833).
  719. This option enables support in the kernel RPC server for
  720. registering kernel RPC services via version 4 of the rpcbind
  721. protocol. If you enable this option, you must run a portmapper
  722. daemon that supports rpcbind protocol version 4.
  723. Serving NFS over IPv6 from knfsd (the kernel's NFS server)
  724. requires that you enable this option and use a portmapper that
  725. supports rpcbind version 4.
  726. If unsure, say N to get traditional behavior (register kernel
  727. RPC services using only rpcbind version 2). Distributions
  728. using the legacy Linux portmapper daemon must say N here.
  729. config RPCSEC_GSS_KRB5
  730. tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
  731. depends on SUNRPC && EXPERIMENTAL
  732. select SUNRPC_GSS
  733. select CRYPTO
  734. select CRYPTO_MD5
  735. select CRYPTO_DES
  736. select CRYPTO_CBC
  737. help
  738. Choose Y here to enable Secure RPC using the Kerberos version 5
  739. GSS-API mechanism (RFC 1964).
  740. Secure RPC calls with Kerberos require an auxiliary user-space
  741. daemon which may be found in the Linux nfs-utils package
  742. available from http://linux-nfs.org/. In addition, user-space
  743. Kerberos support should be installed.
  744. If unsure, say N.
  745. config RPCSEC_GSS_SPKM3
  746. tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
  747. depends on SUNRPC && EXPERIMENTAL
  748. select SUNRPC_GSS
  749. select CRYPTO
  750. select CRYPTO_MD5
  751. select CRYPTO_DES
  752. select CRYPTO_CAST5
  753. select CRYPTO_CBC
  754. help
  755. Choose Y here to enable Secure RPC using the SPKM3 public key
  756. GSS-API mechansim (RFC 2025).
  757. Secure RPC calls with SPKM3 require an auxiliary userspace
  758. daemon which may be found in the Linux nfs-utils package
  759. available from http://linux-nfs.org/.
  760. If unsure, say N.
  761. config SMB_FS
  762. tristate "SMB file system support (OBSOLETE, please use CIFS)"
  763. depends on INET
  764. select NLS
  765. help
  766. SMB (Server Message Block) is the protocol Windows for Workgroups
  767. (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
  768. files and printers over local networks. Saying Y here allows you to
  769. mount their file systems (often called "shares" in this context) and
  770. access them just like any other Unix directory. Currently, this
  771. works only if the Windows machines use TCP/IP as the underlying
  772. transport protocol, and not NetBEUI. For details, read
  773. <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
  774. available from <http://www.tldp.org/docs.html#howto>.
  775. Note: if you just want your box to act as an SMB *server* and make
  776. files and printing services available to Windows clients (which need
  777. to have a TCP/IP stack), you don't need to say Y here; you can use
  778. the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
  779. for that.
  780. General information about how to connect Linux, Windows machines and
  781. Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
  782. To compile the SMB support as a module, choose M here:
  783. the module will be called smbfs. Most people say N, however.
  784. config SMB_NLS_DEFAULT
  785. bool "Use a default NLS"
  786. depends on SMB_FS
  787. help
  788. Enabling this will make smbfs use nls translations by default. You
  789. need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
  790. settings and you need to give the default nls for the SMB server as
  791. CONFIG_SMB_NLS_REMOTE.
  792. The nls settings can be changed at mount time, if your smbmount
  793. supports that, using the codepage and iocharset parameters.
  794. smbmount from samba 2.2.0 or later supports this.
  795. config SMB_NLS_REMOTE
  796. string "Default Remote NLS Option"
  797. depends on SMB_NLS_DEFAULT
  798. default "cp437"
  799. help
  800. This setting allows you to specify a default value for which
  801. codepage the server uses. If this field is left blank no
  802. translations will be done by default. The local codepage/charset
  803. default to CONFIG_NLS_DEFAULT.
  804. The nls settings can be changed at mount time, if your smbmount
  805. supports that, using the codepage and iocharset parameters.
  806. smbmount from samba 2.2.0 or later supports this.
  807. source "fs/cifs/Kconfig"
  808. config NCP_FS
  809. tristate "NCP file system support (to mount NetWare volumes)"
  810. depends on IPX!=n || INET
  811. help
  812. NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
  813. used by Novell NetWare clients to talk to file servers. It is to
  814. IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
  815. to mount NetWare file server volumes and to access them just like
  816. any other Unix directory. For details, please read the file
  817. <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
  818. the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
  819. You do not have to say Y here if you want your Linux box to act as a
  820. file *server* for Novell NetWare clients.
  821. General information about how to connect Linux, Windows machines and
  822. Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
  823. To compile this as a module, choose M here: the module will be called
  824. ncpfs. Say N unless you are connected to a Novell network.
  825. source "fs/ncpfs/Kconfig"
  826. config CODA_FS
  827. tristate "Coda file system support (advanced network fs)"
  828. depends on INET
  829. help
  830. Coda is an advanced network file system, similar to NFS in that it
  831. enables you to mount file systems of a remote server and access them
  832. with regular Unix commands as if they were sitting on your hard
  833. disk. Coda has several advantages over NFS: support for
  834. disconnected operation (e.g. for laptops), read/write server
  835. replication, security model for authentication and encryption,
  836. persistent client caches and write back caching.
  837. If you say Y here, your Linux box will be able to act as a Coda
  838. *client*. You will need user level code as well, both for the
  839. client and server. Servers are currently user level, i.e. they need
  840. no kernel support. Please read
  841. <file:Documentation/filesystems/coda.txt> and check out the Coda
  842. home page <http://www.coda.cs.cmu.edu/>.
  843. To compile the coda client support as a module, choose M here: the
  844. module will be called coda.
  845. config AFS_FS
  846. tristate "Andrew File System support (AFS) (EXPERIMENTAL)"
  847. depends on INET && EXPERIMENTAL
  848. select AF_RXRPC
  849. help
  850. If you say Y here, you will get an experimental Andrew File System
  851. driver. It currently only supports unsecured read-only AFS access.
  852. See <file:Documentation/filesystems/afs.txt> for more information.
  853. If unsure, say N.
  854. config AFS_DEBUG
  855. bool "AFS dynamic debugging"
  856. depends on AFS_FS
  857. help
  858. Say Y here to make runtime controllable debugging messages appear.
  859. See <file:Documentation/filesystems/afs.txt> for more information.
  860. If unsure, say N.
  861. config 9P_FS
  862. tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
  863. depends on INET && NET_9P && EXPERIMENTAL
  864. help
  865. If you say Y here, you will get experimental support for
  866. Plan 9 resource sharing via the 9P2000 protocol.
  867. See <http://v9fs.sf.net> for more information.
  868. If unsure, say N.
  869. endif # NETWORK_FILESYSTEMS
  870. if BLOCK
  871. menu "Partition Types"
  872. source "fs/partitions/Kconfig"
  873. endmenu
  874. endif
  875. source "fs/nls/Kconfig"
  876. source "fs/dlm/Kconfig"
  877. endmenu