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.
186 tristate "Userspace-driven configuration filesystem"
189 configfs is a ram-based filesystem that provides the converse
190 of sysfs's functionality. Where sysfs is a filesystem-based
191 view of kernel objects, configfs is a filesystem-based manager
192 of kernel objects, or config_items.
194 Both sysfs and configfs can and should exist together on the
195 same system. One is not a replacement for the other.
199 menuconfig MISC_FILESYSTEMS
200 bool "Miscellaneous filesystems"
203 Say Y here to get to see options for various miscellaneous
204 filesystems, such as filesystems that came from other
207 This option alone does not add any kernel code.
209 If you say N, all options in this submenu will be skipped and
210 disabled; if unsure, say Y here.
215 tristate "ADFS file system support (EXPERIMENTAL)"
216 depends on BLOCK && EXPERIMENTAL
218 The Acorn Disc Filing System is the standard file system of the
219 RiscOS operating system which runs on Acorn's ARM-based Risc PC
220 systems and the Acorn Archimedes range of machines. If you say Y
221 here, Linux will be able to read from ADFS partitions on hard drives
222 and from ADFS-formatted floppy discs. If you also want to be able to
223 write to those devices, say Y to "ADFS write support" below.
225 The ADFS partition should be the first partition (i.e.,
226 /dev/[hs]d?1) on each of your drives. Please read the file
227 <file:Documentation/filesystems/adfs.txt> for further details.
229 To compile this code as a module, choose M here: the module will be
235 bool "ADFS write support (DANGEROUS)"
238 If you say Y here, you will be able to write to ADFS partitions on
239 hard drives and ADFS-formatted floppy disks. This is experimental
240 codes, so if you're unsure, say N.
243 tristate "Amiga FFS file system support (EXPERIMENTAL)"
244 depends on BLOCK && EXPERIMENTAL
246 The Fast File System (FFS) is the common file system used on hard
247 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
248 if you want to be able to read and write files from and to an Amiga
249 FFS partition on your hard drive. Amiga floppies however cannot be
250 read with this driver due to an incompatibility of the floppy
251 controller used in an Amiga and the standard floppy controller in
252 PCs and workstations. Read <file:Documentation/filesystems/affs.txt>
253 and <file:fs/affs/Changes>.
255 With this driver you can also mount disk files used by Bernd
256 Schmidt's Un*X Amiga Emulator
257 (<http://www.freiburg.linux.de/~uae/>).
258 If you want to do this, you will also need to say Y or M to "Loop
259 device support", above.
261 To compile this file system support as a module, choose M here: the
262 module will be called affs. If unsure, say N.
265 tristate "eCrypt filesystem layer support (EXPERIMENTAL)"
266 depends on EXPERIMENTAL && KEYS && CRYPTO && NET
268 Encrypted filesystem that operates on the VFS layer. See
269 <file:Documentation/filesystems/ecryptfs.txt> to learn more about
270 eCryptfs. Userspace components are required and can be
271 obtained from <http://ecryptfs.sf.net>.
273 To compile this file system support as a module, choose M here: the
274 module will be called ecryptfs.
277 tristate "Apple Macintosh file system support (EXPERIMENTAL)"
278 depends on BLOCK && EXPERIMENTAL
281 If you say Y here, you will be able to mount Macintosh-formatted
282 floppy disks and hard drive partitions with full read-write access.
283 Please read <file:Documentation/filesystems/hfs.txt> to learn about
284 the available mount options.
286 To compile this file system support as a module, choose M here: the
287 module will be called hfs.
290 tristate "Apple Extended HFS file system support"
295 If you say Y here, you will be able to mount extended format
296 Macintosh-formatted hard drive partitions with full read-write access.
298 This file system is often called HFS+ and was introduced with
299 MacOS 8. It includes all Mac specific filesystem data such as
300 data forks and creator codes, but it also has several UNIX
301 style features such as file ownership and permissions.
304 tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)"
305 depends on BLOCK && EXPERIMENTAL
308 The BeOS File System (BeFS) is the native file system of Be, Inc's
309 BeOS. Notable features include support for arbitrary attributes
310 on files and directories, and database-like indices on selected
311 attributes. (Also note that this driver doesn't make those features
312 available at this time). It is a 64 bit filesystem, so it supports
313 extremely large volumes and files.
315 If you use this filesystem, you should also say Y to at least one
316 of the NLS (native language support) options below.
318 If you don't know what this is about, say N.
320 To compile this as a module, choose M here: the module will be
327 If you say Y here, you can use the 'debug' mount option to enable
328 debugging output from the driver.
331 tristate "BFS file system support (EXPERIMENTAL)"
332 depends on BLOCK && EXPERIMENTAL
334 Boot File System (BFS) is a file system used under SCO UnixWare to
335 allow the bootloader access to the kernel image and other important
336 files during the boot process. It is usually mounted under /stand
337 and corresponds to the slice marked as "STAND" in the UnixWare
338 partition. You should say Y if you want to read or write the files
339 on your /stand slice from within Linux. You then also need to say Y
340 to "UnixWare slices support", below. More information about the BFS
341 file system is contained in the file
342 <file:Documentation/filesystems/bfs.txt>.
344 If you don't know what this is about, say N.
346 To compile this as a module, choose M here: the module will be called
347 bfs. Note that the file system of your root partition (the one
348 containing the directory /) cannot be compiled as a module.
353 tristate "EFS file system support (read only) (EXPERIMENTAL)"
354 depends on BLOCK && EXPERIMENTAL
356 EFS is an older file system used for non-ISO9660 CD-ROMs and hard
357 disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
358 uses the XFS file system for hard disk partitions however).
360 This implementation only offers read-only access. If you don't know
361 what all this is about, it's safe to say N. For more information
362 about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
364 To compile the EFS file system support as a module, choose M here: the
365 module will be called efs.
367 source "fs/jffs2/Kconfig"
368 # UBIFS File system configuration
369 source "fs/ubifs/Kconfig"
372 tristate "Compressed ROM file system support (cramfs)"
376 Saying Y here includes support for CramFs (Compressed ROM File
377 System). CramFs is designed to be a simple, small, and compressed
378 file system for ROM based embedded systems. CramFs is read-only,
379 limited to 256MB file systems (with 16MB files), and doesn't support
380 16/32 bits uid/gid, hard links and timestamps.
382 See <file:Documentation/filesystems/cramfs.txt> and
383 <file:fs/cramfs/README> for further information.
385 To compile this as a module, choose M here: the module will be called
386 cramfs. Note that the root file system (the one containing the
387 directory /) cannot be compiled as a module.
392 tristate "SquashFS 4.0 - Squashed file system support"
396 Saying Y here includes support for SquashFS 4.0 (a Compressed
397 Read-Only File System). Squashfs is a highly compressed read-only
398 filesystem for Linux. It uses zlib compression to compress both
399 files, inodes and directories. Inodes in the system are very small
400 and all blocks are packed to minimise data overhead. Block sizes
401 greater than 4K are supported up to a maximum of 1 Mbytes (default
402 block size 128K). SquashFS 4.0 supports 64 bit filesystems and files
403 (larger than 4GB), full uid/gid information, hard links and
406 Squashfs is intended for general read-only filesystem use, for
407 archival use (i.e. in cases where a .tar.gz file may be used), and in
408 embedded systems where low overhead is needed. Further information
409 and tools are available from http://squashfs.sourceforge.net.
411 If you want to compile this as a module ( = code which can be
412 inserted in and removed from the running kernel whenever you want),
413 say M here and read <file:Documentation/modules.txt>. The module
414 will be called squashfs. Note that the root file system (the one
415 containing the directory /) cannot be compiled as a module.
419 config SQUASHFS_EMBEDDED
421 bool "Additional option for memory-constrained systems"
425 Saying Y here allows you to specify cache size.
429 config SQUASHFS_FRAGMENT_CACHE_SIZE
430 int "Number of fragments cached" if SQUASHFS_EMBEDDED
434 By default SquashFS caches the last 3 fragments read from
435 the filesystem. Increasing this amount may mean SquashFS
436 has to re-read fragments less often from disk, at the expense
437 of extra system memory. Decreasing this amount will mean
438 SquashFS uses less memory at the expense of extra reads from disk.
440 Note there must be at least one cached fragment. Anything
441 much more than three will probably not make much difference.
444 tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
447 FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
448 file system format. VERITAS VxFS(TM) is the standard file system
449 of SCO UnixWare (and possibly others) and optionally available
450 for Sunsoft Solaris, HP-UX and many other operating systems.
451 Currently only readonly access is supported.
453 NOTE: the file system type as used by mount(1), mount(2) and
454 fstab(5) is 'vxfs' as it describes the file system format, not
457 To compile this as a module, choose M here: the module will be
458 called freevxfs. If unsure, say N.
461 tristate "Minix file system support"
464 Minix is a simple operating system used in many classes about OS's.
465 The minix file system (method to organize files on a hard disk
466 partition or a floppy disk) was the original file system for Linux,
467 but has been superseded by the second extended file system ext2fs.
468 You don't want to use the minix file system on your hard disk
469 because of certain built-in restrictions, but it is sometimes found
470 on older Linux floppy disks. This option will enlarge your kernel
471 by about 28 KB. If unsure, say N.
473 To compile this file system support as a module, choose M here: the
474 module will be called minix. Note that the file system of your root
475 partition (the one containing the directory /) cannot be compiled as
479 tristate "SonicBlue Optimized MPEG File System support"
483 This is the proprietary file system used by the Rio Karma music
484 player and ReplayTV DVR. Despite the name, this filesystem is not
485 more efficient than a standard FS for MPEG files, in fact likely
486 the opposite is true. Say Y if you have either of these devices
487 and wish to mount its disk.
489 To compile this file system support as a module, choose M here: the
490 module will be called omfs. If unsure, say N.
493 tristate "OS/2 HPFS file system support"
496 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
497 is the file system used for organizing files on OS/2 hard disk
498 partitions. Say Y if you want to be able to read files from and
499 write files to an OS/2 HPFS partition on your hard drive. OS/2
500 floppies however are in regular MSDOS format, so you don't need this
501 option in order to be able to read them. Read
502 <file:Documentation/filesystems/hpfs.txt>.
504 To compile this file system support as a module, choose M here: the
505 module will be called hpfs. If unsure, say N.
509 tristate "QNX4 file system support (read only)"
512 This is the file system used by the real-time operating systems
513 QNX 4 and QNX 6 (the latter is also called QNX RTP).
514 Further information is available at <http://www.qnx.com/>.
515 Say Y if you intend to mount QNX hard disks or floppies.
516 Unless you say Y to "QNX4FS read-write support" below, you will
517 only be able to read these file systems.
519 To compile this file system support as a module, choose M here: the
520 module will be called qnx4.
522 If you don't know whether you need it, then you don't need it:
526 bool "QNX4FS write support (DANGEROUS)"
527 depends on QNX4FS_FS && EXPERIMENTAL && BROKEN
529 Say Y if you want to test write support for QNX4 file systems.
531 It's currently broken, so for now:
535 tristate "ROM file system support"
538 This is a very small read-only file system mainly intended for
539 initial ram disks of installation disks, but it could be used for
540 other read-only media as well. Read
541 <file:Documentation/filesystems/romfs.txt> for details.
543 To compile this file system support as a module, choose M here: the
544 module will be called romfs. Note that the file system of your
545 root partition (the one containing the directory /) cannot be a
548 If you don't know whether you need it, then you don't need it:
553 tristate "System V/Xenix/V7/Coherent file system support"
556 SCO, Xenix and Coherent are commercial Unix systems for Intel
557 machines, and Version 7 was used on the DEC PDP-11. Saying Y
558 here would allow you to read from their floppies and hard disk
561 If you have floppies or hard disk partitions like that, it is likely
562 that they contain binaries from those other Unix systems; in order
563 to run these binaries, you will want to install linux-abi which is
564 a set of kernel modules that lets you run SCO, Xenix, Wyse,
565 UnixWare, Dell Unix and System V programs under Linux. It is
566 available via FTP (user: ftp) from
567 <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
568 NOTE: that will work only for binaries from Intel-based systems;
569 PDP ones will have to wait until somebody ports Linux to -11 ;-)
571 If you only intend to mount files from some other Unix over the
572 network using NFS, you don't need the System V file system support
573 (but you need NFS file system support obviously).
575 Note that this option is generally not needed for floppies, since a
576 good portable way to transport files and directories between unixes
577 (and even other operating systems) is given by the tar program ("man
578 tar" or preferably "info tar"). Note also that this option has
579 nothing whatsoever to do with the option "System V IPC". Read about
580 the System V file system in
581 <file:Documentation/filesystems/sysv-fs.txt>.
582 Saying Y here will enlarge your kernel by about 27 KB.
584 To compile this as a module, choose M here: the module will be called
587 If you haven't heard about all of this before, it's safe to say N.
591 tristate "UFS file system support (read only)"
594 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
595 OpenBSD and NeXTstep) use a file system called UFS. Some System V
596 Unixes can create and mount hard disk partitions and diskettes using
597 this file system as well. Saying Y here will allow you to read from
598 these partitions; if you also want to write to them, say Y to the
599 experimental "UFS file system write support", below. Please read the
600 file <file:Documentation/filesystems/ufs.txt> for more information.
602 The recently released UFS2 variant (used in FreeBSD 5.x) is
605 Note that this option is generally not needed for floppies, since a
606 good portable way to transport files and directories between unixes
607 (and even other operating systems) is given by the tar program ("man
608 tar" or preferably "info tar").
610 When accessing NeXTstep files, you may need to convert them from the
611 NeXT character set to the Latin1 character set; use the program
612 recode ("info recode") for this purpose.
614 To compile the UFS file system support as a module, choose M here: the
615 module will be called ufs.
617 If you haven't heard about all of this before, it's safe to say N.
620 bool "UFS file system write support (DANGEROUS)"
621 depends on UFS_FS && EXPERIMENTAL
623 Say Y here if you want to try writing to UFS partitions. This is
624 experimental, so you should back up your UFS partitions beforehand.
630 If you are experiencing any problems with the UFS filesystem, say
631 Y here. This will result in _many_ additional debugging messages to be
632 written to the system log.
634 endif # MISC_FILESYSTEMS
636 menuconfig NETWORK_FILESYSTEMS
637 bool "Network File Systems"
641 Say Y here to get to see options for network filesystems and
642 filesystem-related networking code, such as NFS daemon and
643 RPCSEC security modules.
645 This option alone does not add any kernel code.
647 If you say N, all options in this submenu will be skipped and
648 disabled; if unsure, say Y here.
650 if NETWORK_FILESYSTEMS
653 tristate "NFS client support"
657 select NFS_ACL_SUPPORT if NFS_V3_ACL
659 Choose Y here if you want to access files residing on other
660 computers using Sun's Network File System protocol. To compile
661 this file system support as a module, choose M here: the module
664 To mount file systems exported by NFS servers, you also need to
665 install the user space mount.nfs command which can be found in
666 the Linux nfs-utils package, available from http://linux-nfs.org/.
667 Information about using the mount command is available in the
668 mount(8) man page. More detail about the Linux NFS client
669 implementation is available via the nfs(5) man page.
671 Below you can choose which versions of the NFS protocol are
672 available in the kernel to mount NFS servers. Support for NFS
673 version 2 (RFC 1094) is always available when NFS_FS is selected.
675 To configure a system which mounts its root file system via NFS
676 at boot time, say Y here, select "Kernel level IP
677 autoconfiguration" in the NETWORK menu, and select "Root file
678 system on NFS" below. You cannot compile this file system as a
684 bool "NFS client support for NFS version 3"
687 This option enables support for version 3 of the NFS protocol
688 (RFC 1813) in the kernel's NFS client.
693 bool "NFS client support for the NFSv3 ACL protocol extension"
696 Some NFS servers support an auxiliary NFSv3 ACL protocol that
697 Sun added to Solaris but never became an official part of the
698 NFS version 3 protocol. This protocol extension allows
699 applications on NFS clients to manipulate POSIX Access Control
700 Lists on files residing on NFS servers. NFS servers enforce
701 ACLs on local files whether this protocol is available or not.
703 Choose Y here if your NFS server supports the Solaris NFSv3 ACL
704 protocol extension and you want your NFS client to allow
705 applications to access and modify ACLs on files on the server.
707 Most NFS servers don't support the Solaris NFSv3 ACL protocol
708 extension. You can choose N here or specify the "noacl" mount
709 option to prevent your NFS client from trying to use the NFSv3
715 bool "NFS client support for NFS version 4 (EXPERIMENTAL)"
716 depends on NFS_FS && EXPERIMENTAL
717 select RPCSEC_GSS_KRB5
719 This option enables support for version 4 of the NFS protocol
720 (RFC 3530) in the kernel's NFS client.
722 To mount NFS servers using NFSv4, you also need to install user
723 space programs which can be found in the Linux nfs-utils package,
724 available from http://linux-nfs.org/.
729 bool "Root file system on NFS"
730 depends on NFS_FS=y && IP_PNP
732 If you want your system to mount its root file system via NFS,
733 choose Y here. This is common practice for managing systems
734 without local permanent storage. For details, read
735 <file:Documentation/filesystems/nfsroot.txt>.
737 Most people say N here.
740 tristate "NFS server support"
745 select NFS_ACL_SUPPORT if NFSD_V2_ACL
747 Choose Y here if you want to allow other computers to access
748 files residing on this system using Sun's Network File System
749 protocol. To compile the NFS server support as a module,
750 choose M here: the module will be called nfsd.
752 You may choose to use a user-space NFS server instead, in which
753 case you can choose N here.
755 To export local file systems using NFS, you also need to install
756 user space programs which can be found in the Linux nfs-utils
757 package, available from http://linux-nfs.org/. More detail about
758 the Linux NFS server implementation is available via the
761 Below you can choose which versions of the NFS protocol are
762 available to clients mounting the NFS server on this system.
763 Support for NFS version 2 (RFC 1094) is always available when
764 CONFIG_NFSD is selected.
773 bool "NFS server support for NFS version 3"
776 This option enables support in your system's NFS server for
777 version 3 of the NFS protocol (RFC 1813).
782 bool "NFS server support for the NFSv3 ACL protocol extension"
786 Solaris NFS servers support an auxiliary NFSv3 ACL protocol that
787 never became an official part of the NFS version 3 protocol.
788 This protocol extension allows applications on NFS clients to
789 manipulate POSIX Access Control Lists on files residing on NFS
790 servers. NFS servers enforce POSIX ACLs on local files whether
791 this protocol is available or not.
793 This option enables support in your system's NFS server for the
794 NFSv3 ACL protocol extension allowing NFS clients to manipulate
795 POSIX ACLs on files exported by your system's NFS server. NFS
796 clients which support the Solaris NFSv3 ACL protocol can then
797 access and modify ACLs on your NFS server.
799 To store ACLs on your NFS server, you also need to enable ACL-
800 related CONFIG options for your local file systems of choice.
805 bool "NFS server support for NFS version 4 (EXPERIMENTAL)"
806 depends on NFSD && PROC_FS && EXPERIMENTAL
809 select RPCSEC_GSS_KRB5
811 This option enables support in your system's NFS server for
812 version 4 of the NFS protocol (RFC 3530).
814 To export files using NFSv4, you need to install additional user
815 space programs which can be found in the Linux nfs-utils package,
816 available from http://linux-nfs.org/.
825 depends on NFSD_V3 || NFS_V3
831 config NFS_ACL_SUPPORT
837 depends on NFSD || NFS_FS
846 config SUNRPC_XPRT_RDMA
848 depends on SUNRPC && INFINIBAND && EXPERIMENTAL
849 default SUNRPC && INFINIBAND
851 This option enables an RPC client transport capability that
852 allows the NFS client to mount servers via an RDMA-enabled
855 To compile RPC client RDMA transport support as a module,
856 choose M here: the module will be called xprtrdma.
860 config SUNRPC_REGISTER_V4
861 bool "Register local RPC services via rpcbind v4 (EXPERIMENTAL)"
862 depends on SUNRPC && EXPERIMENTAL
865 Sun added support for registering RPC services at an IPv6
866 address by creating two new versions of the rpcbind protocol
869 This option enables support in the kernel RPC server for
870 registering kernel RPC services via version 4 of the rpcbind
871 protocol. If you enable this option, you must run a portmapper
872 daemon that supports rpcbind protocol version 4.
874 Serving NFS over IPv6 from knfsd (the kernel's NFS server)
875 requires that you enable this option and use a portmapper that
876 supports rpcbind version 4.
878 If unsure, say N to get traditional behavior (register kernel
879 RPC services using only rpcbind version 2). Distributions
880 using the legacy Linux portmapper daemon must say N here.
882 config RPCSEC_GSS_KRB5
883 tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
884 depends on SUNRPC && EXPERIMENTAL
891 Choose Y here to enable Secure RPC using the Kerberos version 5
892 GSS-API mechanism (RFC 1964).
894 Secure RPC calls with Kerberos require an auxiliary user-space
895 daemon which may be found in the Linux nfs-utils package
896 available from http://linux-nfs.org/. In addition, user-space
897 Kerberos support should be installed.
901 config RPCSEC_GSS_SPKM3
902 tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
903 depends on SUNRPC && EXPERIMENTAL
911 Choose Y here to enable Secure RPC using the SPKM3 public key
912 GSS-API mechansim (RFC 2025).
914 Secure RPC calls with SPKM3 require an auxiliary userspace
915 daemon which may be found in the Linux nfs-utils package
916 available from http://linux-nfs.org/.
921 tristate "SMB file system support (OBSOLETE, please use CIFS)"
925 SMB (Server Message Block) is the protocol Windows for Workgroups
926 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
927 files and printers over local networks. Saying Y here allows you to
928 mount their file systems (often called "shares" in this context) and
929 access them just like any other Unix directory. Currently, this
930 works only if the Windows machines use TCP/IP as the underlying
931 transport protocol, and not NetBEUI. For details, read
932 <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
933 available from <http://www.tldp.org/docs.html#howto>.
935 Note: if you just want your box to act as an SMB *server* and make
936 files and printing services available to Windows clients (which need
937 to have a TCP/IP stack), you don't need to say Y here; you can use
938 the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
941 General information about how to connect Linux, Windows machines and
942 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
944 To compile the SMB support as a module, choose M here:
945 the module will be called smbfs. Most people say N, however.
947 config SMB_NLS_DEFAULT
948 bool "Use a default NLS"
951 Enabling this will make smbfs use nls translations by default. You
952 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
953 settings and you need to give the default nls for the SMB server as
954 CONFIG_SMB_NLS_REMOTE.
956 The nls settings can be changed at mount time, if your smbmount
957 supports that, using the codepage and iocharset parameters.
959 smbmount from samba 2.2.0 or later supports this.
961 config SMB_NLS_REMOTE
962 string "Default Remote NLS Option"
963 depends on SMB_NLS_DEFAULT
966 This setting allows you to specify a default value for which
967 codepage the server uses. If this field is left blank no
968 translations will be done by default. The local codepage/charset
969 default to CONFIG_NLS_DEFAULT.
971 The nls settings can be changed at mount time, if your smbmount
972 supports that, using the codepage and iocharset parameters.
974 smbmount from samba 2.2.0 or later supports this.
976 source "fs/cifs/Kconfig"
979 tristate "NCP file system support (to mount NetWare volumes)"
980 depends on IPX!=n || INET
982 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
983 used by Novell NetWare clients to talk to file servers. It is to
984 IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
985 to mount NetWare file server volumes and to access them just like
986 any other Unix directory. For details, please read the file
987 <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
988 the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
990 You do not have to say Y here if you want your Linux box to act as a
991 file *server* for Novell NetWare clients.
993 General information about how to connect Linux, Windows machines and
994 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
996 To compile this as a module, choose M here: the module will be called
997 ncpfs. Say N unless you are connected to a Novell network.
999 source "fs/ncpfs/Kconfig"
1002 tristate "Coda file system support (advanced network fs)"
1005 Coda is an advanced network file system, similar to NFS in that it
1006 enables you to mount file systems of a remote server and access them
1007 with regular Unix commands as if they were sitting on your hard
1008 disk. Coda has several advantages over NFS: support for
1009 disconnected operation (e.g. for laptops), read/write server
1010 replication, security model for authentication and encryption,
1011 persistent client caches and write back caching.
1013 If you say Y here, your Linux box will be able to act as a Coda
1014 *client*. You will need user level code as well, both for the
1015 client and server. Servers are currently user level, i.e. they need
1016 no kernel support. Please read
1017 <file:Documentation/filesystems/coda.txt> and check out the Coda
1018 home page <http://www.coda.cs.cmu.edu/>.
1020 To compile the coda client support as a module, choose M here: the
1021 module will be called coda.
1024 tristate "Andrew File System support (AFS) (EXPERIMENTAL)"
1025 depends on INET && EXPERIMENTAL
1028 If you say Y here, you will get an experimental Andrew File System
1029 driver. It currently only supports unsecured read-only AFS access.
1031 See <file:Documentation/filesystems/afs.txt> for more information.
1036 bool "AFS dynamic debugging"
1039 Say Y here to make runtime controllable debugging messages appear.
1041 See <file:Documentation/filesystems/afs.txt> for more information.
1046 tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
1047 depends on INET && NET_9P && EXPERIMENTAL
1049 If you say Y here, you will get experimental support for
1050 Plan 9 resource sharing via the 9P2000 protocol.
1052 See <http://v9fs.sf.net> for more information.
1056 endif # NETWORK_FILESYSTEMS
1059 menu "Partition Types"
1061 source "fs/partitions/Kconfig"
1066 source "fs/nls/Kconfig"
1067 source "fs/dlm/Kconfig"