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"
223 source "fs/sysv/Kconfig"
224 source "fs/ufs/Kconfig"
226 endif # MISC_FILESYSTEMS
228 menuconfig NETWORK_FILESYSTEMS
229 bool "Network File Systems"
233 Say Y here to get to see options for network filesystems and
234 filesystem-related networking code, such as NFS daemon and
235 RPCSEC security modules.
237 This option alone does not add any kernel code.
239 If you say N, all options in this submenu will be skipped and
240 disabled; if unsure, say Y here.
242 if NETWORK_FILESYSTEMS
245 tristate "NFS client support"
249 select NFS_ACL_SUPPORT if NFS_V3_ACL
251 Choose Y here if you want to access files residing on other
252 computers using Sun's Network File System protocol. To compile
253 this file system support as a module, choose M here: the module
256 To mount file systems exported by NFS servers, you also need to
257 install the user space mount.nfs command which can be found in
258 the Linux nfs-utils package, available from http://linux-nfs.org/.
259 Information about using the mount command is available in the
260 mount(8) man page. More detail about the Linux NFS client
261 implementation is available via the nfs(5) man page.
263 Below you can choose which versions of the NFS protocol are
264 available in the kernel to mount NFS servers. Support for NFS
265 version 2 (RFC 1094) is always available when NFS_FS is selected.
267 To configure a system which mounts its root file system via NFS
268 at boot time, say Y here, select "Kernel level IP
269 autoconfiguration" in the NETWORK menu, and select "Root file
270 system on NFS" below. You cannot compile this file system as a
276 bool "NFS client support for NFS version 3"
279 This option enables support for version 3 of the NFS protocol
280 (RFC 1813) in the kernel's NFS client.
285 bool "NFS client support for the NFSv3 ACL protocol extension"
288 Some NFS servers support an auxiliary NFSv3 ACL protocol that
289 Sun added to Solaris but never became an official part of the
290 NFS version 3 protocol. This protocol extension allows
291 applications on NFS clients to manipulate POSIX Access Control
292 Lists on files residing on NFS servers. NFS servers enforce
293 ACLs on local files whether this protocol is available or not.
295 Choose Y here if your NFS server supports the Solaris NFSv3 ACL
296 protocol extension and you want your NFS client to allow
297 applications to access and modify ACLs on files on the server.
299 Most NFS servers don't support the Solaris NFSv3 ACL protocol
300 extension. You can choose N here or specify the "noacl" mount
301 option to prevent your NFS client from trying to use the NFSv3
307 bool "NFS client support for NFS version 4 (EXPERIMENTAL)"
308 depends on NFS_FS && EXPERIMENTAL
309 select RPCSEC_GSS_KRB5
311 This option enables support for version 4 of the NFS protocol
312 (RFC 3530) in the kernel's NFS client.
314 To mount NFS servers using NFSv4, you also need to install user
315 space programs which can be found in the Linux nfs-utils package,
316 available from http://linux-nfs.org/.
321 bool "Root file system on NFS"
322 depends on NFS_FS=y && IP_PNP
324 If you want your system to mount its root file system via NFS,
325 choose Y here. This is common practice for managing systems
326 without local permanent storage. For details, read
327 <file:Documentation/filesystems/nfsroot.txt>.
329 Most people say N here.
332 tristate "NFS server support"
337 select NFS_ACL_SUPPORT if NFSD_V2_ACL
339 Choose Y here if you want to allow other computers to access
340 files residing on this system using Sun's Network File System
341 protocol. To compile the NFS server support as a module,
342 choose M here: the module will be called nfsd.
344 You may choose to use a user-space NFS server instead, in which
345 case you can choose N here.
347 To export local file systems using NFS, you also need to install
348 user space programs which can be found in the Linux nfs-utils
349 package, available from http://linux-nfs.org/. More detail about
350 the Linux NFS server implementation is available via the
353 Below you can choose which versions of the NFS protocol are
354 available to clients mounting the NFS server on this system.
355 Support for NFS version 2 (RFC 1094) is always available when
356 CONFIG_NFSD is selected.
365 bool "NFS server support for NFS version 3"
368 This option enables support in your system's NFS server for
369 version 3 of the NFS protocol (RFC 1813).
374 bool "NFS server support for the NFSv3 ACL protocol extension"
378 Solaris NFS servers support an auxiliary NFSv3 ACL protocol that
379 never became an official part of the NFS version 3 protocol.
380 This protocol extension allows applications on NFS clients to
381 manipulate POSIX Access Control Lists on files residing on NFS
382 servers. NFS servers enforce POSIX ACLs on local files whether
383 this protocol is available or not.
385 This option enables support in your system's NFS server for the
386 NFSv3 ACL protocol extension allowing NFS clients to manipulate
387 POSIX ACLs on files exported by your system's NFS server. NFS
388 clients which support the Solaris NFSv3 ACL protocol can then
389 access and modify ACLs on your NFS server.
391 To store ACLs on your NFS server, you also need to enable ACL-
392 related CONFIG options for your local file systems of choice.
397 bool "NFS server support for NFS version 4 (EXPERIMENTAL)"
398 depends on NFSD && PROC_FS && EXPERIMENTAL
401 select RPCSEC_GSS_KRB5
403 This option enables support in your system's NFS server for
404 version 4 of the NFS protocol (RFC 3530).
406 To export files using NFSv4, you need to install additional user
407 space programs which can be found in the Linux nfs-utils package,
408 available from http://linux-nfs.org/.
417 depends on NFSD_V3 || NFS_V3
423 config NFS_ACL_SUPPORT
429 depends on NFSD || NFS_FS
438 config SUNRPC_XPRT_RDMA
440 depends on SUNRPC && INFINIBAND && EXPERIMENTAL
441 default SUNRPC && INFINIBAND
443 This option enables an RPC client transport capability that
444 allows the NFS client to mount servers via an RDMA-enabled
447 To compile RPC client RDMA transport support as a module,
448 choose M here: the module will be called xprtrdma.
452 config SUNRPC_REGISTER_V4
453 bool "Register local RPC services via rpcbind v4 (EXPERIMENTAL)"
454 depends on SUNRPC && EXPERIMENTAL
457 Sun added support for registering RPC services at an IPv6
458 address by creating two new versions of the rpcbind protocol
461 This option enables support in the kernel RPC server for
462 registering kernel RPC services via version 4 of the rpcbind
463 protocol. If you enable this option, you must run a portmapper
464 daemon that supports rpcbind protocol version 4.
466 Serving NFS over IPv6 from knfsd (the kernel's NFS server)
467 requires that you enable this option and use a portmapper that
468 supports rpcbind version 4.
470 If unsure, say N to get traditional behavior (register kernel
471 RPC services using only rpcbind version 2). Distributions
472 using the legacy Linux portmapper daemon must say N here.
474 config RPCSEC_GSS_KRB5
475 tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
476 depends on SUNRPC && EXPERIMENTAL
483 Choose Y here to enable Secure RPC using the Kerberos version 5
484 GSS-API mechanism (RFC 1964).
486 Secure RPC calls with Kerberos require an auxiliary user-space
487 daemon which may be found in the Linux nfs-utils package
488 available from http://linux-nfs.org/. In addition, user-space
489 Kerberos support should be installed.
493 config RPCSEC_GSS_SPKM3
494 tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
495 depends on SUNRPC && EXPERIMENTAL
503 Choose Y here to enable Secure RPC using the SPKM3 public key
504 GSS-API mechansim (RFC 2025).
506 Secure RPC calls with SPKM3 require an auxiliary userspace
507 daemon which may be found in the Linux nfs-utils package
508 available from http://linux-nfs.org/.
513 tristate "SMB file system support (OBSOLETE, please use CIFS)"
517 SMB (Server Message Block) is the protocol Windows for Workgroups
518 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
519 files and printers over local networks. Saying Y here allows you to
520 mount their file systems (often called "shares" in this context) and
521 access them just like any other Unix directory. Currently, this
522 works only if the Windows machines use TCP/IP as the underlying
523 transport protocol, and not NetBEUI. For details, read
524 <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
525 available from <http://www.tldp.org/docs.html#howto>.
527 Note: if you just want your box to act as an SMB *server* and make
528 files and printing services available to Windows clients (which need
529 to have a TCP/IP stack), you don't need to say Y here; you can use
530 the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
533 General information about how to connect Linux, Windows machines and
534 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
536 To compile the SMB support as a module, choose M here:
537 the module will be called smbfs. Most people say N, however.
539 config SMB_NLS_DEFAULT
540 bool "Use a default NLS"
543 Enabling this will make smbfs use nls translations by default. You
544 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
545 settings and you need to give the default nls for the SMB server as
546 CONFIG_SMB_NLS_REMOTE.
548 The nls settings can be changed at mount time, if your smbmount
549 supports that, using the codepage and iocharset parameters.
551 smbmount from samba 2.2.0 or later supports this.
553 config SMB_NLS_REMOTE
554 string "Default Remote NLS Option"
555 depends on SMB_NLS_DEFAULT
558 This setting allows you to specify a default value for which
559 codepage the server uses. If this field is left blank no
560 translations will be done by default. The local codepage/charset
561 default to CONFIG_NLS_DEFAULT.
563 The nls settings can be changed at mount time, if your smbmount
564 supports that, using the codepage and iocharset parameters.
566 smbmount from samba 2.2.0 or later supports this.
568 source "fs/cifs/Kconfig"
571 tristate "NCP file system support (to mount NetWare volumes)"
572 depends on IPX!=n || INET
574 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
575 used by Novell NetWare clients to talk to file servers. It is to
576 IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
577 to mount NetWare file server volumes and to access them just like
578 any other Unix directory. For details, please read the file
579 <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
580 the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
582 You do not have to say Y here if you want your Linux box to act as a
583 file *server* for Novell NetWare clients.
585 General information about how to connect Linux, Windows machines and
586 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
588 To compile this as a module, choose M here: the module will be called
589 ncpfs. Say N unless you are connected to a Novell network.
591 source "fs/ncpfs/Kconfig"
594 tristate "Coda file system support (advanced network fs)"
597 Coda is an advanced network file system, similar to NFS in that it
598 enables you to mount file systems of a remote server and access them
599 with regular Unix commands as if they were sitting on your hard
600 disk. Coda has several advantages over NFS: support for
601 disconnected operation (e.g. for laptops), read/write server
602 replication, security model for authentication and encryption,
603 persistent client caches and write back caching.
605 If you say Y here, your Linux box will be able to act as a Coda
606 *client*. You will need user level code as well, both for the
607 client and server. Servers are currently user level, i.e. they need
608 no kernel support. Please read
609 <file:Documentation/filesystems/coda.txt> and check out the Coda
610 home page <http://www.coda.cs.cmu.edu/>.
612 To compile the coda client support as a module, choose M here: the
613 module will be called coda.
616 tristate "Andrew File System support (AFS) (EXPERIMENTAL)"
617 depends on INET && EXPERIMENTAL
620 If you say Y here, you will get an experimental Andrew File System
621 driver. It currently only supports unsecured read-only AFS access.
623 See <file:Documentation/filesystems/afs.txt> for more information.
628 bool "AFS dynamic debugging"
631 Say Y here to make runtime controllable debugging messages appear.
633 See <file:Documentation/filesystems/afs.txt> for more information.
638 tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
639 depends on INET && NET_9P && EXPERIMENTAL
641 If you say Y here, you will get experimental support for
642 Plan 9 resource sharing via the 9P2000 protocol.
644 See <http://v9fs.sf.net> for more information.
648 endif # NETWORK_FILESYSTEMS
651 menu "Partition Types"
653 source "fs/partitions/Kconfig"
658 source "fs/nls/Kconfig"
659 source "fs/dlm/Kconfig"