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)
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>.
447 config OCFS2_DEBUG_MASKLOG
448 bool "OCFS2 logging support"
452 The ocfs2 filesystem has an extensive logging system. The system
453 allows selection of events to log via files in /sys/o2cb/logmask/.
454 This option will enlarge your kernel, but it allows debugging of
455 ocfs2 filesystem issues.
457 config OCFS2_DEBUG_FS
458 bool "OCFS2 expensive checks"
462 This option will enable expensive consistency checks. Enable
463 this option for debugging only as it is likely to decrease
464 performance of the filesystem.
467 tristate "Minix fs support"
469 Minix is a simple operating system used in many classes about OS's.
470 The minix file system (method to organize files on a hard disk
471 partition or a floppy disk) was the original file system for Linux,
472 but has been superseded by the second extended file system ext2fs.
473 You don't want to use the minix file system on your hard disk
474 because of certain built-in restrictions, but it is sometimes found
475 on older Linux floppy disks. This option will enlarge your kernel
476 by about 28 KB. If unsure, say N.
478 To compile this file system support as a module, choose M here: the
479 module will be called minix. Note that the file system of your root
480 partition (the one containing the directory /) cannot be compiled as
484 tristate "ROM file system support"
486 This is a very small read-only file system mainly intended for
487 initial ram disks of installation disks, but it could be used for
488 other read-only media as well. Read
489 <file:Documentation/filesystems/romfs.txt> for details.
491 To compile this file system support as a module, choose M here: the
492 module will be called romfs. Note that the file system of your
493 root partition (the one containing the directory /) cannot be a
496 If you don't know whether you need it, then you don't need it:
502 bool "Inotify file change notification support"
505 Say Y here to enable inotify support. Inotify is a file change
506 notification system and a replacement for dnotify. Inotify fixes
507 numerous shortcomings in dnotify and introduces several new features
508 including multiple file events, one-shot support, and unmount
511 For more information, see <file:Documentation/filesystems/inotify.txt>
516 bool "Inotify support for userspace"
520 Say Y here to enable inotify support for userspace, including the
521 associated system calls. Inotify allows monitoring of both files and
522 directories via a single open fd. Events are read from the file
523 descriptor, which is also select()- and poll()-able.
525 For more information, see <file:Documentation/filesystems/inotify.txt>
532 If you say Y here, you will be able to set per user limits for disk
533 usage (also called disk quotas). Currently, it works for the
534 ext2, ext3, and reiserfs file system. ext3 also supports journalled
535 quotas for which you don't need to run quotacheck(8) after an unclean
537 For further details, read the Quota mini-HOWTO, available from
538 <http://www.tldp.org/docs.html#howto>, or the documentation provided
539 with the quota tools. Probably the quota support is only useful for
540 multi user systems. If unsure, say N.
542 config QUOTA_NETLINK_INTERFACE
543 bool "Report quota messages through netlink interface"
544 depends on QUOTA && NET
546 If you say Y here, quota warnings (about exceeding softlimit, reaching
547 hardlimit, etc.) will be reported through netlink interface. If unsure,
550 config PRINT_QUOTA_WARNING
551 bool "Print quota warnings to console (OBSOLETE)"
555 If you say Y here, quota warnings (about exceeding softlimit, reaching
556 hardlimit, etc.) will be printed to the process' controlling terminal.
557 Note that this behavior is currently deprecated and may go away in
558 future. Please use notification via netlink socket instead.
561 tristate "Old quota format support"
564 This quota format was (is) used by kernels earlier than 2.4.22. If
565 you have quota working and you don't want to convert to new quota
569 tristate "Quota format v2 support"
572 This quota format allows using quotas with 32-bit UIDs/GIDs. If you
573 need this functionality say Y here.
577 depends on XFS_QUOTA || QUOTA
581 bool "Dnotify support"
584 Dnotify is a directory-based per-fd file change notification system
585 that uses signals to communicate events to user-space. There exist
586 superior alternatives, but some applications may still rely on
592 tristate "Kernel automounter support"
594 The automounter is a tool to automatically mount remote file systems
595 on demand. This implementation is partially kernel-based to reduce
596 overhead in the already-mounted case; this is unlike the BSD
597 automounter (amd), which is a pure user space daemon.
599 To use the automounter you need the user-space tools from the autofs
600 package; you can find the location in <file:Documentation/Changes>.
601 You also want to answer Y to "NFS file system support", below.
603 If you want to use the newer version of the automounter with more
604 features, say N here and say Y to "Kernel automounter v4 support",
607 To compile this support as a module, choose M here: the module will be
610 If you are not a part of a fairly large, distributed network, you
611 probably do not need an automounter, and can say N here.
614 tristate "Kernel automounter version 4 support (also supports v3)"
616 The automounter is a tool to automatically mount remote file systems
617 on demand. This implementation is partially kernel-based to reduce
618 overhead in the already-mounted case; this is unlike the BSD
619 automounter (amd), which is a pure user space daemon.
621 To use the automounter you need the user-space tools from
622 <ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4/>; you also
623 want to answer Y to "NFS file system support", below.
625 To compile this support as a module, choose M here: the module will be
626 called autofs4. You will need to add "alias autofs autofs4" to your
627 modules configuration file.
629 If you are not a part of a fairly large, distributed network or
630 don't have a laptop which needs to dynamically reconfigure to the
631 local network, you probably do not need an automounter, and can say
635 tristate "Filesystem in Userspace support"
637 With FUSE it is possible to implement a fully functional filesystem
638 in a userspace program.
640 There's also companion library: libfuse. This library along with
641 utilities is available from the FUSE homepage:
642 <http://fuse.sourceforge.net/>
644 See <file:Documentation/filesystems/fuse.txt> for more information.
645 See <file:Documentation/Changes> for needed library/utility version.
647 If you want to develop a userspace FS, or if you want to use
648 a filesystem based on FUSE, answer Y or M.
655 menu "CD-ROM/DVD Filesystems"
658 tristate "ISO 9660 CDROM file system support"
660 This is the standard file system used on CD-ROMs. It was previously
661 known as "High Sierra File System" and is called "hsfs" on other
662 Unix systems. The so-called Rock-Ridge extensions which allow for
663 long Unix filenames and symbolic links are also supported by this
664 driver. If you have a CD-ROM drive and want to do more with it than
665 just listen to audio CDs and watch its LEDs, say Y (and read
666 <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO,
667 available from <http://www.tldp.org/docs.html#howto>), thereby
668 enlarging your kernel by about 27 KB; otherwise say N.
670 To compile this file system support as a module, choose M here: the
671 module will be called isofs.
674 bool "Microsoft Joliet CDROM extensions"
675 depends on ISO9660_FS
678 Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system
679 which allows for long filenames in unicode format (unicode is the
680 new 16 bit character code, successor to ASCII, which encodes the
681 characters of almost all languages of the world; see
682 <http://www.unicode.org/> for more information). Say Y here if you
683 want to be able to read Joliet CD-ROMs under Linux.
686 bool "Transparent decompression extension"
687 depends on ISO9660_FS
690 This is a Linux-specific extension to RockRidge which lets you store
691 data in compressed form on a CD-ROM and have it transparently
692 decompressed when the CD-ROM is accessed. See
693 <http://www.kernel.org/pub/linux/utils/fs/zisofs/> for the tools
694 necessary to create such a filesystem. Say Y here if you want to be
695 able to read such compressed CD-ROMs.
698 tristate "UDF file system support"
700 This is the new file system used on some CD-ROMs and DVDs. Say Y if
701 you intend to mount DVD discs or CDRW's written in packet mode, or
702 if written to by other UDF utilities, such as DirectCD.
703 Please read <file:Documentation/filesystems/udf.txt>.
705 To compile this file system support as a module, choose M here: the
706 module will be called udf.
713 depends on (UDF_FS=m && NLS) || (UDF_FS=y && NLS=y)
719 menu "DOS/FAT/NT Filesystems"
725 If you want to use one of the FAT-based file systems (the MS-DOS and
726 VFAT (Windows 95) file systems), then you must say Y or M here
727 to include FAT support. You will then be able to mount partitions or
728 diskettes with FAT-based file systems and transparently access the
729 files on them, i.e. MSDOS files will look and behave just like all
732 This FAT support is not a file system in itself, it only provides
733 the foundation for the other file systems. You will have to say Y or
734 M to at least one of "MSDOS fs support" or "VFAT fs support" in
735 order to make use of it.
737 Another way to read and write MSDOS floppies and hard drive
738 partitions from within Linux (but not transparently) is with the
739 mtools ("man mtools") program suite. You don't need to say Y here in
742 If you need to move large files on floppies between a DOS and a
743 Linux box, say Y here, mount the floppy under Linux with an MSDOS
744 file system and use GNU tar's M option. GNU tar is a program
745 available for Unix and DOS ("man tar" or "info tar").
747 The FAT support will enlarge your kernel by about 37 KB. If unsure,
750 To compile this as a module, choose M here: the module will be called
751 fat. Note that if you compile the FAT support as a module, you
752 cannot compile any of the FAT-based file systems into the kernel
753 -- they will have to be modules as well.
756 tristate "MSDOS fs support"
759 This allows you to mount MSDOS partitions of your hard drive (unless
760 they are compressed; to access compressed MSDOS partitions under
761 Linux, you can either use the DOS emulator DOSEMU, described in the
762 DOSEMU-HOWTO, available from
763 <http://www.tldp.org/docs.html#howto>, or try dmsdosfs in
764 <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you
765 intend to use dosemu with a non-compressed MSDOS partition, say Y
766 here) and MSDOS floppies. This means that file access becomes
767 transparent, i.e. the MSDOS files look and behave just like all
770 If you have Windows 95 or Windows NT installed on your MSDOS
771 partitions, you should use the VFAT file system (say Y to "VFAT fs
772 support" below), or you will not be able to see the long filenames
773 generated by Windows 95 / Windows NT.
775 This option will enlarge your kernel by about 7 KB. If unsure,
776 answer Y. This will only work if you said Y to "DOS FAT fs support"
777 as well. To compile this as a module, choose M here: the module will
781 tristate "VFAT (Windows-95) fs support"
784 This option provides support for normal Windows file systems with
785 long filenames. That includes non-compressed FAT-based file systems
786 used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
787 programs from the mtools package.
789 The VFAT support enlarges your kernel by about 10 KB and it only
790 works if you said Y to the "DOS FAT fs support" above. Please read
791 the file <file:Documentation/filesystems/vfat.txt> for details. If
794 To compile this as a module, choose M here: the module will be called
797 config FAT_DEFAULT_CODEPAGE
798 int "Default codepage for FAT"
799 depends on MSDOS_FS || VFAT_FS
802 This option should be set to the codepage of your FAT filesystems.
803 It can be overridden with the "codepage" mount option.
804 See <file:Documentation/filesystems/vfat.txt> for more information.
806 config FAT_DEFAULT_IOCHARSET
807 string "Default iocharset for FAT"
811 Set this to the default input/output character set you'd
812 like FAT to use. It should probably match the character set
813 that most of your FAT filesystems use, and can be overridden
814 with the "iocharset" mount option for FAT filesystems.
815 Note that "utf8" is not recommended for FAT filesystems.
816 If unsure, you shouldn't set "utf8" here.
817 See <file:Documentation/filesystems/vfat.txt> for more information.
820 tristate "NTFS file system support"
823 NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003.
825 Saying Y or M here enables read support. There is partial, but
826 safe, write support available. For write support you must also
827 say Y to "NTFS write support" below.
829 There are also a number of user-space tools available, called
830 ntfsprogs. These include ntfsundelete and ntfsresize, that work
831 without NTFS support enabled in the kernel.
833 This is a rewrite from scratch of Linux NTFS support and replaced
834 the old NTFS code starting with Linux 2.5.11. A backport to
835 the Linux 2.4 kernel series is separately available as a patch
836 from the project web site.
838 For more information see <file:Documentation/filesystems/ntfs.txt>
839 and <http://linux-ntfs.sourceforge.net/>.
841 To compile this file system support as a module, choose M here: the
842 module will be called ntfs.
844 If you are not using Windows NT, 2000, XP or 2003 in addition to
845 Linux on your computer it is safe to say N.
848 bool "NTFS debugging support"
851 If you are experiencing any problems with the NTFS file system, say
852 Y here. This will result in additional consistency checks to be
853 performed by the driver as well as additional debugging messages to
854 be written to the system log. Note that debugging messages are
855 disabled by default. To enable them, supply the option debug_msgs=1
856 at the kernel command line when booting the kernel or as an option
857 to insmod when loading the ntfs module. Once the driver is active,
858 you can enable debugging messages by doing (as root):
859 echo 1 > /proc/sys/fs/ntfs-debug
860 Replacing the "1" with "0" would disable debug messages.
862 If you leave debugging messages disabled, this results in little
863 overhead, but enabling debug messages results in very significant
864 slowdown of the system.
866 When reporting bugs, please try to have available a full dump of
867 debugging messages while the misbehaviour was occurring.
870 bool "NTFS write support"
873 This enables the partial, but safe, write support in the NTFS driver.
875 The only supported operation is overwriting existing files, without
876 changing the file length. No file or directory creation, deletion or
877 renaming is possible. Note only non-resident files can be written to
878 so you may find that some very small files (<500 bytes or so) cannot
881 While we cannot guarantee that it will not damage any data, we have
882 so far not received a single report where the driver would have
883 damaged someones data so we assume it is perfectly safe to use.
885 Note: While write support is safe in this version (a rewrite from
886 scratch of the NTFS support), it should be noted that the old NTFS
887 write support, included in Linux 2.5.10 and before (since 1997),
890 This is currently useful with TopologiLinux. TopologiLinux is run
891 on top of any DOS/Microsoft Windows system without partitioning your
892 hard disk. Unlike other Linux distributions TopologiLinux does not
893 need its own partition. For more information see
894 <http://topologi-linux.sourceforge.net/>
896 It is perfectly safe to say N here.
901 menu "Pseudo filesystems"
904 bool "/proc file system support" if EMBEDDED
907 This is a virtual file system providing information about the status
908 of the system. "Virtual" means that it doesn't take up any space on
909 your hard disk: the files are created on the fly by the kernel when
910 you try to access them. Also, you cannot read the files with older
911 version of the program less: you need to use more or cat.
913 It's totally cool; for example, "cat /proc/interrupts" gives
914 information about what the different IRQs are used for at the moment
915 (there is a small number of Interrupt ReQuest lines in your computer
916 that are used by the attached devices to gain the CPU's attention --
917 often a source of trouble if two devices are mistakenly configured
918 to use the same IRQ). The program procinfo to display some
919 information about your system gathered from the /proc file system.
921 Before you can use the /proc file system, it has to be mounted,
922 meaning it has to be given a location in the directory hierarchy.
923 That location should be /proc. A command such as "mount -t proc proc
924 /proc" or the equivalent line in /etc/fstab does the job.
926 The /proc file system is explained in the file
927 <file:Documentation/filesystems/proc.txt> and on the proc(5) manpage
930 This option will enlarge your kernel by about 67 KB. Several
931 programs depend on this, so everyone should say Y here.
934 bool "/proc/kcore support" if !ARM
935 depends on PROC_FS && MMU
938 bool "/proc/vmcore support (EXPERIMENTAL)"
939 depends on PROC_FS && EXPERIMENTAL && CRASH_DUMP
942 Exports the dump image of crashed kernel in ELF format.
945 bool "Sysctl support (/proc/sys)" if EMBEDDED
950 The sysctl interface provides a means of dynamically changing
951 certain kernel parameters and variables on the fly without requiring
952 a recompile of the kernel or reboot of the system. The primary
953 interface is through /proc/sys. If you say Y here a tree of
954 modifiable sysctl entries will be generated beneath the
955 /proc/sys directory. They are explained in the files
956 in <file:Documentation/sysctl/>. Note that enabling this
957 option will enlarge the kernel by at least 8 KB.
959 As it is generally a good thing, you should say Y here unless
960 building a kernel for install/rescue disks or your system is very
964 bool "sysfs file system support" if EMBEDDED
967 The sysfs filesystem is a virtual filesystem that the kernel uses to
968 export internal kernel objects, their attributes, and their
969 relationships to one another.
971 Users can use sysfs to ascertain useful information about the running
972 kernel, such as the devices the kernel has discovered on each bus and
973 which driver each is bound to. sysfs can also be used to tune devices
974 and other kernel subsystems.
976 Some system agents rely on the information in sysfs to operate.
977 /sbin/hotplug uses device and object attributes in sysfs to assist in
978 delegating policy decisions, like persistently naming devices.
980 sysfs is currently used by the block subsystem to mount the root
981 partition. If sysfs is disabled you must specify the boot device on
982 the kernel boot command line via its major and minor numbers. For
983 example, "root=03:01" for /dev/hda1.
985 Designers of embedded systems may wish to say N here to conserve space.
988 bool "Virtual memory file system support (former shm fs)"
990 Tmpfs is a file system which keeps all files in virtual memory.
992 Everything in tmpfs is temporary in the sense that no files will be
993 created on your hard drive. The files live in memory and swap
994 space. If you unmount a tmpfs instance, everything stored therein is
997 See <file:Documentation/filesystems/tmpfs.txt> for details.
999 config TMPFS_POSIX_ACL
1000 bool "Tmpfs POSIX Access Control Lists"
1004 POSIX Access Control Lists (ACLs) support permissions for users and
1005 groups beyond the owner/group/world scheme.
1007 To learn more about Access Control Lists, visit the POSIX ACLs for
1008 Linux website <http://acl.bestbits.at/>.
1010 If you don't know what Access Control Lists are, say N.
1013 bool "HugeTLB file system support"
1014 depends on X86 || IA64 || PPC64 || SPARC64 || (SUPERH && MMU) || BROKEN
1016 hugetlbfs is a filesystem backing for HugeTLB pages, based on
1017 ramfs. For architectures that support it, say Y here and read
1018 <file:Documentation/vm/hugetlbpage.txt> for details.
1026 tristate "Userspace-driven configuration filesystem"
1029 configfs is a ram-based filesystem that provides the converse
1030 of sysfs's functionality. Where sysfs is a filesystem-based
1031 view of kernel objects, configfs is a filesystem-based manager
1032 of kernel objects, or config_items.
1034 Both sysfs and configfs can and should exist together on the
1035 same system. One is not a replacement for the other.
1039 menu "Miscellaneous filesystems"
1042 tristate "ADFS file system support (EXPERIMENTAL)"
1043 depends on BLOCK && EXPERIMENTAL
1045 The Acorn Disc Filing System is the standard file system of the
1046 RiscOS operating system which runs on Acorn's ARM-based Risc PC
1047 systems and the Acorn Archimedes range of machines. If you say Y
1048 here, Linux will be able to read from ADFS partitions on hard drives
1049 and from ADFS-formatted floppy discs. If you also want to be able to
1050 write to those devices, say Y to "ADFS write support" below.
1052 The ADFS partition should be the first partition (i.e.,
1053 /dev/[hs]d?1) on each of your drives. Please read the file
1054 <file:Documentation/filesystems/adfs.txt> for further details.
1056 To compile this code as a module, choose M here: the module will be
1062 bool "ADFS write support (DANGEROUS)"
1065 If you say Y here, you will be able to write to ADFS partitions on
1066 hard drives and ADFS-formatted floppy disks. This is experimental
1067 codes, so if you're unsure, say N.
1070 tristate "Amiga FFS file system support (EXPERIMENTAL)"
1071 depends on BLOCK && EXPERIMENTAL
1073 The Fast File System (FFS) is the common file system used on hard
1074 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
1075 if you want to be able to read and write files from and to an Amiga
1076 FFS partition on your hard drive. Amiga floppies however cannot be
1077 read with this driver due to an incompatibility of the floppy
1078 controller used in an Amiga and the standard floppy controller in
1079 PCs and workstations. Read <file:Documentation/filesystems/affs.txt>
1080 and <file:fs/affs/Changes>.
1082 With this driver you can also mount disk files used by Bernd
1083 Schmidt's Un*X Amiga Emulator
1084 (<http://www.freiburg.linux.de/~uae/>).
1085 If you want to do this, you will also need to say Y or M to "Loop
1086 device support", above.
1088 To compile this file system support as a module, choose M here: the
1089 module will be called affs. If unsure, say N.
1092 tristate "eCrypt filesystem layer support (EXPERIMENTAL)"
1093 depends on EXPERIMENTAL && KEYS && CRYPTO && NET
1095 Encrypted filesystem that operates on the VFS layer. See
1096 <file:Documentation/filesystems/ecryptfs.txt> to learn more about
1097 eCryptfs. Userspace components are required and can be
1098 obtained from <http://ecryptfs.sf.net>.
1100 To compile this file system support as a module, choose M here: the
1101 module will be called ecryptfs.
1104 tristate "Apple Macintosh file system support (EXPERIMENTAL)"
1105 depends on BLOCK && EXPERIMENTAL
1108 If you say Y here, you will be able to mount Macintosh-formatted
1109 floppy disks and hard drive partitions with full read-write access.
1110 Please read <file:Documentation/filesystems/hfs.txt> to learn about
1111 the available mount options.
1113 To compile this file system support as a module, choose M here: the
1114 module will be called hfs.
1117 tristate "Apple Extended HFS file system support"
1122 If you say Y here, you will be able to mount extended format
1123 Macintosh-formatted hard drive partitions with full read-write access.
1125 This file system is often called HFS+ and was introduced with
1126 MacOS 8. It includes all Mac specific filesystem data such as
1127 data forks and creator codes, but it also has several UNIX
1128 style features such as file ownership and permissions.
1131 tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)"
1132 depends on BLOCK && EXPERIMENTAL
1135 The BeOS File System (BeFS) is the native file system of Be, Inc's
1136 BeOS. Notable features include support for arbitrary attributes
1137 on files and directories, and database-like indices on selected
1138 attributes. (Also note that this driver doesn't make those features
1139 available at this time). It is a 64 bit filesystem, so it supports
1140 extremely large volumes and files.
1142 If you use this filesystem, you should also say Y to at least one
1143 of the NLS (native language support) options below.
1145 If you don't know what this is about, say N.
1147 To compile this as a module, choose M here: the module will be
1154 If you say Y here, you can use the 'debug' mount option to enable
1155 debugging output from the driver.
1158 tristate "BFS file system support (EXPERIMENTAL)"
1159 depends on BLOCK && EXPERIMENTAL
1161 Boot File System (BFS) is a file system used under SCO UnixWare to
1162 allow the bootloader access to the kernel image and other important
1163 files during the boot process. It is usually mounted under /stand
1164 and corresponds to the slice marked as "STAND" in the UnixWare
1165 partition. You should say Y if you want to read or write the files
1166 on your /stand slice from within Linux. You then also need to say Y
1167 to "UnixWare slices support", below. More information about the BFS
1168 file system is contained in the file
1169 <file:Documentation/filesystems/bfs.txt>.
1171 If you don't know what this is about, say N.
1173 To compile this as a module, choose M here: the module will be called
1174 bfs. Note that the file system of your root partition (the one
1175 containing the directory /) cannot be compiled as a module.
1180 tristate "EFS file system support (read only) (EXPERIMENTAL)"
1181 depends on BLOCK && EXPERIMENTAL
1183 EFS is an older file system used for non-ISO9660 CD-ROMs and hard
1184 disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
1185 uses the XFS file system for hard disk partitions however).
1187 This implementation only offers read-only access. If you don't know
1188 what all this is about, it's safe to say N. For more information
1189 about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
1191 To compile the EFS file system support as a module, choose M here: the
1192 module will be called efs.
1195 tristate "Journalling Flash File System v2 (JFFS2) support"
1199 JFFS2 is the second generation of the Journalling Flash File System
1200 for use on diskless embedded devices. It provides improved wear
1201 levelling, compression and support for hard links. You cannot use
1202 this on normal block devices, only on 'MTD' devices.
1204 Further information on the design and implementation of JFFS2 is
1205 available at <http://sources.redhat.com/jffs2/>.
1207 config JFFS2_FS_DEBUG
1208 int "JFFS2 debugging verbosity (0 = quiet, 2 = noisy)"
1212 This controls the amount of debugging messages produced by the JFFS2
1213 code. Set it to zero for use in production systems. For evaluation,
1214 testing and debugging, it's advisable to set it to one. This will
1215 enable a few assertions and will print debugging messages at the
1216 KERN_DEBUG loglevel, where they won't normally be visible. Level 2
1217 is unlikely to be useful - it enables extra debugging in certain
1218 areas which at one point needed debugging, but when the bugs were
1219 located and fixed, the detailed messages were relegated to level 2.
1221 If reporting bugs, please try to have available a full dump of the
1222 messages at debug level 1 while the misbehaviour was occurring.
1224 config JFFS2_FS_WRITEBUFFER
1225 bool "JFFS2 write-buffering support"
1229 This enables the write-buffering support in JFFS2.
1231 This functionality is required to support JFFS2 on the following
1232 types of flash devices:
1234 - NOR flash with transparent ECC
1237 config JFFS2_FS_WBUF_VERIFY
1238 bool "Verify JFFS2 write-buffer reads"
1239 depends on JFFS2_FS_WRITEBUFFER
1242 This causes JFFS2 to read back every page written through the
1243 write-buffer, and check for errors.
1245 config JFFS2_SUMMARY
1246 bool "JFFS2 summary support (EXPERIMENTAL)"
1247 depends on JFFS2_FS && EXPERIMENTAL
1250 This feature makes it possible to use summary information
1251 for faster filesystem mount.
1253 The summary information can be inserted into a filesystem image
1254 by the utility 'sumtool'.
1258 config JFFS2_FS_XATTR
1259 bool "JFFS2 XATTR support (EXPERIMENTAL)"
1260 depends on JFFS2_FS && EXPERIMENTAL
1263 Extended attributes are name:value pairs associated with inodes by
1264 the kernel or by users (see the attr(5) manual page, or visit
1265 <http://acl.bestbits.at/> for details).
1269 config JFFS2_FS_POSIX_ACL
1270 bool "JFFS2 POSIX Access Control Lists"
1271 depends on JFFS2_FS_XATTR
1275 Posix Access Control Lists (ACLs) support permissions for users and
1276 groups beyond the owner/group/world scheme.
1278 To learn more about Access Control Lists, visit the Posix ACLs for
1279 Linux website <http://acl.bestbits.at/>.
1281 If you don't know what Access Control Lists are, say N
1283 config JFFS2_FS_SECURITY
1284 bool "JFFS2 Security Labels"
1285 depends on JFFS2_FS_XATTR
1288 Security labels support alternative access control models
1289 implemented by security modules like SELinux. This option
1290 enables an extended attribute handler for file security
1291 labels in the jffs2 filesystem.
1293 If you are not using a security module that requires using
1294 extended attributes for file security labels, say N.
1296 config JFFS2_COMPRESSION_OPTIONS
1297 bool "Advanced compression options for JFFS2"
1301 Enabling this option allows you to explicitly choose which
1302 compression modules, if any, are enabled in JFFS2. Removing
1303 compressors can mean you cannot read existing file systems,
1304 and enabling experimental compressors can mean that you
1305 write a file system which cannot be read by a standard kernel.
1307 If unsure, you should _definitely_ say 'N'.
1310 bool "JFFS2 ZLIB compression support" if JFFS2_COMPRESSION_OPTIONS
1316 Zlib is designed to be a free, general-purpose, legally unencumbered,
1317 lossless data-compression library for use on virtually any computer
1318 hardware and operating system. See <http://www.gzip.org/zlib/> for
1319 further information.
1324 bool "JFFS2 LZO compression support" if JFFS2_COMPRESSION_OPTIONS
1326 select LZO_DECOMPRESS
1330 minilzo-based compression. Generally works better than Zlib.
1332 This feature was added in July, 2007. Say 'N' if you need
1333 compatibility with older bootloaders or kernels.
1336 bool "JFFS2 RTIME compression support" if JFFS2_COMPRESSION_OPTIONS
1340 Rtime does manage to recompress already-compressed data. Say 'Y' if unsure.
1343 bool "JFFS2 RUBIN compression support" if JFFS2_COMPRESSION_OPTIONS
1347 RUBINMIPS and DYNRUBIN compressors. Say 'N' if unsure.
1350 prompt "JFFS2 default compression mode" if JFFS2_COMPRESSION_OPTIONS
1351 default JFFS2_CMODE_PRIORITY
1354 You can set here the default compression mode of JFFS2 from
1355 the available compression modes. Don't touch if unsure.
1357 config JFFS2_CMODE_NONE
1358 bool "no compression"
1360 Uses no compression.
1362 config JFFS2_CMODE_PRIORITY
1365 Tries the compressors in a predefined order and chooses the first
1368 config JFFS2_CMODE_SIZE
1369 bool "size (EXPERIMENTAL)"
1371 Tries all compressors and chooses the one which has the smallest
1374 config JFFS2_CMODE_FAVOURLZO
1377 Tries all compressors and chooses the one which has the smallest
1378 result but gives some preference to LZO (which has faster
1379 decompression) at the expense of size.
1384 tristate "Compressed ROM file system support (cramfs)"
1388 Saying Y here includes support for CramFs (Compressed ROM File
1389 System). CramFs is designed to be a simple, small, and compressed
1390 file system for ROM based embedded systems. CramFs is read-only,
1391 limited to 256MB file systems (with 16MB files), and doesn't support
1392 16/32 bits uid/gid, hard links and timestamps.
1394 See <file:Documentation/filesystems/cramfs.txt> and
1395 <file:fs/cramfs/README> for further information.
1397 To compile this as a module, choose M here: the module will be called
1398 cramfs. Note that the root file system (the one containing the
1399 directory /) cannot be compiled as a module.
1404 tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
1407 FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
1408 file system format. VERITAS VxFS(TM) is the standard file system
1409 of SCO UnixWare (and possibly others) and optionally available
1410 for Sunsoft Solaris, HP-UX and many other operating systems.
1411 Currently only readonly access is supported.
1413 NOTE: the file system type as used by mount(1), mount(2) and
1414 fstab(5) is 'vxfs' as it describes the file system format, not
1417 To compile this as a module, choose M here: the module will be
1418 called freevxfs. If unsure, say N.
1422 tristate "OS/2 HPFS file system support"
1425 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
1426 is the file system used for organizing files on OS/2 hard disk
1427 partitions. Say Y if you want to be able to read files from and
1428 write files to an OS/2 HPFS partition on your hard drive. OS/2
1429 floppies however are in regular MSDOS format, so you don't need this
1430 option in order to be able to read them. Read
1431 <file:Documentation/filesystems/hpfs.txt>.
1433 To compile this file system support as a module, choose M here: the
1434 module will be called hpfs. If unsure, say N.
1439 tristate "QNX4 file system support (read only)"
1442 This is the file system used by the real-time operating systems
1443 QNX 4 and QNX 6 (the latter is also called QNX RTP).
1444 Further information is available at <http://www.qnx.com/>.
1445 Say Y if you intend to mount QNX hard disks or floppies.
1446 Unless you say Y to "QNX4FS read-write support" below, you will
1447 only be able to read these file systems.
1449 To compile this file system support as a module, choose M here: the
1450 module will be called qnx4.
1452 If you don't know whether you need it, then you don't need it:
1456 bool "QNX4FS write support (DANGEROUS)"
1457 depends on QNX4FS_FS && EXPERIMENTAL && BROKEN
1459 Say Y if you want to test write support for QNX4 file systems.
1461 It's currently broken, so for now:
1467 tristate "System V/Xenix/V7/Coherent file system support"
1470 SCO, Xenix and Coherent are commercial Unix systems for Intel
1471 machines, and Version 7 was used on the DEC PDP-11. Saying Y
1472 here would allow you to read from their floppies and hard disk
1475 If you have floppies or hard disk partitions like that, it is likely
1476 that they contain binaries from those other Unix systems; in order
1477 to run these binaries, you will want to install linux-abi which is
1478 a set of kernel modules that lets you run SCO, Xenix, Wyse,
1479 UnixWare, Dell Unix and System V programs under Linux. It is
1480 available via FTP (user: ftp) from
1481 <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
1482 NOTE: that will work only for binaries from Intel-based systems;
1483 PDP ones will have to wait until somebody ports Linux to -11 ;-)
1485 If you only intend to mount files from some other Unix over the
1486 network using NFS, you don't need the System V file system support
1487 (but you need NFS file system support obviously).
1489 Note that this option is generally not needed for floppies, since a
1490 good portable way to transport files and directories between unixes
1491 (and even other operating systems) is given by the tar program ("man
1492 tar" or preferably "info tar"). Note also that this option has
1493 nothing whatsoever to do with the option "System V IPC". Read about
1494 the System V file system in
1495 <file:Documentation/filesystems/sysv-fs.txt>.
1496 Saying Y here will enlarge your kernel by about 27 KB.
1498 To compile this as a module, choose M here: the module will be called
1501 If you haven't heard about all of this before, it's safe to say N.
1506 tristate "UFS file system support (read only)"
1509 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
1510 OpenBSD and NeXTstep) use a file system called UFS. Some System V
1511 Unixes can create and mount hard disk partitions and diskettes using
1512 this file system as well. Saying Y here will allow you to read from
1513 these partitions; if you also want to write to them, say Y to the
1514 experimental "UFS file system write support", below. Please read the
1515 file <file:Documentation/filesystems/ufs.txt> for more information.
1517 The recently released UFS2 variant (used in FreeBSD 5.x) is
1518 READ-ONLY supported.
1520 If you only intend to mount files from some other Unix over the
1521 network using NFS, you don't need the UFS file system support (but
1522 you need NFS file system support obviously).
1524 Note that this option is generally not needed for floppies, since a
1525 good portable way to transport files and directories between unixes
1526 (and even other operating systems) is given by the tar program ("man
1527 tar" or preferably "info tar").
1529 When accessing NeXTstep files, you may need to convert them from the
1530 NeXT character set to the Latin1 character set; use the program
1531 recode ("info recode") for this purpose.
1533 To compile the UFS file system support as a module, choose M here: the
1534 module will be called ufs.
1536 If you haven't heard about all of this before, it's safe to say N.
1539 bool "UFS file system write support (DANGEROUS)"
1540 depends on UFS_FS && EXPERIMENTAL
1542 Say Y here if you want to try writing to UFS partitions. This is
1543 experimental, so you should back up your UFS partitions beforehand.
1546 bool "UFS debugging"
1549 If you are experiencing any problems with the UFS filesystem, say
1550 Y here. This will result in _many_ additional debugging messages to be
1551 written to the system log.
1555 menuconfig NETWORK_FILESYSTEMS
1556 bool "Network File Systems"
1560 Say Y here to get to see options for network filesystems and
1561 filesystem-related networking code, such as NFS daemon and
1562 RPCSEC security modules.
1563 This option alone does not add any kernel code.
1565 If you say N, all options in this submenu will be skipped and
1566 disabled; if unsure, say Y here.
1568 if NETWORK_FILESYSTEMS
1571 tristate "NFS file system support"
1575 select NFS_ACL_SUPPORT if NFS_V3_ACL
1577 If you are connected to some other (usually local) Unix computer
1578 (using SLIP, PLIP, PPP or Ethernet) and want to mount files residing
1579 on that computer (the NFS server) using the Network File Sharing
1580 protocol, say Y. "Mounting files" means that the client can access
1581 the files with usual UNIX commands as if they were sitting on the
1582 client's hard disk. For this to work, the server must run the
1583 programs nfsd and mountd (but does not need to have NFS file system
1584 support enabled in its kernel). NFS is explained in the Network
1585 Administrator's Guide, available from
1586 <http://www.tldp.org/docs.html#guide>, on its man page: "man
1587 nfs", and in the NFS-HOWTO.
1589 A superior but less widely used alternative to NFS is provided by
1590 the Coda file system; see "Coda file system support" below.
1592 If you say Y here, you should have said Y to TCP/IP networking also.
1593 This option would enlarge your kernel by about 27 KB.
1595 To compile this file system support as a module, choose M here: the
1596 module will be called nfs.
1598 If you are configuring a diskless machine which will mount its root
1599 file system over NFS at boot time, say Y here and to "Kernel
1600 level IP autoconfiguration" above and to "Root file system on NFS"
1601 below. You cannot compile this driver as a module in this case.
1602 There are two packages designed for booting diskless machines over
1603 the net: netboot, available from
1604 <http://ftp1.sourceforge.net/netboot/>, and Etherboot,
1605 available from <http://ftp1.sourceforge.net/etherboot/>.
1607 If you don't know what all this is about, say N.
1610 bool "Provide NFSv3 client support"
1613 Say Y here if you want your NFS client to be able to speak version
1614 3 of the NFS protocol.
1619 bool "Provide client support for the NFSv3 ACL protocol extension"
1622 Implement the NFSv3 ACL protocol extension for manipulating POSIX
1623 Access Control Lists. The server should also be compiled with
1624 the NFSv3 ACL protocol extension; see the CONFIG_NFSD_V3_ACL option.
1629 bool "Provide NFSv4 client support (EXPERIMENTAL)"
1630 depends on NFS_FS && EXPERIMENTAL
1631 select RPCSEC_GSS_KRB5
1633 Say Y here if you want your NFS client to be able to speak the newer
1634 version 4 of the NFS protocol.
1636 Note: Requires auxiliary userspace daemons which may be found on
1637 http://www.citi.umich.edu/projects/nfsv4/
1642 bool "Allow direct I/O on NFS files"
1645 This option enables applications to perform uncached I/O on files
1646 in NFS file systems using the O_DIRECT open() flag. When O_DIRECT
1647 is set for a file, its data is not cached in the system's page
1648 cache. Data is moved to and from user-level application buffers
1649 directly. Unlike local disk-based file systems, NFS O_DIRECT has
1650 no alignment restrictions.
1652 Unless your program is designed to use O_DIRECT properly, you are
1653 much better off allowing the NFS client to manage data caching for
1654 you. Misusing O_DIRECT can cause poor server performance or network
1655 storms. This kernel build option defaults OFF to avoid exposing
1656 system administrators unwittingly to a potentially hazardous
1659 For more details on NFS O_DIRECT, see fs/nfs/direct.c.
1661 If unsure, say N. This reduces the size of the NFS client, and
1662 causes open() to return EINVAL if a file residing in NFS is
1663 opened with the O_DIRECT flag.
1666 tristate "NFS server support"
1671 select NFSD_V2_ACL if NFSD_V3_ACL
1672 select NFS_ACL_SUPPORT if NFSD_V2_ACL
1673 select NFSD_TCP if NFSD_V4
1674 select CRYPTO_MD5 if NFSD_V4
1675 select CRYPTO if NFSD_V4
1676 select FS_POSIX_ACL if NFSD_V4
1677 select PROC_FS if NFSD_V4
1678 select PROC_FS if SUNRPC_GSS
1680 If you want your Linux box to act as an NFS *server*, so that other
1681 computers on your local network which support NFS can access certain
1682 directories on your box transparently, you have two options: you can
1683 use the self-contained user space program nfsd, in which case you
1684 should say N here, or you can say Y and use the kernel based NFS
1685 server. The advantage of the kernel based solution is that it is
1688 In either case, you will need support software; the respective
1689 locations are given in the file <file:Documentation/Changes> in the
1692 If you say Y here, you will get support for version 2 of the NFS
1693 protocol (NFSv2). If you also want NFSv3, say Y to the next question
1696 Please read the NFS-HOWTO, available from
1697 <http://www.tldp.org/docs.html#howto>.
1699 To compile the NFS server support as a module, choose M here: the
1700 module will be called nfsd. If unsure, say N.
1707 bool "Provide NFSv3 server support"
1710 If you would like to include the NFSv3 server as well as the NFSv2
1711 server, say Y here. If unsure, say Y.
1714 bool "Provide server support for the NFSv3 ACL protocol extension"
1717 Implement the NFSv3 ACL protocol extension for manipulating POSIX
1718 Access Control Lists on exported file systems. NFS clients should
1719 be compiled with the NFSv3 ACL protocol extension; see the
1720 CONFIG_NFS_V3_ACL option. If unsure, say N.
1723 bool "Provide NFSv4 server support (EXPERIMENTAL)"
1724 depends on NFSD && NFSD_V3 && EXPERIMENTAL
1725 select RPCSEC_GSS_KRB5
1727 If you would like to include the NFSv4 server as well as the NFSv2
1728 and NFSv3 servers, say Y here. This feature is experimental, and
1729 should only be used if you are interested in helping to test NFSv4.
1733 bool "Provide NFS server over TCP support"
1737 If you want your NFS server to support TCP connections, say Y here.
1738 TCP connections usually perform better than the default UDP when
1739 the network is lossy or congested. If unsure, say Y.
1742 bool "Root file system on NFS"
1743 depends on NFS_FS=y && IP_PNP
1745 If you want your Linux box to mount its whole root file system (the
1746 one containing the directory /) from some other computer over the
1747 net via NFS (presumably because your box doesn't have a hard disk),
1748 say Y. Read <file:Documentation/nfsroot.txt> for details. It is
1749 likely that in this case, you also want to say Y to "Kernel level IP
1750 autoconfiguration" so that your box can discover its network address
1753 Most people say N here.
1760 depends on NFSD_V3 || NFS_V3
1766 config NFS_ACL_SUPPORT
1772 depends on NFSD || NFS_FS
1781 config SUNRPC_XPRT_RDMA
1782 tristate "RDMA transport for sunrpc (EXPERIMENTAL)"
1783 depends on SUNRPC && INFINIBAND && EXPERIMENTAL
1786 Adds a client RPC transport for supporting kernel NFS over RDMA
1787 mounts, including Infiniband and iWARP. Experimental.
1789 config SUNRPC_BIND34
1790 bool "Support for rpcbind versions 3 & 4 (EXPERIMENTAL)"
1791 depends on SUNRPC && EXPERIMENTAL
1793 Provides kernel support for querying rpcbind servers via versions 3
1794 and 4 of the rpcbind protocol. The kernel automatically falls back
1795 to version 2 if a remote rpcbind service does not support versions
1798 If unsure, say N to get traditional behavior (version 2 rpcbind
1801 config RPCSEC_GSS_KRB5
1802 tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
1803 depends on SUNRPC && EXPERIMENTAL
1810 Provides for secure RPC calls by means of a gss-api
1811 mechanism based on Kerberos V5. This is required for
1814 Note: Requires an auxiliary userspace daemon which may be found on
1815 http://www.citi.umich.edu/projects/nfsv4/
1819 config RPCSEC_GSS_SPKM3
1820 tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
1821 depends on SUNRPC && EXPERIMENTAL
1829 Provides for secure RPC calls by means of a gss-api
1830 mechanism based on the SPKM3 public-key mechanism.
1832 Note: Requires an auxiliary userspace daemon which may be found on
1833 http://www.citi.umich.edu/projects/nfsv4/
1838 tristate "SMB file system support (to mount Windows shares etc.)"
1842 SMB (Server Message Block) is the protocol Windows for Workgroups
1843 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
1844 files and printers over local networks. Saying Y here allows you to
1845 mount their file systems (often called "shares" in this context) and
1846 access them just like any other Unix directory. Currently, this
1847 works only if the Windows machines use TCP/IP as the underlying
1848 transport protocol, and not NetBEUI. For details, read
1849 <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
1850 available from <http://www.tldp.org/docs.html#howto>.
1852 Note: if you just want your box to act as an SMB *server* and make
1853 files and printing services available to Windows clients (which need
1854 to have a TCP/IP stack), you don't need to say Y here; you can use
1855 the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
1858 General information about how to connect Linux, Windows machines and
1859 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1861 To compile the SMB support as a module, choose M here: the module will
1862 be called smbfs. Most people say N, however.
1864 config SMB_NLS_DEFAULT
1865 bool "Use a default NLS"
1868 Enabling this will make smbfs use nls translations by default. You
1869 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
1870 settings and you need to give the default nls for the SMB server as
1871 CONFIG_SMB_NLS_REMOTE.
1873 The nls settings can be changed at mount time, if your smbmount
1874 supports that, using the codepage and iocharset parameters.
1876 smbmount from samba 2.2.0 or later supports this.
1878 config SMB_NLS_REMOTE
1879 string "Default Remote NLS Option"
1880 depends on SMB_NLS_DEFAULT
1883 This setting allows you to specify a default value for which
1884 codepage the server uses. If this field is left blank no
1885 translations will be done by default. The local codepage/charset
1886 default to CONFIG_NLS_DEFAULT.
1888 The nls settings can be changed at mount time, if your smbmount
1889 supports that, using the codepage and iocharset parameters.
1891 smbmount from samba 2.2.0 or later supports this.
1894 tristate "CIFS support (advanced network filesystem for Samba, Window and other CIFS compliant servers)"
1898 This is the client VFS module for the Common Internet File System
1899 (CIFS) protocol which is the successor to the Server Message Block
1900 (SMB) protocol, the native file sharing mechanism for most early
1901 PC operating systems. The CIFS protocol is fully supported by
1902 file servers such as Windows 2000 (including Windows 2003, NT 4
1903 and Windows XP) as well by Samba (which provides excellent CIFS
1904 server support for Linux and many other operating systems). Limited
1905 support for OS/2 and Windows ME and similar servers is provided as
1908 The cifs module provides an advanced network file system
1909 client for mounting to CIFS compliant servers. It includes
1910 support for DFS (hierarchical name space), secure per-user
1911 session establishment via Kerberos or NTLM or NTLMv2,
1912 safe distributed caching (oplock), optional packet
1913 signing, Unicode and other internationalization improvements.
1914 If you need to mount to Samba or Windows from this machine, say Y.
1917 bool "CIFS statistics"
1920 Enabling this option will cause statistics for each server share
1921 mounted by the cifs client to be displayed in /proc/fs/cifs/Stats
1924 bool "Extended statistics"
1925 depends on CIFS_STATS
1927 Enabling this option will allow more detailed statistics on SMB
1928 request timing to be displayed in /proc/fs/cifs/DebugData and also
1929 allow optional logging of slow responses to dmesg (depending on the
1930 value of /proc/fs/cifs/cifsFYI, see fs/cifs/README for more details).
1931 These additional statistics may have a minor effect on performance
1932 and memory utilization.
1934 Unless you are a developer or are doing network performance analysis
1937 config CIFS_WEAK_PW_HASH
1938 bool "Support legacy servers which use weaker LANMAN security"
1941 Modern CIFS servers including Samba and most Windows versions
1942 (since 1997) support stronger NTLM (and even NTLMv2 and Kerberos)
1943 security mechanisms. These hash the password more securely
1944 than the mechanisms used in the older LANMAN version of the
1945 SMB protocol but LANMAN based authentication is needed to
1946 establish sessions with some old SMB servers.
1948 Enabling this option allows the cifs module to mount to older
1949 LANMAN based servers such as OS/2 and Windows 95, but such
1950 mounts may be less secure than mounts using NTLM or more recent
1951 security mechanisms if you are on a public network. Unless you
1952 have a need to access old SMB servers (and are on a private
1953 network) you probably want to say N. Even if this support
1954 is enabled in the kernel build, LANMAN authentication will not be
1955 used automatically. At runtime LANMAN mounts are disabled but
1956 can be set to required (or optional) either in
1957 /proc/fs/cifs (see fs/cifs/README for more detail) or via an
1958 option on the mount command. This support is disabled by
1959 default in order to reduce the possibility of a downgrade
1965 bool "CIFS extended attributes"
1968 Extended attributes are name:value pairs associated with inodes by
1969 the kernel or by users (see the attr(5) manual page, or visit
1970 <http://acl.bestbits.at/> for details). CIFS maps the name of
1971 extended attributes beginning with the user namespace prefix
1972 to SMB/CIFS EAs. EAs are stored on Windows servers without the
1973 user namespace prefix, but their names are seen by Linux cifs clients
1974 prefaced by the user namespace prefix. The system namespace
1975 (used by some filesystems to store ACLs) is not supported at
1981 bool "CIFS POSIX Extensions"
1982 depends on CIFS_XATTR
1984 Enabling this option will cause the cifs client to attempt to
1985 negotiate a newer dialect with servers, such as Samba 3.0.5
1986 or later, that optionally can handle more POSIX like (rather
1987 than Windows like) file behavior. It also enables
1988 support for POSIX ACLs (getfacl and setfacl) to servers
1989 (such as Samba 3.10 and later) which can negotiate
1990 CIFS POSIX ACL support. If unsure, say N.
1993 bool "Enable additional CIFS debugging routines"
1996 Enabling this option adds a few more debugging routines
1997 to the cifs code which slightly increases the size of
1998 the cifs module and can cause additional logging of debug
1999 messages in some error paths, slowing performance. This
2000 option can be turned off unless you are debugging
2001 cifs problems. If unsure, say N.
2003 config CIFS_EXPERIMENTAL
2004 bool "CIFS Experimental Features (EXPERIMENTAL)"
2005 depends on CIFS && EXPERIMENTAL
2007 Enables cifs features under testing. These features are
2008 experimental and currently include DFS support and directory
2009 change notification ie fcntl(F_DNOTIFY), as well as the upcall
2010 mechanism which will be used for Kerberos session negotiation
2011 and uid remapping. Some of these features also may depend on
2012 setting a value of 1 to the pseudo-file /proc/fs/cifs/Experimental
2013 (which is disabled by default). See the file fs/cifs/README
2014 for more details. If unsure, say N.
2017 bool "Kerberos/SPNEGO advanced session setup (EXPERIMENTAL)"
2018 depends on CIFS_EXPERIMENTAL
2021 Enables an upcall mechanism for CIFS which accesses
2022 userspace helper utilities to provide SPNEGO packaged (RFC 4178)
2023 Kerberos tickets which are needed to mount to certain secure servers
2024 (for which more secure Kerberos authentication is required). If
2027 config CIFS_DFS_UPCALL
2028 bool "DFS feature support (EXPERIMENTAL)"
2029 depends on CIFS_EXPERIMENTAL
2032 Enables an upcall mechanism for CIFS which contacts userspace
2033 helper utilities to provide server name resolution (host names to
2034 IP addresses) which is needed for implicit mounts of DFS junction
2035 points. If unsure, say N.
2038 tristate "NCP file system support (to mount NetWare volumes)"
2039 depends on IPX!=n || INET
2041 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
2042 used by Novell NetWare clients to talk to file servers. It is to
2043 IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
2044 to mount NetWare file server volumes and to access them just like
2045 any other Unix directory. For details, please read the file
2046 <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
2047 the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
2049 You do not have to say Y here if you want your Linux box to act as a
2050 file *server* for Novell NetWare clients.
2052 General information about how to connect Linux, Windows machines and
2053 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
2055 To compile this as a module, choose M here: the module will be called
2056 ncpfs. Say N unless you are connected to a Novell network.
2058 source "fs/ncpfs/Kconfig"
2061 tristate "Coda file system support (advanced network fs)"
2064 Coda is an advanced network file system, similar to NFS in that it
2065 enables you to mount file systems of a remote server and access them
2066 with regular Unix commands as if they were sitting on your hard
2067 disk. Coda has several advantages over NFS: support for
2068 disconnected operation (e.g. for laptops), read/write server
2069 replication, security model for authentication and encryption,
2070 persistent client caches and write back caching.
2072 If you say Y here, your Linux box will be able to act as a Coda
2073 *client*. You will need user level code as well, both for the
2074 client and server. Servers are currently user level, i.e. they need
2075 no kernel support. Please read
2076 <file:Documentation/filesystems/coda.txt> and check out the Coda
2077 home page <http://www.coda.cs.cmu.edu/>.
2079 To compile the coda client support as a module, choose M here: the
2080 module will be called coda.
2082 config CODA_FS_OLD_API
2083 bool "Use 96-bit Coda file identifiers"
2086 A new kernel-userspace API had to be introduced for Coda v6.0
2087 to support larger 128-bit file identifiers as needed by the
2088 new realms implementation.
2090 However this new API is not backward compatible with older
2091 clients. If you really need to run the old Coda userspace
2092 cache manager then say Y.
2094 For most cases you probably want to say N.
2097 tristate "Andrew File System support (AFS) (EXPERIMENTAL)"
2098 depends on INET && EXPERIMENTAL
2101 If you say Y here, you will get an experimental Andrew File System
2102 driver. It currently only supports unsecured read-only AFS access.
2104 See <file:Documentation/filesystems/afs.txt> for more information.
2109 bool "AFS dynamic debugging"
2112 Say Y here to make runtime controllable debugging messages appear.
2114 See <file:Documentation/filesystems/afs.txt> for more information.
2119 tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
2120 depends on INET && NET_9P && EXPERIMENTAL
2122 If you say Y here, you will get experimental support for
2123 Plan 9 resource sharing via the 9P2000 protocol.
2125 See <http://v9fs.sf.net> for more information.
2129 endif # NETWORK_FILESYSTEMS
2132 menu "Partition Types"
2134 source "fs/partitions/Kconfig"
2139 source "fs/nls/Kconfig"
2140 source "fs/dlm/Kconfig"