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.
271 config OCFS2_FS_POSIX_ACL
272 bool "OCFS2 POSIX Access Control Lists"
277 Posix Access Control Lists (ACLs) support permissions for users and
278 groups beyond the owner/group/world scheme.
282 source "fs/notify/Kconfig"
287 If you say Y here, you will be able to set per user limits for disk
288 usage (also called disk quotas). Currently, it works for the
289 ext2, ext3, and reiserfs file system. ext3 also supports journalled
290 quotas for which you don't need to run quotacheck(8) after an unclean
292 For further details, read the Quota mini-HOWTO, available from
293 <http://www.tldp.org/docs.html#howto>, or the documentation provided
294 with the quota tools. Probably the quota support is only useful for
295 multi user systems. If unsure, say N.
297 config QUOTA_NETLINK_INTERFACE
298 bool "Report quota messages through netlink interface"
299 depends on QUOTA && NET
301 If you say Y here, quota warnings (about exceeding softlimit, reaching
302 hardlimit, etc.) will be reported through netlink interface. If unsure,
305 config PRINT_QUOTA_WARNING
306 bool "Print quota warnings to console (OBSOLETE)"
310 If you say Y here, quota warnings (about exceeding softlimit, reaching
311 hardlimit, etc.) will be printed to the process' controlling terminal.
312 Note that this behavior is currently deprecated and may go away in
313 future. Please use notification via netlink socket instead.
316 tristate "Old quota format support"
319 This quota format was (is) used by kernels earlier than 2.4.22. If
320 you have quota working and you don't want to convert to new quota
324 tristate "Quota format v2 support"
327 This quota format allows using quotas with 32-bit UIDs/GIDs. If you
328 need this functionality say Y here.
332 depends on XFS_QUOTA || QUOTA
336 tristate "Kernel automounter support"
338 The automounter is a tool to automatically mount remote file systems
339 on demand. This implementation is partially kernel-based to reduce
340 overhead in the already-mounted case; this is unlike the BSD
341 automounter (amd), which is a pure user space daemon.
343 To use the automounter you need the user-space tools from the autofs
344 package; you can find the location in <file:Documentation/Changes>.
345 You also want to answer Y to "NFS file system support", below.
347 If you want to use the newer version of the automounter with more
348 features, say N here and say Y to "Kernel automounter v4 support",
351 To compile this support as a module, choose M here: the module will be
354 If you are not a part of a fairly large, distributed network, you
355 probably do not need an automounter, and can say N here.
358 tristate "Kernel automounter version 4 support (also supports v3)"
360 The automounter is a tool to automatically mount remote file systems
361 on demand. This implementation is partially kernel-based to reduce
362 overhead in the already-mounted case; this is unlike the BSD
363 automounter (amd), which is a pure user space daemon.
365 To use the automounter you need the user-space tools from
366 <ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4/>; you also
367 want to answer Y to "NFS file system support", below.
369 To compile this support as a module, choose M here: the module will be
370 called autofs4. You will need to add "alias autofs autofs4" to your
371 modules configuration file.
373 If you are not a part of a fairly large, distributed network or
374 don't have a laptop which needs to dynamically reconfigure to the
375 local network, you probably do not need an automounter, and can say
379 tristate "FUSE (Filesystem in Userspace) support"
381 With FUSE it is possible to implement a fully functional filesystem
382 in a userspace program.
384 There's also companion library: libfuse. This library along with
385 utilities is available from the FUSE homepage:
386 <http://fuse.sourceforge.net/>
388 See <file:Documentation/filesystems/fuse.txt> for more information.
389 See <file:Documentation/Changes> for needed library/utility version.
391 If you want to develop a userspace FS, or if you want to use
392 a filesystem based on FUSE, answer Y or M.
399 menu "CD-ROM/DVD Filesystems"
402 tristate "ISO 9660 CDROM file system support"
404 This is the standard file system used on CD-ROMs. It was previously
405 known as "High Sierra File System" and is called "hsfs" on other
406 Unix systems. The so-called Rock-Ridge extensions which allow for
407 long Unix filenames and symbolic links are also supported by this
408 driver. If you have a CD-ROM drive and want to do more with it than
409 just listen to audio CDs and watch its LEDs, say Y (and read
410 <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO,
411 available from <http://www.tldp.org/docs.html#howto>), thereby
412 enlarging your kernel by about 27 KB; otherwise say N.
414 To compile this file system support as a module, choose M here: the
415 module will be called isofs.
418 bool "Microsoft Joliet CDROM extensions"
419 depends on ISO9660_FS
422 Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system
423 which allows for long filenames in unicode format (unicode is the
424 new 16 bit character code, successor to ASCII, which encodes the
425 characters of almost all languages of the world; see
426 <http://www.unicode.org/> for more information). Say Y here if you
427 want to be able to read Joliet CD-ROMs under Linux.
430 bool "Transparent decompression extension"
431 depends on ISO9660_FS
434 This is a Linux-specific extension to RockRidge which lets you store
435 data in compressed form on a CD-ROM and have it transparently
436 decompressed when the CD-ROM is accessed. See
437 <http://www.kernel.org/pub/linux/utils/fs/zisofs/> for the tools
438 necessary to create such a filesystem. Say Y here if you want to be
439 able to read such compressed CD-ROMs.
442 tristate "UDF file system support"
445 This is the new file system used on some CD-ROMs and DVDs. Say Y if
446 you intend to mount DVD discs or CDRW's written in packet mode, or
447 if written to by other UDF utilities, such as DirectCD.
448 Please read <file:Documentation/filesystems/udf.txt>.
450 To compile this file system support as a module, choose M here: the
451 module will be called udf.
458 depends on (UDF_FS=m && NLS) || (UDF_FS=y && NLS=y)
464 menu "DOS/FAT/NT Filesystems"
470 If you want to use one of the FAT-based file systems (the MS-DOS and
471 VFAT (Windows 95) file systems), then you must say Y or M here
472 to include FAT support. You will then be able to mount partitions or
473 diskettes with FAT-based file systems and transparently access the
474 files on them, i.e. MSDOS files will look and behave just like all
477 This FAT support is not a file system in itself, it only provides
478 the foundation for the other file systems. You will have to say Y or
479 M to at least one of "MSDOS fs support" or "VFAT fs support" in
480 order to make use of it.
482 Another way to read and write MSDOS floppies and hard drive
483 partitions from within Linux (but not transparently) is with the
484 mtools ("man mtools") program suite. You don't need to say Y here in
487 If you need to move large files on floppies between a DOS and a
488 Linux box, say Y here, mount the floppy under Linux with an MSDOS
489 file system and use GNU tar's M option. GNU tar is a program
490 available for Unix and DOS ("man tar" or "info tar").
492 The FAT support will enlarge your kernel by about 37 KB. If unsure,
495 To compile this as a module, choose M here: the module will be called
496 fat. Note that if you compile the FAT support as a module, you
497 cannot compile any of the FAT-based file systems into the kernel
498 -- they will have to be modules as well.
501 tristate "MSDOS fs support"
504 This allows you to mount MSDOS partitions of your hard drive (unless
505 they are compressed; to access compressed MSDOS partitions under
506 Linux, you can either use the DOS emulator DOSEMU, described in the
507 DOSEMU-HOWTO, available from
508 <http://www.tldp.org/docs.html#howto>, or try dmsdosfs in
509 <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you
510 intend to use dosemu with a non-compressed MSDOS partition, say Y
511 here) and MSDOS floppies. This means that file access becomes
512 transparent, i.e. the MSDOS files look and behave just like all
515 If you have Windows 95 or Windows NT installed on your MSDOS
516 partitions, you should use the VFAT file system (say Y to "VFAT fs
517 support" below), or you will not be able to see the long filenames
518 generated by Windows 95 / Windows NT.
520 This option will enlarge your kernel by about 7 KB. If unsure,
521 answer Y. This will only work if you said Y to "DOS FAT fs support"
522 as well. To compile this as a module, choose M here: the module will
526 tristate "VFAT (Windows-95) fs support"
529 This option provides support for normal Windows file systems with
530 long filenames. That includes non-compressed FAT-based file systems
531 used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
532 programs from the mtools package.
534 The VFAT support enlarges your kernel by about 10 KB and it only
535 works if you said Y to the "DOS FAT fs support" above. Please read
536 the file <file:Documentation/filesystems/vfat.txt> for details. If
539 To compile this as a module, choose M here: the module will be called
542 config FAT_DEFAULT_CODEPAGE
543 int "Default codepage for FAT"
544 depends on MSDOS_FS || VFAT_FS
547 This option should be set to the codepage of your FAT filesystems.
548 It can be overridden with the "codepage" mount option.
549 See <file:Documentation/filesystems/vfat.txt> for more information.
551 config FAT_DEFAULT_IOCHARSET
552 string "Default iocharset for FAT"
556 Set this to the default input/output character set you'd
557 like FAT to use. It should probably match the character set
558 that most of your FAT filesystems use, and can be overridden
559 with the "iocharset" mount option for FAT filesystems.
560 Note that "utf8" is not recommended for FAT filesystems.
561 If unsure, you shouldn't set "utf8" here.
562 See <file:Documentation/filesystems/vfat.txt> for more information.
565 tristate "NTFS file system support"
568 NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003.
570 Saying Y or M here enables read support. There is partial, but
571 safe, write support available. For write support you must also
572 say Y to "NTFS write support" below.
574 There are also a number of user-space tools available, called
575 ntfsprogs. These include ntfsundelete and ntfsresize, that work
576 without NTFS support enabled in the kernel.
578 This is a rewrite from scratch of Linux NTFS support and replaced
579 the old NTFS code starting with Linux 2.5.11. A backport to
580 the Linux 2.4 kernel series is separately available as a patch
581 from the project web site.
583 For more information see <file:Documentation/filesystems/ntfs.txt>
584 and <http://www.linux-ntfs.org/>.
586 To compile this file system support as a module, choose M here: the
587 module will be called ntfs.
589 If you are not using Windows NT, 2000, XP or 2003 in addition to
590 Linux on your computer it is safe to say N.
593 bool "NTFS debugging support"
596 If you are experiencing any problems with the NTFS file system, say
597 Y here. This will result in additional consistency checks to be
598 performed by the driver as well as additional debugging messages to
599 be written to the system log. Note that debugging messages are
600 disabled by default. To enable them, supply the option debug_msgs=1
601 at the kernel command line when booting the kernel or as an option
602 to insmod when loading the ntfs module. Once the driver is active,
603 you can enable debugging messages by doing (as root):
604 echo 1 > /proc/sys/fs/ntfs-debug
605 Replacing the "1" with "0" would disable debug messages.
607 If you leave debugging messages disabled, this results in little
608 overhead, but enabling debug messages results in very significant
609 slowdown of the system.
611 When reporting bugs, please try to have available a full dump of
612 debugging messages while the misbehaviour was occurring.
615 bool "NTFS write support"
618 This enables the partial, but safe, write support in the NTFS driver.
620 The only supported operation is overwriting existing files, without
621 changing the file length. No file or directory creation, deletion or
622 renaming is possible. Note only non-resident files can be written to
623 so you may find that some very small files (<500 bytes or so) cannot
626 While we cannot guarantee that it will not damage any data, we have
627 so far not received a single report where the driver would have
628 damaged someones data so we assume it is perfectly safe to use.
630 Note: While write support is safe in this version (a rewrite from
631 scratch of the NTFS support), it should be noted that the old NTFS
632 write support, included in Linux 2.5.10 and before (since 1997),
635 This is currently useful with TopologiLinux. TopologiLinux is run
636 on top of any DOS/Microsoft Windows system without partitioning your
637 hard disk. Unlike other Linux distributions TopologiLinux does not
638 need its own partition. For more information see
639 <http://topologi-linux.sourceforge.net/>
641 It is perfectly safe to say N here.
646 menu "Pseudo filesystems"
648 source "fs/proc/Kconfig"
651 bool "sysfs file system support" if EMBEDDED
654 The sysfs filesystem is a virtual filesystem that the kernel uses to
655 export internal kernel objects, their attributes, and their
656 relationships to one another.
658 Users can use sysfs to ascertain useful information about the running
659 kernel, such as the devices the kernel has discovered on each bus and
660 which driver each is bound to. sysfs can also be used to tune devices
661 and other kernel subsystems.
663 Some system agents rely on the information in sysfs to operate.
664 /sbin/hotplug uses device and object attributes in sysfs to assist in
665 delegating policy decisions, like persistently naming devices.
667 sysfs is currently used by the block subsystem to mount the root
668 partition. If sysfs is disabled you must specify the boot device on
669 the kernel boot command line via its major and minor numbers. For
670 example, "root=03:01" for /dev/hda1.
672 Designers of embedded systems may wish to say N here to conserve space.
675 bool "Virtual memory file system support (former shm fs)"
677 Tmpfs is a file system which keeps all files in virtual memory.
679 Everything in tmpfs is temporary in the sense that no files will be
680 created on your hard drive. The files live in memory and swap
681 space. If you unmount a tmpfs instance, everything stored therein is
684 See <file:Documentation/filesystems/tmpfs.txt> for details.
686 config TMPFS_POSIX_ACL
687 bool "Tmpfs POSIX Access Control Lists"
691 POSIX Access Control Lists (ACLs) support permissions for users and
692 groups beyond the owner/group/world scheme.
694 To learn more about Access Control Lists, visit the POSIX ACLs for
695 Linux website <http://acl.bestbits.at/>.
697 If you don't know what Access Control Lists are, say N.
700 bool "HugeTLB file system support"
701 depends on X86 || IA64 || PPC64 || SPARC64 || (SUPERH && MMU) || \
702 (S390 && 64BIT) || BROKEN
704 hugetlbfs is a filesystem backing for HugeTLB pages, based on
705 ramfs. For architectures that support it, say Y here and read
706 <file:Documentation/vm/hugetlbpage.txt> for details.
714 tristate "Userspace-driven configuration filesystem"
717 configfs is a ram-based filesystem that provides the converse
718 of sysfs's functionality. Where sysfs is a filesystem-based
719 view of kernel objects, configfs is a filesystem-based manager
720 of kernel objects, or config_items.
722 Both sysfs and configfs can and should exist together on the
723 same system. One is not a replacement for the other.
727 menu "Miscellaneous filesystems"
730 tristate "ADFS file system support (EXPERIMENTAL)"
731 depends on BLOCK && EXPERIMENTAL
733 The Acorn Disc Filing System is the standard file system of the
734 RiscOS operating system which runs on Acorn's ARM-based Risc PC
735 systems and the Acorn Archimedes range of machines. If you say Y
736 here, Linux will be able to read from ADFS partitions on hard drives
737 and from ADFS-formatted floppy discs. If you also want to be able to
738 write to those devices, say Y to "ADFS write support" below.
740 The ADFS partition should be the first partition (i.e.,
741 /dev/[hs]d?1) on each of your drives. Please read the file
742 <file:Documentation/filesystems/adfs.txt> for further details.
744 To compile this code as a module, choose M here: the module will be
750 bool "ADFS write support (DANGEROUS)"
753 If you say Y here, you will be able to write to ADFS partitions on
754 hard drives and ADFS-formatted floppy disks. This is experimental
755 codes, so if you're unsure, say N.
758 tristate "Amiga FFS file system support (EXPERIMENTAL)"
759 depends on BLOCK && EXPERIMENTAL
761 The Fast File System (FFS) is the common file system used on hard
762 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
763 if you want to be able to read and write files from and to an Amiga
764 FFS partition on your hard drive. Amiga floppies however cannot be
765 read with this driver due to an incompatibility of the floppy
766 controller used in an Amiga and the standard floppy controller in
767 PCs and workstations. Read <file:Documentation/filesystems/affs.txt>
768 and <file:fs/affs/Changes>.
770 With this driver you can also mount disk files used by Bernd
771 Schmidt's Un*X Amiga Emulator
772 (<http://www.freiburg.linux.de/~uae/>).
773 If you want to do this, you will also need to say Y or M to "Loop
774 device support", above.
776 To compile this file system support as a module, choose M here: the
777 module will be called affs. If unsure, say N.
780 tristate "eCrypt filesystem layer support (EXPERIMENTAL)"
781 depends on EXPERIMENTAL && KEYS && CRYPTO && NET
783 Encrypted filesystem that operates on the VFS layer. See
784 <file:Documentation/filesystems/ecryptfs.txt> to learn more about
785 eCryptfs. Userspace components are required and can be
786 obtained from <http://ecryptfs.sf.net>.
788 To compile this file system support as a module, choose M here: the
789 module will be called ecryptfs.
792 tristate "Apple Macintosh file system support (EXPERIMENTAL)"
793 depends on BLOCK && EXPERIMENTAL
796 If you say Y here, you will be able to mount Macintosh-formatted
797 floppy disks and hard drive partitions with full read-write access.
798 Please read <file:Documentation/filesystems/hfs.txt> to learn about
799 the available mount options.
801 To compile this file system support as a module, choose M here: the
802 module will be called hfs.
805 tristate "Apple Extended HFS file system support"
810 If you say Y here, you will be able to mount extended format
811 Macintosh-formatted hard drive partitions with full read-write access.
813 This file system is often called HFS+ and was introduced with
814 MacOS 8. It includes all Mac specific filesystem data such as
815 data forks and creator codes, but it also has several UNIX
816 style features such as file ownership and permissions.
819 tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)"
820 depends on BLOCK && EXPERIMENTAL
823 The BeOS File System (BeFS) is the native file system of Be, Inc's
824 BeOS. Notable features include support for arbitrary attributes
825 on files and directories, and database-like indices on selected
826 attributes. (Also note that this driver doesn't make those features
827 available at this time). It is a 64 bit filesystem, so it supports
828 extremely large volumes and files.
830 If you use this filesystem, you should also say Y to at least one
831 of the NLS (native language support) options below.
833 If you don't know what this is about, say N.
835 To compile this as a module, choose M here: the module will be
842 If you say Y here, you can use the 'debug' mount option to enable
843 debugging output from the driver.
846 tristate "BFS file system support (EXPERIMENTAL)"
847 depends on BLOCK && EXPERIMENTAL
849 Boot File System (BFS) is a file system used under SCO UnixWare to
850 allow the bootloader access to the kernel image and other important
851 files during the boot process. It is usually mounted under /stand
852 and corresponds to the slice marked as "STAND" in the UnixWare
853 partition. You should say Y if you want to read or write the files
854 on your /stand slice from within Linux. You then also need to say Y
855 to "UnixWare slices support", below. More information about the BFS
856 file system is contained in the file
857 <file:Documentation/filesystems/bfs.txt>.
859 If you don't know what this is about, say N.
861 To compile this as a module, choose M here: the module will be called
862 bfs. Note that the file system of your root partition (the one
863 containing the directory /) cannot be compiled as a module.
868 tristate "EFS file system support (read only) (EXPERIMENTAL)"
869 depends on BLOCK && EXPERIMENTAL
871 EFS is an older file system used for non-ISO9660 CD-ROMs and hard
872 disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
873 uses the XFS file system for hard disk partitions however).
875 This implementation only offers read-only access. If you don't know
876 what all this is about, it's safe to say N. For more information
877 about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
879 To compile the EFS file system support as a module, choose M here: the
880 module will be called efs.
882 source "fs/jffs2/Kconfig"
883 # UBIFS File system configuration
884 source "fs/ubifs/Kconfig"
887 tristate "Compressed ROM file system support (cramfs)"
891 Saying Y here includes support for CramFs (Compressed ROM File
892 System). CramFs is designed to be a simple, small, and compressed
893 file system for ROM based embedded systems. CramFs is read-only,
894 limited to 256MB file systems (with 16MB files), and doesn't support
895 16/32 bits uid/gid, hard links and timestamps.
897 See <file:Documentation/filesystems/cramfs.txt> and
898 <file:fs/cramfs/README> for further information.
900 To compile this as a module, choose M here: the module will be called
901 cramfs. Note that the root file system (the one containing the
902 directory /) cannot be compiled as a module.
907 tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
910 FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
911 file system format. VERITAS VxFS(TM) is the standard file system
912 of SCO UnixWare (and possibly others) and optionally available
913 for Sunsoft Solaris, HP-UX and many other operating systems.
914 Currently only readonly access is supported.
916 NOTE: the file system type as used by mount(1), mount(2) and
917 fstab(5) is 'vxfs' as it describes the file system format, not
920 To compile this as a module, choose M here: the module will be
921 called freevxfs. If unsure, say N.
924 tristate "Minix file system support"
927 Minix is a simple operating system used in many classes about OS's.
928 The minix file system (method to organize files on a hard disk
929 partition or a floppy disk) was the original file system for Linux,
930 but has been superseded by the second extended file system ext2fs.
931 You don't want to use the minix file system on your hard disk
932 because of certain built-in restrictions, but it is sometimes found
933 on older Linux floppy disks. This option will enlarge your kernel
934 by about 28 KB. If unsure, say N.
936 To compile this file system support as a module, choose M here: the
937 module will be called minix. Note that the file system of your root
938 partition (the one containing the directory /) cannot be compiled as
942 tristate "SonicBlue Optimized MPEG File System support"
946 This is the proprietary file system used by the Rio Karma music
947 player and ReplayTV DVR. Despite the name, this filesystem is not
948 more efficient than a standard FS for MPEG files, in fact likely
949 the opposite is true. Say Y if you have either of these devices
950 and wish to mount its disk.
952 To compile this file system support as a module, choose M here: the
953 module will be called omfs. If unsure, say N.
956 tristate "OS/2 HPFS file system support"
959 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
960 is the file system used for organizing files on OS/2 hard disk
961 partitions. Say Y if you want to be able to read files from and
962 write files to an OS/2 HPFS partition on your hard drive. OS/2
963 floppies however are in regular MSDOS format, so you don't need this
964 option in order to be able to read them. Read
965 <file:Documentation/filesystems/hpfs.txt>.
967 To compile this file system support as a module, choose M here: the
968 module will be called hpfs. If unsure, say N.
972 tristate "QNX4 file system support (read only)"
975 This is the file system used by the real-time operating systems
976 QNX 4 and QNX 6 (the latter is also called QNX RTP).
977 Further information is available at <http://www.qnx.com/>.
978 Say Y if you intend to mount QNX hard disks or floppies.
979 Unless you say Y to "QNX4FS read-write support" below, you will
980 only be able to read these file systems.
982 To compile this file system support as a module, choose M here: the
983 module will be called qnx4.
985 If you don't know whether you need it, then you don't need it:
989 bool "QNX4FS write support (DANGEROUS)"
990 depends on QNX4FS_FS && EXPERIMENTAL && BROKEN
992 Say Y if you want to test write support for QNX4 file systems.
994 It's currently broken, so for now:
998 tristate "ROM file system support"
1001 This is a very small read-only file system mainly intended for
1002 initial ram disks of installation disks, but it could be used for
1003 other read-only media as well. Read
1004 <file:Documentation/filesystems/romfs.txt> for details.
1006 To compile this file system support as a module, choose M here: the
1007 module will be called romfs. Note that the file system of your
1008 root partition (the one containing the directory /) cannot be a
1011 If you don't know whether you need it, then you don't need it:
1016 tristate "System V/Xenix/V7/Coherent file system support"
1019 SCO, Xenix and Coherent are commercial Unix systems for Intel
1020 machines, and Version 7 was used on the DEC PDP-11. Saying Y
1021 here would allow you to read from their floppies and hard disk
1024 If you have floppies or hard disk partitions like that, it is likely
1025 that they contain binaries from those other Unix systems; in order
1026 to run these binaries, you will want to install linux-abi which is
1027 a set of kernel modules that lets you run SCO, Xenix, Wyse,
1028 UnixWare, Dell Unix and System V programs under Linux. It is
1029 available via FTP (user: ftp) from
1030 <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
1031 NOTE: that will work only for binaries from Intel-based systems;
1032 PDP ones will have to wait until somebody ports Linux to -11 ;-)
1034 If you only intend to mount files from some other Unix over the
1035 network using NFS, you don't need the System V file system support
1036 (but you need NFS file system support obviously).
1038 Note that this option is generally not needed for floppies, since a
1039 good portable way to transport files and directories between unixes
1040 (and even other operating systems) is given by the tar program ("man
1041 tar" or preferably "info tar"). Note also that this option has
1042 nothing whatsoever to do with the option "System V IPC". Read about
1043 the System V file system in
1044 <file:Documentation/filesystems/sysv-fs.txt>.
1045 Saying Y here will enlarge your kernel by about 27 KB.
1047 To compile this as a module, choose M here: the module will be called
1050 If you haven't heard about all of this before, it's safe to say N.
1054 tristate "UFS file system support (read only)"
1057 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
1058 OpenBSD and NeXTstep) use a file system called UFS. Some System V
1059 Unixes can create and mount hard disk partitions and diskettes using
1060 this file system as well. Saying Y here will allow you to read from
1061 these partitions; if you also want to write to them, say Y to the
1062 experimental "UFS file system write support", below. Please read the
1063 file <file:Documentation/filesystems/ufs.txt> for more information.
1065 The recently released UFS2 variant (used in FreeBSD 5.x) is
1066 READ-ONLY supported.
1068 Note that this option is generally not needed for floppies, since a
1069 good portable way to transport files and directories between unixes
1070 (and even other operating systems) is given by the tar program ("man
1071 tar" or preferably "info tar").
1073 When accessing NeXTstep files, you may need to convert them from the
1074 NeXT character set to the Latin1 character set; use the program
1075 recode ("info recode") for this purpose.
1077 To compile the UFS file system support as a module, choose M here: the
1078 module will be called ufs.
1080 If you haven't heard about all of this before, it's safe to say N.
1083 bool "UFS file system write support (DANGEROUS)"
1084 depends on UFS_FS && EXPERIMENTAL
1086 Say Y here if you want to try writing to UFS partitions. This is
1087 experimental, so you should back up your UFS partitions beforehand.
1090 bool "UFS debugging"
1093 If you are experiencing any problems with the UFS filesystem, say
1094 Y here. This will result in _many_ additional debugging messages to be
1095 written to the system log.
1099 menuconfig NETWORK_FILESYSTEMS
1100 bool "Network File Systems"
1104 Say Y here to get to see options for network filesystems and
1105 filesystem-related networking code, such as NFS daemon and
1106 RPCSEC security modules.
1108 This option alone does not add any kernel code.
1110 If you say N, all options in this submenu will be skipped and
1111 disabled; if unsure, say Y here.
1113 if NETWORK_FILESYSTEMS
1116 tristate "NFS client support"
1120 select NFS_ACL_SUPPORT if NFS_V3_ACL
1122 Choose Y here if you want to access files residing on other
1123 computers using Sun's Network File System protocol. To compile
1124 this file system support as a module, choose M here: the module
1127 To mount file systems exported by NFS servers, you also need to
1128 install the user space mount.nfs command which can be found in
1129 the Linux nfs-utils package, available from http://linux-nfs.org/.
1130 Information about using the mount command is available in the
1131 mount(8) man page. More detail about the Linux NFS client
1132 implementation is available via the nfs(5) man page.
1134 Below you can choose which versions of the NFS protocol are
1135 available in the kernel to mount NFS servers. Support for NFS
1136 version 2 (RFC 1094) is always available when NFS_FS is selected.
1138 To configure a system which mounts its root file system via NFS
1139 at boot time, say Y here, select "Kernel level IP
1140 autoconfiguration" in the NETWORK menu, and select "Root file
1141 system on NFS" below. You cannot compile this file system as a
1142 module in this case.
1147 bool "NFS client support for NFS version 3"
1150 This option enables support for version 3 of the NFS protocol
1151 (RFC 1813) in the kernel's NFS client.
1156 bool "NFS client support for the NFSv3 ACL protocol extension"
1159 Some NFS servers support an auxiliary NFSv3 ACL protocol that
1160 Sun added to Solaris but never became an official part of the
1161 NFS version 3 protocol. This protocol extension allows
1162 applications on NFS clients to manipulate POSIX Access Control
1163 Lists on files residing on NFS servers. NFS servers enforce
1164 ACLs on local files whether this protocol is available or not.
1166 Choose Y here if your NFS server supports the Solaris NFSv3 ACL
1167 protocol extension and you want your NFS client to allow
1168 applications to access and modify ACLs on files on the server.
1170 Most NFS servers don't support the Solaris NFSv3 ACL protocol
1171 extension. You can choose N here or specify the "noacl" mount
1172 option to prevent your NFS client from trying to use the NFSv3
1178 bool "NFS client support for NFS version 4 (EXPERIMENTAL)"
1179 depends on NFS_FS && EXPERIMENTAL
1180 select RPCSEC_GSS_KRB5
1182 This option enables support for version 4 of the NFS protocol
1183 (RFC 3530) in the kernel's NFS client.
1185 To mount NFS servers using NFSv4, you also need to install user
1186 space programs which can be found in the Linux nfs-utils package,
1187 available from http://linux-nfs.org/.
1192 bool "Root file system on NFS"
1193 depends on NFS_FS=y && IP_PNP
1195 If you want your system to mount its root file system via NFS,
1196 choose Y here. This is common practice for managing systems
1197 without local permanent storage. For details, read
1198 <file:Documentation/filesystems/nfsroot.txt>.
1200 Most people say N here.
1203 tristate "NFS server support"
1208 select NFS_ACL_SUPPORT if NFSD_V2_ACL
1210 Choose Y here if you want to allow other computers to access
1211 files residing on this system using Sun's Network File System
1212 protocol. To compile the NFS server support as a module,
1213 choose M here: the module will be called nfsd.
1215 You may choose to use a user-space NFS server instead, in which
1216 case you can choose N here.
1218 To export local file systems using NFS, you also need to install
1219 user space programs which can be found in the Linux nfs-utils
1220 package, available from http://linux-nfs.org/. More detail about
1221 the Linux NFS server implementation is available via the
1222 exports(5) man page.
1224 Below you can choose which versions of the NFS protocol are
1225 available to clients mounting the NFS server on this system.
1226 Support for NFS version 2 (RFC 1094) is always available when
1227 CONFIG_NFSD is selected.
1236 bool "NFS server support for NFS version 3"
1239 This option enables support in your system's NFS server for
1240 version 3 of the NFS protocol (RFC 1813).
1245 bool "NFS server support for the NFSv3 ACL protocol extension"
1249 Solaris NFS servers support an auxiliary NFSv3 ACL protocol that
1250 never became an official part of the NFS version 3 protocol.
1251 This protocol extension allows applications on NFS clients to
1252 manipulate POSIX Access Control Lists on files residing on NFS
1253 servers. NFS servers enforce POSIX ACLs on local files whether
1254 this protocol is available or not.
1256 This option enables support in your system's NFS server for the
1257 NFSv3 ACL protocol extension allowing NFS clients to manipulate
1258 POSIX ACLs on files exported by your system's NFS server. NFS
1259 clients which support the Solaris NFSv3 ACL protocol can then
1260 access and modify ACLs on your NFS server.
1262 To store ACLs on your NFS server, you also need to enable ACL-
1263 related CONFIG options for your local file systems of choice.
1268 bool "NFS server support for NFS version 4 (EXPERIMENTAL)"
1269 depends on NFSD && PROC_FS && EXPERIMENTAL
1272 select RPCSEC_GSS_KRB5
1274 This option enables support in your system's NFS server for
1275 version 4 of the NFS protocol (RFC 3530).
1277 To export files using NFSv4, you need to install additional user
1278 space programs which can be found in the Linux nfs-utils package,
1279 available from http://linux-nfs.org/.
1288 depends on NFSD_V3 || NFS_V3
1294 config NFS_ACL_SUPPORT
1300 depends on NFSD || NFS_FS
1309 config SUNRPC_XPRT_RDMA
1311 depends on SUNRPC && INFINIBAND && EXPERIMENTAL
1312 default SUNRPC && INFINIBAND
1314 This option enables an RPC client transport capability that
1315 allows the NFS client to mount servers via an RDMA-enabled
1318 To compile RPC client RDMA transport support as a module,
1319 choose M here: the module will be called xprtrdma.
1323 config SUNRPC_REGISTER_V4
1324 bool "Register local RPC services via rpcbind v4 (EXPERIMENTAL)"
1325 depends on SUNRPC && EXPERIMENTAL
1328 Sun added support for registering RPC services at an IPv6
1329 address by creating two new versions of the rpcbind protocol
1332 This option enables support in the kernel RPC server for
1333 registering kernel RPC services via version 4 of the rpcbind
1334 protocol. If you enable this option, you must run a portmapper
1335 daemon that supports rpcbind protocol version 4.
1337 Serving NFS over IPv6 from knfsd (the kernel's NFS server)
1338 requires that you enable this option and use a portmapper that
1339 supports rpcbind version 4.
1341 If unsure, say N to get traditional behavior (register kernel
1342 RPC services using only rpcbind version 2). Distributions
1343 using the legacy Linux portmapper daemon must say N here.
1345 config RPCSEC_GSS_KRB5
1346 tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
1347 depends on SUNRPC && EXPERIMENTAL
1354 Choose Y here to enable Secure RPC using the Kerberos version 5
1355 GSS-API mechanism (RFC 1964).
1357 Secure RPC calls with Kerberos require an auxiliary user-space
1358 daemon which may be found in the Linux nfs-utils package
1359 available from http://linux-nfs.org/. In addition, user-space
1360 Kerberos support should be installed.
1364 config RPCSEC_GSS_SPKM3
1365 tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
1366 depends on SUNRPC && EXPERIMENTAL
1374 Choose Y here to enable Secure RPC using the SPKM3 public key
1375 GSS-API mechansim (RFC 2025).
1377 Secure RPC calls with SPKM3 require an auxiliary userspace
1378 daemon which may be found in the Linux nfs-utils package
1379 available from http://linux-nfs.org/.
1384 tristate "SMB file system support (OBSOLETE, please use CIFS)"
1388 SMB (Server Message Block) is the protocol Windows for Workgroups
1389 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
1390 files and printers over local networks. Saying Y here allows you to
1391 mount their file systems (often called "shares" in this context) and
1392 access them just like any other Unix directory. Currently, this
1393 works only if the Windows machines use TCP/IP as the underlying
1394 transport protocol, and not NetBEUI. For details, read
1395 <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
1396 available from <http://www.tldp.org/docs.html#howto>.
1398 Note: if you just want your box to act as an SMB *server* and make
1399 files and printing services available to Windows clients (which need
1400 to have a TCP/IP stack), you don't need to say Y here; you can use
1401 the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
1404 General information about how to connect Linux, Windows machines and
1405 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1407 To compile the SMB support as a module, choose M here:
1408 the module will be called smbfs. Most people say N, however.
1410 config SMB_NLS_DEFAULT
1411 bool "Use a default NLS"
1414 Enabling this will make smbfs use nls translations by default. You
1415 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
1416 settings and you need to give the default nls for the SMB server as
1417 CONFIG_SMB_NLS_REMOTE.
1419 The nls settings can be changed at mount time, if your smbmount
1420 supports that, using the codepage and iocharset parameters.
1422 smbmount from samba 2.2.0 or later supports this.
1424 config SMB_NLS_REMOTE
1425 string "Default Remote NLS Option"
1426 depends on SMB_NLS_DEFAULT
1429 This setting allows you to specify a default value for which
1430 codepage the server uses. If this field is left blank no
1431 translations will be done by default. The local codepage/charset
1432 default to CONFIG_NLS_DEFAULT.
1434 The nls settings can be changed at mount time, if your smbmount
1435 supports that, using the codepage and iocharset parameters.
1437 smbmount from samba 2.2.0 or later supports this.
1439 source "fs/cifs/Kconfig"
1442 tristate "NCP file system support (to mount NetWare volumes)"
1443 depends on IPX!=n || INET
1445 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
1446 used by Novell NetWare clients to talk to file servers. It is to
1447 IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
1448 to mount NetWare file server volumes and to access them just like
1449 any other Unix directory. For details, please read the file
1450 <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
1451 the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
1453 You do not have to say Y here if you want your Linux box to act as a
1454 file *server* for Novell NetWare clients.
1456 General information about how to connect Linux, Windows machines and
1457 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1459 To compile this as a module, choose M here: the module will be called
1460 ncpfs. Say N unless you are connected to a Novell network.
1462 source "fs/ncpfs/Kconfig"
1465 tristate "Coda file system support (advanced network fs)"
1468 Coda is an advanced network file system, similar to NFS in that it
1469 enables you to mount file systems of a remote server and access them
1470 with regular Unix commands as if they were sitting on your hard
1471 disk. Coda has several advantages over NFS: support for
1472 disconnected operation (e.g. for laptops), read/write server
1473 replication, security model for authentication and encryption,
1474 persistent client caches and write back caching.
1476 If you say Y here, your Linux box will be able to act as a Coda
1477 *client*. You will need user level code as well, both for the
1478 client and server. Servers are currently user level, i.e. they need
1479 no kernel support. Please read
1480 <file:Documentation/filesystems/coda.txt> and check out the Coda
1481 home page <http://www.coda.cs.cmu.edu/>.
1483 To compile the coda client support as a module, choose M here: the
1484 module will be called coda.
1487 tristate "Andrew File System support (AFS) (EXPERIMENTAL)"
1488 depends on INET && EXPERIMENTAL
1491 If you say Y here, you will get an experimental Andrew File System
1492 driver. It currently only supports unsecured read-only AFS access.
1494 See <file:Documentation/filesystems/afs.txt> for more information.
1499 bool "AFS dynamic debugging"
1502 Say Y here to make runtime controllable debugging messages appear.
1504 See <file:Documentation/filesystems/afs.txt> for more information.
1509 tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
1510 depends on INET && NET_9P && EXPERIMENTAL
1512 If you say Y here, you will get experimental support for
1513 Plan 9 resource sharing via the 9P2000 protocol.
1515 See <http://v9fs.sf.net> for more information.
1519 endif # NETWORK_FILESYSTEMS
1522 menu "Partition Types"
1524 source "fs/partitions/Kconfig"
1529 source "fs/nls/Kconfig"
1530 source "fs/dlm/Kconfig"