fs/Kconfig

   1 #
   2 # File system configuration
   3 #
   4
   5 menu "File systems"
   6
   7 if BLOCK
   8
   9 source "fs/ext2/Kconfig"
  10 source "fs/ext3/Kconfig"
  11 source "fs/ext4/Kconfig"
  12
  13 config FS_XIP
  14 # execute in place
  15         bool
  16         depends on EXT2_FS_XIP
  17         default y
  18
  19 source "fs/jbd/Kconfig"
  20 source "fs/jbd2/Kconfig"
  21
  22 config FS_MBCACHE
  23 # Meta block cache for Extended Attributes (ext2/ext3/ext4)
  24         tristate
  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
  29
  30 source "fs/reiserfs/Kconfig"
  31 source "fs/jfs/Kconfig"
  32
  33 config FS_POSIX_ACL
  34 # Posix ACL utility routines (for now, only ext2/ext3/jfs/reiserfs/nfs4)
  35 #
  36 # NOTE: you can implement Posix ACLs without these helpers (XFS does).
  37 #       Never use this symbol for ifdefs.
  38 #
  39         bool
  40         default n
  41
  42 config FILE_LOCKING
  43         bool "Enable POSIX file locking API" if EMBEDDED
  44         default y
  45         help
  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.
  49
  50 source "fs/xfs/Kconfig"
  51 source "fs/gfs2/Kconfig"
  52 source "fs/ocfs2/Kconfig"
  53 source "fs/btrfs/Kconfig"
  54
  55 endif # BLOCK
  56
  57 source "fs/notify/Kconfig"
  58
  59 config QUOTA
  60         bool "Quota support"
  61         help
  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
  66           shutdown.
  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.
  71
  72 config QUOTA_NETLINK_INTERFACE
  73         bool "Report quota messages through netlink interface"
  74         depends on QUOTA && NET
  75         help
  76           If you say Y here, quota warnings (about exceeding softlimit, reaching
  77           hardlimit, etc.) will be reported through netlink interface. If unsure,
  78           say Y.
  79
  80 config PRINT_QUOTA_WARNING
  81         bool "Print quota warnings to console (OBSOLETE)"
  82         depends on QUOTA
  83         default y
  84         help
  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.
  89
  90 # Generic support for tree structured quota files. Seleted when needed.
  91 config QUOTA_TREE
  92          tristate
  93
  94 config QFMT_V1
  95         tristate "Old quota format support"
  96         depends on QUOTA
  97         help
  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
 100           format say Y here.
 101
 102 config QFMT_V2
 103         tristate "Quota format v2 support"
 104         depends on QUOTA
 105         select QUOTA_TREE
 106         help
 107           This quota format allows using quotas with 32-bit UIDs/GIDs. If you
 108           need this functionality say Y here.
 109
 110 config QUOTACTL
 111         bool
 112         depends on XFS_QUOTA || QUOTA
 113         default y
 114
 115 source "fs/autofs/Kconfig"
 116 source "fs/autofs4/Kconfig"
 117 source "fs/fuse/Kconfig"
 118
 119 config GENERIC_ACL
 120         bool
 121         select FS_POSIX_ACL
 122
 123 if BLOCK
 124 menu "CD-ROM/DVD Filesystems"
 125
 126 source "fs/isofs/Kconfig"
 127 source "fs/udf/Kconfig"
 128
 129 endmenu
 130 endif # BLOCK
 131
 132 if BLOCK
 133 menu "DOS/FAT/NT Filesystems"
 134
 135 source "fs/fat/Kconfig"
 136 source "fs/ntfs/Kconfig"
 137
 138 endmenu
 139 endif # BLOCK
 140
 141 menu "Pseudo filesystems"
 142
 143 source "fs/proc/Kconfig"
 144 source "fs/sysfs/Kconfig"
 145
 146 config TMPFS
 147         bool "Virtual memory file system support (former shm fs)"
 148         help
 149           Tmpfs is a file system which keeps all files in virtual memory.
 150
 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
 154           lost.
 155
 156           See <file:Documentation/filesystems/tmpfs.txt> for details.
 157
 158 config TMPFS_POSIX_ACL
 159         bool "Tmpfs POSIX Access Control Lists"
 160         depends on TMPFS
 161         select GENERIC_ACL
 162         help
 163           POSIX Access Control Lists (ACLs) support permissions for users and
 164           groups beyond the owner/group/world scheme.
 165
 166           To learn more about Access Control Lists, visit the POSIX ACLs for
 167           Linux website <http://acl.bestbits.at/>.
 168
 169           If you don't know what Access Control Lists are, say N.
 170
 171 config HUGETLBFS
 172         bool "HugeTLB file system support"
 173         depends on X86 || IA64 || PPC64 || SPARC64 || (SUPERH && MMU) || \
 174                    (S390 && 64BIT) || BROKEN
 175         help
 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.
 179
 180           If unsure, say N.
 181
 182 config HUGETLB_PAGE
 183         def_bool HUGETLBFS
 184
 185 source "fs/configfs/Kconfig"
 186
 187 endmenu
 188
 189 menuconfig MISC_FILESYSTEMS
 190         bool "Miscellaneous filesystems"
 191         default y
 192         ---help---
 193           Say Y here to get to see options for various miscellaneous
 194           filesystems, such as filesystems that came from other
 195           operating systems.
 196
 197           This option alone does not add any kernel code.
 198
 199           If you say N, all options in this submenu will be skipped and
 200           disabled; if unsure, say Y here.
 201
 202 if MISC_FILESYSTEMS
 203
 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
 216 config CRAMFS
 217         tristate "Compressed ROM file system support (cramfs)"
 218         depends on BLOCK
 219         select ZLIB_INFLATE
 220         help
 221           Saying Y here includes support for CramFs (Compressed ROM File
 222           System).  CramFs is designed to be a simple, small, and compressed
 223           file system for ROM based embedded systems.  CramFs is read-only,
 224           limited to 256MB file systems (with 16MB files), and doesn't support
 225           16/32 bits uid/gid, hard links and timestamps.
 226
 227           See <file:Documentation/filesystems/cramfs.txt> and
 228           <file:fs/cramfs/README> for further information.
 229
 230           To compile this as a module, choose M here: the module will be called
 231           cramfs.  Note that the root file system (the one containing the
 232           directory /) cannot be compiled as a module.
 233
 234           If unsure, say N.
 235
 236 config SQUASHFS
 237         tristate "SquashFS 4.0 - Squashed file system support"
 238         depends on BLOCK
 239         select ZLIB_INFLATE
 240         help
 241           Saying Y here includes support for SquashFS 4.0 (a Compressed
 242           Read-Only File System).  Squashfs is a highly compressed read-only
 243           filesystem for Linux.  It uses zlib compression to compress both
 244           files, inodes and directories.  Inodes in the system are very small
 245           and all blocks are packed to minimise data overhead. Block sizes
 246           greater than 4K are supported up to a maximum of 1 Mbytes (default
 247           block size 128K).  SquashFS 4.0 supports 64 bit filesystems and files
 248           (larger than 4GB), full uid/gid information, hard links and
 249           timestamps.
 250
 251           Squashfs is intended for general read-only filesystem use, for
 252           archival use (i.e. in cases where a .tar.gz file may be used), and in
 253           embedded systems where low overhead is needed.  Further information
 254           and tools are available from http://squashfs.sourceforge.net.
 255
 256           If you want to compile this as a module ( = code which can be
 257           inserted in and removed from the running kernel whenever you want),
 258           say M here and read <file:Documentation/modules.txt>.  The module
 259           will be called squashfs.  Note that the root file system (the one
 260           containing the directory /) cannot be compiled as a module.
 261
 262           If unsure, say N.
 263
 264 config SQUASHFS_EMBEDDED
 265
 266         bool "Additional option for memory-constrained systems"
 267         depends on SQUASHFS
 268         default n
 269         help
 270           Saying Y here allows you to specify cache size.
 271
 272           If unsure, say N.
 273
 274 config SQUASHFS_FRAGMENT_CACHE_SIZE
 275         int "Number of fragments cached" if SQUASHFS_EMBEDDED
 276         depends on SQUASHFS
 277         default "3"
 278         help
 279           By default SquashFS caches the last 3 fragments read from
 280           the filesystem.  Increasing this amount may mean SquashFS
 281           has to re-read fragments less often from disk, at the expense
 282           of extra system memory.  Decreasing this amount will mean
 283           SquashFS uses less memory at the expense of extra reads from disk.
 284
 285           Note there must be at least one cached fragment.  Anything
 286           much more than three will probably not make much difference.
 287
 288 config VXFS_FS
 289         tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
 290         depends on BLOCK
 291         help
 292           FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
 293           file system format.  VERITAS VxFS(TM) is the standard file system
 294           of SCO UnixWare (and possibly others) and optionally available
 295           for Sunsoft Solaris, HP-UX and many other operating systems.
 296           Currently only readonly access is supported.
 297
 298           NOTE: the file system type as used by mount(1), mount(2) and
 299           fstab(5) is 'vxfs' as it describes the file system format, not
 300           the actual driver.
 301
 302           To compile this as a module, choose M here: the module will be
 303           called freevxfs.  If unsure, say N.
 304
 305 config MINIX_FS
 306         tristate "Minix file system support"
 307         depends on BLOCK
 308         help
 309           Minix is a simple operating system used in many classes about OS's.
 310           The minix file system (method to organize files on a hard disk
 311           partition or a floppy disk) was the original file system for Linux,
 312           but has been superseded by the second extended file system ext2fs.
 313           You don't want to use the minix file system on your hard disk
 314           because of certain built-in restrictions, but it is sometimes found
 315           on older Linux floppy disks.  This option will enlarge your kernel
 316           by about 28 KB. If unsure, say N.
 317
 318           To compile this file system support as a module, choose M here: the
 319           module will be called minix.  Note that the file system of your root
 320           partition (the one containing the directory /) cannot be compiled as
 321           a module.
 322
 323 config OMFS_FS
 324         tristate "SonicBlue Optimized MPEG File System support"
 325         depends on BLOCK
 326         select CRC_ITU_T
 327         help
 328           This is the proprietary file system used by the Rio Karma music
 329           player and ReplayTV DVR.  Despite the name, this filesystem is not
 330           more efficient than a standard FS for MPEG files, in fact likely
 331           the opposite is true.  Say Y if you have either of these devices
 332           and wish to mount its disk.
 333
 334           To compile this file system support as a module, choose M here: the
 335           module will be called omfs.  If unsure, say N.
 336
 337 config HPFS_FS
 338         tristate "OS/2 HPFS file system support"
 339         depends on BLOCK
 340         help
 341           OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
 342           is the file system used for organizing files on OS/2 hard disk
 343           partitions. Say Y if you want to be able to read files from and
 344           write files to an OS/2 HPFS partition on your hard drive. OS/2
 345           floppies however are in regular MSDOS format, so you don't need this
 346           option in order to be able to read them. Read
 347           <file:Documentation/filesystems/hpfs.txt>.
 348
 349           To compile this file system support as a module, choose M here: the
 350           module will be called hpfs.  If unsure, say N.
 351
 352
 353 config QNX4FS_FS
 354         tristate "QNX4 file system support (read only)"
 355         depends on BLOCK
 356         help
 357           This is the file system used by the real-time operating systems
 358           QNX 4 and QNX 6 (the latter is also called QNX RTP).
 359           Further information is available at <http://www.qnx.com/>.
 360           Say Y if you intend to mount QNX hard disks or floppies.
 361           Unless you say Y to "QNX4FS read-write support" below, you will
 362           only be able to read these file systems.
 363
 364           To compile this file system support as a module, choose M here: the
 365           module will be called qnx4.
 366
 367           If you don't know whether you need it, then you don't need it:
 368           answer N.
 369
 370 config QNX4FS_RW
 371         bool "QNX4FS write support (DANGEROUS)"
 372         depends on QNX4FS_FS && EXPERIMENTAL && BROKEN
 373         help
 374           Say Y if you want to test write support for QNX4 file systems.
 375
 376           It's currently broken, so for now:
 377           answer N.
 378
 379 config ROMFS_FS
 380         tristate "ROM file system support"
 381         depends on BLOCK
 382         ---help---
 383           This is a very small read-only file system mainly intended for
 384           initial ram disks of installation disks, but it could be used for
 385           other read-only media as well.  Read
 386           <file:Documentation/filesystems/romfs.txt> for details.
 387
 388           To compile this file system support as a module, choose M here: the
 389           module will be called romfs.  Note that the file system of your
 390           root partition (the one containing the directory /) cannot be a
 391           module.
 392
 393           If you don't know whether you need it, then you don't need it:
 394           answer N.
 395
 396
 397 config SYSV_FS
 398         tristate "System V/Xenix/V7/Coherent file system support"
 399         depends on BLOCK
 400         help
 401           SCO, Xenix and Coherent are commercial Unix systems for Intel
 402           machines, and Version 7 was used on the DEC PDP-11. Saying Y
 403           here would allow you to read from their floppies and hard disk
 404           partitions.
 405
 406           If you have floppies or hard disk partitions like that, it is likely
 407           that they contain binaries from those other Unix systems; in order
 408           to run these binaries, you will want to install linux-abi which is
 409           a set of kernel modules that lets you run SCO, Xenix, Wyse,
 410           UnixWare, Dell Unix and System V programs under Linux.  It is
 411           available via FTP (user: ftp) from
 412           <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
 413           NOTE: that will work only for binaries from Intel-based systems;
 414           PDP ones will have to wait until somebody ports Linux to -11 ;-)
 415
 416           If you only intend to mount files from some other Unix over the
 417           network using NFS, you don't need the System V file system support
 418           (but you need NFS file system support obviously).
 419
 420           Note that this option is generally not needed for floppies, since a
 421           good portable way to transport files and directories between unixes
 422           (and even other operating systems) is given by the tar program ("man
 423           tar" or preferably "info tar").  Note also that this option has
 424           nothing whatsoever to do with the option "System V IPC". Read about
 425           the System V file system in
 426           <file:Documentation/filesystems/sysv-fs.txt>.
 427           Saying Y here will enlarge your kernel by about 27 KB.
 428
 429           To compile this as a module, choose M here: the module will be called
 430           sysv.
 431
 432           If you haven't heard about all of this before, it's safe to say N.
 433
 434
 435 config UFS_FS
 436         tristate "UFS file system support (read only)"
 437         depends on BLOCK
 438         help
 439           BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
 440           OpenBSD and NeXTstep) use a file system called UFS. Some System V
 441           Unixes can create and mount hard disk partitions and diskettes using
 442           this file system as well. Saying Y here will allow you to read from
 443           these partitions; if you also want to write to them, say Y to the
 444           experimental "UFS file system write support", below. Please read the
 445           file <file:Documentation/filesystems/ufs.txt> for more information.
 446
 447           The recently released UFS2 variant (used in FreeBSD 5.x) is
 448           READ-ONLY supported.
 449
 450           Note that this option is generally not needed for floppies, since a
 451           good portable way to transport files and directories between unixes
 452           (and even other operating systems) is given by the tar program ("man
 453           tar" or preferably "info tar").
 454
 455           When accessing NeXTstep files, you may need to convert them from the
 456           NeXT character set to the Latin1 character set; use the program
 457           recode ("info recode") for this purpose.
 458
 459           To compile the UFS file system support as a module, choose M here: the
 460           module will be called ufs.
 461
 462           If you haven't heard about all of this before, it's safe to say N.
 463
 464 config UFS_FS_WRITE
 465         bool "UFS file system write support (DANGEROUS)"
 466         depends on UFS_FS && EXPERIMENTAL
 467         help
 468           Say Y here if you want to try writing to UFS partitions. This is
 469           experimental, so you should back up your UFS partitions beforehand.
 470
 471 config UFS_DEBUG
 472         bool "UFS debugging"
 473         depends on UFS_FS
 474         help
 475           If you are experiencing any problems with the UFS filesystem, say
 476           Y here.  This will result in _many_ additional debugging messages to be
 477           written to the system log.
 478
 479 endif # MISC_FILESYSTEMS
 480
 481 menuconfig NETWORK_FILESYSTEMS
 482         bool "Network File Systems"
 483         default y
 484         depends on NET
 485         ---help---
 486           Say Y here to get to see options for network filesystems and
 487           filesystem-related networking code, such as NFS daemon and
 488           RPCSEC security modules.
 489
 490           This option alone does not add any kernel code.
 491
 492           If you say N, all options in this submenu will be skipped and
 493           disabled; if unsure, say Y here.
 494
 495 if NETWORK_FILESYSTEMS
 496
 497 config NFS_FS
 498         tristate "NFS client support"
 499         depends on INET
 500         select LOCKD
 501         select SUNRPC
 502         select NFS_ACL_SUPPORT if NFS_V3_ACL
 503         help
 504           Choose Y here if you want to access files residing on other
 505           computers using Sun's Network File System protocol.  To compile
 506           this file system support as a module, choose M here: the module
 507           will be called nfs.
 508
 509           To mount file systems exported by NFS servers, you also need to
 510           install the user space mount.nfs command which can be found in
 511           the Linux nfs-utils package, available from http://linux-nfs.org/.
 512           Information about using the mount command is available in the
 513           mount(8) man page.  More detail about the Linux NFS client
 514           implementation is available via the nfs(5) man page.
 515
 516           Below you can choose which versions of the NFS protocol are
 517           available in the kernel to mount NFS servers.  Support for NFS
 518           version 2 (RFC 1094) is always available when NFS_FS is selected.
 519
 520           To configure a system which mounts its root file system via NFS
 521           at boot time, say Y here, select "Kernel level IP
 522           autoconfiguration" in the NETWORK menu, and select "Root file
 523           system on NFS" below.  You cannot compile this file system as a
 524           module in this case.
 525
 526           If unsure, say N.
 527
 528 config NFS_V3
 529         bool "NFS client support for NFS version 3"
 530         depends on NFS_FS
 531         help
 532           This option enables support for version 3 of the NFS protocol
 533           (RFC 1813) in the kernel's NFS client.
 534
 535           If unsure, say Y.
 536
 537 config NFS_V3_ACL
 538         bool "NFS client support for the NFSv3 ACL protocol extension"
 539         depends on NFS_V3
 540         help
 541           Some NFS servers support an auxiliary NFSv3 ACL protocol that
 542           Sun added to Solaris but never became an official part of the
 543           NFS version 3 protocol.  This protocol extension allows
 544           applications on NFS clients to manipulate POSIX Access Control
 545           Lists on files residing on NFS servers.  NFS servers enforce
 546           ACLs on local files whether this protocol is available or not.
 547
 548           Choose Y here if your NFS server supports the Solaris NFSv3 ACL
 549           protocol extension and you want your NFS client to allow
 550           applications to access and modify ACLs on files on the server.
 551
 552           Most NFS servers don't support the Solaris NFSv3 ACL protocol
 553           extension.  You can choose N here or specify the "noacl" mount
 554           option to prevent your NFS client from trying to use the NFSv3
 555           ACL protocol.
 556
 557           If unsure, say N.
 558
 559 config NFS_V4
 560         bool "NFS client support for NFS version 4 (EXPERIMENTAL)"
 561         depends on NFS_FS && EXPERIMENTAL
 562         select RPCSEC_GSS_KRB5
 563         help
 564           This option enables support for version 4 of the NFS protocol
 565           (RFC 3530) in the kernel's NFS client.
 566
 567           To mount NFS servers using NFSv4, you also need to install user
 568           space programs which can be found in the Linux nfs-utils package,
 569           available from http://linux-nfs.org/.
 570
 571           If unsure, say N.
 572
 573 config ROOT_NFS
 574         bool "Root file system on NFS"
 575         depends on NFS_FS=y && IP_PNP
 576         help
 577           If you want your system to mount its root file system via NFS,
 578           choose Y here.  This is common practice for managing systems
 579           without local permanent storage.  For details, read
 580           <file:Documentation/filesystems/nfsroot.txt>.
 581
 582           Most people say N here.
 583
 584 config NFSD
 585         tristate "NFS server support"
 586         depends on INET
 587         select LOCKD
 588         select SUNRPC
 589         select EXPORTFS
 590         select NFS_ACL_SUPPORT if NFSD_V2_ACL
 591         help
 592           Choose Y here if you want to allow other computers to access
 593           files residing on this system using Sun's Network File System
 594           protocol.  To compile the NFS server support as a module,
 595           choose M here: the module will be called nfsd.
 596
 597           You may choose to use a user-space NFS server instead, in which
 598           case you can choose N here.
 599
 600           To export local file systems using NFS, you also need to install
 601           user space programs which can be found in the Linux nfs-utils
 602           package, available from http://linux-nfs.org/.  More detail about
 603           the Linux NFS server implementation is available via the
 604           exports(5) man page.
 605
 606           Below you can choose which versions of the NFS protocol are
 607           available to clients mounting the NFS server on this system.
 608           Support for NFS version 2 (RFC 1094) is always available when
 609           CONFIG_NFSD is selected.
 610
 611           If unsure, say N.
 612
 613 config NFSD_V2_ACL
 614         bool
 615         depends on NFSD
 616
 617 config NFSD_V3
 618         bool "NFS server support for NFS version 3"
 619         depends on NFSD
 620         help
 621           This option enables support in your system's NFS server for
 622           version 3 of the NFS protocol (RFC 1813).
 623
 624           If unsure, say Y.
 625
 626 config NFSD_V3_ACL
 627         bool "NFS server support for the NFSv3 ACL protocol extension"
 628         depends on NFSD_V3
 629         select NFSD_V2_ACL
 630         help
 631           Solaris NFS servers support an auxiliary NFSv3 ACL protocol that
 632           never became an official part of the NFS version 3 protocol.
 633           This protocol extension allows applications on NFS clients to
 634           manipulate POSIX Access Control Lists on files residing on NFS
 635           servers.  NFS servers enforce POSIX ACLs on local files whether
 636           this protocol is available or not.
 637
 638           This option enables support in your system's NFS server for the
 639           NFSv3 ACL protocol extension allowing NFS clients to manipulate
 640           POSIX ACLs on files exported by your system's NFS server.  NFS
 641           clients which support the Solaris NFSv3 ACL protocol can then
 642           access and modify ACLs on your NFS server.
 643
 644           To store ACLs on your NFS server, you also need to enable ACL-
 645           related CONFIG options for your local file systems of choice.
 646
 647           If unsure, say N.
 648
 649 config NFSD_V4
 650         bool "NFS server support for NFS version 4 (EXPERIMENTAL)"
 651         depends on NFSD && PROC_FS && EXPERIMENTAL
 652         select NFSD_V3
 653         select FS_POSIX_ACL
 654         select RPCSEC_GSS_KRB5
 655         help
 656           This option enables support in your system's NFS server for
 657           version 4 of the NFS protocol (RFC 3530).
 658
 659           To export files using NFSv4, you need to install additional user
 660           space programs which can be found in the Linux nfs-utils package,
 661           available from http://linux-nfs.org/.
 662
 663           If unsure, say N.
 664
 665 config LOCKD
 666         tristate
 667
 668 config LOCKD_V4
 669         bool
 670         depends on NFSD_V3 || NFS_V3
 671         default y
 672
 673 config EXPORTFS
 674         tristate
 675
 676 config NFS_ACL_SUPPORT
 677         tristate
 678         select FS_POSIX_ACL
 679
 680 config NFS_COMMON
 681         bool
 682         depends on NFSD || NFS_FS
 683         default y
 684
 685 config SUNRPC
 686         tristate
 687
 688 config SUNRPC_GSS
 689         tristate
 690
 691 config SUNRPC_XPRT_RDMA
 692         tristate
 693         depends on SUNRPC && INFINIBAND && EXPERIMENTAL
 694         default SUNRPC && INFINIBAND
 695         help
 696           This option enables an RPC client transport capability that
 697           allows the NFS client to mount servers via an RDMA-enabled
 698           transport.
 699
 700           To compile RPC client RDMA transport support as a module,
 701           choose M here: the module will be called xprtrdma.
 702
 703           If unsure, say N.
 704
 705 config SUNRPC_REGISTER_V4
 706         bool "Register local RPC services via rpcbind v4 (EXPERIMENTAL)"
 707         depends on SUNRPC && EXPERIMENTAL
 708         default n
 709         help
 710           Sun added support for registering RPC services at an IPv6
 711           address by creating two new versions of the rpcbind protocol
 712           (RFC 1833).
 713
 714           This option enables support in the kernel RPC server for
 715           registering kernel RPC services via version 4 of the rpcbind
 716           protocol.  If you enable this option, you must run a portmapper
 717           daemon that supports rpcbind protocol version 4.
 718
 719           Serving NFS over IPv6 from knfsd (the kernel's NFS server)
 720           requires that you enable this option and use a portmapper that
 721           supports rpcbind version 4.
 722
 723           If unsure, say N to get traditional behavior (register kernel
 724           RPC services using only rpcbind version 2).  Distributions
 725           using the legacy Linux portmapper daemon must say N here.
 726
 727 config RPCSEC_GSS_KRB5
 728         tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
 729         depends on SUNRPC && EXPERIMENTAL
 730         select SUNRPC_GSS
 731         select CRYPTO
 732         select CRYPTO_MD5
 733         select CRYPTO_DES
 734         select CRYPTO_CBC
 735         help
 736           Choose Y here to enable Secure RPC using the Kerberos version 5
 737           GSS-API mechanism (RFC 1964).
 738
 739           Secure RPC calls with Kerberos require an auxiliary user-space
 740           daemon which may be found in the Linux nfs-utils package
 741           available from http://linux-nfs.org/.  In addition, user-space
 742           Kerberos support should be installed.
 743
 744           If unsure, say N.
 745
 746 config RPCSEC_GSS_SPKM3
 747         tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
 748         depends on SUNRPC && EXPERIMENTAL
 749         select SUNRPC_GSS
 750         select CRYPTO
 751         select CRYPTO_MD5
 752         select CRYPTO_DES
 753         select CRYPTO_CAST5
 754         select CRYPTO_CBC
 755         help
 756           Choose Y here to enable Secure RPC using the SPKM3 public key
 757           GSS-API mechansim (RFC 2025).
 758
 759           Secure RPC calls with SPKM3 require an auxiliary userspace
 760           daemon which may be found in the Linux nfs-utils package
 761           available from http://linux-nfs.org/.
 762
 763           If unsure, say N.
 764
 765 config SMB_FS
 766         tristate "SMB file system support (OBSOLETE, please use CIFS)"
 767         depends on INET
 768         select NLS
 769         help
 770           SMB (Server Message Block) is the protocol Windows for Workgroups
 771           (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
 772           files and printers over local networks.  Saying Y here allows you to
 773           mount their file systems (often called "shares" in this context) and
 774           access them just like any other Unix directory.  Currently, this
 775           works only if the Windows machines use TCP/IP as the underlying
 776           transport protocol, and not NetBEUI.  For details, read
 777           <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
 778           available from <http://www.tldp.org/docs.html#howto>.
 779
 780           Note: if you just want your box to act as an SMB *server* and make
 781           files and printing services available to Windows clients (which need
 782           to have a TCP/IP stack), you don't need to say Y here; you can use
 783           the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
 784           for that.
 785
 786           General information about how to connect Linux, Windows machines and
 787           Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
 788
 789           To compile the SMB support as a module, choose M here:
 790           the module will be called smbfs.  Most people say N, however.
 791
 792 config SMB_NLS_DEFAULT
 793         bool "Use a default NLS"
 794         depends on SMB_FS
 795         help
 796           Enabling this will make smbfs use nls translations by default. You
 797           need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
 798           settings and you need to give the default nls for the SMB server as
 799           CONFIG_SMB_NLS_REMOTE.
 800
 801           The nls settings can be changed at mount time, if your smbmount
 802           supports that, using the codepage and iocharset parameters.
 803
 804           smbmount from samba 2.2.0 or later supports this.
 805
 806 config SMB_NLS_REMOTE
 807         string "Default Remote NLS Option"
 808         depends on SMB_NLS_DEFAULT
 809         default "cp437"
 810         help
 811           This setting allows you to specify a default value for which
 812           codepage the server uses. If this field is left blank no
 813           translations will be done by default. The local codepage/charset
 814           default to CONFIG_NLS_DEFAULT.
 815
 816           The nls settings can be changed at mount time, if your smbmount
 817           supports that, using the codepage and iocharset parameters.
 818
 819           smbmount from samba 2.2.0 or later supports this.
 820
 821 source "fs/cifs/Kconfig"
 822
 823 config NCP_FS
 824         tristate "NCP file system support (to mount NetWare volumes)"
 825         depends on IPX!=n || INET
 826         help
 827           NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
 828           used by Novell NetWare clients to talk to file servers.  It is to
 829           IPX what NFS is to TCP/IP, if that helps.  Saying Y here allows you
 830           to mount NetWare file server volumes and to access them just like
 831           any other Unix directory.  For details, please read the file
 832           <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
 833           the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
 834
 835           You do not have to say Y here if you want your Linux box to act as a
 836           file *server* for Novell NetWare clients.
 837
 838           General information about how to connect Linux, Windows machines and
 839           Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
 840
 841           To compile this as a module, choose M here: the module will be called
 842           ncpfs.  Say N unless you are connected to a Novell network.
 843
 844 source "fs/ncpfs/Kconfig"
 845
 846 config CODA_FS
 847         tristate "Coda file system support (advanced network fs)"
 848         depends on INET
 849         help
 850           Coda is an advanced network file system, similar to NFS in that it
 851           enables you to mount file systems of a remote server and access them
 852           with regular Unix commands as if they were sitting on your hard
 853           disk.  Coda has several advantages over NFS: support for
 854           disconnected operation (e.g. for laptops), read/write server
 855           replication, security model for authentication and encryption,
 856           persistent client caches and write back caching.
 857
 858           If you say Y here, your Linux box will be able to act as a Coda
 859           *client*.  You will need user level code as well, both for the
 860           client and server.  Servers are currently user level, i.e. they need
 861           no kernel support.  Please read
 862           <file:Documentation/filesystems/coda.txt> and check out the Coda
 863           home page <http://www.coda.cs.cmu.edu/>.
 864
 865           To compile the coda client support as a module, choose M here: the
 866           module will be called coda.
 867
 868 config AFS_FS
 869         tristate "Andrew File System support (AFS) (EXPERIMENTAL)"
 870         depends on INET && EXPERIMENTAL
 871         select AF_RXRPC
 872         help
 873           If you say Y here, you will get an experimental Andrew File System
 874           driver. It currently only supports unsecured read-only AFS access.
 875
 876           See <file:Documentation/filesystems/afs.txt> for more information.
 877
 878           If unsure, say N.
 879
 880 config AFS_DEBUG
 881         bool "AFS dynamic debugging"
 882         depends on AFS_FS
 883         help
 884           Say Y here to make runtime controllable debugging messages appear.
 885
 886           See <file:Documentation/filesystems/afs.txt> for more information.
 887
 888           If unsure, say N.
 889
 890 config 9P_FS
 891         tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
 892         depends on INET && NET_9P && EXPERIMENTAL
 893         help
 894           If you say Y here, you will get experimental support for
 895           Plan 9 resource sharing via the 9P2000 protocol.
 896
 897           See <http://v9fs.sf.net> for more information.
 898
 899           If unsure, say N.
 900
 901 endif # NETWORK_FILESYSTEMS
 902
 903 if BLOCK
 904 menu "Partition Types"
 905
 906 source "fs/partitions/Kconfig"
 907
 908 endmenu
 909 endif
 910
 911 source "fs/nls/Kconfig"
 912 source "fs/dlm/Kconfig"
 913
 914 endmenu