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"
222 source "fs/romfs/Kconfig"
225 tristate "System V/Xenix/V7/Coherent file system support"
228 SCO, Xenix and Coherent are commercial Unix systems for Intel
229 machines, and Version 7 was used on the DEC PDP-11. Saying Y
230 here would allow you to read from their floppies and hard disk
233 If you have floppies or hard disk partitions like that, it is likely
234 that they contain binaries from those other Unix systems; in order
235 to run these binaries, you will want to install linux-abi which is
236 a set of kernel modules that lets you run SCO, Xenix, Wyse,
237 UnixWare, Dell Unix and System V programs under Linux. It is
238 available via FTP (user: ftp) from
239 <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
240 NOTE: that will work only for binaries from Intel-based systems;
241 PDP ones will have to wait until somebody ports Linux to -11 ;-)
243 If you only intend to mount files from some other Unix over the
244 network using NFS, you don't need the System V file system support
245 (but you need NFS file system support obviously).
247 Note that this option is generally not needed for floppies, since a
248 good portable way to transport files and directories between unixes
249 (and even other operating systems) is given by the tar program ("man
250 tar" or preferably "info tar"). Note also that this option has
251 nothing whatsoever to do with the option "System V IPC". Read about
252 the System V file system in
253 <file:Documentation/filesystems/sysv-fs.txt>.
254 Saying Y here will enlarge your kernel by about 27 KB.
256 To compile this as a module, choose M here: the module will be called
259 If you haven't heard about all of this before, it's safe to say N.
263 tristate "UFS file system support (read only)"
266 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
267 OpenBSD and NeXTstep) use a file system called UFS. Some System V
268 Unixes can create and mount hard disk partitions and diskettes using
269 this file system as well. Saying Y here will allow you to read from
270 these partitions; if you also want to write to them, say Y to the
271 experimental "UFS file system write support", below. Please read the
272 file <file:Documentation/filesystems/ufs.txt> for more information.
274 The recently released UFS2 variant (used in FreeBSD 5.x) is
277 Note that this option is generally not needed for floppies, since a
278 good portable way to transport files and directories between unixes
279 (and even other operating systems) is given by the tar program ("man
280 tar" or preferably "info tar").
282 When accessing NeXTstep files, you may need to convert them from the
283 NeXT character set to the Latin1 character set; use the program
284 recode ("info recode") for this purpose.
286 To compile the UFS file system support as a module, choose M here: the
287 module will be called ufs.
289 If you haven't heard about all of this before, it's safe to say N.
292 bool "UFS file system write support (DANGEROUS)"
293 depends on UFS_FS && EXPERIMENTAL
295 Say Y here if you want to try writing to UFS partitions. This is
296 experimental, so you should back up your UFS partitions beforehand.
302 If you are experiencing any problems with the UFS filesystem, say
303 Y here. This will result in _many_ additional debugging messages to be
304 written to the system log.
306 endif # MISC_FILESYSTEMS
308 menuconfig NETWORK_FILESYSTEMS
309 bool "Network File Systems"
313 Say Y here to get to see options for network filesystems and
314 filesystem-related networking code, such as NFS daemon and
315 RPCSEC security modules.
317 This option alone does not add any kernel code.
319 If you say N, all options in this submenu will be skipped and
320 disabled; if unsure, say Y here.
322 if NETWORK_FILESYSTEMS
325 tristate "NFS client support"
329 select NFS_ACL_SUPPORT if NFS_V3_ACL
331 Choose Y here if you want to access files residing on other
332 computers using Sun's Network File System protocol. To compile
333 this file system support as a module, choose M here: the module
336 To mount file systems exported by NFS servers, you also need to
337 install the user space mount.nfs command which can be found in
338 the Linux nfs-utils package, available from http://linux-nfs.org/.
339 Information about using the mount command is available in the
340 mount(8) man page. More detail about the Linux NFS client
341 implementation is available via the nfs(5) man page.
343 Below you can choose which versions of the NFS protocol are
344 available in the kernel to mount NFS servers. Support for NFS
345 version 2 (RFC 1094) is always available when NFS_FS is selected.
347 To configure a system which mounts its root file system via NFS
348 at boot time, say Y here, select "Kernel level IP
349 autoconfiguration" in the NETWORK menu, and select "Root file
350 system on NFS" below. You cannot compile this file system as a
356 bool "NFS client support for NFS version 3"
359 This option enables support for version 3 of the NFS protocol
360 (RFC 1813) in the kernel's NFS client.
365 bool "NFS client support for the NFSv3 ACL protocol extension"
368 Some NFS servers support an auxiliary NFSv3 ACL protocol that
369 Sun added to Solaris but never became an official part of the
370 NFS version 3 protocol. This protocol extension allows
371 applications on NFS clients to manipulate POSIX Access Control
372 Lists on files residing on NFS servers. NFS servers enforce
373 ACLs on local files whether this protocol is available or not.
375 Choose Y here if your NFS server supports the Solaris NFSv3 ACL
376 protocol extension and you want your NFS client to allow
377 applications to access and modify ACLs on files on the server.
379 Most NFS servers don't support the Solaris NFSv3 ACL protocol
380 extension. You can choose N here or specify the "noacl" mount
381 option to prevent your NFS client from trying to use the NFSv3
387 bool "NFS client support for NFS version 4 (EXPERIMENTAL)"
388 depends on NFS_FS && EXPERIMENTAL
389 select RPCSEC_GSS_KRB5
391 This option enables support for version 4 of the NFS protocol
392 (RFC 3530) in the kernel's NFS client.
394 To mount NFS servers using NFSv4, you also need to install user
395 space programs which can be found in the Linux nfs-utils package,
396 available from http://linux-nfs.org/.
401 bool "Root file system on NFS"
402 depends on NFS_FS=y && IP_PNP
404 If you want your system to mount its root file system via NFS,
405 choose Y here. This is common practice for managing systems
406 without local permanent storage. For details, read
407 <file:Documentation/filesystems/nfsroot.txt>.
409 Most people say N here.
412 tristate "NFS server support"
417 select NFS_ACL_SUPPORT if NFSD_V2_ACL
419 Choose Y here if you want to allow other computers to access
420 files residing on this system using Sun's Network File System
421 protocol. To compile the NFS server support as a module,
422 choose M here: the module will be called nfsd.
424 You may choose to use a user-space NFS server instead, in which
425 case you can choose N here.
427 To export local file systems using NFS, you also need to install
428 user space programs which can be found in the Linux nfs-utils
429 package, available from http://linux-nfs.org/. More detail about
430 the Linux NFS server implementation is available via the
433 Below you can choose which versions of the NFS protocol are
434 available to clients mounting the NFS server on this system.
435 Support for NFS version 2 (RFC 1094) is always available when
436 CONFIG_NFSD is selected.
445 bool "NFS server support for NFS version 3"
448 This option enables support in your system's NFS server for
449 version 3 of the NFS protocol (RFC 1813).
454 bool "NFS server support for the NFSv3 ACL protocol extension"
458 Solaris NFS servers support an auxiliary NFSv3 ACL protocol that
459 never became an official part of the NFS version 3 protocol.
460 This protocol extension allows applications on NFS clients to
461 manipulate POSIX Access Control Lists on files residing on NFS
462 servers. NFS servers enforce POSIX ACLs on local files whether
463 this protocol is available or not.
465 This option enables support in your system's NFS server for the
466 NFSv3 ACL protocol extension allowing NFS clients to manipulate
467 POSIX ACLs on files exported by your system's NFS server. NFS
468 clients which support the Solaris NFSv3 ACL protocol can then
469 access and modify ACLs on your NFS server.
471 To store ACLs on your NFS server, you also need to enable ACL-
472 related CONFIG options for your local file systems of choice.
477 bool "NFS server support for NFS version 4 (EXPERIMENTAL)"
478 depends on NFSD && PROC_FS && EXPERIMENTAL
481 select RPCSEC_GSS_KRB5
483 This option enables support in your system's NFS server for
484 version 4 of the NFS protocol (RFC 3530).
486 To export files using NFSv4, you need to install additional user
487 space programs which can be found in the Linux nfs-utils package,
488 available from http://linux-nfs.org/.
497 depends on NFSD_V3 || NFS_V3
503 config NFS_ACL_SUPPORT
509 depends on NFSD || NFS_FS
518 config SUNRPC_XPRT_RDMA
520 depends on SUNRPC && INFINIBAND && EXPERIMENTAL
521 default SUNRPC && INFINIBAND
523 This option enables an RPC client transport capability that
524 allows the NFS client to mount servers via an RDMA-enabled
527 To compile RPC client RDMA transport support as a module,
528 choose M here: the module will be called xprtrdma.
532 config SUNRPC_REGISTER_V4
533 bool "Register local RPC services via rpcbind v4 (EXPERIMENTAL)"
534 depends on SUNRPC && EXPERIMENTAL
537 Sun added support for registering RPC services at an IPv6
538 address by creating two new versions of the rpcbind protocol
541 This option enables support in the kernel RPC server for
542 registering kernel RPC services via version 4 of the rpcbind
543 protocol. If you enable this option, you must run a portmapper
544 daemon that supports rpcbind protocol version 4.
546 Serving NFS over IPv6 from knfsd (the kernel's NFS server)
547 requires that you enable this option and use a portmapper that
548 supports rpcbind version 4.
550 If unsure, say N to get traditional behavior (register kernel
551 RPC services using only rpcbind version 2). Distributions
552 using the legacy Linux portmapper daemon must say N here.
554 config RPCSEC_GSS_KRB5
555 tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
556 depends on SUNRPC && EXPERIMENTAL
563 Choose Y here to enable Secure RPC using the Kerberos version 5
564 GSS-API mechanism (RFC 1964).
566 Secure RPC calls with Kerberos require an auxiliary user-space
567 daemon which may be found in the Linux nfs-utils package
568 available from http://linux-nfs.org/. In addition, user-space
569 Kerberos support should be installed.
573 config RPCSEC_GSS_SPKM3
574 tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
575 depends on SUNRPC && EXPERIMENTAL
583 Choose Y here to enable Secure RPC using the SPKM3 public key
584 GSS-API mechansim (RFC 2025).
586 Secure RPC calls with SPKM3 require an auxiliary userspace
587 daemon which may be found in the Linux nfs-utils package
588 available from http://linux-nfs.org/.
593 tristate "SMB file system support (OBSOLETE, please use CIFS)"
597 SMB (Server Message Block) is the protocol Windows for Workgroups
598 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
599 files and printers over local networks. Saying Y here allows you to
600 mount their file systems (often called "shares" in this context) and
601 access them just like any other Unix directory. Currently, this
602 works only if the Windows machines use TCP/IP as the underlying
603 transport protocol, and not NetBEUI. For details, read
604 <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
605 available from <http://www.tldp.org/docs.html#howto>.
607 Note: if you just want your box to act as an SMB *server* and make
608 files and printing services available to Windows clients (which need
609 to have a TCP/IP stack), you don't need to say Y here; you can use
610 the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
613 General information about how to connect Linux, Windows machines and
614 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
616 To compile the SMB support as a module, choose M here:
617 the module will be called smbfs. Most people say N, however.
619 config SMB_NLS_DEFAULT
620 bool "Use a default NLS"
623 Enabling this will make smbfs use nls translations by default. You
624 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
625 settings and you need to give the default nls for the SMB server as
626 CONFIG_SMB_NLS_REMOTE.
628 The nls settings can be changed at mount time, if your smbmount
629 supports that, using the codepage and iocharset parameters.
631 smbmount from samba 2.2.0 or later supports this.
633 config SMB_NLS_REMOTE
634 string "Default Remote NLS Option"
635 depends on SMB_NLS_DEFAULT
638 This setting allows you to specify a default value for which
639 codepage the server uses. If this field is left blank no
640 translations will be done by default. The local codepage/charset
641 default to CONFIG_NLS_DEFAULT.
643 The nls settings can be changed at mount time, if your smbmount
644 supports that, using the codepage and iocharset parameters.
646 smbmount from samba 2.2.0 or later supports this.
648 source "fs/cifs/Kconfig"
651 tristate "NCP file system support (to mount NetWare volumes)"
652 depends on IPX!=n || INET
654 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
655 used by Novell NetWare clients to talk to file servers. It is to
656 IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
657 to mount NetWare file server volumes and to access them just like
658 any other Unix directory. For details, please read the file
659 <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
660 the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
662 You do not have to say Y here if you want your Linux box to act as a
663 file *server* for Novell NetWare clients.
665 General information about how to connect Linux, Windows machines and
666 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
668 To compile this as a module, choose M here: the module will be called
669 ncpfs. Say N unless you are connected to a Novell network.
671 source "fs/ncpfs/Kconfig"
674 tristate "Coda file system support (advanced network fs)"
677 Coda is an advanced network file system, similar to NFS in that it
678 enables you to mount file systems of a remote server and access them
679 with regular Unix commands as if they were sitting on your hard
680 disk. Coda has several advantages over NFS: support for
681 disconnected operation (e.g. for laptops), read/write server
682 replication, security model for authentication and encryption,
683 persistent client caches and write back caching.
685 If you say Y here, your Linux box will be able to act as a Coda
686 *client*. You will need user level code as well, both for the
687 client and server. Servers are currently user level, i.e. they need
688 no kernel support. Please read
689 <file:Documentation/filesystems/coda.txt> and check out the Coda
690 home page <http://www.coda.cs.cmu.edu/>.
692 To compile the coda client support as a module, choose M here: the
693 module will be called coda.
696 tristate "Andrew File System support (AFS) (EXPERIMENTAL)"
697 depends on INET && EXPERIMENTAL
700 If you say Y here, you will get an experimental Andrew File System
701 driver. It currently only supports unsecured read-only AFS access.
703 See <file:Documentation/filesystems/afs.txt> for more information.
708 bool "AFS dynamic debugging"
711 Say Y here to make runtime controllable debugging messages appear.
713 See <file:Documentation/filesystems/afs.txt> for more information.
718 tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
719 depends on INET && NET_9P && EXPERIMENTAL
721 If you say Y here, you will get experimental support for
722 Plan 9 resource sharing via the 9P2000 protocol.
724 See <http://v9fs.sf.net> for more information.
728 endif # NETWORK_FILESYSTEMS
731 menu "Partition Types"
733 source "fs/partitions/Kconfig"
738 source "fs/nls/Kconfig"
739 source "fs/dlm/Kconfig"