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