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 config ADFS_FS
 205         tristate "ADFS file system support (EXPERIMENTAL)"
 206         depends on BLOCK && EXPERIMENTAL
 207         help
 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.
 214
 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.
 218
 219           To compile this code as a module, choose M here: the module will be
 220           called adfs.
 221
 222           If unsure, say N.
 223
 224 config ADFS_FS_RW
 225         bool "ADFS write support (DANGEROUS)"
 226         depends on ADFS_FS
 227         help
 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.
 231
 232 config AFFS_FS
 233         tristate "Amiga FFS file system support (EXPERIMENTAL)"
 234         depends on BLOCK && EXPERIMENTAL
 235         help
 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>.
 244
 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.
 250
 251           To compile this file system support as a module, choose M here: the
 252           module will be called affs.  If unsure, say N.
 253
 254 config ECRYPT_FS
 255         tristate "eCrypt filesystem layer support (EXPERIMENTAL)"
 256         depends on EXPERIMENTAL && KEYS && CRYPTO && NET
 257         help
 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>.
 262
 263           To compile this file system support as a module, choose M here: the
 264           module will be called ecryptfs.
 265
 266 config HFS_FS
 267         tristate "Apple Macintosh file system support (EXPERIMENTAL)"
 268         depends on BLOCK && EXPERIMENTAL
 269         select NLS
 270         help
 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.
 275
 276           To compile this file system support as a module, choose M here: the
 277           module will be called hfs.
 278
 279 config HFSPLUS_FS
 280         tristate "Apple Extended HFS file system support"
 281         depends on BLOCK
 282         select NLS
 283         select NLS_UTF8
 284         help
 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.
 287
 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.
 292
 293 config BEFS_FS
 294         tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)"
 295         depends on BLOCK && EXPERIMENTAL
 296         select NLS
 297         help
 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.
 304
 305           If you use this filesystem, you should also say Y to at least one
 306           of the NLS (native language support) options below.
 307
 308           If you don't know what this is about, say N.
 309
 310           To compile this as a module, choose M here: the module will be
 311           called befs.
 312
 313 config BEFS_DEBUG
 314         bool "Debug BeFS"
 315         depends on BEFS_FS
 316         help
 317           If you say Y here, you can use the 'debug' mount option to enable
 318           debugging output from the driver.
 319
 320 config BFS_FS
 321         tristate "BFS file system support (EXPERIMENTAL)"
 322         depends on BLOCK && EXPERIMENTAL
 323         help
 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>.
 333
 334           If you don't know what this is about, say N.
 335
 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.
 339
 340
 341
 342 config EFS_FS
 343         tristate "EFS file system support (read only) (EXPERIMENTAL)"
 344         depends on BLOCK && EXPERIMENTAL
 345         help
 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).
 349
 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/>.
 353
 354           To compile the EFS file system support as a module, choose M here: the
 355           module will be called efs.
 356
 357 source "fs/jffs2/Kconfig"
 358 # UBIFS File system configuration
 359 source "fs/ubifs/Kconfig"
 360
 361 config CRAMFS
 362         tristate "Compressed ROM file system support (cramfs)"
 363         depends on BLOCK
 364         select ZLIB_INFLATE
 365         help
 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.
 371
 372           See <file:Documentation/filesystems/cramfs.txt> and
 373           <file:fs/cramfs/README> for further information.
 374
 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.
 378
 379           If unsure, say N.
 380
 381 config SQUASHFS
 382         tristate "SquashFS 4.0 - Squashed file system support"
 383         depends on BLOCK
 384         select ZLIB_INFLATE
 385         help
 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
 394           timestamps.
 395
 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.
 400
 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.
 406
 407           If unsure, say N.
 408
 409 config SQUASHFS_EMBEDDED
 410
 411         bool "Additional option for memory-constrained systems"
 412         depends on SQUASHFS
 413         default n
 414         help
 415           Saying Y here allows you to specify cache size.
 416
 417           If unsure, say N.
 418
 419 config SQUASHFS_FRAGMENT_CACHE_SIZE
 420         int "Number of fragments cached" if SQUASHFS_EMBEDDED
 421         depends on SQUASHFS
 422         default "3"
 423         help
 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.
 429
 430           Note there must be at least one cached fragment.  Anything
 431           much more than three will probably not make much difference.
 432
 433 config VXFS_FS
 434         tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
 435         depends on BLOCK
 436         help
 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.
 442
 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
 445           the actual driver.
 446
 447           To compile this as a module, choose M here: the module will be
 448           called freevxfs.  If unsure, say N.
 449
 450 config MINIX_FS
 451         tristate "Minix file system support"
 452         depends on BLOCK
 453         help
 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.
 462
 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
 466           a module.
 467
 468 config OMFS_FS
 469         tristate "SonicBlue Optimized MPEG File System support"
 470         depends on BLOCK
 471         select CRC_ITU_T
 472         help
 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.
 478
 479           To compile this file system support as a module, choose M here: the
 480           module will be called omfs.  If unsure, say N.
 481
 482 config HPFS_FS
 483         tristate "OS/2 HPFS file system support"
 484         depends on BLOCK
 485         help
 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>.
 493
 494           To compile this file system support as a module, choose M here: the
 495           module will be called hpfs.  If unsure, say N.
 496
 497
 498 config QNX4FS_FS
 499         tristate "QNX4 file system support (read only)"
 500         depends on BLOCK
 501         help
 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.
 508
 509           To compile this file system support as a module, choose M here: the
 510           module will be called qnx4.
 511
 512           If you don't know whether you need it, then you don't need it:
 513           answer N.
 514
 515 config QNX4FS_RW
 516         bool "QNX4FS write support (DANGEROUS)"
 517         depends on QNX4FS_FS && EXPERIMENTAL && BROKEN
 518         help
 519           Say Y if you want to test write support for QNX4 file systems.
 520
 521           It's currently broken, so for now:
 522           answer N.
 523
 524 config ROMFS_FS
 525         tristate "ROM file system support"
 526         depends on BLOCK
 527         ---help---
 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.
 532
 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
 536           module.
 537
 538           If you don't know whether you need it, then you don't need it:
 539           answer N.
 540
 541
 542 config SYSV_FS
 543         tristate "System V/Xenix/V7/Coherent file system support"
 544         depends on BLOCK
 545         help
 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
 549           partitions.
 550
 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 ;-)
 560
 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).
 564
 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.
 573
 574           To compile this as a module, choose M here: the module will be called
 575           sysv.
 576
 577           If you haven't heard about all of this before, it's safe to say N.
 578
 579
 580 config UFS_FS
 581         tristate "UFS file system support (read only)"
 582         depends on BLOCK
 583         help
 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.
 591
 592           The recently released UFS2 variant (used in FreeBSD 5.x) is
 593           READ-ONLY supported.
 594
 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").
 599
 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.
 603
 604           To compile the UFS file system support as a module, choose M here: the
 605           module will be called ufs.
 606
 607           If you haven't heard about all of this before, it's safe to say N.
 608
 609 config UFS_FS_WRITE
 610         bool "UFS file system write support (DANGEROUS)"
 611         depends on UFS_FS && EXPERIMENTAL
 612         help
 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.
 615
 616 config UFS_DEBUG
 617         bool "UFS debugging"
 618         depends on UFS_FS
 619         help
 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.
 623
 624 endif # MISC_FILESYSTEMS
 625
 626 menuconfig NETWORK_FILESYSTEMS
 627         bool "Network File Systems"
 628         default y
 629         depends on NET
 630         ---help---
 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.
 634
 635           This option alone does not add any kernel code.
 636
 637           If you say N, all options in this submenu will be skipped and
 638           disabled; if unsure, say Y here.
 639
 640 if NETWORK_FILESYSTEMS
 641
 642 config NFS_FS
 643         tristate "NFS client support"
 644         depends on INET
 645         select LOCKD
 646         select SUNRPC
 647         select NFS_ACL_SUPPORT if NFS_V3_ACL
 648         help
 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
 652           will be called nfs.
 653
 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.
 660
 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.
 664
 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
 669           module in this case.
 670
 671           If unsure, say N.
 672
 673 config NFS_V3
 674         bool "NFS client support for NFS version 3"
 675         depends on NFS_FS
 676         help
 677           This option enables support for version 3 of the NFS protocol
 678           (RFC 1813) in the kernel's NFS client.
 679
 680           If unsure, say Y.
 681
 682 config NFS_V3_ACL
 683         bool "NFS client support for the NFSv3 ACL protocol extension"
 684         depends on NFS_V3
 685         help
 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.
 692
 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.
 696
 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
 700           ACL protocol.
 701
 702           If unsure, say N.
 703
 704 config NFS_V4
 705         bool "NFS client support for NFS version 4 (EXPERIMENTAL)"
 706         depends on NFS_FS && EXPERIMENTAL
 707         select RPCSEC_GSS_KRB5
 708         help
 709           This option enables support for version 4 of the NFS protocol
 710           (RFC 3530) in the kernel's NFS client.
 711
 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/.
 715
 716           If unsure, say N.
 717
 718 config ROOT_NFS
 719         bool "Root file system on NFS"
 720         depends on NFS_FS=y && IP_PNP
 721         help
 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>.
 726
 727           Most people say N here.
 728
 729 config NFSD
 730         tristate "NFS server support"
 731         depends on INET
 732         select LOCKD
 733         select SUNRPC
 734         select EXPORTFS
 735         select NFS_ACL_SUPPORT if NFSD_V2_ACL
 736         help
 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.
 741
 742           You may choose to use a user-space NFS server instead, in which
 743           case you can choose N here.
 744
 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
 749           exports(5) man page.
 750
 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.
 755
 756           If unsure, say N.
 757
 758 config NFSD_V2_ACL
 759         bool
 760         depends on NFSD
 761
 762 config NFSD_V3
 763         bool "NFS server support for NFS version 3"
 764         depends on NFSD
 765         help
 766           This option enables support in your system's NFS server for
 767           version 3 of the NFS protocol (RFC 1813).
 768
 769           If unsure, say Y.
 770
 771 config NFSD_V3_ACL
 772         bool "NFS server support for the NFSv3 ACL protocol extension"
 773         depends on NFSD_V3
 774         select NFSD_V2_ACL
 775         help
 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.
 782
 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.
 788
 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.
 791
 792           If unsure, say N.
 793
 794 config NFSD_V4
 795         bool "NFS server support for NFS version 4 (EXPERIMENTAL)"
 796         depends on NFSD && PROC_FS && EXPERIMENTAL
 797         select NFSD_V3
 798         select FS_POSIX_ACL
 799         select RPCSEC_GSS_KRB5
 800         help
 801           This option enables support in your system's NFS server for
 802           version 4 of the NFS protocol (RFC 3530).
 803
 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/.
 807
 808           If unsure, say N.
 809
 810 config LOCKD
 811         tristate
 812
 813 config LOCKD_V4
 814         bool
 815         depends on NFSD_V3 || NFS_V3
 816         default y
 817
 818 config EXPORTFS
 819         tristate
 820
 821 config NFS_ACL_SUPPORT
 822         tristate
 823         select FS_POSIX_ACL
 824
 825 config NFS_COMMON
 826         bool
 827         depends on NFSD || NFS_FS
 828         default y
 829
 830 config SUNRPC
 831         tristate
 832
 833 config SUNRPC_GSS
 834         tristate
 835
 836 config SUNRPC_XPRT_RDMA
 837         tristate
 838         depends on SUNRPC && INFINIBAND && EXPERIMENTAL
 839         default SUNRPC && INFINIBAND
 840         help
 841           This option enables an RPC client transport capability that
 842           allows the NFS client to mount servers via an RDMA-enabled
 843           transport.
 844
 845           To compile RPC client RDMA transport support as a module,
 846           choose M here: the module will be called xprtrdma.
 847
 848           If unsure, say N.
 849
 850 config SUNRPC_REGISTER_V4
 851         bool "Register local RPC services via rpcbind v4 (EXPERIMENTAL)"
 852         depends on SUNRPC && EXPERIMENTAL
 853         default n
 854         help
 855           Sun added support for registering RPC services at an IPv6
 856           address by creating two new versions of the rpcbind protocol
 857           (RFC 1833).
 858
 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.
 863
 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.
 867
 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.
 871
 872 config RPCSEC_GSS_KRB5
 873         tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
 874         depends on SUNRPC && EXPERIMENTAL
 875         select SUNRPC_GSS
 876         select CRYPTO
 877         select CRYPTO_MD5
 878         select CRYPTO_DES
 879         select CRYPTO_CBC
 880         help
 881           Choose Y here to enable Secure RPC using the Kerberos version 5
 882           GSS-API mechanism (RFC 1964).
 883
 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.
 888
 889           If unsure, say N.
 890
 891 config RPCSEC_GSS_SPKM3
 892         tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
 893         depends on SUNRPC && EXPERIMENTAL
 894         select SUNRPC_GSS
 895         select CRYPTO
 896         select CRYPTO_MD5
 897         select CRYPTO_DES
 898         select CRYPTO_CAST5
 899         select CRYPTO_CBC
 900         help
 901           Choose Y here to enable Secure RPC using the SPKM3 public key
 902           GSS-API mechansim (RFC 2025).
 903
 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/.
 907
 908           If unsure, say N.
 909
 910 config SMB_FS
 911         tristate "SMB file system support (OBSOLETE, please use CIFS)"
 912         depends on INET
 913         select NLS
 914         help
 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>.
 924
 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/>)
 929           for that.
 930
 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>.
 933
 934           To compile the SMB support as a module, choose M here:
 935           the module will be called smbfs.  Most people say N, however.
 936
 937 config SMB_NLS_DEFAULT
 938         bool "Use a default NLS"
 939         depends on SMB_FS
 940         help
 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.
 945
 946           The nls settings can be changed at mount time, if your smbmount
 947           supports that, using the codepage and iocharset parameters.
 948
 949           smbmount from samba 2.2.0 or later supports this.
 950
 951 config SMB_NLS_REMOTE
 952         string "Default Remote NLS Option"
 953         depends on SMB_NLS_DEFAULT
 954         default "cp437"
 955         help
 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.
 960
 961           The nls settings can be changed at mount time, if your smbmount
 962           supports that, using the codepage and iocharset parameters.
 963
 964           smbmount from samba 2.2.0 or later supports this.
 965
 966 source "fs/cifs/Kconfig"
 967
 968 config NCP_FS
 969         tristate "NCP file system support (to mount NetWare volumes)"
 970         depends on IPX!=n || INET
 971         help
 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>.
 979
 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.
 982
 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>.
 985
 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.
 988
 989 source "fs/ncpfs/Kconfig"
 990
 991 config CODA_FS
 992         tristate "Coda file system support (advanced network fs)"
 993         depends on INET
 994         help
 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.
