fs/Kconfig

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