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
115 source "fs/autofs/Kconfig"
116 source "fs/autofs4/Kconfig"
117 source "fs/fuse/Kconfig"
124 menu "CD-ROM/DVD Filesystems"
126 source "fs/isofs/Kconfig"
127 source "fs/udf/Kconfig"
133 menu "DOS/FAT/NT Filesystems"
135 source "fs/fat/Kconfig"
136 source "fs/ntfs/Kconfig"
141 menu "Pseudo filesystems"
143 source "fs/proc/Kconfig"
144 source "fs/sysfs/Kconfig"
147 bool "Virtual memory file system support (former shm fs)"
149 Tmpfs is a file system which keeps all files in virtual memory.
151 Everything in tmpfs is temporary in the sense that no files will be
152 created on your hard drive. The files live in memory and swap
153 space. If you unmount a tmpfs instance, everything stored therein is
156 See <file:Documentation/filesystems/tmpfs.txt> for details.
158 config TMPFS_POSIX_ACL
159 bool "Tmpfs POSIX Access Control Lists"
163 POSIX Access Control Lists (ACLs) support permissions for users and
164 groups beyond the owner/group/world scheme.
166 To learn more about Access Control Lists, visit the POSIX ACLs for
167 Linux website <http://acl.bestbits.at/>.
169 If you don't know what Access Control Lists are, say N.
172 bool "HugeTLB file system support"
173 depends on X86 || IA64 || PPC64 || SPARC64 || (SUPERH && MMU) || \
174 (S390 && 64BIT) || BROKEN
176 hugetlbfs is a filesystem backing for HugeTLB pages, based on
177 ramfs. For architectures that support it, say Y here and read
178 <file:Documentation/vm/hugetlbpage.txt> for details.
185 source "fs/configfs/Kconfig"
189 menuconfig MISC_FILESYSTEMS
190 bool "Miscellaneous filesystems"
193 Say Y here to get to see options for various miscellaneous
194 filesystems, such as filesystems that came from other
197 This option alone does not add any kernel code.
199 If you say N, all options in this submenu will be skipped and
200 disabled; if unsure, say Y here.
204 source "fs/adfs/Kconfig"
205 source "fs/affs/Kconfig"
206 source "fs/ecryptfs/Kconfig"
207 source "fs/hfs/Kconfig"
208 source "fs/hfsplus/Kconfig"
209 source "fs/befs/Kconfig"
210 source "fs/bfs/Kconfig"
211 source "fs/efs/Kconfig"
212 source "fs/jffs2/Kconfig"
213 # UBIFS File system configuration
214 source "fs/ubifs/Kconfig"
215 source "fs/cramfs/Kconfig"
216 source "fs/squashfs/Kconfig"
217 source "fs/freevxfs/Kconfig"
218 source "fs/minix/Kconfig"
219 source "fs/omfs/Kconfig"
220 source "fs/hpfs/Kconfig"
221 source "fs/qnx4/Kconfig"
224 tristate "ROM file system support"
227 This is a very small read-only file system mainly intended for
228 initial ram disks of installation disks, but it could be used for
229 other read-only media as well. Read
230 <file:Documentation/filesystems/romfs.txt> for details.
232 To compile this file system support as a module, choose M here: the
233 module will be called romfs. Note that the file system of your
234 root partition (the one containing the directory /) cannot be a
237 If you don't know whether you need it, then you don't need it:
242 tristate "System V/Xenix/V7/Coherent file system support"
245 SCO, Xenix and Coherent are commercial Unix systems for Intel
246 machines, and Version 7 was used on the DEC PDP-11. Saying Y
247 here would allow you to read from their floppies and hard disk
250 If you have floppies or hard disk partitions like that, it is likely
251 that they contain binaries from those other Unix systems; in order
252 to run these binaries, you will want to install linux-abi which is
253 a set of kernel modules that lets you run SCO, Xenix, Wyse,
254 UnixWare, Dell Unix and System V programs under Linux. It is
255 available via FTP (user: ftp) from
256 <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
257 NOTE: that will work only for binaries from Intel-based systems;
258 PDP ones will have to wait until somebody ports Linux to -11 ;-)
260 If you only intend to mount files from some other Unix over the
261 network using NFS, you don't need the System V file system support
262 (but you need NFS file system support obviously).
264 Note that this option is generally not needed for floppies, since a
265 good portable way to transport files and directories between unixes
266 (and even other operating systems) is given by the tar program ("man
267 tar" or preferably "info tar"). Note also that this option has
268 nothing whatsoever to do with the option "System V IPC". Read about
269 the System V file system in
270 <file:Documentation/filesystems/sysv-fs.txt>.
271 Saying Y here will enlarge your kernel by about 27 KB.
273 To compile this as a module, choose M here: the module will be called
276 If you haven't heard about all of this before, it's safe to say N.
280 tristate "UFS file system support (read only)"
283 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
284 OpenBSD and NeXTstep) use a file system called UFS. Some System V
285 Unixes can create and mount hard disk partitions and diskettes using
286 this file system as well. Saying Y here will allow you to read from
287 these partitions; if you also want to write to them, say Y to the
288 experimental "UFS file system write support", below. Please read the
289 file <file:Documentation/filesystems/ufs.txt> for more information.
291 The recently released UFS2 variant (used in FreeBSD 5.x) is
294 Note that this option is generally not needed for floppies, since a
295 good portable way to transport files and directories between unixes
296 (and even other operating systems) is given by the tar program ("man
297 tar" or preferably "info tar").
299 When accessing NeXTstep files, you may need to convert them from the
300 NeXT character set to the Latin1 character set; use the program
301 recode ("info recode") for this purpose.
303 To compile the UFS file system support as a module, choose M here: the
304 module will be called ufs.
306 If you haven't heard about all of this before, it's safe to say N.
309 bool "UFS file system write support (DANGEROUS)"
310 depends on UFS_FS && EXPERIMENTAL
312 Say Y here if you want to try writing to UFS partitions. This is
313 experimental, so you should back up your UFS partitions beforehand.
319 If you are experiencing any problems with the UFS filesystem, say
320 Y here. This will result in _many_ additional debugging messages to be
321 written to the system log.
323 endif # MISC_FILESYSTEMS
325 menuconfig NETWORK_FILESYSTEMS
326 bool "Network File Systems"
330 Say Y here to get to see options for network filesystems and
331 filesystem-related networking code, such as NFS daemon and
332 RPCSEC security modules.
334 This option alone does not add any kernel code.
336 If you say N, all options in this submenu will be skipped and
337 disabled; if unsure, say Y here.
339 if NETWORK_FILESYSTEMS
342 tristate "NFS client support"
346 select NFS_ACL_SUPPORT if NFS_V3_ACL
348 Choose Y here if you want to access files residing on other
349 computers using Sun's Network File System protocol. To compile
350 this file system support as a module, choose M here: the module
353 To mount file systems exported by NFS servers, you also need to
354 install the user space mount.nfs command which can be found in
355 the Linux nfs-utils package, available from http://linux-nfs.org/.
356 Information about using the mount command is available in the
357 mount(8) man page. More detail about the Linux NFS client
358 implementation is available via the nfs(5) man page.
360 Below you can choose which versions of the NFS protocol are
361 available in the kernel to mount NFS servers. Support for NFS
362 version 2 (RFC 1094) is always available when NFS_FS is selected.
364 To configure a system which mounts its root file system via NFS
365 at boot time, say Y here, select "Kernel level IP
366 autoconfiguration" in the NETWORK menu, and select "Root file
367 system on NFS" below. You cannot compile this file system as a
373 bool "NFS client support for NFS version 3"
376 This option enables support for version 3 of the NFS protocol
377 (RFC 1813) in the kernel's NFS client.
382 bool "NFS client support for the NFSv3 ACL protocol extension"
385 Some NFS servers support an auxiliary NFSv3 ACL protocol that
386 Sun added to Solaris but never became an official part of the
387 NFS version 3 protocol. This protocol extension allows
388 applications on NFS clients to manipulate POSIX Access Control
389 Lists on files residing on NFS servers. NFS servers enforce
390 ACLs on local files whether this protocol is available or not.
392 Choose Y here if your NFS server supports the Solaris NFSv3 ACL
393 protocol extension and you want your NFS client to allow
394 applications to access and modify ACLs on files on the server.
396 Most NFS servers don't support the Solaris NFSv3 ACL protocol
397 extension. You can choose N here or specify the "noacl" mount
398 option to prevent your NFS client from trying to use the NFSv3
404 bool "NFS client support for NFS version 4 (EXPERIMENTAL)"
405 depends on NFS_FS && EXPERIMENTAL
406 select RPCSEC_GSS_KRB5
408 This option enables support for version 4 of the NFS protocol
409 (RFC 3530) in the kernel's NFS client.
411 To mount NFS servers using NFSv4, you also need to install user
412 space programs which can be found in the Linux nfs-utils package,
413 available from http://linux-nfs.org/.
418 bool "Root file system on NFS"
419 depends on NFS_FS=y && IP_PNP
421 If you want your system to mount its root file system via NFS,
422 choose Y here. This is common practice for managing systems
423 without local permanent storage. For details, read
424 <file:Documentation/filesystems/nfsroot.txt>.
426 Most people say N here.
429 tristate "NFS server support"
434 select NFS_ACL_SUPPORT if NFSD_V2_ACL
436 Choose Y here if you want to allow other computers to access
437 files residing on this system using Sun's Network File System
438 protocol. To compile the NFS server support as a module,
439 choose M here: the module will be called nfsd.
441 You may choose to use a user-space NFS server instead, in which
442 case you can choose N here.
444 To export local file systems using NFS, you also need to install
445 user space programs which can be found in the Linux nfs-utils
446 package, available from http://linux-nfs.org/. More detail about
447 the Linux NFS server implementation is available via the
450 Below you can choose which versions of the NFS protocol are
451 available to clients mounting the NFS server on this system.
452 Support for NFS version 2 (RFC 1094) is always available when
453 CONFIG_NFSD is selected.
462 bool "NFS server support for NFS version 3"
465 This option enables support in your system's NFS server for
466 version 3 of the NFS protocol (RFC 1813).
471 bool "NFS server support for the NFSv3 ACL protocol extension"
475 Solaris NFS servers support an auxiliary NFSv3 ACL protocol that
476 never became an official part of the NFS version 3 protocol.
477 This protocol extension allows applications on NFS clients to
478 manipulate POSIX Access Control Lists on files residing on NFS
479 servers. NFS servers enforce POSIX ACLs on local files whether
480 this protocol is available or not.
482 This option enables support in your system's NFS server for the
483 NFSv3 ACL protocol extension allowing NFS clients to manipulate
484 POSIX ACLs on files exported by your system's NFS server. NFS
485 clients which support the Solaris NFSv3 ACL protocol can then
486 access and modify ACLs on your NFS server.
488 To store ACLs on your NFS server, you also need to enable ACL-
489 related CONFIG options for your local file systems of choice.
494 bool "NFS server support for NFS version 4 (EXPERIMENTAL)"
495 depends on NFSD && PROC_FS && EXPERIMENTAL
498 select RPCSEC_GSS_KRB5
500 This option enables support in your system's NFS server for
501 version 4 of the NFS protocol (RFC 3530).
503 To export files using NFSv4, you need to install additional user
504 space programs which can be found in the Linux nfs-utils package,
505 available from http://linux-nfs.org/.
514 depends on NFSD_V3 || NFS_V3
520 config NFS_ACL_SUPPORT
526 depends on NFSD || NFS_FS
535 config SUNRPC_XPRT_RDMA
537 depends on SUNRPC && INFINIBAND && EXPERIMENTAL
538 default SUNRPC && INFINIBAND
540 This option enables an RPC client transport capability that
541 allows the NFS client to mount servers via an RDMA-enabled
544 To compile RPC client RDMA transport support as a module,
545 choose M here: the module will be called xprtrdma.
549 config SUNRPC_REGISTER_V4
550 bool "Register local RPC services via rpcbind v4 (EXPERIMENTAL)"
551 depends on SUNRPC && EXPERIMENTAL
554 Sun added support for registering RPC services at an IPv6
555 address by creating two new versions of the rpcbind protocol
558 This option enables support in the kernel RPC server for
559 registering kernel RPC services via version 4 of the rpcbind
560 protocol. If you enable this option, you must run a portmapper
561 daemon that supports rpcbind protocol version 4.
563 Serving NFS over IPv6 from knfsd (the kernel's NFS server)
564 requires that you enable this option and use a portmapper that
565 supports rpcbind version 4.
567 If unsure, say N to get traditional behavior (register kernel
568 RPC services using only rpcbind version 2). Distributions
569 using the legacy Linux portmapper daemon must say N here.
571 config RPCSEC_GSS_KRB5
572 tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
573 depends on SUNRPC && EXPERIMENTAL
580 Choose Y here to enable Secure RPC using the Kerberos version 5
581 GSS-API mechanism (RFC 1964).
583 Secure RPC calls with Kerberos require an auxiliary user-space
584 daemon which may be found in the Linux nfs-utils package
585 available from http://linux-nfs.org/. In addition, user-space
586 Kerberos support should be installed.
590 config RPCSEC_GSS_SPKM3
591 tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
592 depends on SUNRPC && EXPERIMENTAL
600 Choose Y here to enable Secure RPC using the SPKM3 public key
601 GSS-API mechansim (RFC 2025).
603 Secure RPC calls with SPKM3 require an auxiliary userspace
604 daemon which may be found in the Linux nfs-utils package
605 available from http://linux-nfs.org/.
610 tristate "SMB file system support (OBSOLETE, please use CIFS)"
614 SMB (Server Message Block) is the protocol Windows for Workgroups
615 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
616 files and printers over local networks. Saying Y here allows you to
617 mount their file systems (often called "shares" in this context) and
618 access them just like any other Unix directory. Currently, this
619 works only if the Windows machines use TCP/IP as the underlying
620 transport protocol, and not NetBEUI. For details, read
621 <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
622 available from <http://www.tldp.org/docs.html#howto>.
624 Note: if you just want your box to act as an SMB *server* and make
625 files and printing services available to Windows clients (which need
626 to have a TCP/IP stack), you don't need to say Y here; you can use
627 the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
630 General information about how to connect Linux, Windows machines and
631 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
633 To compile the SMB support as a module, choose M here:
634 the module will be called smbfs. Most people say N, however.
636 config SMB_NLS_DEFAULT
637 bool "Use a default NLS"
640 Enabling this will make smbfs use nls translations by default. You
641 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
642 settings and you need to give the default nls for the SMB server as
643 CONFIG_SMB_NLS_REMOTE.
645 The nls settings can be changed at mount time, if your smbmount
646 supports that, using the codepage and iocharset parameters.
648 smbmount from samba 2.2.0 or later supports this.
650 config SMB_NLS_REMOTE
651 string "Default Remote NLS Option"
652 depends on SMB_NLS_DEFAULT
655 This setting allows you to specify a default value for which
656 codepage the server uses. If this field is left blank no
657 translations will be done by default. The local codepage/charset
658 default to CONFIG_NLS_DEFAULT.
660 The nls settings can be changed at mount time, if your smbmount
661 supports that, using the codepage and iocharset parameters.
663 smbmount from samba 2.2.0 or later supports this.
665 source "fs/cifs/Kconfig"
668 tristate "NCP file system support (to mount NetWare volumes)"
669 depends on IPX!=n || INET
671 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
672 used by Novell NetWare clients to talk to file servers. It is to
673 IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
674 to mount NetWare file server volumes and to access them just like
675 any other Unix directory. For details, please read the file
676 <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
677 the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
679 You do not have to say Y here if you want your Linux box to act as a
680 file *server* for Novell NetWare clients.
682 General information about how to connect Linux, Windows machines and
683 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
685 To compile this as a module, choose M here: the module will be called
686 ncpfs. Say N unless you are connected to a Novell network.
688 source "fs/ncpfs/Kconfig"
691 tristate "Coda file system support (advanced network fs)"
694 Coda is an advanced network file system, similar to NFS in that it
695 enables you to mount file systems of a remote server and access them
696 with regular Unix commands as if they were sitting on your hard
697 disk. Coda has several advantages over NFS: support for
698 disconnected operation (e.g. for laptops), read/write server
699 replication, security model for authentication and encryption,
700 persistent client caches and write back caching.
702 If you say Y here, your Linux box will be able to act as a Coda
703 *client*. You will need user level code as well, both for the
704 client and server. Servers are currently user level, i.e. they need
705 no kernel support. Please read
706 <file:Documentation/filesystems/coda.txt> and check out the Coda
707 home page <http://www.coda.cs.cmu.edu/>.
709 To compile the coda client support as a module, choose M here: the
710 module will be called coda.
713 tristate "Andrew File System support (AFS) (EXPERIMENTAL)"
714 depends on INET && EXPERIMENTAL
717 If you say Y here, you will get an experimental Andrew File System
718 driver. It currently only supports unsecured read-only AFS access.
720 See <file:Documentation/filesystems/afs.txt> for more information.
725 bool "AFS dynamic debugging"
728 Say Y here to make runtime controllable debugging messages appear.
730 See <file:Documentation/filesystems/afs.txt> for more information.
735 tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
736 depends on INET && NET_9P && EXPERIMENTAL
738 If you say Y here, you will get experimental support for
739 Plan 9 resource sharing via the 9P2000 protocol.
741 See <http://v9fs.sf.net> for more information.
745 endif # NETWORK_FILESYSTEMS
748 menu "Partition Types"
750 source "fs/partitions/Kconfig"
755 source "fs/nls/Kconfig"
756 source "fs/dlm/Kconfig"