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"
218 tristate "SquashFS 4.0 - Squashed file system support"
222 Saying Y here includes support for SquashFS 4.0 (a Compressed
223 Read-Only File System). Squashfs is a highly compressed read-only
224 filesystem for Linux. It uses zlib compression to compress both
225 files, inodes and directories. Inodes in the system are very small
226 and all blocks are packed to minimise data overhead. Block sizes
227 greater than 4K are supported up to a maximum of 1 Mbytes (default
228 block size 128K). SquashFS 4.0 supports 64 bit filesystems and files
229 (larger than 4GB), full uid/gid information, hard links and
232 Squashfs is intended for general read-only filesystem use, for
233 archival use (i.e. in cases where a .tar.gz file may be used), and in
234 embedded systems where low overhead is needed. Further information
235 and tools are available from http://squashfs.sourceforge.net.
237 If you want to compile this as a module ( = code which can be
238 inserted in and removed from the running kernel whenever you want),
239 say M here and read <file:Documentation/modules.txt>. The module
240 will be called squashfs. Note that the root file system (the one
241 containing the directory /) cannot be compiled as a module.
245 config SQUASHFS_EMBEDDED
247 bool "Additional option for memory-constrained systems"
251 Saying Y here allows you to specify cache size.
255 config SQUASHFS_FRAGMENT_CACHE_SIZE
256 int "Number of fragments cached" if SQUASHFS_EMBEDDED
260 By default SquashFS caches the last 3 fragments read from
261 the filesystem. Increasing this amount may mean SquashFS
262 has to re-read fragments less often from disk, at the expense
263 of extra system memory. Decreasing this amount will mean
264 SquashFS uses less memory at the expense of extra reads from disk.
266 Note there must be at least one cached fragment. Anything
267 much more than three will probably not make much difference.
270 tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
273 FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
274 file system format. VERITAS VxFS(TM) is the standard file system
275 of SCO UnixWare (and possibly others) and optionally available
276 for Sunsoft Solaris, HP-UX and many other operating systems.
277 Currently only readonly access is supported.
279 NOTE: the file system type as used by mount(1), mount(2) and
280 fstab(5) is 'vxfs' as it describes the file system format, not
283 To compile this as a module, choose M here: the module will be
284 called freevxfs. If unsure, say N.
287 tristate "Minix file system support"
290 Minix is a simple operating system used in many classes about OS's.
291 The minix file system (method to organize files on a hard disk
292 partition or a floppy disk) was the original file system for Linux,
293 but has been superseded by the second extended file system ext2fs.
294 You don't want to use the minix file system on your hard disk
295 because of certain built-in restrictions, but it is sometimes found
296 on older Linux floppy disks. This option will enlarge your kernel
297 by about 28 KB. If unsure, say N.
299 To compile this file system support as a module, choose M here: the
300 module will be called minix. Note that the file system of your root
301 partition (the one containing the directory /) cannot be compiled as
305 tristate "SonicBlue Optimized MPEG File System support"
309 This is the proprietary file system used by the Rio Karma music
310 player and ReplayTV DVR. Despite the name, this filesystem is not
311 more efficient than a standard FS for MPEG files, in fact likely
312 the opposite is true. Say Y if you have either of these devices
313 and wish to mount its disk.
315 To compile this file system support as a module, choose M here: the
316 module will be called omfs. If unsure, say N.
319 tristate "OS/2 HPFS file system support"
322 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
323 is the file system used for organizing files on OS/2 hard disk
324 partitions. Say Y if you want to be able to read files from and
325 write files to an OS/2 HPFS partition on your hard drive. OS/2
326 floppies however are in regular MSDOS format, so you don't need this
327 option in order to be able to read them. Read
328 <file:Documentation/filesystems/hpfs.txt>.
330 To compile this file system support as a module, choose M here: the
331 module will be called hpfs. If unsure, say N.
335 tristate "QNX4 file system support (read only)"
338 This is the file system used by the real-time operating systems
339 QNX 4 and QNX 6 (the latter is also called QNX RTP).
340 Further information is available at <http://www.qnx.com/>.
341 Say Y if you intend to mount QNX hard disks or floppies.
342 Unless you say Y to "QNX4FS read-write support" below, you will
343 only be able to read these file systems.
345 To compile this file system support as a module, choose M here: the
346 module will be called qnx4.
348 If you don't know whether you need it, then you don't need it:
352 bool "QNX4FS write support (DANGEROUS)"
353 depends on QNX4FS_FS && EXPERIMENTAL && BROKEN
355 Say Y if you want to test write support for QNX4 file systems.
357 It's currently broken, so for now:
361 tristate "ROM file system support"
364 This is a very small read-only file system mainly intended for
365 initial ram disks of installation disks, but it could be used for
366 other read-only media as well. Read
367 <file:Documentation/filesystems/romfs.txt> for details.
369 To compile this file system support as a module, choose M here: the
370 module will be called romfs. Note that the file system of your
371 root partition (the one containing the directory /) cannot be a
374 If you don't know whether you need it, then you don't need it:
379 tristate "System V/Xenix/V7/Coherent file system support"
382 SCO, Xenix and Coherent are commercial Unix systems for Intel
383 machines, and Version 7 was used on the DEC PDP-11. Saying Y
384 here would allow you to read from their floppies and hard disk
387 If you have floppies or hard disk partitions like that, it is likely
388 that they contain binaries from those other Unix systems; in order
389 to run these binaries, you will want to install linux-abi which is
390 a set of kernel modules that lets you run SCO, Xenix, Wyse,
391 UnixWare, Dell Unix and System V programs under Linux. It is
392 available via FTP (user: ftp) from
393 <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
394 NOTE: that will work only for binaries from Intel-based systems;
395 PDP ones will have to wait until somebody ports Linux to -11 ;-)
397 If you only intend to mount files from some other Unix over the
398 network using NFS, you don't need the System V file system support
399 (but you need NFS file system support obviously).
401 Note that this option is generally not needed for floppies, since a
402 good portable way to transport files and directories between unixes
403 (and even other operating systems) is given by the tar program ("man
404 tar" or preferably "info tar"). Note also that this option has
405 nothing whatsoever to do with the option "System V IPC". Read about
406 the System V file system in
407 <file:Documentation/filesystems/sysv-fs.txt>.
408 Saying Y here will enlarge your kernel by about 27 KB.
410 To compile this as a module, choose M here: the module will be called
413 If you haven't heard about all of this before, it's safe to say N.
417 tristate "UFS file system support (read only)"
420 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
421 OpenBSD and NeXTstep) use a file system called UFS. Some System V
422 Unixes can create and mount hard disk partitions and diskettes using
423 this file system as well. Saying Y here will allow you to read from
424 these partitions; if you also want to write to them, say Y to the
425 experimental "UFS file system write support", below. Please read the
426 file <file:Documentation/filesystems/ufs.txt> for more information.
428 The recently released UFS2 variant (used in FreeBSD 5.x) is
431 Note that this option is generally not needed for floppies, since a
432 good portable way to transport files and directories between unixes
433 (and even other operating systems) is given by the tar program ("man
434 tar" or preferably "info tar").
436 When accessing NeXTstep files, you may need to convert them from the
437 NeXT character set to the Latin1 character set; use the program
438 recode ("info recode") for this purpose.
440 To compile the UFS file system support as a module, choose M here: the
441 module will be called ufs.
443 If you haven't heard about all of this before, it's safe to say N.
446 bool "UFS file system write support (DANGEROUS)"
447 depends on UFS_FS && EXPERIMENTAL
449 Say Y here if you want to try writing to UFS partitions. This is
450 experimental, so you should back up your UFS partitions beforehand.
456 If you are experiencing any problems with the UFS filesystem, say
457 Y here. This will result in _many_ additional debugging messages to be
458 written to the system log.
460 endif # MISC_FILESYSTEMS
462 menuconfig NETWORK_FILESYSTEMS
463 bool "Network File Systems"
467 Say Y here to get to see options for network filesystems and
468 filesystem-related networking code, such as NFS daemon and
469 RPCSEC security modules.
471 This option alone does not add any kernel code.
473 If you say N, all options in this submenu will be skipped and
474 disabled; if unsure, say Y here.
476 if NETWORK_FILESYSTEMS
479 tristate "NFS client support"
483 select NFS_ACL_SUPPORT if NFS_V3_ACL
485 Choose Y here if you want to access files residing on other
486 computers using Sun's Network File System protocol. To compile
487 this file system support as a module, choose M here: the module
490 To mount file systems exported by NFS servers, you also need to
491 install the user space mount.nfs command which can be found in
492 the Linux nfs-utils package, available from http://linux-nfs.org/.
493 Information about using the mount command is available in the
494 mount(8) man page. More detail about the Linux NFS client
495 implementation is available via the nfs(5) man page.
497 Below you can choose which versions of the NFS protocol are
498 available in the kernel to mount NFS servers. Support for NFS
499 version 2 (RFC 1094) is always available when NFS_FS is selected.
501 To configure a system which mounts its root file system via NFS
502 at boot time, say Y here, select "Kernel level IP
503 autoconfiguration" in the NETWORK menu, and select "Root file
504 system on NFS" below. You cannot compile this file system as a
510 bool "NFS client support for NFS version 3"
513 This option enables support for version 3 of the NFS protocol
514 (RFC 1813) in the kernel's NFS client.
519 bool "NFS client support for the NFSv3 ACL protocol extension"
522 Some NFS servers support an auxiliary NFSv3 ACL protocol that
523 Sun added to Solaris but never became an official part of the
524 NFS version 3 protocol. This protocol extension allows
525 applications on NFS clients to manipulate POSIX Access Control
526 Lists on files residing on NFS servers. NFS servers enforce
527 ACLs on local files whether this protocol is available or not.
529 Choose Y here if your NFS server supports the Solaris NFSv3 ACL
530 protocol extension and you want your NFS client to allow
531 applications to access and modify ACLs on files on the server.
533 Most NFS servers don't support the Solaris NFSv3 ACL protocol
534 extension. You can choose N here or specify the "noacl" mount
535 option to prevent your NFS client from trying to use the NFSv3
541 bool "NFS client support for NFS version 4 (EXPERIMENTAL)"
542 depends on NFS_FS && EXPERIMENTAL
543 select RPCSEC_GSS_KRB5
545 This option enables support for version 4 of the NFS protocol
546 (RFC 3530) in the kernel's NFS client.
548 To mount NFS servers using NFSv4, you also need to install user
549 space programs which can be found in the Linux nfs-utils package,
550 available from http://linux-nfs.org/.
555 bool "Root file system on NFS"
556 depends on NFS_FS=y && IP_PNP
558 If you want your system to mount its root file system via NFS,
559 choose Y here. This is common practice for managing systems
560 without local permanent storage. For details, read
561 <file:Documentation/filesystems/nfsroot.txt>.
563 Most people say N here.
566 tristate "NFS server support"
571 select NFS_ACL_SUPPORT if NFSD_V2_ACL
573 Choose Y here if you want to allow other computers to access
574 files residing on this system using Sun's Network File System
575 protocol. To compile the NFS server support as a module,
576 choose M here: the module will be called nfsd.
578 You may choose to use a user-space NFS server instead, in which
579 case you can choose N here.
581 To export local file systems using NFS, you also need to install
582 user space programs which can be found in the Linux nfs-utils
583 package, available from http://linux-nfs.org/. More detail about
584 the Linux NFS server implementation is available via the
587 Below you can choose which versions of the NFS protocol are
588 available to clients mounting the NFS server on this system.
589 Support for NFS version 2 (RFC 1094) is always available when
590 CONFIG_NFSD is selected.
599 bool "NFS server support for NFS version 3"
602 This option enables support in your system's NFS server for
603 version 3 of the NFS protocol (RFC 1813).
608 bool "NFS server support for the NFSv3 ACL protocol extension"
612 Solaris NFS servers support an auxiliary NFSv3 ACL protocol that
613 never became an official part of the NFS version 3 protocol.
614 This protocol extension allows applications on NFS clients to
615 manipulate POSIX Access Control Lists on files residing on NFS
616 servers. NFS servers enforce POSIX ACLs on local files whether
617 this protocol is available or not.
619 This option enables support in your system's NFS server for the
620 NFSv3 ACL protocol extension allowing NFS clients to manipulate
621 POSIX ACLs on files exported by your system's NFS server. NFS
622 clients which support the Solaris NFSv3 ACL protocol can then
623 access and modify ACLs on your NFS server.
625 To store ACLs on your NFS server, you also need to enable ACL-
626 related CONFIG options for your local file systems of choice.
631 bool "NFS server support for NFS version 4 (EXPERIMENTAL)"
632 depends on NFSD && PROC_FS && EXPERIMENTAL
635 select RPCSEC_GSS_KRB5
637 This option enables support in your system's NFS server for
638 version 4 of the NFS protocol (RFC 3530).
640 To export files using NFSv4, you need to install additional user
641 space programs which can be found in the Linux nfs-utils package,
642 available from http://linux-nfs.org/.
651 depends on NFSD_V3 || NFS_V3
657 config NFS_ACL_SUPPORT
663 depends on NFSD || NFS_FS
672 config SUNRPC_XPRT_RDMA
674 depends on SUNRPC && INFINIBAND && EXPERIMENTAL
675 default SUNRPC && INFINIBAND
677 This option enables an RPC client transport capability that
678 allows the NFS client to mount servers via an RDMA-enabled
681 To compile RPC client RDMA transport support as a module,
682 choose M here: the module will be called xprtrdma.
686 config SUNRPC_REGISTER_V4
687 bool "Register local RPC services via rpcbind v4 (EXPERIMENTAL)"
688 depends on SUNRPC && EXPERIMENTAL
691 Sun added support for registering RPC services at an IPv6
692 address by creating two new versions of the rpcbind protocol
695 This option enables support in the kernel RPC server for
696 registering kernel RPC services via version 4 of the rpcbind
697 protocol. If you enable this option, you must run a portmapper
698 daemon that supports rpcbind protocol version 4.
700 Serving NFS over IPv6 from knfsd (the kernel's NFS server)
701 requires that you enable this option and use a portmapper that
702 supports rpcbind version 4.
704 If unsure, say N to get traditional behavior (register kernel
705 RPC services using only rpcbind version 2). Distributions
706 using the legacy Linux portmapper daemon must say N here.
708 config RPCSEC_GSS_KRB5
709 tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
710 depends on SUNRPC && EXPERIMENTAL
717 Choose Y here to enable Secure RPC using the Kerberos version 5
718 GSS-API mechanism (RFC 1964).
720 Secure RPC calls with Kerberos require an auxiliary user-space
721 daemon which may be found in the Linux nfs-utils package
722 available from http://linux-nfs.org/. In addition, user-space
723 Kerberos support should be installed.
727 config RPCSEC_GSS_SPKM3
728 tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
729 depends on SUNRPC && EXPERIMENTAL
737 Choose Y here to enable Secure RPC using the SPKM3 public key
738 GSS-API mechansim (RFC 2025).
740 Secure RPC calls with SPKM3 require an auxiliary userspace
741 daemon which may be found in the Linux nfs-utils package
742 available from http://linux-nfs.org/.
747 tristate "SMB file system support (OBSOLETE, please use CIFS)"
751 SMB (Server Message Block) is the protocol Windows for Workgroups
752 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
753 files and printers over local networks. Saying Y here allows you to
754 mount their file systems (often called "shares" in this context) and
755 access them just like any other Unix directory. Currently, this
756 works only if the Windows machines use TCP/IP as the underlying
757 transport protocol, and not NetBEUI. For details, read
758 <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
759 available from <http://www.tldp.org/docs.html#howto>.
761 Note: if you just want your box to act as an SMB *server* and make
762 files and printing services available to Windows clients (which need
763 to have a TCP/IP stack), you don't need to say Y here; you can use
764 the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
767 General information about how to connect Linux, Windows machines and
768 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
770 To compile the SMB support as a module, choose M here:
771 the module will be called smbfs. Most people say N, however.
773 config SMB_NLS_DEFAULT
774 bool "Use a default NLS"
777 Enabling this will make smbfs use nls translations by default. You
778 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
779 settings and you need to give the default nls for the SMB server as
780 CONFIG_SMB_NLS_REMOTE.
782 The nls settings can be changed at mount time, if your smbmount
783 supports that, using the codepage and iocharset parameters.
785 smbmount from samba 2.2.0 or later supports this.
787 config SMB_NLS_REMOTE
788 string "Default Remote NLS Option"
789 depends on SMB_NLS_DEFAULT
792 This setting allows you to specify a default value for which
793 codepage the server uses. If this field is left blank no
794 translations will be done by default. The local codepage/charset
795 default to CONFIG_NLS_DEFAULT.
797 The nls settings can be changed at mount time, if your smbmount
798 supports that, using the codepage and iocharset parameters.
800 smbmount from samba 2.2.0 or later supports this.
802 source "fs/cifs/Kconfig"
805 tristate "NCP file system support (to mount NetWare volumes)"
806 depends on IPX!=n || INET
808 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
809 used by Novell NetWare clients to talk to file servers. It is to
810 IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
811 to mount NetWare file server volumes and to access them just like
812 any other Unix directory. For details, please read the file
813 <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
814 the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
816 You do not have to say Y here if you want your Linux box to act as a
817 file *server* for Novell NetWare clients.
819 General information about how to connect Linux, Windows machines and
820 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
822 To compile this as a module, choose M here: the module will be called
823 ncpfs. Say N unless you are connected to a Novell network.
825 source "fs/ncpfs/Kconfig"
828 tristate "Coda file system support (advanced network fs)"
831 Coda is an advanced network file system, similar to NFS in that it
832 enables you to mount file systems of a remote server and access them
833 with regular Unix commands as if they were sitting on your hard
834 disk. Coda has several advantages over NFS: support for
835 disconnected operation (e.g. for laptops), read/write server
836 replication, security model for authentication and encryption,
837 persistent client caches and write back caching.
839 If you say Y here, your Linux box will be able to act as a Coda
840 *client*. You will need user level code as well, both for the
841 client and server. Servers are currently user level, i.e. they need
842 no kernel support. Please read
843 <file:Documentation/filesystems/coda.txt> and check out the Coda
844 home page <http://www.coda.cs.cmu.edu/>.
846 To compile the coda client support as a module, choose M here: the
847 module will be called coda.
850 tristate "Andrew File System support (AFS) (EXPERIMENTAL)"
851 depends on INET && EXPERIMENTAL
854 If you say Y here, you will get an experimental Andrew File System
855 driver. It currently only supports unsecured read-only AFS access.
857 See <file:Documentation/filesystems/afs.txt> for more information.
862 bool "AFS dynamic debugging"
865 Say Y here to make runtime controllable debugging messages appear.
867 See <file:Documentation/filesystems/afs.txt> for more information.
872 tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
873 depends on INET && NET_9P && EXPERIMENTAL
875 If you say Y here, you will get experimental support for
876 Plan 9 resource sharing via the 9P2000 protocol.
878 See <http://v9fs.sf.net> for more information.
882 endif # NETWORK_FILESYSTEMS
885 menu "Partition Types"
887 source "fs/partitions/Kconfig"
892 source "fs/nls/Kconfig"
893 source "fs/dlm/Kconfig"