2 # File system configuration
9 source "fs/ext2/Kconfig"
10 source "fs/ext3/Kconfig"
11 source "fs/ext4/Kconfig"
16 depends on EXT2_FS_XIP
19 source "fs/jbd/Kconfig"
20 source "fs/jbd2/Kconfig"
23 # Meta block cache for Extended Attributes (ext2/ext3/ext4)
25 depends on EXT2_FS_XATTR || EXT3_FS_XATTR || EXT4_FS_XATTR
26 default y if EXT2_FS=y || EXT3_FS=y || EXT4_FS=y
27 default m if EXT2_FS=m || EXT3_FS=m || EXT4_FS=m
30 tristate "Reiserfs support"
32 Stores not just filenames but the files themselves in a balanced
33 tree. Uses journalling.
35 Balanced trees are more efficient than traditional file system
36 architectural foundations.
38 In general, ReiserFS is as fast as ext2, but is very efficient with
39 large directories and small files. Additional patches are needed
40 for NFS and quotas, please see <http://www.namesys.com/> for links.
42 It is more easily extended to have features currently found in
43 database and keyword search systems than block allocation based file
44 systems are. The next version will be so extended, and will support
45 plugins consistent with our motto ``It takes more than a license to
46 make source code open.''
48 Read <http://www.namesys.com/> to learn more about reiserfs.
50 Sponsored by Threshold Networks, Emusic.com, and Bigstorage.com.
52 If you like it, you can pay us to add new features to it that you
53 need, buy a support contract, or pay us to port it to another OS.
56 bool "Enable reiserfs debug mode"
57 depends on REISERFS_FS
59 If you set this to Y, then ReiserFS will perform every check it can
60 possibly imagine of its internal consistency throughout its
61 operation. It will also go substantially slower. More than once we
62 have forgotten that this was on, and then gone despondent over the
63 latest benchmarks.:-) Use of this option allows our team to go all
64 out in checking for consistency when debugging without fear of its
65 effect on end users. If you are on the verge of sending in a bug
66 report, say Y and you might get a useful error message. Almost
67 everyone should say N.
69 config REISERFS_PROC_INFO
70 bool "Stats in /proc/fs/reiserfs"
71 depends on REISERFS_FS && PROC_FS
73 Create under /proc/fs/reiserfs a hierarchy of files, displaying
74 various ReiserFS statistics and internal data at the expense of
75 making your kernel or module slightly larger (+8 KB). This also
76 increases the amount of kernel memory required for each mount.
77 Almost everyone but ReiserFS developers and people fine-tuning
78 reiserfs or tracing problems should say N.
80 config REISERFS_FS_XATTR
81 bool "ReiserFS extended attributes"
82 depends on REISERFS_FS
84 Extended attributes are name:value pairs associated with inodes by
85 the kernel or by users (see the attr(5) manual page, or visit
86 <http://acl.bestbits.at/> for details).
90 config REISERFS_FS_POSIX_ACL
91 bool "ReiserFS POSIX Access Control Lists"
92 depends on REISERFS_FS_XATTR
95 Posix Access Control Lists (ACLs) support permissions for users and
96 groups beyond the owner/group/world scheme.
98 To learn more about Access Control Lists, visit the Posix ACLs for
99 Linux website <http://acl.bestbits.at/>.
101 If you don't know what Access Control Lists are, say N
103 config REISERFS_FS_SECURITY
104 bool "ReiserFS Security Labels"
105 depends on REISERFS_FS_XATTR
107 Security labels support alternative access control models
108 implemented by security modules like SELinux. This option
109 enables an extended attribute handler for file security
110 labels in the ReiserFS filesystem.
112 If you are not using a security module that requires using
113 extended attributes for file security labels, say N.
116 tristate "JFS filesystem support"
119 This is a port of IBM's Journaled Filesystem . More information is
120 available in the file <file:Documentation/filesystems/jfs.txt>.
122 If you do not intend to use the JFS filesystem, say N.
125 bool "JFS POSIX Access Control Lists"
129 Posix Access Control Lists (ACLs) support permissions for users and
130 groups beyond the owner/group/world scheme.
132 To learn more about Access Control Lists, visit the Posix ACLs for
133 Linux website <http://acl.bestbits.at/>.
135 If you don't know what Access Control Lists are, say N
138 bool "JFS Security Labels"
141 Security labels support alternative access control models
142 implemented by security modules like SELinux. This option
143 enables an extended attribute handler for file security
144 labels in the jfs filesystem.
146 If you are not using a security module that requires using
147 extended attributes for file security labels, say N.
153 If you are experiencing any problems with the JFS filesystem, say
154 Y here. This will result in additional debugging messages to be
155 written to the system log. Under normal circumstances, this
156 results in very little overhead.
158 config JFS_STATISTICS
159 bool "JFS statistics"
162 Enabling this option will cause statistics from the JFS file system
163 to be made available to the user in the /proc/fs/jfs/ directory.
166 # Posix ACL utility routines (for now, only ext2/ext3/jfs/reiserfs/nfs4)
168 # NOTE: you can implement Posix ACLs without these helpers (XFS does).
169 # Never use this symbol for ifdefs.
175 bool "Enable POSIX file locking API" if EMBEDDED
178 This option enables standard file locking support, required
179 for filesystems like NFS and for the flock() system
180 call. Disabling this option saves about 11k.
182 source "fs/xfs/Kconfig"
183 source "fs/gfs2/Kconfig"
186 tristate "OCFS2 file system support"
187 depends on NET && SYSFS
192 OCFS2 is a general purpose extent based shared disk cluster file
193 system with many similarities to ext3. It supports 64 bit inode
194 numbers, and has automatically extending metadata groups which may
195 also make it attractive for non-clustered use.
197 You'll want to install the ocfs2-tools package in order to at least
200 Project web page: http://oss.oracle.com/projects/ocfs2
201 Tools web page: http://oss.oracle.com/projects/ocfs2-tools
202 OCFS2 mailing lists: http://oss.oracle.com/projects/ocfs2/mailman/
204 For more information on OCFS2, see the file
205 <file:Documentation/filesystems/ocfs2.txt>.
208 tristate "O2CB Kernelspace Clustering"
212 OCFS2 includes a simple kernelspace clustering package, the OCFS2
213 Cluster Base. It only requires a very small userspace component
214 to configure it. This comes with the standard ocfs2-tools package.
215 O2CB is limited to maintaining a cluster for OCFS2 file systems.
216 It cannot manage any other cluster applications.
218 It is always safe to say Y here, as the clustering method is
221 config OCFS2_FS_USERSPACE_CLUSTER
222 tristate "OCFS2 Userspace Clustering"
223 depends on OCFS2_FS && DLM
226 This option will allow OCFS2 to use userspace clustering services
227 in conjunction with the DLM in fs/dlm. If you are using a
228 userspace cluster manager, say Y here.
230 It is safe to say Y, as the clustering method is run-time
233 config OCFS2_FS_STATS
234 bool "OCFS2 statistics"
238 This option allows some fs statistics to be captured. Enabling
239 this option may increase the memory consumption.
241 config OCFS2_DEBUG_MASKLOG
242 bool "OCFS2 logging support"
246 The ocfs2 filesystem has an extensive logging system. The system
247 allows selection of events to log via files in /sys/o2cb/logmask/.
248 This option will enlarge your kernel, but it allows debugging of
249 ocfs2 filesystem issues.
251 config OCFS2_DEBUG_FS
252 bool "OCFS2 expensive checks"
256 This option will enable expensive consistency checks. Enable
257 this option for debugging only as it is likely to decrease
258 performance of the filesystem.
260 config OCFS2_COMPAT_JBD
261 bool "Use JBD for compatibility"
266 The ocfs2 filesystem now uses JBD2 for its journalling. JBD2
267 is backwards compatible with JBD. It is safe to say N here.
268 However, if you really want to use the original JBD, say Y here.
273 bool "Dnotify support"
276 Dnotify is a directory-based per-fd file change notification system
277 that uses signals to communicate events to user-space. There exist
278 superior alternatives, but some applications may still rely on
284 bool "Inotify file change notification support"
287 Say Y here to enable inotify support. Inotify is a file change
288 notification system and a replacement for dnotify. Inotify fixes
289 numerous shortcomings in dnotify and introduces several new features
290 including multiple file events, one-shot support, and unmount
293 For more information, see <file:Documentation/filesystems/inotify.txt>
298 bool "Inotify support for userspace"
302 Say Y here to enable inotify support for userspace, including the
303 associated system calls. Inotify allows monitoring of both files and
304 directories via a single open fd. Events are read from the file
305 descriptor, which is also select()- and poll()-able.
307 For more information, see <file:Documentation/filesystems/inotify.txt>
314 If you say Y here, you will be able to set per user limits for disk
315 usage (also called disk quotas). Currently, it works for the
316 ext2, ext3, and reiserfs file system. ext3 also supports journalled
317 quotas for which you don't need to run quotacheck(8) after an unclean
319 For further details, read the Quota mini-HOWTO, available from
320 <http://www.tldp.org/docs.html#howto>, or the documentation provided
321 with the quota tools. Probably the quota support is only useful for
322 multi user systems. If unsure, say N.
324 config QUOTA_NETLINK_INTERFACE
325 bool "Report quota messages through netlink interface"
326 depends on QUOTA && NET
328 If you say Y here, quota warnings (about exceeding softlimit, reaching
329 hardlimit, etc.) will be reported through netlink interface. If unsure,
332 config PRINT_QUOTA_WARNING
333 bool "Print quota warnings to console (OBSOLETE)"
337 If you say Y here, quota warnings (about exceeding softlimit, reaching
338 hardlimit, etc.) will be printed to the process' controlling terminal.
339 Note that this behavior is currently deprecated and may go away in
340 future. Please use notification via netlink socket instead.
343 tristate "Old quota format support"
346 This quota format was (is) used by kernels earlier than 2.4.22. If
347 you have quota working and you don't want to convert to new quota
351 tristate "Quota format v2 support"
354 This quota format allows using quotas with 32-bit UIDs/GIDs. If you
355 need this functionality say Y here.
359 depends on XFS_QUOTA || QUOTA
363 tristate "Kernel automounter support"
365 The automounter is a tool to automatically mount remote file systems
366 on demand. This implementation is partially kernel-based to reduce
367 overhead in the already-mounted case; this is unlike the BSD
368 automounter (amd), which is a pure user space daemon.
370 To use the automounter you need the user-space tools from the autofs
371 package; you can find the location in <file:Documentation/Changes>.
372 You also want to answer Y to "NFS file system support", below.
374 If you want to use the newer version of the automounter with more
375 features, say N here and say Y to "Kernel automounter v4 support",
378 To compile this support as a module, choose M here: the module will be
381 If you are not a part of a fairly large, distributed network, you
382 probably do not need an automounter, and can say N here.
385 tristate "Kernel automounter version 4 support (also supports v3)"
387 The automounter is a tool to automatically mount remote file systems
388 on demand. This implementation is partially kernel-based to reduce
389 overhead in the already-mounted case; this is unlike the BSD
390 automounter (amd), which is a pure user space daemon.
392 To use the automounter you need the user-space tools from
393 <ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4/>; you also
394 want to answer Y to "NFS file system support", below.
396 To compile this support as a module, choose M here: the module will be
397 called autofs4. You will need to add "alias autofs autofs4" to your
398 modules configuration file.
400 If you are not a part of a fairly large, distributed network or
401 don't have a laptop which needs to dynamically reconfigure to the
402 local network, you probably do not need an automounter, and can say
406 tristate "FUSE (Filesystem in Userspace) support"
408 With FUSE it is possible to implement a fully functional filesystem
409 in a userspace program.
411 There's also companion library: libfuse. This library along with
412 utilities is available from the FUSE homepage:
413 <http://fuse.sourceforge.net/>
415 See <file:Documentation/filesystems/fuse.txt> for more information.
416 See <file:Documentation/Changes> for needed library/utility version.
418 If you want to develop a userspace FS, or if you want to use
419 a filesystem based on FUSE, answer Y or M.
426 menu "CD-ROM/DVD Filesystems"
429 tristate "ISO 9660 CDROM file system support"
431 This is the standard file system used on CD-ROMs. It was previously
432 known as "High Sierra File System" and is called "hsfs" on other
433 Unix systems. The so-called Rock-Ridge extensions which allow for
434 long Unix filenames and symbolic links are also supported by this
435 driver. If you have a CD-ROM drive and want to do more with it than
436 just listen to audio CDs and watch its LEDs, say Y (and read
437 <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO,
438 available from <http://www.tldp.org/docs.html#howto>), thereby
439 enlarging your kernel by about 27 KB; otherwise say N.
441 To compile this file system support as a module, choose M here: the
442 module will be called isofs.
445 bool "Microsoft Joliet CDROM extensions"
446 depends on ISO9660_FS
449 Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system
450 which allows for long filenames in unicode format (unicode is the
451 new 16 bit character code, successor to ASCII, which encodes the
452 characters of almost all languages of the world; see
453 <http://www.unicode.org/> for more information). Say Y here if you
454 want to be able to read Joliet CD-ROMs under Linux.
457 bool "Transparent decompression extension"
458 depends on ISO9660_FS
461 This is a Linux-specific extension to RockRidge which lets you store
462 data in compressed form on a CD-ROM and have it transparently
463 decompressed when the CD-ROM is accessed. See
464 <http://www.kernel.org/pub/linux/utils/fs/zisofs/> for the tools
465 necessary to create such a filesystem. Say Y here if you want to be
466 able to read such compressed CD-ROMs.
469 tristate "UDF file system support"
472 This is the new file system used on some CD-ROMs and DVDs. Say Y if
473 you intend to mount DVD discs or CDRW's written in packet mode, or
474 if written to by other UDF utilities, such as DirectCD.
475 Please read <file:Documentation/filesystems/udf.txt>.
477 To compile this file system support as a module, choose M here: the
478 module will be called udf.
485 depends on (UDF_FS=m && NLS) || (UDF_FS=y && NLS=y)
491 menu "DOS/FAT/NT Filesystems"
497 If you want to use one of the FAT-based file systems (the MS-DOS and
498 VFAT (Windows 95) file systems), then you must say Y or M here
499 to include FAT support. You will then be able to mount partitions or
500 diskettes with FAT-based file systems and transparently access the
501 files on them, i.e. MSDOS files will look and behave just like all
504 This FAT support is not a file system in itself, it only provides
505 the foundation for the other file systems. You will have to say Y or
506 M to at least one of "MSDOS fs support" or "VFAT fs support" in
507 order to make use of it.
509 Another way to read and write MSDOS floppies and hard drive
510 partitions from within Linux (but not transparently) is with the
511 mtools ("man mtools") program suite. You don't need to say Y here in
514 If you need to move large files on floppies between a DOS and a
515 Linux box, say Y here, mount the floppy under Linux with an MSDOS
516 file system and use GNU tar's M option. GNU tar is a program
517 available for Unix and DOS ("man tar" or "info tar").
519 The FAT support will enlarge your kernel by about 37 KB. If unsure,
522 To compile this as a module, choose M here: the module will be called
523 fat. Note that if you compile the FAT support as a module, you
524 cannot compile any of the FAT-based file systems into the kernel
525 -- they will have to be modules as well.
528 tristate "MSDOS fs support"
531 This allows you to mount MSDOS partitions of your hard drive (unless
532 they are compressed; to access compressed MSDOS partitions under
533 Linux, you can either use the DOS emulator DOSEMU, described in the
534 DOSEMU-HOWTO, available from
535 <http://www.tldp.org/docs.html#howto>, or try dmsdosfs in
536 <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you
537 intend to use dosemu with a non-compressed MSDOS partition, say Y
538 here) and MSDOS floppies. This means that file access becomes
539 transparent, i.e. the MSDOS files look and behave just like all
542 If you have Windows 95 or Windows NT installed on your MSDOS
543 partitions, you should use the VFAT file system (say Y to "VFAT fs
544 support" below), or you will not be able to see the long filenames
545 generated by Windows 95 / Windows NT.
547 This option will enlarge your kernel by about 7 KB. If unsure,
548 answer Y. This will only work if you said Y to "DOS FAT fs support"
549 as well. To compile this as a module, choose M here: the module will
553 tristate "VFAT (Windows-95) fs support"
556 This option provides support for normal Windows file systems with
557 long filenames. That includes non-compressed FAT-based file systems
558 used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
559 programs from the mtools package.
561 The VFAT support enlarges your kernel by about 10 KB and it only
562 works if you said Y to the "DOS FAT fs support" above. Please read
563 the file <file:Documentation/filesystems/vfat.txt> for details. If
566 To compile this as a module, choose M here: the module will be called
569 config FAT_DEFAULT_CODEPAGE
570 int "Default codepage for FAT"
571 depends on MSDOS_FS || VFAT_FS
574 This option should be set to the codepage of your FAT filesystems.
575 It can be overridden with the "codepage" mount option.
576 See <file:Documentation/filesystems/vfat.txt> for more information.
578 config FAT_DEFAULT_IOCHARSET
579 string "Default iocharset for FAT"
583 Set this to the default input/output character set you'd
584 like FAT to use. It should probably match the character set
585 that most of your FAT filesystems use, and can be overridden
586 with the "iocharset" mount option for FAT filesystems.
587 Note that "utf8" is not recommended for FAT filesystems.
588 If unsure, you shouldn't set "utf8" here.
589 See <file:Documentation/filesystems/vfat.txt> for more information.
592 tristate "NTFS file system support"
595 NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003.
597 Saying Y or M here enables read support. There is partial, but
598 safe, write support available. For write support you must also
599 say Y to "NTFS write support" below.
601 There are also a number of user-space tools available, called
602 ntfsprogs. These include ntfsundelete and ntfsresize, that work
603 without NTFS support enabled in the kernel.
605 This is a rewrite from scratch of Linux NTFS support and replaced
606 the old NTFS code starting with Linux 2.5.11. A backport to
607 the Linux 2.4 kernel series is separately available as a patch
608 from the project web site.
610 For more information see <file:Documentation/filesystems/ntfs.txt>
611 and <http://www.linux-ntfs.org/>.
613 To compile this file system support as a module, choose M here: the
614 module will be called ntfs.
616 If you are not using Windows NT, 2000, XP or 2003 in addition to
617 Linux on your computer it is safe to say N.
620 bool "NTFS debugging support"
623 If you are experiencing any problems with the NTFS file system, say
624 Y here. This will result in additional consistency checks to be
625 performed by the driver as well as additional debugging messages to
626 be written to the system log. Note that debugging messages are
627 disabled by default. To enable them, supply the option debug_msgs=1
628 at the kernel command line when booting the kernel or as an option
629 to insmod when loading the ntfs module. Once the driver is active,
630 you can enable debugging messages by doing (as root):
631 echo 1 > /proc/sys/fs/ntfs-debug
632 Replacing the "1" with "0" would disable debug messages.
634 If you leave debugging messages disabled, this results in little
635 overhead, but enabling debug messages results in very significant
636 slowdown of the system.
638 When reporting bugs, please try to have available a full dump of
639 debugging messages while the misbehaviour was occurring.
642 bool "NTFS write support"
645 This enables the partial, but safe, write support in the NTFS driver.
647 The only supported operation is overwriting existing files, without
648 changing the file length. No file or directory creation, deletion or
649 renaming is possible. Note only non-resident files can be written to
650 so you may find that some very small files (<500 bytes or so) cannot
653 While we cannot guarantee that it will not damage any data, we have
654 so far not received a single report where the driver would have
655 damaged someones data so we assume it is perfectly safe to use.
657 Note: While write support is safe in this version (a rewrite from
658 scratch of the NTFS support), it should be noted that the old NTFS
659 write support, included in Linux 2.5.10 and before (since 1997),
662 This is currently useful with TopologiLinux. TopologiLinux is run
663 on top of any DOS/Microsoft Windows system without partitioning your
664 hard disk. Unlike other Linux distributions TopologiLinux does not
665 need its own partition. For more information see
666 <http://topologi-linux.sourceforge.net/>
668 It is perfectly safe to say N here.
673 menu "Pseudo filesystems"
675 source "fs/proc/Kconfig"
678 bool "sysfs file system support" if EMBEDDED
681 The sysfs filesystem is a virtual filesystem that the kernel uses to
682 export internal kernel objects, their attributes, and their
683 relationships to one another.
685 Users can use sysfs to ascertain useful information about the running
686 kernel, such as the devices the kernel has discovered on each bus and
687 which driver each is bound to. sysfs can also be used to tune devices
688 and other kernel subsystems.
690 Some system agents rely on the information in sysfs to operate.
691 /sbin/hotplug uses device and object attributes in sysfs to assist in
692 delegating policy decisions, like persistently naming devices.
694 sysfs is currently used by the block subsystem to mount the root
695 partition. If sysfs is disabled you must specify the boot device on
696 the kernel boot command line via its major and minor numbers. For
697 example, "root=03:01" for /dev/hda1.
699 Designers of embedded systems may wish to say N here to conserve space.
702 bool "Virtual memory file system support (former shm fs)"
704 Tmpfs is a file system which keeps all files in virtual memory.
706 Everything in tmpfs is temporary in the sense that no files will be
707 created on your hard drive. The files live in memory and swap
708 space. If you unmount a tmpfs instance, everything stored therein is
711 See <file:Documentation/filesystems/tmpfs.txt> for details.
713 config TMPFS_POSIX_ACL
714 bool "Tmpfs POSIX Access Control Lists"
718 POSIX Access Control Lists (ACLs) support permissions for users and
719 groups beyond the owner/group/world scheme.
721 To learn more about Access Control Lists, visit the POSIX ACLs for
722 Linux website <http://acl.bestbits.at/>.
724 If you don't know what Access Control Lists are, say N.
727 bool "HugeTLB file system support"
728 depends on X86 || IA64 || PPC64 || SPARC64 || (SUPERH && MMU) || \
729 (S390 && 64BIT) || BROKEN
731 hugetlbfs is a filesystem backing for HugeTLB pages, based on
732 ramfs. For architectures that support it, say Y here and read
733 <file:Documentation/vm/hugetlbpage.txt> for details.
741 tristate "Userspace-driven configuration filesystem"
744 configfs is a ram-based filesystem that provides the converse
745 of sysfs's functionality. Where sysfs is a filesystem-based
746 view of kernel objects, configfs is a filesystem-based manager
747 of kernel objects, or config_items.
749 Both sysfs and configfs can and should exist together on the
750 same system. One is not a replacement for the other.
754 menu "Miscellaneous filesystems"
757 tristate "ADFS file system support (EXPERIMENTAL)"
758 depends on BLOCK && EXPERIMENTAL
760 The Acorn Disc Filing System is the standard file system of the
761 RiscOS operating system which runs on Acorn's ARM-based Risc PC
762 systems and the Acorn Archimedes range of machines. If you say Y
763 here, Linux will be able to read from ADFS partitions on hard drives
764 and from ADFS-formatted floppy discs. If you also want to be able to
765 write to those devices, say Y to "ADFS write support" below.
767 The ADFS partition should be the first partition (i.e.,
768 /dev/[hs]d?1) on each of your drives. Please read the file
769 <file:Documentation/filesystems/adfs.txt> for further details.
771 To compile this code as a module, choose M here: the module will be
777 bool "ADFS write support (DANGEROUS)"
780 If you say Y here, you will be able to write to ADFS partitions on
781 hard drives and ADFS-formatted floppy disks. This is experimental
782 codes, so if you're unsure, say N.
785 tristate "Amiga FFS file system support (EXPERIMENTAL)"
786 depends on BLOCK && EXPERIMENTAL
788 The Fast File System (FFS) is the common file system used on hard
789 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
790 if you want to be able to read and write files from and to an Amiga
791 FFS partition on your hard drive. Amiga floppies however cannot be
792 read with this driver due to an incompatibility of the floppy
793 controller used in an Amiga and the standard floppy controller in
794 PCs and workstations. Read <file:Documentation/filesystems/affs.txt>
795 and <file:fs/affs/Changes>.
797 With this driver you can also mount disk files used by Bernd
798 Schmidt's Un*X Amiga Emulator
799 (<http://www.freiburg.linux.de/~uae/>).
800 If you want to do this, you will also need to say Y or M to "Loop
801 device support", above.
803 To compile this file system support as a module, choose M here: the
804 module will be called affs. If unsure, say N.
807 tristate "eCrypt filesystem layer support (EXPERIMENTAL)"
808 depends on EXPERIMENTAL && KEYS && CRYPTO && NET
810 Encrypted filesystem that operates on the VFS layer. See
811 <file:Documentation/filesystems/ecryptfs.txt> to learn more about
812 eCryptfs. Userspace components are required and can be
813 obtained from <http://ecryptfs.sf.net>.
815 To compile this file system support as a module, choose M here: the
816 module will be called ecryptfs.
819 tristate "Apple Macintosh file system support (EXPERIMENTAL)"
820 depends on BLOCK && EXPERIMENTAL
823 If you say Y here, you will be able to mount Macintosh-formatted
824 floppy disks and hard drive partitions with full read-write access.
825 Please read <file:Documentation/filesystems/hfs.txt> to learn about
826 the available mount options.
828 To compile this file system support as a module, choose M here: the
829 module will be called hfs.
832 tristate "Apple Extended HFS file system support"
837 If you say Y here, you will be able to mount extended format
838 Macintosh-formatted hard drive partitions with full read-write access.
840 This file system is often called HFS+ and was introduced with
841 MacOS 8. It includes all Mac specific filesystem data such as
842 data forks and creator codes, but it also has several UNIX
843 style features such as file ownership and permissions.
846 tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)"
847 depends on BLOCK && EXPERIMENTAL
850 The BeOS File System (BeFS) is the native file system of Be, Inc's
851 BeOS. Notable features include support for arbitrary attributes
852 on files and directories, and database-like indices on selected
853 attributes. (Also note that this driver doesn't make those features
854 available at this time). It is a 64 bit filesystem, so it supports
855 extremely large volumes and files.
857 If you use this filesystem, you should also say Y to at least one
858 of the NLS (native language support) options below.
860 If you don't know what this is about, say N.
862 To compile this as a module, choose M here: the module will be
869 If you say Y here, you can use the 'debug' mount option to enable
870 debugging output from the driver.
873 tristate "BFS file system support (EXPERIMENTAL)"
874 depends on BLOCK && EXPERIMENTAL
876 Boot File System (BFS) is a file system used under SCO UnixWare to
877 allow the bootloader access to the kernel image and other important
878 files during the boot process. It is usually mounted under /stand
879 and corresponds to the slice marked as "STAND" in the UnixWare
880 partition. You should say Y if you want to read or write the files
881 on your /stand slice from within Linux. You then also need to say Y
882 to "UnixWare slices support", below. More information about the BFS
883 file system is contained in the file
884 <file:Documentation/filesystems/bfs.txt>.
886 If you don't know what this is about, say N.
888 To compile this as a module, choose M here: the module will be called
889 bfs. Note that the file system of your root partition (the one
890 containing the directory /) cannot be compiled as a module.
895 tristate "EFS file system support (read only) (EXPERIMENTAL)"
896 depends on BLOCK && EXPERIMENTAL
898 EFS is an older file system used for non-ISO9660 CD-ROMs and hard
899 disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
900 uses the XFS file system for hard disk partitions however).
902 This implementation only offers read-only access. If you don't know
903 what all this is about, it's safe to say N. For more information
904 about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
906 To compile the EFS file system support as a module, choose M here: the
907 module will be called efs.
909 source "fs/jffs2/Kconfig"
910 # UBIFS File system configuration
911 source "fs/ubifs/Kconfig"
914 tristate "Compressed ROM file system support (cramfs)"
918 Saying Y here includes support for CramFs (Compressed ROM File
919 System). CramFs is designed to be a simple, small, and compressed
920 file system for ROM based embedded systems. CramFs is read-only,
921 limited to 256MB file systems (with 16MB files), and doesn't support
922 16/32 bits uid/gid, hard links and timestamps.
924 See <file:Documentation/filesystems/cramfs.txt> and
925 <file:fs/cramfs/README> for further information.
927 To compile this as a module, choose M here: the module will be called
928 cramfs. Note that the root file system (the one containing the
929 directory /) cannot be compiled as a module.
934 tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
937 FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
938 file system format. VERITAS VxFS(TM) is the standard file system
939 of SCO UnixWare (and possibly others) and optionally available
940 for Sunsoft Solaris, HP-UX and many other operating systems.
941 Currently only readonly access is supported.
943 NOTE: the file system type as used by mount(1), mount(2) and
944 fstab(5) is 'vxfs' as it describes the file system format, not
947 To compile this as a module, choose M here: the module will be
948 called freevxfs. If unsure, say N.
951 tristate "Minix file system support"
954 Minix is a simple operating system used in many classes about OS's.
955 The minix file system (method to organize files on a hard disk
956 partition or a floppy disk) was the original file system for Linux,
957 but has been superseded by the second extended file system ext2fs.
958 You don't want to use the minix file system on your hard disk
959 because of certain built-in restrictions, but it is sometimes found
960 on older Linux floppy disks. This option will enlarge your kernel
961 by about 28 KB. If unsure, say N.
963 To compile this file system support as a module, choose M here: the
964 module will be called minix. Note that the file system of your root
965 partition (the one containing the directory /) cannot be compiled as
969 tristate "SonicBlue Optimized MPEG File System support"
973 This is the proprietary file system used by the Rio Karma music
974 player and ReplayTV DVR. Despite the name, this filesystem is not
975 more efficient than a standard FS for MPEG files, in fact likely
976 the opposite is true. Say Y if you have either of these devices
977 and wish to mount its disk.
979 To compile this file system support as a module, choose M here: the
980 module will be called omfs. If unsure, say N.
983 tristate "OS/2 HPFS file system support"
986 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
987 is the file system used for organizing files on OS/2 hard disk
988 partitions. Say Y if you want to be able to read files from and
989 write files to an OS/2 HPFS partition on your hard drive. OS/2
990 floppies however are in regular MSDOS format, so you don't need this
991 option in order to be able to read them. Read
992 <file:Documentation/filesystems/hpfs.txt>.
994 To compile this file system support as a module, choose M here: the
995 module will be called hpfs. If unsure, say N.
999 tristate "QNX4 file system support (read only)"
1002 This is the file system used by the real-time operating systems
1003 QNX 4 and QNX 6 (the latter is also called QNX RTP).
1004 Further information is available at <http://www.qnx.com/>.
1005 Say Y if you intend to mount QNX hard disks or floppies.
1006 Unless you say Y to "QNX4FS read-write support" below, you will
1007 only be able to read these file systems.
1009 To compile this file system support as a module, choose M here: the
1010 module will be called qnx4.
1012 If you don't know whether you need it, then you don't need it:
1016 bool "QNX4FS write support (DANGEROUS)"
1017 depends on QNX4FS_FS && EXPERIMENTAL && BROKEN
1019 Say Y if you want to test write support for QNX4 file systems.
1021 It's currently broken, so for now:
1025 tristate "ROM file system support"
1028 This is a very small read-only file system mainly intended for
1029 initial ram disks of installation disks, but it could be used for
1030 other read-only media as well. Read
1031 <file:Documentation/filesystems/romfs.txt> for details.
1033 To compile this file system support as a module, choose M here: the
1034 module will be called romfs. Note that the file system of your
1035 root partition (the one containing the directory /) cannot be a
1038 If you don't know whether you need it, then you don't need it:
1043 tristate "System V/Xenix/V7/Coherent file system support"
1046 SCO, Xenix and Coherent are commercial Unix systems for Intel
1047 machines, and Version 7 was used on the DEC PDP-11. Saying Y
1048 here would allow you to read from their floppies and hard disk
1051 If you have floppies or hard disk partitions like that, it is likely
1052 that they contain binaries from those other Unix systems; in order
1053 to run these binaries, you will want to install linux-abi which is
1054 a set of kernel modules that lets you run SCO, Xenix, Wyse,
1055 UnixWare, Dell Unix and System V programs under Linux. It is
1056 available via FTP (user: ftp) from
1057 <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
1058 NOTE: that will work only for binaries from Intel-based systems;
1059 PDP ones will have to wait until somebody ports Linux to -11 ;-)
1061 If you only intend to mount files from some other Unix over the
1062 network using NFS, you don't need the System V file system support
1063 (but you need NFS file system support obviously).
1065 Note that this option is generally not needed for floppies, since a
1066 good portable way to transport files and directories between unixes
1067 (and even other operating systems) is given by the tar program ("man
1068 tar" or preferably "info tar"). Note also that this option has
1069 nothing whatsoever to do with the option "System V IPC". Read about
1070 the System V file system in
1071 <file:Documentation/filesystems/sysv-fs.txt>.
1072 Saying Y here will enlarge your kernel by about 27 KB.
1074 To compile this as a module, choose M here: the module will be called
1077 If you haven't heard about all of this before, it's safe to say N.
1081 tristate "UFS file system support (read only)"
1084 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
1085 OpenBSD and NeXTstep) use a file system called UFS. Some System V
1086 Unixes can create and mount hard disk partitions and diskettes using
1087 this file system as well. Saying Y here will allow you to read from
1088 these partitions; if you also want to write to them, say Y to the
1089 experimental "UFS file system write support", below. Please read the
1090 file <file:Documentation/filesystems/ufs.txt> for more information.
1092 The recently released UFS2 variant (used in FreeBSD 5.x) is
1093 READ-ONLY supported.
1095 Note that this option is generally not needed for floppies, since a
1096 good portable way to transport files and directories between unixes
1097 (and even other operating systems) is given by the tar program ("man
1098 tar" or preferably "info tar").
1100 When accessing NeXTstep files, you may need to convert them from the
1101 NeXT character set to the Latin1 character set; use the program
1102 recode ("info recode") for this purpose.
1104 To compile the UFS file system support as a module, choose M here: the
1105 module will be called ufs.
1107 If you haven't heard about all of this before, it's safe to say N.
1110 bool "UFS file system write support (DANGEROUS)"
1111 depends on UFS_FS && EXPERIMENTAL
1113 Say Y here if you want to try writing to UFS partitions. This is
1114 experimental, so you should back up your UFS partitions beforehand.
1117 bool "UFS debugging"
1120 If you are experiencing any problems with the UFS filesystem, say
1121 Y here. This will result in _many_ additional debugging messages to be
1122 written to the system log.
1126 menuconfig NETWORK_FILESYSTEMS
1127 bool "Network File Systems"
1131 Say Y here to get to see options for network filesystems and
1132 filesystem-related networking code, such as NFS daemon and
1133 RPCSEC security modules.
1135 This option alone does not add any kernel code.
1137 If you say N, all options in this submenu will be skipped and
1138 disabled; if unsure, say Y here.
1140 if NETWORK_FILESYSTEMS
1143 tristate "NFS client support"
1147 select NFS_ACL_SUPPORT if NFS_V3_ACL
1149 Choose Y here if you want to access files residing on other
1150 computers using Sun's Network File System protocol. To compile
1151 this file system support as a module, choose M here: the module
1154 To mount file systems exported by NFS servers, you also need to
1155 install the user space mount.nfs command which can be found in
1156 the Linux nfs-utils package, available from http://linux-nfs.org/.
1157 Information about using the mount command is available in the
1158 mount(8) man page. More detail about the Linux NFS client
1159 implementation is available via the nfs(5) man page.
1161 Below you can choose which versions of the NFS protocol are
1162 available in the kernel to mount NFS servers. Support for NFS
1163 version 2 (RFC 1094) is always available when NFS_FS is selected.
1165 To configure a system which mounts its root file system via NFS
1166 at boot time, say Y here, select "Kernel level IP
1167 autoconfiguration" in the NETWORK menu, and select "Root file
1168 system on NFS" below. You cannot compile this file system as a
1169 module in this case.
1174 bool "NFS client support for NFS version 3"
1177 This option enables support for version 3 of the NFS protocol
1178 (RFC 1813) in the kernel's NFS client.
1183 bool "NFS client support for the NFSv3 ACL protocol extension"
1186 Some NFS servers support an auxiliary NFSv3 ACL protocol that
1187 Sun added to Solaris but never became an official part of the
1188 NFS version 3 protocol. This protocol extension allows
1189 applications on NFS clients to manipulate POSIX Access Control
1190 Lists on files residing on NFS servers. NFS servers enforce
1191 ACLs on local files whether this protocol is available or not.
1193 Choose Y here if your NFS server supports the Solaris NFSv3 ACL
1194 protocol extension and you want your NFS client to allow
1195 applications to access and modify ACLs on files on the server.
1197 Most NFS servers don't support the Solaris NFSv3 ACL protocol
1198 extension. You can choose N here or specify the "noacl" mount
1199 option to prevent your NFS client from trying to use the NFSv3
1205 bool "NFS client support for NFS version 4 (EXPERIMENTAL)"
1206 depends on NFS_FS && EXPERIMENTAL
1207 select RPCSEC_GSS_KRB5
1209 This option enables support for version 4 of the NFS protocol
1210 (RFC 3530) in the kernel's NFS client.
1212 To mount NFS servers using NFSv4, you also need to install user
1213 space programs which can be found in the Linux nfs-utils package,
1214 available from http://linux-nfs.org/.
1219 bool "Root file system on NFS"
1220 depends on NFS_FS=y && IP_PNP
1222 If you want your system to mount its root file system via NFS,
1223 choose Y here. This is common practice for managing systems
1224 without local permanent storage. For details, read
1225 <file:Documentation/filesystems/nfsroot.txt>.
1227 Most people say N here.
1230 tristate "NFS server support"
1235 select NFS_ACL_SUPPORT if NFSD_V2_ACL
1237 Choose Y here if you want to allow other computers to access
1238 files residing on this system using Sun's Network File System
1239 protocol. To compile the NFS server support as a module,
1240 choose M here: the module will be called nfsd.
1242 You may choose to use a user-space NFS server instead, in which
1243 case you can choose N here.
1245 To export local file systems using NFS, you also need to install
1246 user space programs which can be found in the Linux nfs-utils
1247 package, available from http://linux-nfs.org/. More detail about
1248 the Linux NFS server implementation is available via the
1249 exports(5) man page.
1251 Below you can choose which versions of the NFS protocol are
1252 available to clients mounting the NFS server on this system.
1253 Support for NFS version 2 (RFC 1094) is always available when
1254 CONFIG_NFSD is selected.
1263 bool "NFS server support for NFS version 3"
1266 This option enables support in your system's NFS server for
1267 version 3 of the NFS protocol (RFC 1813).
1272 bool "NFS server support for the NFSv3 ACL protocol extension"
1276 Solaris NFS servers support an auxiliary NFSv3 ACL protocol that
1277 never became an official part of the NFS version 3 protocol.
1278 This protocol extension allows applications on NFS clients to
1279 manipulate POSIX Access Control Lists on files residing on NFS
1280 servers. NFS servers enforce POSIX ACLs on local files whether
1281 this protocol is available or not.
1283 This option enables support in your system's NFS server for the
1284 NFSv3 ACL protocol extension allowing NFS clients to manipulate
1285 POSIX ACLs on files exported by your system's NFS server. NFS
1286 clients which support the Solaris NFSv3 ACL protocol can then
1287 access and modify ACLs on your NFS server.
1289 To store ACLs on your NFS server, you also need to enable ACL-
1290 related CONFIG options for your local file systems of choice.
1295 bool "NFS server support for NFS version 4 (EXPERIMENTAL)"
1296 depends on NFSD && PROC_FS && EXPERIMENTAL
1299 select RPCSEC_GSS_KRB5
1301 This option enables support in your system's NFS server for
1302 version 4 of the NFS protocol (RFC 3530).
1304 To export files using NFSv4, you need to install additional user
1305 space programs which can be found in the Linux nfs-utils package,
1306 available from http://linux-nfs.org/.
1315 depends on NFSD_V3 || NFS_V3
1321 config NFS_ACL_SUPPORT
1327 depends on NFSD || NFS_FS
1336 config SUNRPC_XPRT_RDMA
1338 depends on SUNRPC && INFINIBAND && EXPERIMENTAL
1339 default SUNRPC && INFINIBAND
1341 This option enables an RPC client transport capability that
1342 allows the NFS client to mount servers via an RDMA-enabled
1345 To compile RPC client RDMA transport support as a module,
1346 choose M here: the module will be called xprtrdma.
1350 config SUNRPC_REGISTER_V4
1351 bool "Register local RPC services via rpcbind v4 (EXPERIMENTAL)"
1352 depends on SUNRPC && EXPERIMENTAL
1355 Sun added support for registering RPC services at an IPv6
1356 address by creating two new versions of the rpcbind protocol
1359 This option enables support in the kernel RPC server for
1360 registering kernel RPC services via version 4 of the rpcbind
1361 protocol. If you enable this option, you must run a portmapper
1362 daemon that supports rpcbind protocol version 4.
1364 Serving NFS over IPv6 from knfsd (the kernel's NFS server)
1365 requires that you enable this option and use a portmapper that
1366 supports rpcbind version 4.
1368 If unsure, say N to get traditional behavior (register kernel
1369 RPC services using only rpcbind version 2). Distributions
1370 using the legacy Linux portmapper daemon must say N here.
1372 config RPCSEC_GSS_KRB5
1373 tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
1374 depends on SUNRPC && EXPERIMENTAL
1381 Choose Y here to enable Secure RPC using the Kerberos version 5
1382 GSS-API mechanism (RFC 1964).
1384 Secure RPC calls with Kerberos require an auxiliary user-space
1385 daemon which may be found in the Linux nfs-utils package
1386 available from http://linux-nfs.org/. In addition, user-space
1387 Kerberos support should be installed.
1391 config RPCSEC_GSS_SPKM3
1392 tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
1393 depends on SUNRPC && EXPERIMENTAL
1401 Choose Y here to enable Secure RPC using the SPKM3 public key
1402 GSS-API mechansim (RFC 2025).
1404 Secure RPC calls with SPKM3 require an auxiliary userspace
1405 daemon which may be found in the Linux nfs-utils package
1406 available from http://linux-nfs.org/.
1411 tristate "SMB file system support (OBSOLETE, please use CIFS)"
1415 SMB (Server Message Block) is the protocol Windows for Workgroups
1416 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
1417 files and printers over local networks. Saying Y here allows you to
1418 mount their file systems (often called "shares" in this context) and
1419 access them just like any other Unix directory. Currently, this
1420 works only if the Windows machines use TCP/IP as the underlying
1421 transport protocol, and not NetBEUI. For details, read
1422 <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
1423 available from <http://www.tldp.org/docs.html#howto>.
1425 Note: if you just want your box to act as an SMB *server* and make
1426 files and printing services available to Windows clients (which need
1427 to have a TCP/IP stack), you don't need to say Y here; you can use
1428 the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
1431 General information about how to connect Linux, Windows machines and
1432 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1434 To compile the SMB support as a module, choose M here:
1435 the module will be called smbfs. Most people say N, however.
1437 config SMB_NLS_DEFAULT
1438 bool "Use a default NLS"
1441 Enabling this will make smbfs use nls translations by default. You
1442 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
1443 settings and you need to give the default nls for the SMB server as
1444 CONFIG_SMB_NLS_REMOTE.
1446 The nls settings can be changed at mount time, if your smbmount
1447 supports that, using the codepage and iocharset parameters.
1449 smbmount from samba 2.2.0 or later supports this.
1451 config SMB_NLS_REMOTE
1452 string "Default Remote NLS Option"
1453 depends on SMB_NLS_DEFAULT
1456 This setting allows you to specify a default value for which
1457 codepage the server uses. If this field is left blank no
1458 translations will be done by default. The local codepage/charset
1459 default to CONFIG_NLS_DEFAULT.
1461 The nls settings can be changed at mount time, if your smbmount
1462 supports that, using the codepage and iocharset parameters.
1464 smbmount from samba 2.2.0 or later supports this.
1466 source "fs/cifs/Kconfig"
1469 tristate "NCP file system support (to mount NetWare volumes)"
1470 depends on IPX!=n || INET
1472 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
1473 used by Novell NetWare clients to talk to file servers. It is to
1474 IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
1475 to mount NetWare file server volumes and to access them just like
1476 any other Unix directory. For details, please read the file
1477 <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
1478 the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
1480 You do not have to say Y here if you want your Linux box to act as a
1481 file *server* for Novell NetWare clients.
1483 General information about how to connect Linux, Windows machines and
1484 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1486 To compile this as a module, choose M here: the module will be called
1487 ncpfs. Say N unless you are connected to a Novell network.
1489 source "fs/ncpfs/Kconfig"
1492 tristate "Coda file system support (advanced network fs)"
1495 Coda is an advanced network file system, similar to NFS in that it
1496 enables you to mount file systems of a remote server and access them
1497 with regular Unix commands as if they were sitting on your hard
1498 disk. Coda has several advantages over NFS: support for
1499 disconnected operation (e.g. for laptops), read/write server
1500 replication, security model for authentication and encryption,
1501 persistent client caches and write back caching.
1503 If you say Y here, your Linux box will be able to act as a Coda
1504 *client*. You will need user level code as well, both for the
1505 client and server. Servers are currently user level, i.e. they need
1506 no kernel support. Please read
1507 <file:Documentation/filesystems/coda.txt> and check out the Coda
1508 home page <http://www.coda.cs.cmu.edu/>.
1510 To compile the coda client support as a module, choose M here: the
1511 module will be called coda.
1514 tristate "Andrew File System support (AFS) (EXPERIMENTAL)"
1515 depends on INET && EXPERIMENTAL
1518 If you say Y here, you will get an experimental Andrew File System
1519 driver. It currently only supports unsecured read-only AFS access.
1521 See <file:Documentation/filesystems/afs.txt> for more information.
1526 bool "AFS dynamic debugging"
1529 Say Y here to make runtime controllable debugging messages appear.
1531 See <file:Documentation/filesystems/afs.txt> for more information.
1536 tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
1537 depends on INET && NET_9P && EXPERIMENTAL
1539 If you say Y here, you will get experimental support for
1540 Plan 9 resource sharing via the 9P2000 protocol.
1542 See <http://v9fs.sf.net> for more information.
1546 endif # NETWORK_FILESYSTEMS
1549 menu "Partition Types"
1551 source "fs/partitions/Kconfig"
1556 source "fs/nls/Kconfig"
1557 source "fs/dlm/Kconfig"
git://ftp.safe.ca / safe / jmp / linux-2.6 / blob