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 default y if EXT2_FS=y && EXT2_FS_XATTR
26 default y if EXT3_FS=y && EXT3_FS_XATTR
27 default y if EXT4_FS=y && EXT4_FS_XATTR
28 default m if EXT2_FS_XATTR || EXT3_FS_XATTR || EXT4_FS_XATTR
31 tristate "Reiserfs support"
33 Stores not just filenames but the files themselves in a balanced
34 tree. Uses journalling.
36 Balanced trees are more efficient than traditional file system
37 architectural foundations.
39 In general, ReiserFS is as fast as ext2, but is very efficient with
40 large directories and small files. Additional patches are needed
41 for NFS and quotas, please see <http://www.namesys.com/> for links.
43 It is more easily extended to have features currently found in
44 database and keyword search systems than block allocation based file
45 systems are. The next version will be so extended, and will support
46 plugins consistent with our motto ``It takes more than a license to
47 make source code open.''
49 Read <http://www.namesys.com/> to learn more about reiserfs.
51 Sponsored by Threshold Networks, Emusic.com, and Bigstorage.com.
53 If you like it, you can pay us to add new features to it that you
54 need, buy a support contract, or pay us to port it to another OS.
57 bool "Enable reiserfs debug mode"
58 depends on REISERFS_FS
60 If you set this to Y, then ReiserFS will perform every check it can
61 possibly imagine of its internal consistency throughout its
62 operation. It will also go substantially slower. More than once we
63 have forgotten that this was on, and then gone despondent over the
64 latest benchmarks.:-) Use of this option allows our team to go all
65 out in checking for consistency when debugging without fear of its
66 effect on end users. If you are on the verge of sending in a bug
67 report, say Y and you might get a useful error message. Almost
68 everyone should say N.
70 config REISERFS_PROC_INFO
71 bool "Stats in /proc/fs/reiserfs"
72 depends on REISERFS_FS && PROC_FS
74 Create under /proc/fs/reiserfs a hierarchy of files, displaying
75 various ReiserFS statistics and internal data at the expense of
76 making your kernel or module slightly larger (+8 KB). This also
77 increases the amount of kernel memory required for each mount.
78 Almost everyone but ReiserFS developers and people fine-tuning
79 reiserfs or tracing problems should say N.
81 config REISERFS_FS_XATTR
82 bool "ReiserFS extended attributes"
83 depends on REISERFS_FS
85 Extended attributes are name:value pairs associated with inodes by
86 the kernel or by users (see the attr(5) manual page, or visit
87 <http://acl.bestbits.at/> for details).
91 config REISERFS_FS_POSIX_ACL
92 bool "ReiserFS POSIX Access Control Lists"
93 depends on REISERFS_FS_XATTR
96 Posix Access Control Lists (ACLs) support permissions for users and
97 groups beyond the owner/group/world scheme.
99 To learn more about Access Control Lists, visit the Posix ACLs for
100 Linux website <http://acl.bestbits.at/>.
102 If you don't know what Access Control Lists are, say N
104 config REISERFS_FS_SECURITY
105 bool "ReiserFS Security Labels"
106 depends on REISERFS_FS_XATTR
108 Security labels support alternative access control models
109 implemented by security modules like SELinux. This option
110 enables an extended attribute handler for file security
111 labels in the ReiserFS filesystem.
113 If you are not using a security module that requires using
114 extended attributes for file security labels, say N.
117 tristate "JFS filesystem support"
120 This is a port of IBM's Journaled Filesystem . More information is
121 available in the file <file:Documentation/filesystems/jfs.txt>.
123 If you do not intend to use the JFS filesystem, say N.
126 bool "JFS POSIX Access Control Lists"
130 Posix Access Control Lists (ACLs) support permissions for users and
131 groups beyond the owner/group/world scheme.
133 To learn more about Access Control Lists, visit the Posix ACLs for
134 Linux website <http://acl.bestbits.at/>.
136 If you don't know what Access Control Lists are, say N
139 bool "JFS Security Labels"
142 Security labels support alternative access control models
143 implemented by security modules like SELinux. This option
144 enables an extended attribute handler for file security
145 labels in the jfs filesystem.
147 If you are not using a security module that requires using
148 extended attributes for file security labels, say N.
154 If you are experiencing any problems with the JFS filesystem, say
155 Y here. This will result in additional debugging messages to be
156 written to the system log. Under normal circumstances, this
157 results in very little overhead.
159 config JFS_STATISTICS
160 bool "JFS statistics"
163 Enabling this option will cause statistics from the JFS file system
164 to be made available to the user in the /proc/fs/jfs/ directory.
167 # Posix ACL utility routines (for now, only ext2/ext3/jfs/reiserfs/nfs4)
169 # NOTE: you can implement Posix ACLs without these helpers (XFS does).
170 # Never use this symbol for ifdefs.
176 bool "Enable POSIX file locking API" if EMBEDDED
179 This option enables standard file locking support, required
180 for filesystems like NFS and for the flock() system
181 call. Disabling this option saves about 11k.
183 source "fs/xfs/Kconfig"
184 source "fs/gfs2/Kconfig"
187 tristate "OCFS2 file system support"
188 depends on NET && SYSFS
193 OCFS2 is a general purpose extent based shared disk cluster file
194 system with many similarities to ext3. It supports 64 bit inode
195 numbers, and has automatically extending metadata groups which may
196 also make it attractive for non-clustered use.
198 You'll want to install the ocfs2-tools package in order to at least
201 Project web page: http://oss.oracle.com/projects/ocfs2
202 Tools web page: http://oss.oracle.com/projects/ocfs2-tools
203 OCFS2 mailing lists: http://oss.oracle.com/projects/ocfs2/mailman/
205 For more information on OCFS2, see the file
206 <file:Documentation/filesystems/ocfs2.txt>.
209 tristate "O2CB Kernelspace Clustering"
213 OCFS2 includes a simple kernelspace clustering package, the OCFS2
214 Cluster Base. It only requires a very small userspace component
215 to configure it. This comes with the standard ocfs2-tools package.
216 O2CB is limited to maintaining a cluster for OCFS2 file systems.
217 It cannot manage any other cluster applications.
219 It is always safe to say Y here, as the clustering method is
222 config OCFS2_FS_USERSPACE_CLUSTER
223 tristate "OCFS2 Userspace Clustering"
224 depends on OCFS2_FS && DLM
227 This option will allow OCFS2 to use userspace clustering services
228 in conjunction with the DLM in fs/dlm. If you are using a
229 userspace cluster manager, say Y here.
231 It is safe to say Y, as the clustering method is run-time
234 config OCFS2_FS_STATS
235 bool "OCFS2 statistics"
239 This option allows some fs statistics to be captured. Enabling
240 this option may increase the memory consumption.
242 config OCFS2_DEBUG_MASKLOG
243 bool "OCFS2 logging support"
247 The ocfs2 filesystem has an extensive logging system. The system
248 allows selection of events to log via files in /sys/o2cb/logmask/.
249 This option will enlarge your kernel, but it allows debugging of
250 ocfs2 filesystem issues.
252 config OCFS2_DEBUG_FS
253 bool "OCFS2 expensive checks"
257 This option will enable expensive consistency checks. Enable
258 this option for debugging only as it is likely to decrease
259 performance of the filesystem.
261 config OCFS2_COMPAT_JBD
262 bool "Use JBD for compatibility"
267 The ocfs2 filesystem now uses JBD2 for its journalling. JBD2
268 is backwards compatible with JBD. It is safe to say N here.
269 However, if you really want to use the original JBD, say Y here.
272 tristate "Btrfs filesystem (EXPERIMENTAL) Unstable disk format"
273 depends on EXPERIMENTAL
278 Btrfs is a new filesystem with extents, writable snapshotting,
279 support for multiple devices and many more features.
281 Btrfs is highly experimental, and THE DISK FORMAT IS NOT YET
282 FINALIZED. You should say N here unless you are interested in
283 testing Btrfs with non-critical data.
285 To compile this file system support as a module, choose M here. The
286 module will be called btrfs.
293 bool "Dnotify support"
296 Dnotify is a directory-based per-fd file change notification system
297 that uses signals to communicate events to user-space. There exist
298 superior alternatives, but some applications may still rely on
304 bool "Inotify file change notification support"
307 Say Y here to enable inotify support. Inotify is a file change
308 notification system and a replacement for dnotify. Inotify fixes
309 numerous shortcomings in dnotify and introduces several new features
310 including multiple file events, one-shot support, and unmount
313 For more information, see <file:Documentation/filesystems/inotify.txt>
318 bool "Inotify support for userspace"
322 Say Y here to enable inotify support for userspace, including the
323 associated system calls. Inotify allows monitoring of both files and
324 directories via a single open fd. Events are read from the file
325 descriptor, which is also select()- and poll()-able.
327 For more information, see <file:Documentation/filesystems/inotify.txt>
334 If you say Y here, you will be able to set per user limits for disk
335 usage (also called disk quotas). Currently, it works for the
336 ext2, ext3, and reiserfs file system. ext3 also supports journalled
337 quotas for which you don't need to run quotacheck(8) after an unclean
339 For further details, read the Quota mini-HOWTO, available from
340 <http://www.tldp.org/docs.html#howto>, or the documentation provided
341 with the quota tools. Probably the quota support is only useful for
342 multi user systems. If unsure, say N.
344 config QUOTA_NETLINK_INTERFACE
345 bool "Report quota messages through netlink interface"
346 depends on QUOTA && NET
348 If you say Y here, quota warnings (about exceeding softlimit, reaching
349 hardlimit, etc.) will be reported through netlink interface. If unsure,
352 config PRINT_QUOTA_WARNING
353 bool "Print quota warnings to console (OBSOLETE)"
357 If you say Y here, quota warnings (about exceeding softlimit, reaching
358 hardlimit, etc.) will be printed to the process' controlling terminal.
359 Note that this behavior is currently deprecated and may go away in
360 future. Please use notification via netlink socket instead.
363 tristate "Old quota format support"
366 This quota format was (is) used by kernels earlier than 2.4.22. If
367 you have quota working and you don't want to convert to new quota
371 tristate "Quota format v2 support"
374 This quota format allows using quotas with 32-bit UIDs/GIDs. If you
375 need this functionality say Y here.
379 depends on XFS_QUOTA || QUOTA
383 tristate "Kernel automounter support"
385 The automounter is a tool to automatically mount remote file systems
386 on demand. This implementation is partially kernel-based to reduce
387 overhead in the already-mounted case; this is unlike the BSD
388 automounter (amd), which is a pure user space daemon.
390 To use the automounter you need the user-space tools from the autofs
391 package; you can find the location in <file:Documentation/Changes>.
392 You also want to answer Y to "NFS file system support", below.
394 If you want to use the newer version of the automounter with more
395 features, say N here and say Y to "Kernel automounter v4 support",
398 To compile this support as a module, choose M here: the module will be
401 If you are not a part of a fairly large, distributed network, you
402 probably do not need an automounter, and can say N here.
405 tristate "Kernel automounter version 4 support (also supports v3)"
407 The automounter is a tool to automatically mount remote file systems
408 on demand. This implementation is partially kernel-based to reduce
409 overhead in the already-mounted case; this is unlike the BSD
410 automounter (amd), which is a pure user space daemon.
412 To use the automounter you need the user-space tools from
413 <ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4/>; you also
414 want to answer Y to "NFS file system support", below.
416 To compile this support as a module, choose M here: the module will be
417 called autofs4. You will need to add "alias autofs autofs4" to your
418 modules configuration file.
420 If you are not a part of a fairly large, distributed network or
421 don't have a laptop which needs to dynamically reconfigure to the
422 local network, you probably do not need an automounter, and can say
426 tristate "FUSE (Filesystem in Userspace) support"
428 With FUSE it is possible to implement a fully functional filesystem
429 in a userspace program.
431 There's also companion library: libfuse. This library along with
432 utilities is available from the FUSE homepage:
433 <http://fuse.sourceforge.net/>
435 See <file:Documentation/filesystems/fuse.txt> for more information.
436 See <file:Documentation/Changes> for needed library/utility version.
438 If you want to develop a userspace FS, or if you want to use
439 a filesystem based on FUSE, answer Y or M.
446 menu "CD-ROM/DVD Filesystems"
449 tristate "ISO 9660 CDROM file system support"
451 This is the standard file system used on CD-ROMs. It was previously
452 known as "High Sierra File System" and is called "hsfs" on other
453 Unix systems. The so-called Rock-Ridge extensions which allow for
454 long Unix filenames and symbolic links are also supported by this
455 driver. If you have a CD-ROM drive and want to do more with it than
456 just listen to audio CDs and watch its LEDs, say Y (and read
457 <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO,
458 available from <http://www.tldp.org/docs.html#howto>), thereby
459 enlarging your kernel by about 27 KB; otherwise say N.
461 To compile this file system support as a module, choose M here: the
462 module will be called isofs.
465 bool "Microsoft Joliet CDROM extensions"
466 depends on ISO9660_FS
469 Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system
470 which allows for long filenames in unicode format (unicode is the
471 new 16 bit character code, successor to ASCII, which encodes the
472 characters of almost all languages of the world; see
473 <http://www.unicode.org/> for more information). Say Y here if you
474 want to be able to read Joliet CD-ROMs under Linux.
477 bool "Transparent decompression extension"
478 depends on ISO9660_FS
481 This is a Linux-specific extension to RockRidge which lets you store
482 data in compressed form on a CD-ROM and have it transparently
483 decompressed when the CD-ROM is accessed. See
484 <http://www.kernel.org/pub/linux/utils/fs/zisofs/> for the tools
485 necessary to create such a filesystem. Say Y here if you want to be
486 able to read such compressed CD-ROMs.
489 tristate "UDF file system support"
492 This is the new file system used on some CD-ROMs and DVDs. Say Y if
493 you intend to mount DVD discs or CDRW's written in packet mode, or
494 if written to by other UDF utilities, such as DirectCD.
495 Please read <file:Documentation/filesystems/udf.txt>.
497 To compile this file system support as a module, choose M here: the
498 module will be called udf.
505 depends on (UDF_FS=m && NLS) || (UDF_FS=y && NLS=y)
511 menu "DOS/FAT/NT Filesystems"
517 If you want to use one of the FAT-based file systems (the MS-DOS and
518 VFAT (Windows 95) file systems), then you must say Y or M here
519 to include FAT support. You will then be able to mount partitions or
520 diskettes with FAT-based file systems and transparently access the
521 files on them, i.e. MSDOS files will look and behave just like all
524 This FAT support is not a file system in itself, it only provides
525 the foundation for the other file systems. You will have to say Y or
526 M to at least one of "MSDOS fs support" or "VFAT fs support" in
527 order to make use of it.
529 Another way to read and write MSDOS floppies and hard drive
530 partitions from within Linux (but not transparently) is with the
531 mtools ("man mtools") program suite. You don't need to say Y here in
534 If you need to move large files on floppies between a DOS and a
535 Linux box, say Y here, mount the floppy under Linux with an MSDOS
536 file system and use GNU tar's M option. GNU tar is a program
537 available for Unix and DOS ("man tar" or "info tar").
539 The FAT support will enlarge your kernel by about 37 KB. If unsure,
542 To compile this as a module, choose M here: the module will be called
543 fat. Note that if you compile the FAT support as a module, you
544 cannot compile any of the FAT-based file systems into the kernel
545 -- they will have to be modules as well.
548 tristate "MSDOS fs support"
551 This allows you to mount MSDOS partitions of your hard drive (unless
552 they are compressed; to access compressed MSDOS partitions under
553 Linux, you can either use the DOS emulator DOSEMU, described in the
554 DOSEMU-HOWTO, available from
555 <http://www.tldp.org/docs.html#howto>, or try dmsdosfs in
556 <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you
557 intend to use dosemu with a non-compressed MSDOS partition, say Y
558 here) and MSDOS floppies. This means that file access becomes
559 transparent, i.e. the MSDOS files look and behave just like all
562 If you have Windows 95 or Windows NT installed on your MSDOS
563 partitions, you should use the VFAT file system (say Y to "VFAT fs
564 support" below), or you will not be able to see the long filenames
565 generated by Windows 95 / Windows NT.
567 This option will enlarge your kernel by about 7 KB. If unsure,
568 answer Y. This will only work if you said Y to "DOS FAT fs support"
569 as well. To compile this as a module, choose M here: the module will
573 tristate "VFAT (Windows-95) fs support"
576 This option provides support for normal Windows file systems with
577 long filenames. That includes non-compressed FAT-based file systems
578 used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
579 programs from the mtools package.
581 The VFAT support enlarges your kernel by about 10 KB and it only
582 works if you said Y to the "DOS FAT fs support" above. Please read
583 the file <file:Documentation/filesystems/vfat.txt> for details. If
586 To compile this as a module, choose M here: the module will be called
589 config FAT_DEFAULT_CODEPAGE
590 int "Default codepage for FAT"
591 depends on MSDOS_FS || VFAT_FS
594 This option should be set to the codepage of your FAT filesystems.
595 It can be overridden with the "codepage" mount option.
596 See <file:Documentation/filesystems/vfat.txt> for more information.
598 config FAT_DEFAULT_IOCHARSET
599 string "Default iocharset for FAT"
603 Set this to the default input/output character set you'd
604 like FAT to use. It should probably match the character set
605 that most of your FAT filesystems use, and can be overridden
606 with the "iocharset" mount option for FAT filesystems.
607 Note that "utf8" is not recommended for FAT filesystems.
608 If unsure, you shouldn't set "utf8" here.
609 See <file:Documentation/filesystems/vfat.txt> for more information.
612 tristate "NTFS file system support"
615 NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003.
617 Saying Y or M here enables read support. There is partial, but
618 safe, write support available. For write support you must also
619 say Y to "NTFS write support" below.
621 There are also a number of user-space tools available, called
622 ntfsprogs. These include ntfsundelete and ntfsresize, that work
623 without NTFS support enabled in the kernel.
625 This is a rewrite from scratch of Linux NTFS support and replaced
626 the old NTFS code starting with Linux 2.5.11. A backport to
627 the Linux 2.4 kernel series is separately available as a patch
628 from the project web site.
630 For more information see <file:Documentation/filesystems/ntfs.txt>
631 and <http://www.linux-ntfs.org/>.
633 To compile this file system support as a module, choose M here: the
634 module will be called ntfs.
636 If you are not using Windows NT, 2000, XP or 2003 in addition to
637 Linux on your computer it is safe to say N.
640 bool "NTFS debugging support"
643 If you are experiencing any problems with the NTFS file system, say
644 Y here. This will result in additional consistency checks to be
645 performed by the driver as well as additional debugging messages to
646 be written to the system log. Note that debugging messages are
647 disabled by default. To enable them, supply the option debug_msgs=1
648 at the kernel command line when booting the kernel or as an option
649 to insmod when loading the ntfs module. Once the driver is active,
650 you can enable debugging messages by doing (as root):
651 echo 1 > /proc/sys/fs/ntfs-debug
652 Replacing the "1" with "0" would disable debug messages.
654 If you leave debugging messages disabled, this results in little
655 overhead, but enabling debug messages results in very significant
656 slowdown of the system.
658 When reporting bugs, please try to have available a full dump of
659 debugging messages while the misbehaviour was occurring.
662 bool "NTFS write support"
665 This enables the partial, but safe, write support in the NTFS driver.
667 The only supported operation is overwriting existing files, without
668 changing the file length. No file or directory creation, deletion or
669 renaming is possible. Note only non-resident files can be written to
670 so you may find that some very small files (<500 bytes or so) cannot
673 While we cannot guarantee that it will not damage any data, we have
674 so far not received a single report where the driver would have
675 damaged someones data so we assume it is perfectly safe to use.
677 Note: While write support is safe in this version (a rewrite from
678 scratch of the NTFS support), it should be noted that the old NTFS
679 write support, included in Linux 2.5.10 and before (since 1997),
682 This is currently useful with TopologiLinux. TopologiLinux is run
683 on top of any DOS/Microsoft Windows system without partitioning your
684 hard disk. Unlike other Linux distributions TopologiLinux does not
685 need its own partition. For more information see
686 <http://topologi-linux.sourceforge.net/>
688 It is perfectly safe to say N here.
693 menu "Pseudo filesystems"
695 source "fs/proc/Kconfig"
698 bool "sysfs file system support" if EMBEDDED
701 The sysfs filesystem is a virtual filesystem that the kernel uses to
702 export internal kernel objects, their attributes, and their
703 relationships to one another.
705 Users can use sysfs to ascertain useful information about the running
706 kernel, such as the devices the kernel has discovered on each bus and
707 which driver each is bound to. sysfs can also be used to tune devices
708 and other kernel subsystems.
710 Some system agents rely on the information in sysfs to operate.
711 /sbin/hotplug uses device and object attributes in sysfs to assist in
712 delegating policy decisions, like persistently naming devices.
714 sysfs is currently used by the block subsystem to mount the root
715 partition. If sysfs is disabled you must specify the boot device on
716 the kernel boot command line via its major and minor numbers. For
717 example, "root=03:01" for /dev/hda1.
719 Designers of embedded systems may wish to say N here to conserve space.
722 bool "Virtual memory file system support (former shm fs)"
724 Tmpfs is a file system which keeps all files in virtual memory.
726 Everything in tmpfs is temporary in the sense that no files will be
727 created on your hard drive. The files live in memory and swap
728 space. If you unmount a tmpfs instance, everything stored therein is
731 See <file:Documentation/filesystems/tmpfs.txt> for details.
733 config TMPFS_POSIX_ACL
734 bool "Tmpfs POSIX Access Control Lists"
738 POSIX Access Control Lists (ACLs) support permissions for users and
739 groups beyond the owner/group/world scheme.
741 To learn more about Access Control Lists, visit the POSIX ACLs for
742 Linux website <http://acl.bestbits.at/>.
744 If you don't know what Access Control Lists are, say N.
747 bool "HugeTLB file system support"
748 depends on X86 || IA64 || PPC64 || SPARC64 || (SUPERH && MMU) || \
749 (S390 && 64BIT) || BROKEN
751 hugetlbfs is a filesystem backing for HugeTLB pages, based on
752 ramfs. For architectures that support it, say Y here and read
753 <file:Documentation/vm/hugetlbpage.txt> for details.
761 tristate "Userspace-driven configuration filesystem"
764 configfs is a ram-based filesystem that provides the converse
765 of sysfs's functionality. Where sysfs is a filesystem-based
766 view of kernel objects, configfs is a filesystem-based manager
767 of kernel objects, or config_items.
769 Both sysfs and configfs can and should exist together on the
770 same system. One is not a replacement for the other.
774 menu "Miscellaneous filesystems"
777 tristate "ADFS file system support (EXPERIMENTAL)"
778 depends on BLOCK && EXPERIMENTAL
780 The Acorn Disc Filing System is the standard file system of the
781 RiscOS operating system which runs on Acorn's ARM-based Risc PC
782 systems and the Acorn Archimedes range of machines. If you say Y
783 here, Linux will be able to read from ADFS partitions on hard drives
784 and from ADFS-formatted floppy discs. If you also want to be able to
785 write to those devices, say Y to "ADFS write support" below.
787 The ADFS partition should be the first partition (i.e.,
788 /dev/[hs]d?1) on each of your drives. Please read the file
789 <file:Documentation/filesystems/adfs.txt> for further details.
791 To compile this code as a module, choose M here: the module will be
797 bool "ADFS write support (DANGEROUS)"
800 If you say Y here, you will be able to write to ADFS partitions on
801 hard drives and ADFS-formatted floppy disks. This is experimental
802 codes, so if you're unsure, say N.
805 tristate "Amiga FFS file system support (EXPERIMENTAL)"
806 depends on BLOCK && EXPERIMENTAL
808 The Fast File System (FFS) is the common file system used on hard
809 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
810 if you want to be able to read and write files from and to an Amiga
811 FFS partition on your hard drive. Amiga floppies however cannot be
812 read with this driver due to an incompatibility of the floppy
813 controller used in an Amiga and the standard floppy controller in
814 PCs and workstations. Read <file:Documentation/filesystems/affs.txt>
815 and <file:fs/affs/Changes>.
817 With this driver you can also mount disk files used by Bernd
818 Schmidt's Un*X Amiga Emulator
819 (<http://www.freiburg.linux.de/~uae/>).
820 If you want to do this, you will also need to say Y or M to "Loop
821 device support", above.
823 To compile this file system support as a module, choose M here: the
824 module will be called affs. If unsure, say N.
827 tristate "eCrypt filesystem layer support (EXPERIMENTAL)"
828 depends on EXPERIMENTAL && KEYS && CRYPTO && NET
830 Encrypted filesystem that operates on the VFS layer. See
831 <file:Documentation/filesystems/ecryptfs.txt> to learn more about
832 eCryptfs. Userspace components are required and can be
833 obtained from <http://ecryptfs.sf.net>.
835 To compile this file system support as a module, choose M here: the
836 module will be called ecryptfs.
839 tristate "Apple Macintosh file system support (EXPERIMENTAL)"
840 depends on BLOCK && EXPERIMENTAL
843 If you say Y here, you will be able to mount Macintosh-formatted
844 floppy disks and hard drive partitions with full read-write access.
845 Please read <file:Documentation/filesystems/hfs.txt> to learn about
846 the available mount options.
848 To compile this file system support as a module, choose M here: the
849 module will be called hfs.
852 tristate "Apple Extended HFS file system support"
857 If you say Y here, you will be able to mount extended format
858 Macintosh-formatted hard drive partitions with full read-write access.
860 This file system is often called HFS+ and was introduced with
861 MacOS 8. It includes all Mac specific filesystem data such as
862 data forks and creator codes, but it also has several UNIX
863 style features such as file ownership and permissions.
866 tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)"
867 depends on BLOCK && EXPERIMENTAL
870 The BeOS File System (BeFS) is the native file system of Be, Inc's
871 BeOS. Notable features include support for arbitrary attributes
872 on files and directories, and database-like indices on selected
873 attributes. (Also note that this driver doesn't make those features
874 available at this time). It is a 64 bit filesystem, so it supports
875 extremely large volumes and files.
877 If you use this filesystem, you should also say Y to at least one
878 of the NLS (native language support) options below.
880 If you don't know what this is about, say N.
882 To compile this as a module, choose M here: the module will be
889 If you say Y here, you can use the 'debug' mount option to enable
890 debugging output from the driver.
893 tristate "BFS file system support (EXPERIMENTAL)"
894 depends on BLOCK && EXPERIMENTAL
896 Boot File System (BFS) is a file system used under SCO UnixWare to
897 allow the bootloader access to the kernel image and other important
898 files during the boot process. It is usually mounted under /stand
899 and corresponds to the slice marked as "STAND" in the UnixWare
900 partition. You should say Y if you want to read or write the files
901 on your /stand slice from within Linux. You then also need to say Y
902 to "UnixWare slices support", below. More information about the BFS
903 file system is contained in the file
904 <file:Documentation/filesystems/bfs.txt>.
906 If you don't know what this is about, say N.
908 To compile this as a module, choose M here: the module will be called
909 bfs. Note that the file system of your root partition (the one
910 containing the directory /) cannot be compiled as a module.
915 tristate "EFS file system support (read only) (EXPERIMENTAL)"
916 depends on BLOCK && EXPERIMENTAL
918 EFS is an older file system used for non-ISO9660 CD-ROMs and hard
919 disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
920 uses the XFS file system for hard disk partitions however).
922 This implementation only offers read-only access. If you don't know
923 what all this is about, it's safe to say N. For more information
924 about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
926 To compile the EFS file system support as a module, choose M here: the
927 module will be called efs.
929 source "fs/jffs2/Kconfig"
930 # UBIFS File system configuration
931 source "fs/ubifs/Kconfig"
934 tristate "Compressed ROM file system support (cramfs)"
938 Saying Y here includes support for CramFs (Compressed ROM File
939 System). CramFs is designed to be a simple, small, and compressed
940 file system for ROM based embedded systems. CramFs is read-only,
941 limited to 256MB file systems (with 16MB files), and doesn't support
942 16/32 bits uid/gid, hard links and timestamps.
944 See <file:Documentation/filesystems/cramfs.txt> and
945 <file:fs/cramfs/README> for further information.
947 To compile this as a module, choose M here: the module will be called
948 cramfs. Note that the root file system (the one containing the
949 directory /) cannot be compiled as a module.
954 tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
957 FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
958 file system format. VERITAS VxFS(TM) is the standard file system
959 of SCO UnixWare (and possibly others) and optionally available
960 for Sunsoft Solaris, HP-UX and many other operating systems.
961 Currently only readonly access is supported.
963 NOTE: the file system type as used by mount(1), mount(2) and
964 fstab(5) is 'vxfs' as it describes the file system format, not
967 To compile this as a module, choose M here: the module will be
968 called freevxfs. If unsure, say N.
971 tristate "Minix file system support"
974 Minix is a simple operating system used in many classes about OS's.
975 The minix file system (method to organize files on a hard disk
976 partition or a floppy disk) was the original file system for Linux,
977 but has been superseded by the second extended file system ext2fs.
978 You don't want to use the minix file system on your hard disk
979 because of certain built-in restrictions, but it is sometimes found
980 on older Linux floppy disks. This option will enlarge your kernel
981 by about 28 KB. If unsure, say N.
983 To compile this file system support as a module, choose M here: the
984 module will be called minix. Note that the file system of your root
985 partition (the one containing the directory /) cannot be compiled as
989 tristate "SonicBlue Optimized MPEG File System support"
993 This is the proprietary file system used by the Rio Karma music
994 player and ReplayTV DVR. Despite the name, this filesystem is not
995 more efficient than a standard FS for MPEG files, in fact likely
996 the opposite is true. Say Y if you have either of these devices
997 and wish to mount its disk.
999 To compile this file system support as a module, choose M here: the
1000 module will be called omfs. If unsure, say N.
1003 tristate "OS/2 HPFS file system support"
1006 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
1007 is the file system used for organizing files on OS/2 hard disk
1008 partitions. Say Y if you want to be able to read files from and
1009 write files to an OS/2 HPFS partition on your hard drive. OS/2
1010 floppies however are in regular MSDOS format, so you don't need this
1011 option in order to be able to read them. Read
1012 <file:Documentation/filesystems/hpfs.txt>.
1014 To compile this file system support as a module, choose M here: the
1015 module will be called hpfs. If unsure, say N.
1019 tristate "QNX4 file system support (read only)"
1022 This is the file system used by the real-time operating systems
1023 QNX 4 and QNX 6 (the latter is also called QNX RTP).
1024 Further information is available at <http://www.qnx.com/>.
1025 Say Y if you intend to mount QNX hard disks or floppies.
1026 Unless you say Y to "QNX4FS read-write support" below, you will
1027 only be able to read these file systems.
1029 To compile this file system support as a module, choose M here: the
1030 module will be called qnx4.
1032 If you don't know whether you need it, then you don't need it:
1036 bool "QNX4FS write support (DANGEROUS)"
1037 depends on QNX4FS_FS && EXPERIMENTAL && BROKEN
1039 Say Y if you want to test write support for QNX4 file systems.
1041 It's currently broken, so for now:
1045 tristate "ROM file system support"
1048 This is a very small read-only file system mainly intended for
1049 initial ram disks of installation disks, but it could be used for
1050 other read-only media as well. Read
1051 <file:Documentation/filesystems/romfs.txt> for details.
1053 To compile this file system support as a module, choose M here: the
1054 module will be called romfs. Note that the file system of your
1055 root partition (the one containing the directory /) cannot be a
1058 If you don't know whether you need it, then you don't need it:
1063 tristate "System V/Xenix/V7/Coherent file system support"
1066 SCO, Xenix and Coherent are commercial Unix systems for Intel
1067 machines, and Version 7 was used on the DEC PDP-11. Saying Y
1068 here would allow you to read from their floppies and hard disk
1071 If you have floppies or hard disk partitions like that, it is likely
1072 that they contain binaries from those other Unix systems; in order
1073 to run these binaries, you will want to install linux-abi which is
1074 a set of kernel modules that lets you run SCO, Xenix, Wyse,
1075 UnixWare, Dell Unix and System V programs under Linux. It is
1076 available via FTP (user: ftp) from
1077 <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
1078 NOTE: that will work only for binaries from Intel-based systems;
1079 PDP ones will have to wait until somebody ports Linux to -11 ;-)
1081 If you only intend to mount files from some other Unix over the
1082 network using NFS, you don't need the System V file system support
1083 (but you need NFS file system support obviously).
1085 Note that this option is generally not needed for floppies, since a
1086 good portable way to transport files and directories between unixes
1087 (and even other operating systems) is given by the tar program ("man
1088 tar" or preferably "info tar"). Note also that this option has
1089 nothing whatsoever to do with the option "System V IPC". Read about
1090 the System V file system in
1091 <file:Documentation/filesystems/sysv-fs.txt>.
1092 Saying Y here will enlarge your kernel by about 27 KB.
1094 To compile this as a module, choose M here: the module will be called
1097 If you haven't heard about all of this before, it's safe to say N.
1101 tristate "UFS file system support (read only)"
1104 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
1105 OpenBSD and NeXTstep) use a file system called UFS. Some System V
1106 Unixes can create and mount hard disk partitions and diskettes using
1107 this file system as well. Saying Y here will allow you to read from
1108 these partitions; if you also want to write to them, say Y to the
1109 experimental "UFS file system write support", below. Please read the
1110 file <file:Documentation/filesystems/ufs.txt> for more information.
1112 The recently released UFS2 variant (used in FreeBSD 5.x) is
1113 READ-ONLY supported.
1115 Note that this option is generally not needed for floppies, since a
1116 good portable way to transport files and directories between unixes
1117 (and even other operating systems) is given by the tar program ("man
1118 tar" or preferably "info tar").
1120 When accessing NeXTstep files, you may need to convert them from the
1121 NeXT character set to the Latin1 character set; use the program
1122 recode ("info recode") for this purpose.
1124 To compile the UFS file system support as a module, choose M here: the
1125 module will be called ufs.
1127 If you haven't heard about all of this before, it's safe to say N.
1130 bool "UFS file system write support (DANGEROUS)"
1131 depends on UFS_FS && EXPERIMENTAL
1133 Say Y here if you want to try writing to UFS partitions. This is
1134 experimental, so you should back up your UFS partitions beforehand.
1137 bool "UFS debugging"
1140 If you are experiencing any problems with the UFS filesystem, say
1141 Y here. This will result in _many_ additional debugging messages to be
1142 written to the system log.
1146 menuconfig NETWORK_FILESYSTEMS
1147 bool "Network File Systems"
1151 Say Y here to get to see options for network filesystems and
1152 filesystem-related networking code, such as NFS daemon and
1153 RPCSEC security modules.
1155 This option alone does not add any kernel code.
1157 If you say N, all options in this submenu will be skipped and
1158 disabled; if unsure, say Y here.
1160 if NETWORK_FILESYSTEMS
1163 tristate "NFS client support"
1167 select NFS_ACL_SUPPORT if NFS_V3_ACL
1169 Choose Y here if you want to access files residing on other
1170 computers using Sun's Network File System protocol. To compile
1171 this file system support as a module, choose M here: the module
1174 To mount file systems exported by NFS servers, you also need to
1175 install the user space mount.nfs command which can be found in
1176 the Linux nfs-utils package, available from http://linux-nfs.org/.
1177 Information about using the mount command is available in the
1178 mount(8) man page. More detail about the Linux NFS client
1179 implementation is available via the nfs(5) man page.
1181 Below you can choose which versions of the NFS protocol are
1182 available in the kernel to mount NFS servers. Support for NFS
1183 version 2 (RFC 1094) is always available when NFS_FS is selected.
1185 To configure a system which mounts its root file system via NFS
1186 at boot time, say Y here, select "Kernel level IP
1187 autoconfiguration" in the NETWORK menu, and select "Root file
1188 system on NFS" below. You cannot compile this file system as a
1189 module in this case.
1194 bool "NFS client support for NFS version 3"
1197 This option enables support for version 3 of the NFS protocol
1198 (RFC 1813) in the kernel's NFS client.
1203 bool "NFS client support for the NFSv3 ACL protocol extension"
1206 Some NFS servers support an auxiliary NFSv3 ACL protocol that
1207 Sun added to Solaris but never became an official part of the
1208 NFS version 3 protocol. This protocol extension allows
1209 applications on NFS clients to manipulate POSIX Access Control
1210 Lists on files residing on NFS servers. NFS servers enforce
1211 ACLs on local files whether this protocol is available or not.
1213 Choose Y here if your NFS server supports the Solaris NFSv3 ACL
1214 protocol extension and you want your NFS client to allow
1215 applications to access and modify ACLs on files on the server.
1217 Most NFS servers don't support the Solaris NFSv3 ACL protocol
1218 extension. You can choose N here or specify the "noacl" mount
1219 option to prevent your NFS client from trying to use the NFSv3
1225 bool "NFS client support for NFS version 4 (EXPERIMENTAL)"
1226 depends on NFS_FS && EXPERIMENTAL
1227 select RPCSEC_GSS_KRB5
1229 This option enables support for version 4 of the NFS protocol
1230 (RFC 3530) in the kernel's NFS client.
1232 To mount NFS servers using NFSv4, you also need to install user
1233 space programs which can be found in the Linux nfs-utils package,
1234 available from http://linux-nfs.org/.
1239 bool "Root file system on NFS"
1240 depends on NFS_FS=y && IP_PNP
1242 If you want your system to mount its root file system via NFS,
1243 choose Y here. This is common practice for managing systems
1244 without local permanent storage. For details, read
1245 <file:Documentation/filesystems/nfsroot.txt>.
1247 Most people say N here.
1250 tristate "NFS server support"
1255 select NFS_ACL_SUPPORT if NFSD_V2_ACL
1257 Choose Y here if you want to allow other computers to access
1258 files residing on this system using Sun's Network File System
1259 protocol. To compile the NFS server support as a module,
1260 choose M here: the module will be called nfsd.
1262 You may choose to use a user-space NFS server instead, in which
1263 case you can choose N here.
1265 To export local file systems using NFS, you also need to install
1266 user space programs which can be found in the Linux nfs-utils
1267 package, available from http://linux-nfs.org/. More detail about
1268 the Linux NFS server implementation is available via the
1269 exports(5) man page.
1271 Below you can choose which versions of the NFS protocol are
1272 available to clients mounting the NFS server on this system.
1273 Support for NFS version 2 (RFC 1094) is always available when
1274 CONFIG_NFSD is selected.
1283 bool "NFS server support for NFS version 3"
1286 This option enables support in your system's NFS server for
1287 version 3 of the NFS protocol (RFC 1813).
1292 bool "NFS server support for the NFSv3 ACL protocol extension"
1296 Solaris NFS servers support an auxiliary NFSv3 ACL protocol that
1297 never became an official part of the NFS version 3 protocol.
1298 This protocol extension allows applications on NFS clients to
1299 manipulate POSIX Access Control Lists on files residing on NFS
1300 servers. NFS servers enforce POSIX ACLs on local files whether
1301 this protocol is available or not.
1303 This option enables support in your system's NFS server for the
1304 NFSv3 ACL protocol extension allowing NFS clients to manipulate
1305 POSIX ACLs on files exported by your system's NFS server. NFS
1306 clients which support the Solaris NFSv3 ACL protocol can then
1307 access and modify ACLs on your NFS server.
1309 To store ACLs on your NFS server, you also need to enable ACL-
1310 related CONFIG options for your local file systems of choice.
1315 bool "NFS server support for NFS version 4 (EXPERIMENTAL)"
1316 depends on NFSD && PROC_FS && EXPERIMENTAL
1319 select RPCSEC_GSS_KRB5
1321 This option enables support in your system's NFS server for
1322 version 4 of the NFS protocol (RFC 3530).
1324 To export files using NFSv4, you need to install additional user
1325 space programs which can be found in the Linux nfs-utils package,
1326 available from http://linux-nfs.org/.
1335 depends on NFSD_V3 || NFS_V3
1341 config NFS_ACL_SUPPORT
1347 depends on NFSD || NFS_FS
1356 config SUNRPC_XPRT_RDMA
1358 depends on SUNRPC && INFINIBAND && EXPERIMENTAL
1359 default SUNRPC && INFINIBAND
1361 This option enables an RPC client transport capability that
1362 allows the NFS client to mount servers via an RDMA-enabled
1365 To compile RPC client RDMA transport support as a module,
1366 choose M here: the module will be called xprtrdma.
1370 config SUNRPC_REGISTER_V4
1371 bool "Register local RPC services via rpcbind v4 (EXPERIMENTAL)"
1372 depends on SUNRPC && EXPERIMENTAL
1375 Sun added support for registering RPC services at an IPv6
1376 address by creating two new versions of the rpcbind protocol
1379 This option enables support in the kernel RPC server for
1380 registering kernel RPC services via version 4 of the rpcbind
1381 protocol. If you enable this option, you must run a portmapper
1382 daemon that supports rpcbind protocol version 4.
1384 Serving NFS over IPv6 from knfsd (the kernel's NFS server)
1385 requires that you enable this option and use a portmapper that
1386 supports rpcbind version 4.
1388 If unsure, say N to get traditional behavior (register kernel
1389 RPC services using only rpcbind version 2). Distributions
1390 using the legacy Linux portmapper daemon must say N here.
1392 config RPCSEC_GSS_KRB5
1393 tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
1394 depends on SUNRPC && EXPERIMENTAL
1401 Choose Y here to enable Secure RPC using the Kerberos version 5
1402 GSS-API mechanism (RFC 1964).
1404 Secure RPC calls with Kerberos require an auxiliary user-space
1405 daemon which may be found in the Linux nfs-utils package
1406 available from http://linux-nfs.org/. In addition, user-space
1407 Kerberos support should be installed.
1411 config RPCSEC_GSS_SPKM3
1412 tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
1413 depends on SUNRPC && EXPERIMENTAL
1421 Choose Y here to enable Secure RPC using the SPKM3 public key
1422 GSS-API mechansim (RFC 2025).
1424 Secure RPC calls with SPKM3 require an auxiliary userspace
1425 daemon which may be found in the Linux nfs-utils package
1426 available from http://linux-nfs.org/.
1431 tristate "SMB file system support (OBSOLETE, please use CIFS)"
1435 SMB (Server Message Block) is the protocol Windows for Workgroups
1436 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
1437 files and printers over local networks. Saying Y here allows you to
1438 mount their file systems (often called "shares" in this context) and
1439 access them just like any other Unix directory. Currently, this
1440 works only if the Windows machines use TCP/IP as the underlying
1441 transport protocol, and not NetBEUI. For details, read
1442 <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
1443 available from <http://www.tldp.org/docs.html#howto>.
1445 Note: if you just want your box to act as an SMB *server* and make
1446 files and printing services available to Windows clients (which need
1447 to have a TCP/IP stack), you don't need to say Y here; you can use
1448 the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
1451 General information about how to connect Linux, Windows machines and
1452 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1454 To compile the SMB support as a module, choose M here:
1455 the module will be called smbfs. Most people say N, however.
1457 config SMB_NLS_DEFAULT
1458 bool "Use a default NLS"
1461 Enabling this will make smbfs use nls translations by default. You
1462 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
1463 settings and you need to give the default nls for the SMB server as
1464 CONFIG_SMB_NLS_REMOTE.
1466 The nls settings can be changed at mount time, if your smbmount
1467 supports that, using the codepage and iocharset parameters.
1469 smbmount from samba 2.2.0 or later supports this.
1471 config SMB_NLS_REMOTE
1472 string "Default Remote NLS Option"
1473 depends on SMB_NLS_DEFAULT
1476 This setting allows you to specify a default value for which
1477 codepage the server uses. If this field is left blank no
1478 translations will be done by default. The local codepage/charset
1479 default to CONFIG_NLS_DEFAULT.
1481 The nls settings can be changed at mount time, if your smbmount
1482 supports that, using the codepage and iocharset parameters.
1484 smbmount from samba 2.2.0 or later supports this.
1486 source "fs/cifs/Kconfig"
1489 tristate "NCP file system support (to mount NetWare volumes)"
1490 depends on IPX!=n || INET
1492 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
1493 used by Novell NetWare clients to talk to file servers. It is to
1494 IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
1495 to mount NetWare file server volumes and to access them just like
1496 any other Unix directory. For details, please read the file
1497 <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
1498 the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
1500 You do not have to say Y here if you want your Linux box to act as a
1501 file *server* for Novell NetWare clients.
1503 General information about how to connect Linux, Windows machines and
1504 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1506 To compile this as a module, choose M here: the module will be called
1507 ncpfs. Say N unless you are connected to a Novell network.
1509 source "fs/ncpfs/Kconfig"
1512 tristate "Coda file system support (advanced network fs)"
1515 Coda is an advanced network file system, similar to NFS in that it
1516 enables you to mount file systems of a remote server and access them
1517 with regular Unix commands as if they were sitting on your hard
1518 disk. Coda has several advantages over NFS: support for
1519 disconnected operation (e.g. for laptops), read/write server
1520 replication, security model for authentication and encryption,
1521 persistent client caches and write back caching.
1523 If you say Y here, your Linux box will be able to act as a Coda
1524 *client*. You will need user level code as well, both for the
1525 client and server. Servers are currently user level, i.e. they need
1526 no kernel support. Please read
1527 <file:Documentation/filesystems/coda.txt> and check out the Coda
1528 home page <http://www.coda.cs.cmu.edu/>.
1530 To compile the coda client support as a module, choose M here: the
1531 module will be called coda.
1534 tristate "Andrew File System support (AFS) (EXPERIMENTAL)"
1535 depends on INET && EXPERIMENTAL
1538 If you say Y here, you will get an experimental Andrew File System
1539 driver. It currently only supports unsecured read-only AFS access.
1541 See <file:Documentation/filesystems/afs.txt> for more information.
1546 bool "AFS dynamic debugging"
1549 Say Y here to make runtime controllable debugging messages appear.
1551 See <file:Documentation/filesystems/afs.txt> for more information.
1556 tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
1557 depends on INET && NET_9P && EXPERIMENTAL
1559 If you say Y here, you will get experimental support for
1560 Plan 9 resource sharing via the 9P2000 protocol.
1562 See <http://v9fs.sf.net> for more information.
1566 endif # NETWORK_FILESYSTEMS
1569 menu "Partition Types"
1571 source "fs/partitions/Kconfig"
1576 source "fs/nls/Kconfig"
1577 source "fs/dlm/Kconfig"
projects / linux-2.6 / blob