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