2 # File system configuration
9 source "fs/ext2/Kconfig"
10 source "fs/ext3/Kconfig"
11 source "fs/ext4/Kconfig"
16 depends on EXT2_FS_XIP
19 source "fs/jbd/Kconfig"
20 source "fs/jbd2/Kconfig"
23 # Meta block cache for Extended Attributes (ext2/ext3/ext4)
25 default y if EXT2_FS=y && EXT2_FS_XATTR
26 default y if EXT3_FS=y && EXT3_FS_XATTR
27 default y if EXT4_FS=y && EXT4_FS_XATTR
28 default m if EXT2_FS_XATTR || EXT3_FS_XATTR || EXT4_FS_XATTR
30 source "fs/reiserfs/Kconfig"
31 source "fs/jfs/Kconfig"
34 # Posix ACL utility routines (for now, only ext2/ext3/jfs/reiserfs/nfs4)
36 # NOTE: you can implement Posix ACLs without these helpers (XFS does).
37 # Never use this symbol for ifdefs.
43 bool "Enable POSIX file locking API" if EMBEDDED
46 This option enables standard file locking support, required
47 for filesystems like NFS and for the flock() system
48 call. Disabling this option saves about 11k.
50 source "fs/xfs/Kconfig"
51 source "fs/gfs2/Kconfig"
52 source "fs/ocfs2/Kconfig"
53 source "fs/btrfs/Kconfig"
57 source "fs/notify/Kconfig"
62 If you say Y here, you will be able to set per user limits for disk
63 usage (also called disk quotas). Currently, it works for the
64 ext2, ext3, and reiserfs file system. ext3 also supports journalled
65 quotas for which you don't need to run quotacheck(8) after an unclean
67 For further details, read the Quota mini-HOWTO, available from
68 <http://www.tldp.org/docs.html#howto>, or the documentation provided
69 with the quota tools. Probably the quota support is only useful for
70 multi user systems. If unsure, say N.
72 config QUOTA_NETLINK_INTERFACE
73 bool "Report quota messages through netlink interface"
74 depends on QUOTA && NET
76 If you say Y here, quota warnings (about exceeding softlimit, reaching
77 hardlimit, etc.) will be reported through netlink interface. If unsure,
80 config PRINT_QUOTA_WARNING
81 bool "Print quota warnings to console (OBSOLETE)"
85 If you say Y here, quota warnings (about exceeding softlimit, reaching
86 hardlimit, etc.) will be printed to the process' controlling terminal.
87 Note that this behavior is currently deprecated and may go away in
88 future. Please use notification via netlink socket instead.
90 # Generic support for tree structured quota files. Seleted when needed.
95 tristate "Old quota format support"
98 This quota format was (is) used by kernels earlier than 2.4.22. If
99 you have quota working and you don't want to convert to new quota
103 tristate "Quota format v2 support"
107 This quota format allows using quotas with 32-bit UIDs/GIDs. If you
108 need this functionality say Y here.
112 depends on XFS_QUOTA || QUOTA
116 tristate "Kernel automounter support"
118 The automounter is a tool to automatically mount remote file systems
119 on demand. This implementation is partially kernel-based to reduce
120 overhead in the already-mounted case; this is unlike the BSD
121 automounter (amd), which is a pure user space daemon.
123 To use the automounter you need the user-space tools from the autofs
124 package; you can find the location in <file:Documentation/Changes>.
125 You also want to answer Y to "NFS file system support", below.
127 If you want to use the newer version of the automounter with more
128 features, say N here and say Y to "Kernel automounter v4 support",
131 To compile this support as a module, choose M here: the module will be
134 If you are not a part of a fairly large, distributed network, you
135 probably do not need an automounter, and can say N here.
138 tristate "Kernel automounter version 4 support (also supports v3)"
140 The automounter is a tool to automatically mount remote file systems
141 on demand. This implementation is partially kernel-based to reduce
142 overhead in the already-mounted case; this is unlike the BSD
143 automounter (amd), which is a pure user space daemon.
145 To use the automounter you need the user-space tools from
146 <ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4/>; you also
147 want to answer Y to "NFS file system support", below.
149 To compile this support as a module, choose M here: the module will be
150 called autofs4. You will need to add "alias autofs autofs4" to your
151 modules configuration file.
153 If you are not a part of a fairly large, distributed network or
154 don't have a laptop which needs to dynamically reconfigure to the
155 local network, you probably do not need an automounter, and can say
159 tristate "FUSE (Filesystem in Userspace) support"
161 With FUSE it is possible to implement a fully functional filesystem
162 in a userspace program.
164 There's also companion library: libfuse. This library along with
165 utilities is available from the FUSE homepage:
166 <http://fuse.sourceforge.net/>
168 See <file:Documentation/filesystems/fuse.txt> for more information.
169 See <file:Documentation/Changes> for needed library/utility version.
171 If you want to develop a userspace FS, or if you want to use
172 a filesystem based on FUSE, answer Y or M.
179 menu "CD-ROM/DVD Filesystems"
182 tristate "ISO 9660 CDROM file system support"
184 This is the standard file system used on CD-ROMs. It was previously
185 known as "High Sierra File System" and is called "hsfs" on other
186 Unix systems. The so-called Rock-Ridge extensions which allow for
187 long Unix filenames and symbolic links are also supported by this
188 driver. If you have a CD-ROM drive and want to do more with it than
189 just listen to audio CDs and watch its LEDs, say Y (and read
190 <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO,
191 available from <http://www.tldp.org/docs.html#howto>), thereby
192 enlarging your kernel by about 27 KB; otherwise say N.
194 To compile this file system support as a module, choose M here: the
195 module will be called isofs.
198 bool "Microsoft Joliet CDROM extensions"
199 depends on ISO9660_FS
202 Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system
203 which allows for long filenames in unicode format (unicode is the
204 new 16 bit character code, successor to ASCII, which encodes the
205 characters of almost all languages of the world; see
206 <http://www.unicode.org/> for more information). Say Y here if you
207 want to be able to read Joliet CD-ROMs under Linux.
210 bool "Transparent decompression extension"
211 depends on ISO9660_FS
214 This is a Linux-specific extension to RockRidge which lets you store
215 data in compressed form on a CD-ROM and have it transparently
216 decompressed when the CD-ROM is accessed. See
217 <http://www.kernel.org/pub/linux/utils/fs/zisofs/> for the tools
218 necessary to create such a filesystem. Say Y here if you want to be
219 able to read such compressed CD-ROMs.
222 tristate "UDF file system support"
225 This is the new file system used on some CD-ROMs and DVDs. Say Y if
226 you intend to mount DVD discs or CDRW's written in packet mode, or
227 if written to by other UDF utilities, such as DirectCD.
228 Please read <file:Documentation/filesystems/udf.txt>.
230 To compile this file system support as a module, choose M here: the
231 module will be called udf.
238 depends on (UDF_FS=m && NLS) || (UDF_FS=y && NLS=y)
244 menu "DOS/FAT/NT Filesystems"
250 If you want to use one of the FAT-based file systems (the MS-DOS and
251 VFAT (Windows 95) file systems), then you must say Y or M here
252 to include FAT support. You will then be able to mount partitions or
253 diskettes with FAT-based file systems and transparently access the
254 files on them, i.e. MSDOS files will look and behave just like all
257 This FAT support is not a file system in itself, it only provides
258 the foundation for the other file systems. You will have to say Y or
259 M to at least one of "MSDOS fs support" or "VFAT fs support" in
260 order to make use of it.
262 Another way to read and write MSDOS floppies and hard drive
263 partitions from within Linux (but not transparently) is with the
264 mtools ("man mtools") program suite. You don't need to say Y here in
267 If you need to move large files on floppies between a DOS and a
268 Linux box, say Y here, mount the floppy under Linux with an MSDOS
269 file system and use GNU tar's M option. GNU tar is a program
270 available for Unix and DOS ("man tar" or "info tar").
272 The FAT support will enlarge your kernel by about 37 KB. If unsure,
275 To compile this as a module, choose M here: the module will be called
276 fat. Note that if you compile the FAT support as a module, you
277 cannot compile any of the FAT-based file systems into the kernel
278 -- they will have to be modules as well.
281 tristate "MSDOS fs support"
284 This allows you to mount MSDOS partitions of your hard drive (unless
285 they are compressed; to access compressed MSDOS partitions under
286 Linux, you can either use the DOS emulator DOSEMU, described in the
287 DOSEMU-HOWTO, available from
288 <http://www.tldp.org/docs.html#howto>, or try dmsdosfs in
289 <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you
290 intend to use dosemu with a non-compressed MSDOS partition, say Y
291 here) and MSDOS floppies. This means that file access becomes
292 transparent, i.e. the MSDOS files look and behave just like all
295 If you have Windows 95 or Windows NT installed on your MSDOS
296 partitions, you should use the VFAT file system (say Y to "VFAT fs
297 support" below), or you will not be able to see the long filenames
298 generated by Windows 95 / Windows NT.
300 This option will enlarge your kernel by about 7 KB. If unsure,
301 answer Y. This will only work if you said Y to "DOS FAT fs support"
302 as well. To compile this as a module, choose M here: the module will
306 tristate "VFAT (Windows-95) fs support"
309 This option provides support for normal Windows file systems with
310 long filenames. That includes non-compressed FAT-based file systems
311 used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
312 programs from the mtools package.
314 The VFAT support enlarges your kernel by about 10 KB and it only
315 works if you said Y to the "DOS FAT fs support" above. Please read
316 the file <file:Documentation/filesystems/vfat.txt> for details. If
319 To compile this as a module, choose M here: the module will be called
322 config FAT_DEFAULT_CODEPAGE
323 int "Default codepage for FAT"
324 depends on MSDOS_FS || VFAT_FS
327 This option should be set to the codepage of your FAT filesystems.
328 It can be overridden with the "codepage" mount option.
329 See <file:Documentation/filesystems/vfat.txt> for more information.
331 config FAT_DEFAULT_IOCHARSET
332 string "Default iocharset for FAT"
336 Set this to the default input/output character set you'd
337 like FAT to use. It should probably match the character set
338 that most of your FAT filesystems use, and can be overridden
339 with the "iocharset" mount option for FAT filesystems.
340 Note that "utf8" is not recommended for FAT filesystems.
341 If unsure, you shouldn't set "utf8" here.
342 See <file:Documentation/filesystems/vfat.txt> for more information.
345 tristate "NTFS file system support"
348 NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003.
350 Saying Y or M here enables read support. There is partial, but
351 safe, write support available. For write support you must also
352 say Y to "NTFS write support" below.
354 There are also a number of user-space tools available, called
355 ntfsprogs. These include ntfsundelete and ntfsresize, that work
356 without NTFS support enabled in the kernel.
358 This is a rewrite from scratch of Linux NTFS support and replaced
359 the old NTFS code starting with Linux 2.5.11. A backport to
360 the Linux 2.4 kernel series is separately available as a patch
361 from the project web site.
363 For more information see <file:Documentation/filesystems/ntfs.txt>
364 and <http://www.linux-ntfs.org/>.
366 To compile this file system support as a module, choose M here: the
367 module will be called ntfs.
369 If you are not using Windows NT, 2000, XP or 2003 in addition to
370 Linux on your computer it is safe to say N.
373 bool "NTFS debugging support"
376 If you are experiencing any problems with the NTFS file system, say
377 Y here. This will result in additional consistency checks to be
378 performed by the driver as well as additional debugging messages to
379 be written to the system log. Note that debugging messages are
380 disabled by default. To enable them, supply the option debug_msgs=1
381 at the kernel command line when booting the kernel or as an option
382 to insmod when loading the ntfs module. Once the driver is active,
383 you can enable debugging messages by doing (as root):
384 echo 1 > /proc/sys/fs/ntfs-debug
385 Replacing the "1" with "0" would disable debug messages.
387 If you leave debugging messages disabled, this results in little
388 overhead, but enabling debug messages results in very significant
389 slowdown of the system.
391 When reporting bugs, please try to have available a full dump of
392 debugging messages while the misbehaviour was occurring.
395 bool "NTFS write support"
398 This enables the partial, but safe, write support in the NTFS driver.
400 The only supported operation is overwriting existing files, without
401 changing the file length. No file or directory creation, deletion or
402 renaming is possible. Note only non-resident files can be written to
403 so you may find that some very small files (<500 bytes or so) cannot
406 While we cannot guarantee that it will not damage any data, we have
407 so far not received a single report where the driver would have
408 damaged someones data so we assume it is perfectly safe to use.
410 Note: While write support is safe in this version (a rewrite from
411 scratch of the NTFS support), it should be noted that the old NTFS
412 write support, included in Linux 2.5.10 and before (since 1997),
415 This is currently useful with TopologiLinux. TopologiLinux is run
416 on top of any DOS/Microsoft Windows system without partitioning your
417 hard disk. Unlike other Linux distributions TopologiLinux does not
418 need its own partition. For more information see
419 <http://topologi-linux.sourceforge.net/>
421 It is perfectly safe to say N here.
426 menu "Pseudo filesystems"
428 source "fs/proc/Kconfig"
431 bool "sysfs file system support" if EMBEDDED
434 The sysfs filesystem is a virtual filesystem that the kernel uses to
435 export internal kernel objects, their attributes, and their
436 relationships to one another.
438 Users can use sysfs to ascertain useful information about the running
439 kernel, such as the devices the kernel has discovered on each bus and
440 which driver each is bound to. sysfs can also be used to tune devices
441 and other kernel subsystems.
443 Some system agents rely on the information in sysfs to operate.
444 /sbin/hotplug uses device and object attributes in sysfs to assist in
445 delegating policy decisions, like persistently naming devices.
447 sysfs is currently used by the block subsystem to mount the root
448 partition. If sysfs is disabled you must specify the boot device on
449 the kernel boot command line via its major and minor numbers. For
450 example, "root=03:01" for /dev/hda1.
452 Designers of embedded systems may wish to say N here to conserve space.
455 bool "Virtual memory file system support (former shm fs)"
457 Tmpfs is a file system which keeps all files in virtual memory.
459 Everything in tmpfs is temporary in the sense that no files will be
460 created on your hard drive. The files live in memory and swap
461 space. If you unmount a tmpfs instance, everything stored therein is
464 See <file:Documentation/filesystems/tmpfs.txt> for details.
466 config TMPFS_POSIX_ACL
467 bool "Tmpfs POSIX Access Control Lists"
471 POSIX Access Control Lists (ACLs) support permissions for users and
472 groups beyond the owner/group/world scheme.
474 To learn more about Access Control Lists, visit the POSIX ACLs for
475 Linux website <http://acl.bestbits.at/>.
477 If you don't know what Access Control Lists are, say N.
480 bool "HugeTLB file system support"
481 depends on X86 || IA64 || PPC64 || SPARC64 || (SUPERH && MMU) || \
482 (S390 && 64BIT) || BROKEN
484 hugetlbfs is a filesystem backing for HugeTLB pages, based on
485 ramfs. For architectures that support it, say Y here and read
486 <file:Documentation/vm/hugetlbpage.txt> for details.
494 tristate "Userspace-driven configuration filesystem"
497 configfs is a ram-based filesystem that provides the converse
498 of sysfs's functionality. Where sysfs is a filesystem-based
499 view of kernel objects, configfs is a filesystem-based manager
500 of kernel objects, or config_items.
502 Both sysfs and configfs can and should exist together on the
503 same system. One is not a replacement for the other.
507 menuconfig MISC_FILESYSTEMS
508 bool "Miscellaneous filesystems"
511 Say Y here to get to see options for various miscellaneous
512 filesystems, such as filesystems that came from other
515 This option alone does not add any kernel code.
517 If you say N, all options in this submenu will be skipped and
518 disabled; if unsure, say Y here.
523 tristate "ADFS file system support (EXPERIMENTAL)"
524 depends on BLOCK && EXPERIMENTAL
526 The Acorn Disc Filing System is the standard file system of the
527 RiscOS operating system which runs on Acorn's ARM-based Risc PC
528 systems and the Acorn Archimedes range of machines. If you say Y
529 here, Linux will be able to read from ADFS partitions on hard drives
530 and from ADFS-formatted floppy discs. If you also want to be able to
531 write to those devices, say Y to "ADFS write support" below.
533 The ADFS partition should be the first partition (i.e.,
534 /dev/[hs]d?1) on each of your drives. Please read the file
535 <file:Documentation/filesystems/adfs.txt> for further details.
537 To compile this code as a module, choose M here: the module will be
543 bool "ADFS write support (DANGEROUS)"
546 If you say Y here, you will be able to write to ADFS partitions on
547 hard drives and ADFS-formatted floppy disks. This is experimental
548 codes, so if you're unsure, say N.
551 tristate "Amiga FFS file system support (EXPERIMENTAL)"
552 depends on BLOCK && EXPERIMENTAL
554 The Fast File System (FFS) is the common file system used on hard
555 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
556 if you want to be able to read and write files from and to an Amiga
557 FFS partition on your hard drive. Amiga floppies however cannot be
558 read with this driver due to an incompatibility of the floppy
559 controller used in an Amiga and the standard floppy controller in
560 PCs and workstations. Read <file:Documentation/filesystems/affs.txt>
561 and <file:fs/affs/Changes>.
563 With this driver you can also mount disk files used by Bernd
564 Schmidt's Un*X Amiga Emulator
565 (<http://www.freiburg.linux.de/~uae/>).
566 If you want to do this, you will also need to say Y or M to "Loop
567 device support", above.
569 To compile this file system support as a module, choose M here: the
570 module will be called affs. If unsure, say N.
573 tristate "eCrypt filesystem layer support (EXPERIMENTAL)"
574 depends on EXPERIMENTAL && KEYS && CRYPTO && NET
576 Encrypted filesystem that operates on the VFS layer. See
577 <file:Documentation/filesystems/ecryptfs.txt> to learn more about
578 eCryptfs. Userspace components are required and can be
579 obtained from <http://ecryptfs.sf.net>.
581 To compile this file system support as a module, choose M here: the
582 module will be called ecryptfs.
585 tristate "Apple Macintosh file system support (EXPERIMENTAL)"
586 depends on BLOCK && EXPERIMENTAL
589 If you say Y here, you will be able to mount Macintosh-formatted
590 floppy disks and hard drive partitions with full read-write access.
591 Please read <file:Documentation/filesystems/hfs.txt> to learn about
592 the available mount options.
594 To compile this file system support as a module, choose M here: the
595 module will be called hfs.
598 tristate "Apple Extended HFS file system support"
603 If you say Y here, you will be able to mount extended format
604 Macintosh-formatted hard drive partitions with full read-write access.
606 This file system is often called HFS+ and was introduced with
607 MacOS 8. It includes all Mac specific filesystem data such as
608 data forks and creator codes, but it also has several UNIX
609 style features such as file ownership and permissions.
612 tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)"
613 depends on BLOCK && EXPERIMENTAL
616 The BeOS File System (BeFS) is the native file system of Be, Inc's
617 BeOS. Notable features include support for arbitrary attributes
618 on files and directories, and database-like indices on selected
619 attributes. (Also note that this driver doesn't make those features
620 available at this time). It is a 64 bit filesystem, so it supports
621 extremely large volumes and files.
623 If you use this filesystem, you should also say Y to at least one
624 of the NLS (native language support) options below.
626 If you don't know what this is about, say N.
628 To compile this as a module, choose M here: the module will be
635 If you say Y here, you can use the 'debug' mount option to enable
636 debugging output from the driver.
639 tristate "BFS file system support (EXPERIMENTAL)"
640 depends on BLOCK && EXPERIMENTAL
642 Boot File System (BFS) is a file system used under SCO UnixWare to
643 allow the bootloader access to the kernel image and other important
644 files during the boot process. It is usually mounted under /stand
645 and corresponds to the slice marked as "STAND" in the UnixWare
646 partition. You should say Y if you want to read or write the files
647 on your /stand slice from within Linux. You then also need to say Y
648 to "UnixWare slices support", below. More information about the BFS
649 file system is contained in the file
650 <file:Documentation/filesystems/bfs.txt>.
652 If you don't know what this is about, say N.
654 To compile this as a module, choose M here: the module will be called
655 bfs. Note that the file system of your root partition (the one
656 containing the directory /) cannot be compiled as a module.
661 tristate "EFS file system support (read only) (EXPERIMENTAL)"
662 depends on BLOCK && EXPERIMENTAL
664 EFS is an older file system used for non-ISO9660 CD-ROMs and hard
665 disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
666 uses the XFS file system for hard disk partitions however).
668 This implementation only offers read-only access. If you don't know
669 what all this is about, it's safe to say N. For more information
670 about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
672 To compile the EFS file system support as a module, choose M here: the
673 module will be called efs.
675 source "fs/jffs2/Kconfig"
676 # UBIFS File system configuration
677 source "fs/ubifs/Kconfig"
680 tristate "Compressed ROM file system support (cramfs)"
684 Saying Y here includes support for CramFs (Compressed ROM File
685 System). CramFs is designed to be a simple, small, and compressed
686 file system for ROM based embedded systems. CramFs is read-only,
687 limited to 256MB file systems (with 16MB files), and doesn't support
688 16/32 bits uid/gid, hard links and timestamps.
690 See <file:Documentation/filesystems/cramfs.txt> and
691 <file:fs/cramfs/README> for further information.
693 To compile this as a module, choose M here: the module will be called
694 cramfs. Note that the root file system (the one containing the
695 directory /) cannot be compiled as a module.
700 tristate "SquashFS 4.0 - Squashed file system support"
704 Saying Y here includes support for SquashFS 4.0 (a Compressed
705 Read-Only File System). Squashfs is a highly compressed read-only
706 filesystem for Linux. It uses zlib compression to compress both
707 files, inodes and directories. Inodes in the system are very small
708 and all blocks are packed to minimise data overhead. Block sizes
709 greater than 4K are supported up to a maximum of 1 Mbytes (default
710 block size 128K). SquashFS 4.0 supports 64 bit filesystems and files
711 (larger than 4GB), full uid/gid information, hard links and
714 Squashfs is intended for general read-only filesystem use, for
715 archival use (i.e. in cases where a .tar.gz file may be used), and in
716 embedded systems where low overhead is needed. Further information
717 and tools are available from http://squashfs.sourceforge.net.
719 If you want to compile this as a module ( = code which can be
720 inserted in and removed from the running kernel whenever you want),
721 say M here and read <file:Documentation/modules.txt>. The module
722 will be called squashfs. Note that the root file system (the one
723 containing the directory /) cannot be compiled as a module.
727 config SQUASHFS_EMBEDDED
729 bool "Additional option for memory-constrained systems"
733 Saying Y here allows you to specify cache size.
737 config SQUASHFS_FRAGMENT_CACHE_SIZE
738 int "Number of fragments cached" if SQUASHFS_EMBEDDED
742 By default SquashFS caches the last 3 fragments read from
743 the filesystem. Increasing this amount may mean SquashFS
744 has to re-read fragments less often from disk, at the expense
745 of extra system memory. Decreasing this amount will mean
746 SquashFS uses less memory at the expense of extra reads from disk.
748 Note there must be at least one cached fragment. Anything
749 much more than three will probably not make much difference.
752 tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
755 FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
756 file system format. VERITAS VxFS(TM) is the standard file system
757 of SCO UnixWare (and possibly others) and optionally available
758 for Sunsoft Solaris, HP-UX and many other operating systems.
759 Currently only readonly access is supported.
761 NOTE: the file system type as used by mount(1), mount(2) and
762 fstab(5) is 'vxfs' as it describes the file system format, not
765 To compile this as a module, choose M here: the module will be
766 called freevxfs. If unsure, say N.
769 tristate "Minix file system support"
772 Minix is a simple operating system used in many classes about OS's.
773 The minix file system (method to organize files on a hard disk
774 partition or a floppy disk) was the original file system for Linux,
775 but has been superseded by the second extended file system ext2fs.
776 You don't want to use the minix file system on your hard disk
777 because of certain built-in restrictions, but it is sometimes found
778 on older Linux floppy disks. This option will enlarge your kernel
779 by about 28 KB. If unsure, say N.
781 To compile this file system support as a module, choose M here: the
782 module will be called minix. Note that the file system of your root
783 partition (the one containing the directory /) cannot be compiled as
787 tristate "SonicBlue Optimized MPEG File System support"
791 This is the proprietary file system used by the Rio Karma music
792 player and ReplayTV DVR. Despite the name, this filesystem is not
793 more efficient than a standard FS for MPEG files, in fact likely
794 the opposite is true. Say Y if you have either of these devices
795 and wish to mount its disk.
797 To compile this file system support as a module, choose M here: the
798 module will be called omfs. If unsure, say N.
801 tristate "OS/2 HPFS file system support"
804 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
805 is the file system used for organizing files on OS/2 hard disk
806 partitions. Say Y if you want to be able to read files from and
807 write files to an OS/2 HPFS partition on your hard drive. OS/2
808 floppies however are in regular MSDOS format, so you don't need this
809 option in order to be able to read them. Read
810 <file:Documentation/filesystems/hpfs.txt>.
812 To compile this file system support as a module, choose M here: the
813 module will be called hpfs. If unsure, say N.
817 tristate "QNX4 file system support (read only)"
820 This is the file system used by the real-time operating systems
821 QNX 4 and QNX 6 (the latter is also called QNX RTP).
822 Further information is available at <http://www.qnx.com/>.
823 Say Y if you intend to mount QNX hard disks or floppies.
824 Unless you say Y to "QNX4FS read-write support" below, you will
825 only be able to read these file systems.
827 To compile this file system support as a module, choose M here: the
828 module will be called qnx4.
830 If you don't know whether you need it, then you don't need it:
834 bool "QNX4FS write support (DANGEROUS)"
835 depends on QNX4FS_FS && EXPERIMENTAL && BROKEN
837 Say Y if you want to test write support for QNX4 file systems.
839 It's currently broken, so for now:
843 tristate "ROM file system support"
846 This is a very small read-only file system mainly intended for
847 initial ram disks of installation disks, but it could be used for
848 other read-only media as well. Read
849 <file:Documentation/filesystems/romfs.txt> for details.
851 To compile this file system support as a module, choose M here: the
852 module will be called romfs. Note that the file system of your
853 root partition (the one containing the directory /) cannot be a
856 If you don't know whether you need it, then you don't need it:
861 tristate "System V/Xenix/V7/Coherent file system support"
864 SCO, Xenix and Coherent are commercial Unix systems for Intel
865 machines, and Version 7 was used on the DEC PDP-11. Saying Y
866 here would allow you to read from their floppies and hard disk
869 If you have floppies or hard disk partitions like that, it is likely
870 that they contain binaries from those other Unix systems; in order
871 to run these binaries, you will want to install linux-abi which is
872 a set of kernel modules that lets you run SCO, Xenix, Wyse,
873 UnixWare, Dell Unix and System V programs under Linux. It is
874 available via FTP (user: ftp) from
875 <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
876 NOTE: that will work only for binaries from Intel-based systems;
877 PDP ones will have to wait until somebody ports Linux to -11 ;-)
879 If you only intend to mount files from some other Unix over the
880 network using NFS, you don't need the System V file system support
881 (but you need NFS file system support obviously).
883 Note that this option is generally not needed for floppies, since a
884 good portable way to transport files and directories between unixes
885 (and even other operating systems) is given by the tar program ("man
886 tar" or preferably "info tar"). Note also that this option has
887 nothing whatsoever to do with the option "System V IPC". Read about
888 the System V file system in
889 <file:Documentation/filesystems/sysv-fs.txt>.
890 Saying Y here will enlarge your kernel by about 27 KB.
892 To compile this as a module, choose M here: the module will be called
895 If you haven't heard about all of this before, it's safe to say N.
899 tristate "UFS file system support (read only)"
902 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
903 OpenBSD and NeXTstep) use a file system called UFS. Some System V
904 Unixes can create and mount hard disk partitions and diskettes using
905 this file system as well. Saying Y here will allow you to read from
906 these partitions; if you also want to write to them, say Y to the
907 experimental "UFS file system write support", below. Please read the
908 file <file:Documentation/filesystems/ufs.txt> for more information.
910 The recently released UFS2 variant (used in FreeBSD 5.x) is
913 Note that this option is generally not needed for floppies, since a
914 good portable way to transport files and directories between unixes
915 (and even other operating systems) is given by the tar program ("man
916 tar" or preferably "info tar").
918 When accessing NeXTstep files, you may need to convert them from the
919 NeXT character set to the Latin1 character set; use the program
920 recode ("info recode") for this purpose.
922 To compile the UFS file system support as a module, choose M here: the
923 module will be called ufs.
925 If you haven't heard about all of this before, it's safe to say N.
928 bool "UFS file system write support (DANGEROUS)"
929 depends on UFS_FS && EXPERIMENTAL
931 Say Y here if you want to try writing to UFS partitions. This is
932 experimental, so you should back up your UFS partitions beforehand.
938 If you are experiencing any problems with the UFS filesystem, say
939 Y here. This will result in _many_ additional debugging messages to be
940 written to the system log.
942 endif # MISC_FILESYSTEMS
944 menuconfig NETWORK_FILESYSTEMS
945 bool "Network File Systems"
949 Say Y here to get to see options for network filesystems and
950 filesystem-related networking code, such as NFS daemon and
951 RPCSEC security modules.
953 This option alone does not add any kernel code.
955 If you say N, all options in this submenu will be skipped and
956 disabled; if unsure, say Y here.
958 if NETWORK_FILESYSTEMS
961 tristate "NFS client support"
965 select NFS_ACL_SUPPORT if NFS_V3_ACL
967 Choose Y here if you want to access files residing on other
968 computers using Sun's Network File System protocol. To compile
969 this file system support as a module, choose M here: the module
972 To mount file systems exported by NFS servers, you also need to
973 install the user space mount.nfs command which can be found in
974 the Linux nfs-utils package, available from http://linux-nfs.org/.
975 Information about using the mount command is available in the
976 mount(8) man page. More detail about the Linux NFS client
977 implementation is available via the nfs(5) man page.
979 Below you can choose which versions of the NFS protocol are
980 available in the kernel to mount NFS servers. Support for NFS
981 version 2 (RFC 1094) is always available when NFS_FS is selected.
983 To configure a system which mounts its root file system via NFS
984 at boot time, say Y here, select "Kernel level IP
985 autoconfiguration" in the NETWORK menu, and select "Root file
986 system on NFS" below. You cannot compile this file system as a
992 bool "NFS client support for NFS version 3"
995 This option enables support for version 3 of the NFS protocol
996 (RFC 1813) in the kernel's NFS client.
1001 bool "NFS client support for the NFSv3 ACL protocol extension"
1004 Some NFS servers support an auxiliary NFSv3 ACL protocol that
1005 Sun added to Solaris but never became an official part of the
1006 NFS version 3 protocol. This protocol extension allows
1007 applications on NFS clients to manipulate POSIX Access Control
1008 Lists on files residing on NFS servers. NFS servers enforce
1009 ACLs on local files whether this protocol is available or not.
1011 Choose Y here if your NFS server supports the Solaris NFSv3 ACL
1012 protocol extension and you want your NFS client to allow
1013 applications to access and modify ACLs on files on the server.
1015 Most NFS servers don't support the Solaris NFSv3 ACL protocol
1016 extension. You can choose N here or specify the "noacl" mount
1017 option to prevent your NFS client from trying to use the NFSv3
1023 bool "NFS client support for NFS version 4 (EXPERIMENTAL)"
1024 depends on NFS_FS && EXPERIMENTAL
1025 select RPCSEC_GSS_KRB5
1027 This option enables support for version 4 of the NFS protocol
1028 (RFC 3530) in the kernel's NFS client.
1030 To mount NFS servers using NFSv4, you also need to install user
1031 space programs which can be found in the Linux nfs-utils package,
1032 available from http://linux-nfs.org/.
1037 bool "Root file system on NFS"
1038 depends on NFS_FS=y && IP_PNP
1040 If you want your system to mount its root file system via NFS,
1041 choose Y here. This is common practice for managing systems
1042 without local permanent storage. For details, read
1043 <file:Documentation/filesystems/nfsroot.txt>.
1045 Most people say N here.
1048 tristate "NFS server support"
1053 select NFS_ACL_SUPPORT if NFSD_V2_ACL
1055 Choose Y here if you want to allow other computers to access
1056 files residing on this system using Sun's Network File System
1057 protocol. To compile the NFS server support as a module,
1058 choose M here: the module will be called nfsd.
1060 You may choose to use a user-space NFS server instead, in which
1061 case you can choose N here.
1063 To export local file systems using NFS, you also need to install
1064 user space programs which can be found in the Linux nfs-utils
1065 package, available from http://linux-nfs.org/. More detail about
1066 the Linux NFS server implementation is available via the
1067 exports(5) man page.
1069 Below you can choose which versions of the NFS protocol are
1070 available to clients mounting the NFS server on this system.
1071 Support for NFS version 2 (RFC 1094) is always available when
1072 CONFIG_NFSD is selected.
1081 bool "NFS server support for NFS version 3"
1084 This option enables support in your system's NFS server for
1085 version 3 of the NFS protocol (RFC 1813).
1090 bool "NFS server support for the NFSv3 ACL protocol extension"
1094 Solaris NFS servers support an auxiliary NFSv3 ACL protocol that
1095 never became an official part of the NFS version 3 protocol.
1096 This protocol extension allows applications on NFS clients to
1097 manipulate POSIX Access Control Lists on files residing on NFS
1098 servers. NFS servers enforce POSIX ACLs on local files whether
1099 this protocol is available or not.
1101 This option enables support in your system's NFS server for the
1102 NFSv3 ACL protocol extension allowing NFS clients to manipulate
1103 POSIX ACLs on files exported by your system's NFS server. NFS
1104 clients which support the Solaris NFSv3 ACL protocol can then
1105 access and modify ACLs on your NFS server.
1107 To store ACLs on your NFS server, you also need to enable ACL-
1108 related CONFIG options for your local file systems of choice.
1113 bool "NFS server support for NFS version 4 (EXPERIMENTAL)"
1114 depends on NFSD && PROC_FS && EXPERIMENTAL
1117 select RPCSEC_GSS_KRB5
1119 This option enables support in your system's NFS server for
1120 version 4 of the NFS protocol (RFC 3530).
1122 To export files using NFSv4, you need to install additional user
1123 space programs which can be found in the Linux nfs-utils package,
1124 available from http://linux-nfs.org/.
1133 depends on NFSD_V3 || NFS_V3
1139 config NFS_ACL_SUPPORT
1145 depends on NFSD || NFS_FS
1154 config SUNRPC_XPRT_RDMA
1156 depends on SUNRPC && INFINIBAND && EXPERIMENTAL
1157 default SUNRPC && INFINIBAND
1159 This option enables an RPC client transport capability that
1160 allows the NFS client to mount servers via an RDMA-enabled
1163 To compile RPC client RDMA transport support as a module,
1164 choose M here: the module will be called xprtrdma.
1168 config SUNRPC_REGISTER_V4
1169 bool "Register local RPC services via rpcbind v4 (EXPERIMENTAL)"
1170 depends on SUNRPC && EXPERIMENTAL
1173 Sun added support for registering RPC services at an IPv6
1174 address by creating two new versions of the rpcbind protocol
1177 This option enables support in the kernel RPC server for
1178 registering kernel RPC services via version 4 of the rpcbind
1179 protocol. If you enable this option, you must run a portmapper
1180 daemon that supports rpcbind protocol version 4.
1182 Serving NFS over IPv6 from knfsd (the kernel's NFS server)
1183 requires that you enable this option and use a portmapper that
1184 supports rpcbind version 4.
1186 If unsure, say N to get traditional behavior (register kernel
1187 RPC services using only rpcbind version 2). Distributions
1188 using the legacy Linux portmapper daemon must say N here.
1190 config RPCSEC_GSS_KRB5
1191 tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
1192 depends on SUNRPC && EXPERIMENTAL
1199 Choose Y here to enable Secure RPC using the Kerberos version 5
1200 GSS-API mechanism (RFC 1964).
1202 Secure RPC calls with Kerberos require an auxiliary user-space
1203 daemon which may be found in the Linux nfs-utils package
1204 available from http://linux-nfs.org/. In addition, user-space
1205 Kerberos support should be installed.
1209 config RPCSEC_GSS_SPKM3
1210 tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
1211 depends on SUNRPC && EXPERIMENTAL
1219 Choose Y here to enable Secure RPC using the SPKM3 public key
1220 GSS-API mechansim (RFC 2025).
1222 Secure RPC calls with SPKM3 require an auxiliary userspace
1223 daemon which may be found in the Linux nfs-utils package
1224 available from http://linux-nfs.org/.
1229 tristate "SMB file system support (OBSOLETE, please use CIFS)"
1233 SMB (Server Message Block) is the protocol Windows for Workgroups
1234 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
1235 files and printers over local networks. Saying Y here allows you to
1236 mount their file systems (often called "shares" in this context) and
1237 access them just like any other Unix directory. Currently, this
1238 works only if the Windows machines use TCP/IP as the underlying
1239 transport protocol, and not NetBEUI. For details, read
1240 <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
1241 available from <http://www.tldp.org/docs.html#howto>.
1243 Note: if you just want your box to act as an SMB *server* and make
1244 files and printing services available to Windows clients (which need
1245 to have a TCP/IP stack), you don't need to say Y here; you can use
1246 the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
1249 General information about how to connect Linux, Windows machines and
1250 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1252 To compile the SMB support as a module, choose M here:
1253 the module will be called smbfs. Most people say N, however.
1255 config SMB_NLS_DEFAULT
1256 bool "Use a default NLS"
1259 Enabling this will make smbfs use nls translations by default. You
1260 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
1261 settings and you need to give the default nls for the SMB server as
1262 CONFIG_SMB_NLS_REMOTE.
1264 The nls settings can be changed at mount time, if your smbmount
1265 supports that, using the codepage and iocharset parameters.
1267 smbmount from samba 2.2.0 or later supports this.
1269 config SMB_NLS_REMOTE
1270 string "Default Remote NLS Option"
1271 depends on SMB_NLS_DEFAULT
1274 This setting allows you to specify a default value for which
1275 codepage the server uses. If this field is left blank no
1276 translations will be done by default. The local codepage/charset
1277 default to CONFIG_NLS_DEFAULT.
1279 The nls settings can be changed at mount time, if your smbmount
1280 supports that, using the codepage and iocharset parameters.
1282 smbmount from samba 2.2.0 or later supports this.
1284 source "fs/cifs/Kconfig"
1287 tristate "NCP file system support (to mount NetWare volumes)"
1288 depends on IPX!=n || INET
1290 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
1291 used by Novell NetWare clients to talk to file servers. It is to
1292 IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
1293 to mount NetWare file server volumes and to access them just like
1294 any other Unix directory. For details, please read the file
1295 <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
1296 the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
1298 You do not have to say Y here if you want your Linux box to act as a
1299 file *server* for Novell NetWare clients.
1301 General information about how to connect Linux, Windows machines and
1302 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1304 To compile this as a module, choose M here: the module will be called
1305 ncpfs. Say N unless you are connected to a Novell network.
1307 source "fs/ncpfs/Kconfig"
1310 tristate "Coda file system support (advanced network fs)"
1313 Coda is an advanced network file system, similar to NFS in that it
1314 enables you to mount file systems of a remote server and access them
1315 with regular Unix commands as if they were sitting on your hard
1316 disk. Coda has several advantages over NFS: support for
1317 disconnected operation (e.g. for laptops), read/write server
1318 replication, security model for authentication and encryption,
1319 persistent client caches and write back caching.
1321 If you say Y here, your Linux box will be able to act as a Coda
1322 *client*. You will need user level code as well, both for the
1323 client and server. Servers are currently user level, i.e. they need
1324 no kernel support. Please read
1325 <file:Documentation/filesystems/coda.txt> and check out the Coda
1326 home page <http://www.coda.cs.cmu.edu/>.
1328 To compile the coda client support as a module, choose M here: the
1329 module will be called coda.
1332 tristate "Andrew File System support (AFS) (EXPERIMENTAL)"
1333 depends on INET && EXPERIMENTAL
1336 If you say Y here, you will get an experimental Andrew File System
1337 driver. It currently only supports unsecured read-only AFS access.
1339 See <file:Documentation/filesystems/afs.txt> for more information.
1344 bool "AFS dynamic debugging"
1347 Say Y here to make runtime controllable debugging messages appear.
1349 See <file:Documentation/filesystems/afs.txt> for more information.
1354 tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
1355 depends on INET && NET_9P && EXPERIMENTAL
1357 If you say Y here, you will get experimental support for
1358 Plan 9 resource sharing via the 9P2000 protocol.
1360 See <http://v9fs.sf.net> for more information.
1364 endif # NETWORK_FILESYSTEMS
1367 menu "Partition Types"
1369 source "fs/partitions/Kconfig"
1374 source "fs/nls/Kconfig"
1375 source "fs/dlm/Kconfig"