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"
226 tristate "UFS file system support (read only)"
229 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
230 OpenBSD and NeXTstep) use a file system called UFS. Some System V
231 Unixes can create and mount hard disk partitions and diskettes using
232 this file system as well. Saying Y here will allow you to read from
233 these partitions; if you also want to write to them, say Y to the
234 experimental "UFS file system write support", below. Please read the
235 file <file:Documentation/filesystems/ufs.txt> for more information.
237 The recently released UFS2 variant (used in FreeBSD 5.x) is
240 Note that this option is generally not needed for floppies, since a
241 good portable way to transport files and directories between unixes
242 (and even other operating systems) is given by the tar program ("man
243 tar" or preferably "info tar").
245 When accessing NeXTstep files, you may need to convert them from the
246 NeXT character set to the Latin1 character set; use the program
247 recode ("info recode") for this purpose.
249 To compile the UFS file system support as a module, choose M here: the
250 module will be called ufs.
252 If you haven't heard about all of this before, it's safe to say N.
255 bool "UFS file system write support (DANGEROUS)"
256 depends on UFS_FS && EXPERIMENTAL
258 Say Y here if you want to try writing to UFS partitions. This is
259 experimental, so you should back up your UFS partitions beforehand.
265 If you are experiencing any problems with the UFS filesystem, say
266 Y here. This will result in _many_ additional debugging messages to be
267 written to the system log.
269 endif # MISC_FILESYSTEMS
271 menuconfig NETWORK_FILESYSTEMS
272 bool "Network File Systems"
276 Say Y here to get to see options for network filesystems and
277 filesystem-related networking code, such as NFS daemon and
278 RPCSEC security modules.
280 This option alone does not add any kernel code.
282 If you say N, all options in this submenu will be skipped and
283 disabled; if unsure, say Y here.
285 if NETWORK_FILESYSTEMS
288 tristate "NFS client support"
292 select NFS_ACL_SUPPORT if NFS_V3_ACL
294 Choose Y here if you want to access files residing on other
295 computers using Sun's Network File System protocol. To compile
296 this file system support as a module, choose M here: the module
299 To mount file systems exported by NFS servers, you also need to
300 install the user space mount.nfs command which can be found in
301 the Linux nfs-utils package, available from http://linux-nfs.org/.
302 Information about using the mount command is available in the
303 mount(8) man page. More detail about the Linux NFS client
304 implementation is available via the nfs(5) man page.
306 Below you can choose which versions of the NFS protocol are
307 available in the kernel to mount NFS servers. Support for NFS
308 version 2 (RFC 1094) is always available when NFS_FS is selected.
310 To configure a system which mounts its root file system via NFS
311 at boot time, say Y here, select "Kernel level IP
312 autoconfiguration" in the NETWORK menu, and select "Root file
313 system on NFS" below. You cannot compile this file system as a
319 bool "NFS client support for NFS version 3"
322 This option enables support for version 3 of the NFS protocol
323 (RFC 1813) in the kernel's NFS client.
328 bool "NFS client support for the NFSv3 ACL protocol extension"
331 Some NFS servers support an auxiliary NFSv3 ACL protocol that
332 Sun added to Solaris but never became an official part of the
333 NFS version 3 protocol. This protocol extension allows
334 applications on NFS clients to manipulate POSIX Access Control
335 Lists on files residing on NFS servers. NFS servers enforce
336 ACLs on local files whether this protocol is available or not.
338 Choose Y here if your NFS server supports the Solaris NFSv3 ACL
339 protocol extension and you want your NFS client to allow
340 applications to access and modify ACLs on files on the server.
342 Most NFS servers don't support the Solaris NFSv3 ACL protocol
343 extension. You can choose N here or specify the "noacl" mount
344 option to prevent your NFS client from trying to use the NFSv3
350 bool "NFS client support for NFS version 4 (EXPERIMENTAL)"
351 depends on NFS_FS && EXPERIMENTAL
352 select RPCSEC_GSS_KRB5
354 This option enables support for version 4 of the NFS protocol
355 (RFC 3530) in the kernel's NFS client.
357 To mount NFS servers using NFSv4, you also need to install user
358 space programs which can be found in the Linux nfs-utils package,
359 available from http://linux-nfs.org/.
364 bool "Root file system on NFS"
365 depends on NFS_FS=y && IP_PNP
367 If you want your system to mount its root file system via NFS,
368 choose Y here. This is common practice for managing systems
369 without local permanent storage. For details, read
370 <file:Documentation/filesystems/nfsroot.txt>.
372 Most people say N here.
375 tristate "NFS server support"
380 select NFS_ACL_SUPPORT if NFSD_V2_ACL
382 Choose Y here if you want to allow other computers to access
383 files residing on this system using Sun's Network File System
384 protocol. To compile the NFS server support as a module,
385 choose M here: the module will be called nfsd.
387 You may choose to use a user-space NFS server instead, in which
388 case you can choose N here.
390 To export local file systems using NFS, you also need to install
391 user space programs which can be found in the Linux nfs-utils
392 package, available from http://linux-nfs.org/. More detail about
393 the Linux NFS server implementation is available via the
396 Below you can choose which versions of the NFS protocol are
397 available to clients mounting the NFS server on this system.
398 Support for NFS version 2 (RFC 1094) is always available when
399 CONFIG_NFSD is selected.
408 bool "NFS server support for NFS version 3"
411 This option enables support in your system's NFS server for
412 version 3 of the NFS protocol (RFC 1813).
417 bool "NFS server support for the NFSv3 ACL protocol extension"
421 Solaris NFS servers support an auxiliary NFSv3 ACL protocol that
422 never became an official part of the NFS version 3 protocol.
423 This protocol extension allows applications on NFS clients to
424 manipulate POSIX Access Control Lists on files residing on NFS
425 servers. NFS servers enforce POSIX ACLs on local files whether
426 this protocol is available or not.
428 This option enables support in your system's NFS server for the
429 NFSv3 ACL protocol extension allowing NFS clients to manipulate
430 POSIX ACLs on files exported by your system's NFS server. NFS
431 clients which support the Solaris NFSv3 ACL protocol can then
432 access and modify ACLs on your NFS server.
434 To store ACLs on your NFS server, you also need to enable ACL-
435 related CONFIG options for your local file systems of choice.
440 bool "NFS server support for NFS version 4 (EXPERIMENTAL)"
441 depends on NFSD && PROC_FS && EXPERIMENTAL
444 select RPCSEC_GSS_KRB5
446 This option enables support in your system's NFS server for
447 version 4 of the NFS protocol (RFC 3530).
449 To export files using NFSv4, you need to install additional user
450 space programs which can be found in the Linux nfs-utils package,
451 available from http://linux-nfs.org/.
460 depends on NFSD_V3 || NFS_V3
466 config NFS_ACL_SUPPORT
472 depends on NFSD || NFS_FS
481 config SUNRPC_XPRT_RDMA
483 depends on SUNRPC && INFINIBAND && EXPERIMENTAL
484 default SUNRPC && INFINIBAND
486 This option enables an RPC client transport capability that
487 allows the NFS client to mount servers via an RDMA-enabled
490 To compile RPC client RDMA transport support as a module,
491 choose M here: the module will be called xprtrdma.
495 config SUNRPC_REGISTER_V4
496 bool "Register local RPC services via rpcbind v4 (EXPERIMENTAL)"
497 depends on SUNRPC && EXPERIMENTAL
500 Sun added support for registering RPC services at an IPv6
501 address by creating two new versions of the rpcbind protocol
504 This option enables support in the kernel RPC server for
505 registering kernel RPC services via version 4 of the rpcbind
506 protocol. If you enable this option, you must run a portmapper
507 daemon that supports rpcbind protocol version 4.
509 Serving NFS over IPv6 from knfsd (the kernel's NFS server)
510 requires that you enable this option and use a portmapper that
511 supports rpcbind version 4.
513 If unsure, say N to get traditional behavior (register kernel
514 RPC services using only rpcbind version 2). Distributions
515 using the legacy Linux portmapper daemon must say N here.
517 config RPCSEC_GSS_KRB5
518 tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
519 depends on SUNRPC && EXPERIMENTAL
526 Choose Y here to enable Secure RPC using the Kerberos version 5
527 GSS-API mechanism (RFC 1964).
529 Secure RPC calls with Kerberos require an auxiliary user-space
530 daemon which may be found in the Linux nfs-utils package
531 available from http://linux-nfs.org/. In addition, user-space
532 Kerberos support should be installed.
536 config RPCSEC_GSS_SPKM3
537 tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
538 depends on SUNRPC && EXPERIMENTAL
546 Choose Y here to enable Secure RPC using the SPKM3 public key
547 GSS-API mechansim (RFC 2025).
549 Secure RPC calls with SPKM3 require an auxiliary userspace
550 daemon which may be found in the Linux nfs-utils package
551 available from http://linux-nfs.org/.
556 tristate "SMB file system support (OBSOLETE, please use CIFS)"
560 SMB (Server Message Block) is the protocol Windows for Workgroups
561 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
562 files and printers over local networks. Saying Y here allows you to
563 mount their file systems (often called "shares" in this context) and
564 access them just like any other Unix directory. Currently, this
565 works only if the Windows machines use TCP/IP as the underlying
566 transport protocol, and not NetBEUI. For details, read
567 <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
568 available from <http://www.tldp.org/docs.html#howto>.
570 Note: if you just want your box to act as an SMB *server* and make
571 files and printing services available to Windows clients (which need
572 to have a TCP/IP stack), you don't need to say Y here; you can use
573 the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
576 General information about how to connect Linux, Windows machines and
577 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
579 To compile the SMB support as a module, choose M here:
580 the module will be called smbfs. Most people say N, however.
582 config SMB_NLS_DEFAULT
583 bool "Use a default NLS"
586 Enabling this will make smbfs use nls translations by default. You
587 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
588 settings and you need to give the default nls for the SMB server as
589 CONFIG_SMB_NLS_REMOTE.
591 The nls settings can be changed at mount time, if your smbmount
592 supports that, using the codepage and iocharset parameters.
594 smbmount from samba 2.2.0 or later supports this.
596 config SMB_NLS_REMOTE
597 string "Default Remote NLS Option"
598 depends on SMB_NLS_DEFAULT
601 This setting allows you to specify a default value for which
602 codepage the server uses. If this field is left blank no
603 translations will be done by default. The local codepage/charset
604 default to CONFIG_NLS_DEFAULT.
606 The nls settings can be changed at mount time, if your smbmount
607 supports that, using the codepage and iocharset parameters.
609 smbmount from samba 2.2.0 or later supports this.
611 source "fs/cifs/Kconfig"
614 tristate "NCP file system support (to mount NetWare volumes)"
615 depends on IPX!=n || INET
617 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
618 used by Novell NetWare clients to talk to file servers. It is to
619 IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
620 to mount NetWare file server volumes and to access them just like
621 any other Unix directory. For details, please read the file
622 <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
623 the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
625 You do not have to say Y here if you want your Linux box to act as a
626 file *server* for Novell NetWare clients.
628 General information about how to connect Linux, Windows machines and
629 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
631 To compile this as a module, choose M here: the module will be called
632 ncpfs. Say N unless you are connected to a Novell network.
634 source "fs/ncpfs/Kconfig"
637 tristate "Coda file system support (advanced network fs)"
640 Coda is an advanced network file system, similar to NFS in that it
641 enables you to mount file systems of a remote server and access them
642 with regular Unix commands as if they were sitting on your hard
643 disk. Coda has several advantages over NFS: support for
644 disconnected operation (e.g. for laptops), read/write server
645 replication, security model for authentication and encryption,
646 persistent client caches and write back caching.
648 If you say Y here, your Linux box will be able to act as a Coda
649 *client*. You will need user level code as well, both for the
650 client and server. Servers are currently user level, i.e. they need
651 no kernel support. Please read
652 <file:Documentation/filesystems/coda.txt> and check out the Coda
653 home page <http://www.coda.cs.cmu.edu/>.
655 To compile the coda client support as a module, choose M here: the
656 module will be called coda.
659 tristate "Andrew File System support (AFS) (EXPERIMENTAL)"
660 depends on INET && EXPERIMENTAL
663 If you say Y here, you will get an experimental Andrew File System
664 driver. It currently only supports unsecured read-only AFS access.
666 See <file:Documentation/filesystems/afs.txt> for more information.
671 bool "AFS dynamic debugging"
674 Say Y here to make runtime controllable debugging messages appear.
676 See <file:Documentation/filesystems/afs.txt> for more information.
681 tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
682 depends on INET && NET_9P && EXPERIMENTAL
684 If you say Y here, you will get experimental support for
685 Plan 9 resource sharing via the 9P2000 protocol.
687 See <http://v9fs.sf.net> for more information.
691 endif # NETWORK_FILESYSTEMS
694 menu "Partition Types"
696 source "fs/partitions/Kconfig"
701 source "fs/nls/Kconfig"
702 source "fs/dlm/Kconfig"