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
 208 config HFS_FS
 209         tristate "Apple Macintosh file system support (EXPERIMENTAL)"
 210         depends on BLOCK && EXPERIMENTAL
 211         select NLS
 212         help
 213           If you say Y here, you will be able to mount Macintosh-formatted
 214           floppy disks and hard drive partitions with full read-write access.
 215           Please read <file:Documentation/filesystems/hfs.txt> to learn about
 216           the available mount options.
 217
 218           To compile this file system support as a module, choose M here: the
 219           module will be called hfs.
 220
 221 config HFSPLUS_FS
 222         tristate "Apple Extended HFS file system support"
 223         depends on BLOCK
 224         select NLS
 225         select NLS_UTF8
 226         help
 227           If you say Y here, you will be able to mount extended format
 228           Macintosh-formatted hard drive partitions with full read-write access.
 229
 230           This file system is often called HFS+ and was introduced with
 231           MacOS 8. It includes all Mac specific filesystem data such as
 232           data forks and creator codes, but it also has several UNIX
 233           style features such as file ownership and permissions.
 234
 235 config BEFS_FS
 236         tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)"
 237         depends on BLOCK && EXPERIMENTAL
 238         select NLS
 239         help
 240           The BeOS File System (BeFS) is the native file system of Be, Inc's
 241           BeOS. Notable features include support for arbitrary attributes
 242           on files and directories, and database-like indices on selected
 243           attributes. (Also note that this driver doesn't make those features
 244           available at this time). It is a 64 bit filesystem, so it supports
 245           extremely large volumes and files.
 246
 247           If you use this filesystem, you should also say Y to at least one
 248           of the NLS (native language support) options below.
 249
 250           If you don't know what this is about, say N.
 251
 252           To compile this as a module, choose M here: the module will be
 253           called befs.
 254
 255 config BEFS_DEBUG
 256         bool "Debug BeFS"
 257         depends on BEFS_FS
 258         help
 259           If you say Y here, you can use the 'debug' mount option to enable
 260           debugging output from the driver.
 261
 262 config BFS_FS
 263         tristate "BFS file system support (EXPERIMENTAL)"
 264         depends on BLOCK && EXPERIMENTAL
 265         help
 266           Boot File System (BFS) is a file system used under SCO UnixWare to
 267           allow the bootloader access to the kernel image and other important
 268           files during the boot process.  It is usually mounted under /stand
 269           and corresponds to the slice marked as "STAND" in the UnixWare
 270           partition.  You should say Y if you want to read or write the files
 271           on your /stand slice from within Linux.  You then also need to say Y
 272           to "UnixWare slices support", below.  More information about the BFS
 273           file system is contained in the file
 274           <file:Documentation/filesystems/bfs.txt>.
 275
 276           If you don't know what this is about, say N.
 277
 278           To compile this as a module, choose M here: the module will be called
 279           bfs.  Note that the file system of your root partition (the one
 280           containing the directory /) cannot be compiled as a module.
 281
 282
 283
 284 config EFS_FS
 285         tristate "EFS file system support (read only) (EXPERIMENTAL)"
 286         depends on BLOCK && EXPERIMENTAL
 287         help
 288           EFS is an older file system used for non-ISO9660 CD-ROMs and hard
 289           disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
 290           uses the XFS file system for hard disk partitions however).
 291
 292           This implementation only offers read-only access. If you don't know
 293           what all this is about, it's safe to say N. For more information
 294           about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
 295
 296           To compile the EFS file system support as a module, choose M here: the
 297           module will be called efs.
 298
 299 source "fs/jffs2/Kconfig"
 300 # UBIFS File system configuration
 301 source "fs/ubifs/Kconfig"
 302
 303 config CRAMFS
 304         tristate "Compressed ROM file system support (cramfs)"
 305         depends on BLOCK
 306         select ZLIB_INFLATE
 307         help
 308           Saying Y here includes support for CramFs (Compressed ROM File
 309           System).  CramFs is designed to be a simple, small, and compressed
 310           file system for ROM based embedded systems.  CramFs is read-only,
 311           limited to 256MB file systems (with 16MB files), and doesn't support
 312           16/32 bits uid/gid, hard links and timestamps.
 313
 314           See <file:Documentation/filesystems/cramfs.txt> and
 315           <file:fs/cramfs/README> for further information.
 316
 317           To compile this as a module, choose M here: the module will be called
 318           cramfs.  Note that the root file system (the one containing the
 319           directory /) cannot be compiled as a module.
 320
 321           If unsure, say N.
 322
 323 config SQUASHFS
 324         tristate "SquashFS 4.0 - Squashed file system support"
 325         depends on BLOCK
 326         select ZLIB_INFLATE
 327         help
 328           Saying Y here includes support for SquashFS 4.0 (a Compressed
 329           Read-Only File System).  Squashfs is a highly compressed read-only
 330           filesystem for Linux.  It uses zlib compression to compress both
 331           files, inodes and directories.  Inodes in the system are very small
 332           and all blocks are packed to minimise data overhead. Block sizes
 333           greater than 4K are supported up to a maximum of 1 Mbytes (default
 334           block size 128K).  SquashFS 4.0 supports 64 bit filesystems and files
 335           (larger than 4GB), full uid/gid information, hard links and
 336           timestamps.
 337
 338           Squashfs is intended for general read-only filesystem use, for
 339           archival use (i.e. in cases where a .tar.gz file may be used), and in
 340           embedded systems where low overhead is needed.  Further information
 341           and tools are available from http://squashfs.sourceforge.net.
 342
 343           If you want to compile this as a module ( = code which can be
 344           inserted in and removed from the running kernel whenever you want),
 345           say M here and read <file:Documentation/modules.txt>.  The module
 346           will be called squashfs.  Note that the root file system (the one
 347           containing the directory /) cannot be compiled as a module.
 348
 349           If unsure, say N.
 350
 351 config SQUASHFS_EMBEDDED
 352
 353         bool "Additional option for memory-constrained systems"
 354         depends on SQUASHFS
 355         default n
 356         help
 357           Saying Y here allows you to specify cache size.
 358
 359           If unsure, say N.
 360
 361 config SQUASHFS_FRAGMENT_CACHE_SIZE
 362         int "Number of fragments cached" if SQUASHFS_EMBEDDED
 363         depends on SQUASHFS
 364         default "3"
 365         help
 366           By default SquashFS caches the last 3 fragments read from
 367           the filesystem.  Increasing this amount may mean SquashFS
 368           has to re-read fragments less often from disk, at the expense
 369           of extra system memory.  Decreasing this amount will mean
 370           SquashFS uses less memory at the expense of extra reads from disk.
 371
 372           Note there must be at least one cached fragment.  Anything
 373           much more than three will probably not make much difference.
 374
 375 config VXFS_FS
 376         tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
 377         depends on BLOCK
 378         help
 379           FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
 380           file system format.  VERITAS VxFS(TM) is the standard file system
 381           of SCO UnixWare (and possibly others) and optionally available
 382           for Sunsoft Solaris, HP-UX and many other operating systems.
 383           Currently only readonly access is supported.
 384
 385           NOTE: the file system type as used by mount(1), mount(2) and
 386           fstab(5) is 'vxfs' as it describes the file system format, not
 387           the actual driver.
 388
 389           To compile this as a module, choose M here: the module will be
 390           called freevxfs.  If unsure, say N.
 391
 392 config MINIX_FS
 393         tristate "Minix file system support"
 394         depends on BLOCK
 395         help
 396           Minix is a simple operating system used in many classes about OS's.
 397           The minix file system (method to organize files on a hard disk
 398           partition or a floppy disk) was the original file system for Linux,
 399           but has been superseded by the second extended file system ext2fs.
 400           You don't want to use the minix file system on your hard disk
 401           because of certain built-in restrictions, but it is sometimes found
 402           on older Linux floppy disks.  This option will enlarge your kernel
 403           by about 28 KB. If unsure, say N.
 404
 405           To compile this file system support as a module, choose M here: the
 406           module will be called minix.  Note that the file system of your root
 407           partition (the one containing the directory /) cannot be compiled as
 408           a module.
 409
 410 config OMFS_FS
 411         tristate "SonicBlue Optimized MPEG File System support"
 412         depends on BLOCK
 413         select CRC_ITU_T
 414         help
 415           This is the proprietary file system used by the Rio Karma music
 416           player and ReplayTV DVR.  Despite the name, this filesystem is not
 417           more efficient than a standard FS for MPEG files, in fact likely
 418           the opposite is true.  Say Y if you have either of these devices
 419           and wish to mount its disk.
 420
 421           To compile this file system support as a module, choose M here: the
 422           module will be called omfs.  If unsure, say N.
 423
 424 config HPFS_FS
 425         tristate "OS/2 HPFS file system support"
 426         depends on BLOCK
 427         help
 428           OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
 429           is the file system used for organizing files on OS/2 hard disk
 430           partitions. Say Y if you want to be able to read files from and
 431           write files to an OS/2 HPFS partition on your hard drive. OS/2
 432           floppies however are in regular MSDOS format, so you don't need this
 433           option in order to be able to read them. Read
 434           <file:Documentation/filesystems/hpfs.txt>.
 435
 436           To compile this file system support as a module, choose M here: the
 437           module will be called hpfs.  If unsure, say N.
 438
 439
 440 config QNX4FS_FS
 441         tristate "QNX4 file system support (read only)"
 442         depends on BLOCK
 443         help
 444           This is the file system used by the real-time operating systems
 445           QNX 4 and QNX 6 (the latter is also called QNX RTP).
 446           Further information is available at <http://www.qnx.com/>.
 447           Say Y if you intend to mount QNX hard disks or floppies.
 448           Unless you say Y to "QNX4FS read-write support" below, you will
 449           only be able to read these file systems.
 450
 451           To compile this file system support as a module, choose M here: the
 452           module will be called qnx4.
 453
 454           If you don't know whether you need it, then you don't need it:
 455           answer N.
 456
 457 config QNX4FS_RW
 458         bool "QNX4FS write support (DANGEROUS)"
 459         depends on QNX4FS_FS && EXPERIMENTAL && BROKEN
 460         help
 461           Say Y if you want to test write support for QNX4 file systems.
 462
 463           It's currently broken, so for now:
 464           answer N.
 465
 466 config ROMFS_FS
 467         tristate "ROM file system support"
 468         depends on BLOCK
 469         ---help---
 470           This is a very small read-only file system mainly intended for
 471           initial ram disks of installation disks, but it could be used for
 472           other read-only media as well.  Read
 473           <file:Documentation/filesystems/romfs.txt> for details.
 474
 475           To compile this file system support as a module, choose M here: the
 476           module will be called romfs.  Note that the file system of your
 477           root partition (the one containing the directory /) cannot be a
 478           module.
 479
 480           If you don't know whether you need it, then you don't need it:
 481           answer N.
 482
 483
 484 config SYSV_FS
 485         tristate "System V/Xenix/V7/Coherent file system support"
 486         depends on BLOCK
 487         help
 488           SCO, Xenix and Coherent are commercial Unix systems for Intel
 489           machines, and Version 7 was used on the DEC PDP-11. Saying Y
 490           here would allow you to read from their floppies and hard disk
 491           partitions.
 492
 493           If you have floppies or hard disk partitions like that, it is likely
 494           that they contain binaries from those other Unix systems; in order
 495           to run these binaries, you will want to install linux-abi which is
 496           a set of kernel modules that lets you run SCO, Xenix, Wyse,
 497           UnixWare, Dell Unix and System V programs under Linux.  It is
 498           available via FTP (user: ftp) from
 499           <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
 500           NOTE: that will work only for binaries from Intel-based systems;
 501           PDP ones will have to wait until somebody ports Linux to -11 ;-)
 502
 503           If you only intend to mount files from some other Unix over the
 504           network using NFS, you don't need the System V file system support
 505           (but you need NFS file system support obviously).
 506
 507           Note that this option is generally not needed for floppies, since a
 508           good portable way to transport files and directories between unixes
 509           (and even other operating systems) is given by the tar program ("man
 510           tar" or preferably "info tar").  Note also that this option has
 511           nothing whatsoever to do with the option "System V IPC". Read about
 512           the System V file system in
 513           <file:Documentation/filesystems/sysv-fs.txt>.
 514           Saying Y here will enlarge your kernel by about 27 KB.
 515
 516           To compile this as a module, choose M here: the module will be called
 517           sysv.
 518
 519           If you haven't heard about all of this before, it's safe to say N.
 520
 521
 522 config UFS_FS
 523         tristate "UFS file system support (read only)"
 524         depends on BLOCK
 525         help
 526           BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
 527           OpenBSD and NeXTstep) use a file system called UFS. Some System V
 528           Unixes can create and mount hard disk partitions and diskettes using
 529           this file system as well. Saying Y here will allow you to read from
 530           these partitions; if you also want to write to them, say Y to the
 531           experimental "UFS file system write support", below. Please read the
 532           file <file:Documentation/filesystems/ufs.txt> for more information.
 533
 534           The recently released UFS2 variant (used in FreeBSD 5.x) is
 535           READ-ONLY supported.
 536
 537           Note that this option is generally not needed for floppies, since a
 538           good portable way to transport files and directories between unixes
 539           (and even other operating systems) is given by the tar program ("man
 540           tar" or preferably "info tar").
 541
 542           When accessing NeXTstep files, you may need to convert them from the
 543           NeXT character set to the Latin1 character set; use the program
 544           recode ("info recode") for this purpose.
 545
 546           To compile the UFS file system support as a module, choose M here: the
 547           module will be called ufs.
 548
 549           If you haven't heard about all of this before, it's safe to say N.
 550
 551 config UFS_FS_WRITE
 552         bool "UFS file system write support (DANGEROUS)"
 553         depends on UFS_FS && EXPERIMENTAL
 554         help
 555           Say Y here if you want to try writing to UFS partitions. This is
 556           experimental, so you should back up your UFS partitions beforehand.
 557
 558 config UFS_DEBUG
 559         bool "UFS debugging"
 560         depends on UFS_FS
 561         help
 562           If you are experiencing any problems with the UFS filesystem, say
 563           Y here.  This will result in _many_ additional debugging messages to be
 564           written to the system log.
 565
 566 endif # MISC_FILESYSTEMS
 567
 568 menuconfig NETWORK_FILESYSTEMS
 569         bool "Network File Systems"
 570         default y
 571         depends on NET
 572         ---help---
 573           Say Y here to get to see options for network filesystems and
 574           filesystem-related networking code, such as NFS daemon and
 575           RPCSEC security modules.
 576
 577           This option alone does not add any kernel code.
 578
 579           If you say N, all options in this submenu will be skipped and
 580           disabled; if unsure, say Y here.
 581
 582 if NETWORK_FILESYSTEMS
 583
 584 config NFS_FS
 585         tristate "NFS client support"
 586         depends on INET
 587         select LOCKD
 588         select SUNRPC
 589         select NFS_ACL_SUPPORT if NFS_V3_ACL
 590         help
 591           Choose Y here if you want to access files residing on other
 592           computers using Sun's Network File System protocol.  To compile
 593           this file system support as a module, choose M here: the module
 594           will be called nfs.
 595
 596           To mount file systems exported by NFS servers, you also need to
 597           install the user space mount.nfs command which can be found in
 598           the Linux nfs-utils package, available from http://linux-nfs.org/.
 599           Information about using the mount command is available in the
 600           mount(8) man page.  More detail about the Linux NFS client
 601           implementation is available via the nfs(5) man page.
 602
 603           Below you can choose which versions of the NFS protocol are
 604           available in the kernel to mount NFS servers.  Support for NFS
 605           version 2 (RFC 1094) is always available when NFS_FS is selected.
 606
 607           To configure a system which mounts its root file system via NFS
 608           at boot time, say Y here, select "Kernel level IP
 609           autoconfiguration" in the NETWORK menu, and select "Root file
 610           system on NFS" below.  You cannot compile this file system as a
 611           module in this case.
 612
 613           If unsure, say N.
 614
 615 config NFS_V3
 616         bool "NFS client support for NFS version 3"
 617         depends on NFS_FS
 618         help
 619           This option enables support for version 3 of the NFS protocol
 620           (RFC 1813) in the kernel's NFS client.
 621
 622           If unsure, say Y.
 623
 624 config NFS_V3_ACL
 625         bool "NFS client support for the NFSv3 ACL protocol extension"
 626         depends on NFS_V3
 627         help
 628           Some NFS servers support an auxiliary NFSv3 ACL protocol that
 629           Sun added to Solaris but never became an official part of the
 630           NFS version 3 protocol.  This protocol extension allows
 631           applications on NFS clients to manipulate POSIX Access Control
 632           Lists on files residing on NFS servers.  NFS servers enforce
 633           ACLs on local files whether this protocol is available or not.
 634
 635           Choose Y here if your NFS server supports the Solaris NFSv3 ACL
 636           protocol extension and you want your NFS client to allow
 637           applications to access and modify ACLs on files on the server.
 638
 639           Most NFS servers don't support the Solaris NFSv3 ACL protocol
 640           extension.  You can choose N here or specify the "noacl" mount
 641           option to prevent your NFS client from trying to use the NFSv3
 642           ACL protocol.
 643
 644           If unsure, say N.
 645
 646 config NFS_V4
 647         bool "NFS client support for NFS version 4 (EXPERIMENTAL)"
 648         depends on NFS_FS && EXPERIMENTAL
 649         select RPCSEC_GSS_KRB5
 650         help
 651           This option enables support for version 4 of the NFS protocol
 652           (RFC 3530) in the kernel's NFS client.
 653
 654           To mount NFS servers using NFSv4, you also need to install user
 655           space programs which can be found in the Linux nfs-utils package,
 656           available from http://linux-nfs.org/.
 657
 658           If unsure, say N.
 659
 660 config ROOT_NFS
 661         bool "Root file system on NFS"
 662         depends on NFS_FS=y && IP_PNP
 663         help
 664           If you want your system to mount its root file system via NFS,
 665           choose Y here.  This is common practice for managing systems
 666           without local permanent storage.  For details, read
 667           <file:Documentation/filesystems/nfsroot.txt>.
 668
 669           Most people say N here.
 670
 671 config NFSD
 672         tristate "NFS server support"
 673         depends on INET
 674         select LOCKD
 675         select SUNRPC
 676         select EXPORTFS
 677         select NFS_ACL_SUPPORT if NFSD_V2_ACL
 678         help
 679           Choose Y here if you want to allow other computers to access
 680           files residing on this system using Sun's Network File System
 681           protocol.  To compile the NFS server support as a module,
 682           choose M here: the module will be called nfsd.
 683
 684           You may choose to use a user-space NFS server instead, in which
 685           case you can choose N here.
 686
 687           To export local file systems using NFS, you also need to install
 688           user space programs which can be found in the Linux nfs-utils
 689           package, available from http://linux-nfs.org/.  More detail about
 690           the Linux NFS server implementation is available via the
 691           exports(5) man page.
 692
 693           Below you can choose which versions of the NFS protocol are
 694           available to clients mounting the NFS server on this system.
 695           Support for NFS version 2 (RFC 1094) is always available when
 696           CONFIG_NFSD is selected.
 697
 698           If unsure, say N.
 699
 700 config NFSD_V2_ACL
 701         bool
 702         depends on NFSD
 703
 704 config NFSD_V3
 705         bool "NFS server support for NFS version 3"
 706         depends on NFSD
 707         help
 708           This option enables support in your system's NFS server for
 709           version 3 of the NFS protocol (RFC 1813).
 710
 711           If unsure, say Y.
 712
 713 config NFSD_V3_ACL
 714         bool "NFS server support for the NFSv3 ACL protocol extension"
 715         depends on NFSD_V3
 716         select NFSD_V2_ACL
 717         help
 718           Solaris NFS servers support an auxiliary NFSv3 ACL protocol that
 719           never became an official part of the NFS version 3 protocol.
 720           This protocol extension allows applications on NFS clients to
 721           manipulate POSIX Access Control Lists on files residing on NFS
 722           servers.  NFS servers enforce POSIX ACLs on local files whether
 723           this protocol is available or not.
 724
 725           This option enables support in your system's NFS server for the
 726           NFSv3 ACL protocol extension allowing NFS clients to manipulate
 727           POSIX ACLs on files exported by your system's NFS server.  NFS
 728           clients which support the Solaris NFSv3 ACL protocol can then
 729           access and modify ACLs on your NFS server.
 730
 731           To store ACLs on your NFS server, you also need to enable ACL-
 732           related CONFIG options for your local file systems of choice.
 733
 734           If unsure, say N.
 735
 736 config NFSD_V4
 737         bool "NFS server support for NFS version 4 (EXPERIMENTAL)"
 738         depends on NFSD && PROC_FS && EXPERIMENTAL
 739         select NFSD_V3
 740         select FS_POSIX_ACL
 741         select RPCSEC_GSS_KRB5
 742         help
 743           This option enables support in your system's NFS server for
 744           version 4 of the NFS protocol (RFC 3530).
 745
 746           To export files using NFSv4, you need to install additional user
 747           space programs which can be found in the Linux nfs-utils package,
 748           available from http://linux-nfs.org/.
 749
 750           If unsure, say N.
 751
 752 config LOCKD
 753         tristate
 754
 755 config LOCKD_V4
 756         bool
 757         depends on NFSD_V3 || NFS_V3
 758         default y
 759
 760 config EXPORTFS
 761         tristate
 762
 763 config NFS_ACL_SUPPORT
 764         tristate
 765         select FS_POSIX_ACL
 766
 767 config NFS_COMMON
 768         bool
 769         depends on NFSD || NFS_FS
 770         default y
 771
 772 config SUNRPC
 773         tristate
 774
 775 config SUNRPC_GSS
 776         tristate
 777
 778 config SUNRPC_XPRT_RDMA
 779         tristate
 780         depends on SUNRPC && INFINIBAND && EXPERIMENTAL
 781         default SUNRPC && INFINIBAND
 782         help
 783           This option enables an RPC client transport capability that
 784           allows the NFS client to mount servers via an RDMA-enabled
 785           transport.
 786
 787           To compile RPC client RDMA transport support as a module,
 788           choose M here: the module will be called xprtrdma.
 789
 790           If unsure, say N.
 791
 792 config SUNRPC_REGISTER_V4
 793         bool "Register local RPC services via rpcbind v4 (EXPERIMENTAL)"
 794         depends on SUNRPC && EXPERIMENTAL
 795         default n
 796         help
 797           Sun added support for registering RPC services at an IPv6
 798           address by creating two new versions of the rpcbind protocol
 799           (RFC 1833).
 800
 801           This option enables support in the kernel RPC server for
 802           registering kernel RPC services via version 4 of the rpcbind
 803           protocol.  If you enable this option, you must run a portmapper
 804           daemon that supports rpcbind protocol version 4.
 805
 806           Serving NFS over IPv6 from knfsd (the kernel's NFS server)
 807           requires that you enable this option and use a portmapper that
 808           supports rpcbind version 4.
 809
 810           If unsure, say N to get traditional behavior (register kernel
 811           RPC services using only rpcbind version 2).  Distributions
 812           using the legacy Linux portmapper daemon must say N here.
 813
 814 config RPCSEC_GSS_KRB5
 815         tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
 816         depends on SUNRPC && EXPERIMENTAL
 817         select SUNRPC_GSS
 818         select CRYPTO
 819         select CRYPTO_MD5
 820         select CRYPTO_DES
 821         select CRYPTO_CBC
 822         help
 823           Choose Y here to enable Secure RPC using the Kerberos version 5
 824           GSS-API mechanism (RFC 1964).
 825
 826           Secure RPC calls with Kerberos require an auxiliary user-space
 827           daemon which may be found in the Linux nfs-utils package
 828           available from http://linux-nfs.org/.  In addition, user-space
 829           Kerberos support should be installed.
 830
 831           If unsure, say N.
 832
 833 config RPCSEC_GSS_SPKM3
 834         tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
 835         depends on SUNRPC && EXPERIMENTAL
 836         select SUNRPC_GSS
 837         select CRYPTO
 838         select CRYPTO_MD5
 839         select CRYPTO_DES
 840         select CRYPTO_CAST5
 841         select CRYPTO_CBC
 842         help
 843           Choose Y here to enable Secure RPC using the SPKM3 public key
 844           GSS-API mechansim (RFC 2025).
 845
 846           Secure RPC calls with SPKM3 require an auxiliary userspace
 847           daemon which may be found in the Linux nfs-utils package
 848           available from http://linux-nfs.org/.
 849
 850           If unsure, say N.
 851
 852 config SMB_FS
 853         tristate "SMB file system support (OBSOLETE, please use CIFS)"
 854         depends on INET
 855         select NLS
 856         help
 857           SMB (Server Message Block) is the protocol Windows for Workgroups
 858           (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
 859           files and printers over local networks.  Saying Y here allows you to
 860           mount their file systems (often called "shares" in this context) and
 861           access them just like any other Unix directory.  Currently, this
 862           works only if the Windows machines use TCP/IP as the underlying
 863           transport protocol, and not NetBEUI.  For details, read
 864           <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
 865           available from <http://www.tldp.org/docs.html#howto>.
 866
 867           Note: if you just want your box to act as an SMB *server* and make
 868           files and printing services available to Windows clients (which need
 869           to have a TCP/IP stack), you don't need to say Y here; you can use
 870           the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
 871           for that.
 872
 873           General information about how to connect Linux, Windows machines and
 874           Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
 875
 876           To compile the SMB support as a module, choose M here:
 877           the module will be called smbfs.  Most people say N, however.
 878
 879 config SMB_NLS_DEFAULT
 880         bool "Use a default NLS"
 881         depends on SMB_FS
 882         help
 883           Enabling this will make smbfs use nls translations by default. You
 884           need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
 885           settings and you need to give the default nls for the SMB server as
 886           CONFIG_SMB_NLS_REMOTE.
 887
 888           The nls settings can be changed at mount time, if your smbmount
 889           supports that, using the codepage and iocharset parameters.
 890
 891           smbmount from samba 2.2.0 or later supports this.
 892
 893 config SMB_NLS_REMOTE
 894         string "Default Remote NLS Option"
 895         depends on SMB_NLS_DEFAULT
 896         default "cp437"
 897         help
 898           This setting allows you to specify a default value for which
 899           codepage the server uses. If this field is left blank no
 900           translations will be done by default. The local codepage/charset
 901           default to CONFIG_NLS_DEFAULT.
 902
 903           The nls settings can be changed at mount time, if your smbmount
 904           supports that, using the codepage and iocharset parameters.
 905
 906           smbmount from samba 2.2.0 or later supports this.
 907
 908 source "fs/cifs/Kconfig"
 909
 910 config NCP_FS
 911         tristate "NCP file system support (to mount NetWare volumes)"
 912         depends on IPX!=n || INET
 913         help
 914           NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
 915           used by Novell NetWare clients to talk to file servers.  It is to
 916           IPX what NFS is to TCP/IP, if that helps.  Saying Y here allows you
 917           to mount NetWare file server volumes and to access them just like
 918           any other Unix directory.  For details, please read the file
 919           <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
 920           the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
 921
 922           You do not have to say Y here if you want your Linux box to act as a
 923           file *server* for Novell NetWare clients.
 924
 925           General information about how to connect Linux, Windows machines and
 926           Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
 927
 928           To compile this as a module, choose M here: the module will be called
 929           ncpfs.  Say N unless you are connected to a Novell network.
 930
 931 source "fs/ncpfs/Kconfig"
 932
 933 config CODA_FS
 934         tristate "Coda file system support (advanced network fs)"
 935         depends on INET
 936         help
 937           Coda is an advanced network file system, similar to NFS in that it
 938           enables you to mount file systems of a remote server and access them
 939           with regular Unix commands as if they were sitting on your hard
 940           disk.  Coda has several advantages over NFS: support for
 941           disconnected operation (e.g. for laptops), read/write server
 942           replication, security model for authentication and encryption,
 943           persistent client caches and write back caching.
 944
 945           If you say Y here, your Linux box will be able to act as a Coda
 946           *client*.  You will need user level code as well, both for the
 947           client and server.  Servers are currently user level, i.e. they need
 948           no kernel support.  Please read
 949           <file:Documentation/filesystems/coda.txt> and check out the Coda
 950           home page <http://www.coda.cs.cmu.edu/>.
 951
 952           To compile the coda client support as a module, choose M here: the
 953           module will be called coda.
 954
 955 config AFS_FS
 956         tristate "Andrew File System support (AFS) (EXPERIMENTAL)"
 957         depends on INET && EXPERIMENTAL
 958         select AF_RXRPC
 959         help
 960           If you say Y here, you will get an experimental Andrew File System
 961           driver. It currently only supports unsecured read-only AFS access.
 962
 963           See <file:Documentation/filesystems/afs.txt> for more information.
 964
 965           If unsure, say N.
 966
 967 config AFS_DEBUG
 968         bool "AFS dynamic debugging"
 969         depends on AFS_FS
 970         help
 971           Say Y here to make runtime controllable debugging messages appear.
 972
 973           See <file:Documentation/filesystems/afs.txt> for more information.
 974
 975           If unsure, say N.
 976
 977 config 9P_FS
 978         tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
 979         depends on INET && NET_9P && EXPERIMENTAL
 980         help
 981           If you say Y here, you will get experimental support for
 982           Plan 9 resource sharing via the 9P2000 protocol.
 983
 984           See <http://v9fs.sf.net> for more information.
 985
 986           If unsure, say N.
 987
 988 endif # NETWORK_FILESYSTEMS
 989
 990 if BLOCK
 991 menu "Partition Types"
 992
 993 source "fs/partitions/Kconfig"
 994
 995 endmenu
 996 endif
 997
 998 source "fs/nls/Kconfig"
 999 source "fs/dlm/Kconfig"
1000
1001 endmenu