Kconfig 47 KB

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