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
244 source "fs/nfs/Kconfig"
247 tristate "NFS server support"
252 select NFS_ACL_SUPPORT if NFSD_V2_ACL
254 Choose Y here if you want to allow other computers to access
255 files residing on this system using Sun's Network File System
256 protocol. To compile the NFS server support as a module,
257 choose M here: the module will be called nfsd.
259 You may choose to use a user-space NFS server instead, in which
260 case you can choose N here.
262 To export local file systems using NFS, you also need to install
263 user space programs which can be found in the Linux nfs-utils
264 package, available from http://linux-nfs.org/. More detail about
265 the Linux NFS server implementation is available via the
268 Below you can choose which versions of the NFS protocol are
269 available to clients mounting the NFS server on this system.
270 Support for NFS version 2 (RFC 1094) is always available when
271 CONFIG_NFSD is selected.
280 bool "NFS server support for NFS version 3"
283 This option enables support in your system's NFS server for
284 version 3 of the NFS protocol (RFC 1813).
289 bool "NFS server support for the NFSv3 ACL protocol extension"
293 Solaris NFS servers support an auxiliary NFSv3 ACL protocol that
294 never became an official part of the NFS version 3 protocol.
295 This protocol extension allows applications on NFS clients to
296 manipulate POSIX Access Control Lists on files residing on NFS
297 servers. NFS servers enforce POSIX ACLs on local files whether
298 this protocol is available or not.
300 This option enables support in your system's NFS server for the
301 NFSv3 ACL protocol extension allowing NFS clients to manipulate
302 POSIX ACLs on files exported by your system's NFS server. NFS
303 clients which support the Solaris NFSv3 ACL protocol can then
304 access and modify ACLs on your NFS server.
306 To store ACLs on your NFS server, you also need to enable ACL-
307 related CONFIG options for your local file systems of choice.
312 bool "NFS server support for NFS version 4 (EXPERIMENTAL)"
313 depends on NFSD && PROC_FS && EXPERIMENTAL
316 select RPCSEC_GSS_KRB5
318 This option enables support in your system's NFS server for
319 version 4 of the NFS protocol (RFC 3530).
321 To export files using NFSv4, you need to install additional user
322 space programs which can be found in the Linux nfs-utils package,
323 available from http://linux-nfs.org/.
332 depends on NFSD_V3 || NFS_V3
338 config NFS_ACL_SUPPORT
344 depends on NFSD || NFS_FS
353 config SUNRPC_XPRT_RDMA
355 depends on SUNRPC && INFINIBAND && EXPERIMENTAL
356 default SUNRPC && INFINIBAND
358 This option enables an RPC client transport capability that
359 allows the NFS client to mount servers via an RDMA-enabled
362 To compile RPC client RDMA transport support as a module,
363 choose M here: the module will be called xprtrdma.
367 config SUNRPC_REGISTER_V4
368 bool "Register local RPC services via rpcbind v4 (EXPERIMENTAL)"
369 depends on SUNRPC && EXPERIMENTAL
372 Sun added support for registering RPC services at an IPv6
373 address by creating two new versions of the rpcbind protocol
376 This option enables support in the kernel RPC server for
377 registering kernel RPC services via version 4 of the rpcbind
378 protocol. If you enable this option, you must run a portmapper
379 daemon that supports rpcbind protocol version 4.
381 Serving NFS over IPv6 from knfsd (the kernel's NFS server)
382 requires that you enable this option and use a portmapper that
383 supports rpcbind version 4.
385 If unsure, say N to get traditional behavior (register kernel
386 RPC services using only rpcbind version 2). Distributions
387 using the legacy Linux portmapper daemon must say N here.
389 config RPCSEC_GSS_KRB5
390 tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
391 depends on SUNRPC && EXPERIMENTAL
398 Choose Y here to enable Secure RPC using the Kerberos version 5
399 GSS-API mechanism (RFC 1964).
401 Secure RPC calls with Kerberos require an auxiliary user-space
402 daemon which may be found in the Linux nfs-utils package
403 available from http://linux-nfs.org/. In addition, user-space
404 Kerberos support should be installed.
408 config RPCSEC_GSS_SPKM3
409 tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
410 depends on SUNRPC && EXPERIMENTAL
418 Choose Y here to enable Secure RPC using the SPKM3 public key
419 GSS-API mechansim (RFC 2025).
421 Secure RPC calls with SPKM3 require an auxiliary userspace
422 daemon which may be found in the Linux nfs-utils package
423 available from http://linux-nfs.org/.
428 tristate "SMB file system support (OBSOLETE, please use CIFS)"
432 SMB (Server Message Block) is the protocol Windows for Workgroups
433 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
434 files and printers over local networks. Saying Y here allows you to
435 mount their file systems (often called "shares" in this context) and
436 access them just like any other Unix directory. Currently, this
437 works only if the Windows machines use TCP/IP as the underlying
438 transport protocol, and not NetBEUI. For details, read
439 <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
440 available from <http://www.tldp.org/docs.html#howto>.
442 Note: if you just want your box to act as an SMB *server* and make
443 files and printing services available to Windows clients (which need
444 to have a TCP/IP stack), you don't need to say Y here; you can use
445 the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
448 General information about how to connect Linux, Windows machines and
449 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
451 To compile the SMB support as a module, choose M here:
452 the module will be called smbfs. Most people say N, however.
454 config SMB_NLS_DEFAULT
455 bool "Use a default NLS"
458 Enabling this will make smbfs use nls translations by default. You
459 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
460 settings and you need to give the default nls for the SMB server as
461 CONFIG_SMB_NLS_REMOTE.
463 The nls settings can be changed at mount time, if your smbmount
464 supports that, using the codepage and iocharset parameters.
466 smbmount from samba 2.2.0 or later supports this.
468 config SMB_NLS_REMOTE
469 string "Default Remote NLS Option"
470 depends on SMB_NLS_DEFAULT
473 This setting allows you to specify a default value for which
474 codepage the server uses. If this field is left blank no
475 translations will be done by default. The local codepage/charset
476 default to CONFIG_NLS_DEFAULT.
478 The nls settings can be changed at mount time, if your smbmount
479 supports that, using the codepage and iocharset parameters.
481 smbmount from samba 2.2.0 or later supports this.
483 source "fs/cifs/Kconfig"
486 tristate "NCP file system support (to mount NetWare volumes)"
487 depends on IPX!=n || INET
489 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
490 used by Novell NetWare clients to talk to file servers. It is to
491 IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
492 to mount NetWare file server volumes and to access them just like
493 any other Unix directory. For details, please read the file
494 <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
495 the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
497 You do not have to say Y here if you want your Linux box to act as a
498 file *server* for Novell NetWare clients.
500 General information about how to connect Linux, Windows machines and
501 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
503 To compile this as a module, choose M here: the module will be called
504 ncpfs. Say N unless you are connected to a Novell network.
506 source "fs/ncpfs/Kconfig"
509 tristate "Coda file system support (advanced network fs)"
512 Coda is an advanced network file system, similar to NFS in that it
513 enables you to mount file systems of a remote server and access them
514 with regular Unix commands as if they were sitting on your hard
515 disk. Coda has several advantages over NFS: support for
516 disconnected operation (e.g. for laptops), read/write server
517 replication, security model for authentication and encryption,
518 persistent client caches and write back caching.
520 If you say Y here, your Linux box will be able to act as a Coda
521 *client*. You will need user level code as well, both for the
522 client and server. Servers are currently user level, i.e. they need
523 no kernel support. Please read
524 <file:Documentation/filesystems/coda.txt> and check out the Coda
525 home page <http://www.coda.cs.cmu.edu/>.
527 To compile the coda client support as a module, choose M here: the
528 module will be called coda.
531 tristate "Andrew File System support (AFS) (EXPERIMENTAL)"
532 depends on INET && EXPERIMENTAL
535 If you say Y here, you will get an experimental Andrew File System
536 driver. It currently only supports unsecured read-only AFS access.
538 See <file:Documentation/filesystems/afs.txt> for more information.
543 bool "AFS dynamic debugging"
546 Say Y here to make runtime controllable debugging messages appear.
548 See <file:Documentation/filesystems/afs.txt> for more information.
553 tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
554 depends on INET && NET_9P && EXPERIMENTAL
556 If you say Y here, you will get experimental support for
557 Plan 9 resource sharing via the 9P2000 protocol.
559 See <http://v9fs.sf.net> for more information.
563 endif # NETWORK_FILESYSTEMS
566 menu "Partition Types"
568 source "fs/partitions/Kconfig"
573 source "fs/nls/Kconfig"
574 source "fs/dlm/Kconfig"