2 # File system configuration
10 tristate "Second extended fs support"
12 Ext2 is a standard Linux file system for hard disks.
14 To compile this file system support as a module, choose M here: the
15 module will be called ext2.
20 bool "Ext2 extended attributes"
23 Extended attributes are name:value pairs associated with inodes by
24 the kernel or by users (see the attr(5) manual page, or visit
25 <http://acl.bestbits.at/> for details).
29 config EXT2_FS_POSIX_ACL
30 bool "Ext2 POSIX Access Control Lists"
31 depends on EXT2_FS_XATTR
34 Posix Access Control Lists (ACLs) support permissions for users and
35 groups beyond the owner/group/world scheme.
37 To learn more about Access Control Lists, visit the Posix ACLs for
38 Linux website <http://acl.bestbits.at/>.
40 If you don't know what Access Control Lists are, say N
42 config EXT2_FS_SECURITY
43 bool "Ext2 Security Labels"
44 depends on EXT2_FS_XATTR
46 Security labels support alternative access control models
47 implemented by security modules like SELinux. This option
48 enables an extended attribute handler for file security
49 labels in the ext2 filesystem.
51 If you are not using a security module that requires using
52 extended attributes for file security labels, say N.
55 bool "Ext2 execute in place support"
56 depends on EXT2_FS && MMU
58 Execute in place can be used on memory-backed block devices. If you
59 enable this option, you can select to mount block devices which are
60 capable of this feature without using the page cache.
62 If you do not use a block device that is capable of using this,
68 depends on EXT2_FS_XIP
72 tristate "Ext3 journalling file system support"
75 This is the journalling version of the Second extended file system
76 (often called ext3), the de facto standard Linux file system
77 (method to organize files on a storage device) for hard disks.
79 The journalling code included in this driver means you do not have
80 to run e2fsck (file system checker) on your file systems after a
81 crash. The journal keeps track of any changes that were being made
82 at the time the system crashed, and can ensure that your file system
83 is consistent without the need for a lengthy check.
85 Other than adding the journal to the file system, the on-disk format
86 of ext3 is identical to ext2. It is possible to freely switch
87 between using the ext3 driver and the ext2 driver, as long as the
88 file system has been cleanly unmounted, or e2fsck is run on the file
91 To add a journal on an existing ext2 file system or change the
92 behavior of ext3 file systems, you can use the tune2fs utility ("man
93 tune2fs"). To modify attributes of files and directories on ext3
94 file systems, use chattr ("man chattr"). You need to be using
95 e2fsprogs version 1.20 or later in order to create ext3 journals
96 (available at <http://sourceforge.net/projects/e2fsprogs/>).
98 To compile this file system support as a module, choose M here: the
99 module will be called ext3.
102 bool "Ext3 extended attributes"
106 Extended attributes are name:value pairs associated with inodes by
107 the kernel or by users (see the attr(5) manual page, or visit
108 <http://acl.bestbits.at/> for details).
112 You need this for POSIX ACL support on ext3.
114 config EXT3_FS_POSIX_ACL
115 bool "Ext3 POSIX Access Control Lists"
116 depends on EXT3_FS_XATTR
119 Posix Access Control Lists (ACLs) support permissions for users and
120 groups beyond the owner/group/world scheme.
122 To learn more about Access Control Lists, visit the Posix ACLs for
123 Linux website <http://acl.bestbits.at/>.
125 If you don't know what Access Control Lists are, say N
127 config EXT3_FS_SECURITY
128 bool "Ext3 Security Labels"
129 depends on EXT3_FS_XATTR
131 Security labels support alternative access control models
132 implemented by security modules like SELinux. This option
133 enables an extended attribute handler for file security
134 labels in the ext3 filesystem.
136 If you are not using a security module that requires using
137 extended attributes for file security labels, say N.
140 tristate "Ext4dev/ext4 extended fs support development (EXPERIMENTAL)"
141 depends on EXPERIMENTAL
145 Ext4dev is a predecessor filesystem of the next generation
146 extended fs ext4, based on ext3 filesystem code. It will be
147 renamed ext4 fs later, once ext4dev is mature and stabilized.
149 Unlike the change from ext2 filesystem to ext3 filesystem,
150 the on-disk format of ext4dev is not the same as ext3 any more:
151 it is based on extent maps and it supports 48-bit physical block
152 numbers. These combined on-disk format changes will allow
153 ext4dev/ext4 to handle more than 16 TB filesystem volumes --
154 a hard limit that ext3 cannot overcome without changing the
157 Other than extent maps and 48-bit block numbers, ext4dev also is
158 likely to have other new features such as persistent preallocation,
159 high resolution time stamps, and larger file support etc. These
160 features will be added to ext4dev gradually.
162 To compile this file system support as a module, choose M here. The
163 module will be called ext4dev.
167 config EXT4DEV_FS_XATTR
168 bool "Ext4dev extended attributes"
169 depends on EXT4DEV_FS
172 Extended attributes are name:value pairs associated with inodes by
173 the kernel or by users (see the attr(5) manual page, or visit
174 <http://acl.bestbits.at/> for details).
178 You need this for POSIX ACL support on ext4dev/ext4.
180 config EXT4DEV_FS_POSIX_ACL
181 bool "Ext4dev POSIX Access Control Lists"
182 depends on EXT4DEV_FS_XATTR
185 POSIX Access Control Lists (ACLs) support permissions for users and
186 groups beyond the owner/group/world scheme.
188 To learn more about Access Control Lists, visit the POSIX ACLs for
189 Linux website <http://acl.bestbits.at/>.
191 If you don't know what Access Control Lists are, say N
193 config EXT4DEV_FS_SECURITY
194 bool "Ext4dev Security Labels"
195 depends on EXT4DEV_FS_XATTR
197 Security labels support alternative access control models
198 implemented by security modules like SELinux. This option
199 enables an extended attribute handler for file security
200 labels in the ext4dev/ext4 filesystem.
202 If you are not using a security module that requires using
203 extended attributes for file security labels, say N.
208 This is a generic journalling layer for block devices. It is
209 currently used by the ext3 and OCFS2 file systems, but it could
210 also be used to add journal support to other file systems or block
211 devices such as RAID or LVM.
213 If you are using the ext3 or OCFS2 file systems, you need to
214 say Y here. If you are not using ext3 OCFS2 then you will probably
217 To compile this device as a module, choose M here: the module will be
218 called jbd. If you are compiling ext3 or OCFS2 into the kernel,
219 you cannot compile this code as a module.
222 bool "JBD (ext3) debugging support"
223 depends on JBD && DEBUG_FS
225 If you are using the ext3 journaled file system (or potentially any
226 other file system/device using JBD), this option allows you to
227 enable debugging output while the system is running, in order to
228 help track down any problems you are having. By default the
229 debugging output will be turned off.
231 If you select Y here, then you will be able to turn on debugging
232 with "echo N > /sys/kernel/debug/jbd/jbd-debug", where N is a
233 number between 1 and 5, the higher the number, the more debugging
234 output is generated. To turn debugging off again, do
235 "echo 0 > /sys/kernel/debug/jbd/jbd-debug".
241 This is a generic journaling layer for block devices that support
242 both 32-bit and 64-bit block numbers. It is currently used by
243 the ext4dev/ext4 filesystem, but it could also be used to add
244 journal support to other file systems or block devices such
247 If you are using ext4dev/ext4, you need to say Y here. If you are not
248 using ext4dev/ext4 then you will probably want to say N.
250 To compile this device as a module, choose M here. The module will be
251 called jbd2. If you are compiling ext4dev/ext4 into the kernel,
252 you cannot compile this code as a module.
255 bool "JBD2 (ext4dev/ext4) debugging support"
256 depends on JBD2 && DEBUG_FS
258 If you are using the ext4dev/ext4 journaled file system (or
259 potentially any other filesystem/device using JBD2), this option
260 allows you to enable debugging output while the system is running,
261 in order to help track down any problems you are having.
262 By default, the debugging output will be turned off.
264 If you select Y here, then you will be able to turn on debugging
265 with "echo N > /sys/kernel/debug/jbd2/jbd2-debug", where N is a
266 number between 1 and 5. The higher the number, the more debugging
267 output is generated. To turn debugging off again, do
268 "echo 0 > /sys/kernel/debug/jbd2/jbd2-debug".
271 # Meta block cache for Extended Attributes (ext2/ext3/ext4)
273 depends on EXT2_FS_XATTR || EXT3_FS_XATTR || EXT4DEV_FS_XATTR
274 default y if EXT2_FS=y || EXT3_FS=y || EXT4DEV_FS=y
275 default m if EXT2_FS=m || EXT3_FS=m || EXT4DEV_FS=m
278 tristate "Reiserfs support"
280 Stores not just filenames but the files themselves in a balanced
281 tree. Uses journalling.
283 Balanced trees are more efficient than traditional file system
284 architectural foundations.
286 In general, ReiserFS is as fast as ext2, but is very efficient with
287 large directories and small files. Additional patches are needed
288 for NFS and quotas, please see <http://www.namesys.com/> for links.
290 It is more easily extended to have features currently found in
291 database and keyword search systems than block allocation based file
292 systems are. The next version will be so extended, and will support
293 plugins consistent with our motto ``It takes more than a license to
294 make source code open.''
296 Read <http://www.namesys.com/> to learn more about reiserfs.
298 Sponsored by Threshold Networks, Emusic.com, and Bigstorage.com.
300 If you like it, you can pay us to add new features to it that you
301 need, buy a support contract, or pay us to port it to another OS.
303 config REISERFS_CHECK
304 bool "Enable reiserfs debug mode"
305 depends on REISERFS_FS
307 If you set this to Y, then ReiserFS will perform every check it can
308 possibly imagine of its internal consistency throughout its
309 operation. It will also go substantially slower. More than once we
310 have forgotten that this was on, and then gone despondent over the
311 latest benchmarks.:-) Use of this option allows our team to go all
312 out in checking for consistency when debugging without fear of its
313 effect on end users. If you are on the verge of sending in a bug
314 report, say Y and you might get a useful error message. Almost
315 everyone should say N.
317 config REISERFS_PROC_INFO
318 bool "Stats in /proc/fs/reiserfs"
319 depends on REISERFS_FS && PROC_FS
321 Create under /proc/fs/reiserfs a hierarchy of files, displaying
322 various ReiserFS statistics and internal data at the expense of
323 making your kernel or module slightly larger (+8 KB). This also
324 increases the amount of kernel memory required for each mount.
325 Almost everyone but ReiserFS developers and people fine-tuning
326 reiserfs or tracing problems should say N.
328 config REISERFS_FS_XATTR
329 bool "ReiserFS extended attributes"
330 depends on REISERFS_FS
332 Extended attributes are name:value pairs associated with inodes by
333 the kernel or by users (see the attr(5) manual page, or visit
334 <http://acl.bestbits.at/> for details).
338 config REISERFS_FS_POSIX_ACL
339 bool "ReiserFS POSIX Access Control Lists"
340 depends on REISERFS_FS_XATTR
343 Posix Access Control Lists (ACLs) support permissions for users and
344 groups beyond the owner/group/world scheme.
346 To learn more about Access Control Lists, visit the Posix ACLs for
347 Linux website <http://acl.bestbits.at/>.
349 If you don't know what Access Control Lists are, say N
351 config REISERFS_FS_SECURITY
352 bool "ReiserFS Security Labels"
353 depends on REISERFS_FS_XATTR
355 Security labels support alternative access control models
356 implemented by security modules like SELinux. This option
357 enables an extended attribute handler for file security
358 labels in the ReiserFS filesystem.
360 If you are not using a security module that requires using
361 extended attributes for file security labels, say N.
364 tristate "JFS filesystem support"
367 This is a port of IBM's Journaled Filesystem . More information is
368 available in the file <file:Documentation/filesystems/jfs.txt>.
370 If you do not intend to use the JFS filesystem, say N.
373 bool "JFS POSIX Access Control Lists"
377 Posix Access Control Lists (ACLs) support permissions for users and
378 groups beyond the owner/group/world scheme.
380 To learn more about Access Control Lists, visit the Posix ACLs for
381 Linux website <http://acl.bestbits.at/>.
383 If you don't know what Access Control Lists are, say N
386 bool "JFS Security Labels"
389 Security labels support alternative access control models
390 implemented by security modules like SELinux. This option
391 enables an extended attribute handler for file security
392 labels in the jfs filesystem.
394 If you are not using a security module that requires using
395 extended attributes for file security labels, say N.
401 If you are experiencing any problems with the JFS filesystem, say
402 Y here. This will result in additional debugging messages to be
403 written to the system log. Under normal circumstances, this
404 results in very little overhead.
406 config JFS_STATISTICS
407 bool "JFS statistics"
410 Enabling this option will cause statistics from the JFS file system
411 to be made available to the user in the /proc/fs/jfs/ directory.
414 # Posix ACL utility routines (for now, only ext2/ext3/jfs/reiserfs/nfs4)
416 # NOTE: you can implement Posix ACLs without these helpers (XFS does).
417 # Never use this symbol for ifdefs.
422 source "fs/xfs/Kconfig"
423 source "fs/gfs2/Kconfig"
426 tristate "OCFS2 file system support"
427 depends on NET && SYSFS
432 OCFS2 is a general purpose extent based shared disk cluster file
433 system with many similarities to ext3. It supports 64 bit inode
434 numbers, and has automatically extending metadata groups which may
435 also make it attractive for non-clustered use.
437 You'll want to install the ocfs2-tools package in order to at least
440 Project web page: http://oss.oracle.com/projects/ocfs2
441 Tools web page: http://oss.oracle.com/projects/ocfs2-tools
442 OCFS2 mailing lists: http://oss.oracle.com/projects/ocfs2/mailman/
444 For more information on OCFS2, see the file
445 <file:Documentation/filesystems/ocfs2.txt>.
448 tristate "O2CB Kernelspace Clustering"
452 OCFS2 includes a simple kernelspace clustering package, the OCFS2
453 Cluster Base. It only requires a very small userspace component
454 to configure it. This comes with the standard ocfs2-tools package.
455 O2CB is limited to maintaining a cluster for OCFS2 file systems.
456 It cannot manage any other cluster applications.
458 It is always safe to say Y here, as the clustering method is
461 config OCFS2_FS_USERSPACE_CLUSTER
462 tristate "OCFS2 Userspace Clustering"
463 depends on OCFS2_FS && DLM
466 This option will allow OCFS2 to use userspace clustering services
467 in conjunction with the DLM in fs/dlm. If you are using a
468 userspace cluster manager, say Y here.
470 It is safe to say Y, as the clustering method is run-time
473 config OCFS2_FS_STATS
474 bool "OCFS2 statistics"
478 This option allows some fs statistics to be captured. Enabling
479 this option may increase the memory consumption.
481 config OCFS2_DEBUG_MASKLOG
482 bool "OCFS2 logging support"
486 The ocfs2 filesystem has an extensive logging system. The system
487 allows selection of events to log via files in /sys/o2cb/logmask/.
488 This option will enlarge your kernel, but it allows debugging of
489 ocfs2 filesystem issues.
491 config OCFS2_DEBUG_FS
492 bool "OCFS2 expensive checks"
496 This option will enable expensive consistency checks. Enable
497 this option for debugging only as it is likely to decrease
498 performance of the filesystem.
501 tristate "Btrfs filesystem (EXPERIMENTAL) Unstable disk format"
502 depends on EXPERIMENTAL
507 Btrfs is a new filesystem with extents, writable snapshotting,
508 support for multiple devices and many more features.
510 Btrfs is highly experimental, and THE DISK FORMAT IS NOT YET
511 FINALIZED. You should say N here unless you are interested in
512 testing Btrfs with non-critical data.
514 To compile this file system support as a module, choose M here. The
515 module will be called btrfs.
522 bool "Dnotify support"
525 Dnotify is a directory-based per-fd file change notification system
526 that uses signals to communicate events to user-space. There exist
527 superior alternatives, but some applications may still rely on
533 bool "Inotify file change notification support"
536 Say Y here to enable inotify support. Inotify is a file change
537 notification system and a replacement for dnotify. Inotify fixes
538 numerous shortcomings in dnotify and introduces several new features
539 including multiple file events, one-shot support, and unmount
542 For more information, see <file:Documentation/filesystems/inotify.txt>
547 bool "Inotify support for userspace"
551 Say Y here to enable inotify support for userspace, including the
552 associated system calls. Inotify allows monitoring of both files and
553 directories via a single open fd. Events are read from the file
554 descriptor, which is also select()- and poll()-able.
556 For more information, see <file:Documentation/filesystems/inotify.txt>
563 If you say Y here, you will be able to set per user limits for disk
564 usage (also called disk quotas). Currently, it works for the
565 ext2, ext3, and reiserfs file system. ext3 also supports journalled
566 quotas for which you don't need to run quotacheck(8) after an unclean
568 For further details, read the Quota mini-HOWTO, available from
569 <http://www.tldp.org/docs.html#howto>, or the documentation provided
570 with the quota tools. Probably the quota support is only useful for
571 multi user systems. If unsure, say N.
573 config QUOTA_NETLINK_INTERFACE
574 bool "Report quota messages through netlink interface"
575 depends on QUOTA && NET
577 If you say Y here, quota warnings (about exceeding softlimit, reaching
578 hardlimit, etc.) will be reported through netlink interface. If unsure,
581 config PRINT_QUOTA_WARNING
582 bool "Print quota warnings to console (OBSOLETE)"
586 If you say Y here, quota warnings (about exceeding softlimit, reaching
587 hardlimit, etc.) will be printed to the process' controlling terminal.
588 Note that this behavior is currently deprecated and may go away in
589 future. Please use notification via netlink socket instead.
592 tristate "Old quota format support"
595 This quota format was (is) used by kernels earlier than 2.4.22. If
596 you have quota working and you don't want to convert to new quota
600 tristate "Quota format v2 support"
603 This quota format allows using quotas with 32-bit UIDs/GIDs. If you
604 need this functionality say Y here.
608 depends on XFS_QUOTA || QUOTA
612 tristate "Kernel automounter support"
614 The automounter is a tool to automatically mount remote file systems
615 on demand. This implementation is partially kernel-based to reduce
616 overhead in the already-mounted case; this is unlike the BSD
617 automounter (amd), which is a pure user space daemon.
619 To use the automounter you need the user-space tools from the autofs
620 package; you can find the location in <file:Documentation/Changes>.
621 You also want to answer Y to "NFS file system support", below.
623 If you want to use the newer version of the automounter with more
624 features, say N here and say Y to "Kernel automounter v4 support",
627 To compile this support as a module, choose M here: the module will be
630 If you are not a part of a fairly large, distributed network, you
631 probably do not need an automounter, and can say N here.
634 tristate "Kernel automounter version 4 support (also supports v3)"
636 The automounter is a tool to automatically mount remote file systems
637 on demand. This implementation is partially kernel-based to reduce
638 overhead in the already-mounted case; this is unlike the BSD
639 automounter (amd), which is a pure user space daemon.
641 To use the automounter you need the user-space tools from
642 <ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4/>; you also
643 want to answer Y to "NFS file system support", below.
645 To compile this support as a module, choose M here: the module will be
646 called autofs4. You will need to add "alias autofs autofs4" to your
647 modules configuration file.
649 If you are not a part of a fairly large, distributed network or
650 don't have a laptop which needs to dynamically reconfigure to the
651 local network, you probably do not need an automounter, and can say
655 tristate "Filesystem in Userspace support"
657 With FUSE it is possible to implement a fully functional filesystem
658 in a userspace program.
660 There's also companion library: libfuse. This library along with
661 utilities is available from the FUSE homepage:
662 <http://fuse.sourceforge.net/>
664 See <file:Documentation/filesystems/fuse.txt> for more information.
665 See <file:Documentation/Changes> for needed library/utility version.
667 If you want to develop a userspace FS, or if you want to use
668 a filesystem based on FUSE, answer Y or M.
675 menu "CD-ROM/DVD Filesystems"
678 tristate "ISO 9660 CDROM file system support"
680 This is the standard file system used on CD-ROMs. It was previously
681 known as "High Sierra File System" and is called "hsfs" on other
682 Unix systems. The so-called Rock-Ridge extensions which allow for
683 long Unix filenames and symbolic links are also supported by this
684 driver. If you have a CD-ROM drive and want to do more with it than
685 just listen to audio CDs and watch its LEDs, say Y (and read
686 <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO,
687 available from <http://www.tldp.org/docs.html#howto>), thereby
688 enlarging your kernel by about 27 KB; otherwise say N.
690 To compile this file system support as a module, choose M here: the
691 module will be called isofs.
694 bool "Microsoft Joliet CDROM extensions"
695 depends on ISO9660_FS
698 Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system
699 which allows for long filenames in unicode format (unicode is the
700 new 16 bit character code, successor to ASCII, which encodes the
701 characters of almost all languages of the world; see
702 <http://www.unicode.org/> for more information). Say Y here if you
703 want to be able to read Joliet CD-ROMs under Linux.
706 bool "Transparent decompression extension"
707 depends on ISO9660_FS
710 This is a Linux-specific extension to RockRidge which lets you store
711 data in compressed form on a CD-ROM and have it transparently
712 decompressed when the CD-ROM is accessed. See
713 <http://www.kernel.org/pub/linux/utils/fs/zisofs/> for the tools
714 necessary to create such a filesystem. Say Y here if you want to be
715 able to read such compressed CD-ROMs.
718 tristate "UDF file system support"
721 This is the new file system used on some CD-ROMs and DVDs. Say Y if
722 you intend to mount DVD discs or CDRW's written in packet mode, or
723 if written to by other UDF utilities, such as DirectCD.
724 Please read <file:Documentation/filesystems/udf.txt>.
726 To compile this file system support as a module, choose M here: the
727 module will be called udf.
734 depends on (UDF_FS=m && NLS) || (UDF_FS=y && NLS=y)
740 menu "DOS/FAT/NT Filesystems"
746 If you want to use one of the FAT-based file systems (the MS-DOS and
747 VFAT (Windows 95) file systems), then you must say Y or M here
748 to include FAT support. You will then be able to mount partitions or
749 diskettes with FAT-based file systems and transparently access the
750 files on them, i.e. MSDOS files will look and behave just like all
753 This FAT support is not a file system in itself, it only provides
754 the foundation for the other file systems. You will have to say Y or
755 M to at least one of "MSDOS fs support" or "VFAT fs support" in
756 order to make use of it.
758 Another way to read and write MSDOS floppies and hard drive
759 partitions from within Linux (but not transparently) is with the
760 mtools ("man mtools") program suite. You don't need to say Y here in
763 If you need to move large files on floppies between a DOS and a
764 Linux box, say Y here, mount the floppy under Linux with an MSDOS
765 file system and use GNU tar's M option. GNU tar is a program
766 available for Unix and DOS ("man tar" or "info tar").
768 The FAT support will enlarge your kernel by about 37 KB. If unsure,
771 To compile this as a module, choose M here: the module will be called
772 fat. Note that if you compile the FAT support as a module, you
773 cannot compile any of the FAT-based file systems into the kernel
774 -- they will have to be modules as well.
777 tristate "MSDOS fs support"
780 This allows you to mount MSDOS partitions of your hard drive (unless
781 they are compressed; to access compressed MSDOS partitions under
782 Linux, you can either use the DOS emulator DOSEMU, described in the
783 DOSEMU-HOWTO, available from
784 <http://www.tldp.org/docs.html#howto>, or try dmsdosfs in
785 <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you
786 intend to use dosemu with a non-compressed MSDOS partition, say Y
787 here) and MSDOS floppies. This means that file access becomes
788 transparent, i.e. the MSDOS files look and behave just like all
791 If you have Windows 95 or Windows NT installed on your MSDOS
792 partitions, you should use the VFAT file system (say Y to "VFAT fs
793 support" below), or you will not be able to see the long filenames
794 generated by Windows 95 / Windows NT.
796 This option will enlarge your kernel by about 7 KB. If unsure,
797 answer Y. This will only work if you said Y to "DOS FAT fs support"
798 as well. To compile this as a module, choose M here: the module will
802 tristate "VFAT (Windows-95) fs support"
805 This option provides support for normal Windows file systems with
806 long filenames. That includes non-compressed FAT-based file systems
807 used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
808 programs from the mtools package.
810 The VFAT support enlarges your kernel by about 10 KB and it only
811 works if you said Y to the "DOS FAT fs support" above. Please read
812 the file <file:Documentation/filesystems/vfat.txt> for details. If
815 To compile this as a module, choose M here: the module will be called
818 config FAT_DEFAULT_CODEPAGE
819 int "Default codepage for FAT"
820 depends on MSDOS_FS || VFAT_FS
823 This option should be set to the codepage of your FAT filesystems.
824 It can be overridden with the "codepage" mount option.
825 See <file:Documentation/filesystems/vfat.txt> for more information.
827 config FAT_DEFAULT_IOCHARSET
828 string "Default iocharset for FAT"
832 Set this to the default input/output character set you'd
833 like FAT to use. It should probably match the character set
834 that most of your FAT filesystems use, and can be overridden
835 with the "iocharset" mount option for FAT filesystems.
836 Note that "utf8" is not recommended for FAT filesystems.
837 If unsure, you shouldn't set "utf8" here.
838 See <file:Documentation/filesystems/vfat.txt> for more information.
841 tristate "NTFS file system support"
844 NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003.
846 Saying Y or M here enables read support. There is partial, but
847 safe, write support available. For write support you must also
848 say Y to "NTFS write support" below.
850 There are also a number of user-space tools available, called
851 ntfsprogs. These include ntfsundelete and ntfsresize, that work
852 without NTFS support enabled in the kernel.
854 This is a rewrite from scratch of Linux NTFS support and replaced
855 the old NTFS code starting with Linux 2.5.11. A backport to
856 the Linux 2.4 kernel series is separately available as a patch
857 from the project web site.
859 For more information see <file:Documentation/filesystems/ntfs.txt>
860 and <http://www.linux-ntfs.org/>.
862 To compile this file system support as a module, choose M here: the
863 module will be called ntfs.
865 If you are not using Windows NT, 2000, XP or 2003 in addition to
866 Linux on your computer it is safe to say N.
869 bool "NTFS debugging support"
872 If you are experiencing any problems with the NTFS file system, say
873 Y here. This will result in additional consistency checks to be
874 performed by the driver as well as additional debugging messages to
875 be written to the system log. Note that debugging messages are
876 disabled by default. To enable them, supply the option debug_msgs=1
877 at the kernel command line when booting the kernel or as an option
878 to insmod when loading the ntfs module. Once the driver is active,
879 you can enable debugging messages by doing (as root):
880 echo 1 > /proc/sys/fs/ntfs-debug
881 Replacing the "1" with "0" would disable debug messages.
883 If you leave debugging messages disabled, this results in little
884 overhead, but enabling debug messages results in very significant
885 slowdown of the system.
887 When reporting bugs, please try to have available a full dump of
888 debugging messages while the misbehaviour was occurring.
891 bool "NTFS write support"
894 This enables the partial, but safe, write support in the NTFS driver.
896 The only supported operation is overwriting existing files, without
897 changing the file length. No file or directory creation, deletion or
898 renaming is possible. Note only non-resident files can be written to
899 so you may find that some very small files (<500 bytes or so) cannot
902 While we cannot guarantee that it will not damage any data, we have
903 so far not received a single report where the driver would have
904 damaged someones data so we assume it is perfectly safe to use.
906 Note: While write support is safe in this version (a rewrite from
907 scratch of the NTFS support), it should be noted that the old NTFS
908 write support, included in Linux 2.5.10 and before (since 1997),
911 This is currently useful with TopologiLinux. TopologiLinux is run
912 on top of any DOS/Microsoft Windows system without partitioning your
913 hard disk. Unlike other Linux distributions TopologiLinux does not
914 need its own partition. For more information see
915 <http://topologi-linux.sourceforge.net/>
917 It is perfectly safe to say N here.
922 menu "Pseudo filesystems"
924 source "fs/proc/Kconfig"
927 bool "sysfs file system support" if EMBEDDED
930 The sysfs filesystem is a virtual filesystem that the kernel uses to
931 export internal kernel objects, their attributes, and their
932 relationships to one another.
934 Users can use sysfs to ascertain useful information about the running
935 kernel, such as the devices the kernel has discovered on each bus and
936 which driver each is bound to. sysfs can also be used to tune devices
937 and other kernel subsystems.
939 Some system agents rely on the information in sysfs to operate.
940 /sbin/hotplug uses device and object attributes in sysfs to assist in
941 delegating policy decisions, like persistently naming devices.
943 sysfs is currently used by the block subsystem to mount the root
944 partition. If sysfs is disabled you must specify the boot device on
945 the kernel boot command line via its major and minor numbers. For
946 example, "root=03:01" for /dev/hda1.
948 Designers of embedded systems may wish to say N here to conserve space.
951 bool "Virtual memory file system support (former shm fs)"
953 Tmpfs is a file system which keeps all files in virtual memory.
955 Everything in tmpfs is temporary in the sense that no files will be
956 created on your hard drive. The files live in memory and swap
957 space. If you unmount a tmpfs instance, everything stored therein is
960 See <file:Documentation/filesystems/tmpfs.txt> for details.
962 config TMPFS_POSIX_ACL
963 bool "Tmpfs POSIX Access Control Lists"
967 POSIX Access Control Lists (ACLs) support permissions for users and
968 groups beyond the owner/group/world scheme.
970 To learn more about Access Control Lists, visit the POSIX ACLs for
971 Linux website <http://acl.bestbits.at/>.
973 If you don't know what Access Control Lists are, say N.
976 bool "HugeTLB file system support"
977 depends on X86 || IA64 || PPC64 || SPARC64 || (SUPERH && MMU) || \
978 (S390 && 64BIT) || BROKEN
980 hugetlbfs is a filesystem backing for HugeTLB pages, based on
981 ramfs. For architectures that support it, say Y here and read
982 <file:Documentation/vm/hugetlbpage.txt> for details.
990 tristate "Userspace-driven configuration filesystem"
993 configfs is a ram-based filesystem that provides the converse
994 of sysfs's functionality. Where sysfs is a filesystem-based
995 view of kernel objects, configfs is a filesystem-based manager
996 of kernel objects, or config_items.
998 Both sysfs and configfs can and should exist together on the
999 same system. One is not a replacement for the other.
1003 menu "Miscellaneous filesystems"
1006 tristate "ADFS file system support (EXPERIMENTAL)"
1007 depends on BLOCK && EXPERIMENTAL
1009 The Acorn Disc Filing System is the standard file system of the
1010 RiscOS operating system which runs on Acorn's ARM-based Risc PC
1011 systems and the Acorn Archimedes range of machines. If you say Y
1012 here, Linux will be able to read from ADFS partitions on hard drives
1013 and from ADFS-formatted floppy discs. If you also want to be able to
1014 write to those devices, say Y to "ADFS write support" below.
1016 The ADFS partition should be the first partition (i.e.,
1017 /dev/[hs]d?1) on each of your drives. Please read the file
1018 <file:Documentation/filesystems/adfs.txt> for further details.
1020 To compile this code as a module, choose M here: the module will be
1026 bool "ADFS write support (DANGEROUS)"
1029 If you say Y here, you will be able to write to ADFS partitions on
1030 hard drives and ADFS-formatted floppy disks. This is experimental
1031 codes, so if you're unsure, say N.
1034 tristate "Amiga FFS file system support (EXPERIMENTAL)"
1035 depends on BLOCK && EXPERIMENTAL
1037 The Fast File System (FFS) is the common file system used on hard
1038 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
1039 if you want to be able to read and write files from and to an Amiga
1040 FFS partition on your hard drive. Amiga floppies however cannot be
1041 read with this driver due to an incompatibility of the floppy
1042 controller used in an Amiga and the standard floppy controller in
1043 PCs and workstations. Read <file:Documentation/filesystems/affs.txt>
1044 and <file:fs/affs/Changes>.
1046 With this driver you can also mount disk files used by Bernd
1047 Schmidt's Un*X Amiga Emulator
1048 (<http://www.freiburg.linux.de/~uae/>).
1049 If you want to do this, you will also need to say Y or M to "Loop
1050 device support", above.
1052 To compile this file system support as a module, choose M here: the
1053 module will be called affs. If unsure, say N.
1056 tristate "eCrypt filesystem layer support (EXPERIMENTAL)"
1057 depends on EXPERIMENTAL && KEYS && CRYPTO && NET
1059 Encrypted filesystem that operates on the VFS layer. See
1060 <file:Documentation/filesystems/ecryptfs.txt> to learn more about
1061 eCryptfs. Userspace components are required and can be
1062 obtained from <http://ecryptfs.sf.net>.
1064 To compile this file system support as a module, choose M here: the
1065 module will be called ecryptfs.
1068 tristate "Apple Macintosh file system support (EXPERIMENTAL)"
1069 depends on BLOCK && EXPERIMENTAL
1072 If you say Y here, you will be able to mount Macintosh-formatted
1073 floppy disks and hard drive partitions with full read-write access.
1074 Please read <file:Documentation/filesystems/hfs.txt> to learn about
1075 the available mount options.
1077 To compile this file system support as a module, choose M here: the
1078 module will be called hfs.
1081 tristate "Apple Extended HFS file system support"
1086 If you say Y here, you will be able to mount extended format
1087 Macintosh-formatted hard drive partitions with full read-write access.
1089 This file system is often called HFS+ and was introduced with
1090 MacOS 8. It includes all Mac specific filesystem data such as
1091 data forks and creator codes, but it also has several UNIX
1092 style features such as file ownership and permissions.
1095 tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)"
1096 depends on BLOCK && EXPERIMENTAL
1099 The BeOS File System (BeFS) is the native file system of Be, Inc's
1100 BeOS. Notable features include support for arbitrary attributes
1101 on files and directories, and database-like indices on selected
1102 attributes. (Also note that this driver doesn't make those features
1103 available at this time). It is a 64 bit filesystem, so it supports
1104 extremely large volumes and files.
1106 If you use this filesystem, you should also say Y to at least one
1107 of the NLS (native language support) options below.
1109 If you don't know what this is about, say N.
1111 To compile this as a module, choose M here: the module will be
1118 If you say Y here, you can use the 'debug' mount option to enable
1119 debugging output from the driver.
1122 tristate "BFS file system support (EXPERIMENTAL)"
1123 depends on BLOCK && EXPERIMENTAL
1125 Boot File System (BFS) is a file system used under SCO UnixWare to
1126 allow the bootloader access to the kernel image and other important
1127 files during the boot process. It is usually mounted under /stand
1128 and corresponds to the slice marked as "STAND" in the UnixWare
1129 partition. You should say Y if you want to read or write the files
1130 on your /stand slice from within Linux. You then also need to say Y
1131 to "UnixWare slices support", below. More information about the BFS
1132 file system is contained in the file
1133 <file:Documentation/filesystems/bfs.txt>.
1135 If you don't know what this is about, say N.
1137 To compile this as a module, choose M here: the module will be called
1138 bfs. Note that the file system of your root partition (the one
1139 containing the directory /) cannot be compiled as a module.
1144 tristate "EFS file system support (read only) (EXPERIMENTAL)"
1145 depends on BLOCK && EXPERIMENTAL
1147 EFS is an older file system used for non-ISO9660 CD-ROMs and hard
1148 disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
1149 uses the XFS file system for hard disk partitions however).
1151 This implementation only offers read-only access. If you don't know
1152 what all this is about, it's safe to say N. For more information
1153 about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
1155 To compile the EFS file system support as a module, choose M here: the
1156 module will be called efs.
1159 tristate "Journalling Flash File System v2 (JFFS2) support"
1163 JFFS2 is the second generation of the Journalling Flash File System
1164 for use on diskless embedded devices. It provides improved wear
1165 levelling, compression and support for hard links. You cannot use
1166 this on normal block devices, only on 'MTD' devices.
1168 Further information on the design and implementation of JFFS2 is
1169 available at <http://sources.redhat.com/jffs2/>.
1171 config JFFS2_FS_DEBUG
1172 int "JFFS2 debugging verbosity (0 = quiet, 2 = noisy)"
1176 This controls the amount of debugging messages produced by the JFFS2
1177 code. Set it to zero for use in production systems. For evaluation,
1178 testing and debugging, it's advisable to set it to one. This will
1179 enable a few assertions and will print debugging messages at the
1180 KERN_DEBUG loglevel, where they won't normally be visible. Level 2
1181 is unlikely to be useful - it enables extra debugging in certain
1182 areas which at one point needed debugging, but when the bugs were
1183 located and fixed, the detailed messages were relegated to level 2.
1185 If reporting bugs, please try to have available a full dump of the
1186 messages at debug level 1 while the misbehaviour was occurring.
1188 config JFFS2_FS_WRITEBUFFER
1189 bool "JFFS2 write-buffering support"
1193 This enables the write-buffering support in JFFS2.
1195 This functionality is required to support JFFS2 on the following
1196 types of flash devices:
1198 - NOR flash with transparent ECC
1201 config JFFS2_FS_WBUF_VERIFY
1202 bool "Verify JFFS2 write-buffer reads"
1203 depends on JFFS2_FS_WRITEBUFFER
1206 This causes JFFS2 to read back every page written through the
1207 write-buffer, and check for errors.
1209 config JFFS2_SUMMARY
1210 bool "JFFS2 summary support (EXPERIMENTAL)"
1211 depends on JFFS2_FS && EXPERIMENTAL
1214 This feature makes it possible to use summary information
1215 for faster filesystem mount.
1217 The summary information can be inserted into a filesystem image
1218 by the utility 'sumtool'.
1222 config JFFS2_FS_XATTR
1223 bool "JFFS2 XATTR support (EXPERIMENTAL)"
1224 depends on JFFS2_FS && EXPERIMENTAL
1227 Extended attributes are name:value pairs associated with inodes by
1228 the kernel or by users (see the attr(5) manual page, or visit
1229 <http://acl.bestbits.at/> for details).
1233 config JFFS2_FS_POSIX_ACL
1234 bool "JFFS2 POSIX Access Control Lists"
1235 depends on JFFS2_FS_XATTR
1239 Posix Access Control Lists (ACLs) support permissions for users and
1240 groups beyond the owner/group/world scheme.
1242 To learn more about Access Control Lists, visit the Posix ACLs for
1243 Linux website <http://acl.bestbits.at/>.
1245 If you don't know what Access Control Lists are, say N
1247 config JFFS2_FS_SECURITY
1248 bool "JFFS2 Security Labels"
1249 depends on JFFS2_FS_XATTR
1252 Security labels support alternative access control models
1253 implemented by security modules like SELinux. This option
1254 enables an extended attribute handler for file security
1255 labels in the jffs2 filesystem.
1257 If you are not using a security module that requires using
1258 extended attributes for file security labels, say N.
1260 config JFFS2_COMPRESSION_OPTIONS
1261 bool "Advanced compression options for JFFS2"
1265 Enabling this option allows you to explicitly choose which
1266 compression modules, if any, are enabled in JFFS2. Removing
1267 compressors can mean you cannot read existing file systems,
1268 and enabling experimental compressors can mean that you
1269 write a file system which cannot be read by a standard kernel.
1271 If unsure, you should _definitely_ say 'N'.
1274 bool "JFFS2 ZLIB compression support" if JFFS2_COMPRESSION_OPTIONS
1280 Zlib is designed to be a free, general-purpose, legally unencumbered,
1281 lossless data-compression library for use on virtually any computer
1282 hardware and operating system. See <http://www.gzip.org/zlib/> for
1283 further information.
1288 bool "JFFS2 LZO compression support" if JFFS2_COMPRESSION_OPTIONS
1290 select LZO_DECOMPRESS
1294 minilzo-based compression. Generally works better than Zlib.
1296 This feature was added in July, 2007. Say 'N' if you need
1297 compatibility with older bootloaders or kernels.
1300 bool "JFFS2 RTIME compression support" if JFFS2_COMPRESSION_OPTIONS
1304 Rtime does manage to recompress already-compressed data. Say 'Y' if unsure.
1307 bool "JFFS2 RUBIN compression support" if JFFS2_COMPRESSION_OPTIONS
1311 RUBINMIPS and DYNRUBIN compressors. Say 'N' if unsure.
1314 prompt "JFFS2 default compression mode" if JFFS2_COMPRESSION_OPTIONS
1315 default JFFS2_CMODE_PRIORITY
1318 You can set here the default compression mode of JFFS2 from
1319 the available compression modes. Don't touch if unsure.
1321 config JFFS2_CMODE_NONE
1322 bool "no compression"
1324 Uses no compression.
1326 config JFFS2_CMODE_PRIORITY
1329 Tries the compressors in a predefined order and chooses the first
1332 config JFFS2_CMODE_SIZE
1333 bool "size (EXPERIMENTAL)"
1335 Tries all compressors and chooses the one which has the smallest
1338 config JFFS2_CMODE_FAVOURLZO
1341 Tries all compressors and chooses the one which has the smallest
1342 result but gives some preference to LZO (which has faster
1343 decompression) at the expense of size.
1347 # UBIFS File system configuration
1348 source "fs/ubifs/Kconfig"
1351 tristate "Compressed ROM file system support (cramfs)"
1355 Saying Y here includes support for CramFs (Compressed ROM File
1356 System). CramFs is designed to be a simple, small, and compressed
1357 file system for ROM based embedded systems. CramFs is read-only,
1358 limited to 256MB file systems (with 16MB files), and doesn't support
1359 16/32 bits uid/gid, hard links and timestamps.
1361 See <file:Documentation/filesystems/cramfs.txt> and
1362 <file:fs/cramfs/README> for further information.
1364 To compile this as a module, choose M here: the module will be called
1365 cramfs. Note that the root file system (the one containing the
1366 directory /) cannot be compiled as a module.
1371 tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
1374 FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
1375 file system format. VERITAS VxFS(TM) is the standard file system
1376 of SCO UnixWare (and possibly others) and optionally available
1377 for Sunsoft Solaris, HP-UX and many other operating systems.
1378 Currently only readonly access is supported.
1380 NOTE: the file system type as used by mount(1), mount(2) and
1381 fstab(5) is 'vxfs' as it describes the file system format, not
1384 To compile this as a module, choose M here: the module will be
1385 called freevxfs. If unsure, say N.
1388 tristate "Minix file system support"
1391 Minix is a simple operating system used in many classes about OS's.
1392 The minix file system (method to organize files on a hard disk
1393 partition or a floppy disk) was the original file system for Linux,
1394 but has been superseded by the second extended file system ext2fs.
1395 You don't want to use the minix file system on your hard disk
1396 because of certain built-in restrictions, but it is sometimes found
1397 on older Linux floppy disks. This option will enlarge your kernel
1398 by about 28 KB. If unsure, say N.
1400 To compile this file system support as a module, choose M here: the
1401 module will be called minix. Note that the file system of your root
1402 partition (the one containing the directory /) cannot be compiled as
1406 tristate "SonicBlue Optimized MPEG File System support"
1410 This is the proprietary file system used by the Rio Karma music
1411 player and ReplayTV DVR. Despite the name, this filesystem is not
1412 more efficient than a standard FS for MPEG files, in fact likely
1413 the opposite is true. Say Y if you have either of these devices
1414 and wish to mount its disk.
1416 To compile this file system support as a module, choose M here: the
1417 module will be called omfs. If unsure, say N.
1420 tristate "OS/2 HPFS file system support"
1423 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
1424 is the file system used for organizing files on OS/2 hard disk
1425 partitions. Say Y if you want to be able to read files from and
1426 write files to an OS/2 HPFS partition on your hard drive. OS/2
1427 floppies however are in regular MSDOS format, so you don't need this
1428 option in order to be able to read them. Read
1429 <file:Documentation/filesystems/hpfs.txt>.
1431 To compile this file system support as a module, choose M here: the
1432 module will be called hpfs. If unsure, say N.
1436 tristate "QNX4 file system support (read only)"
1439 This is the file system used by the real-time operating systems
1440 QNX 4 and QNX 6 (the latter is also called QNX RTP).
1441 Further information is available at <http://www.qnx.com/>.
1442 Say Y if you intend to mount QNX hard disks or floppies.
1443 Unless you say Y to "QNX4FS read-write support" below, you will
1444 only be able to read these file systems.
1446 To compile this file system support as a module, choose M here: the
1447 module will be called qnx4.
1449 If you don't know whether you need it, then you don't need it:
1453 bool "QNX4FS write support (DANGEROUS)"
1454 depends on QNX4FS_FS && EXPERIMENTAL && BROKEN
1456 Say Y if you want to test write support for QNX4 file systems.
1458 It's currently broken, so for now:
1462 tristate "ROM file system support"
1465 This is a very small read-only file system mainly intended for
1466 initial ram disks of installation disks, but it could be used for
1467 other read-only media as well. Read
1468 <file:Documentation/filesystems/romfs.txt> for details.
1470 To compile this file system support as a module, choose M here: the
1471 module will be called romfs. Note that the file system of your
1472 root partition (the one containing the directory /) cannot be a
1475 If you don't know whether you need it, then you don't need it:
1480 tristate "System V/Xenix/V7/Coherent file system support"
1483 SCO, Xenix and Coherent are commercial Unix systems for Intel
1484 machines, and Version 7 was used on the DEC PDP-11. Saying Y
1485 here would allow you to read from their floppies and hard disk
1488 If you have floppies or hard disk partitions like that, it is likely
1489 that they contain binaries from those other Unix systems; in order
1490 to run these binaries, you will want to install linux-abi which is
1491 a set of kernel modules that lets you run SCO, Xenix, Wyse,
1492 UnixWare, Dell Unix and System V programs under Linux. It is
1493 available via FTP (user: ftp) from
1494 <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
1495 NOTE: that will work only for binaries from Intel-based systems;
1496 PDP ones will have to wait until somebody ports Linux to -11 ;-)
1498 If you only intend to mount files from some other Unix over the
1499 network using NFS, you don't need the System V file system support
1500 (but you need NFS file system support obviously).
1502 Note that this option is generally not needed for floppies, since a
1503 good portable way to transport files and directories between unixes
1504 (and even other operating systems) is given by the tar program ("man
1505 tar" or preferably "info tar"). Note also that this option has
1506 nothing whatsoever to do with the option "System V IPC". Read about
1507 the System V file system in
1508 <file:Documentation/filesystems/sysv-fs.txt>.
1509 Saying Y here will enlarge your kernel by about 27 KB.
1511 To compile this as a module, choose M here: the module will be called
1514 If you haven't heard about all of this before, it's safe to say N.
1518 tristate "UFS file system support (read only)"
1521 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
1522 OpenBSD and NeXTstep) use a file system called UFS. Some System V
1523 Unixes can create and mount hard disk partitions and diskettes using
1524 this file system as well. Saying Y here will allow you to read from
1525 these partitions; if you also want to write to them, say Y to the
1526 experimental "UFS file system write support", below. Please read the
1527 file <file:Documentation/filesystems/ufs.txt> for more information.
1529 The recently released UFS2 variant (used in FreeBSD 5.x) is
1530 READ-ONLY supported.
1532 Note that this option is generally not needed for floppies, since a
1533 good portable way to transport files and directories between unixes
1534 (and even other operating systems) is given by the tar program ("man
1535 tar" or preferably "info tar").
1537 When accessing NeXTstep files, you may need to convert them from the
1538 NeXT character set to the Latin1 character set; use the program
1539 recode ("info recode") for this purpose.
1541 To compile the UFS file system support as a module, choose M here: the
1542 module will be called ufs.
1544 If you haven't heard about all of this before, it's safe to say N.
1547 bool "UFS file system write support (DANGEROUS)"
1548 depends on UFS_FS && EXPERIMENTAL
1550 Say Y here if you want to try writing to UFS partitions. This is
1551 experimental, so you should back up your UFS partitions beforehand.
1554 bool "UFS debugging"
1557 If you are experiencing any problems with the UFS filesystem, say
1558 Y here. This will result in _many_ additional debugging messages to be
1559 written to the system log.
1563 menuconfig NETWORK_FILESYSTEMS
1564 bool "Network File Systems"
1568 Say Y here to get to see options for network filesystems and
1569 filesystem-related networking code, such as NFS daemon and
1570 RPCSEC security modules.
1572 This option alone does not add any kernel code.
1574 If you say N, all options in this submenu will be skipped and
1575 disabled; if unsure, say Y here.
1577 if NETWORK_FILESYSTEMS
1580 tristate "NFS client support"
1584 select NFS_ACL_SUPPORT if NFS_V3_ACL
1586 Choose Y here if you want to access files residing on other
1587 computers using Sun's Network File System protocol. To compile
1588 this file system support as a module, choose M here: the module
1591 To mount file systems exported by NFS servers, you also need to
1592 install the user space mount.nfs command which can be found in
1593 the Linux nfs-utils package, available from http://linux-nfs.org/.
1594 Information about using the mount command is available in the
1595 mount(8) man page. More detail about the Linux NFS client
1596 implementation is available via the nfs(5) man page.
1598 Below you can choose which versions of the NFS protocol are
1599 available in the kernel to mount NFS servers. Support for NFS
1600 version 2 (RFC 1094) is always available when NFS_FS is selected.
1602 To configure a system which mounts its root file system via NFS
1603 at boot time, say Y here, select "Kernel level IP
1604 autoconfiguration" in the NETWORK menu, and select "Root file
1605 system on NFS" below. You cannot compile this file system as a
1606 module in this case.
1611 bool "NFS client support for NFS version 3"
1614 This option enables support for version 3 of the NFS protocol
1615 (RFC 1813) in the kernel's NFS client.
1620 bool "NFS client support for the NFSv3 ACL protocol extension"
1623 Some NFS servers support an auxiliary NFSv3 ACL protocol that
1624 Sun added to Solaris but never became an official part of the
1625 NFS version 3 protocol. This protocol extension allows
1626 applications on NFS clients to manipulate POSIX Access Control
1627 Lists on files residing on NFS servers. NFS servers enforce
1628 ACLs on local files whether this protocol is available or not.
1630 Choose Y here if your NFS server supports the Solaris NFSv3 ACL
1631 protocol extension and you want your NFS client to allow
1632 applications to access and modify ACLs on files on the server.
1634 Most NFS servers don't support the Solaris NFSv3 ACL protocol
1635 extension. You can choose N here or specify the "noacl" mount
1636 option to prevent your NFS client from trying to use the NFSv3
1642 bool "NFS client support for NFS version 4 (EXPERIMENTAL)"
1643 depends on NFS_FS && EXPERIMENTAL
1644 select RPCSEC_GSS_KRB5
1646 This option enables support for version 4 of the NFS protocol
1647 (RFC 3530) in the kernel's NFS client.
1649 To mount NFS servers using NFSv4, you also need to install user
1650 space programs which can be found in the Linux nfs-utils package,
1651 available from http://linux-nfs.org/.
1656 bool "Root file system on NFS"
1657 depends on NFS_FS=y && IP_PNP
1659 If you want your system to mount its root file system via NFS,
1660 choose Y here. This is common practice for managing systems
1661 without local permanent storage. For details, read
1662 <file:Documentation/filesystems/nfsroot.txt>.
1664 Most people say N here.
1667 tristate "NFS server support"
1672 select NFS_ACL_SUPPORT if NFSD_V2_ACL
1674 Choose Y here if you want to allow other computers to access
1675 files residing on this system using Sun's Network File System
1676 protocol. To compile the NFS server support as a module,
1677 choose M here: the module will be called nfsd.
1679 You may choose to use a user-space NFS server instead, in which
1680 case you can choose N here.
1682 To export local file systems using NFS, you also need to install
1683 user space programs which can be found in the Linux nfs-utils
1684 package, available from http://linux-nfs.org/. More detail about
1685 the Linux NFS server implementation is available via the
1686 exports(5) man page.
1688 Below you can choose which versions of the NFS protocol are
1689 available to clients mounting the NFS server on this system.
1690 Support for NFS version 2 (RFC 1094) is always available when
1691 CONFIG_NFSD is selected.
1700 bool "NFS server support for NFS version 3"
1703 This option enables support in your system's NFS server for
1704 version 3 of the NFS protocol (RFC 1813).
1709 bool "NFS server support for the NFSv3 ACL protocol extension"
1713 Solaris NFS servers support an auxiliary NFSv3 ACL protocol that
1714 never became an official part of the NFS version 3 protocol.
1715 This protocol extension allows applications on NFS clients to
1716 manipulate POSIX Access Control Lists on files residing on NFS
1717 servers. NFS servers enforce POSIX ACLs on local files whether
1718 this protocol is available or not.
1720 This option enables support in your system's NFS server for the
1721 NFSv3 ACL protocol extension allowing NFS clients to manipulate
1722 POSIX ACLs on files exported by your system's NFS server. NFS
1723 clients which support the Solaris NFSv3 ACL protocol can then
1724 access and modify ACLs on your NFS server.
1726 To store ACLs on your NFS server, you also need to enable ACL-
1727 related CONFIG options for your local file systems of choice.
1732 bool "NFS server support for NFS version 4 (EXPERIMENTAL)"
1733 depends on NFSD && PROC_FS && EXPERIMENTAL
1736 select RPCSEC_GSS_KRB5
1738 This option enables support in your system's NFS server for
1739 version 4 of the NFS protocol (RFC 3530).
1741 To export files using NFSv4, you need to install additional user
1742 space programs which can be found in the Linux nfs-utils package,
1743 available from http://linux-nfs.org/.
1752 depends on NFSD_V3 || NFS_V3
1758 config NFS_ACL_SUPPORT
1764 depends on NFSD || NFS_FS
1773 config SUNRPC_XPRT_RDMA
1775 depends on SUNRPC && INFINIBAND && EXPERIMENTAL
1776 default SUNRPC && INFINIBAND
1778 This option enables an RPC client transport capability that
1779 allows the NFS client to mount servers via an RDMA-enabled
1782 To compile RPC client RDMA transport support as a module,
1783 choose M here: the module will be called xprtrdma.
1787 config RPCSEC_GSS_KRB5
1788 tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
1789 depends on SUNRPC && EXPERIMENTAL
1796 Choose Y here to enable Secure RPC using the Kerberos version 5
1797 GSS-API mechanism (RFC 1964).
1799 Secure RPC calls with Kerberos require an auxiliary user-space
1800 daemon which may be found in the Linux nfs-utils package
1801 available from http://linux-nfs.org/. In addition, user-space
1802 Kerberos support should be installed.
1806 config RPCSEC_GSS_SPKM3
1807 tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
1808 depends on SUNRPC && EXPERIMENTAL
1816 Choose Y here to enable Secure RPC using the SPKM3 public key
1817 GSS-API mechansim (RFC 2025).
1819 Secure RPC calls with SPKM3 require an auxiliary userspace
1820 daemon which may be found in the Linux nfs-utils package
1821 available from http://linux-nfs.org/.
1826 tristate "SMB file system support (OBSOLETE, please use CIFS)"
1830 SMB (Server Message Block) is the protocol Windows for Workgroups
1831 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
1832 files and printers over local networks. Saying Y here allows you to
1833 mount their file systems (often called "shares" in this context) and
1834 access them just like any other Unix directory. Currently, this
1835 works only if the Windows machines use TCP/IP as the underlying
1836 transport protocol, and not NetBEUI. For details, read
1837 <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
1838 available from <http://www.tldp.org/docs.html#howto>.
1840 Note: if you just want your box to act as an SMB *server* and make
1841 files and printing services available to Windows clients (which need
1842 to have a TCP/IP stack), you don't need to say Y here; you can use
1843 the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
1846 General information about how to connect Linux, Windows machines and
1847 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1849 To compile the SMB support as a module, choose M here:
1850 the module will be called smbfs. Most people say N, however.
1852 config SMB_NLS_DEFAULT
1853 bool "Use a default NLS"
1856 Enabling this will make smbfs use nls translations by default. You
1857 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
1858 settings and you need to give the default nls for the SMB server as
1859 CONFIG_SMB_NLS_REMOTE.
1861 The nls settings can be changed at mount time, if your smbmount
1862 supports that, using the codepage and iocharset parameters.
1864 smbmount from samba 2.2.0 or later supports this.
1866 config SMB_NLS_REMOTE
1867 string "Default Remote NLS Option"
1868 depends on SMB_NLS_DEFAULT
1871 This setting allows you to specify a default value for which
1872 codepage the server uses. If this field is left blank no
1873 translations will be done by default. The local codepage/charset
1874 default to CONFIG_NLS_DEFAULT.
1876 The nls settings can be changed at mount time, if your smbmount
1877 supports that, using the codepage and iocharset parameters.
1879 smbmount from samba 2.2.0 or later supports this.
1882 tristate "CIFS support (advanced network filesystem, SMBFS successor)"
1886 This is the client VFS module for the Common Internet File System
1887 (CIFS) protocol which is the successor to the Server Message Block
1888 (SMB) protocol, the native file sharing mechanism for most early
1889 PC operating systems. The CIFS protocol is fully supported by
1890 file servers such as Windows 2000 (including Windows 2003, NT 4
1891 and Windows XP) as well by Samba (which provides excellent CIFS
1892 server support for Linux and many other operating systems). Limited
1893 support for OS/2 and Windows ME and similar servers is provided as
1896 The cifs module provides an advanced network file system
1897 client for mounting to CIFS compliant servers. It includes
1898 support for DFS (hierarchical name space), secure per-user
1899 session establishment via Kerberos or NTLM or NTLMv2,
1900 safe distributed caching (oplock), optional packet
1901 signing, Unicode and other internationalization improvements.
1902 If you need to mount to Samba or Windows from this machine, say Y.
1905 bool "CIFS statistics"
1908 Enabling this option will cause statistics for each server share
1909 mounted by the cifs client to be displayed in /proc/fs/cifs/Stats
1912 bool "Extended statistics"
1913 depends on CIFS_STATS
1915 Enabling this option will allow more detailed statistics on SMB
1916 request timing to be displayed in /proc/fs/cifs/DebugData and also
1917 allow optional logging of slow responses to dmesg (depending on the
1918 value of /proc/fs/cifs/cifsFYI, see fs/cifs/README for more details).
1919 These additional statistics may have a minor effect on performance
1920 and memory utilization.
1922 Unless you are a developer or are doing network performance analysis
1925 config CIFS_WEAK_PW_HASH
1926 bool "Support legacy servers which use weaker LANMAN security"
1929 Modern CIFS servers including Samba and most Windows versions
1930 (since 1997) support stronger NTLM (and even NTLMv2 and Kerberos)
1931 security mechanisms. These hash the password more securely
1932 than the mechanisms used in the older LANMAN version of the
1933 SMB protocol but LANMAN based authentication is needed to
1934 establish sessions with some old SMB servers.
1936 Enabling this option allows the cifs module to mount to older
1937 LANMAN based servers such as OS/2 and Windows 95, but such
1938 mounts may be less secure than mounts using NTLM or more recent
1939 security mechanisms if you are on a public network. Unless you
1940 have a need to access old SMB servers (and are on a private
1941 network) you probably want to say N. Even if this support
1942 is enabled in the kernel build, LANMAN authentication will not be
1943 used automatically. At runtime LANMAN mounts are disabled but
1944 can be set to required (or optional) either in
1945 /proc/fs/cifs (see fs/cifs/README for more detail) or via an
1946 option on the mount command. This support is disabled by
1947 default in order to reduce the possibility of a downgrade
1953 bool "Kerberos/SPNEGO advanced session setup"
1954 depends on CIFS && KEYS
1956 Enables an upcall mechanism for CIFS which accesses
1957 userspace helper utilities to provide SPNEGO packaged (RFC 4178)
1958 Kerberos tickets which are needed to mount to certain secure servers
1959 (for which more secure Kerberos authentication is required). If
1963 bool "CIFS extended attributes"
1966 Extended attributes are name:value pairs associated with inodes by
1967 the kernel or by users (see the attr(5) manual page, or visit
1968 <http://acl.bestbits.at/> for details). CIFS maps the name of
1969 extended attributes beginning with the user namespace prefix
1970 to SMB/CIFS EAs. EAs are stored on Windows servers without the
1971 user namespace prefix, but their names are seen by Linux cifs clients
1972 prefaced by the user namespace prefix. The system namespace
1973 (used by some filesystems to store ACLs) is not supported at
1979 bool "CIFS POSIX Extensions"
1980 depends on CIFS_XATTR
1982 Enabling this option will cause the cifs client to attempt to
1983 negotiate a newer dialect with servers, such as Samba 3.0.5
1984 or later, that optionally can handle more POSIX like (rather
1985 than Windows like) file behavior. It also enables
1986 support for POSIX ACLs (getfacl and setfacl) to servers
1987 (such as Samba 3.10 and later) which can negotiate
1988 CIFS POSIX ACL support. If unsure, say N.
1991 bool "Enable additional CIFS debugging routines"
1994 Enabling this option adds a few more debugging routines
1995 to the cifs code which slightly increases the size of
1996 the cifs module and can cause additional logging of debug
1997 messages in some error paths, slowing performance. This
1998 option can be turned off unless you are debugging
1999 cifs problems. If unsure, say N.
2001 config CIFS_EXPERIMENTAL
2002 bool "CIFS Experimental Features (EXPERIMENTAL)"
2003 depends on CIFS && EXPERIMENTAL
2005 Enables cifs features under testing. These features are
2006 experimental and currently include DFS support and directory
2007 change notification ie fcntl(F_DNOTIFY), as well as the upcall
2008 mechanism which will be used for Kerberos session negotiation
2009 and uid remapping. Some of these features also may depend on
2010 setting a value of 1 to the pseudo-file /proc/fs/cifs/Experimental
2011 (which is disabled by default). See the file fs/cifs/README
2012 for more details. If unsure, say N.
2014 config CIFS_DFS_UPCALL
2015 bool "DFS feature support (EXPERIMENTAL)"
2016 depends on CIFS_EXPERIMENTAL
2019 Enables an upcall mechanism for CIFS which contacts userspace
2020 helper utilities to provide server name resolution (host names to
2021 IP addresses) which is needed for implicit mounts of DFS junction
2022 points. If unsure, say N.
2025 tristate "NCP file system support (to mount NetWare volumes)"
2026 depends on IPX!=n || INET
2028 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
2029 used by Novell NetWare clients to talk to file servers. It is to
2030 IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
2031 to mount NetWare file server volumes and to access them just like
2032 any other Unix directory. For details, please read the file
2033 <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
2034 the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
2036 You do not have to say Y here if you want your Linux box to act as a
2037 file *server* for Novell NetWare clients.
2039 General information about how to connect Linux, Windows machines and
2040 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
2042 To compile this as a module, choose M here: the module will be called
2043 ncpfs. Say N unless you are connected to a Novell network.
2045 source "fs/ncpfs/Kconfig"
2048 tristate "Coda file system support (advanced network fs)"
2051 Coda is an advanced network file system, similar to NFS in that it
2052 enables you to mount file systems of a remote server and access them
2053 with regular Unix commands as if they were sitting on your hard
2054 disk. Coda has several advantages over NFS: support for
2055 disconnected operation (e.g. for laptops), read/write server
2056 replication, security model for authentication and encryption,
2057 persistent client caches and write back caching.
2059 If you say Y here, your Linux box will be able to act as a Coda
2060 *client*. You will need user level code as well, both for the
2061 client and server. Servers are currently user level, i.e. they need
2062 no kernel support. Please read
2063 <file:Documentation/filesystems/coda.txt> and check out the Coda
2064 home page <http://www.coda.cs.cmu.edu/>.
2066 To compile the coda client support as a module, choose M here: the
2067 module will be called coda.
2070 tristate "Andrew File System support (AFS) (EXPERIMENTAL)"
2071 depends on INET && EXPERIMENTAL
2074 If you say Y here, you will get an experimental Andrew File System
2075 driver. It currently only supports unsecured read-only AFS access.
2077 See <file:Documentation/filesystems/afs.txt> for more information.
2082 bool "AFS dynamic debugging"
2085 Say Y here to make runtime controllable debugging messages appear.
2087 See <file:Documentation/filesystems/afs.txt> for more information.
2092 tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
2093 depends on INET && NET_9P && EXPERIMENTAL
2095 If you say Y here, you will get experimental support for
2096 Plan 9 resource sharing via the 9P2000 protocol.
2098 See <http://v9fs.sf.net> for more information.
2102 endif # NETWORK_FILESYSTEMS
2105 menu "Partition Types"
2107 source "fs/partitions/Kconfig"
2112 source "fs/nls/Kconfig"
2113 source "fs/dlm/Kconfig"