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
505 Btrfs is a new filesystem with extents, writable snapshotting,
506 support for multiple devices and many more features.
508 Btrfs is highly experimental, and THE DISK FORMAT IS NOT YET
509 FINALIZED. You should say N here unless you are interested in
510 testing Btrfs with non-critical data.
512 To compile this file system support as a module, choose M here. The
513 module will be called btrfs.
520 bool "Dnotify support"
523 Dnotify is a directory-based per-fd file change notification system
524 that uses signals to communicate events to user-space. There exist
525 superior alternatives, but some applications may still rely on
531 bool "Inotify file change notification support"
534 Say Y here to enable inotify support. Inotify is a file change
535 notification system and a replacement for dnotify. Inotify fixes
536 numerous shortcomings in dnotify and introduces several new features
537 including multiple file events, one-shot support, and unmount
540 For more information, see <file:Documentation/filesystems/inotify.txt>
545 bool "Inotify support for userspace"
549 Say Y here to enable inotify support for userspace, including the
550 associated system calls. Inotify allows monitoring of both files and
551 directories via a single open fd. Events are read from the file
552 descriptor, which is also select()- and poll()-able.
554 For more information, see <file:Documentation/filesystems/inotify.txt>
561 If you say Y here, you will be able to set per user limits for disk
562 usage (also called disk quotas). Currently, it works for the
563 ext2, ext3, and reiserfs file system. ext3 also supports journalled
564 quotas for which you don't need to run quotacheck(8) after an unclean
566 For further details, read the Quota mini-HOWTO, available from
567 <http://www.tldp.org/docs.html#howto>, or the documentation provided
568 with the quota tools. Probably the quota support is only useful for
569 multi user systems. If unsure, say N.
571 config QUOTA_NETLINK_INTERFACE
572 bool "Report quota messages through netlink interface"
573 depends on QUOTA && NET
575 If you say Y here, quota warnings (about exceeding softlimit, reaching
576 hardlimit, etc.) will be reported through netlink interface. If unsure,
579 config PRINT_QUOTA_WARNING
580 bool "Print quota warnings to console (OBSOLETE)"
584 If you say Y here, quota warnings (about exceeding softlimit, reaching
585 hardlimit, etc.) will be printed to the process' controlling terminal.
586 Note that this behavior is currently deprecated and may go away in
587 future. Please use notification via netlink socket instead.
590 tristate "Old quota format support"
593 This quota format was (is) used by kernels earlier than 2.4.22. If
594 you have quota working and you don't want to convert to new quota
598 tristate "Quota format v2 support"
601 This quota format allows using quotas with 32-bit UIDs/GIDs. If you
602 need this functionality say Y here.
606 depends on XFS_QUOTA || QUOTA
610 tristate "Kernel automounter support"
612 The automounter is a tool to automatically mount remote file systems
613 on demand. This implementation is partially kernel-based to reduce
614 overhead in the already-mounted case; this is unlike the BSD
615 automounter (amd), which is a pure user space daemon.
617 To use the automounter you need the user-space tools from the autofs
618 package; you can find the location in <file:Documentation/Changes>.
619 You also want to answer Y to "NFS file system support", below.
621 If you want to use the newer version of the automounter with more
622 features, say N here and say Y to "Kernel automounter v4 support",
625 To compile this support as a module, choose M here: the module will be
628 If you are not a part of a fairly large, distributed network, you
629 probably do not need an automounter, and can say N here.
632 tristate "Kernel automounter version 4 support (also supports v3)"
634 The automounter is a tool to automatically mount remote file systems
635 on demand. This implementation is partially kernel-based to reduce
636 overhead in the already-mounted case; this is unlike the BSD
637 automounter (amd), which is a pure user space daemon.
639 To use the automounter you need the user-space tools from
640 <ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4/>; you also
641 want to answer Y to "NFS file system support", below.
643 To compile this support as a module, choose M here: the module will be
644 called autofs4. You will need to add "alias autofs autofs4" to your
645 modules configuration file.
647 If you are not a part of a fairly large, distributed network or
648 don't have a laptop which needs to dynamically reconfigure to the
649 local network, you probably do not need an automounter, and can say
653 tristate "Filesystem in Userspace support"
655 With FUSE it is possible to implement a fully functional filesystem
656 in a userspace program.
658 There's also companion library: libfuse. This library along with
659 utilities is available from the FUSE homepage:
660 <http://fuse.sourceforge.net/>
662 See <file:Documentation/filesystems/fuse.txt> for more information.
663 See <file:Documentation/Changes> for needed library/utility version.
665 If you want to develop a userspace FS, or if you want to use
666 a filesystem based on FUSE, answer Y or M.
673 menu "CD-ROM/DVD Filesystems"
676 tristate "ISO 9660 CDROM file system support"
678 This is the standard file system used on CD-ROMs. It was previously
679 known as "High Sierra File System" and is called "hsfs" on other
680 Unix systems. The so-called Rock-Ridge extensions which allow for
681 long Unix filenames and symbolic links are also supported by this
682 driver. If you have a CD-ROM drive and want to do more with it than
683 just listen to audio CDs and watch its LEDs, say Y (and read
684 <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO,
685 available from <http://www.tldp.org/docs.html#howto>), thereby
686 enlarging your kernel by about 27 KB; otherwise say N.
688 To compile this file system support as a module, choose M here: the
689 module will be called isofs.
692 bool "Microsoft Joliet CDROM extensions"
693 depends on ISO9660_FS
696 Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system
697 which allows for long filenames in unicode format (unicode is the
698 new 16 bit character code, successor to ASCII, which encodes the
699 characters of almost all languages of the world; see
700 <http://www.unicode.org/> for more information). Say Y here if you
701 want to be able to read Joliet CD-ROMs under Linux.
704 bool "Transparent decompression extension"
705 depends on ISO9660_FS
708 This is a Linux-specific extension to RockRidge which lets you store
709 data in compressed form on a CD-ROM and have it transparently
710 decompressed when the CD-ROM is accessed. See
711 <http://www.kernel.org/pub/linux/utils/fs/zisofs/> for the tools
712 necessary to create such a filesystem. Say Y here if you want to be
713 able to read such compressed CD-ROMs.
716 tristate "UDF file system support"
719 This is the new file system used on some CD-ROMs and DVDs. Say Y if
720 you intend to mount DVD discs or CDRW's written in packet mode, or
721 if written to by other UDF utilities, such as DirectCD.
722 Please read <file:Documentation/filesystems/udf.txt>.
724 To compile this file system support as a module, choose M here: the
725 module will be called udf.
732 depends on (UDF_FS=m && NLS) || (UDF_FS=y && NLS=y)
738 menu "DOS/FAT/NT Filesystems"
744 If you want to use one of the FAT-based file systems (the MS-DOS and
745 VFAT (Windows 95) file systems), then you must say Y or M here
746 to include FAT support. You will then be able to mount partitions or
747 diskettes with FAT-based file systems and transparently access the
748 files on them, i.e. MSDOS files will look and behave just like all
751 This FAT support is not a file system in itself, it only provides
752 the foundation for the other file systems. You will have to say Y or
753 M to at least one of "MSDOS fs support" or "VFAT fs support" in
754 order to make use of it.
756 Another way to read and write MSDOS floppies and hard drive
757 partitions from within Linux (but not transparently) is with the
758 mtools ("man mtools") program suite. You don't need to say Y here in
761 If you need to move large files on floppies between a DOS and a
762 Linux box, say Y here, mount the floppy under Linux with an MSDOS
763 file system and use GNU tar's M option. GNU tar is a program
764 available for Unix and DOS ("man tar" or "info tar").
766 The FAT support will enlarge your kernel by about 37 KB. If unsure,
769 To compile this as a module, choose M here: the module will be called
770 fat. Note that if you compile the FAT support as a module, you
771 cannot compile any of the FAT-based file systems into the kernel
772 -- they will have to be modules as well.
775 tristate "MSDOS fs support"
778 This allows you to mount MSDOS partitions of your hard drive (unless
779 they are compressed; to access compressed MSDOS partitions under
780 Linux, you can either use the DOS emulator DOSEMU, described in the
781 DOSEMU-HOWTO, available from
782 <http://www.tldp.org/docs.html#howto>, or try dmsdosfs in
783 <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you
784 intend to use dosemu with a non-compressed MSDOS partition, say Y
785 here) and MSDOS floppies. This means that file access becomes
786 transparent, i.e. the MSDOS files look and behave just like all
789 If you have Windows 95 or Windows NT installed on your MSDOS
790 partitions, you should use the VFAT file system (say Y to "VFAT fs
791 support" below), or you will not be able to see the long filenames
792 generated by Windows 95 / Windows NT.
794 This option will enlarge your kernel by about 7 KB. If unsure,
795 answer Y. This will only work if you said Y to "DOS FAT fs support"
796 as well. To compile this as a module, choose M here: the module will
800 tristate "VFAT (Windows-95) fs support"
803 This option provides support for normal Windows file systems with
804 long filenames. That includes non-compressed FAT-based file systems
805 used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
806 programs from the mtools package.
808 The VFAT support enlarges your kernel by about 10 KB and it only
809 works if you said Y to the "DOS FAT fs support" above. Please read
810 the file <file:Documentation/filesystems/vfat.txt> for details. If
813 To compile this as a module, choose M here: the module will be called
816 config FAT_DEFAULT_CODEPAGE
817 int "Default codepage for FAT"
818 depends on MSDOS_FS || VFAT_FS
821 This option should be set to the codepage of your FAT filesystems.
822 It can be overridden with the "codepage" mount option.
823 See <file:Documentation/filesystems/vfat.txt> for more information.
825 config FAT_DEFAULT_IOCHARSET
826 string "Default iocharset for FAT"
830 Set this to the default input/output character set you'd
831 like FAT to use. It should probably match the character set
832 that most of your FAT filesystems use, and can be overridden
833 with the "iocharset" mount option for FAT filesystems.
834 Note that "utf8" is not recommended for FAT filesystems.
835 If unsure, you shouldn't set "utf8" here.
836 See <file:Documentation/filesystems/vfat.txt> for more information.
839 tristate "NTFS file system support"
842 NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003.
844 Saying Y or M here enables read support. There is partial, but
845 safe, write support available. For write support you must also
846 say Y to "NTFS write support" below.
848 There are also a number of user-space tools available, called
849 ntfsprogs. These include ntfsundelete and ntfsresize, that work
850 without NTFS support enabled in the kernel.
852 This is a rewrite from scratch of Linux NTFS support and replaced
853 the old NTFS code starting with Linux 2.5.11. A backport to
854 the Linux 2.4 kernel series is separately available as a patch
855 from the project web site.
857 For more information see <file:Documentation/filesystems/ntfs.txt>
858 and <http://www.linux-ntfs.org/>.
860 To compile this file system support as a module, choose M here: the
861 module will be called ntfs.
863 If you are not using Windows NT, 2000, XP or 2003 in addition to
864 Linux on your computer it is safe to say N.
867 bool "NTFS debugging support"
870 If you are experiencing any problems with the NTFS file system, say
871 Y here. This will result in additional consistency checks to be
872 performed by the driver as well as additional debugging messages to
873 be written to the system log. Note that debugging messages are
874 disabled by default. To enable them, supply the option debug_msgs=1
875 at the kernel command line when booting the kernel or as an option
876 to insmod when loading the ntfs module. Once the driver is active,
877 you can enable debugging messages by doing (as root):
878 echo 1 > /proc/sys/fs/ntfs-debug
879 Replacing the "1" with "0" would disable debug messages.
881 If you leave debugging messages disabled, this results in little
882 overhead, but enabling debug messages results in very significant
883 slowdown of the system.
885 When reporting bugs, please try to have available a full dump of
886 debugging messages while the misbehaviour was occurring.
889 bool "NTFS write support"
892 This enables the partial, but safe, write support in the NTFS driver.
894 The only supported operation is overwriting existing files, without
895 changing the file length. No file or directory creation, deletion or
896 renaming is possible. Note only non-resident files can be written to
897 so you may find that some very small files (<500 bytes or so) cannot
900 While we cannot guarantee that it will not damage any data, we have
901 so far not received a single report where the driver would have
902 damaged someones data so we assume it is perfectly safe to use.
904 Note: While write support is safe in this version (a rewrite from
905 scratch of the NTFS support), it should be noted that the old NTFS
906 write support, included in Linux 2.5.10 and before (since 1997),
909 This is currently useful with TopologiLinux. TopologiLinux is run
910 on top of any DOS/Microsoft Windows system without partitioning your
911 hard disk. Unlike other Linux distributions TopologiLinux does not
912 need its own partition. For more information see
913 <http://topologi-linux.sourceforge.net/>
915 It is perfectly safe to say N here.
920 menu "Pseudo filesystems"
922 source "fs/proc/Kconfig"
925 bool "sysfs file system support" if EMBEDDED
928 The sysfs filesystem is a virtual filesystem that the kernel uses to
929 export internal kernel objects, their attributes, and their
930 relationships to one another.
932 Users can use sysfs to ascertain useful information about the running
933 kernel, such as the devices the kernel has discovered on each bus and
934 which driver each is bound to. sysfs can also be used to tune devices
935 and other kernel subsystems.
937 Some system agents rely on the information in sysfs to operate.
938 /sbin/hotplug uses device and object attributes in sysfs to assist in
939 delegating policy decisions, like persistently naming devices.
941 sysfs is currently used by the block subsystem to mount the root
942 partition. If sysfs is disabled you must specify the boot device on
943 the kernel boot command line via its major and minor numbers. For
944 example, "root=03:01" for /dev/hda1.
946 Designers of embedded systems may wish to say N here to conserve space.
949 bool "Virtual memory file system support (former shm fs)"
951 Tmpfs is a file system which keeps all files in virtual memory.
953 Everything in tmpfs is temporary in the sense that no files will be
954 created on your hard drive. The files live in memory and swap
955 space. If you unmount a tmpfs instance, everything stored therein is
958 See <file:Documentation/filesystems/tmpfs.txt> for details.
960 config TMPFS_POSIX_ACL
961 bool "Tmpfs POSIX Access Control Lists"
965 POSIX Access Control Lists (ACLs) support permissions for users and
966 groups beyond the owner/group/world scheme.
968 To learn more about Access Control Lists, visit the POSIX ACLs for
969 Linux website <http://acl.bestbits.at/>.
971 If you don't know what Access Control Lists are, say N.
974 bool "HugeTLB file system support"
975 depends on X86 || IA64 || PPC64 || SPARC64 || (SUPERH && MMU) || \
976 (S390 && 64BIT) || BROKEN
978 hugetlbfs is a filesystem backing for HugeTLB pages, based on
979 ramfs. For architectures that support it, say Y here and read
980 <file:Documentation/vm/hugetlbpage.txt> for details.
988 tristate "Userspace-driven configuration filesystem"
991 configfs is a ram-based filesystem that provides the converse
992 of sysfs's functionality. Where sysfs is a filesystem-based
993 view of kernel objects, configfs is a filesystem-based manager
994 of kernel objects, or config_items.
996 Both sysfs and configfs can and should exist together on the
997 same system. One is not a replacement for the other.
1001 menu "Miscellaneous filesystems"
1004 tristate "ADFS file system support (EXPERIMENTAL)"
1005 depends on BLOCK && EXPERIMENTAL
1007 The Acorn Disc Filing System is the standard file system of the
1008 RiscOS operating system which runs on Acorn's ARM-based Risc PC
1009 systems and the Acorn Archimedes range of machines. If you say Y
1010 here, Linux will be able to read from ADFS partitions on hard drives
1011 and from ADFS-formatted floppy discs. If you also want to be able to
1012 write to those devices, say Y to "ADFS write support" below.
1014 The ADFS partition should be the first partition (i.e.,
1015 /dev/[hs]d?1) on each of your drives. Please read the file
1016 <file:Documentation/filesystems/adfs.txt> for further details.
1018 To compile this code as a module, choose M here: the module will be
1024 bool "ADFS write support (DANGEROUS)"
1027 If you say Y here, you will be able to write to ADFS partitions on
1028 hard drives and ADFS-formatted floppy disks. This is experimental
1029 codes, so if you're unsure, say N.
1032 tristate "Amiga FFS file system support (EXPERIMENTAL)"
1033 depends on BLOCK && EXPERIMENTAL
1035 The Fast File System (FFS) is the common file system used on hard
1036 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
1037 if you want to be able to read and write files from and to an Amiga
1038 FFS partition on your hard drive. Amiga floppies however cannot be
1039 read with this driver due to an incompatibility of the floppy
1040 controller used in an Amiga and the standard floppy controller in
1041 PCs and workstations. Read <file:Documentation/filesystems/affs.txt>
1042 and <file:fs/affs/Changes>.
1044 With this driver you can also mount disk files used by Bernd
1045 Schmidt's Un*X Amiga Emulator
1046 (<http://www.freiburg.linux.de/~uae/>).
1047 If you want to do this, you will also need to say Y or M to "Loop
1048 device support", above.
1050 To compile this file system support as a module, choose M here: the
1051 module will be called affs. If unsure, say N.
1054 tristate "eCrypt filesystem layer support (EXPERIMENTAL)"
1055 depends on EXPERIMENTAL && KEYS && CRYPTO && NET
1057 Encrypted filesystem that operates on the VFS layer. See
1058 <file:Documentation/filesystems/ecryptfs.txt> to learn more about
1059 eCryptfs. Userspace components are required and can be
1060 obtained from <http://ecryptfs.sf.net>.
1062 To compile this file system support as a module, choose M here: the
1063 module will be called ecryptfs.
1066 tristate "Apple Macintosh file system support (EXPERIMENTAL)"
1067 depends on BLOCK && EXPERIMENTAL
1070 If you say Y here, you will be able to mount Macintosh-formatted
1071 floppy disks and hard drive partitions with full read-write access.
1072 Please read <file:Documentation/filesystems/hfs.txt> to learn about
1073 the available mount options.
1075 To compile this file system support as a module, choose M here: the
1076 module will be called hfs.
1079 tristate "Apple Extended HFS file system support"
1084 If you say Y here, you will be able to mount extended format
1085 Macintosh-formatted hard drive partitions with full read-write access.
1087 This file system is often called HFS+ and was introduced with
1088 MacOS 8. It includes all Mac specific filesystem data such as
1089 data forks and creator codes, but it also has several UNIX
1090 style features such as file ownership and permissions.
1093 tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)"
1094 depends on BLOCK && EXPERIMENTAL
1097 The BeOS File System (BeFS) is the native file system of Be, Inc's
1098 BeOS. Notable features include support for arbitrary attributes
1099 on files and directories, and database-like indices on selected
1100 attributes. (Also note that this driver doesn't make those features
1101 available at this time). It is a 64 bit filesystem, so it supports
1102 extremely large volumes and files.
1104 If you use this filesystem, you should also say Y to at least one
1105 of the NLS (native language support) options below.
1107 If you don't know what this is about, say N.
1109 To compile this as a module, choose M here: the module will be
1116 If you say Y here, you can use the 'debug' mount option to enable
1117 debugging output from the driver.
1120 tristate "BFS file system support (EXPERIMENTAL)"
1121 depends on BLOCK && EXPERIMENTAL
1123 Boot File System (BFS) is a file system used under SCO UnixWare to
1124 allow the bootloader access to the kernel image and other important
1125 files during the boot process. It is usually mounted under /stand
1126 and corresponds to the slice marked as "STAND" in the UnixWare
1127 partition. You should say Y if you want to read or write the files
1128 on your /stand slice from within Linux. You then also need to say Y
1129 to "UnixWare slices support", below. More information about the BFS
1130 file system is contained in the file
1131 <file:Documentation/filesystems/bfs.txt>.
1133 If you don't know what this is about, say N.
1135 To compile this as a module, choose M here: the module will be called
1136 bfs. Note that the file system of your root partition (the one
1137 containing the directory /) cannot be compiled as a module.
1142 tristate "EFS file system support (read only) (EXPERIMENTAL)"
1143 depends on BLOCK && EXPERIMENTAL
1145 EFS is an older file system used for non-ISO9660 CD-ROMs and hard
1146 disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
1147 uses the XFS file system for hard disk partitions however).
1149 This implementation only offers read-only access. If you don't know
1150 what all this is about, it's safe to say N. For more information
1151 about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
1153 To compile the EFS file system support as a module, choose M here: the
1154 module will be called efs.
1157 tristate "Journalling Flash File System v2 (JFFS2) support"
1161 JFFS2 is the second generation of the Journalling Flash File System
1162 for use on diskless embedded devices. It provides improved wear
1163 levelling, compression and support for hard links. You cannot use
1164 this on normal block devices, only on 'MTD' devices.
1166 Further information on the design and implementation of JFFS2 is
1167 available at <http://sources.redhat.com/jffs2/>.
1169 config JFFS2_FS_DEBUG
1170 int "JFFS2 debugging verbosity (0 = quiet, 2 = noisy)"
1174 This controls the amount of debugging messages produced by the JFFS2
1175 code. Set it to zero for use in production systems. For evaluation,
1176 testing and debugging, it's advisable to set it to one. This will
1177 enable a few assertions and will print debugging messages at the
1178 KERN_DEBUG loglevel, where they won't normally be visible. Level 2
1179 is unlikely to be useful - it enables extra debugging in certain
1180 areas which at one point needed debugging, but when the bugs were
1181 located and fixed, the detailed messages were relegated to level 2.
1183 If reporting bugs, please try to have available a full dump of the
1184 messages at debug level 1 while the misbehaviour was occurring.
1186 config JFFS2_FS_WRITEBUFFER
1187 bool "JFFS2 write-buffering support"
1191 This enables the write-buffering support in JFFS2.
1193 This functionality is required to support JFFS2 on the following
1194 types of flash devices:
1196 - NOR flash with transparent ECC
1199 config JFFS2_FS_WBUF_VERIFY
1200 bool "Verify JFFS2 write-buffer reads"
1201 depends on JFFS2_FS_WRITEBUFFER
1204 This causes JFFS2 to read back every page written through the
1205 write-buffer, and check for errors.
1207 config JFFS2_SUMMARY
1208 bool "JFFS2 summary support (EXPERIMENTAL)"
1209 depends on JFFS2_FS && EXPERIMENTAL
1212 This feature makes it possible to use summary information
1213 for faster filesystem mount.
1215 The summary information can be inserted into a filesystem image
1216 by the utility 'sumtool'.
1220 config JFFS2_FS_XATTR
1221 bool "JFFS2 XATTR support (EXPERIMENTAL)"
1222 depends on JFFS2_FS && EXPERIMENTAL
1225 Extended attributes are name:value pairs associated with inodes by
1226 the kernel or by users (see the attr(5) manual page, or visit
1227 <http://acl.bestbits.at/> for details).
1231 config JFFS2_FS_POSIX_ACL
1232 bool "JFFS2 POSIX Access Control Lists"
1233 depends on JFFS2_FS_XATTR
1237 Posix Access Control Lists (ACLs) support permissions for users and
1238 groups beyond the owner/group/world scheme.
1240 To learn more about Access Control Lists, visit the Posix ACLs for
1241 Linux website <http://acl.bestbits.at/>.
1243 If you don't know what Access Control Lists are, say N
1245 config JFFS2_FS_SECURITY
1246 bool "JFFS2 Security Labels"
1247 depends on JFFS2_FS_XATTR
1250 Security labels support alternative access control models
1251 implemented by security modules like SELinux. This option
1252 enables an extended attribute handler for file security
1253 labels in the jffs2 filesystem.
1255 If you are not using a security module that requires using
1256 extended attributes for file security labels, say N.
1258 config JFFS2_COMPRESSION_OPTIONS
1259 bool "Advanced compression options for JFFS2"
1263 Enabling this option allows you to explicitly choose which
1264 compression modules, if any, are enabled in JFFS2. Removing
1265 compressors can mean you cannot read existing file systems,
1266 and enabling experimental compressors can mean that you
1267 write a file system which cannot be read by a standard kernel.
1269 If unsure, you should _definitely_ say 'N'.
1272 bool "JFFS2 ZLIB compression support" if JFFS2_COMPRESSION_OPTIONS
1278 Zlib is designed to be a free, general-purpose, legally unencumbered,
1279 lossless data-compression library for use on virtually any computer
1280 hardware and operating system. See <http://www.gzip.org/zlib/> for
1281 further information.
1286 bool "JFFS2 LZO compression support" if JFFS2_COMPRESSION_OPTIONS
1288 select LZO_DECOMPRESS
1292 minilzo-based compression. Generally works better than Zlib.
1294 This feature was added in July, 2007. Say 'N' if you need
1295 compatibility with older bootloaders or kernels.
1298 bool "JFFS2 RTIME compression support" if JFFS2_COMPRESSION_OPTIONS
1302 Rtime does manage to recompress already-compressed data. Say 'Y' if unsure.
1305 bool "JFFS2 RUBIN compression support" if JFFS2_COMPRESSION_OPTIONS
1309 RUBINMIPS and DYNRUBIN compressors. Say 'N' if unsure.
1312 prompt "JFFS2 default compression mode" if JFFS2_COMPRESSION_OPTIONS
1313 default JFFS2_CMODE_PRIORITY
1316 You can set here the default compression mode of JFFS2 from
1317 the available compression modes. Don't touch if unsure.
1319 config JFFS2_CMODE_NONE
1320 bool "no compression"
1322 Uses no compression.
1324 config JFFS2_CMODE_PRIORITY
1327 Tries the compressors in a predefined order and chooses the first
1330 config JFFS2_CMODE_SIZE
1331 bool "size (EXPERIMENTAL)"
1333 Tries all compressors and chooses the one which has the smallest
1336 config JFFS2_CMODE_FAVOURLZO
1339 Tries all compressors and chooses the one which has the smallest
1340 result but gives some preference to LZO (which has faster
1341 decompression) at the expense of size.
1345 # UBIFS File system configuration
1346 source "fs/ubifs/Kconfig"
1349 tristate "Compressed ROM file system support (cramfs)"
1353 Saying Y here includes support for CramFs (Compressed ROM File
1354 System). CramFs is designed to be a simple, small, and compressed
1355 file system for ROM based embedded systems. CramFs is read-only,
1356 limited to 256MB file systems (with 16MB files), and doesn't support
1357 16/32 bits uid/gid, hard links and timestamps.
1359 See <file:Documentation/filesystems/cramfs.txt> and
1360 <file:fs/cramfs/README> for further information.
1362 To compile this as a module, choose M here: the module will be called
1363 cramfs. Note that the root file system (the one containing the
1364 directory /) cannot be compiled as a module.
1369 tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
1372 FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
1373 file system format. VERITAS VxFS(TM) is the standard file system
1374 of SCO UnixWare (and possibly others) and optionally available
1375 for Sunsoft Solaris, HP-UX and many other operating systems.
1376 Currently only readonly access is supported.
1378 NOTE: the file system type as used by mount(1), mount(2) and
1379 fstab(5) is 'vxfs' as it describes the file system format, not
1382 To compile this as a module, choose M here: the module will be
1383 called freevxfs. If unsure, say N.
1386 tristate "Minix file system support"
1389 Minix is a simple operating system used in many classes about OS's.
1390 The minix file system (method to organize files on a hard disk
1391 partition or a floppy disk) was the original file system for Linux,
1392 but has been superseded by the second extended file system ext2fs.
1393 You don't want to use the minix file system on your hard disk
1394 because of certain built-in restrictions, but it is sometimes found
1395 on older Linux floppy disks. This option will enlarge your kernel
1396 by about 28 KB. If unsure, say N.
1398 To compile this file system support as a module, choose M here: the
1399 module will be called minix. Note that the file system of your root
1400 partition (the one containing the directory /) cannot be compiled as
1404 tristate "SonicBlue Optimized MPEG File System support"
1408 This is the proprietary file system used by the Rio Karma music
1409 player and ReplayTV DVR. Despite the name, this filesystem is not
1410 more efficient than a standard FS for MPEG files, in fact likely
1411 the opposite is true. Say Y if you have either of these devices
1412 and wish to mount its disk.
1414 To compile this file system support as a module, choose M here: the
1415 module will be called omfs. If unsure, say N.
1418 tristate "OS/2 HPFS file system support"
1421 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
1422 is the file system used for organizing files on OS/2 hard disk
1423 partitions. Say Y if you want to be able to read files from and
1424 write files to an OS/2 HPFS partition on your hard drive. OS/2
1425 floppies however are in regular MSDOS format, so you don't need this
1426 option in order to be able to read them. Read
1427 <file:Documentation/filesystems/hpfs.txt>.
1429 To compile this file system support as a module, choose M here: the
1430 module will be called hpfs. If unsure, say N.
1434 tristate "QNX4 file system support (read only)"
1437 This is the file system used by the real-time operating systems
1438 QNX 4 and QNX 6 (the latter is also called QNX RTP).
1439 Further information is available at <http://www.qnx.com/>.
1440 Say Y if you intend to mount QNX hard disks or floppies.
1441 Unless you say Y to "QNX4FS read-write support" below, you will
1442 only be able to read these file systems.
1444 To compile this file system support as a module, choose M here: the
1445 module will be called qnx4.
1447 If you don't know whether you need it, then you don't need it:
1451 bool "QNX4FS write support (DANGEROUS)"
1452 depends on QNX4FS_FS && EXPERIMENTAL && BROKEN
1454 Say Y if you want to test write support for QNX4 file systems.
1456 It's currently broken, so for now:
1460 tristate "ROM file system support"
1463 This is a very small read-only file system mainly intended for
1464 initial ram disks of installation disks, but it could be used for
1465 other read-only media as well. Read
1466 <file:Documentation/filesystems/romfs.txt> for details.
1468 To compile this file system support as a module, choose M here: the
1469 module will be called romfs. Note that the file system of your
1470 root partition (the one containing the directory /) cannot be a
1473 If you don't know whether you need it, then you don't need it:
1478 tristate "System V/Xenix/V7/Coherent file system support"
1481 SCO, Xenix and Coherent are commercial Unix systems for Intel
1482 machines, and Version 7 was used on the DEC PDP-11. Saying Y
1483 here would allow you to read from their floppies and hard disk
1486 If you have floppies or hard disk partitions like that, it is likely
1487 that they contain binaries from those other Unix systems; in order
1488 to run these binaries, you will want to install linux-abi which is
1489 a set of kernel modules that lets you run SCO, Xenix, Wyse,
1490 UnixWare, Dell Unix and System V programs under Linux. It is
1491 available via FTP (user: ftp) from
1492 <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
1493 NOTE: that will work only for binaries from Intel-based systems;
1494 PDP ones will have to wait until somebody ports Linux to -11 ;-)
1496 If you only intend to mount files from some other Unix over the
1497 network using NFS, you don't need the System V file system support
1498 (but you need NFS file system support obviously).
1500 Note that this option is generally not needed for floppies, since a
1501 good portable way to transport files and directories between unixes
1502 (and even other operating systems) is given by the tar program ("man
1503 tar" or preferably "info tar"). Note also that this option has
1504 nothing whatsoever to do with the option "System V IPC". Read about
1505 the System V file system in
1506 <file:Documentation/filesystems/sysv-fs.txt>.
1507 Saying Y here will enlarge your kernel by about 27 KB.
1509 To compile this as a module, choose M here: the module will be called
1512 If you haven't heard about all of this before, it's safe to say N.
1516 tristate "UFS file system support (read only)"
1519 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
1520 OpenBSD and NeXTstep) use a file system called UFS. Some System V
1521 Unixes can create and mount hard disk partitions and diskettes using
1522 this file system as well. Saying Y here will allow you to read from
1523 these partitions; if you also want to write to them, say Y to the
1524 experimental "UFS file system write support", below. Please read the
1525 file <file:Documentation/filesystems/ufs.txt> for more information.
1527 The recently released UFS2 variant (used in FreeBSD 5.x) is
1528 READ-ONLY supported.
1530 Note that this option is generally not needed for floppies, since a
1531 good portable way to transport files and directories between unixes
1532 (and even other operating systems) is given by the tar program ("man
1533 tar" or preferably "info tar").
1535 When accessing NeXTstep files, you may need to convert them from the
1536 NeXT character set to the Latin1 character set; use the program
1537 recode ("info recode") for this purpose.
1539 To compile the UFS file system support as a module, choose M here: the
1540 module will be called ufs.
1542 If you haven't heard about all of this before, it's safe to say N.
1545 bool "UFS file system write support (DANGEROUS)"
1546 depends on UFS_FS && EXPERIMENTAL
1548 Say Y here if you want to try writing to UFS partitions. This is
1549 experimental, so you should back up your UFS partitions beforehand.
1552 bool "UFS debugging"
1555 If you are experiencing any problems with the UFS filesystem, say
1556 Y here. This will result in _many_ additional debugging messages to be
1557 written to the system log.
1561 menuconfig NETWORK_FILESYSTEMS
1562 bool "Network File Systems"
1566 Say Y here to get to see options for network filesystems and
1567 filesystem-related networking code, such as NFS daemon and
1568 RPCSEC security modules.
1570 This option alone does not add any kernel code.
1572 If you say N, all options in this submenu will be skipped and
1573 disabled; if unsure, say Y here.
1575 if NETWORK_FILESYSTEMS
1578 tristate "NFS client support"
1582 select NFS_ACL_SUPPORT if NFS_V3_ACL
1584 Choose Y here if you want to access files residing on other
1585 computers using Sun's Network File System protocol. To compile
1586 this file system support as a module, choose M here: the module
1589 To mount file systems exported by NFS servers, you also need to
1590 install the user space mount.nfs command which can be found in
1591 the Linux nfs-utils package, available from http://linux-nfs.org/.
1592 Information about using the mount command is available in the
1593 mount(8) man page. More detail about the Linux NFS client
1594 implementation is available via the nfs(5) man page.
1596 Below you can choose which versions of the NFS protocol are
1597 available in the kernel to mount NFS servers. Support for NFS
1598 version 2 (RFC 1094) is always available when NFS_FS is selected.
1600 To configure a system which mounts its root file system via NFS
1601 at boot time, say Y here, select "Kernel level IP
1602 autoconfiguration" in the NETWORK menu, and select "Root file
1603 system on NFS" below. You cannot compile this file system as a
1604 module in this case.
1609 bool "NFS client support for NFS version 3"
1612 This option enables support for version 3 of the NFS protocol
1613 (RFC 1813) in the kernel's NFS client.
1618 bool "NFS client support for the NFSv3 ACL protocol extension"
1621 Some NFS servers support an auxiliary NFSv3 ACL protocol that
1622 Sun added to Solaris but never became an official part of the
1623 NFS version 3 protocol. This protocol extension allows
1624 applications on NFS clients to manipulate POSIX Access Control
1625 Lists on files residing on NFS servers. NFS servers enforce
1626 ACLs on local files whether this protocol is available or not.
1628 Choose Y here if your NFS server supports the Solaris NFSv3 ACL
1629 protocol extension and you want your NFS client to allow
1630 applications to access and modify ACLs on files on the server.
1632 Most NFS servers don't support the Solaris NFSv3 ACL protocol
1633 extension. You can choose N here or specify the "noacl" mount
1634 option to prevent your NFS client from trying to use the NFSv3
1640 bool "NFS client support for NFS version 4 (EXPERIMENTAL)"
1641 depends on NFS_FS && EXPERIMENTAL
1642 select RPCSEC_GSS_KRB5
1644 This option enables support for version 4 of the NFS protocol
1645 (RFC 3530) in the kernel's NFS client.
1647 To mount NFS servers using NFSv4, you also need to install user
1648 space programs which can be found in the Linux nfs-utils package,
1649 available from http://linux-nfs.org/.
1654 bool "Root file system on NFS"
1655 depends on NFS_FS=y && IP_PNP
1657 If you want your system to mount its root file system via NFS,
1658 choose Y here. This is common practice for managing systems
1659 without local permanent storage. For details, read
1660 <file:Documentation/filesystems/nfsroot.txt>.
1662 Most people say N here.
1665 tristate "NFS server support"
1670 select NFS_ACL_SUPPORT if NFSD_V2_ACL
1672 Choose Y here if you want to allow other computers to access
1673 files residing on this system using Sun's Network File System
1674 protocol. To compile the NFS server support as a module,
1675 choose M here: the module will be called nfsd.
1677 You may choose to use a user-space NFS server instead, in which
1678 case you can choose N here.
1680 To export local file systems using NFS, you also need to install
1681 user space programs which can be found in the Linux nfs-utils
1682 package, available from http://linux-nfs.org/. More detail about
1683 the Linux NFS server implementation is available via the
1684 exports(5) man page.
1686 Below you can choose which versions of the NFS protocol are
1687 available to clients mounting the NFS server on this system.
1688 Support for NFS version 2 (RFC 1094) is always available when
1689 CONFIG_NFSD is selected.
1698 bool "NFS server support for NFS version 3"
1701 This option enables support in your system's NFS server for
1702 version 3 of the NFS protocol (RFC 1813).
1707 bool "NFS server support for the NFSv3 ACL protocol extension"
1711 Solaris NFS servers support an auxiliary NFSv3 ACL protocol that
1712 never became an official part of the NFS version 3 protocol.
1713 This protocol extension allows applications on NFS clients to
1714 manipulate POSIX Access Control Lists on files residing on NFS
1715 servers. NFS servers enforce POSIX ACLs on local files whether
1716 this protocol is available or not.
1718 This option enables support in your system's NFS server for the
1719 NFSv3 ACL protocol extension allowing NFS clients to manipulate
1720 POSIX ACLs on files exported by your system's NFS server. NFS
1721 clients which support the Solaris NFSv3 ACL protocol can then
1722 access and modify ACLs on your NFS server.
1724 To store ACLs on your NFS server, you also need to enable ACL-
1725 related CONFIG options for your local file systems of choice.
1730 bool "NFS server support for NFS version 4 (EXPERIMENTAL)"
1731 depends on NFSD && PROC_FS && EXPERIMENTAL
1734 select RPCSEC_GSS_KRB5
1736 This option enables support in your system's NFS server for
1737 version 4 of the NFS protocol (RFC 3530).
1739 To export files using NFSv4, you need to install additional user
1740 space programs which can be found in the Linux nfs-utils package,
1741 available from http://linux-nfs.org/.
1750 depends on NFSD_V3 || NFS_V3
1756 config NFS_ACL_SUPPORT
1762 depends on NFSD || NFS_FS
1771 config SUNRPC_XPRT_RDMA
1773 depends on SUNRPC && INFINIBAND && EXPERIMENTAL
1774 default SUNRPC && INFINIBAND
1776 This option enables an RPC client transport capability that
1777 allows the NFS client to mount servers via an RDMA-enabled
1780 To compile RPC client RDMA transport support as a module,
1781 choose M here: the module will be called xprtrdma.
1785 config RPCSEC_GSS_KRB5
1786 tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
1787 depends on SUNRPC && EXPERIMENTAL
1794 Choose Y here to enable Secure RPC using the Kerberos version 5
1795 GSS-API mechanism (RFC 1964).
1797 Secure RPC calls with Kerberos require an auxiliary user-space
1798 daemon which may be found in the Linux nfs-utils package
1799 available from http://linux-nfs.org/. In addition, user-space
1800 Kerberos support should be installed.
1804 config RPCSEC_GSS_SPKM3
1805 tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
1806 depends on SUNRPC && EXPERIMENTAL
1814 Choose Y here to enable Secure RPC using the SPKM3 public key
1815 GSS-API mechansim (RFC 2025).
1817 Secure RPC calls with SPKM3 require an auxiliary userspace
1818 daemon which may be found in the Linux nfs-utils package
1819 available from http://linux-nfs.org/.
1824 tristate "SMB file system support (OBSOLETE, please use CIFS)"
1828 SMB (Server Message Block) is the protocol Windows for Workgroups
1829 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
1830 files and printers over local networks. Saying Y here allows you to
1831 mount their file systems (often called "shares" in this context) and
1832 access them just like any other Unix directory. Currently, this
1833 works only if the Windows machines use TCP/IP as the underlying
1834 transport protocol, and not NetBEUI. For details, read
1835 <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
1836 available from <http://www.tldp.org/docs.html#howto>.
1838 Note: if you just want your box to act as an SMB *server* and make
1839 files and printing services available to Windows clients (which need
1840 to have a TCP/IP stack), you don't need to say Y here; you can use
1841 the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
1844 General information about how to connect Linux, Windows machines and
1845 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1847 To compile the SMB support as a module, choose M here:
1848 the module will be called smbfs. Most people say N, however.
1850 config SMB_NLS_DEFAULT
1851 bool "Use a default NLS"
1854 Enabling this will make smbfs use nls translations by default. You
1855 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
1856 settings and you need to give the default nls for the SMB server as
1857 CONFIG_SMB_NLS_REMOTE.
1859 The nls settings can be changed at mount time, if your smbmount
1860 supports that, using the codepage and iocharset parameters.
1862 smbmount from samba 2.2.0 or later supports this.
1864 config SMB_NLS_REMOTE
1865 string "Default Remote NLS Option"
1866 depends on SMB_NLS_DEFAULT
1869 This setting allows you to specify a default value for which
1870 codepage the server uses. If this field is left blank no
1871 translations will be done by default. The local codepage/charset
1872 default to CONFIG_NLS_DEFAULT.
1874 The nls settings can be changed at mount time, if your smbmount
1875 supports that, using the codepage and iocharset parameters.
1877 smbmount from samba 2.2.0 or later supports this.
1880 tristate "CIFS support (advanced network filesystem, SMBFS successor)"
1884 This is the client VFS module for the Common Internet File System
1885 (CIFS) protocol which is the successor to the Server Message Block
1886 (SMB) protocol, the native file sharing mechanism for most early
1887 PC operating systems. The CIFS protocol is fully supported by
1888 file servers such as Windows 2000 (including Windows 2003, NT 4
1889 and Windows XP) as well by Samba (which provides excellent CIFS
1890 server support for Linux and many other operating systems). Limited
1891 support for OS/2 and Windows ME and similar servers is provided as
1894 The cifs module provides an advanced network file system
1895 client for mounting to CIFS compliant servers. It includes
1896 support for DFS (hierarchical name space), secure per-user
1897 session establishment via Kerberos or NTLM or NTLMv2,
1898 safe distributed caching (oplock), optional packet
1899 signing, Unicode and other internationalization improvements.
1900 If you need to mount to Samba or Windows from this machine, say Y.
1903 bool "CIFS statistics"
1906 Enabling this option will cause statistics for each server share
1907 mounted by the cifs client to be displayed in /proc/fs/cifs/Stats
1910 bool "Extended statistics"
1911 depends on CIFS_STATS
1913 Enabling this option will allow more detailed statistics on SMB
1914 request timing to be displayed in /proc/fs/cifs/DebugData and also
1915 allow optional logging of slow responses to dmesg (depending on the
1916 value of /proc/fs/cifs/cifsFYI, see fs/cifs/README for more details).
1917 These additional statistics may have a minor effect on performance
1918 and memory utilization.
1920 Unless you are a developer or are doing network performance analysis
1923 config CIFS_WEAK_PW_HASH
1924 bool "Support legacy servers which use weaker LANMAN security"
1927 Modern CIFS servers including Samba and most Windows versions
1928 (since 1997) support stronger NTLM (and even NTLMv2 and Kerberos)
1929 security mechanisms. These hash the password more securely
1930 than the mechanisms used in the older LANMAN version of the
1931 SMB protocol but LANMAN based authentication is needed to
1932 establish sessions with some old SMB servers.
1934 Enabling this option allows the cifs module to mount to older
1935 LANMAN based servers such as OS/2 and Windows 95, but such
1936 mounts may be less secure than mounts using NTLM or more recent
1937 security mechanisms if you are on a public network. Unless you
1938 have a need to access old SMB servers (and are on a private
1939 network) you probably want to say N. Even if this support
1940 is enabled in the kernel build, LANMAN authentication will not be
1941 used automatically. At runtime LANMAN mounts are disabled but
1942 can be set to required (or optional) either in
1943 /proc/fs/cifs (see fs/cifs/README for more detail) or via an
1944 option on the mount command. This support is disabled by
1945 default in order to reduce the possibility of a downgrade
1951 bool "Kerberos/SPNEGO advanced session setup"
1952 depends on CIFS && KEYS
1954 Enables an upcall mechanism for CIFS which accesses
1955 userspace helper utilities to provide SPNEGO packaged (RFC 4178)
1956 Kerberos tickets which are needed to mount to certain secure servers
1957 (for which more secure Kerberos authentication is required). If
1961 bool "CIFS extended attributes"
1964 Extended attributes are name:value pairs associated with inodes by
1965 the kernel or by users (see the attr(5) manual page, or visit
1966 <http://acl.bestbits.at/> for details). CIFS maps the name of
1967 extended attributes beginning with the user namespace prefix
1968 to SMB/CIFS EAs. EAs are stored on Windows servers without the
1969 user namespace prefix, but their names are seen by Linux cifs clients
1970 prefaced by the user namespace prefix. The system namespace
1971 (used by some filesystems to store ACLs) is not supported at
1977 bool "CIFS POSIX Extensions"
1978 depends on CIFS_XATTR
1980 Enabling this option will cause the cifs client to attempt to
1981 negotiate a newer dialect with servers, such as Samba 3.0.5
1982 or later, that optionally can handle more POSIX like (rather
1983 than Windows like) file behavior. It also enables
1984 support for POSIX ACLs (getfacl and setfacl) to servers
1985 (such as Samba 3.10 and later) which can negotiate
1986 CIFS POSIX ACL support. If unsure, say N.
1989 bool "Enable additional CIFS debugging routines"
1992 Enabling this option adds a few more debugging routines
1993 to the cifs code which slightly increases the size of
1994 the cifs module and can cause additional logging of debug
1995 messages in some error paths, slowing performance. This
1996 option can be turned off unless you are debugging
1997 cifs problems. If unsure, say N.
1999 config CIFS_EXPERIMENTAL
2000 bool "CIFS Experimental Features (EXPERIMENTAL)"
2001 depends on CIFS && EXPERIMENTAL
2003 Enables cifs features under testing. These features are
2004 experimental and currently include DFS support and directory
2005 change notification ie fcntl(F_DNOTIFY), as well as the upcall
2006 mechanism which will be used for Kerberos session negotiation
2007 and uid remapping. Some of these features also may depend on
2008 setting a value of 1 to the pseudo-file /proc/fs/cifs/Experimental
2009 (which is disabled by default). See the file fs/cifs/README
2010 for more details. If unsure, say N.
2012 config CIFS_DFS_UPCALL
2013 bool "DFS feature support (EXPERIMENTAL)"
2014 depends on CIFS_EXPERIMENTAL
2017 Enables an upcall mechanism for CIFS which contacts userspace
2018 helper utilities to provide server name resolution (host names to
2019 IP addresses) which is needed for implicit mounts of DFS junction
2020 points. If unsure, say N.
2023 tristate "NCP file system support (to mount NetWare volumes)"
2024 depends on IPX!=n || INET
2026 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
2027 used by Novell NetWare clients to talk to file servers. It is to
2028 IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
2029 to mount NetWare file server volumes and to access them just like
2030 any other Unix directory. For details, please read the file
2031 <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
2032 the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
2034 You do not have to say Y here if you want your Linux box to act as a
2035 file *server* for Novell NetWare clients.
2037 General information about how to connect Linux, Windows machines and
2038 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
2040 To compile this as a module, choose M here: the module will be called
2041 ncpfs. Say N unless you are connected to a Novell network.
2043 source "fs/ncpfs/Kconfig"
2046 tristate "Coda file system support (advanced network fs)"
2049 Coda is an advanced network file system, similar to NFS in that it
2050 enables you to mount file systems of a remote server and access them
2051 with regular Unix commands as if they were sitting on your hard
2052 disk. Coda has several advantages over NFS: support for
2053 disconnected operation (e.g. for laptops), read/write server
2054 replication, security model for authentication and encryption,
2055 persistent client caches and write back caching.
2057 If you say Y here, your Linux box will be able to act as a Coda
2058 *client*. You will need user level code as well, both for the
2059 client and server. Servers are currently user level, i.e. they need
2060 no kernel support. Please read
2061 <file:Documentation/filesystems/coda.txt> and check out the Coda
2062 home page <http://www.coda.cs.cmu.edu/>.
2064 To compile the coda client support as a module, choose M here: the
2065 module will be called coda.
2068 tristate "Andrew File System support (AFS) (EXPERIMENTAL)"
2069 depends on INET && EXPERIMENTAL
2072 If you say Y here, you will get an experimental Andrew File System
2073 driver. It currently only supports unsecured read-only AFS access.
2075 See <file:Documentation/filesystems/afs.txt> for more information.
2080 bool "AFS dynamic debugging"
2083 Say Y here to make runtime controllable debugging messages appear.
2085 See <file:Documentation/filesystems/afs.txt> for more information.
2090 tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
2091 depends on INET && NET_9P && EXPERIMENTAL
2093 If you say Y here, you will get experimental support for
2094 Plan 9 resource sharing via the 9P2000 protocol.
2096 See <http://v9fs.sf.net> for more information.
2100 endif # NETWORK_FILESYSTEMS
2103 menu "Partition Types"
2105 source "fs/partitions/Kconfig"
2110 source "fs/nls/Kconfig"
2111 source "fs/dlm/Kconfig"