1002
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/>.
1009
1010           To compile the coda client support as a module, choose M here: the
1011           module will be called coda.
1012
1013 config AFS_FS
1014         tristate "Andrew File System support (AFS) (EXPERIMENTAL)"
1015         depends on INET && EXPERIMENTAL
1016         select AF_RXRPC
1017         help
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.
1020
1021           See <file:Documentation/filesystems/afs.txt> for more information.
1022
1023           If unsure, say N.
1024
1025 config AFS_DEBUG
1026         bool "AFS dynamic debugging"
1027         depends on AFS_FS
1028         help
1029           Say Y here to make runtime controllable debugging messages appear.
1030
1031           See <file:Documentation/filesystems/afs.txt> for more information.
1032
1033           If unsure, say N.
1034
1035 config 9P_FS
1036         tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
1037         depends on INET && NET_9P && EXPERIMENTAL
1038         help
1039           If you say Y here, you will get experimental support for
1040           Plan 9 resource sharing via the 9P2000 protocol.
1041
1042           See <http://v9fs.sf.net> for more information.
1043
1044           If unsure, say N.
1045
1046 endif # NETWORK_FILESYSTEMS
1047
1048 if BLOCK
1049 menu "Partition Types"
1050
1051 source "fs/partitions/Kconfig"
1052
1053 endmenu
1054 endif
1055
1056 source "fs/nls/Kconfig"
1057 source "fs/dlm/Kconfig"
1058
1059 endmenu