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