fs/Kconfig

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