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
144 Ext4dev is a predecessor filesystem of the next generation
145 extended fs ext4, based on ext3 filesystem code. It will be
146 renamed ext4 fs later, once ext4dev is mature and stabilized.
148 Unlike the change from ext2 filesystem to ext3 filesystem,
149 the on-disk format of ext4dev is not the same as ext3 any more:
150 it is based on extent maps and it supports 48-bit physical block
151 numbers. These combined on-disk format changes will allow
152 ext4dev/ext4 to handle more than 16 TB filesystem volumes --
153 a hard limit that ext3 cannot overcome without changing the
156 Other than extent maps and 48-bit block numbers, ext4dev also is
157 likely to have other new features such as persistent preallocation,
158 high resolution time stamps, and larger file support etc. These
159 features will be added to ext4dev gradually.
161 To compile this file system support as a module, choose M here. The
162 module will be called ext4dev.
166 config EXT4DEV_FS_XATTR
167 bool "Ext4dev extended attributes"
168 depends on EXT4DEV_FS
171 Extended attributes are name:value pairs associated with inodes by
172 the kernel or by users (see the attr(5) manual page, or visit
173 <http://acl.bestbits.at/> for details).
177 You need this for POSIX ACL support on ext4dev/ext4.
179 config EXT4DEV_FS_POSIX_ACL
180 bool "Ext4dev POSIX Access Control Lists"
181 depends on EXT4DEV_FS_XATTR
184 POSIX Access Control Lists (ACLs) support permissions for users and
185 groups beyond the owner/group/world scheme.
187 To learn more about Access Control Lists, visit the POSIX ACLs for
188 Linux website <http://acl.bestbits.at/>.
190 If you don't know what Access Control Lists are, say N
192 config EXT4DEV_FS_SECURITY
193 bool "Ext4dev Security Labels"
194 depends on EXT4DEV_FS_XATTR
196 Security labels support alternative access control models
197 implemented by security modules like SELinux. This option
198 enables an extended attribute handler for file security
199 labels in the ext4dev/ext4 filesystem.
201 If you are not using a security module that requires using
202 extended attributes for file security labels, say N.
207 This is a generic journalling layer for block devices. It is
208 currently used by the ext3 and OCFS2 file systems, but it could
209 also be used to add journal support to other file systems or block
210 devices such as RAID or LVM.
212 If you are using the ext3 or OCFS2 file systems, you need to
213 say Y here. If you are not using ext3 OCFS2 then you will probably
216 To compile this device as a module, choose M here: the module will be
217 called jbd. If you are compiling ext3 or OCFS2 into the kernel,
218 you cannot compile this code as a module.
221 bool "JBD (ext3) debugging support"
224 If you are using the ext3 journaled file system (or potentially any
225 other file system/device using JBD), this option allows you to
226 enable debugging output while the system is running, in order to
227 help track down any problems you are having. By default the
228 debugging output will be turned off.
230 If you select Y here, then you will be able to turn on debugging
231 with "echo N > /proc/sys/fs/jbd-debug", where N is a number between
232 1 and 5, the higher the number, the more debugging output is
233 generated. To turn debugging off again, do
234 "echo 0 > /proc/sys/fs/jbd-debug".
239 This is a generic journaling layer for block devices that support
240 both 32-bit and 64-bit block numbers. It is currently used by
241 the ext4dev/ext4 filesystem, but it could also be used to add
242 journal support to other file systems or block devices such
245 If you are using ext4dev/ext4, you need to say Y here. If you are not
246 using ext4dev/ext4 then you will probably want to say N.
248 To compile this device as a module, choose M here. The module will be
249 called jbd2. If you are compiling ext4dev/ext4 into the kernel,
250 you cannot compile this code as a module.
253 bool "JBD2 (ext4dev/ext4) debugging support"
254 depends on JBD2 && DEBUG_FS
256 If you are using the ext4dev/ext4 journaled file system (or
257 potentially any other filesystem/device using JBD2), this option
258 allows you to enable debugging output while the system is running,
259 in order to help track down any problems you are having.
260 By default, the debugging output will be turned off.
262 If you select Y here, then you will be able to turn on debugging
263 with "echo N > /sys/kernel/debug/jbd2/jbd2-debug", where N is a
264 number between 1 and 5. The higher the number, the more debugging
265 output is generated. To turn debugging off again, do
266 "echo 0 > /sys/kernel/debug/jbd2/jbd2-debug".
269 # Meta block cache for Extended Attributes (ext2/ext3/ext4)
271 depends on EXT2_FS_XATTR || EXT3_FS_XATTR || EXT4DEV_FS_XATTR
272 default y if EXT2_FS=y || EXT3_FS=y || EXT4DEV_FS=y
273 default m if EXT2_FS=m || EXT3_FS=m || EXT4DEV_FS=m
276 tristate "Reiserfs support"
278 Stores not just filenames but the files themselves in a balanced
279 tree. Uses journalling.
281 Balanced trees are more efficient than traditional file system
282 architectural foundations.
284 In general, ReiserFS is as fast as ext2, but is very efficient with
285 large directories and small files. Additional patches are needed
286 for NFS and quotas, please see <http://www.namesys.com/> for links.
288 It is more easily extended to have features currently found in
289 database and keyword search systems than block allocation based file
290 systems are. The next version will be so extended, and will support
291 plugins consistent with our motto ``It takes more than a license to
292 make source code open.''
294 Read <http://www.namesys.com/> to learn more about reiserfs.
296 Sponsored by Threshold Networks, Emusic.com, and Bigstorage.com.
298 If you like it, you can pay us to add new features to it that you
299 need, buy a support contract, or pay us to port it to another OS.
301 config REISERFS_CHECK
302 bool "Enable reiserfs debug mode"
303 depends on REISERFS_FS
305 If you set this to Y, then ReiserFS will perform every check it can
306 possibly imagine of its internal consistency throughout its
307 operation. It will also go substantially slower. More than once we
308 have forgotten that this was on, and then gone despondent over the
309 latest benchmarks.:-) Use of this option allows our team to go all
310 out in checking for consistency when debugging without fear of its
311 effect on end users. If you are on the verge of sending in a bug
312 report, say Y and you might get a useful error message. Almost
313 everyone should say N.
315 config REISERFS_PROC_INFO
316 bool "Stats in /proc/fs/reiserfs"
317 depends on REISERFS_FS && PROC_FS
319 Create under /proc/fs/reiserfs a hierarchy of files, displaying
320 various ReiserFS statistics and internal data at the expense of
321 making your kernel or module slightly larger (+8 KB). This also
322 increases the amount of kernel memory required for each mount.
323 Almost everyone but ReiserFS developers and people fine-tuning
324 reiserfs or tracing problems should say N.
326 config REISERFS_FS_XATTR
327 bool "ReiserFS extended attributes"
328 depends on REISERFS_FS
330 Extended attributes are name:value pairs associated with inodes by
331 the kernel or by users (see the attr(5) manual page, or visit
332 <http://acl.bestbits.at/> for details).
336 config REISERFS_FS_POSIX_ACL
337 bool "ReiserFS POSIX Access Control Lists"
338 depends on REISERFS_FS_XATTR
341 Posix Access Control Lists (ACLs) support permissions for users and
342 groups beyond the owner/group/world scheme.
344 To learn more about Access Control Lists, visit the Posix ACLs for
345 Linux website <http://acl.bestbits.at/>.
347 If you don't know what Access Control Lists are, say N
349 config REISERFS_FS_SECURITY
350 bool "ReiserFS Security Labels"
351 depends on REISERFS_FS_XATTR
353 Security labels support alternative access control models
354 implemented by security modules like SELinux. This option
355 enables an extended attribute handler for file security
356 labels in the ReiserFS filesystem.
358 If you are not using a security module that requires using
359 extended attributes for file security labels, say N.
362 tristate "JFS filesystem support"
365 This is a port of IBM's Journaled Filesystem . More information is
366 available in the file <file:Documentation/filesystems/jfs.txt>.
368 If you do not intend to use the JFS filesystem, say N.
371 bool "JFS POSIX Access Control Lists"
375 Posix Access Control Lists (ACLs) support permissions for users and
376 groups beyond the owner/group/world scheme.
378 To learn more about Access Control Lists, visit the Posix ACLs for
379 Linux website <http://acl.bestbits.at/>.
381 If you don't know what Access Control Lists are, say N
384 bool "JFS Security Labels"
387 Security labels support alternative access control models
388 implemented by security modules like SELinux. This option
389 enables an extended attribute handler for file security
390 labels in the jfs filesystem.
392 If you are not using a security module that requires using
393 extended attributes for file security labels, say N.
399 If you are experiencing any problems with the JFS filesystem, say
400 Y here. This will result in additional debugging messages to be
401 written to the system log. Under normal circumstances, this
402 results in very little overhead.
404 config JFS_STATISTICS
405 bool "JFS statistics"
408 Enabling this option will cause statistics from the JFS file system
409 to be made available to the user in the /proc/fs/jfs/ directory.
412 # Posix ACL utility routines (for now, only ext2/ext3/jfs/reiserfs)
414 # NOTE: you can implement Posix ACLs without these helpers (XFS does).
415 # Never use this symbol for ifdefs.
420 source "fs/xfs/Kconfig"
421 source "fs/gfs2/Kconfig"
424 tristate "OCFS2 file system support"
425 depends on NET && SYSFS
430 OCFS2 is a general purpose extent based shared disk cluster file
431 system with many similarities to ext3. It supports 64 bit inode
432 numbers, and has automatically extending metadata groups which may
433 also make it attractive for non-clustered use.
435 You'll want to install the ocfs2-tools package in order to at least
438 Project web page: http://oss.oracle.com/projects/ocfs2
439 Tools web page: http://oss.oracle.com/projects/ocfs2-tools
440 OCFS2 mailing lists: http://oss.oracle.com/projects/ocfs2/mailman/
442 Note: Features which OCFS2 does not support yet:
443 - extended attributes
445 - cluster aware flock
446 - Directory change notification (F_NOTIFY)
447 - Distributed Caching (F_SETLEASE/F_GETLEASE/break_lease)
449 - readpages / writepages (not user visible)
451 config OCFS2_DEBUG_MASKLOG
452 bool "OCFS2 logging support"
456 The ocfs2 filesystem has an extensive logging system. The system
457 allows selection of events to log via files in /sys/o2cb/logmask/.
458 This option will enlarge your kernel, but it allows debugging of
459 ocfs2 filesystem issues.
462 tristate "Minix fs support"
464 Minix is a simple operating system used in many classes about OS's.
465 The minix file system (method to organize files on a hard disk
466 partition or a floppy disk) was the original file system for Linux,
467 but has been superseded by the second extended file system ext2fs.
468 You don't want to use the minix file system on your hard disk
469 because of certain built-in restrictions, but it is sometimes found
470 on older Linux floppy disks. This option will enlarge your kernel
471 by about 28 KB. If unsure, say N.
473 To compile this file system support as a module, choose M here: the
474 module will be called minix. Note that the file system of your root
475 partition (the one containing the directory /) cannot be compiled as
479 tristate "ROM file system support"
481 This is a very small read-only file system mainly intended for
482 initial ram disks of installation disks, but it could be used for
483 other read-only media as well. Read
484 <file:Documentation/filesystems/romfs.txt> for details.
486 To compile this file system support as a module, choose M here: the
487 module will be called romfs. Note that the file system of your
488 root partition (the one containing the directory /) cannot be a
491 If you don't know whether you need it, then you don't need it:
497 bool "Inotify file change notification support"
500 Say Y here to enable inotify support. Inotify is a file change
501 notification system and a replacement for dnotify. Inotify fixes
502 numerous shortcomings in dnotify and introduces several new features
503 including multiple file events, one-shot support, and unmount
506 For more information, see Documentation/filesystems/inotify.txt
511 bool "Inotify support for userspace"
515 Say Y here to enable inotify support for userspace, including the
516 associated system calls. Inotify allows monitoring of both files and
517 directories via a single open fd. Events are read from the file
518 descriptor, which is also select()- and poll()-able.
520 For more information, see Documentation/filesystems/inotify.txt
527 If you say Y here, you will be able to set per user limits for disk
528 usage (also called disk quotas). Currently, it works for the
529 ext2, ext3, and reiserfs file system. ext3 also supports journalled
530 quotas for which you don't need to run quotacheck(8) after an unclean
532 For further details, read the Quota mini-HOWTO, available from
533 <http://www.tldp.org/docs.html#howto>, or the documentation provided
534 with the quota tools. Probably the quota support is only useful for
535 multi user systems. If unsure, say N.
538 tristate "Old quota format support"
541 This quota format was (is) used by kernels earlier than 2.4.22. If
542 you have quota working and you don't want to convert to new quota
546 tristate "Quota format v2 support"
549 This quota format allows using quotas with 32-bit UIDs/GIDs. If you
550 need this functionality say Y here.
554 depends on XFS_QUOTA || QUOTA
558 bool "Dnotify support"
561 Dnotify is a directory-based per-fd file change notification system
562 that uses signals to communicate events to user-space. There exist
563 superior alternatives, but some applications may still rely on
569 tristate "Kernel automounter support"
571 The automounter is a tool to automatically mount remote file systems
572 on demand. This implementation is partially kernel-based to reduce
573 overhead in the already-mounted case; this is unlike the BSD
574 automounter (amd), which is a pure user space daemon.
576 To use the automounter you need the user-space tools from the autofs
577 package; you can find the location in <file:Documentation/Changes>.
578 You also want to answer Y to "NFS file system support", below.
580 If you want to use the newer version of the automounter with more
581 features, say N here and say Y to "Kernel automounter v4 support",
584 To compile this support as a module, choose M here: the module will be
587 If you are not a part of a fairly large, distributed network, you
588 probably do not need an automounter, and can say N here.
591 tristate "Kernel automounter version 4 support (also supports v3)"
593 The automounter is a tool to automatically mount remote file systems
594 on demand. This implementation is partially kernel-based to reduce
595 overhead in the already-mounted case; this is unlike the BSD
596 automounter (amd), which is a pure user space daemon.
598 To use the automounter you need the user-space tools from
599 <ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4/>; you also
600 want to answer Y to "NFS file system support", below.
602 To compile this support as a module, choose M here: the module will be
603 called autofs4. You will need to add "alias autofs autofs4" to your
604 modules configuration file.
606 If you are not a part of a fairly large, distributed network or
607 don't have a laptop which needs to dynamically reconfigure to the
608 local network, you probably do not need an automounter, and can say
612 tristate "Filesystem in Userspace support"
614 With FUSE it is possible to implement a fully functional filesystem
615 in a userspace program.
617 There's also companion library: libfuse. This library along with
618 utilities is available from the FUSE homepage:
619 <http://fuse.sourceforge.net/>
621 See <file:Documentation/filesystems/fuse.txt> for more information.
622 See <file:Documentation/Changes> for needed library/utility version.
624 If you want to develop a userspace FS, or if you want to use
625 a filesystem based on FUSE, answer Y or M.
632 menu "CD-ROM/DVD Filesystems"
635 tristate "ISO 9660 CDROM file system support"
637 This is the standard file system used on CD-ROMs. It was previously
638 known as "High Sierra File System" and is called "hsfs" on other
639 Unix systems. The so-called Rock-Ridge extensions which allow for
640 long Unix filenames and symbolic links are also supported by this
641 driver. If you have a CD-ROM drive and want to do more with it than
642 just listen to audio CDs and watch its LEDs, say Y (and read
643 <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO,
644 available from <http://www.tldp.org/docs.html#howto>), thereby
645 enlarging your kernel by about 27 KB; otherwise say N.
647 To compile this file system support as a module, choose M here: the
648 module will be called isofs.
651 bool "Microsoft Joliet CDROM extensions"
652 depends on ISO9660_FS
655 Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system
656 which allows for long filenames in unicode format (unicode is the
657 new 16 bit character code, successor to ASCII, which encodes the
658 characters of almost all languages of the world; see
659 <http://www.unicode.org/> for more information). Say Y here if you
660 want to be able to read Joliet CD-ROMs under Linux.
663 bool "Transparent decompression extension"
664 depends on ISO9660_FS
667 This is a Linux-specific extension to RockRidge which lets you store
668 data in compressed form on a CD-ROM and have it transparently
669 decompressed when the CD-ROM is accessed. See
670 <http://www.kernel.org/pub/linux/utils/fs/zisofs/> for the tools
671 necessary to create such a filesystem. Say Y here if you want to be
672 able to read such compressed CD-ROMs.
675 tristate "UDF file system support"
677 This is the new file system used on some CD-ROMs and DVDs. Say Y if
678 you intend to mount DVD discs or CDRW's written in packet mode, or
679 if written to by other UDF utilities, such as DirectCD.
680 Please read <file:Documentation/filesystems/udf.txt>.
682 To compile this file system support as a module, choose M here: the
683 module will be called udf.
690 depends on (UDF_FS=m && NLS) || (UDF_FS=y && NLS=y)
696 menu "DOS/FAT/NT Filesystems"
702 If you want to use one of the FAT-based file systems (the MS-DOS and
703 VFAT (Windows 95) file systems), then you must say Y or M here
704 to include FAT support. You will then be able to mount partitions or
705 diskettes with FAT-based file systems and transparently access the
706 files on them, i.e. MSDOS files will look and behave just like all
709 This FAT support is not a file system in itself, it only provides
710 the foundation for the other file systems. You will have to say Y or
711 M to at least one of "MSDOS fs support" or "VFAT fs support" in
712 order to make use of it.
714 Another way to read and write MSDOS floppies and hard drive
715 partitions from within Linux (but not transparently) is with the
716 mtools ("man mtools") program suite. You don't need to say Y here in
719 If you need to move large files on floppies between a DOS and a
720 Linux box, say Y here, mount the floppy under Linux with an MSDOS
721 file system and use GNU tar's M option. GNU tar is a program
722 available for Unix and DOS ("man tar" or "info tar").
724 The FAT support will enlarge your kernel by about 37 KB. If unsure,
727 To compile this as a module, choose M here: the module will be called
728 fat. Note that if you compile the FAT support as a module, you
729 cannot compile any of the FAT-based file systems into the kernel
730 -- they will have to be modules as well.
733 tristate "MSDOS fs support"
736 This allows you to mount MSDOS partitions of your hard drive (unless
737 they are compressed; to access compressed MSDOS partitions under
738 Linux, you can either use the DOS emulator DOSEMU, described in the
739 DOSEMU-HOWTO, available from
740 <http://www.tldp.org/docs.html#howto>, or try dmsdosfs in
741 <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you
742 intend to use dosemu with a non-compressed MSDOS partition, say Y
743 here) and MSDOS floppies. This means that file access becomes
744 transparent, i.e. the MSDOS files look and behave just like all
747 If you have Windows 95 or Windows NT installed on your MSDOS
748 partitions, you should use the VFAT file system (say Y to "VFAT fs
749 support" below), or you will not be able to see the long filenames
750 generated by Windows 95 / Windows NT.
752 This option will enlarge your kernel by about 7 KB. If unsure,
753 answer Y. This will only work if you said Y to "DOS FAT fs support"
754 as well. To compile this as a module, choose M here: the module will
758 tristate "VFAT (Windows-95) fs support"
761 This option provides support for normal Windows file systems with
762 long filenames. That includes non-compressed FAT-based file systems
763 used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
764 programs from the mtools package.
766 The VFAT support enlarges your kernel by about 10 KB and it only
767 works if you said Y to the "DOS FAT fs support" above. Please read
768 the file <file:Documentation/filesystems/vfat.txt> for details. If
771 To compile this as a module, choose M here: the module will be called
774 config FAT_DEFAULT_CODEPAGE
775 int "Default codepage for FAT"
776 depends on MSDOS_FS || VFAT_FS
779 This option should be set to the codepage of your FAT filesystems.
780 It can be overridden with the "codepage" mount option.
781 See <file:Documentation/filesystems/vfat.txt> for more information.
783 config FAT_DEFAULT_IOCHARSET
784 string "Default iocharset for FAT"
788 Set this to the default input/output character set you'd
789 like FAT to use. It should probably match the character set
790 that most of your FAT filesystems use, and can be overridden
791 with the "iocharset" mount option for FAT filesystems.
792 Note that "utf8" is not recommended for FAT filesystems.
793 If unsure, you shouldn't set "utf8" here.
794 See <file:Documentation/filesystems/vfat.txt> for more information.
797 tristate "NTFS file system support"
800 NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003.
802 Saying Y or M here enables read support. There is partial, but
803 safe, write support available. For write support you must also
804 say Y to "NTFS write support" below.
806 There are also a number of user-space tools available, called
807 ntfsprogs. These include ntfsundelete and ntfsresize, that work
808 without NTFS support enabled in the kernel.
810 This is a rewrite from scratch of Linux NTFS support and replaced
811 the old NTFS code starting with Linux 2.5.11. A backport to
812 the Linux 2.4 kernel series is separately available as a patch
813 from the project web site.
815 For more information see <file:Documentation/filesystems/ntfs.txt>
816 and <http://linux-ntfs.sourceforge.net/>.
818 To compile this file system support as a module, choose M here: the
819 module will be called ntfs.
821 If you are not using Windows NT, 2000, XP or 2003 in addition to
822 Linux on your computer it is safe to say N.
825 bool "NTFS debugging support"
828 If you are experiencing any problems with the NTFS file system, say
829 Y here. This will result in additional consistency checks to be
830 performed by the driver as well as additional debugging messages to
831 be written to the system log. Note that debugging messages are
832 disabled by default. To enable them, supply the option debug_msgs=1
833 at the kernel command line when booting the kernel or as an option
834 to insmod when loading the ntfs module. Once the driver is active,
835 you can enable debugging messages by doing (as root):
836 echo 1 > /proc/sys/fs/ntfs-debug
837 Replacing the "1" with "0" would disable debug messages.
839 If you leave debugging messages disabled, this results in little
840 overhead, but enabling debug messages results in very significant
841 slowdown of the system.
843 When reporting bugs, please try to have available a full dump of
844 debugging messages while the misbehaviour was occurring.
847 bool "NTFS write support"
850 This enables the partial, but safe, write support in the NTFS driver.
852 The only supported operation is overwriting existing files, without
853 changing the file length. No file or directory creation, deletion or
854 renaming is possible. Note only non-resident files can be written to
855 so you may find that some very small files (<500 bytes or so) cannot
858 While we cannot guarantee that it will not damage any data, we have
859 so far not received a single report where the driver would have
860 damaged someones data so we assume it is perfectly safe to use.
862 Note: While write support is safe in this version (a rewrite from
863 scratch of the NTFS support), it should be noted that the old NTFS
864 write support, included in Linux 2.5.10 and before (since 1997),
867 This is currently useful with TopologiLinux. TopologiLinux is run
868 on top of any DOS/Microsoft Windows system without partitioning your
869 hard disk. Unlike other Linux distributions TopologiLinux does not
870 need its own partition. For more information see
871 <http://topologi-linux.sourceforge.net/>
873 It is perfectly safe to say N here.
878 menu "Pseudo filesystems"
881 bool "/proc file system support" if EMBEDDED
884 This is a virtual file system providing information about the status
885 of the system. "Virtual" means that it doesn't take up any space on
886 your hard disk: the files are created on the fly by the kernel when
887 you try to access them. Also, you cannot read the files with older
888 version of the program less: you need to use more or cat.
890 It's totally cool; for example, "cat /proc/interrupts" gives
891 information about what the different IRQs are used for at the moment
892 (there is a small number of Interrupt ReQuest lines in your computer
893 that are used by the attached devices to gain the CPU's attention --
894 often a source of trouble if two devices are mistakenly configured
895 to use the same IRQ). The program procinfo to display some
896 information about your system gathered from the /proc file system.
898 Before you can use the /proc file system, it has to be mounted,
899 meaning it has to be given a location in the directory hierarchy.
900 That location should be /proc. A command such as "mount -t proc proc
901 /proc" or the equivalent line in /etc/fstab does the job.
903 The /proc file system is explained in the file
904 <file:Documentation/filesystems/proc.txt> and on the proc(5) manpage
907 This option will enlarge your kernel by about 67 KB. Several
908 programs depend on this, so everyone should say Y here.
911 bool "/proc/kcore support" if !ARM
912 depends on PROC_FS && MMU
915 bool "/proc/vmcore support (EXPERIMENTAL)"
916 depends on PROC_FS && EXPERIMENTAL && CRASH_DUMP
919 Exports the dump image of crashed kernel in ELF format.
922 bool "Sysctl support (/proc/sys)" if EMBEDDED
927 The sysctl interface provides a means of dynamically changing
928 certain kernel parameters and variables on the fly without requiring
929 a recompile of the kernel or reboot of the system. The primary
930 interface is through /proc/sys. If you say Y here a tree of
931 modifiable sysctl entries will be generated beneath the
932 /proc/sys directory. They are explained in the files
933 in <file:Documentation/sysctl/>. Note that enabling this
934 option will enlarge the kernel by at least 8 KB.
936 As it is generally a good thing, you should say Y here unless
937 building a kernel for install/rescue disks or your system is very
941 bool "sysfs file system support" if EMBEDDED
944 The sysfs filesystem is a virtual filesystem that the kernel uses to
945 export internal kernel objects, their attributes, and their
946 relationships to one another.
948 Users can use sysfs to ascertain useful information about the running
949 kernel, such as the devices the kernel has discovered on each bus and
950 which driver each is bound to. sysfs can also be used to tune devices
951 and other kernel subsystems.
953 Some system agents rely on the information in sysfs to operate.
954 /sbin/hotplug uses device and object attributes in sysfs to assist in
955 delegating policy decisions, like persistently naming devices.
957 sysfs is currently used by the block subsystem to mount the root
958 partition. If sysfs is disabled you must specify the boot device on
959 the kernel boot command line via its major and minor numbers. For
960 example, "root=03:01" for /dev/hda1.
962 Designers of embedded systems may wish to say N here to conserve space.
965 bool "Virtual memory file system support (former shm fs)"
967 Tmpfs is a file system which keeps all files in virtual memory.
969 Everything in tmpfs is temporary in the sense that no files will be
970 created on your hard drive. The files live in memory and swap
971 space. If you unmount a tmpfs instance, everything stored therein is
974 See <file:Documentation/filesystems/tmpfs.txt> for details.
976 config TMPFS_POSIX_ACL
977 bool "Tmpfs POSIX Access Control Lists"
981 POSIX Access Control Lists (ACLs) support permissions for users and
982 groups beyond the owner/group/world scheme.
984 To learn more about Access Control Lists, visit the POSIX ACLs for
985 Linux website <http://acl.bestbits.at/>.
987 If you don't know what Access Control Lists are, say N.
990 bool "HugeTLB file system support"
991 depends on X86 || IA64 || PPC64 || SPARC64 || (SUPERH && MMU) || BROKEN
993 hugetlbfs is a filesystem backing for HugeTLB pages, based on
994 ramfs. For architectures that support it, say Y here and read
995 <file:Documentation/vm/hugetlbpage.txt> for details.
1003 tristate "Userspace-driven configuration filesystem (EXPERIMENTAL)"
1004 depends on SYSFS && EXPERIMENTAL
1006 configfs is a ram-based filesystem that provides the converse
1007 of sysfs's functionality. Where sysfs is a filesystem-based
1008 view of kernel objects, configfs is a filesystem-based manager
1009 of kernel objects, or config_items.
1011 Both sysfs and configfs can and should exist together on the
1012 same system. One is not a replacement for the other.
1016 menu "Miscellaneous filesystems"
1019 tristate "ADFS file system support (EXPERIMENTAL)"
1020 depends on BLOCK && EXPERIMENTAL
1022 The Acorn Disc Filing System is the standard file system of the
1023 RiscOS operating system which runs on Acorn's ARM-based Risc PC
1024 systems and the Acorn Archimedes range of machines. If you say Y
1025 here, Linux will be able to read from ADFS partitions on hard drives
1026 and from ADFS-formatted floppy discs. If you also want to be able to
1027 write to those devices, say Y to "ADFS write support" below.
1029 The ADFS partition should be the first partition (i.e.,
1030 /dev/[hs]d?1) on each of your drives. Please read the file
1031 <file:Documentation/filesystems/adfs.txt> for further details.
1033 To compile this code as a module, choose M here: the module will be
1039 bool "ADFS write support (DANGEROUS)"
1042 If you say Y here, you will be able to write to ADFS partitions on
1043 hard drives and ADFS-formatted floppy disks. This is experimental
1044 codes, so if you're unsure, say N.
1047 tristate "Amiga FFS file system support (EXPERIMENTAL)"
1048 depends on BLOCK && EXPERIMENTAL
1050 The Fast File System (FFS) is the common file system used on hard
1051 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
1052 if you want to be able to read and write files from and to an Amiga
1053 FFS partition on your hard drive. Amiga floppies however cannot be
1054 read with this driver due to an incompatibility of the floppy
1055 controller used in an Amiga and the standard floppy controller in
1056 PCs and workstations. Read <file:Documentation/filesystems/affs.txt>
1057 and <file:fs/affs/Changes>.
1059 With this driver you can also mount disk files used by Bernd
1060 Schmidt's Un*X Amiga Emulator
1061 (<http://www.freiburg.linux.de/~uae/>).
1062 If you want to do this, you will also need to say Y or M to "Loop
1063 device support", above.
1065 To compile this file system support as a module, choose M here: the
1066 module will be called affs. If unsure, say N.
1069 tristate "eCrypt filesystem layer support (EXPERIMENTAL)"
1070 depends on EXPERIMENTAL && KEYS && CRYPTO && NET
1072 Encrypted filesystem that operates on the VFS layer. See
1073 <file:Documentation/ecryptfs.txt> to learn more about
1074 eCryptfs. Userspace components are required and can be
1075 obtained from <http://ecryptfs.sf.net>.
1077 To compile this file system support as a module, choose M here: the
1078 module will be called ecryptfs.
1081 tristate "Apple Macintosh file system support (EXPERIMENTAL)"
1082 depends on BLOCK && EXPERIMENTAL
1085 If you say Y here, you will be able to mount Macintosh-formatted
1086 floppy disks and hard drive partitions with full read-write access.
1087 Please read <file:fs/hfs/HFS.txt> to learn about the available mount
1090 To compile this file system support as a module, choose M here: the
1091 module will be called hfs.
1094 tristate "Apple Extended HFS file system support"
1099 If you say Y here, you will be able to mount extended format
1100 Macintosh-formatted hard drive partitions with full read-write access.
1102 This file system is often called HFS+ and was introduced with
1103 MacOS 8. It includes all Mac specific filesystem data such as
1104 data forks and creator codes, but it also has several UNIX
1105 style features such as file ownership and permissions.
1108 tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)"
1109 depends on BLOCK && EXPERIMENTAL
1112 The BeOS File System (BeFS) is the native file system of Be, Inc's
1113 BeOS. Notable features include support for arbitrary attributes
1114 on files and directories, and database-like indices on selected
1115 attributes. (Also note that this driver doesn't make those features
1116 available at this time). It is a 64 bit filesystem, so it supports
1117 extremely large volumes and files.
1119 If you use this filesystem, you should also say Y to at least one
1120 of the NLS (native language support) options below.
1122 If you don't know what this is about, say N.
1124 To compile this as a module, choose M here: the module will be
1131 If you say Y here, you can use the 'debug' mount option to enable
1132 debugging output from the driver.
1135 tristate "BFS file system support (EXPERIMENTAL)"
1136 depends on BLOCK && EXPERIMENTAL
1138 Boot File System (BFS) is a file system used under SCO UnixWare to
1139 allow the bootloader access to the kernel image and other important
1140 files during the boot process. It is usually mounted under /stand
1141 and corresponds to the slice marked as "STAND" in the UnixWare
1142 partition. You should say Y if you want to read or write the files
1143 on your /stand slice from within Linux. You then also need to say Y
1144 to "UnixWare slices support", below. More information about the BFS
1145 file system is contained in the file
1146 <file:Documentation/filesystems/bfs.txt>.
1148 If you don't know what this is about, say N.
1150 To compile this as a module, choose M here: the module will be called
1151 bfs. Note that the file system of your root partition (the one
1152 containing the directory /) cannot be compiled as a module.
1157 tristate "EFS file system support (read only) (EXPERIMENTAL)"
1158 depends on BLOCK && EXPERIMENTAL
1160 EFS is an older file system used for non-ISO9660 CD-ROMs and hard
1161 disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
1162 uses the XFS file system for hard disk partitions however).
1164 This implementation only offers read-only access. If you don't know
1165 what all this is about, it's safe to say N. For more information
1166 about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
1168 To compile the EFS file system support as a module, choose M here: the
1169 module will be called efs.
1172 tristate "Journalling Flash File System v2 (JFFS2) support"
1176 JFFS2 is the second generation of the Journalling Flash File System
1177 for use on diskless embedded devices. It provides improved wear
1178 levelling, compression and support for hard links. You cannot use
1179 this on normal block devices, only on 'MTD' devices.
1181 Further information on the design and implementation of JFFS2 is
1182 available at <http://sources.redhat.com/jffs2/>.
1184 config JFFS2_FS_DEBUG
1185 int "JFFS2 debugging verbosity (0 = quiet, 2 = noisy)"
1189 This controls the amount of debugging messages produced by the JFFS2
1190 code. Set it to zero for use in production systems. For evaluation,
1191 testing and debugging, it's advisable to set it to one. This will
1192 enable a few assertions and will print debugging messages at the
1193 KERN_DEBUG loglevel, where they won't normally be visible. Level 2
1194 is unlikely to be useful - it enables extra debugging in certain
1195 areas which at one point needed debugging, but when the bugs were
1196 located and fixed, the detailed messages were relegated to level 2.
1198 If reporting bugs, please try to have available a full dump of the
1199 messages at debug level 1 while the misbehaviour was occurring.
1201 config JFFS2_FS_WRITEBUFFER
1202 bool "JFFS2 write-buffering support"
1206 This enables the write-buffering support in JFFS2.
1208 This functionality is required to support JFFS2 on the following
1209 types of flash devices:
1211 - NOR flash with transparent ECC
1214 config JFFS2_FS_WBUF_VERIFY
1215 bool "Verify JFFS2 write-buffer reads"
1216 depends on JFFS2_FS_WRITEBUFFER
1219 This causes JFFS2 to read back every page written through the
1220 write-buffer, and check for errors.
1222 config JFFS2_SUMMARY
1223 bool "JFFS2 summary support (EXPERIMENTAL)"
1224 depends on JFFS2_FS && EXPERIMENTAL
1227 This feature makes it possible to use summary information
1228 for faster filesystem mount.
1230 The summary information can be inserted into a filesystem image
1231 by the utility 'sumtool'.
1235 config JFFS2_FS_XATTR
1236 bool "JFFS2 XATTR support (EXPERIMENTAL)"
1237 depends on JFFS2_FS && EXPERIMENTAL
1240 Extended attributes are name:value pairs associated with inodes by
1241 the kernel or by users (see the attr(5) manual page, or visit
1242 <http://acl.bestbits.at/> for details).
1246 config JFFS2_FS_POSIX_ACL
1247 bool "JFFS2 POSIX Access Control Lists"
1248 depends on JFFS2_FS_XATTR
1252 Posix Access Control Lists (ACLs) support permissions for users and
1253 groups beyond the owner/group/world scheme.
1255 To learn more about Access Control Lists, visit the Posix ACLs for
1256 Linux website <http://acl.bestbits.at/>.
1258 If you don't know what Access Control Lists are, say N
1260 config JFFS2_FS_SECURITY
1261 bool "JFFS2 Security Labels"
1262 depends on JFFS2_FS_XATTR
1265 Security labels support alternative access control models
1266 implemented by security modules like SELinux. This option
1267 enables an extended attribute handler for file security
1268 labels in the jffs2 filesystem.
1270 If you are not using a security module that requires using
1271 extended attributes for file security labels, say N.
1273 config JFFS2_COMPRESSION_OPTIONS
1274 bool "Advanced compression options for JFFS2"
1278 Enabling this option allows you to explicitly choose which
1279 compression modules, if any, are enabled in JFFS2. Removing
1280 compressors and mean you cannot read existing file systems,
1281 and enabling experimental compressors can mean that you
1282 write a file system which cannot be read by a standard kernel.
1284 If unsure, you should _definitely_ say 'N'.
1287 bool "JFFS2 ZLIB compression support" if JFFS2_COMPRESSION_OPTIONS
1293 Zlib is designed to be a free, general-purpose, legally unencumbered,
1294 lossless data-compression library for use on virtually any computer
1295 hardware and operating system. See <http://www.gzip.org/zlib/> for
1296 further information.
1301 bool "JFFS2 LZO compression support" if JFFS2_COMPRESSION_OPTIONS
1303 select LZO_DECOMPRESS
1307 minilzo-based compression. Generally works better than Zlib.
1309 This feature was added in July, 2007. Say 'N' if you need
1310 compatibility with older bootloaders or kernels.
1313 bool "JFFS2 RTIME compression support" if JFFS2_COMPRESSION_OPTIONS
1317 Rtime does manage to recompress already-compressed data. Say 'Y' if unsure.
1320 bool "JFFS2 RUBIN compression support" if JFFS2_COMPRESSION_OPTIONS
1324 RUBINMIPS and DYNRUBIN compressors. Say 'N' if unsure.
1327 prompt "JFFS2 default compression mode" if JFFS2_COMPRESSION_OPTIONS
1328 default JFFS2_CMODE_PRIORITY
1331 You can set here the default compression mode of JFFS2 from
1332 the available compression modes. Don't touch if unsure.
1334 config JFFS2_CMODE_NONE
1335 bool "no compression"
1337 Uses no compression.
1339 config JFFS2_CMODE_PRIORITY
1342 Tries the compressors in a predefined order and chooses the first
1345 config JFFS2_CMODE_SIZE
1346 bool "size (EXPERIMENTAL)"
1348 Tries all compressors and chooses the one which has the smallest
1351 config JFFS2_CMODE_FAVOURLZO
1354 Tries all compressors and chooses the one which has the smallest
1355 result but gives some preference to LZO (which has faster
1356 decompression) at the expense of size.
1361 tristate "Compressed ROM file system support (cramfs)"
1365 Saying Y here includes support for CramFs (Compressed ROM File
1366 System). CramFs is designed to be a simple, small, and compressed
1367 file system for ROM based embedded systems. CramFs is read-only,
1368 limited to 256MB file systems (with 16MB files), and doesn't support
1369 16/32 bits uid/gid, hard links and timestamps.
1371 See <file:Documentation/filesystems/cramfs.txt> and
1372 <file:fs/cramfs/README> for further information.
1374 To compile this as a module, choose M here: the module will be called
1375 cramfs. Note that the root file system (the one containing the
1376 directory /) cannot be compiled as a module.
1381 tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
1384 FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
1385 file system format. VERITAS VxFS(TM) is the standard file system
1386 of SCO UnixWare (and possibly others) and optionally available
1387 for Sunsoft Solaris, HP-UX and many other operating systems.
1388 Currently only readonly access is supported.
1390 NOTE: the file system type as used by mount(1), mount(2) and
1391 fstab(5) is 'vxfs' as it describes the file system format, not
1394 To compile this as a module, choose M here: the module will be
1395 called freevxfs. If unsure, say N.
1399 tristate "OS/2 HPFS file system support"
1402 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
1403 is the file system used for organizing files on OS/2 hard disk
1404 partitions. Say Y if you want to be able to read files from and
1405 write files to an OS/2 HPFS partition on your hard drive. OS/2
1406 floppies however are in regular MSDOS format, so you don't need this
1407 option in order to be able to read them. Read
1408 <file:Documentation/filesystems/hpfs.txt>.
1410 To compile this file system support as a module, choose M here: the
1411 module will be called hpfs. If unsure, say N.
1416 tristate "QNX4 file system support (read only)"
1419 This is the file system used by the real-time operating systems
1420 QNX 4 and QNX 6 (the latter is also called QNX RTP).
1421 Further information is available at <http://www.qnx.com/>.
1422 Say Y if you intend to mount QNX hard disks or floppies.
1423 Unless you say Y to "QNX4FS read-write support" below, you will
1424 only be able to read these file systems.
1426 To compile this file system support as a module, choose M here: the
1427 module will be called qnx4.
1429 If you don't know whether you need it, then you don't need it:
1433 bool "QNX4FS write support (DANGEROUS)"
1434 depends on QNX4FS_FS && EXPERIMENTAL && BROKEN
1436 Say Y if you want to test write support for QNX4 file systems.
1438 It's currently broken, so for now:
1444 tristate "System V/Xenix/V7/Coherent file system support"
1447 SCO, Xenix and Coherent are commercial Unix systems for Intel
1448 machines, and Version 7 was used on the DEC PDP-11. Saying Y
1449 here would allow you to read from their floppies and hard disk
1452 If you have floppies or hard disk partitions like that, it is likely
1453 that they contain binaries from those other Unix systems; in order
1454 to run these binaries, you will want to install linux-abi which is
1455 a set of kernel modules that lets you run SCO, Xenix, Wyse,
1456 UnixWare, Dell Unix and System V programs under Linux. It is
1457 available via FTP (user: ftp) from
1458 <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
1459 NOTE: that will work only for binaries from Intel-based systems;
1460 PDP ones will have to wait until somebody ports Linux to -11 ;-)
1462 If you only intend to mount files from some other Unix over the
1463 network using NFS, you don't need the System V file system support
1464 (but you need NFS file system support obviously).
1466 Note that this option is generally not needed for floppies, since a
1467 good portable way to transport files and directories between unixes
1468 (and even other operating systems) is given by the tar program ("man
1469 tar" or preferably "info tar"). Note also that this option has
1470 nothing whatsoever to do with the option "System V IPC". Read about
1471 the System V file system in
1472 <file:Documentation/filesystems/sysv-fs.txt>.
1473 Saying Y here will enlarge your kernel by about 27 KB.
1475 To compile this as a module, choose M here: the module will be called
1478 If you haven't heard about all of this before, it's safe to say N.
1483 tristate "UFS file system support (read only)"
1486 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
1487 OpenBSD and NeXTstep) use a file system called UFS. Some System V
1488 Unixes can create and mount hard disk partitions and diskettes using
1489 this file system as well. Saying Y here will allow you to read from
1490 these partitions; if you also want to write to them, say Y to the
1491 experimental "UFS file system write support", below. Please read the
1492 file <file:Documentation/filesystems/ufs.txt> for more information.
1494 The recently released UFS2 variant (used in FreeBSD 5.x) is
1495 READ-ONLY supported.
1497 If you only intend to mount files from some other Unix over the
1498 network using NFS, you don't need the UFS file system support (but
1499 you need NFS file system support obviously).
1501 Note that this option is generally not needed for floppies, since a
1502 good portable way to transport files and directories between unixes
1503 (and even other operating systems) is given by the tar program ("man
1504 tar" or preferably "info tar").
1506 When accessing NeXTstep files, you may need to convert them from the
1507 NeXT character set to the Latin1 character set; use the program
1508 recode ("info recode") for this purpose.
1510 To compile the UFS file system support as a module, choose M here: the
1511 module will be called ufs.
1513 If you haven't heard about all of this before, it's safe to say N.
1516 bool "UFS file system write support (DANGEROUS)"
1517 depends on UFS_FS && EXPERIMENTAL
1519 Say Y here if you want to try writing to UFS partitions. This is
1520 experimental, so you should back up your UFS partitions beforehand.
1523 bool "UFS debugging"
1526 If you are experiencing any problems with the UFS filesystem, say
1527 Y here. This will result in _many_ additional debugging messages to be
1528 written to the system log.
1532 menu "Network File Systems"
1536 tristate "NFS file system support"
1540 select NFS_ACL_SUPPORT if NFS_V3_ACL
1542 If you are connected to some other (usually local) Unix computer
1543 (using SLIP, PLIP, PPP or Ethernet) and want to mount files residing
1544 on that computer (the NFS server) using the Network File Sharing
1545 protocol, say Y. "Mounting files" means that the client can access
1546 the files with usual UNIX commands as if they were sitting on the
1547 client's hard disk. For this to work, the server must run the
1548 programs nfsd and mountd (but does not need to have NFS file system
1549 support enabled in its kernel). NFS is explained in the Network
1550 Administrator's Guide, available from
1551 <http://www.tldp.org/docs.html#guide>, on its man page: "man
1552 nfs", and in the NFS-HOWTO.
1554 A superior but less widely used alternative to NFS is provided by
1555 the Coda file system; see "Coda file system support" below.
1557 If you say Y here, you should have said Y to TCP/IP networking also.
1558 This option would enlarge your kernel by about 27 KB.
1560 To compile this file system support as a module, choose M here: the
1561 module will be called nfs.
1563 If you are configuring a diskless machine which will mount its root
1564 file system over NFS at boot time, say Y here and to "Kernel
1565 level IP autoconfiguration" above and to "Root file system on NFS"
1566 below. You cannot compile this driver as a module in this case.
1567 There are two packages designed for booting diskless machines over
1568 the net: netboot, available from
1569 <http://ftp1.sourceforge.net/netboot/>, and Etherboot,
1570 available from <http://ftp1.sourceforge.net/etherboot/>.
1572 If you don't know what all this is about, say N.
1575 bool "Provide NFSv3 client support"
1578 Say Y here if you want your NFS client to be able to speak version
1579 3 of the NFS protocol.
1584 bool "Provide client support for the NFSv3 ACL protocol extension"
1587 Implement the NFSv3 ACL protocol extension for manipulating POSIX
1588 Access Control Lists. The server should also be compiled with
1589 the NFSv3 ACL protocol extension; see the CONFIG_NFSD_V3_ACL option.
1594 bool "Provide NFSv4 client support (EXPERIMENTAL)"
1595 depends on NFS_FS && EXPERIMENTAL
1596 select RPCSEC_GSS_KRB5
1598 Say Y here if you want your NFS client to be able to speak the newer
1599 version 4 of the NFS protocol.
1601 Note: Requires auxiliary userspace daemons which may be found on
1602 http://www.citi.umich.edu/projects/nfsv4/
1607 bool "Allow direct I/O on NFS files"
1610 This option enables applications to perform uncached I/O on files
1611 in NFS file systems using the O_DIRECT open() flag. When O_DIRECT
1612 is set for a file, its data is not cached in the system's page
1613 cache. Data is moved to and from user-level application buffers
1614 directly. Unlike local disk-based file systems, NFS O_DIRECT has
1615 no alignment restrictions.
1617 Unless your program is designed to use O_DIRECT properly, you are
1618 much better off allowing the NFS client to manage data caching for
1619 you. Misusing O_DIRECT can cause poor server performance or network
1620 storms. This kernel build option defaults OFF to avoid exposing
1621 system administrators unwittingly to a potentially hazardous
1624 For more details on NFS O_DIRECT, see fs/nfs/direct.c.
1626 If unsure, say N. This reduces the size of the NFS client, and
1627 causes open() to return EINVAL if a file residing in NFS is
1628 opened with the O_DIRECT flag.
1631 tristate "NFS server support"
1636 select NFSD_V2_ACL if NFSD_V3_ACL
1637 select NFS_ACL_SUPPORT if NFSD_V2_ACL
1638 select NFSD_TCP if NFSD_V4
1639 select CRYPTO_MD5 if NFSD_V4
1640 select CRYPTO if NFSD_V4
1641 select FS_POSIX_ACL if NFSD_V4
1643 If you want your Linux box to act as an NFS *server*, so that other
1644 computers on your local network which support NFS can access certain
1645 directories on your box transparently, you have two options: you can
1646 use the self-contained user space program nfsd, in which case you
1647 should say N here, or you can say Y and use the kernel based NFS
1648 server. The advantage of the kernel based solution is that it is
1651 In either case, you will need support software; the respective
1652 locations are given in the file <file:Documentation/Changes> in the
1655 If you say Y here, you will get support for version 2 of the NFS
1656 protocol (NFSv2). If you also want NFSv3, say Y to the next question
1659 Please read the NFS-HOWTO, available from
1660 <http://www.tldp.org/docs.html#howto>.
1662 To compile the NFS server support as a module, choose M here: the
1663 module will be called nfsd. If unsure, say N.
1670 bool "Provide NFSv3 server support"
1673 If you would like to include the NFSv3 server as well as the NFSv2
1674 server, say Y here. If unsure, say Y.
1677 bool "Provide server support for the NFSv3 ACL protocol extension"
1680 Implement the NFSv3 ACL protocol extension for manipulating POSIX
1681 Access Control Lists on exported file systems. NFS clients should
1682 be compiled with the NFSv3 ACL protocol extension; see the
1683 CONFIG_NFS_V3_ACL option. If unsure, say N.
1686 bool "Provide NFSv4 server support (EXPERIMENTAL)"
1687 depends on NFSD && NFSD_V3 && EXPERIMENTAL
1688 select RPCSEC_GSS_KRB5
1690 If you would like to include the NFSv4 server as well as the NFSv2
1691 and NFSv3 servers, say Y here. This feature is experimental, and
1692 should only be used if you are interested in helping to test NFSv4.
1696 bool "Provide NFS server over TCP support"
1700 If you want your NFS server to support TCP connections, say Y here.
1701 TCP connections usually perform better than the default UDP when
1702 the network is lossy or congested. If unsure, say Y.
1705 bool "Root file system on NFS"
1706 depends on NFS_FS=y && IP_PNP
1708 If you want your Linux box to mount its whole root file system (the
1709 one containing the directory /) from some other computer over the
1710 net via NFS (presumably because your box doesn't have a hard disk),
1711 say Y. Read <file:Documentation/nfsroot.txt> for details. It is
1712 likely that in this case, you also want to say Y to "Kernel level IP
1713 autoconfiguration" so that your box can discover its network address
1716 Most people say N here.
1723 depends on NFSD_V3 || NFS_V3
1729 config NFS_ACL_SUPPORT
1735 depends on NFSD || NFS_FS
1744 config SUNRPC_XPRT_RDMA
1745 tristate "RDMA transport for sunrpc (EXPERIMENTAL)"
1746 depends on SUNRPC && INFINIBAND && EXPERIMENTAL
1749 Adds a client RPC transport for supporting kernel NFS over RDMA
1750 mounts, including Infiniband and iWARP. Experimental.
1752 config SUNRPC_BIND34
1753 bool "Support for rpcbind versions 3 & 4 (EXPERIMENTAL)"
1754 depends on SUNRPC && EXPERIMENTAL
1756 Provides kernel support for querying rpcbind servers via versions 3
1757 and 4 of the rpcbind protocol. The kernel automatically falls back
1758 to version 2 if a remote rpcbind service does not support versions
1761 If unsure, say N to get traditional behavior (version 2 rpcbind
1764 config RPCSEC_GSS_KRB5
1765 tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
1766 depends on SUNRPC && EXPERIMENTAL
1773 Provides for secure RPC calls by means of a gss-api
1774 mechanism based on Kerberos V5. This is required for
1777 Note: Requires an auxiliary userspace daemon which may be found on
1778 http://www.citi.umich.edu/projects/nfsv4/
1782 config RPCSEC_GSS_SPKM3
1783 tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
1784 depends on SUNRPC && EXPERIMENTAL
1792 Provides for secure RPC calls by means of a gss-api
1793 mechanism based on the SPKM3 public-key mechanism.
1795 Note: Requires an auxiliary userspace daemon which may be found on
1796 http://www.citi.umich.edu/projects/nfsv4/
1801 tristate "SMB file system support (to mount Windows shares etc.)"
1805 SMB (Server Message Block) is the protocol Windows for Workgroups
1806 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
1807 files and printers over local networks. Saying Y here allows you to
1808 mount their file systems (often called "shares" in this context) and
1809 access them just like any other Unix directory. Currently, this
1810 works only if the Windows machines use TCP/IP as the underlying
1811 transport protocol, and not NetBEUI. For details, read
1812 <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
1813 available from <http://www.tldp.org/docs.html#howto>.
1815 Note: if you just want your box to act as an SMB *server* and make
1816 files and printing services available to Windows clients (which need
1817 to have a TCP/IP stack), you don't need to say Y here; you can use
1818 the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
1821 General information about how to connect Linux, Windows machines and
1822 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1824 To compile the SMB support as a module, choose M here: the module will
1825 be called smbfs. Most people say N, however.
1827 config SMB_NLS_DEFAULT
1828 bool "Use a default NLS"
1831 Enabling this will make smbfs use nls translations by default. You
1832 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
1833 settings and you need to give the default nls for the SMB server as
1834 CONFIG_SMB_NLS_REMOTE.
1836 The nls settings can be changed at mount time, if your smbmount
1837 supports that, using the codepage and iocharset parameters.
1839 smbmount from samba 2.2.0 or later supports this.
1841 config SMB_NLS_REMOTE
1842 string "Default Remote NLS Option"
1843 depends on SMB_NLS_DEFAULT
1846 This setting allows you to specify a default value for which
1847 codepage the server uses. If this field is left blank no
1848 translations will be done by default. The local codepage/charset
1849 default to CONFIG_NLS_DEFAULT.
1851 The nls settings can be changed at mount time, if your smbmount
1852 supports that, using the codepage and iocharset parameters.
1854 smbmount from samba 2.2.0 or later supports this.
1857 tristate "CIFS support (advanced network filesystem for Samba, Window and other CIFS compliant servers)"
1861 This is the client VFS module for the Common Internet File System
1862 (CIFS) protocol which is the successor to the Server Message Block
1863 (SMB) protocol, the native file sharing mechanism for most early
1864 PC operating systems. The CIFS protocol is fully supported by
1865 file servers such as Windows 2000 (including Windows 2003, NT 4
1866 and Windows XP) as well by Samba (which provides excellent CIFS
1867 server support for Linux and many other operating systems). Limited
1868 support for OS/2 and Windows ME and similar servers is provided as well.
1870 The intent of the cifs module is to provide an advanced
1871 network file system client for mounting to CIFS compliant servers,
1872 including support for dfs (hierarchical name space), secure per-user
1873 session establishment, safe distributed caching (oplock), optional
1874 packet signing, Unicode and other internationalization improvements.
1875 If you need to mount to Samba or Windows from this machine, say Y.
1878 bool "CIFS statistics"
1881 Enabling this option will cause statistics for each server share
1882 mounted by the cifs client to be displayed in /proc/fs/cifs/Stats
1885 bool "Extended statistics"
1886 depends on CIFS_STATS
1888 Enabling this option will allow more detailed statistics on SMB
1889 request timing to be displayed in /proc/fs/cifs/DebugData and also
1890 allow optional logging of slow responses to dmesg (depending on the
1891 value of /proc/fs/cifs/cifsFYI, see fs/cifs/README for more details).
1892 These additional statistics may have a minor effect on performance
1893 and memory utilization.
1895 Unless you are a developer or are doing network performance analysis
1898 config CIFS_WEAK_PW_HASH
1899 bool "Support legacy servers which use weaker LANMAN security"
1902 Modern CIFS servers including Samba and most Windows versions
1903 (since 1997) support stronger NTLM (and even NTLMv2 and Kerberos)
1904 security mechanisms. These hash the password more securely
1905 than the mechanisms used in the older LANMAN version of the
1906 SMB protocol needed to establish sessions with old SMB servers.
1908 Enabling this option allows the cifs module to mount to older
1909 LANMAN based servers such as OS/2 and Windows 95, but such
1910 mounts may be less secure than mounts using NTLM or more recent
1911 security mechanisms if you are on a public network. Unless you
1912 have a need to access old SMB servers (and are on a private
1913 network) you probably want to say N. Even if this support
1914 is enabled in the kernel build, they will not be used
1915 automatically. At runtime LANMAN mounts are disabled but
1916 can be set to required (or optional) either in
1917 /proc/fs/cifs (see fs/cifs/README for more detail) or via an
1918 option on the mount command. This support is disabled by
1919 default in order to reduce the possibility of a downgrade
1925 bool "CIFS extended attributes"
1928 Extended attributes are name:value pairs associated with inodes by
1929 the kernel or by users (see the attr(5) manual page, or visit
1930 <http://acl.bestbits.at/> for details). CIFS maps the name of
1931 extended attributes beginning with the user namespace prefix
1932 to SMB/CIFS EAs. EAs are stored on Windows servers without the
1933 user namespace prefix, but their names are seen by Linux cifs clients
1934 prefaced by the user namespace prefix. The system namespace
1935 (used by some filesystems to store ACLs) is not supported at
1941 bool "CIFS POSIX Extensions"
1942 depends on CIFS_XATTR
1944 Enabling this option will cause the cifs client to attempt to
1945 negotiate a newer dialect with servers, such as Samba 3.0.5
1946 or later, that optionally can handle more POSIX like (rather
1947 than Windows like) file behavior. It also enables
1948 support for POSIX ACLs (getfacl and setfacl) to servers
1949 (such as Samba 3.10 and later) which can negotiate
1950 CIFS POSIX ACL support. If unsure, say N.
1953 bool "Enable additional CIFS debugging routines"
1956 Enabling this option adds a few more debugging routines
1957 to the cifs code which slightly increases the size of
1958 the cifs module and can cause additional logging of debug
1959 messages in some error paths, slowing performance. This
1960 option can be turned off unless you are debugging
1961 cifs problems. If unsure, say N.
1963 config CIFS_EXPERIMENTAL
1964 bool "CIFS Experimental Features (EXPERIMENTAL)"
1965 depends on CIFS && EXPERIMENTAL
1967 Enables cifs features under testing. These features are
1968 experimental and currently include DFS support and directory
1969 change notification ie fcntl(F_DNOTIFY), as well as the upcall
1970 mechanism which will be used for Kerberos session negotiation
1971 and uid remapping. Some of these features also may depend on
1972 setting a value of 1 to the pseudo-file /proc/fs/cifs/Experimental
1973 (which is disabled by default). See the file fs/cifs/README
1974 for more details. If unsure, say N.
1977 bool "Kerberos/SPNEGO advanced session setup (EXPERIMENTAL)"
1978 depends on CIFS_EXPERIMENTAL
1979 depends on CONNECTOR
1981 Enables an upcall mechanism for CIFS which will be used to contact
1982 userspace helper utilities to provide SPNEGO packaged Kerberos
1983 tickets which are needed to mount to certain secure servers
1984 (for which more secure Kerberos authentication is required). If
1988 tristate "NCP file system support (to mount NetWare volumes)"
1989 depends on IPX!=n || INET
1991 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
1992 used by Novell NetWare clients to talk to file servers. It is to
1993 IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
1994 to mount NetWare file server volumes and to access them just like
1995 any other Unix directory. For details, please read the file
1996 <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
1997 the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
1999 You do not have to say Y here if you want your Linux box to act as a
2000 file *server* for Novell NetWare clients.
2002 General information about how to connect Linux, Windows machines and
2003 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
2005 To compile this as a module, choose M here: the module will be called
2006 ncpfs. Say N unless you are connected to a Novell network.
2008 source "fs/ncpfs/Kconfig"
2011 tristate "Coda file system support (advanced network fs)"
2014 Coda is an advanced network file system, similar to NFS in that it
2015 enables you to mount file systems of a remote server and access them
2016 with regular Unix commands as if they were sitting on your hard
2017 disk. Coda has several advantages over NFS: support for
2018 disconnected operation (e.g. for laptops), read/write server
2019 replication, security model for authentication and encryption,
2020 persistent client caches and write back caching.
2022 If you say Y here, your Linux box will be able to act as a Coda
2023 *client*. You will need user level code as well, both for the
2024 client and server. Servers are currently user level, i.e. they need
2025 no kernel support. Please read
2026 <file:Documentation/filesystems/coda.txt> and check out the Coda
2027 home page <http://www.coda.cs.cmu.edu/>.
2029 To compile the coda client support as a module, choose M here: the
2030 module will be called coda.
2032 config CODA_FS_OLD_API
2033 bool "Use 96-bit Coda file identifiers"
2036 A new kernel-userspace API had to be introduced for Coda v6.0
2037 to support larger 128-bit file identifiers as needed by the
2038 new realms implementation.
2040 However this new API is not backward compatible with older
2041 clients. If you really need to run the old Coda userspace
2042 cache manager then say Y.
2044 For most cases you probably want to say N.
2047 tristate "Andrew File System support (AFS) (EXPERIMENTAL)"
2048 depends on INET && EXPERIMENTAL
2051 If you say Y here, you will get an experimental Andrew File System
2052 driver. It currently only supports unsecured read-only AFS access.
2054 See <file:Documentation/filesystems/afs.txt> for more information.
2059 bool "AFS dynamic debugging"
2062 Say Y here to make runtime controllable debugging messages appear.
2064 See <file:Documentation/filesystems/afs.txt> for more information.
2069 tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
2070 depends on INET && NET_9P && EXPERIMENTAL
2072 If you say Y here, you will get experimental support for
2073 Plan 9 resource sharing via the 9P2000 protocol.
2075 See <http://v9fs.sf.net> for more information.
2082 menu "Partition Types"
2084 source "fs/partitions/Kconfig"
2089 source "fs/nls/Kconfig"
2090 source "fs/dlm/Kconfig"