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