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.
205 tristate "ADFS file system support (EXPERIMENTAL)"
206 depends on BLOCK && EXPERIMENTAL
208 The Acorn Disc Filing System is the standard file system of the
209 RiscOS operating system which runs on Acorn's ARM-based Risc PC
210 systems and the Acorn Archimedes range of machines. If you say Y
211 here, Linux will be able to read from ADFS partitions on hard drives
212 and from ADFS-formatted floppy discs. If you also want to be able to
213 write to those devices, say Y to "ADFS write support" below.
215 The ADFS partition should be the first partition (i.e.,
216 /dev/[hs]d?1) on each of your drives. Please read the file
217 <file:Documentation/filesystems/adfs.txt> for further details.
219 To compile this code as a module, choose M here: the module will be
225 bool "ADFS write support (DANGEROUS)"
228 If you say Y here, you will be able to write to ADFS partitions on
229 hard drives and ADFS-formatted floppy disks. This is experimental
230 codes, so if you're unsure, say N.
233 tristate "Amiga FFS file system support (EXPERIMENTAL)"
234 depends on BLOCK && EXPERIMENTAL
236 The Fast File System (FFS) is the common file system used on hard
237 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
238 if you want to be able to read and write files from and to an Amiga
239 FFS partition on your hard drive. Amiga floppies however cannot be
240 read with this driver due to an incompatibility of the floppy
241 controller used in an Amiga and the standard floppy controller in
242 PCs and workstations. Read <file:Documentation/filesystems/affs.txt>
243 and <file:fs/affs/Changes>.
245 With this driver you can also mount disk files used by Bernd
246 Schmidt's Un*X Amiga Emulator
247 (<http://www.freiburg.linux.de/~uae/>).
248 If you want to do this, you will also need to say Y or M to "Loop
249 device support", above.
251 To compile this file system support as a module, choose M here: the
252 module will be called affs. If unsure, say N.
255 tristate "eCrypt filesystem layer support (EXPERIMENTAL)"
256 depends on EXPERIMENTAL && KEYS && CRYPTO && NET
258 Encrypted filesystem that operates on the VFS layer. See
259 <file:Documentation/filesystems/ecryptfs.txt> to learn more about
260 eCryptfs. Userspace components are required and can be
261 obtained from <http://ecryptfs.sf.net>.
263 To compile this file system support as a module, choose M here: the
264 module will be called ecryptfs.
267 tristate "Apple Macintosh file system support (EXPERIMENTAL)"
268 depends on BLOCK && EXPERIMENTAL
271 If you say Y here, you will be able to mount Macintosh-formatted
272 floppy disks and hard drive partitions with full read-write access.
273 Please read <file:Documentation/filesystems/hfs.txt> to learn about
274 the available mount options.
276 To compile this file system support as a module, choose M here: the
277 module will be called hfs.
280 tristate "Apple Extended HFS file system support"
285 If you say Y here, you will be able to mount extended format
286 Macintosh-formatted hard drive partitions with full read-write access.
288 This file system is often called HFS+ and was introduced with
289 MacOS 8. It includes all Mac specific filesystem data such as
290 data forks and creator codes, but it also has several UNIX
291 style features such as file ownership and permissions.
294 tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)"
295 depends on BLOCK && EXPERIMENTAL
298 The BeOS File System (BeFS) is the native file system of Be, Inc's
299 BeOS. Notable features include support for arbitrary attributes
300 on files and directories, and database-like indices on selected
301 attributes. (Also note that this driver doesn't make those features
302 available at this time). It is a 64 bit filesystem, so it supports
303 extremely large volumes and files.
305 If you use this filesystem, you should also say Y to at least one
306 of the NLS (native language support) options below.
308 If you don't know what this is about, say N.
310 To compile this as a module, choose M here: the module will be
317 If you say Y here, you can use the 'debug' mount option to enable
318 debugging output from the driver.
321 tristate "BFS file system support (EXPERIMENTAL)"
322 depends on BLOCK && EXPERIMENTAL
324 Boot File System (BFS) is a file system used under SCO UnixWare to
325 allow the bootloader access to the kernel image and other important
326 files during the boot process. It is usually mounted under /stand
327 and corresponds to the slice marked as "STAND" in the UnixWare
328 partition. You should say Y if you want to read or write the files
329 on your /stand slice from within Linux. You then also need to say Y
330 to "UnixWare slices support", below. More information about the BFS
331 file system is contained in the file
332 <file:Documentation/filesystems/bfs.txt>.
334 If you don't know what this is about, say N.
336 To compile this as a module, choose M here: the module will be called
337 bfs. Note that the file system of your root partition (the one
338 containing the directory /) cannot be compiled as a module.
343 tristate "EFS file system support (read only) (EXPERIMENTAL)"
344 depends on BLOCK && EXPERIMENTAL
346 EFS is an older file system used for non-ISO9660 CD-ROMs and hard
347 disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
348 uses the XFS file system for hard disk partitions however).
350 This implementation only offers read-only access. If you don't know
351 what all this is about, it's safe to say N. For more information
352 about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
354 To compile the EFS file system support as a module, choose M here: the
355 module will be called efs.
357 source "fs/jffs2/Kconfig"
358 # UBIFS File system configuration
359 source "fs/ubifs/Kconfig"
362 tristate "Compressed ROM file system support (cramfs)"
366 Saying Y here includes support for CramFs (Compressed ROM File
367 System). CramFs is designed to be a simple, small, and compressed
368 file system for ROM based embedded systems. CramFs is read-only,
369 limited to 256MB file systems (with 16MB files), and doesn't support
370 16/32 bits uid/gid, hard links and timestamps.
372 See <file:Documentation/filesystems/cramfs.txt> and
373 <file:fs/cramfs/README> for further information.
375 To compile this as a module, choose M here: the module will be called
376 cramfs. Note that the root file system (the one containing the
377 directory /) cannot be compiled as a module.
382 tristate "SquashFS 4.0 - Squashed file system support"
386 Saying Y here includes support for SquashFS 4.0 (a Compressed
387 Read-Only File System). Squashfs is a highly compressed read-only
388 filesystem for Linux. It uses zlib compression to compress both
389 files, inodes and directories. Inodes in the system are very small
390 and all blocks are packed to minimise data overhead. Block sizes
391 greater than 4K are supported up to a maximum of 1 Mbytes (default
392 block size 128K). SquashFS 4.0 supports 64 bit filesystems and files
393 (larger than 4GB), full uid/gid information, hard links and
396 Squashfs is intended for general read-only filesystem use, for
397 archival use (i.e. in cases where a .tar.gz file may be used), and in
398 embedded systems where low overhead is needed. Further information
399 and tools are available from http://squashfs.sourceforge.net.
401 If you want to compile this as a module ( = code which can be
402 inserted in and removed from the running kernel whenever you want),
403 say M here and read <file:Documentation/modules.txt>. The module
404 will be called squashfs. Note that the root file system (the one
405 containing the directory /) cannot be compiled as a module.
409 config SQUASHFS_EMBEDDED
411 bool "Additional option for memory-constrained systems"
415 Saying Y here allows you to specify cache size.
419 config SQUASHFS_FRAGMENT_CACHE_SIZE
420 int "Number of fragments cached" if SQUASHFS_EMBEDDED
424 By default SquashFS caches the last 3 fragments read from
425 the filesystem. Increasing this amount may mean SquashFS
426 has to re-read fragments less often from disk, at the expense
427 of extra system memory. Decreasing this amount will mean
428 SquashFS uses less memory at the expense of extra reads from disk.
430 Note there must be at least one cached fragment. Anything
431 much more than three will probably not make much difference.
434 tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
437 FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
438 file system format. VERITAS VxFS(TM) is the standard file system
439 of SCO UnixWare (and possibly others) and optionally available
440 for Sunsoft Solaris, HP-UX and many other operating systems.
441 Currently only readonly access is supported.
443 NOTE: the file system type as used by mount(1), mount(2) and
444 fstab(5) is 'vxfs' as it describes the file system format, not
447 To compile this as a module, choose M here: the module will be
448 called freevxfs. If unsure, say N.
451 tristate "Minix file system support"
454 Minix is a simple operating system used in many classes about OS's.
455 The minix file system (method to organize files on a hard disk
456 partition or a floppy disk) was the original file system for Linux,
457 but has been superseded by the second extended file system ext2fs.
458 You don't want to use the minix file system on your hard disk
459 because of certain built-in restrictions, but it is sometimes found
460 on older Linux floppy disks. This option will enlarge your kernel
461 by about 28 KB. If unsure, say N.
463 To compile this file system support as a module, choose M here: the
464 module will be called minix. Note that the file system of your root
465 partition (the one containing the directory /) cannot be compiled as
469 tristate "SonicBlue Optimized MPEG File System support"
473 This is the proprietary file system used by the Rio Karma music
474 player and ReplayTV DVR. Despite the name, this filesystem is not
475 more efficient than a standard FS for MPEG files, in fact likely
476 the opposite is true. Say Y if you have either of these devices
477 and wish to mount its disk.
479 To compile this file system support as a module, choose M here: the
480 module will be called omfs. If unsure, say N.
483 tristate "OS/2 HPFS file system support"
486 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
487 is the file system used for organizing files on OS/2 hard disk
488 partitions. Say Y if you want to be able to read files from and
489 write files to an OS/2 HPFS partition on your hard drive. OS/2
490 floppies however are in regular MSDOS format, so you don't need this
491 option in order to be able to read them. Read
492 <file:Documentation/filesystems/hpfs.txt>.
494 To compile this file system support as a module, choose M here: the
495 module will be called hpfs. If unsure, say N.
499 tristate "QNX4 file system support (read only)"
502 This is the file system used by the real-time operating systems
503 QNX 4 and QNX 6 (the latter is also called QNX RTP).
504 Further information is available at <http://www.qnx.com/>.
505 Say Y if you intend to mount QNX hard disks or floppies.
506 Unless you say Y to "QNX4FS read-write support" below, you will
507 only be able to read these file systems.
509 To compile this file system support as a module, choose M here: the
510 module will be called qnx4.
512 If you don't know whether you need it, then you don't need it:
516 bool "QNX4FS write support (DANGEROUS)"
517 depends on QNX4FS_FS && EXPERIMENTAL && BROKEN
519 Say Y if you want to test write support for QNX4 file systems.
521 It's currently broken, so for now:
525 tristate "ROM file system support"
528 This is a very small read-only file system mainly intended for
529 initial ram disks of installation disks, but it could be used for
530 other read-only media as well. Read
531 <file:Documentation/filesystems/romfs.txt> for details.
533 To compile this file system support as a module, choose M here: the
534 module will be called romfs. Note that the file system of your
535 root partition (the one containing the directory /) cannot be a
538 If you don't know whether you need it, then you don't need it:
543 tristate "System V/Xenix/V7/Coherent file system support"
546 SCO, Xenix and Coherent are commercial Unix systems for Intel
547 machines, and Version 7 was used on the DEC PDP-11. Saying Y
548 here would allow you to read from their floppies and hard disk
551 If you have floppies or hard disk partitions like that, it is likely
552 that they contain binaries from those other Unix systems; in order
553 to run these binaries, you will want to install linux-abi which is
554 a set of kernel modules that lets you run SCO, Xenix, Wyse,
555 UnixWare, Dell Unix and System V programs under Linux. It is
556 available via FTP (user: ftp) from
557 <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
558 NOTE: that will work only for binaries from Intel-based systems;
559 PDP ones will have to wait until somebody ports Linux to -11 ;-)
561 If you only intend to mount files from some other Unix over the
562 network using NFS, you don't need the System V file system support
563 (but you need NFS file system support obviously).
565 Note that this option is generally not needed for floppies, since a
566 good portable way to transport files and directories between unixes
567 (and even other operating systems) is given by the tar program ("man
568 tar" or preferably "info tar"). Note also that this option has
569 nothing whatsoever to do with the option "System V IPC". Read about
570 the System V file system in
571 <file:Documentation/filesystems/sysv-fs.txt>.
572 Saying Y here will enlarge your kernel by about 27 KB.
574 To compile this as a module, choose M here: the module will be called
577 If you haven't heard about all of this before, it's safe to say N.
581 tristate "UFS file system support (read only)"
584 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
585 OpenBSD and NeXTstep) use a file system called UFS. Some System V
586 Unixes can create and mount hard disk partitions and diskettes using
587 this file system as well. Saying Y here will allow you to read from
588 these partitions; if you also want to write to them, say Y to the
589 experimental "UFS file system write support", below. Please read the
590 file <file:Documentation/filesystems/ufs.txt> for more information.
592 The recently released UFS2 variant (used in FreeBSD 5.x) is
595 Note that this option is generally not needed for floppies, since a
596 good portable way to transport files and directories between unixes
597 (and even other operating systems) is given by the tar program ("man
598 tar" or preferably "info tar").
600 When accessing NeXTstep files, you may need to convert them from the
601 NeXT character set to the Latin1 character set; use the program
602 recode ("info recode") for this purpose.
604 To compile the UFS file system support as a module, choose M here: the
605 module will be called ufs.
607 If you haven't heard about all of this before, it's safe to say N.
610 bool "UFS file system write support (DANGEROUS)"
611 depends on UFS_FS && EXPERIMENTAL
613 Say Y here if you want to try writing to UFS partitions. This is
614 experimental, so you should back up your UFS partitions beforehand.
620 If you are experiencing any problems with the UFS filesystem, say
621 Y here. This will result in _many_ additional debugging messages to be
622 written to the system log.
624 endif # MISC_FILESYSTEMS
626 menuconfig NETWORK_FILESYSTEMS
627 bool "Network File Systems"
631 Say Y here to get to see options for network filesystems and
632 filesystem-related networking code, such as NFS daemon and
633 RPCSEC security modules.
635 This option alone does not add any kernel code.
637 If you say N, all options in this submenu will be skipped and
638 disabled; if unsure, say Y here.
640 if NETWORK_FILESYSTEMS
643 tristate "NFS client support"
647 select NFS_ACL_SUPPORT if NFS_V3_ACL
649 Choose Y here if you want to access files residing on other
650 computers using Sun's Network File System protocol. To compile
651 this file system support as a module, choose M here: the module
654 To mount file systems exported by NFS servers, you also need to
655 install the user space mount.nfs command which can be found in
656 the Linux nfs-utils package, available from http://linux-nfs.org/.
657 Information about using the mount command is available in the
658 mount(8) man page. More detail about the Linux NFS client
659 implementation is available via the nfs(5) man page.
661 Below you can choose which versions of the NFS protocol are
662 available in the kernel to mount NFS servers. Support for NFS
663 version 2 (RFC 1094) is always available when NFS_FS is selected.
665 To configure a system which mounts its root file system via NFS
666 at boot time, say Y here, select "Kernel level IP
667 autoconfiguration" in the NETWORK menu, and select "Root file
668 system on NFS" below. You cannot compile this file system as a
674 bool "NFS client support for NFS version 3"
677 This option enables support for version 3 of the NFS protocol
678 (RFC 1813) in the kernel's NFS client.
683 bool "NFS client support for the NFSv3 ACL protocol extension"
686 Some NFS servers support an auxiliary NFSv3 ACL protocol that
687 Sun added to Solaris but never became an official part of the
688 NFS version 3 protocol. This protocol extension allows
689 applications on NFS clients to manipulate POSIX Access Control
690 Lists on files residing on NFS servers. NFS servers enforce
691 ACLs on local files whether this protocol is available or not.
693 Choose Y here if your NFS server supports the Solaris NFSv3 ACL
694 protocol extension and you want your NFS client to allow
695 applications to access and modify ACLs on files on the server.
697 Most NFS servers don't support the Solaris NFSv3 ACL protocol
698 extension. You can choose N here or specify the "noacl" mount
699 option to prevent your NFS client from trying to use the NFSv3
705 bool "NFS client support for NFS version 4 (EXPERIMENTAL)"
706 depends on NFS_FS && EXPERIMENTAL
707 select RPCSEC_GSS_KRB5
709 This option enables support for version 4 of the NFS protocol
710 (RFC 3530) in the kernel's NFS client.
712 To mount NFS servers using NFSv4, you also need to install user
713 space programs which can be found in the Linux nfs-utils package,
714 available from http://linux-nfs.org/.
719 bool "Root file system on NFS"
720 depends on NFS_FS=y && IP_PNP
722 If you want your system to mount its root file system via NFS,
723 choose Y here. This is common practice for managing systems
724 without local permanent storage. For details, read
725 <file:Documentation/filesystems/nfsroot.txt>.
727 Most people say N here.
730 tristate "NFS server support"
735 select NFS_ACL_SUPPORT if NFSD_V2_ACL
737 Choose Y here if you want to allow other computers to access
738 files residing on this system using Sun's Network File System
739 protocol. To compile the NFS server support as a module,
740 choose M here: the module will be called nfsd.
742 You may choose to use a user-space NFS server instead, in which
743 case you can choose N here.
745 To export local file systems using NFS, you also need to install
746 user space programs which can be found in the Linux nfs-utils
747 package, available from http://linux-nfs.org/. More detail about
748 the Linux NFS server implementation is available via the
751 Below you can choose which versions of the NFS protocol are
752 available to clients mounting the NFS server on this system.
753 Support for NFS version 2 (RFC 1094) is always available when
754 CONFIG_NFSD is selected.
763 bool "NFS server support for NFS version 3"
766 This option enables support in your system's NFS server for
767 version 3 of the NFS protocol (RFC 1813).
772 bool "NFS server support for the NFSv3 ACL protocol extension"
776 Solaris NFS servers support an auxiliary NFSv3 ACL protocol that
777 never became an official part of the NFS version 3 protocol.
778 This protocol extension allows applications on NFS clients to
779 manipulate POSIX Access Control Lists on files residing on NFS
780 servers. NFS servers enforce POSIX ACLs on local files whether
781 this protocol is available or not.
783 This option enables support in your system's NFS server for the
784 NFSv3 ACL protocol extension allowing NFS clients to manipulate
785 POSIX ACLs on files exported by your system's NFS server. NFS
786 clients which support the Solaris NFSv3 ACL protocol can then
787 access and modify ACLs on your NFS server.
789 To store ACLs on your NFS server, you also need to enable ACL-
790 related CONFIG options for your local file systems of choice.
795 bool "NFS server support for NFS version 4 (EXPERIMENTAL)"
796 depends on NFSD && PROC_FS && EXPERIMENTAL
799 select RPCSEC_GSS_KRB5
801 This option enables support in your system's NFS server for
802 version 4 of the NFS protocol (RFC 3530).
804 To export files using NFSv4, you need to install additional user
805 space programs which can be found in the Linux nfs-utils package,
806 available from http://linux-nfs.org/.
815 depends on NFSD_V3 || NFS_V3
821 config NFS_ACL_SUPPORT
827 depends on NFSD || NFS_FS
836 config SUNRPC_XPRT_RDMA
838 depends on SUNRPC && INFINIBAND && EXPERIMENTAL
839 default SUNRPC && INFINIBAND
841 This option enables an RPC client transport capability that
842 allows the NFS client to mount servers via an RDMA-enabled
845 To compile RPC client RDMA transport support as a module,
846 choose M here: the module will be called xprtrdma.
850 config SUNRPC_REGISTER_V4
851 bool "Register local RPC services via rpcbind v4 (EXPERIMENTAL)"
852 depends on SUNRPC && EXPERIMENTAL
855 Sun added support for registering RPC services at an IPv6
856 address by creating two new versions of the rpcbind protocol
859 This option enables support in the kernel RPC server for
860 registering kernel RPC services via version 4 of the rpcbind
861 protocol. If you enable this option, you must run a portmapper
862 daemon that supports rpcbind protocol version 4.
864 Serving NFS over IPv6 from knfsd (the kernel's NFS server)
865 requires that you enable this option and use a portmapper that
866 supports rpcbind version 4.
868 If unsure, say N to get traditional behavior (register kernel
869 RPC services using only rpcbind version 2). Distributions
870 using the legacy Linux portmapper daemon must say N here.
872 config RPCSEC_GSS_KRB5
873 tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
874 depends on SUNRPC && EXPERIMENTAL
881 Choose Y here to enable Secure RPC using the Kerberos version 5
882 GSS-API mechanism (RFC 1964).
884 Secure RPC calls with Kerberos require an auxiliary user-space
885 daemon which may be found in the Linux nfs-utils package
886 available from http://linux-nfs.org/. In addition, user-space
887 Kerberos support should be installed.
891 config RPCSEC_GSS_SPKM3
892 tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
893 depends on SUNRPC && EXPERIMENTAL
901 Choose Y here to enable Secure RPC using the SPKM3 public key
902 GSS-API mechansim (RFC 2025).
904 Secure RPC calls with SPKM3 require an auxiliary userspace
905 daemon which may be found in the Linux nfs-utils package
906 available from http://linux-nfs.org/.
911 tristate "SMB file system support (OBSOLETE, please use CIFS)"
915 SMB (Server Message Block) is the protocol Windows for Workgroups
916 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
917 files and printers over local networks. Saying Y here allows you to
918 mount their file systems (often called "shares" in this context) and
919 access them just like any other Unix directory. Currently, this
920 works only if the Windows machines use TCP/IP as the underlying
921 transport protocol, and not NetBEUI. For details, read
922 <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
923 available from <http://www.tldp.org/docs.html#howto>.
925 Note: if you just want your box to act as an SMB *server* and make
926 files and printing services available to Windows clients (which need
927 to have a TCP/IP stack), you don't need to say Y here; you can use
928 the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
931 General information about how to connect Linux, Windows machines and
932 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
934 To compile the SMB support as a module, choose M here:
935 the module will be called smbfs. Most people say N, however.
937 config SMB_NLS_DEFAULT
938 bool "Use a default NLS"
941 Enabling this will make smbfs use nls translations by default. You
942 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
943 settings and you need to give the default nls for the SMB server as
944 CONFIG_SMB_NLS_REMOTE.
946 The nls settings can be changed at mount time, if your smbmount
947 supports that, using the codepage and iocharset parameters.
949 smbmount from samba 2.2.0 or later supports this.
951 config SMB_NLS_REMOTE
952 string "Default Remote NLS Option"
953 depends on SMB_NLS_DEFAULT
956 This setting allows you to specify a default value for which
957 codepage the server uses. If this field is left blank no
958 translations will be done by default. The local codepage/charset
959 default to CONFIG_NLS_DEFAULT.
961 The nls settings can be changed at mount time, if your smbmount
962 supports that, using the codepage and iocharset parameters.
964 smbmount from samba 2.2.0 or later supports this.
966 source "fs/cifs/Kconfig"
969 tristate "NCP file system support (to mount NetWare volumes)"
970 depends on IPX!=n || INET
972 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
973 used by Novell NetWare clients to talk to file servers. It is to
974 IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
975 to mount NetWare file server volumes and to access them just like
976 any other Unix directory. For details, please read the file
977 <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
978 the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
980 You do not have to say Y here if you want your Linux box to act as a
981 file *server* for Novell NetWare clients.
983 General information about how to connect Linux, Windows machines and
984 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
986 To compile this as a module, choose M here: the module will be called
987 ncpfs. Say N unless you are connected to a Novell network.
989 source "fs/ncpfs/Kconfig"
992 tristate "Coda file system support (advanced network fs)"
995 Coda is an advanced network file system, similar to NFS in that it
996 enables you to mount file systems of a remote server and access them
997 with regular Unix commands as if they were sitting on your hard
998 disk. Coda has several advantages over NFS: support for
999 disconnected operation (e.g. for laptops), read/write server
1000 replication, security model for authentication and encryption,
1001 persistent client caches and write back caching.
1003 If you say Y here, your Linux box will be able to act as a Coda
1004 *client*. You will need user level code as well, both for the
1005 client and server. Servers are currently user level, i.e. they need
1006 no kernel support. Please read
1007 <file:Documentation/filesystems/coda.txt> and check out the Coda
1008 home page <http://www.coda.cs.cmu.edu/>.
1010 To compile the coda client support as a module, choose M here: the
1011 module will be called coda.
1014 tristate "Andrew File System support (AFS) (EXPERIMENTAL)"
1015 depends on INET && EXPERIMENTAL
1018 If you say Y here, you will get an experimental Andrew File System
1019 driver. It currently only supports unsecured read-only AFS access.
1021 See <file:Documentation/filesystems/afs.txt> for more information.
1026 bool "AFS dynamic debugging"
1029 Say Y here to make runtime controllable debugging messages appear.
1031 See <file:Documentation/filesystems/afs.txt> for more information.
1036 tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
1037 depends on INET && NET_9P && EXPERIMENTAL
1039 If you say Y here, you will get experimental support for
1040 Plan 9 resource sharing via the 9P2000 protocol.
1042 See <http://v9fs.sf.net> for more information.
1046 endif # NETWORK_FILESYSTEMS
1049 menu "Partition Types"
1051 source "fs/partitions/Kconfig"
1056 source "fs/nls/Kconfig"
1057 source "fs/dlm/Kconfig"