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
195 OCFS2 is a general purpose extent based shared disk cluster file
196 system with many similarities to ext3. It supports 64 bit inode
197 numbers, and has automatically extending metadata groups which may
198 also make it attractive for non-clustered use.
200 You'll want to install the ocfs2-tools package in order to at least
203 Project web page: http://oss.oracle.com/projects/ocfs2
204 Tools web page: http://oss.oracle.com/projects/ocfs2-tools
205 OCFS2 mailing lists: http://oss.oracle.com/projects/ocfs2/mailman/
207 For more information on OCFS2, see the file
208 <file:Documentation/filesystems/ocfs2.txt>.
211 tristate "O2CB Kernelspace Clustering"
215 OCFS2 includes a simple kernelspace clustering package, the OCFS2
216 Cluster Base. It only requires a very small userspace component
217 to configure it. This comes with the standard ocfs2-tools package.
218 O2CB is limited to maintaining a cluster for OCFS2 file systems.
219 It cannot manage any other cluster applications.
221 It is always safe to say Y here, as the clustering method is
224 config OCFS2_FS_USERSPACE_CLUSTER
225 tristate "OCFS2 Userspace Clustering"
226 depends on OCFS2_FS && DLM
229 This option will allow OCFS2 to use userspace clustering services
230 in conjunction with the DLM in fs/dlm. If you are using a
231 userspace cluster manager, say Y here.
233 It is safe to say Y, as the clustering method is run-time
236 config OCFS2_FS_STATS
237 bool "OCFS2 statistics"
241 This option allows some fs statistics to be captured. Enabling
242 this option may increase the memory consumption.
244 config OCFS2_DEBUG_MASKLOG
245 bool "OCFS2 logging support"
249 The ocfs2 filesystem has an extensive logging system. The system
250 allows selection of events to log via files in /sys/o2cb/logmask/.
251 This option will enlarge your kernel, but it allows debugging of
252 ocfs2 filesystem issues.
254 config OCFS2_DEBUG_FS
255 bool "OCFS2 expensive checks"
259 This option will enable expensive consistency checks. Enable
260 this option for debugging only as it is likely to decrease
261 performance of the filesystem.
263 config OCFS2_FS_POSIX_ACL
264 bool "OCFS2 POSIX Access Control Lists"
269 Posix Access Control Lists (ACLs) support permissions for users and
270 groups beyond the owner/group/world scheme.
274 source "fs/notify/Kconfig"
279 If you say Y here, you will be able to set per user limits for disk
280 usage (also called disk quotas). Currently, it works for the
281 ext2, ext3, and reiserfs file system. ext3 also supports journalled
282 quotas for which you don't need to run quotacheck(8) after an unclean
284 For further details, read the Quota mini-HOWTO, available from
285 <http://www.tldp.org/docs.html#howto>, or the documentation provided
286 with the quota tools. Probably the quota support is only useful for
287 multi user systems. If unsure, say N.
289 config QUOTA_NETLINK_INTERFACE
290 bool "Report quota messages through netlink interface"
291 depends on QUOTA && NET
293 If you say Y here, quota warnings (about exceeding softlimit, reaching
294 hardlimit, etc.) will be reported through netlink interface. If unsure,
297 config PRINT_QUOTA_WARNING
298 bool "Print quota warnings to console (OBSOLETE)"
302 If you say Y here, quota warnings (about exceeding softlimit, reaching
303 hardlimit, etc.) will be printed to the process' controlling terminal.
304 Note that this behavior is currently deprecated and may go away in
305 future. Please use notification via netlink socket instead.
307 # Generic support for tree structured quota files. Seleted when needed.
312 tristate "Old quota format support"
315 This quota format was (is) used by kernels earlier than 2.4.22. If
316 you have quota working and you don't want to convert to new quota
320 tristate "Quota format v2 support"
324 This quota format allows using quotas with 32-bit UIDs/GIDs. If you
325 need this functionality say Y here.
329 depends on XFS_QUOTA || QUOTA
333 tristate "Kernel automounter support"
335 The automounter is a tool to automatically mount remote file systems
336 on demand. This implementation is partially kernel-based to reduce
337 overhead in the already-mounted case; this is unlike the BSD
338 automounter (amd), which is a pure user space daemon.
340 To use the automounter you need the user-space tools from the autofs
341 package; you can find the location in <file:Documentation/Changes>.
342 You also want to answer Y to "NFS file system support", below.
344 If you want to use the newer version of the automounter with more
345 features, say N here and say Y to "Kernel automounter v4 support",
348 To compile this support as a module, choose M here: the module will be
351 If you are not a part of a fairly large, distributed network, you
352 probably do not need an automounter, and can say N here.
355 tristate "Kernel automounter version 4 support (also supports v3)"
357 The automounter is a tool to automatically mount remote file systems
358 on demand. This implementation is partially kernel-based to reduce
359 overhead in the already-mounted case; this is unlike the BSD
360 automounter (amd), which is a pure user space daemon.
362 To use the automounter you need the user-space tools from
363 <ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4/>; you also
364 want to answer Y to "NFS file system support", below.
366 To compile this support as a module, choose M here: the module will be
367 called autofs4. You will need to add "alias autofs autofs4" to your
368 modules configuration file.
370 If you are not a part of a fairly large, distributed network or
371 don't have a laptop which needs to dynamically reconfigure to the
372 local network, you probably do not need an automounter, and can say
376 tristate "FUSE (Filesystem in Userspace) support"
378 With FUSE it is possible to implement a fully functional filesystem
379 in a userspace program.
381 There's also companion library: libfuse. This library along with
382 utilities is available from the FUSE homepage:
383 <http://fuse.sourceforge.net/>
385 See <file:Documentation/filesystems/fuse.txt> for more information.
386 See <file:Documentation/Changes> for needed library/utility version.
388 If you want to develop a userspace FS, or if you want to use
389 a filesystem based on FUSE, answer Y or M.
396 menu "CD-ROM/DVD Filesystems"
399 tristate "ISO 9660 CDROM file system support"
401 This is the standard file system used on CD-ROMs. It was previously
402 known as "High Sierra File System" and is called "hsfs" on other
403 Unix systems. The so-called Rock-Ridge extensions which allow for
404 long Unix filenames and symbolic links are also supported by this
405 driver. If you have a CD-ROM drive and want to do more with it than
406 just listen to audio CDs and watch its LEDs, say Y (and read
407 <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO,
408 available from <http://www.tldp.org/docs.html#howto>), thereby
409 enlarging your kernel by about 27 KB; otherwise say N.
411 To compile this file system support as a module, choose M here: the
412 module will be called isofs.
415 bool "Microsoft Joliet CDROM extensions"
416 depends on ISO9660_FS
419 Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system
420 which allows for long filenames in unicode format (unicode is the
421 new 16 bit character code, successor to ASCII, which encodes the
422 characters of almost all languages of the world; see
423 <http://www.unicode.org/> for more information). Say Y here if you
424 want to be able to read Joliet CD-ROMs under Linux.
427 bool "Transparent decompression extension"
428 depends on ISO9660_FS
431 This is a Linux-specific extension to RockRidge which lets you store
432 data in compressed form on a CD-ROM and have it transparently
433 decompressed when the CD-ROM is accessed. See
434 <http://www.kernel.org/pub/linux/utils/fs/zisofs/> for the tools
435 necessary to create such a filesystem. Say Y here if you want to be
436 able to read such compressed CD-ROMs.
439 tristate "UDF file system support"
442 This is the new file system used on some CD-ROMs and DVDs. Say Y if
443 you intend to mount DVD discs or CDRW's written in packet mode, or
444 if written to by other UDF utilities, such as DirectCD.
445 Please read <file:Documentation/filesystems/udf.txt>.
447 To compile this file system support as a module, choose M here: the
448 module will be called udf.
455 depends on (UDF_FS=m && NLS) || (UDF_FS=y && NLS=y)
461 menu "DOS/FAT/NT Filesystems"
467 If you want to use one of the FAT-based file systems (the MS-DOS and
468 VFAT (Windows 95) file systems), then you must say Y or M here
469 to include FAT support. You will then be able to mount partitions or
470 diskettes with FAT-based file systems and transparently access the
471 files on them, i.e. MSDOS files will look and behave just like all
474 This FAT support is not a file system in itself, it only provides
475 the foundation for the other file systems. You will have to say Y or
476 M to at least one of "MSDOS fs support" or "VFAT fs support" in
477 order to make use of it.
479 Another way to read and write MSDOS floppies and hard drive
480 partitions from within Linux (but not transparently) is with the
481 mtools ("man mtools") program suite. You don't need to say Y here in
484 If you need to move large files on floppies between a DOS and a
485 Linux box, say Y here, mount the floppy under Linux with an MSDOS
486 file system and use GNU tar's M option. GNU tar is a program
487 available for Unix and DOS ("man tar" or "info tar").
489 The FAT support will enlarge your kernel by about 37 KB. If unsure,
492 To compile this as a module, choose M here: the module will be called
493 fat. Note that if you compile the FAT support as a module, you
494 cannot compile any of the FAT-based file systems into the kernel
495 -- they will have to be modules as well.
498 tristate "MSDOS fs support"
501 This allows you to mount MSDOS partitions of your hard drive (unless
502 they are compressed; to access compressed MSDOS partitions under
503 Linux, you can either use the DOS emulator DOSEMU, described in the
504 DOSEMU-HOWTO, available from
505 <http://www.tldp.org/docs.html#howto>, or try dmsdosfs in
506 <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you
507 intend to use dosemu with a non-compressed MSDOS partition, say Y
508 here) and MSDOS floppies. This means that file access becomes
509 transparent, i.e. the MSDOS files look and behave just like all
512 If you have Windows 95 or Windows NT installed on your MSDOS
513 partitions, you should use the VFAT file system (say Y to "VFAT fs
514 support" below), or you will not be able to see the long filenames
515 generated by Windows 95 / Windows NT.
517 This option will enlarge your kernel by about 7 KB. If unsure,
518 answer Y. This will only work if you said Y to "DOS FAT fs support"
519 as well. To compile this as a module, choose M here: the module will
523 tristate "VFAT (Windows-95) fs support"
526 This option provides support for normal Windows file systems with
527 long filenames. That includes non-compressed FAT-based file systems
528 used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
529 programs from the mtools package.
531 The VFAT support enlarges your kernel by about 10 KB and it only
532 works if you said Y to the "DOS FAT fs support" above. Please read
533 the file <file:Documentation/filesystems/vfat.txt> for details. If
536 To compile this as a module, choose M here: the module will be called
539 config FAT_DEFAULT_CODEPAGE
540 int "Default codepage for FAT"
541 depends on MSDOS_FS || VFAT_FS
544 This option should be set to the codepage of your FAT filesystems.
545 It can be overridden with the "codepage" mount option.
546 See <file:Documentation/filesystems/vfat.txt> for more information.
548 config FAT_DEFAULT_IOCHARSET
549 string "Default iocharset for FAT"
553 Set this to the default input/output character set you'd
554 like FAT to use. It should probably match the character set
555 that most of your FAT filesystems use, and can be overridden
556 with the "iocharset" mount option for FAT filesystems.
557 Note that "utf8" is not recommended for FAT filesystems.
558 If unsure, you shouldn't set "utf8" here.
559 See <file:Documentation/filesystems/vfat.txt> for more information.
562 tristate "NTFS file system support"
565 NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003.
567 Saying Y or M here enables read support. There is partial, but
568 safe, write support available. For write support you must also
569 say Y to "NTFS write support" below.
571 There are also a number of user-space tools available, called
572 ntfsprogs. These include ntfsundelete and ntfsresize, that work
573 without NTFS support enabled in the kernel.
575 This is a rewrite from scratch of Linux NTFS support and replaced
576 the old NTFS code starting with Linux 2.5.11. A backport to
577 the Linux 2.4 kernel series is separately available as a patch
578 from the project web site.
580 For more information see <file:Documentation/filesystems/ntfs.txt>
581 and <http://www.linux-ntfs.org/>.
583 To compile this file system support as a module, choose M here: the
584 module will be called ntfs.
586 If you are not using Windows NT, 2000, XP or 2003 in addition to
587 Linux on your computer it is safe to say N.
590 bool "NTFS debugging support"
593 If you are experiencing any problems with the NTFS file system, say
594 Y here. This will result in additional consistency checks to be
595 performed by the driver as well as additional debugging messages to
596 be written to the system log. Note that debugging messages are
597 disabled by default. To enable them, supply the option debug_msgs=1
598 at the kernel command line when booting the kernel or as an option
599 to insmod when loading the ntfs module. Once the driver is active,
600 you can enable debugging messages by doing (as root):
601 echo 1 > /proc/sys/fs/ntfs-debug
602 Replacing the "1" with "0" would disable debug messages.
604 If you leave debugging messages disabled, this results in little
605 overhead, but enabling debug messages results in very significant
606 slowdown of the system.
608 When reporting bugs, please try to have available a full dump of
609 debugging messages while the misbehaviour was occurring.
612 bool "NTFS write support"
615 This enables the partial, but safe, write support in the NTFS driver.
617 The only supported operation is overwriting existing files, without
618 changing the file length. No file or directory creation, deletion or
619 renaming is possible. Note only non-resident files can be written to
620 so you may find that some very small files (<500 bytes or so) cannot
623 While we cannot guarantee that it will not damage any data, we have
624 so far not received a single report where the driver would have
625 damaged someones data so we assume it is perfectly safe to use.
627 Note: While write support is safe in this version (a rewrite from
628 scratch of the NTFS support), it should be noted that the old NTFS
629 write support, included in Linux 2.5.10 and before (since 1997),
632 This is currently useful with TopologiLinux. TopologiLinux is run
633 on top of any DOS/Microsoft Windows system without partitioning your
634 hard disk. Unlike other Linux distributions TopologiLinux does not
635 need its own partition. For more information see
636 <http://topologi-linux.sourceforge.net/>
638 It is perfectly safe to say N here.
643 menu "Pseudo filesystems"
645 source "fs/proc/Kconfig"
648 bool "sysfs file system support" if EMBEDDED
651 The sysfs filesystem is a virtual filesystem that the kernel uses to
652 export internal kernel objects, their attributes, and their
653 relationships to one another.
655 Users can use sysfs to ascertain useful information about the running
656 kernel, such as the devices the kernel has discovered on each bus and
657 which driver each is bound to. sysfs can also be used to tune devices
658 and other kernel subsystems.
660 Some system agents rely on the information in sysfs to operate.
661 /sbin/hotplug uses device and object attributes in sysfs to assist in
662 delegating policy decisions, like persistently naming devices.
664 sysfs is currently used by the block subsystem to mount the root
665 partition. If sysfs is disabled you must specify the boot device on
666 the kernel boot command line via its major and minor numbers. For
667 example, "root=03:01" for /dev/hda1.
669 Designers of embedded systems may wish to say N here to conserve space.
672 bool "Virtual memory file system support (former shm fs)"
674 Tmpfs is a file system which keeps all files in virtual memory.
676 Everything in tmpfs is temporary in the sense that no files will be
677 created on your hard drive. The files live in memory and swap
678 space. If you unmount a tmpfs instance, everything stored therein is
681 See <file:Documentation/filesystems/tmpfs.txt> for details.
683 config TMPFS_POSIX_ACL
684 bool "Tmpfs POSIX Access Control Lists"
688 POSIX Access Control Lists (ACLs) support permissions for users and
689 groups beyond the owner/group/world scheme.
691 To learn more about Access Control Lists, visit the POSIX ACLs for
692 Linux website <http://acl.bestbits.at/>.
694 If you don't know what Access Control Lists are, say N.
697 bool "HugeTLB file system support"
698 depends on X86 || IA64 || PPC64 || SPARC64 || (SUPERH && MMU) || \
699 (S390 && 64BIT) || BROKEN
701 hugetlbfs is a filesystem backing for HugeTLB pages, based on
702 ramfs. For architectures that support it, say Y here and read
703 <file:Documentation/vm/hugetlbpage.txt> for details.
711 tristate "Userspace-driven configuration filesystem"
714 configfs is a ram-based filesystem that provides the converse
715 of sysfs's functionality. Where sysfs is a filesystem-based
716 view of kernel objects, configfs is a filesystem-based manager
717 of kernel objects, or config_items.
719 Both sysfs and configfs can and should exist together on the
720 same system. One is not a replacement for the other.
724 menu "Miscellaneous filesystems"
727 tristate "ADFS file system support (EXPERIMENTAL)"
728 depends on BLOCK && EXPERIMENTAL
730 The Acorn Disc Filing System is the standard file system of the
731 RiscOS operating system which runs on Acorn's ARM-based Risc PC
732 systems and the Acorn Archimedes range of machines. If you say Y
733 here, Linux will be able to read from ADFS partitions on hard drives
734 and from ADFS-formatted floppy discs. If you also want to be able to
735 write to those devices, say Y to "ADFS write support" below.
737 The ADFS partition should be the first partition (i.e.,
738 /dev/[hs]d?1) on each of your drives. Please read the file
739 <file:Documentation/filesystems/adfs.txt> for further details.
741 To compile this code as a module, choose M here: the module will be
747 bool "ADFS write support (DANGEROUS)"
750 If you say Y here, you will be able to write to ADFS partitions on
751 hard drives and ADFS-formatted floppy disks. This is experimental
752 codes, so if you're unsure, say N.
755 tristate "Amiga FFS file system support (EXPERIMENTAL)"
756 depends on BLOCK && EXPERIMENTAL
758 The Fast File System (FFS) is the common file system used on hard
759 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
760 if you want to be able to read and write files from and to an Amiga
761 FFS partition on your hard drive. Amiga floppies however cannot be
762 read with this driver due to an incompatibility of the floppy
763 controller used in an Amiga and the standard floppy controller in
764 PCs and workstations. Read <file:Documentation/filesystems/affs.txt>
765 and <file:fs/affs/Changes>.
767 With this driver you can also mount disk files used by Bernd
768 Schmidt's Un*X Amiga Emulator
769 (<http://www.freiburg.linux.de/~uae/>).
770 If you want to do this, you will also need to say Y or M to "Loop
771 device support", above.
773 To compile this file system support as a module, choose M here: the
774 module will be called affs. If unsure, say N.
777 tristate "eCrypt filesystem layer support (EXPERIMENTAL)"
778 depends on EXPERIMENTAL && KEYS && CRYPTO && NET
780 Encrypted filesystem that operates on the VFS layer. See
781 <file:Documentation/filesystems/ecryptfs.txt> to learn more about
782 eCryptfs. Userspace components are required and can be
783 obtained from <http://ecryptfs.sf.net>.
785 To compile this file system support as a module, choose M here: the
786 module will be called ecryptfs.
789 tristate "Apple Macintosh file system support (EXPERIMENTAL)"
790 depends on BLOCK && EXPERIMENTAL
793 If you say Y here, you will be able to mount Macintosh-formatted
794 floppy disks and hard drive partitions with full read-write access.
795 Please read <file:Documentation/filesystems/hfs.txt> to learn about
796 the available mount options.
798 To compile this file system support as a module, choose M here: the
799 module will be called hfs.
802 tristate "Apple Extended HFS file system support"
807 If you say Y here, you will be able to mount extended format
808 Macintosh-formatted hard drive partitions with full read-write access.
810 This file system is often called HFS+ and was introduced with
811 MacOS 8. It includes all Mac specific filesystem data such as
812 data forks and creator codes, but it also has several UNIX
813 style features such as file ownership and permissions.
816 tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)"
817 depends on BLOCK && EXPERIMENTAL
820 The BeOS File System (BeFS) is the native file system of Be, Inc's
821 BeOS. Notable features include support for arbitrary attributes
822 on files and directories, and database-like indices on selected
823 attributes. (Also note that this driver doesn't make those features
824 available at this time). It is a 64 bit filesystem, so it supports
825 extremely large volumes and files.
827 If you use this filesystem, you should also say Y to at least one
828 of the NLS (native language support) options below.
830 If you don't know what this is about, say N.
832 To compile this as a module, choose M here: the module will be
839 If you say Y here, you can use the 'debug' mount option to enable
840 debugging output from the driver.
843 tristate "BFS file system support (EXPERIMENTAL)"
844 depends on BLOCK && EXPERIMENTAL
846 Boot File System (BFS) is a file system used under SCO UnixWare to
847 allow the bootloader access to the kernel image and other important
848 files during the boot process. It is usually mounted under /stand
849 and corresponds to the slice marked as "STAND" in the UnixWare
850 partition. You should say Y if you want to read or write the files
851 on your /stand slice from within Linux. You then also need to say Y
852 to "UnixWare slices support", below. More information about the BFS
853 file system is contained in the file
854 <file:Documentation/filesystems/bfs.txt>.
856 If you don't know what this is about, say N.
858 To compile this as a module, choose M here: the module will be called
859 bfs. Note that the file system of your root partition (the one
860 containing the directory /) cannot be compiled as a module.
865 tristate "EFS file system support (read only) (EXPERIMENTAL)"
866 depends on BLOCK && EXPERIMENTAL
868 EFS is an older file system used for non-ISO9660 CD-ROMs and hard
869 disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
870 uses the XFS file system for hard disk partitions however).
872 This implementation only offers read-only access. If you don't know
873 what all this is about, it's safe to say N. For more information
874 about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
876 To compile the EFS file system support as a module, choose M here: the
877 module will be called efs.
879 source "fs/jffs2/Kconfig"
880 # UBIFS File system configuration
881 source "fs/ubifs/Kconfig"
884 tristate "Compressed ROM file system support (cramfs)"
888 Saying Y here includes support for CramFs (Compressed ROM File
889 System). CramFs is designed to be a simple, small, and compressed
890 file system for ROM based embedded systems. CramFs is read-only,
891 limited to 256MB file systems (with 16MB files), and doesn't support
892 16/32 bits uid/gid, hard links and timestamps.
894 See <file:Documentation/filesystems/cramfs.txt> and
895 <file:fs/cramfs/README> for further information.
897 To compile this as a module, choose M here: the module will be called
898 cramfs. Note that the root file system (the one containing the
899 directory /) cannot be compiled as a module.
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.
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"
git://ftp.safe.ca / safe / jmp / linux-2.6 / blob