fs/Kconfig

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