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
30 source "fs/reiserfs/Kconfig"
33 tristate "JFS filesystem support"
36 This is a port of IBM's Journaled Filesystem . More information is
37 available in the file <file:Documentation/filesystems/jfs.txt>.
39 If you do not intend to use the JFS filesystem, say N.
42 bool "JFS POSIX Access Control Lists"
46 Posix Access Control Lists (ACLs) support permissions for users and
47 groups beyond the owner/group/world scheme.
49 To learn more about Access Control Lists, visit the Posix ACLs for
50 Linux website <http://acl.bestbits.at/>.
52 If you don't know what Access Control Lists are, say N
55 bool "JFS Security Labels"
58 Security labels support alternative access control models
59 implemented by security modules like SELinux. This option
60 enables an extended attribute handler for file security
61 labels in the jfs filesystem.
63 If you are not using a security module that requires using
64 extended attributes for file security labels, say N.
70 If you are experiencing any problems with the JFS filesystem, say
71 Y here. This will result in additional debugging messages to be
72 written to the system log. Under normal circumstances, this
73 results in very little overhead.
79 Enabling this option will cause statistics from the JFS file system
80 to be made available to the user in the /proc/fs/jfs/ directory.
83 # Posix ACL utility routines (for now, only ext2/ext3/jfs/reiserfs/nfs4)
85 # NOTE: you can implement Posix ACLs without these helpers (XFS does).
86 # Never use this symbol for ifdefs.
92 bool "Enable POSIX file locking API" if EMBEDDED
95 This option enables standard file locking support, required
96 for filesystems like NFS and for the flock() system
97 call. Disabling this option saves about 11k.
99 source "fs/xfs/Kconfig"
100 source "fs/gfs2/Kconfig"
103 tristate "OCFS2 file system support"
104 depends on NET && SYSFS
111 OCFS2 is a general purpose extent based shared disk cluster file
112 system with many similarities to ext3. It supports 64 bit inode
113 numbers, and has automatically extending metadata groups which may
114 also make it attractive for non-clustered use.
116 You'll want to install the ocfs2-tools package in order to at least
119 Project web page: http://oss.oracle.com/projects/ocfs2
120 Tools web page: http://oss.oracle.com/projects/ocfs2-tools
121 OCFS2 mailing lists: http://oss.oracle.com/projects/ocfs2/mailman/
123 For more information on OCFS2, see the file
124 <file:Documentation/filesystems/ocfs2.txt>.
127 tristate "O2CB Kernelspace Clustering"
131 OCFS2 includes a simple kernelspace clustering package, the OCFS2
132 Cluster Base. It only requires a very small userspace component
133 to configure it. This comes with the standard ocfs2-tools package.
134 O2CB is limited to maintaining a cluster for OCFS2 file systems.
135 It cannot manage any other cluster applications.
137 It is always safe to say Y here, as the clustering method is
140 config OCFS2_FS_USERSPACE_CLUSTER
141 tristate "OCFS2 Userspace Clustering"
142 depends on OCFS2_FS && DLM
145 This option will allow OCFS2 to use userspace clustering services
146 in conjunction with the DLM in fs/dlm. If you are using a
147 userspace cluster manager, say Y here.
149 It is safe to say Y, as the clustering method is run-time
152 config OCFS2_FS_STATS
153 bool "OCFS2 statistics"
157 This option allows some fs statistics to be captured. Enabling
158 this option may increase the memory consumption.
160 config OCFS2_DEBUG_MASKLOG
161 bool "OCFS2 logging support"
165 The ocfs2 filesystem has an extensive logging system. The system
166 allows selection of events to log via files in /sys/o2cb/logmask/.
167 This option will enlarge your kernel, but it allows debugging of
168 ocfs2 filesystem issues.
170 config OCFS2_DEBUG_FS
171 bool "OCFS2 expensive checks"
175 This option will enable expensive consistency checks. Enable
176 this option for debugging only as it is likely to decrease
177 performance of the filesystem.
179 config OCFS2_FS_POSIX_ACL
180 bool "OCFS2 POSIX Access Control Lists"
185 Posix Access Control Lists (ACLs) support permissions for users and
186 groups beyond the owner/group/world scheme.
189 tristate "Btrfs filesystem (EXPERIMENTAL) Unstable disk format"
190 depends on EXPERIMENTAL
195 Btrfs is a new filesystem with extents, writable snapshotting,
196 support for multiple devices and many more features.
198 Btrfs is highly experimental, and THE DISK FORMAT IS NOT YET
199 FINALIZED. You should say N here unless you are interested in
200 testing Btrfs with non-critical data.
202 To compile this file system support as a module, choose M here. The
203 module will be called btrfs.
209 source "fs/notify/Kconfig"
214 If you say Y here, you will be able to set per user limits for disk
215 usage (also called disk quotas). Currently, it works for the
216 ext2, ext3, and reiserfs file system. ext3 also supports journalled
217 quotas for which you don't need to run quotacheck(8) after an unclean
219 For further details, read the Quota mini-HOWTO, available from
220 <http://www.tldp.org/docs.html#howto>, or the documentation provided
221 with the quota tools. Probably the quota support is only useful for
222 multi user systems. If unsure, say N.
224 config QUOTA_NETLINK_INTERFACE
225 bool "Report quota messages through netlink interface"
226 depends on QUOTA && NET
228 If you say Y here, quota warnings (about exceeding softlimit, reaching
229 hardlimit, etc.) will be reported through netlink interface. If unsure,
232 config PRINT_QUOTA_WARNING
233 bool "Print quota warnings to console (OBSOLETE)"
237 If you say Y here, quota warnings (about exceeding softlimit, reaching
238 hardlimit, etc.) will be printed to the process' controlling terminal.
239 Note that this behavior is currently deprecated and may go away in
240 future. Please use notification via netlink socket instead.
242 # Generic support for tree structured quota files. Seleted when needed.
247 tristate "Old quota format support"
250 This quota format was (is) used by kernels earlier than 2.4.22. If
251 you have quota working and you don't want to convert to new quota
255 tristate "Quota format v2 support"
259 This quota format allows using quotas with 32-bit UIDs/GIDs. If you
260 need this functionality say Y here.
264 depends on XFS_QUOTA || QUOTA
268 tristate "Kernel automounter support"
270 The automounter is a tool to automatically mount remote file systems
271 on demand. This implementation is partially kernel-based to reduce
272 overhead in the already-mounted case; this is unlike the BSD
273 automounter (amd), which is a pure user space daemon.
275 To use the automounter you need the user-space tools from the autofs
276 package; you can find the location in <file:Documentation/Changes>.
277 You also want to answer Y to "NFS file system support", below.
279 If you want to use the newer version of the automounter with more
280 features, say N here and say Y to "Kernel automounter v4 support",
283 To compile this support as a module, choose M here: the module will be
286 If you are not a part of a fairly large, distributed network, you
287 probably do not need an automounter, and can say N here.
290 tristate "Kernel automounter version 4 support (also supports v3)"
292 The automounter is a tool to automatically mount remote file systems
293 on demand. This implementation is partially kernel-based to reduce
294 overhead in the already-mounted case; this is unlike the BSD
295 automounter (amd), which is a pure user space daemon.
297 To use the automounter you need the user-space tools from
298 <ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4/>; you also
299 want to answer Y to "NFS file system support", below.
301 To compile this support as a module, choose M here: the module will be
302 called autofs4. You will need to add "alias autofs autofs4" to your
303 modules configuration file.
305 If you are not a part of a fairly large, distributed network or
306 don't have a laptop which needs to dynamically reconfigure to the
307 local network, you probably do not need an automounter, and can say
311 tristate "FUSE (Filesystem in Userspace) support"
313 With FUSE it is possible to implement a fully functional filesystem
314 in a userspace program.
316 There's also companion library: libfuse. This library along with
317 utilities is available from the FUSE homepage:
318 <http://fuse.sourceforge.net/>
320 See <file:Documentation/filesystems/fuse.txt> for more information.
321 See <file:Documentation/Changes> for needed library/utility version.
323 If you want to develop a userspace FS, or if you want to use
324 a filesystem based on FUSE, answer Y or M.
331 menu "CD-ROM/DVD Filesystems"
334 tristate "ISO 9660 CDROM file system support"
336 This is the standard file system used on CD-ROMs. It was previously
337 known as "High Sierra File System" and is called "hsfs" on other
338 Unix systems. The so-called Rock-Ridge extensions which allow for
339 long Unix filenames and symbolic links are also supported by this
340 driver. If you have a CD-ROM drive and want to do more with it than
341 just listen to audio CDs and watch its LEDs, say Y (and read
342 <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO,
343 available from <http://www.tldp.org/docs.html#howto>), thereby
344 enlarging your kernel by about 27 KB; otherwise say N.
346 To compile this file system support as a module, choose M here: the
347 module will be called isofs.
350 bool "Microsoft Joliet CDROM extensions"
351 depends on ISO9660_FS
354 Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system
355 which allows for long filenames in unicode format (unicode is the
356 new 16 bit character code, successor to ASCII, which encodes the
357 characters of almost all languages of the world; see
358 <http://www.unicode.org/> for more information). Say Y here if you
359 want to be able to read Joliet CD-ROMs under Linux.
362 bool "Transparent decompression extension"
363 depends on ISO9660_FS
366 This is a Linux-specific extension to RockRidge which lets you store
367 data in compressed form on a CD-ROM and have it transparently
368 decompressed when the CD-ROM is accessed. See
369 <http://www.kernel.org/pub/linux/utils/fs/zisofs/> for the tools
370 necessary to create such a filesystem. Say Y here if you want to be
371 able to read such compressed CD-ROMs.
374 tristate "UDF file system support"
377 This is the new file system used on some CD-ROMs and DVDs. Say Y if
378 you intend to mount DVD discs or CDRW's written in packet mode, or
379 if written to by other UDF utilities, such as DirectCD.
380 Please read <file:Documentation/filesystems/udf.txt>.
382 To compile this file system support as a module, choose M here: the
383 module will be called udf.
390 depends on (UDF_FS=m && NLS) || (UDF_FS=y && NLS=y)
396 menu "DOS/FAT/NT Filesystems"
402 If you want to use one of the FAT-based file systems (the MS-DOS and
403 VFAT (Windows 95) file systems), then you must say Y or M here
404 to include FAT support. You will then be able to mount partitions or
405 diskettes with FAT-based file systems and transparently access the
406 files on them, i.e. MSDOS files will look and behave just like all
409 This FAT support is not a file system in itself, it only provides
410 the foundation for the other file systems. You will have to say Y or
411 M to at least one of "MSDOS fs support" or "VFAT fs support" in
412 order to make use of it.
414 Another way to read and write MSDOS floppies and hard drive
415 partitions from within Linux (but not transparently) is with the
416 mtools ("man mtools") program suite. You don't need to say Y here in
419 If you need to move large files on floppies between a DOS and a
420 Linux box, say Y here, mount the floppy under Linux with an MSDOS
421 file system and use GNU tar's M option. GNU tar is a program
422 available for Unix and DOS ("man tar" or "info tar").
424 The FAT support will enlarge your kernel by about 37 KB. If unsure,
427 To compile this as a module, choose M here: the module will be called
428 fat. Note that if you compile the FAT support as a module, you
429 cannot compile any of the FAT-based file systems into the kernel
430 -- they will have to be modules as well.
433 tristate "MSDOS fs support"
436 This allows you to mount MSDOS partitions of your hard drive (unless
437 they are compressed; to access compressed MSDOS partitions under
438 Linux, you can either use the DOS emulator DOSEMU, described in the
439 DOSEMU-HOWTO, available from
440 <http://www.tldp.org/docs.html#howto>, or try dmsdosfs in
441 <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you
442 intend to use dosemu with a non-compressed MSDOS partition, say Y
443 here) and MSDOS floppies. This means that file access becomes
444 transparent, i.e. the MSDOS files look and behave just like all
447 If you have Windows 95 or Windows NT installed on your MSDOS
448 partitions, you should use the VFAT file system (say Y to "VFAT fs
449 support" below), or you will not be able to see the long filenames
450 generated by Windows 95 / Windows NT.
452 This option will enlarge your kernel by about 7 KB. If unsure,
453 answer Y. This will only work if you said Y to "DOS FAT fs support"
454 as well. To compile this as a module, choose M here: the module will
458 tristate "VFAT (Windows-95) fs support"
461 This option provides support for normal Windows file systems with
462 long filenames. That includes non-compressed FAT-based file systems
463 used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
464 programs from the mtools package.
466 The VFAT support enlarges your kernel by about 10 KB and it only
467 works if you said Y to the "DOS FAT fs support" above. Please read
468 the file <file:Documentation/filesystems/vfat.txt> for details. If
471 To compile this as a module, choose M here: the module will be called
474 config FAT_DEFAULT_CODEPAGE
475 int "Default codepage for FAT"
476 depends on MSDOS_FS || VFAT_FS
479 This option should be set to the codepage of your FAT filesystems.
480 It can be overridden with the "codepage" mount option.
481 See <file:Documentation/filesystems/vfat.txt> for more information.
483 config FAT_DEFAULT_IOCHARSET
484 string "Default iocharset for FAT"
488 Set this to the default input/output character set you'd
489 like FAT to use. It should probably match the character set
490 that most of your FAT filesystems use, and can be overridden
491 with the "iocharset" mount option for FAT filesystems.
492 Note that "utf8" is not recommended for FAT filesystems.
493 If unsure, you shouldn't set "utf8" here.
494 See <file:Documentation/filesystems/vfat.txt> for more information.
497 tristate "NTFS file system support"
500 NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003.
502 Saying Y or M here enables read support. There is partial, but
503 safe, write support available. For write support you must also
504 say Y to "NTFS write support" below.
506 There are also a number of user-space tools available, called
507 ntfsprogs. These include ntfsundelete and ntfsresize, that work
508 without NTFS support enabled in the kernel.
510 This is a rewrite from scratch of Linux NTFS support and replaced
511 the old NTFS code starting with Linux 2.5.11. A backport to
512 the Linux 2.4 kernel series is separately available as a patch
513 from the project web site.
515 For more information see <file:Documentation/filesystems/ntfs.txt>
516 and <http://www.linux-ntfs.org/>.
518 To compile this file system support as a module, choose M here: the
519 module will be called ntfs.
521 If you are not using Windows NT, 2000, XP or 2003 in addition to
522 Linux on your computer it is safe to say N.
525 bool "NTFS debugging support"
528 If you are experiencing any problems with the NTFS file system, say
529 Y here. This will result in additional consistency checks to be
530 performed by the driver as well as additional debugging messages to
531 be written to the system log. Note that debugging messages are
532 disabled by default. To enable them, supply the option debug_msgs=1
533 at the kernel command line when booting the kernel or as an option
534 to insmod when loading the ntfs module. Once the driver is active,
535 you can enable debugging messages by doing (as root):
536 echo 1 > /proc/sys/fs/ntfs-debug
537 Replacing the "1" with "0" would disable debug messages.
539 If you leave debugging messages disabled, this results in little
540 overhead, but enabling debug messages results in very significant
541 slowdown of the system.
543 When reporting bugs, please try to have available a full dump of
544 debugging messages while the misbehaviour was occurring.
547 bool "NTFS write support"
550 This enables the partial, but safe, write support in the NTFS driver.
552 The only supported operation is overwriting existing files, without
553 changing the file length. No file or directory creation, deletion or
554 renaming is possible. Note only non-resident files can be written to
555 so you may find that some very small files (<500 bytes or so) cannot
558 While we cannot guarantee that it will not damage any data, we have
559 so far not received a single report where the driver would have
560 damaged someones data so we assume it is perfectly safe to use.
562 Note: While write support is safe in this version (a rewrite from
563 scratch of the NTFS support), it should be noted that the old NTFS
564 write support, included in Linux 2.5.10 and before (since 1997),
567 This is currently useful with TopologiLinux. TopologiLinux is run
568 on top of any DOS/Microsoft Windows system without partitioning your
569 hard disk. Unlike other Linux distributions TopologiLinux does not
570 need its own partition. For more information see
571 <http://topologi-linux.sourceforge.net/>
573 It is perfectly safe to say N here.
578 menu "Pseudo filesystems"
580 source "fs/proc/Kconfig"
583 bool "sysfs file system support" if EMBEDDED
586 The sysfs filesystem is a virtual filesystem that the kernel uses to
587 export internal kernel objects, their attributes, and their
588 relationships to one another.
590 Users can use sysfs to ascertain useful information about the running
591 kernel, such as the devices the kernel has discovered on each bus and
592 which driver each is bound to. sysfs can also be used to tune devices
593 and other kernel subsystems.
595 Some system agents rely on the information in sysfs to operate.
596 /sbin/hotplug uses device and object attributes in sysfs to assist in
597 delegating policy decisions, like persistently naming devices.
599 sysfs is currently used by the block subsystem to mount the root
600 partition. If sysfs is disabled you must specify the boot device on
601 the kernel boot command line via its major and minor numbers. For
602 example, "root=03:01" for /dev/hda1.
604 Designers of embedded systems may wish to say N here to conserve space.
607 bool "Virtual memory file system support (former shm fs)"
609 Tmpfs is a file system which keeps all files in virtual memory.
611 Everything in tmpfs is temporary in the sense that no files will be
612 created on your hard drive. The files live in memory and swap
613 space. If you unmount a tmpfs instance, everything stored therein is
616 See <file:Documentation/filesystems/tmpfs.txt> for details.
618 config TMPFS_POSIX_ACL
619 bool "Tmpfs POSIX Access Control Lists"
623 POSIX Access Control Lists (ACLs) support permissions for users and
624 groups beyond the owner/group/world scheme.
626 To learn more about Access Control Lists, visit the POSIX ACLs for
627 Linux website <http://acl.bestbits.at/>.
629 If you don't know what Access Control Lists are, say N.
632 bool "HugeTLB file system support"
633 depends on X86 || IA64 || PPC64 || SPARC64 || (SUPERH && MMU) || \
634 (S390 && 64BIT) || BROKEN
636 hugetlbfs is a filesystem backing for HugeTLB pages, based on
637 ramfs. For architectures that support it, say Y here and read
638 <file:Documentation/vm/hugetlbpage.txt> for details.
646 tristate "Userspace-driven configuration filesystem"
649 configfs is a ram-based filesystem that provides the converse
650 of sysfs's functionality. Where sysfs is a filesystem-based
651 view of kernel objects, configfs is a filesystem-based manager
652 of kernel objects, or config_items.
654 Both sysfs and configfs can and should exist together on the
655 same system. One is not a replacement for the other.
659 menuconfig MISC_FILESYSTEMS
660 bool "Miscellaneous filesystems"
663 Say Y here to get to see options for various miscellaneous
664 filesystems, such as filesystems that came from other
667 This option alone does not add any kernel code.
669 If you say N, all options in this submenu will be skipped and
670 disabled; if unsure, say Y here.
675 tristate "ADFS file system support (EXPERIMENTAL)"
676 depends on BLOCK && EXPERIMENTAL
678 The Acorn Disc Filing System is the standard file system of the
679 RiscOS operating system which runs on Acorn's ARM-based Risc PC
680 systems and the Acorn Archimedes range of machines. If you say Y
681 here, Linux will be able to read from ADFS partitions on hard drives
682 and from ADFS-formatted floppy discs. If you also want to be able to
683 write to those devices, say Y to "ADFS write support" below.
685 The ADFS partition should be the first partition (i.e.,
686 /dev/[hs]d?1) on each of your drives. Please read the file
687 <file:Documentation/filesystems/adfs.txt> for further details.
689 To compile this code as a module, choose M here: the module will be
695 bool "ADFS write support (DANGEROUS)"
698 If you say Y here, you will be able to write to ADFS partitions on
699 hard drives and ADFS-formatted floppy disks. This is experimental
700 codes, so if you're unsure, say N.
703 tristate "Amiga FFS file system support (EXPERIMENTAL)"
704 depends on BLOCK && EXPERIMENTAL
706 The Fast File System (FFS) is the common file system used on hard
707 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
708 if you want to be able to read and write files from and to an Amiga
709 FFS partition on your hard drive. Amiga floppies however cannot be
710 read with this driver due to an incompatibility of the floppy
711 controller used in an Amiga and the standard floppy controller in
712 PCs and workstations. Read <file:Documentation/filesystems/affs.txt>
713 and <file:fs/affs/Changes>.
715 With this driver you can also mount disk files used by Bernd
716 Schmidt's Un*X Amiga Emulator
717 (<http://www.freiburg.linux.de/~uae/>).
718 If you want to do this, you will also need to say Y or M to "Loop
719 device support", above.
721 To compile this file system support as a module, choose M here: the
722 module will be called affs. If unsure, say N.
725 tristate "eCrypt filesystem layer support (EXPERIMENTAL)"
726 depends on EXPERIMENTAL && KEYS && CRYPTO && NET
728 Encrypted filesystem that operates on the VFS layer. See
729 <file:Documentation/filesystems/ecryptfs.txt> to learn more about
730 eCryptfs. Userspace components are required and can be
731 obtained from <http://ecryptfs.sf.net>.
733 To compile this file system support as a module, choose M here: the
734 module will be called ecryptfs.
737 tristate "Apple Macintosh file system support (EXPERIMENTAL)"
738 depends on BLOCK && EXPERIMENTAL
741 If you say Y here, you will be able to mount Macintosh-formatted
742 floppy disks and hard drive partitions with full read-write access.
743 Please read <file:Documentation/filesystems/hfs.txt> to learn about
744 the available mount options.
746 To compile this file system support as a module, choose M here: the
747 module will be called hfs.
750 tristate "Apple Extended HFS file system support"
755 If you say Y here, you will be able to mount extended format
756 Macintosh-formatted hard drive partitions with full read-write access.
758 This file system is often called HFS+ and was introduced with
759 MacOS 8. It includes all Mac specific filesystem data such as
760 data forks and creator codes, but it also has several UNIX
761 style features such as file ownership and permissions.
764 tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)"
765 depends on BLOCK && EXPERIMENTAL
768 The BeOS File System (BeFS) is the native file system of Be, Inc's
769 BeOS. Notable features include support for arbitrary attributes
770 on files and directories, and database-like indices on selected
771 attributes. (Also note that this driver doesn't make those features
772 available at this time). It is a 64 bit filesystem, so it supports
773 extremely large volumes and files.
775 If you use this filesystem, you should also say Y to at least one
776 of the NLS (native language support) options below.
778 If you don't know what this is about, say N.
780 To compile this as a module, choose M here: the module will be
787 If you say Y here, you can use the 'debug' mount option to enable
788 debugging output from the driver.
791 tristate "BFS file system support (EXPERIMENTAL)"
792 depends on BLOCK && EXPERIMENTAL
794 Boot File System (BFS) is a file system used under SCO UnixWare to
795 allow the bootloader access to the kernel image and other important
796 files during the boot process. It is usually mounted under /stand
797 and corresponds to the slice marked as "STAND" in the UnixWare
798 partition. You should say Y if you want to read or write the files
799 on your /stand slice from within Linux. You then also need to say Y
800 to "UnixWare slices support", below. More information about the BFS
801 file system is contained in the file
802 <file:Documentation/filesystems/bfs.txt>.
804 If you don't know what this is about, say N.
806 To compile this as a module, choose M here: the module will be called
807 bfs. Note that the file system of your root partition (the one
808 containing the directory /) cannot be compiled as a module.
813 tristate "EFS file system support (read only) (EXPERIMENTAL)"
814 depends on BLOCK && EXPERIMENTAL
816 EFS is an older file system used for non-ISO9660 CD-ROMs and hard
817 disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
818 uses the XFS file system for hard disk partitions however).
820 This implementation only offers read-only access. If you don't know
821 what all this is about, it's safe to say N. For more information
822 about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
824 To compile the EFS file system support as a module, choose M here: the
825 module will be called efs.
827 source "fs/jffs2/Kconfig"
828 # UBIFS File system configuration
829 source "fs/ubifs/Kconfig"
832 tristate "Compressed ROM file system support (cramfs)"
836 Saying Y here includes support for CramFs (Compressed ROM File
837 System). CramFs is designed to be a simple, small, and compressed
838 file system for ROM based embedded systems. CramFs is read-only,
839 limited to 256MB file systems (with 16MB files), and doesn't support
840 16/32 bits uid/gid, hard links and timestamps.
842 See <file:Documentation/filesystems/cramfs.txt> and
843 <file:fs/cramfs/README> for further information.
845 To compile this as a module, choose M here: the module will be called
846 cramfs. Note that the root file system (the one containing the
847 directory /) cannot be compiled as a module.
852 tristate "SquashFS 4.0 - Squashed file system support"
856 Saying Y here includes support for SquashFS 4.0 (a Compressed
857 Read-Only File System). Squashfs is a highly compressed read-only
858 filesystem for Linux. It uses zlib compression to compress both
859 files, inodes and directories. Inodes in the system are very small
860 and all blocks are packed to minimise data overhead. Block sizes
861 greater than 4K are supported up to a maximum of 1 Mbytes (default
862 block size 128K). SquashFS 4.0 supports 64 bit filesystems and files
863 (larger than 4GB), full uid/gid information, hard links and
866 Squashfs is intended for general read-only filesystem use, for
867 archival use (i.e. in cases where a .tar.gz file may be used), and in
868 embedded systems where low overhead is needed. Further information
869 and tools are available from http://squashfs.sourceforge.net.
871 If you want to compile this as a module ( = code which can be
872 inserted in and removed from the running kernel whenever you want),
873 say M here and read <file:Documentation/modules.txt>. The module
874 will be called squashfs. Note that the root file system (the one
875 containing the directory /) cannot be compiled as a module.
879 config SQUASHFS_EMBEDDED
881 bool "Additional option for memory-constrained systems"
885 Saying Y here allows you to specify cache size.
889 config SQUASHFS_FRAGMENT_CACHE_SIZE
890 int "Number of fragments cached" if SQUASHFS_EMBEDDED
894 By default SquashFS caches the last 3 fragments read from
895 the filesystem. Increasing this amount may mean SquashFS
896 has to re-read fragments less often from disk, at the expense
897 of extra system memory. Decreasing this amount will mean
898 SquashFS uses less memory at the expense of extra reads from disk.
900 Note there must be at least one cached fragment. Anything
901 much more than three will probably not make much difference.
904 tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
907 FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
908 file system format. VERITAS VxFS(TM) is the standard file system
909 of SCO UnixWare (and possibly others) and optionally available
910 for Sunsoft Solaris, HP-UX and many other operating systems.
911 Currently only readonly access is supported.
913 NOTE: the file system type as used by mount(1), mount(2) and
914 fstab(5) is 'vxfs' as it describes the file system format, not
917 To compile this as a module, choose M here: the module will be
918 called freevxfs. If unsure, say N.
921 tristate "Minix file system support"
924 Minix is a simple operating system used in many classes about OS's.
925 The minix file system (method to organize files on a hard disk
926 partition or a floppy disk) was the original file system for Linux,
927 but has been superseded by the second extended file system ext2fs.
928 You don't want to use the minix file system on your hard disk
929 because of certain built-in restrictions, but it is sometimes found
930 on older Linux floppy disks. This option will enlarge your kernel
931 by about 28 KB. If unsure, say N.
933 To compile this file system support as a module, choose M here: the
934 module will be called minix. Note that the file system of your root
935 partition (the one containing the directory /) cannot be compiled as
939 tristate "SonicBlue Optimized MPEG File System support"
943 This is the proprietary file system used by the Rio Karma music
944 player and ReplayTV DVR. Despite the name, this filesystem is not
945 more efficient than a standard FS for MPEG files, in fact likely
946 the opposite is true. Say Y if you have either of these devices
947 and wish to mount its disk.
949 To compile this file system support as a module, choose M here: the
950 module will be called omfs. If unsure, say N.
953 tristate "OS/2 HPFS file system support"
956 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
957 is the file system used for organizing files on OS/2 hard disk
958 partitions. Say Y if you want to be able to read files from and
959 write files to an OS/2 HPFS partition on your hard drive. OS/2
960 floppies however are in regular MSDOS format, so you don't need this
961 option in order to be able to read them. Read
962 <file:Documentation/filesystems/hpfs.txt>.
964 To compile this file system support as a module, choose M here: the
965 module will be called hpfs. If unsure, say N.
969 tristate "QNX4 file system support (read only)"
972 This is the file system used by the real-time operating systems
973 QNX 4 and QNX 6 (the latter is also called QNX RTP).
974 Further information is available at <http://www.qnx.com/>.
975 Say Y if you intend to mount QNX hard disks or floppies.
976 Unless you say Y to "QNX4FS read-write support" below, you will
977 only be able to read these file systems.
979 To compile this file system support as a module, choose M here: the
980 module will be called qnx4.
982 If you don't know whether you need it, then you don't need it:
986 bool "QNX4FS write support (DANGEROUS)"
987 depends on QNX4FS_FS && EXPERIMENTAL && BROKEN
989 Say Y if you want to test write support for QNX4 file systems.
991 It's currently broken, so for now:
995 tristate "ROM file system support"
998 This is a very small read-only file system mainly intended for
999 initial ram disks of installation disks, but it could be used for
1000 other read-only media as well. Read
1001 <file:Documentation/filesystems/romfs.txt> for details.
1003 To compile this file system support as a module, choose M here: the
1004 module will be called romfs. Note that the file system of your
1005 root partition (the one containing the directory /) cannot be a
1008 If you don't know whether you need it, then you don't need it:
1013 tristate "System V/Xenix/V7/Coherent file system support"
1016 SCO, Xenix and Coherent are commercial Unix systems for Intel
1017 machines, and Version 7 was used on the DEC PDP-11. Saying Y
1018 here would allow you to read from their floppies and hard disk
1021 If you have floppies or hard disk partitions like that, it is likely
1022 that they contain binaries from those other Unix systems; in order
1023 to run these binaries, you will want to install linux-abi which is
1024 a set of kernel modules that lets you run SCO, Xenix, Wyse,
1025 UnixWare, Dell Unix and System V programs under Linux. It is
1026 available via FTP (user: ftp) from
1027 <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
1028 NOTE: that will work only for binaries from Intel-based systems;
1029 PDP ones will have to wait until somebody ports Linux to -11 ;-)
1031 If you only intend to mount files from some other Unix over the
1032 network using NFS, you don't need the System V file system support
1033 (but you need NFS file system support obviously).
1035 Note that this option is generally not needed for floppies, since a
1036 good portable way to transport files and directories between unixes
1037 (and even other operating systems) is given by the tar program ("man
1038 tar" or preferably "info tar"). Note also that this option has
1039 nothing whatsoever to do with the option "System V IPC". Read about
1040 the System V file system in
1041 <file:Documentation/filesystems/sysv-fs.txt>.
1042 Saying Y here will enlarge your kernel by about 27 KB.
1044 To compile this as a module, choose M here: the module will be called
1047 If you haven't heard about all of this before, it's safe to say N.
1051 tristate "UFS file system support (read only)"
1054 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
1055 OpenBSD and NeXTstep) use a file system called UFS. Some System V
1056 Unixes can create and mount hard disk partitions and diskettes using
1057 this file system as well. Saying Y here will allow you to read from
1058 these partitions; if you also want to write to them, say Y to the
1059 experimental "UFS file system write support", below. Please read the
1060 file <file:Documentation/filesystems/ufs.txt> for more information.
1062 The recently released UFS2 variant (used in FreeBSD 5.x) is
1063 READ-ONLY supported.
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").
1070 When accessing NeXTstep files, you may need to convert them from the
1071 NeXT character set to the Latin1 character set; use the program
1072 recode ("info recode") for this purpose.
1074 To compile the UFS file system support as a module, choose M here: the
1075 module will be called ufs.
1077 If you haven't heard about all of this before, it's safe to say N.
1080 bool "UFS file system write support (DANGEROUS)"
1081 depends on UFS_FS && EXPERIMENTAL
1083 Say Y here if you want to try writing to UFS partitions. This is
1084 experimental, so you should back up your UFS partitions beforehand.
1087 bool "UFS debugging"
1090 If you are experiencing any problems with the UFS filesystem, say
1091 Y here. This will result in _many_ additional debugging messages to be
1092 written to the system log.
1094 endif # MISC_FILESYSTEMS
1096 menuconfig NETWORK_FILESYSTEMS
1097 bool "Network File Systems"
1101 Say Y here to get to see options for network filesystems and
1102 filesystem-related networking code, such as NFS daemon and
1103 RPCSEC security modules.
1105 This option alone does not add any kernel code.
1107 If you say N, all options in this submenu will be skipped and
1108 disabled; if unsure, say Y here.
1110 if NETWORK_FILESYSTEMS
1113 tristate "NFS client support"
1117 select NFS_ACL_SUPPORT if NFS_V3_ACL
1119 Choose Y here if you want to access files residing on other
1120 computers using Sun's Network File System protocol. To compile
1121 this file system support as a module, choose M here: the module
1124 To mount file systems exported by NFS servers, you also need to
1125 install the user space mount.nfs command which can be found in
1126 the Linux nfs-utils package, available from http://linux-nfs.org/.
1127 Information about using the mount command is available in the
1128 mount(8) man page. More detail about the Linux NFS client
1129 implementation is available via the nfs(5) man page.
1131 Below you can choose which versions of the NFS protocol are
1132 available in the kernel to mount NFS servers. Support for NFS
1133 version 2 (RFC 1094) is always available when NFS_FS is selected.
1135 To configure a system which mounts its root file system via NFS
1136 at boot time, say Y here, select "Kernel level IP
1137 autoconfiguration" in the NETWORK menu, and select "Root file
1138 system on NFS" below. You cannot compile this file system as a
1139 module in this case.
1144 bool "NFS client support for NFS version 3"
1147 This option enables support for version 3 of the NFS protocol
1148 (RFC 1813) in the kernel's NFS client.
1153 bool "NFS client support for the NFSv3 ACL protocol extension"
1156 Some NFS servers support an auxiliary NFSv3 ACL protocol that
1157 Sun added to Solaris but never became an official part of the
1158 NFS version 3 protocol. This protocol extension allows
1159 applications on NFS clients to manipulate POSIX Access Control
1160 Lists on files residing on NFS servers. NFS servers enforce
1161 ACLs on local files whether this protocol is available or not.
1163 Choose Y here if your NFS server supports the Solaris NFSv3 ACL
1164 protocol extension and you want your NFS client to allow
1165 applications to access and modify ACLs on files on the server.
1167 Most NFS servers don't support the Solaris NFSv3 ACL protocol
1168 extension. You can choose N here or specify the "noacl" mount
1169 option to prevent your NFS client from trying to use the NFSv3
1175 bool "NFS client support for NFS version 4 (EXPERIMENTAL)"
1176 depends on NFS_FS && EXPERIMENTAL
1177 select RPCSEC_GSS_KRB5
1179 This option enables support for version 4 of the NFS protocol
1180 (RFC 3530) in the kernel's NFS client.
1182 To mount NFS servers using NFSv4, you also need to install user
1183 space programs which can be found in the Linux nfs-utils package,
1184 available from http://linux-nfs.org/.
1189 bool "Root file system on NFS"
1190 depends on NFS_FS=y && IP_PNP
1192 If you want your system to mount its root file system via NFS,
1193 choose Y here. This is common practice for managing systems
1194 without local permanent storage. For details, read
1195 <file:Documentation/filesystems/nfsroot.txt>.
1197 Most people say N here.
1200 tristate "NFS server support"
1205 select NFS_ACL_SUPPORT if NFSD_V2_ACL
1207 Choose Y here if you want to allow other computers to access
1208 files residing on this system using Sun's Network File System
1209 protocol. To compile the NFS server support as a module,
1210 choose M here: the module will be called nfsd.
1212 You may choose to use a user-space NFS server instead, in which
1213 case you can choose N here.
1215 To export local file systems using NFS, you also need to install
1216 user space programs which can be found in the Linux nfs-utils
1217 package, available from http://linux-nfs.org/. More detail about
1218 the Linux NFS server implementation is available via the
1219 exports(5) man page.
1221 Below you can choose which versions of the NFS protocol are
1222 available to clients mounting the NFS server on this system.
1223 Support for NFS version 2 (RFC 1094) is always available when
1224 CONFIG_NFSD is selected.
1233 bool "NFS server support for NFS version 3"
1236 This option enables support in your system's NFS server for
1237 version 3 of the NFS protocol (RFC 1813).
1242 bool "NFS server support for the NFSv3 ACL protocol extension"
1246 Solaris NFS servers support an auxiliary NFSv3 ACL protocol that
1247 never became an official part of the NFS version 3 protocol.
1248 This protocol extension allows applications on NFS clients to
1249 manipulate POSIX Access Control Lists on files residing on NFS
1250 servers. NFS servers enforce POSIX ACLs on local files whether
1251 this protocol is available or not.
1253 This option enables support in your system's NFS server for the
1254 NFSv3 ACL protocol extension allowing NFS clients to manipulate
1255 POSIX ACLs on files exported by your system's NFS server. NFS
1256 clients which support the Solaris NFSv3 ACL protocol can then
1257 access and modify ACLs on your NFS server.
1259 To store ACLs on your NFS server, you also need to enable ACL-
1260 related CONFIG options for your local file systems of choice.
1265 bool "NFS server support for NFS version 4 (EXPERIMENTAL)"
1266 depends on NFSD && PROC_FS && EXPERIMENTAL
1269 select RPCSEC_GSS_KRB5
1271 This option enables support in your system's NFS server for
1272 version 4 of the NFS protocol (RFC 3530).
1274 To export files using NFSv4, you need to install additional user
1275 space programs which can be found in the Linux nfs-utils package,
1276 available from http://linux-nfs.org/.
1285 depends on NFSD_V3 || NFS_V3
1291 config NFS_ACL_SUPPORT
1297 depends on NFSD || NFS_FS
1306 config SUNRPC_XPRT_RDMA
1308 depends on SUNRPC && INFINIBAND && EXPERIMENTAL
1309 default SUNRPC && INFINIBAND
1311 This option enables an RPC client transport capability that
1312 allows the NFS client to mount servers via an RDMA-enabled
1315 To compile RPC client RDMA transport support as a module,
1316 choose M here: the module will be called xprtrdma.
1320 config SUNRPC_REGISTER_V4
1321 bool "Register local RPC services via rpcbind v4 (EXPERIMENTAL)"
1322 depends on SUNRPC && EXPERIMENTAL
1325 Sun added support for registering RPC services at an IPv6
1326 address by creating two new versions of the rpcbind protocol
1329 This option enables support in the kernel RPC server for
1330 registering kernel RPC services via version 4 of the rpcbind
1331 protocol. If you enable this option, you must run a portmapper
1332 daemon that supports rpcbind protocol version 4.
1334 Serving NFS over IPv6 from knfsd (the kernel's NFS server)
1335 requires that you enable this option and use a portmapper that
1336 supports rpcbind version 4.
1338 If unsure, say N to get traditional behavior (register kernel
1339 RPC services using only rpcbind version 2). Distributions
1340 using the legacy Linux portmapper daemon must say N here.
1342 config RPCSEC_GSS_KRB5
1343 tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
1344 depends on SUNRPC && EXPERIMENTAL
1351 Choose Y here to enable Secure RPC using the Kerberos version 5
1352 GSS-API mechanism (RFC 1964).
1354 Secure RPC calls with Kerberos require an auxiliary user-space
1355 daemon which may be found in the Linux nfs-utils package
1356 available from http://linux-nfs.org/. In addition, user-space
1357 Kerberos support should be installed.
1361 config RPCSEC_GSS_SPKM3
1362 tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
1363 depends on SUNRPC && EXPERIMENTAL
1371 Choose Y here to enable Secure RPC using the SPKM3 public key
1372 GSS-API mechansim (RFC 2025).
1374 Secure RPC calls with SPKM3 require an auxiliary userspace
1375 daemon which may be found in the Linux nfs-utils package
1376 available from http://linux-nfs.org/.
1381 tristate "SMB file system support (OBSOLETE, please use CIFS)"
1385 SMB (Server Message Block) is the protocol Windows for Workgroups
1386 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
1387 files and printers over local networks. Saying Y here allows you to
1388 mount their file systems (often called "shares" in this context) and
1389 access them just like any other Unix directory. Currently, this
1390 works only if the Windows machines use TCP/IP as the underlying
1391 transport protocol, and not NetBEUI. For details, read
1392 <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
1393 available from <http://www.tldp.org/docs.html#howto>.
1395 Note: if you just want your box to act as an SMB *server* and make
1396 files and printing services available to Windows clients (which need
1397 to have a TCP/IP stack), you don't need to say Y here; you can use
1398 the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
1401 General information about how to connect Linux, Windows machines and
1402 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1404 To compile the SMB support as a module, choose M here:
1405 the module will be called smbfs. Most people say N, however.
1407 config SMB_NLS_DEFAULT
1408 bool "Use a default NLS"
1411 Enabling this will make smbfs use nls translations by default. You
1412 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
1413 settings and you need to give the default nls for the SMB server as
1414 CONFIG_SMB_NLS_REMOTE.
1416 The nls settings can be changed at mount time, if your smbmount
1417 supports that, using the codepage and iocharset parameters.
1419 smbmount from samba 2.2.0 or later supports this.
1421 config SMB_NLS_REMOTE
1422 string "Default Remote NLS Option"
1423 depends on SMB_NLS_DEFAULT
1426 This setting allows you to specify a default value for which
1427 codepage the server uses. If this field is left blank no
1428 translations will be done by default. The local codepage/charset
1429 default to CONFIG_NLS_DEFAULT.
1431 The nls settings can be changed at mount time, if your smbmount
1432 supports that, using the codepage and iocharset parameters.
1434 smbmount from samba 2.2.0 or later supports this.
1436 source "fs/cifs/Kconfig"
1439 tristate "NCP file system support (to mount NetWare volumes)"
1440 depends on IPX!=n || INET
1442 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
1443 used by Novell NetWare clients to talk to file servers. It is to
1444 IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
1445 to mount NetWare file server volumes and to access them just like
1446 any other Unix directory. For details, please read the file
1447 <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
1448 the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
1450 You do not have to say Y here if you want your Linux box to act as a
1451 file *server* for Novell NetWare clients.
1453 General information about how to connect Linux, Windows machines and
1454 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1456 To compile this as a module, choose M here: the module will be called
1457 ncpfs. Say N unless you are connected to a Novell network.
1459 source "fs/ncpfs/Kconfig"
1462 tristate "Coda file system support (advanced network fs)"
1465 Coda is an advanced network file system, similar to NFS in that it
1466 enables you to mount file systems of a remote server and access them
1467 with regular Unix commands as if they were sitting on your hard
1468 disk. Coda has several advantages over NFS: support for
1469 disconnected operation (e.g. for laptops), read/write server
1470 replication, security model for authentication and encryption,
1471 persistent client caches and write back caching.
1473 If you say Y here, your Linux box will be able to act as a Coda
1474 *client*. You will need user level code as well, both for the
1475 client and server. Servers are currently user level, i.e. they need
1476 no kernel support. Please read
1477 <file:Documentation/filesystems/coda.txt> and check out the Coda
1478 home page <http://www.coda.cs.cmu.edu/>.
1480 To compile the coda client support as a module, choose M here: the
1481 module will be called coda.
1484 tristate "Andrew File System support (AFS) (EXPERIMENTAL)"
1485 depends on INET && EXPERIMENTAL
1488 If you say Y here, you will get an experimental Andrew File System
1489 driver. It currently only supports unsecured read-only AFS access.
1491 See <file:Documentation/filesystems/afs.txt> for more information.
1496 bool "AFS dynamic debugging"
1499 Say Y here to make runtime controllable debugging messages appear.
1501 See <file:Documentation/filesystems/afs.txt> for more information.
1506 tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
1507 depends on INET && NET_9P && EXPERIMENTAL
1509 If you say Y here, you will get experimental support for
1510 Plan 9 resource sharing via the 9P2000 protocol.
1512 See <http://v9fs.sf.net> for more information.
1516 endif # NETWORK_FILESYSTEMS
1519 menu "Partition Types"
1521 source "fs/partitions/Kconfig"
1526 source "fs/nls/Kconfig"
1527 source "fs/dlm/Kconfig"