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 config REISERFS_FS
  31         tristate "Reiserfs support"
  32         help
  33           Stores not just filenames but the files themselves in a balanced
  34           tree.  Uses journalling.
  35
  36           Balanced trees are more efficient than traditional file system
  37           architectural foundations.
  38
  39           In general, ReiserFS is as fast as ext2, but is very efficient with
  40           large directories and small files.  Additional patches are needed
  41           for NFS and quotas, please see <http://www.namesys.com/> for links.
  42
  43           It is more easily extended to have features currently found in
  44           database and keyword search systems than block allocation based file
  45           systems are.  The next version will be so extended, and will support
  46           plugins consistent with our motto ``It takes more than a license to
  47           make source code open.''
  48
  49           Read <http://www.namesys.com/> to learn more about reiserfs.
  50
  51           Sponsored by Threshold Networks, Emusic.com, and Bigstorage.com.
  52
  53           If you like it, you can pay us to add new features to it that you
  54           need, buy a support contract, or pay us to port it to another OS.
  55
  56 config REISERFS_CHECK
  57         bool "Enable reiserfs debug mode"
  58         depends on REISERFS_FS
  59         help
  60           If you set this to Y, then ReiserFS will perform every check it can
  61           possibly imagine of its internal consistency throughout its
  62           operation.  It will also go substantially slower.  More than once we
  63           have forgotten that this was on, and then gone despondent over the
  64           latest benchmarks.:-) Use of this option allows our team to go all
  65           out in checking for consistency when debugging without fear of its
  66           effect on end users.  If you are on the verge of sending in a bug
  67           report, say Y and you might get a useful error message.  Almost
  68           everyone should say N.
  69
  70 config REISERFS_PROC_INFO
  71         bool "Stats in /proc/fs/reiserfs"
  72         depends on REISERFS_FS && PROC_FS
  73         help
  74           Create under /proc/fs/reiserfs a hierarchy of files, displaying
  75           various ReiserFS statistics and internal data at the expense of
  76           making your kernel or module slightly larger (+8 KB). This also
  77           increases the amount of kernel memory required for each mount.
  78           Almost everyone but ReiserFS developers and people fine-tuning
  79           reiserfs or tracing problems should say N.
  80
  81 config REISERFS_FS_XATTR
  82         bool "ReiserFS extended attributes"
  83         depends on REISERFS_FS
  84         help
  85           Extended attributes are name:value pairs associated with inodes by
  86           the kernel or by users (see the attr(5) manual page, or visit
  87           <http://acl.bestbits.at/> for details).
  88
  89           If unsure, say N.
  90
  91 config REISERFS_FS_POSIX_ACL
  92         bool "ReiserFS POSIX Access Control Lists"
  93         depends on REISERFS_FS_XATTR
  94         select FS_POSIX_ACL
  95         help
  96           Posix Access Control Lists (ACLs) support permissions for users and
  97           groups beyond the owner/group/world scheme.
  98
  99           To learn more about Access Control Lists, visit the Posix ACLs for
 100           Linux website <http://acl.bestbits.at/>.
 101
 102           If you don't know what Access Control Lists are, say N
 103
 104 config REISERFS_FS_SECURITY
 105         bool "ReiserFS Security Labels"
 106         depends on REISERFS_FS_XATTR
 107         help
 108           Security labels support alternative access control models
 109           implemented by security modules like SELinux.  This option
 110           enables an extended attribute handler for file security
 111           labels in the ReiserFS filesystem.
 112
 113           If you are not using a security module that requires using
 114           extended attributes for file security labels, say N.
 115
 116 config JFS_FS
 117         tristate "JFS filesystem support"
 118         select NLS
 119         help
 120           This is a port of IBM's Journaled Filesystem .  More information is
 121           available in the file <file:Documentation/filesystems/jfs.txt>.
 122
 123           If you do not intend to use the JFS filesystem, say N.
 124
 125 config JFS_POSIX_ACL
 126         bool "JFS POSIX Access Control Lists"
 127         depends on JFS_FS
 128         select FS_POSIX_ACL
 129         help
 130           Posix Access Control Lists (ACLs) support permissions for users and
 131           groups beyond the owner/group/world scheme.
 132
 133           To learn more about Access Control Lists, visit the Posix ACLs for
 134           Linux website <http://acl.bestbits.at/>.
 135
 136           If you don't know what Access Control Lists are, say N
 137
 138 config JFS_SECURITY
 139         bool "JFS Security Labels"
 140         depends on JFS_FS
 141         help
 142           Security labels support alternative access control models
 143           implemented by security modules like SELinux.  This option
 144           enables an extended attribute handler for file security
 145           labels in the jfs filesystem.
 146
 147           If you are not using a security module that requires using
 148           extended attributes for file security labels, say N.
 149
 150 config JFS_DEBUG
 151         bool "JFS debugging"
 152         depends on JFS_FS
 153         help
 154           If you are experiencing any problems with the JFS filesystem, say
 155           Y here.  This will result in additional debugging messages to be
 156           written to the system log.  Under normal circumstances, this
 157           results in very little overhead.
 158
 159 config JFS_STATISTICS
 160         bool "JFS statistics"
 161         depends on JFS_FS
 162         help
 163           Enabling this option will cause statistics from the JFS file system
 164           to be made available to the user in the /proc/fs/jfs/ directory.
 165
 166 config FS_POSIX_ACL
 167 # Posix ACL utility routines (for now, only ext2/ext3/jfs/reiserfs/nfs4)
 168 #
 169 # NOTE: you can implement Posix ACLs without these helpers (XFS does).
 170 #       Never use this symbol for ifdefs.
 171 #
 172         bool
 173         default n
 174
 175 config FILE_LOCKING
 176         bool "Enable POSIX file locking API" if EMBEDDED
 177         default y
 178         help
 179           This option enables standard file locking support, required
 180           for filesystems like NFS and for the flock() system
 181           call. Disabling this option saves about 11k.
 182
 183 source "fs/xfs/Kconfig"
 184 source "fs/gfs2/Kconfig"
 185
 186 config OCFS2_FS
 187         tristate "OCFS2 file system support"
 188         depends on NET && SYSFS
 189         select CONFIGFS_FS
 190         select JBD2
 191         select CRC32
 192         select QUOTA
 193         select QUOTA_TREE
 194         help
 195           OCFS2 is a general purpose extent based shared disk cluster file
 196           system with many similarities to ext3. It supports 64 bit inode
 197           numbers, and has automatically extending metadata groups which may
 198           also make it attractive for non-clustered use.
 199
 200           You'll want to install the ocfs2-tools package in order to at least
 201           get "mount.ocfs2".
 202
 203           Project web page:    http://oss.oracle.com/projects/ocfs2
 204           Tools web page:      http://oss.oracle.com/projects/ocfs2-tools
 205           OCFS2 mailing lists: http://oss.oracle.com/projects/ocfs2/mailman/
 206
 207           For more information on OCFS2, see the file
 208           <file:Documentation/filesystems/ocfs2.txt>.
 209
 210 config OCFS2_FS_O2CB
 211         tristate "O2CB Kernelspace Clustering"
 212         depends on OCFS2_FS
 213         default y
 214         help
 215           OCFS2 includes a simple kernelspace clustering package, the OCFS2
 216           Cluster Base.  It only requires a very small userspace component
 217           to configure it. This comes with the standard ocfs2-tools package.
 218           O2CB is limited to maintaining a cluster for OCFS2 file systems.
 219           It cannot manage any other cluster applications.
 220
 221           It is always safe to say Y here, as the clustering method is
 222           run-time selectable.
 223
 224 config OCFS2_FS_USERSPACE_CLUSTER
 225         tristate "OCFS2 Userspace Clustering"
 226         depends on OCFS2_FS && DLM
 227         default y
 228         help
 229           This option will allow OCFS2 to use userspace clustering services
 230           in conjunction with the DLM in fs/dlm.  If you are using a
 231           userspace cluster manager, say Y here.
 232
 233           It is safe to say Y, as the clustering method is run-time
 234           selectable.
 235
 236 config OCFS2_FS_STATS
 237         bool "OCFS2 statistics"
 238         depends on OCFS2_FS
 239         default y
 240         help
 241           This option allows some fs statistics to be captured. Enabling
 242           this option may increase the memory consumption.
 243
 244 config OCFS2_DEBUG_MASKLOG
 245         bool "OCFS2 logging support"
 246         depends on OCFS2_FS
 247         default y
 248         help
 249           The ocfs2 filesystem has an extensive logging system.  The system
 250           allows selection of events to log via files in /sys/o2cb/logmask/.
 251           This option will enlarge your kernel, but it allows debugging of
 252           ocfs2 filesystem issues.
 253
 254 config OCFS2_DEBUG_FS
 255         bool "OCFS2 expensive checks"
 256         depends on OCFS2_FS
 257         default n
 258         help
 259           This option will enable expensive consistency checks. Enable
 260           this option for debugging only as it is likely to decrease
 261           performance of the filesystem.
 262
 263 config OCFS2_FS_POSIX_ACL
 264         bool "OCFS2 POSIX Access Control Lists"
 265         depends on OCFS2_FS
 266         select FS_POSIX_ACL
 267         default n
 268         help
 269           Posix Access Control Lists (ACLs) support permissions for users and
 270           groups beyond the owner/group/world scheme.
 271
 272 endif # BLOCK
 273
 274 source "fs/notify/Kconfig"
 275
 276 config QUOTA
 277         bool "Quota support"
 278         help
 279           If you say Y here, you will be able to set per user limits for disk
 280           usage (also called disk quotas). Currently, it works for the
 281           ext2, ext3, and reiserfs file system. ext3 also supports journalled
 282           quotas for which you don't need to run quotacheck(8) after an unclean
 283           shutdown.
 284           For further details, read the Quota mini-HOWTO, available from
 285           <http://www.tldp.org/docs.html#howto>, or the documentation provided
 286           with the quota tools. Probably the quota support is only useful for
 287           multi user systems. If unsure, say N.
 288
 289 config QUOTA_NETLINK_INTERFACE
 290         bool "Report quota messages through netlink interface"
 291         depends on QUOTA && NET
 292         help
 293           If you say Y here, quota warnings (about exceeding softlimit, reaching
 294           hardlimit, etc.) will be reported through netlink interface. If unsure,
 295           say Y.
 296
 297 config PRINT_QUOTA_WARNING
 298         bool "Print quota warnings to console (OBSOLETE)"
 299         depends on QUOTA
 300         default y
 301         help
 302           If you say Y here, quota warnings (about exceeding softlimit, reaching
 303           hardlimit, etc.) will be printed to the process' controlling terminal.
 304           Note that this behavior is currently deprecated and may go away in
 305           future. Please use notification via netlink socket instead.
 306
 307 # Generic support for tree structured quota files. Seleted when needed.
 308 config QUOTA_TREE
 309          tristate
 310
 311 config QFMT_V1
 312         tristate "Old quota format support"
 313         depends on QUOTA
 314         help
 315           This quota format was (is) used by kernels earlier than 2.4.22. If
 316           you have quota working and you don't want to convert to new quota
 317           format say Y here.
 318
 319 config QFMT_V2
 320         tristate "Quota format v2 support"
 321         depends on QUOTA
 322         select QUOTA_TREE
 323         help
 324           This quota format allows using quotas with 32-bit UIDs/GIDs. If you
 325           need this functionality say Y here.
 326
 327 config QUOTACTL
 328         bool
 329         depends on XFS_QUOTA || QUOTA
 330         default y
 331
 332 config AUTOFS_FS
 333         tristate "Kernel automounter support"
 334         help
 335           The automounter is a tool to automatically mount remote file systems
 336           on demand. This implementation is partially kernel-based to reduce
 337           overhead in the already-mounted case; this is unlike the BSD
 338           automounter (amd), which is a pure user space daemon.
 339
 340           To use the automounter you need the user-space tools from the autofs
 341           package; you can find the location in <file:Documentation/Changes>.
 342           You also want to answer Y to "NFS file system support", below.
 343
 344           If you want to use the newer version of the automounter with more
 345           features, say N here and say Y to "Kernel automounter v4 support",
 346           below.
 347
 348           To compile this support as a module, choose M here: the module will be
 349           called autofs.
 350
 351           If you are not a part of a fairly large, distributed network, you
 352           probably do not need an automounter, and can say N here.
 353
 354 config AUTOFS4_FS
 355         tristate "Kernel automounter version 4 support (also supports v3)"
 356         help
 357           The automounter is a tool to automatically mount remote file systems
 358           on demand. This implementation is partially kernel-based to reduce
 359           overhead in the already-mounted case; this is unlike the BSD
 360           automounter (amd), which is a pure user space daemon.
 361
 362           To use the automounter you need the user-space tools from
 363           <ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4/>; you also
 364           want to answer Y to "NFS file system support", below.
 365
 366           To compile this support as a module, choose M here: the module will be
 367           called autofs4.  You will need to add "alias autofs autofs4" to your
 368           modules configuration file.
 369
 370           If you are not a part of a fairly large, distributed network or
 371           don't have a laptop which needs to dynamically reconfigure to the
 372           local network, you probably do not need an automounter, and can say
 373           N here.
 374
 375 config FUSE_FS
 376         tristate "FUSE (Filesystem in Userspace) support"
 377         help
 378           With FUSE it is possible to implement a fully functional filesystem
 379           in a userspace program.
 380
 381           There's also companion library: libfuse.  This library along with
 382           utilities is available from the FUSE homepage:
 383           <http://fuse.sourceforge.net/>
 384
 385           See <file:Documentation/filesystems/fuse.txt> for more information.
 386           See <file:Documentation/Changes> for needed library/utility version.
 387
 388           If you want to develop a userspace FS, or if you want to use
 389           a filesystem based on FUSE, answer Y or M.
 390
 391 config GENERIC_ACL
 392         bool
 393         select FS_POSIX_ACL
 394
 395 if BLOCK
 396 menu "CD-ROM/DVD Filesystems"
 397
 398 config ISO9660_FS
 399         tristate "ISO 9660 CDROM file system support"
 400         help
 401           This is the standard file system used on CD-ROMs.  It was previously
 402           known as "High Sierra File System" and is called "hsfs" on other
 403           Unix systems.  The so-called Rock-Ridge extensions which allow for
 404           long Unix filenames and symbolic links are also supported by this
 405           driver.  If you have a CD-ROM drive and want to do more with it than
 406           just listen to audio CDs and watch its LEDs, say Y (and read
 407           <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO,
 408           available from <http://www.tldp.org/docs.html#howto>), thereby
 409           enlarging your kernel by about 27 KB; otherwise say N.
 410
 411           To compile this file system support as a module, choose M here: the
 412           module will be called isofs.
 413
 414 config JOLIET
 415         bool "Microsoft Joliet CDROM extensions"
 416         depends on ISO9660_FS
 417         select NLS
 418         help
 419           Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system
 420           which allows for long filenames in unicode format (unicode is the
 421           new 16 bit character code, successor to ASCII, which encodes the
 422           characters of almost all languages of the world; see
 423           <http://www.unicode.org/> for more information).  Say Y here if you
 424           want to be able to read Joliet CD-ROMs under Linux.
 425
 426 config ZISOFS
 427         bool "Transparent decompression extension"
 428         depends on ISO9660_FS
 429         select ZLIB_INFLATE
 430         help
 431           This is a Linux-specific extension to RockRidge which lets you store
 432           data in compressed form on a CD-ROM and have it transparently
 433           decompressed when the CD-ROM is accessed.  See
 434           <http://www.kernel.org/pub/linux/utils/fs/zisofs/> for the tools
 435           necessary to create such a filesystem.  Say Y here if you want to be
 436           able to read such compressed CD-ROMs.
 437
 438 config UDF_FS
 439         tristate "UDF file system support"
 440         select CRC_ITU_T
 441         help
 442           This is the new file system used on some CD-ROMs and DVDs. Say Y if
 443           you intend to mount DVD discs or CDRW's written in packet mode, or
 444           if written to by other UDF utilities, such as DirectCD.
 445           Please read <file:Documentation/filesystems/udf.txt>.
 446
 447           To compile this file system support as a module, choose M here: the
 448           module will be called udf.
 449
 450           If unsure, say N.
 451
 452 config UDF_NLS
 453         bool
 454         default y
 455         depends on (UDF_FS=m && NLS) || (UDF_FS=y && NLS=y)
 456
 457 endmenu
 458 endif # BLOCK
 459
 460 if BLOCK
 461 menu "DOS/FAT/NT Filesystems"
 462
 463 config FAT_FS
 464         tristate
 465         select NLS
 466         help
 467           If you want to use one of the FAT-based file systems (the MS-DOS and
 468           VFAT (Windows 95) file systems), then you must say Y or M here
 469           to include FAT support. You will then be able to mount partitions or
 470           diskettes with FAT-based file systems and transparently access the
 471           files on them, i.e. MSDOS files will look and behave just like all
 472           other Unix files.
 473
 474           This FAT support is not a file system in itself, it only provides
 475           the foundation for the other file systems. You will have to say Y or
 476           M to at least one of "MSDOS fs support" or "VFAT fs support" in
 477           order to make use of it.
 478
 479           Another way to read and write MSDOS floppies and hard drive
 480           partitions from within Linux (but not transparently) is with the
 481           mtools ("man mtools") program suite. You don't need to say Y here in
 482           order to do that.
 483
 484           If you need to move large files on floppies between a DOS and a
 485           Linux box, say Y here, mount the floppy under Linux with an MSDOS
 486           file system and use GNU tar's M option. GNU tar is a program
 487           available for Unix and DOS ("man tar" or "info tar").
 488
 489           The FAT support will enlarge your kernel by about 37 KB. If unsure,
 490           say Y.
 491
 492           To compile this as a module, choose M here: the module will be called
 493           fat.  Note that if you compile the FAT support as a module, you
 494           cannot compile any of the FAT-based file systems into the kernel
 495           -- they will have to be modules as well.
 496
 497 config MSDOS_FS
 498         tristate "MSDOS fs support"
 499         select FAT_FS
 500         help
 501           This allows you to mount MSDOS partitions of your hard drive (unless
 502           they are compressed; to access compressed MSDOS partitions under
 503           Linux, you can either use the DOS emulator DOSEMU, described in the
 504           DOSEMU-HOWTO, available from
 505           <http://www.tldp.org/docs.html#howto>, or try dmsdosfs in
 506           <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you
 507           intend to use dosemu with a non-compressed MSDOS partition, say Y
 508           here) and MSDOS floppies. This means that file access becomes
 509           transparent, i.e. the MSDOS files look and behave just like all
 510           other Unix files.
 511
 512           If you have Windows 95 or Windows NT installed on your MSDOS
 513           partitions, you should use the VFAT file system (say Y to "VFAT fs
 514           support" below), or you will not be able to see the long filenames
 515           generated by Windows 95 / Windows NT.
 516
 517           This option will enlarge your kernel by about 7 KB. If unsure,
 518           answer Y. This will only work if you said Y to "DOS FAT fs support"
 519           as well. To compile this as a module, choose M here: the module will
 520           be called msdos.
 521
 522 config VFAT_FS
 523         tristate "VFAT (Windows-95) fs support"
 524         select FAT_FS
 525         help
 526           This option provides support for normal Windows file systems with
 527           long filenames.  That includes non-compressed FAT-based file systems
 528           used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
 529           programs from the mtools package.
 530
 531           The VFAT support enlarges your kernel by about 10 KB and it only
 532           works if you said Y to the "DOS FAT fs support" above.  Please read
 533           the file <file:Documentation/filesystems/vfat.txt> for details.  If
 534           unsure, say Y.
 535
 536           To compile this as a module, choose M here: the module will be called
 537           vfat.
 538
 539 config FAT_DEFAULT_CODEPAGE
 540         int "Default codepage for FAT"
 541         depends on MSDOS_FS || VFAT_FS
 542         default 437
 543         help
 544           This option should be set to the codepage of your FAT filesystems.
 545           It can be overridden with the "codepage" mount option.
 546           See <file:Documentation/filesystems/vfat.txt> for more information.
 547
 548 config FAT_DEFAULT_IOCHARSET
 549         string "Default iocharset for FAT"
 550         depends on VFAT_FS
 551         default "iso8859-1"
 552         help
 553           Set this to the default input/output character set you'd
 554           like FAT to use. It should probably match the character set
 555           that most of your FAT filesystems use, and can be overridden
 556           with the "iocharset" mount option for FAT filesystems.
 557           Note that "utf8" is not recommended for FAT filesystems.
 558           If unsure, you shouldn't set "utf8" here.
 559           See <file:Documentation/filesystems/vfat.txt> for more information.
 560
 561 config NTFS_FS
 562         tristate "NTFS file system support"
 563         select NLS
 564         help
 565           NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003.
 566
 567           Saying Y or M here enables read support.  There is partial, but
 568           safe, write support available.  For write support you must also
 569           say Y to "NTFS write support" below.
 570
 571           There are also a number of user-space tools available, called
 572           ntfsprogs.  These include ntfsundelete and ntfsresize, that work
 573           without NTFS support enabled in the kernel.
 574
 575           This is a rewrite from scratch of Linux NTFS support and replaced
 576           the old NTFS code starting with Linux 2.5.11.  A backport to
 577           the Linux 2.4 kernel series is separately available as a patch
 578           from the project web site.
 579
 580           For more information see <file:Documentation/filesystems/ntfs.txt>
 581           and <http://www.linux-ntfs.org/>.
 582
 583           To compile this file system support as a module, choose M here: the
 584           module will be called ntfs.
 585
 586           If you are not using Windows NT, 2000, XP or 2003 in addition to
 587           Linux on your computer it is safe to say N.
 588
 589 config NTFS_DEBUG
 590         bool "NTFS debugging support"
 591         depends on NTFS_FS
 592         help
 593           If you are experiencing any problems with the NTFS file system, say
 594           Y here.  This will result in additional consistency checks to be
 595           performed by the driver as well as additional debugging messages to
 596           be written to the system log.  Note that debugging messages are
 597           disabled by default.  To enable them, supply the option debug_msgs=1
 598           at the kernel command line when booting the kernel or as an option
 599           to insmod when loading the ntfs module.  Once the driver is active,
 600           you can enable debugging messages by doing (as root):
 601           echo 1 > /proc/sys/fs/ntfs-debug
 602           Replacing the "1" with "0" would disable debug messages.
 603
 604           If you leave debugging messages disabled, this results in little
 605           overhead, but enabling debug messages results in very significant
 606           slowdown of the system.
 607
 608           When reporting bugs, please try to have available a full dump of
 609           debugging messages while the misbehaviour was occurring.
 610
 611 config NTFS_RW
 612         bool "NTFS write support"
 613         depends on NTFS_FS
 614         help
 615           This enables the partial, but safe, write support in the NTFS driver.
 616
 617           The only supported operation is overwriting existing files, without
 618           changing the file length.  No file or directory creation, deletion or
 619           renaming is possible.  Note only non-resident files can be written to
 620           so you may find that some very small files (<500 bytes or so) cannot
 621           be written to.
 622
 623           While we cannot guarantee that it will not damage any data, we have
 624           so far not received a single report where the driver would have
 625           damaged someones data so we assume it is perfectly safe to use.
 626
 627           Note:  While write support is safe in this version (a rewrite from
 628           scratch of the NTFS support), it should be noted that the old NTFS
 629           write support, included in Linux 2.5.10 and before (since 1997),
 630           is not safe.
 631
 632           This is currently useful with TopologiLinux.  TopologiLinux is run
 633           on top of any DOS/Microsoft Windows system without partitioning your
 634           hard disk.  Unlike other Linux distributions TopologiLinux does not
 635           need its own partition.  For more information see
 636           <http://topologi-linux.sourceforge.net/>
 637
 638           It is perfectly safe to say N here.
 639
 640 endmenu
 641 endif # BLOCK
 642
 643 menu "Pseudo filesystems"
 644
 645 source "fs/proc/Kconfig"
 646
 647 config SYSFS
 648         bool "sysfs file system support" if EMBEDDED
 649         default y
 650         help
 651         The sysfs filesystem is a virtual filesystem that the kernel uses to
 652         export internal kernel objects, their attributes, and their
 653         relationships to one another.
 654
 655         Users can use sysfs to ascertain useful information about the running
 656         kernel, such as the devices the kernel has discovered on each bus and
 657         which driver each is bound to. sysfs can also be used to tune devices
 658         and other kernel subsystems.
 659
 660         Some system agents rely on the information in sysfs to operate.
 661         /sbin/hotplug uses device and object attributes in sysfs to assist in
 662         delegating policy decisions, like persistently naming devices.
 663
 664         sysfs is currently used by the block subsystem to mount the root
 665         partition.  If sysfs is disabled you must specify the boot device on
 666         the kernel boot command line via its major and minor numbers.  For
 667         example, "root=03:01" for /dev/hda1.
 668
 669         Designers of embedded systems may wish to say N here to conserve space.
 670
 671 config TMPFS
 672         bool "Virtual memory file system support (former shm fs)"
 673         help
 674           Tmpfs is a file system which keeps all files in virtual memory.
 675
 676           Everything in tmpfs is temporary in the sense that no files will be
 677           created on your hard drive. The files live in memory and swap
 678           space. If you unmount a tmpfs instance, everything stored therein is
 679           lost.
 680
 681           See <file:Documentation/filesystems/tmpfs.txt> for details.
 682
 683 config TMPFS_POSIX_ACL
 684         bool "Tmpfs POSIX Access Control Lists"
 685         depends on TMPFS
 686         select GENERIC_ACL
 687         help
 688           POSIX Access Control Lists (ACLs) support permissions for users and
 689           groups beyond the owner/group/world scheme.
 690
 691           To learn more about Access Control Lists, visit the POSIX ACLs for
 692           Linux website <http://acl.bestbits.at/>.
 693
 694           If you don't know what Access Control Lists are, say N.
 695
 696 config HUGETLBFS
 697         bool "HugeTLB file system support"
 698         depends on X86 || IA64 || PPC64 || SPARC64 || (SUPERH && MMU) || \
 699                    (S390 && 64BIT) || BROKEN
 700         help
 701           hugetlbfs is a filesystem backing for HugeTLB pages, based on
 702           ramfs. For architectures that support it, say Y here and read
 703           <file:Documentation/vm/hugetlbpage.txt> for details.
 704
 705           If unsure, say N.
 706
 707 config HUGETLB_PAGE
 708         def_bool HUGETLBFS
 709
 710 config CONFIGFS_FS
 711         tristate "Userspace-driven configuration filesystem"
 712         depends on SYSFS
 713         help
 714           configfs is a ram-based filesystem that provides the converse
 715           of sysfs's functionality. Where sysfs is a filesystem-based
 716           view of kernel objects, configfs is a filesystem-based manager
 717           of kernel objects, or config_items.
 718
 719           Both sysfs and configfs can and should exist together on the
 720           same system. One is not a replacement for the other.
 721
 722 endmenu
 723
 724 menuconfig MISC_FILESYSTEMS
 725         bool "Miscellaneous filesystems"
 726         default y
 727         ---help---
 728           Say Y here to get to see options for various miscellaneous
 729           filesystems, such as filesystems that came from other
 730           operating systems.
 731
 732           This option alone does not add any kernel code.
 733
 734           If you say N, all options in this submenu will be skipped and
 735           disabled; if unsure, say Y here.
 736
 737 if MISC_FILESYSTEMS
 738
 739 config ADFS_FS
 740         tristate "ADFS file system support (EXPERIMENTAL)"
 741         depends on BLOCK && EXPERIMENTAL
 742         help
 743           The Acorn Disc Filing System is the standard file system of the
 744           RiscOS operating system which runs on Acorn's ARM-based Risc PC
 745           systems and the Acorn Archimedes range of machines. If you say Y
 746           here, Linux will be able to read from ADFS partitions on hard drives
 747           and from ADFS-formatted floppy discs. If you also want to be able to
 748           write to those devices, say Y to "ADFS write support" below.
 749
 750           The ADFS partition should be the first partition (i.e.,
 751           /dev/[hs]d?1) on each of your drives. Please read the file
 752           <file:Documentation/filesystems/adfs.txt> for further details.
 753
 754           To compile this code as a module, choose M here: the module will be
 755           called adfs.
 756
 757           If unsure, say N.
 758
 759 config ADFS_FS_RW
 760         bool "ADFS write support (DANGEROUS)"
 761         depends on ADFS_FS
 762         help
 763           If you say Y here, you will be able to write to ADFS partitions on
 764           hard drives and ADFS-formatted floppy disks. This is experimental
 765           codes, so if you're unsure, say N.
 766
 767 config AFFS_FS
 768         tristate "Amiga FFS file system support (EXPERIMENTAL)"
 769         depends on BLOCK && EXPERIMENTAL
 770         help
 771           The Fast File System (FFS) is the common file system used on hard
 772           disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20).  Say Y
 773           if you want to be able to read and write files from and to an Amiga
 774           FFS partition on your hard drive.  Amiga floppies however cannot be
 775           read with this driver due to an incompatibility of the floppy
 776           controller used in an Amiga and the standard floppy controller in
 777           PCs and workstations. Read <file:Documentation/filesystems/affs.txt>
 778           and <file:fs/affs/Changes>.
 779
 780           With this driver you can also mount disk files used by Bernd
 781           Schmidt's Un*X Amiga Emulator
 782           (<http://www.freiburg.linux.de/~uae/>).
 783           If you want to do this, you will also need to say Y or M to "Loop
 784           device support", above.
 785
 786           To compile this file system support as a module, choose M here: the
 787           module will be called affs.  If unsure, say N.
 788
 789 config ECRYPT_FS
 790         tristate "eCrypt filesystem layer support (EXPERIMENTAL)"
 791         depends on EXPERIMENTAL && KEYS && CRYPTO && NET
 792         help
 793           Encrypted filesystem that operates on the VFS layer.  See
 794           <file:Documentation/filesystems/ecryptfs.txt> to learn more about
 795           eCryptfs.  Userspace components are required and can be
 796           obtained from <http://ecryptfs.sf.net>.
 797
 798           To compile this file system support as a module, choose M here: the
 799           module will be called ecryptfs.
 800
 801 config HFS_FS
 802         tristate "Apple Macintosh file system support (EXPERIMENTAL)"
 803         depends on BLOCK && EXPERIMENTAL
 804         select NLS
 805         help
 806           If you say Y here, you will be able to mount Macintosh-formatted
 807           floppy disks and hard drive partitions with full read-write access.
 808           Please read <file:Documentation/filesystems/hfs.txt> to learn about
 809           the available mount options.
 810
 811           To compile this file system support as a module, choose M here: the
 812           module will be called hfs.
 813
 814 config HFSPLUS_FS
 815         tristate "Apple Extended HFS file system support"
 816         depends on BLOCK
 817         select NLS
 818         select NLS_UTF8
 819         help
 820           If you say Y here, you will be able to mount extended format
 821           Macintosh-formatted hard drive partitions with full read-write access.
 822
 823           This file system is often called HFS+ and was introduced with
 824           MacOS 8. It includes all Mac specific filesystem data such as
 825           data forks and creator codes, but it also has several UNIX
 826           style features such as file ownership and permissions.
 827
 828 config BEFS_FS
 829         tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)"
 830         depends on BLOCK && EXPERIMENTAL
 831         select NLS
 832         help
 833           The BeOS File System (BeFS) is the native file system of Be, Inc's
 834           BeOS. Notable features include support for arbitrary attributes
 835           on files and directories, and database-like indices on selected
 836           attributes. (Also note that this driver doesn't make those features
 837           available at this time). It is a 64 bit filesystem, so it supports
 838           extremely large volumes and files.
 839
 840           If you use this filesystem, you should also say Y to at least one
 841           of the NLS (native language support) options below.
 842
 843           If you don't know what this is about, say N.
 844
 845           To compile this as a module, choose M here: the module will be
 846           called befs.
 847
 848 config BEFS_DEBUG
 849         bool "Debug BeFS"
 850         depends on BEFS_FS
 851         help
 852           If you say Y here, you can use the 'debug' mount option to enable
 853           debugging output from the driver.
 854
 855 config BFS_FS
 856         tristate "BFS file system support (EXPERIMENTAL)"
 857         depends on BLOCK && EXPERIMENTAL
 858         help
 859           Boot File System (BFS) is a file system used under SCO UnixWare to
 860           allow the bootloader access to the kernel image and other important
 861           files during the boot process.  It is usually mounted under /stand
 862           and corresponds to the slice marked as "STAND" in the UnixWare
 863           partition.  You should say Y if you want to read or write the files
 864           on your /stand slice from within Linux.  You then also need to say Y
 865           to "UnixWare slices support", below.  More information about the BFS
 866           file system is contained in the file
 867           <file:Documentation/filesystems/bfs.txt>.
 868
 869           If you don't know what this is about, say N.
 870
 871           To compile this as a module, choose M here: the module will be called
 872           bfs.  Note that the file system of your root partition (the one
 873           containing the directory /) cannot be compiled as a module.
 874
 875
 876
 877 config EFS_FS
 878         tristate "EFS file system support (read only) (EXPERIMENTAL)"
 879         depends on BLOCK && EXPERIMENTAL
 880         help
 881           EFS is an older file system used for non-ISO9660 CD-ROMs and hard
 882           disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
 883           uses the XFS file system for hard disk partitions however).
 884
 885           This implementation only offers read-only access. If you don't know
 886           what all this is about, it's safe to say N. For more information
 887           about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
 888
 889           To compile the EFS file system support as a module, choose M here: the
 890           module will be called efs.
 891
 892 source "fs/jffs2/Kconfig"
 893 # UBIFS File system configuration
 894 source "fs/ubifs/Kconfig"
 895
 896 config CRAMFS
 897         tristate "Compressed ROM file system support (cramfs)"
 898         depends on BLOCK
 899         select ZLIB_INFLATE
 900         help
 901           Saying Y here includes support for CramFs (Compressed ROM File
 902           System).  CramFs is designed to be a simple, small, and compressed
 903           file system for ROM based embedded systems.  CramFs is read-only,
 904           limited to 256MB file systems (with 16MB files), and doesn't support
 905           16/32 bits uid/gid, hard links and timestamps.
 906
 907           See <file:Documentation/filesystems/cramfs.txt> and
 908           <file:fs/cramfs/README> for further information.
 909
 910           To compile this as a module, choose M here: the module will be called
 911           cramfs.  Note that the root file system (the one containing the
 912           directory /) cannot be compiled as a module.
 913
 914           If unsure, say N.
 915
 916 config VXFS_FS
 917         tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
 918         depends on BLOCK
 919         help
 920           FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
 921           file system format.  VERITAS VxFS(TM) is the standard file system
 922           of SCO UnixWare (and possibly others) and optionally available
 923           for Sunsoft Solaris, HP-UX and many other operating systems.
 924           Currently only readonly access is supported.
 925
 926           NOTE: the file system type as used by mount(1), mount(2) and
 927           fstab(5) is 'vxfs' as it describes the file system format, not
 928           the actual driver.
 929
 930           To compile this as a module, choose M here: the module will be
 931           called freevxfs.  If unsure, say N.
 932
 933 config MINIX_FS
 934         tristate "Minix file system support"
 935         depends on BLOCK
 936         help
 937           Minix is a simple operating system used in many classes about OS's.
 938           The minix file system (method to organize files on a hard disk
 939           partition or a floppy disk) was the original file system for Linux,
 940           but has been superseded by the second extended file system ext2fs.
 941           You don't want to use the minix file system on your hard disk
 942           because of certain built-in restrictions, but it is sometimes found
 943           on older Linux floppy disks.  This option will enlarge your kernel
 944           by about 28 KB. If unsure, say N.
 945
 946           To compile this file system support as a module, choose M here: the
 947           module will be called minix.  Note that the file system of your root
 948           partition (the one containing the directory /) cannot be compiled as
 949           a module.
 950
 951 config OMFS_FS
 952         tristate "SonicBlue Optimized MPEG File System support"
 953         depends on BLOCK
 954         select CRC_ITU_T
 955         help
 956           This is the proprietary file system used by the Rio Karma music
 957           player and ReplayTV DVR.  Despite the name, this filesystem is not
 958           more efficient than a standard FS for MPEG files, in fact likely
 959           the opposite is true.  Say Y if you have either of these devices
 960           and wish to mount its disk.
 961
 962           To compile this file system support as a module, choose M here: the
 963           module will be called omfs.  If unsure, say N.
 964
 965 config HPFS_FS
 966         tristate "OS/2 HPFS file system support"
 967         depends on BLOCK
 968         help
 969           OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
 970           is the file system used for organizing files on OS/2 hard disk
 971           partitions. Say Y if you want to be able to read files from and
 972           write files to an OS/2 HPFS partition on your hard drive. OS/2
 973           floppies however are in regular MSDOS format, so you don't need this
 974           option in order to be able to read them. Read
 975           <file:Documentation/filesystems/hpfs.txt>.
 976
 977           To compile this file system support as a module, choose M here: the
 978           module will be called hpfs.  If unsure, say N.
 979
 980
 981 config QNX4FS_FS
 982         tristate "QNX4 file system support (read only)"
 983         depends on BLOCK
 984         help
 985           This is the file system used by the real-time operating systems
 986           QNX 4 and QNX 6 (the latter is also called QNX RTP).
 987           Further information is available at <http://www.qnx.com/>.
 988           Say Y if you intend to mount QNX hard disks or floppies.
 989           Unless you say Y to "QNX4FS read-write support" below, you will
 990           only be able to read these file systems.
 991
 992           To compile this file system support as a module, choose M here: the
 993           module will be called qnx4.
 994
 995           If you don't know whether you need it, then you don't need it:
 996           answer N.
 997
 998 config QNX4FS_RW
 999         bool "QNX4FS write support (DANGEROUS)"
1000         depends on QNX4FS_FS && EXPERIMENTAL && BROKEN
1001         help
1002           Say Y if you want to test write support for QNX4 file systems.
1003
1004           It's currently broken, so for now:
1005           answer N.
1006
1007 config ROMFS_FS
1008         tristate "ROM file system support"
1009         depends on BLOCK
1010         ---help---
1011           This is a very small read-only file system mainly intended for
1012           initial ram disks of installation disks, but it could be used for
1013           other read-only media as well.  Read
1014           <file:Documentation/filesystems/romfs.txt> for details.
1015
1016           To compile this file system support as a module, choose M here: the
1017           module will be called romfs.  Note that the file system of your
1018           root partition (the one containing the directory /) cannot be a
1019           module.
1020
1021           If you don't know whether you need it, then you don't need it:
1022           answer N.
1023
1024
1025 config SYSV_FS
1026         tristate "System V/Xenix/V7/Coherent file system support"
1027         depends on BLOCK
1028         help
1029           SCO, Xenix and Coherent are commercial Unix systems for Intel
1030           machines, and Version 7 was used on the DEC PDP-11. Saying Y
1031           here would allow you to read from their floppies and hard disk
1032           partitions.
1033
1034           If you have floppies or hard disk partitions like that, it is likely
1035           that they contain binaries from those other Unix systems; in order
1036           to run these binaries, you will want to install linux-abi which is
1037           a set of kernel modules that lets you run SCO, Xenix, Wyse,
1038           UnixWare, Dell Unix and System V programs under Linux.  It is
1039           available via FTP (user: ftp) from
1040           <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
1041           NOTE: that will work only for binaries from Intel-based systems;
1042           PDP ones will have to wait until somebody ports Linux to -11 ;-)
1043
1044           If you only intend to mount files from some other Unix over the
1045           network using NFS, you don't need the System V file system support
1046           (but you need NFS file system support obviously).
1047
1048           Note that this option is generally not needed for floppies, since a
1049           good portable way to transport files and directories between unixes
1050           (and even other operating systems) is given by the tar program ("man
1051           tar" or preferably "info tar").  Note also that this option has
1052           nothing whatsoever to do with the option "System V IPC". Read about
1053           the System V file system in
1054           <file:Documentation/filesystems/sysv-fs.txt>.
1055           Saying Y here will enlarge your kernel by about 27 KB.
1056
1057           To compile this as a module, choose M here: the module will be called
1058           sysv.
1059
1060           If you haven't heard about all of this before, it's safe to say N.
1061
1062
1063 config UFS_FS
1064         tristate "UFS file system support (read only)"
1065         depends on BLOCK
1066         help
1067           BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
1068           OpenBSD and NeXTstep) use a file system called UFS. Some System V
1069           Unixes can create and mount hard disk partitions and diskettes using
1070           this file system as well. Saying Y here will allow you to read from
1071           these partitions; if you also want to write to them, say Y to the
1072           experimental "UFS file system write support", below. Please read the
1073           file <file:Documentation/filesystems/ufs.txt> for more information.
1074
1075           The recently released UFS2 variant (used in FreeBSD 5.x) is
1076           READ-ONLY supported.
1077
1078           Note that this option is generally not needed for floppies, since a
1079           good portable way to transport files and directories between unixes
1080           (and even other operating systems) is given by the tar program ("man
1081           tar" or preferably "info tar").
1082
1083           When accessing NeXTstep files, you may need to convert them from the
1084           NeXT character set to the Latin1 character set; use the program
1085           recode ("info recode") for this purpose.
1086
1087           To compile the UFS file system support as a module, choose M here: the
1088           module will be called ufs.
1089
1090           If you haven't heard about all of this before, it's safe to say N.
1091
1092 config UFS_FS_WRITE
1093         bool "UFS file system write support (DANGEROUS)"
1094         depends on UFS_FS && EXPERIMENTAL
1095         help
1096           Say Y here if you want to try writing to UFS partitions. This is
1097           experimental, so you should back up your UFS partitions beforehand.
1098
1099 config UFS_DEBUG
1100         bool "UFS debugging"
1101         depends on UFS_FS
1102         help
1103           If you are experiencing any problems with the UFS filesystem, say
1104           Y here.  This will result in _many_ additional debugging messages to be
1105           written to the system log.
1106
1107 endif # MISC_FILESYSTEMS
1108
1109 menuconfig NETWORK_FILESYSTEMS
1110         bool "Network File Systems"
1111         default y
1112         depends on NET
1113         ---help---
1114           Say Y here to get to see options for network filesystems and
1115           filesystem-related networking code, such as NFS daemon and
1116           RPCSEC security modules.
1117
1118           This option alone does not add any kernel code.
1119
1120           If you say N, all options in this submenu will be skipped and
1121           disabled; if unsure, say Y here.
1122
1123 if NETWORK_FILESYSTEMS
1124
1125 config NFS_FS
1126         tristate "NFS client support"
1127         depends on INET
1128         select LOCKD
1129         select SUNRPC
1130         select NFS_ACL_SUPPORT if NFS_V3_ACL
1131         help
1132           Choose Y here if you want to access files residing on other
1133           computers using Sun's Network File System protocol.  To compile
1134           this file system support as a module, choose M here: the module
1135           will be called nfs.
1136
1137           To mount file systems exported by NFS servers, you also need to
1138           install the user space mount.nfs command which can be found in
1139           the Linux nfs-utils package, available from http://linux-nfs.org/.
1140           Information about using the mount command is available in the
1141           mount(8) man page.  More detail about the Linux NFS client
1142           implementation is available via the nfs(5) man page.
1143
1144           Below you can choose which versions of the NFS protocol are
1145           available in the kernel to mount NFS servers.  Support for NFS
1146           version 2 (RFC 1094) is always available when NFS_FS is selected.
1147
1148           To configure a system which mounts its root file system via NFS
1149           at boot time, say Y here, select "Kernel level IP
1150           autoconfiguration" in the NETWORK menu, and select "Root file
1151           system on NFS" below.  You cannot compile this file system as a
1152           module in this case.
1153
1154           If unsure, say N.
1155
1156 config NFS_V3
1157         bool "NFS client support for NFS version 3"
1158         depends on NFS_FS
1159         help
1160           This option enables support for version 3 of the NFS protocol
1161           (RFC 1813) in the kernel's NFS client.
1162
1163           If unsure, say Y.
1164
1165 config NFS_V3_ACL
1166         bool "NFS client support for the NFSv3 ACL protocol extension"
1167         depends on NFS_V3
1168         help
1169           Some NFS servers support an auxiliary NFSv3 ACL protocol that
1170           Sun added to Solaris but never became an official part of the
1171           NFS version 3 protocol.  This protocol extension allows
1172           applications on NFS clients to manipulate POSIX Access Control
1173           Lists on files residing on NFS servers.  NFS servers enforce
1174           ACLs on local files whether this protocol is available or not.
1175
1176           Choose Y here if your NFS server supports the Solaris NFSv3 ACL
1177           protocol extension and you want your NFS client to allow
1178           applications to access and modify ACLs on files on the server.
1179
1180           Most NFS servers don't support the Solaris NFSv3 ACL protocol
1181           extension.  You can choose N here or specify the "noacl" mount
1182           option to prevent your NFS client from trying to use the NFSv3
1183           ACL protocol.
1184
1185           If unsure, say N.
1186
1187 config NFS_V4
1188         bool "NFS client support for NFS version 4 (EXPERIMENTAL)"
1189         depends on NFS_FS && EXPERIMENTAL
1190         select RPCSEC_GSS_KRB5
1191         help
1192           This option enables support for version 4 of the NFS protocol
1193           (RFC 3530) in the kernel's NFS client.
1194
1195           To mount NFS servers using NFSv4, you also need to install user
1196           space programs which can be found in the Linux nfs-utils package,
1197           available from http://linux-nfs.org/.
1198
1199           If unsure, say N.
1200
1201 config ROOT_NFS
1202         bool "Root file system on NFS"
1203         depends on NFS_FS=y && IP_PNP
1204         help
1205           If you want your system to mount its root file system via NFS,
1206           choose Y here.  This is common practice for managing systems
1207           without local permanent storage.  For details, read
1208           <file:Documentation/filesystems/nfsroot.txt>.
1209
1210           Most people say N here.
1211
1212 config NFSD
1213         tristate "NFS server support"
1214         depends on INET
1215         select LOCKD
1216         select SUNRPC
1217         select EXPORTFS
1218         select NFS_ACL_SUPPORT if NFSD_V2_ACL
1219         help
1220           Choose Y here if you want to allow other computers to access
1221           files residing on this system using Sun's Network File System
1222           protocol.  To compile the NFS server support as a module,
1223           choose M here: the module will be called nfsd.
1224
1225           You may choose to use a user-space NFS server instead, in which
1226           case you can choose N here.
1227
1228           To export local file systems using NFS, you also need to install
1229           user space programs which can be found in the Linux nfs-utils
1230           package, available from http://linux-nfs.org/.  More detail about
1231           the Linux NFS server implementation is available via the
1232           exports(5) man page.
1233
1234           Below you can choose which versions of the NFS protocol are
1235           available to clients mounting the NFS server on this system.
1236           Support for NFS version 2 (RFC 1094) is always available when
1237           CONFIG_NFSD is selected.
1238
1239           If unsure, say N.
1240
1241 config NFSD_V2_ACL
1242         bool
1243         depends on NFSD
1244
1245 config NFSD_V3
1246         bool "NFS server support for NFS version 3"
1247         depends on NFSD
1248         help
1249           This option enables support in your system's NFS server for
1250           version 3 of the NFS protocol (RFC 1813).
1251
1252           If unsure, say Y.
1253
1254 config NFSD_V3_ACL
1255         bool "NFS server support for the NFSv3 ACL protocol extension"
1256         depends on NFSD_V3
1257         select NFSD_V2_ACL
1258         help
1259           Solaris NFS servers support an auxiliary NFSv3 ACL protocol that
1260           never became an official part of the NFS version 3 protocol.
1261           This protocol extension allows applications on NFS clients to
1262           manipulate POSIX Access Control Lists on files residing on NFS
1263           servers.  NFS servers enforce POSIX ACLs on local files whether
1264           this protocol is available or not.
1265
1266           This option enables support in your system's NFS server for the
1267           NFSv3 ACL protocol extension allowing NFS clients to manipulate
1268           POSIX ACLs on files exported by your system's NFS server.  NFS
1269           clients which support the Solaris NFSv3 ACL protocol can then
1270           access and modify ACLs on your NFS server.
1271
1272           To store ACLs on your NFS server, you also need to enable ACL-
1273           related CONFIG options for your local file systems of choice.
1274
1275           If unsure, say N.
1276
1277 config NFSD_V4
1278         bool "NFS server support for NFS version 4 (EXPERIMENTAL)"
1279         depends on NFSD && PROC_FS && EXPERIMENTAL
1280         select NFSD_V3
1281         select FS_POSIX_ACL
1282         select RPCSEC_GSS_KRB5
1283         help
1284           This option enables support in your system's NFS server for
1285           version 4 of the NFS protocol (RFC 3530).
1286
1287           To export files using NFSv4, you need to install additional user
1288           space programs which can be found in the Linux nfs-utils package,
1289           available from http://linux-nfs.org/.
1290
1291           If unsure, say N.
1292
1293 config LOCKD
1294         tristate
1295
1296 config LOCKD_V4
1297         bool
1298         depends on NFSD_V3 || NFS_V3
1299         default y
1300
1301 config EXPORTFS
1302         tristate
1303
1304 config NFS_ACL_SUPPORT
1305         tristate
1306         select FS_POSIX_ACL
1307
1308 config NFS_COMMON
1309         bool
1310         depends on NFSD || NFS_FS
1311         default y
1312
1313 config SUNRPC
1314         tristate
1315
1316 config SUNRPC_GSS
1317         tristate
1318
1319 config SUNRPC_XPRT_RDMA
1320         tristate
1321         depends on SUNRPC && INFINIBAND && EXPERIMENTAL
1322         default SUNRPC && INFINIBAND
1323         help
1324           This option enables an RPC client transport capability that
1325           allows the NFS client to mount servers via an RDMA-enabled
1326           transport.
1327
1328           To compile RPC client RDMA transport support as a module,
1329           choose M here: the module will be called xprtrdma.
1330
1331           If unsure, say N.
1332
1333 config SUNRPC_REGISTER_V4
1334         bool "Register local RPC services via rpcbind v4 (EXPERIMENTAL)"
1335         depends on SUNRPC && EXPERIMENTAL
1336         default n
1337         help
1338           Sun added support for registering RPC services at an IPv6
1339           address by creating two new versions of the rpcbind protocol
1340           (RFC 1833).
1341
1342           This option enables support in the kernel RPC server for
1343           registering kernel RPC services via version 4 of the rpcbind
1344           protocol.  If you enable this option, you must run a portmapper
1345           daemon that supports rpcbind protocol version 4.
1346
1347           Serving NFS over IPv6 from knfsd (the kernel's NFS server)
1348           requires that you enable this option and use a portmapper that
1349           supports rpcbind version 4.
1350
1351           If unsure, say N to get traditional behavior (register kernel
1352           RPC services using only rpcbind version 2).  Distributions
1353           using the legacy Linux portmapper daemon must say N here.
1354
1355 config RPCSEC_GSS_KRB5
1356         tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
1357         depends on SUNRPC && EXPERIMENTAL
1358         select SUNRPC_GSS
1359         select CRYPTO
1360         select CRYPTO_MD5
1361         select CRYPTO_DES
1362         select CRYPTO_CBC
1363         help
1364           Choose Y here to enable Secure RPC using the Kerberos version 5
1365           GSS-API mechanism (RFC 1964).
1366
1367           Secure RPC calls with Kerberos require an auxiliary user-space
1368           daemon which may be found in the Linux nfs-utils package
1369           available from http://linux-nfs.org/.  In addition, user-space
1370           Kerberos support should be installed.
1371
1372           If unsure, say N.
1373
1374 config RPCSEC_GSS_SPKM3
1375         tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
1376         depends on SUNRPC && EXPERIMENTAL
1377         select SUNRPC_GSS
1378         select CRYPTO
1379         select CRYPTO_MD5
1380         select CRYPTO_DES
1381         select CRYPTO_CAST5
1382         select CRYPTO_CBC
1383         help
1384           Choose Y here to enable Secure RPC using the SPKM3 public key
1385           GSS-API mechansim (RFC 2025).
1386
1387           Secure RPC calls with SPKM3 require an auxiliary userspace
1388           daemon which may be found in the Linux nfs-utils package
1389           available from http://linux-nfs.org/.
1390
1391           If unsure, say N.
1392
1393 config SMB_FS
1394         tristate "SMB file system support (OBSOLETE, please use CIFS)"
1395         depends on INET
1396         select NLS
1397         help
1398           SMB (Server Message Block) is the protocol Windows for Workgroups
1399           (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
1400           files and printers over local networks.  Saying Y here allows you to
1401           mount their file systems (often called "shares" in this context) and
1402           access them just like any other Unix directory.  Currently, this
1403           works only if the Windows machines use TCP/IP as the underlying
1404           transport protocol, and not NetBEUI.  For details, read
1405           <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
1406           available from <http://www.tldp.org/docs.html#howto>.
1407
1408           Note: if you just want your box to act as an SMB *server* and make
1409           files and printing services available to Windows clients (which need
1410           to have a TCP/IP stack), you don't need to say Y here; you can use
1411           the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
1412           for that.
1413
1414           General information about how to connect Linux, Windows machines and
1415           Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1416
1417           To compile the SMB support as a module, choose M here:
1418           the module will be called smbfs.  Most people say N, however.
1419
1420 config SMB_NLS_DEFAULT
1421         bool "Use a default NLS"
1422         depends on SMB_FS
1423         help
1424           Enabling this will make smbfs use nls translations by default. You
1425           need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
1426           settings and you need to give the default nls for the SMB server as
1427           CONFIG_SMB_NLS_REMOTE.
1428
1429           The nls settings can be changed at mount time, if your smbmount
1430           supports that, using the codepage and iocharset parameters.
1431
1432           smbmount from samba 2.2.0 or later supports this.
1433
1434 config SMB_NLS_REMOTE
1435         string "Default Remote NLS Option"
1436         depends on SMB_NLS_DEFAULT
1437         default "cp437"
1438         help
1439           This setting allows you to specify a default value for which
1440           codepage the server uses. If this field is left blank no
1441           translations will be done by default. The local codepage/charset
1442           default to CONFIG_NLS_DEFAULT.
1443
1444           The nls settings can be changed at mount time, if your smbmount
1445           supports that, using the codepage and iocharset parameters.
1446
1447           smbmount from samba 2.2.0 or later supports this.
1448
1449 source "fs/cifs/Kconfig"
1450
1451 config NCP_FS
1452         tristate "NCP file system support (to mount NetWare volumes)"
1453         depends on IPX!=n || INET
1454         help
1455           NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
1456           used by Novell NetWare clients to talk to file servers.  It is to
1457           IPX what NFS is to TCP/IP, if that helps.  Saying Y here allows you
1458           to mount NetWare file server volumes and to access them just like
1459           any other Unix directory.  For details, please read the file
1460           <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
1461           the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
1462
1463           You do not have to say Y here if you want your Linux box to act as a
1464           file *server* for Novell NetWare clients.
1465
1466           General information about how to connect Linux, Windows machines and
1467           Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1468
1469           To compile this as a module, choose M here: the module will be called
1470           ncpfs.  Say N unless you are connected to a Novell network.
1471
1472 source "fs/ncpfs/Kconfig"
1473
1474 config CODA_FS
1475         tristate "Coda file system support (advanced network fs)"
1476         depends on INET
1477         help
1478           Coda is an advanced network file system, similar to NFS in that it
1479           enables you to mount file systems of a remote server and access them
1480           with regular Unix commands as if they were sitting on your hard
1481           disk.  Coda has several advantages over NFS: support for
1482           disconnected operation (e.g. for laptops), read/write server
1483           replication, security model for authentication and encryption,
1484           persistent client caches and write back caching.
1485
1486           If you say Y here, your Linux box will be able to act as a Coda
1487           *client*.  You will need user level code as well, both for the
1488           client and server.  Servers are currently user level, i.e. they need
1489           no kernel support.  Please read
1490           <file:Documentation/filesystems/coda.txt> and check out the Coda
1491           home page <http://www.coda.cs.cmu.edu/>.
1492
1493           To compile the coda client support as a module, choose M here: the
1494           module will be called coda.
1495
1496 config AFS_FS
1497         tristate "Andrew File System support (AFS) (EXPERIMENTAL)"
1498         depends on INET && EXPERIMENTAL
1499         select AF_RXRPC
1500         help
1501           If you say Y here, you will get an experimental Andrew File System
1502           driver. It currently only supports unsecured read-only AFS access.
1503
1504           See <file:Documentation/filesystems/afs.txt> for more information.
1505
1506           If unsure, say N.
1507
1508 config AFS_DEBUG
1509         bool "AFS dynamic debugging"
1510         depends on AFS_FS
1511         help
1512           Say Y here to make runtime controllable debugging messages appear.
1513
1514           See <file:Documentation/filesystems/afs.txt> for more information.
1515
1516           If unsure, say N.
1517
1518 config 9P_FS
1519         tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
1520         depends on INET && NET_9P && EXPERIMENTAL
1521         help
1522           If you say Y here, you will get experimental support for
1523           Plan 9 resource sharing via the 9P2000 protocol.
1524
1525           See <http://v9fs.sf.net> for more information.
1526
1527           If unsure, say N.
1528
1529 endif # NETWORK_FILESYSTEMS
1530
1531 if BLOCK
1532 menu "Partition Types"
1533
1534 source "fs/partitions/Kconfig"
1535
1536 endmenu
1537 endif
1538
1539 source "fs/nls/Kconfig"
1540 source "fs/dlm/Kconfig"
1541
1542 endmenu