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 source "fs/reiserfs/Kconfig"
  31 source "fs/jfs/Kconfig"
  32
  33 config FS_POSIX_ACL
  34 # Posix ACL utility routines (for now, only ext2/ext3/jfs/reiserfs/nfs4)
  35 #
  36 # NOTE: you can implement Posix ACLs without these helpers (XFS does).
  37 #       Never use this symbol for ifdefs.
  38 #
  39         bool
  40         default n
  41
  42 config FILE_LOCKING
  43         bool "Enable POSIX file locking API" if EMBEDDED
  44         default y
  45         help
  46           This option enables standard file locking support, required
  47           for filesystems like NFS and for the flock() system
  48           call. Disabling this option saves about 11k.
  49
  50 source "fs/xfs/Kconfig"
  51 source "fs/gfs2/Kconfig"
  52 source "fs/ocfs2/Kconfig"
  53 source "fs/btrfs/Kconfig"
  54
  55 endif # BLOCK
  56
  57 source "fs/notify/Kconfig"
  58
  59 config QUOTA
  60         bool "Quota support"
  61         help
  62           If you say Y here, you will be able to set per user limits for disk
  63           usage (also called disk quotas). Currently, it works for the
  64           ext2, ext3, and reiserfs file system. ext3 also supports journalled
  65           quotas for which you don't need to run quotacheck(8) after an unclean
  66           shutdown.
  67           For further details, read the Quota mini-HOWTO, available from
  68           <http://www.tldp.org/docs.html#howto>, or the documentation provided
  69           with the quota tools. Probably the quota support is only useful for
  70           multi user systems. If unsure, say N.
  71
  72 config QUOTA_NETLINK_INTERFACE
  73         bool "Report quota messages through netlink interface"
  74         depends on QUOTA && NET
  75         help
  76           If you say Y here, quota warnings (about exceeding softlimit, reaching
  77           hardlimit, etc.) will be reported through netlink interface. If unsure,
  78           say Y.
  79
  80 config PRINT_QUOTA_WARNING
  81         bool "Print quota warnings to console (OBSOLETE)"
  82         depends on QUOTA
  83         default y
  84         help
  85           If you say Y here, quota warnings (about exceeding softlimit, reaching
  86           hardlimit, etc.) will be printed to the process' controlling terminal.
  87           Note that this behavior is currently deprecated and may go away in
  88           future. Please use notification via netlink socket instead.
  89
  90 # Generic support for tree structured quota files. Seleted when needed.
  91 config QUOTA_TREE
  92          tristate
  93
  94 config QFMT_V1
  95         tristate "Old quota format support"
  96         depends on QUOTA
  97         help
  98           This quota format was (is) used by kernels earlier than 2.4.22. If
  99           you have quota working and you don't want to convert to new quota
 100           format say Y here.
 101
 102 config QFMT_V2
 103         tristate "Quota format v2 support"
 104         depends on QUOTA
 105         select QUOTA_TREE
 106         help
 107           This quota format allows using quotas with 32-bit UIDs/GIDs. If you
 108           need this functionality say Y here.
 109
 110 config QUOTACTL
 111         bool
 112         depends on XFS_QUOTA || QUOTA
 113         default y
 114
 115 source "fs/autofs/Kconfig"
 116 source "fs/autofs4/Kconfig"
 117 source "fs/fuse/Kconfig"
 118
 119 config GENERIC_ACL
 120         bool
 121         select FS_POSIX_ACL
 122
 123 if BLOCK
 124 menu "CD-ROM/DVD Filesystems"
 125
 126 source "fs/isofs/Kconfig"
 127 source "fs/udf/Kconfig"
 128
 129 endmenu
 130 endif # BLOCK
 131
 132 if BLOCK
 133 menu "DOS/FAT/NT Filesystems"
 134
 135 source "fs/fat/Kconfig"
 136 source "fs/ntfs/Kconfig"
 137
 138 endmenu
 139 endif # BLOCK
 140
 141 menu "Pseudo filesystems"
 142
 143 source "fs/proc/Kconfig"
 144 source "fs/sysfs/Kconfig"
 145
 146 config TMPFS
 147         bool "Virtual memory file system support (former shm fs)"
 148         help
 149           Tmpfs is a file system which keeps all files in virtual memory.
 150
 151           Everything in tmpfs is temporary in the sense that no files will be
 152           created on your hard drive. The files live in memory and swap
 153           space. If you unmount a tmpfs instance, everything stored therein is
 154           lost.
 155
 156           See <file:Documentation/filesystems/tmpfs.txt> for details.
 157
 158 config TMPFS_POSIX_ACL
 159         bool "Tmpfs POSIX Access Control Lists"
 160         depends on TMPFS
 161         select GENERIC_ACL
 162         help
 163           POSIX Access Control Lists (ACLs) support permissions for users and
 164           groups beyond the owner/group/world scheme.
 165
 166           To learn more about Access Control Lists, visit the POSIX ACLs for
 167           Linux website <http://acl.bestbits.at/>.
 168
 169           If you don't know what Access Control Lists are, say N.
 170
 171 config HUGETLBFS
 172         bool "HugeTLB file system support"
 173         depends on X86 || IA64 || PPC64 || SPARC64 || (SUPERH && MMU) || \
 174                    (S390 && 64BIT) || BROKEN
 175         help
 176           hugetlbfs is a filesystem backing for HugeTLB pages, based on
 177           ramfs. For architectures that support it, say Y here and read
 178           <file:Documentation/vm/hugetlbpage.txt> for details.
 179
 180           If unsure, say N.
 181
 182 config HUGETLB_PAGE
 183         def_bool HUGETLBFS
 184
 185 source "fs/configfs/Kconfig"
 186
 187 endmenu
 188
 189 menuconfig MISC_FILESYSTEMS
 190         bool "Miscellaneous filesystems"
 191         default y
 192         ---help---
 193           Say Y here to get to see options for various miscellaneous
 194           filesystems, such as filesystems that came from other
 195           operating systems.
 196
 197           This option alone does not add any kernel code.
 198
 199           If you say N, all options in this submenu will be skipped and
 200           disabled; if unsure, say Y here.
 201
 202 if MISC_FILESYSTEMS
 203
 204 source "fs/adfs/Kconfig"
 205 source "fs/affs/Kconfig"
 206 source "fs/ecryptfs/Kconfig"
 207 source "fs/hfs/Kconfig"
 208 source "fs/hfsplus/Kconfig"
 209 source "fs/befs/Kconfig"
 210 source "fs/bfs/Kconfig"
 211 source "fs/efs/Kconfig"
 212 source "fs/jffs2/Kconfig"
 213 # UBIFS File system configuration
 214 source "fs/ubifs/Kconfig"
 215 source "fs/cramfs/Kconfig"
 216 source "fs/squashfs/Kconfig"
 217 source "fs/freevxfs/Kconfig"
 218 source "fs/minix/Kconfig"
 219 source "fs/omfs/Kconfig"
 220
 221 config HPFS_FS
 222         tristate "OS/2 HPFS file system support"
 223         depends on BLOCK
 224         help
 225           OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
 226           is the file system used for organizing files on OS/2 hard disk
 227           partitions. Say Y if you want to be able to read files from and
 228           write files to an OS/2 HPFS partition on your hard drive. OS/2
 229           floppies however are in regular MSDOS format, so you don't need this
 230           option in order to be able to read them. Read
 231           <file:Documentation/filesystems/hpfs.txt>.
 232
 233           To compile this file system support as a module, choose M here: the
 234           module will be called hpfs.  If unsure, say N.
 235
 236
 237 config QNX4FS_FS
 238         tristate "QNX4 file system support (read only)"
 239         depends on BLOCK
 240         help
 241           This is the file system used by the real-time operating systems
 242           QNX 4 and QNX 6 (the latter is also called QNX RTP).
 243           Further information is available at <http://www.qnx.com/>.
 244           Say Y if you intend to mount QNX hard disks or floppies.
 245           Unless you say Y to "QNX4FS read-write support" below, you will
 246           only be able to read these file systems.
 247
 248           To compile this file system support as a module, choose M here: the
 249           module will be called qnx4.
 250
 251           If you don't know whether you need it, then you don't need it:
 252           answer N.
 253
 254 config QNX4FS_RW
 255         bool "QNX4FS write support (DANGEROUS)"
 256         depends on QNX4FS_FS && EXPERIMENTAL && BROKEN
 257         help
 258           Say Y if you want to test write support for QNX4 file systems.
 259
 260           It's currently broken, so for now:
 261           answer N.
 262
 263 config ROMFS_FS
 264         tristate "ROM file system support"
 265         depends on BLOCK
 266         ---help---
 267           This is a very small read-only file system mainly intended for
 268           initial ram disks of installation disks, but it could be used for
 269           other read-only media as well.  Read
 270           <file:Documentation/filesystems/romfs.txt> for details.
 271
 272           To compile this file system support as a module, choose M here: the
 273           module will be called romfs.  Note that the file system of your
 274           root partition (the one containing the directory /) cannot be a
 275           module.
 276
 277           If you don't know whether you need it, then you don't need it:
 278           answer N.
 279
 280
 281 config SYSV_FS
 282         tristate "System V/Xenix/V7/Coherent file system support"
 283         depends on BLOCK
 284         help
 285           SCO, Xenix and Coherent are commercial Unix systems for Intel
 286           machines, and Version 7 was used on the DEC PDP-11. Saying Y
 287           here would allow you to read from their floppies and hard disk
 288           partitions.
 289
 290           If you have floppies or hard disk partitions like that, it is likely
 291           that they contain binaries from those other Unix systems; in order
 292           to run these binaries, you will want to install linux-abi which is
 293           a set of kernel modules that lets you run SCO, Xenix, Wyse,
 294           UnixWare, Dell Unix and System V programs under Linux.  It is
 295           available via FTP (user: ftp) from
 296           <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
 297           NOTE: that will work only for binaries from Intel-based systems;
 298           PDP ones will have to wait until somebody ports Linux to -11 ;-)
 299
 300           If you only intend to mount files from some other Unix over the
 301           network using NFS, you don't need the System V file system support
 302           (but you need NFS file system support obviously).
 303
 304           Note that this option is generally not needed for floppies, since a
 305           good portable way to transport files and directories between unixes
 306           (and even other operating systems) is given by the tar program ("man
 307           tar" or preferably "info tar").  Note also that this option has
 308           nothing whatsoever to do with the option "System V IPC". Read about
 309           the System V file system in
 310           <file:Documentation/filesystems/sysv-fs.txt>.
 311           Saying Y here will enlarge your kernel by about 27 KB.
 312
 313           To compile this as a module, choose M here: the module will be called
 314           sysv.
 315
 316           If you haven't heard about all of this before, it's safe to say N.
 317
 318
 319 config UFS_FS
 320         tristate "UFS file system support (read only)"
 321         depends on BLOCK
 322         help
 323           BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
 324           OpenBSD and NeXTstep) use a file system called UFS. Some System V
 325           Unixes can create and mount hard disk partitions and diskettes using
 326           this file system as well. Saying Y here will allow you to read from
 327           these partitions; if you also want to write to them, say Y to the
 328           experimental "UFS file system write support", below. Please read the
 329           file <file:Documentation/filesystems/ufs.txt> for more information.
 330
 331           The recently released UFS2 variant (used in FreeBSD 5.x) is
 332           READ-ONLY supported.
 333
 334           Note that this option is generally not needed for floppies, since a
 335           good portable way to transport files and directories between unixes
 336           (and even other operating systems) is given by the tar program ("man
 337           tar" or preferably "info tar").
 338
 339           When accessing NeXTstep files, you may need to convert them from the
 340           NeXT character set to the Latin1 character set; use the program
 341           recode ("info recode") for this purpose.
 342
 343           To compile the UFS file system support as a module, choose M here: the
 344           module will be called ufs.
 345
 346           If you haven't heard about all of this before, it's safe to say N.
 347
 348 config UFS_FS_WRITE
 349         bool "UFS file system write support (DANGEROUS)"
 350         depends on UFS_FS && EXPERIMENTAL
 351         help
 352           Say Y here if you want to try writing to UFS partitions. This is
 353           experimental, so you should back up your UFS partitions beforehand.
 354
 355 config UFS_DEBUG
 356         bool "UFS debugging"
 357         depends on UFS_FS
 358         help
 359           If you are experiencing any problems with the UFS filesystem, say
 360           Y here.  This will result in _many_ additional debugging messages to be
 361           written to the system log.
 362
 363 endif # MISC_FILESYSTEMS
 364
 365 menuconfig NETWORK_FILESYSTEMS
 366         bool "Network File Systems"
 367         default y
 368         depends on NET
 369         ---help---
 370           Say Y here to get to see options for network filesystems and
 371           filesystem-related networking code, such as NFS daemon and
 372           RPCSEC security modules.
 373
 374           This option alone does not add any kernel code.
 375
 376           If you say N, all options in this submenu will be skipped and
 377           disabled; if unsure, say Y here.
 378
 379 if NETWORK_FILESYSTEMS
 380
 381 config NFS_FS
 382         tristate "NFS client support"
 383         depends on INET
 384         select LOCKD
 385         select SUNRPC
 386         select NFS_ACL_SUPPORT if NFS_V3_ACL
 387         help
 388           Choose Y here if you want to access files residing on other
 389           computers using Sun's Network File System protocol.  To compile
 390           this file system support as a module, choose M here: the module
 391           will be called nfs.
 392
 393           To mount file systems exported by NFS servers, you also need to
 394           install the user space mount.nfs command which can be found in
 395           the Linux nfs-utils package, available from http://linux-nfs.org/.
 396           Information about using the mount command is available in the
 397           mount(8) man page.  More detail about the Linux NFS client
 398           implementation is available via the nfs(5) man page.
 399
 400           Below you can choose which versions of the NFS protocol are
 401           available in the kernel to mount NFS servers.  Support for NFS
 402           version 2 (RFC 1094) is always available when NFS_FS is selected.
 403
 404           To configure a system which mounts its root file system via NFS
 405           at boot time, say Y here, select "Kernel level IP
 406           autoconfiguration" in the NETWORK menu, and select "Root file
 407           system on NFS" below.  You cannot compile this file system as a
 408           module in this case.
 409
 410           If unsure, say N.
 411
 412 config NFS_V3
 413         bool "NFS client support for NFS version 3"
 414         depends on NFS_FS
 415         help
 416           This option enables support for version 3 of the NFS protocol
 417           (RFC 1813) in the kernel's NFS client.
 418
 419           If unsure, say Y.
 420
 421 config NFS_V3_ACL
 422         bool "NFS client support for the NFSv3 ACL protocol extension"
 423         depends on NFS_V3
 424         help
 425           Some NFS servers support an auxiliary NFSv3 ACL protocol that
 426           Sun added to Solaris but never became an official part of the
 427           NFS version 3 protocol.  This protocol extension allows
 428           applications on NFS clients to manipulate POSIX Access Control
 429           Lists on files residing on NFS servers.  NFS servers enforce
 430           ACLs on local files whether this protocol is available or not.
 431
 432           Choose Y here if your NFS server supports the Solaris NFSv3 ACL
 433           protocol extension and you want your NFS client to allow
 434           applications to access and modify ACLs on files on the server.
 435
 436           Most NFS servers don't support the Solaris NFSv3 ACL protocol
 437           extension.  You can choose N here or specify the "noacl" mount
 438           option to prevent your NFS client from trying to use the NFSv3
 439           ACL protocol.
 440
 441           If unsure, say N.
 442
 443 config NFS_V4
 444         bool "NFS client support for NFS version 4 (EXPERIMENTAL)"
 445         depends on NFS_FS && EXPERIMENTAL
 446         select RPCSEC_GSS_KRB5
 447         help
 448           This option enables support for version 4 of the NFS protocol
 449           (RFC 3530) in the kernel's NFS client.
 450
 451           To mount NFS servers using NFSv4, you also need to install user
 452           space programs which can be found in the Linux nfs-utils package,
 453           available from http://linux-nfs.org/.
 454
 455           If unsure, say N.
 456
 457 config ROOT_NFS
 458         bool "Root file system on NFS"
 459         depends on NFS_FS=y && IP_PNP
 460         help
 461           If you want your system to mount its root file system via NFS,
 462           choose Y here.  This is common practice for managing systems
 463           without local permanent storage.  For details, read
 464           <file:Documentation/filesystems/nfsroot.txt>.
 465
 466           Most people say N here.
 467
 468 config NFSD
 469         tristate "NFS server support"
 470         depends on INET
 471         select LOCKD
 472         select SUNRPC
 473         select EXPORTFS
 474         select NFS_ACL_SUPPORT if NFSD_V2_ACL
 475         help
 476           Choose Y here if you want to allow other computers to access
 477           files residing on this system using Sun's Network File System
 478           protocol.  To compile the NFS server support as a module,
 479           choose M here: the module will be called nfsd.
 480
 481           You may choose to use a user-space NFS server instead, in which
 482           case you can choose N here.
 483
 484           To export local file systems using NFS, you also need to install
 485           user space programs which can be found in the Linux nfs-utils
 486           package, available from http://linux-nfs.org/.  More detail about
 487           the Linux NFS server implementation is available via the
 488           exports(5) man page.
 489
 490           Below you can choose which versions of the NFS protocol are
 491           available to clients mounting the NFS server on this system.
 492           Support for NFS version 2 (RFC 1094) is always available when
 493           CONFIG_NFSD is selected.
 494
 495           If unsure, say N.
 496
 497 config NFSD_V2_ACL
 498         bool
 499         depends on NFSD
 500
 501 config NFSD_V3
 502         bool "NFS server support for NFS version 3"
 503         depends on NFSD
 504         help
 505           This option enables support in your system's NFS server for
 506           version 3 of the NFS protocol (RFC 1813).
 507
 508           If unsure, say Y.
 509
 510 config NFSD_V3_ACL
 511         bool "NFS server support for the NFSv3 ACL protocol extension"
 512         depends on NFSD_V3
 513         select NFSD_V2_ACL
 514         help
 515           Solaris NFS servers support an auxiliary NFSv3 ACL protocol that
 516           never became an official part of the NFS version 3 protocol.
 517           This protocol extension allows applications on NFS clients to
 518           manipulate POSIX Access Control Lists on files residing on NFS
 519           servers.  NFS servers enforce POSIX ACLs on local files whether
 520           this protocol is available or not.
 521
 522           This option enables support in your system's NFS server for the
 523           NFSv3 ACL protocol extension allowing NFS clients to manipulate
 524           POSIX ACLs on files exported by your system's NFS server.  NFS
 525           clients which support the Solaris NFSv3 ACL protocol can then
 526           access and modify ACLs on your NFS server.
 527
 528           To store ACLs on your NFS server, you also need to enable ACL-
 529           related CONFIG options for your local file systems of choice.
 530
 531           If unsure, say N.
 532
 533 config NFSD_V4
 534         bool "NFS server support for NFS version 4 (EXPERIMENTAL)"
 535         depends on NFSD && PROC_FS && EXPERIMENTAL
 536         select NFSD_V3
 537         select FS_POSIX_ACL
 538         select RPCSEC_GSS_KRB5
 539         help
 540           This option enables support in your system's NFS server for
 541           version 4 of the NFS protocol (RFC 3530).
 542
 543           To export files using NFSv4, you need to install additional user
 544           space programs which can be found in the Linux nfs-utils package,
 545           available from http://linux-nfs.org/.
 546
 547           If unsure, say N.
 548
 549 config LOCKD
 550         tristate
 551
 552 config LOCKD_V4
 553         bool
 554         depends on NFSD_V3 || NFS_V3
 555         default y
 556
 557 config EXPORTFS
 558         tristate
 559
 560 config NFS_ACL_SUPPORT
 561         tristate
 562         select FS_POSIX_ACL
 563
 564 config NFS_COMMON
 565         bool
 566         depends on NFSD || NFS_FS
 567         default y
 568
 569 config SUNRPC
 570         tristate
 571
 572 config SUNRPC_GSS
 573         tristate
 574
 575 config SUNRPC_XPRT_RDMA
 576         tristate
 577         depends on SUNRPC && INFINIBAND && EXPERIMENTAL
 578         default SUNRPC && INFINIBAND
 579         help
 580           This option enables an RPC client transport capability that
 581           allows the NFS client to mount servers via an RDMA-enabled
 582           transport.
 583
 584           To compile RPC client RDMA transport support as a module,
 585           choose M here: the module will be called xprtrdma.
 586
 587           If unsure, say N.
 588
 589 config SUNRPC_REGISTER_V4
 590         bool "Register local RPC services via rpcbind v4 (EXPERIMENTAL)"
 591         depends on SUNRPC && EXPERIMENTAL
 592         default n
 593         help
 594           Sun added support for registering RPC services at an IPv6
 595           address by creating two new versions of the rpcbind protocol
 596           (RFC 1833).
 597
 598           This option enables support in the kernel RPC server for
 599           registering kernel RPC services via version 4 of the rpcbind
 600           protocol.  If you enable this option, you must run a portmapper
 601           daemon that supports rpcbind protocol version 4.
 602
 603           Serving NFS over IPv6 from knfsd (the kernel's NFS server)
 604           requires that you enable this option and use a portmapper that
 605           supports rpcbind version 4.
 606
 607           If unsure, say N to get traditional behavior (register kernel
 608           RPC services using only rpcbind version 2).  Distributions
 609           using the legacy Linux portmapper daemon must say N here.
 610
 611 config RPCSEC_GSS_KRB5
 612         tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
 613         depends on SUNRPC && EXPERIMENTAL
 614         select SUNRPC_GSS
 615         select CRYPTO
 616         select CRYPTO_MD5
 617         select CRYPTO_DES
 618         select CRYPTO_CBC
 619         help
 620           Choose Y here to enable Secure RPC using the Kerberos version 5
 621           GSS-API mechanism (RFC 1964).
 622
 623           Secure RPC calls with Kerberos require an auxiliary user-space
 624           daemon which may be found in the Linux nfs-utils package
 625           available from http://linux-nfs.org/.  In addition, user-space
 626           Kerberos support should be installed.
 627
 628           If unsure, say N.
 629
 630 config RPCSEC_GSS_SPKM3
 631         tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
 632         depends on SUNRPC && EXPERIMENTAL
 633         select SUNRPC_GSS
 634         select CRYPTO
 635         select CRYPTO_MD5
 636         select CRYPTO_DES
 637         select CRYPTO_CAST5
 638         select CRYPTO_CBC
 639         help
 640           Choose Y here to enable Secure RPC using the SPKM3 public key
 641           GSS-API mechansim (RFC 2025).
 642
 643           Secure RPC calls with SPKM3 require an auxiliary userspace
 644           daemon which may be found in the Linux nfs-utils package
 645           available from http://linux-nfs.org/.
 646
 647           If unsure, say N.
 648
 649 config SMB_FS
 650         tristate "SMB file system support (OBSOLETE, please use CIFS)"
 651         depends on INET
 652         select NLS
 653         help
 654           SMB (Server Message Block) is the protocol Windows for Workgroups
 655           (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
 656           files and printers over local networks.  Saying Y here allows you to
 657           mount their file systems (often called "shares" in this context) and
 658           access them just like any other Unix directory.  Currently, this
 659           works only if the Windows machines use TCP/IP as the underlying
 660           transport protocol, and not NetBEUI.  For details, read
 661           <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
 662           available from <http://www.tldp.org/docs.html#howto>.
 663
 664           Note: if you just want your box to act as an SMB *server* and make
 665           files and printing services available to Windows clients (which need
 666           to have a TCP/IP stack), you don't need to say Y here; you can use
 667           the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
 668           for that.
 669
 670           General information about how to connect Linux, Windows machines and
 671           Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
 672
 673           To compile the SMB support as a module, choose M here:
 674           the module will be called smbfs.  Most people say N, however.
 675
 676 config SMB_NLS_DEFAULT
 677         bool "Use a default NLS"
 678         depends on SMB_FS
 679         help
 680           Enabling this will make smbfs use nls translations by default. You
 681           need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
 682           settings and you need to give the default nls for the SMB server as
 683           CONFIG_SMB_NLS_REMOTE.
 684
 685           The nls settings can be changed at mount time, if your smbmount
 686           supports that, using the codepage and iocharset parameters.
 687
 688           smbmount from samba 2.2.0 or later supports this.
 689
 690 config SMB_NLS_REMOTE
 691         string "Default Remote NLS Option"
 692         depends on SMB_NLS_DEFAULT
 693         default "cp437"
 694         help
 695           This setting allows you to specify a default value for which
 696           codepage the server uses. If this field is left blank no
 697           translations will be done by default. The local codepage/charset
 698           default to CONFIG_NLS_DEFAULT.
 699
 700           The nls settings can be changed at mount time, if your smbmount
 701           supports that, using the codepage and iocharset parameters.
 702
 703           smbmount from samba 2.2.0 or later supports this.
 704
 705 source "fs/cifs/Kconfig"
 706
 707 config NCP_FS
 708         tristate "NCP file system support (to mount NetWare volumes)"
 709         depends on IPX!=n || INET
 710         help
 711           NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
 712           used by Novell NetWare clients to talk to file servers.  It is to
 713           IPX what NFS is to TCP/IP, if that helps.  Saying Y here allows you
 714           to mount NetWare file server volumes and to access them just like
 715           any other Unix directory.  For details, please read the file
 716           <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
 717           the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
 718
 719           You do not have to say Y here if you want your Linux box to act as a
 720           file *server* for Novell NetWare clients.
 721
 722           General information about how to connect Linux, Windows machines and
 723           Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
 724
 725           To compile this as a module, choose M here: the module will be called
 726           ncpfs.  Say N unless you are connected to a Novell network.
 727
 728 source "fs/ncpfs/Kconfig"
 729
 730 config CODA_FS
 731         tristate "Coda file system support (advanced network fs)"
 732         depends on INET
 733         help
 734           Coda is an advanced network file system, similar to NFS in that it
 735           enables you to mount file systems of a remote server and access them
 736           with regular Unix commands as if they were sitting on your hard
 737           disk.  Coda has several advantages over NFS: support for
 738           disconnected operation (e.g. for laptops), read/write server
 739           replication, security model for authentication and encryption,
 740           persistent client caches and write back caching.
 741
 742           If you say Y here, your Linux box will be able to act as a Coda
 743           *client*.  You will need user level code as well, both for the
 744           client and server.  Servers are currently user level, i.e. they need
 745           no kernel support.  Please read
 746           <file:Documentation/filesystems/coda.txt> and check out the Coda
 747           home page <http://www.coda.cs.cmu.edu/>.
 748
 749           To compile the coda client support as a module, choose M here: the
 750           module will be called coda.
 751
 752 config AFS_FS
 753         tristate "Andrew File System support (AFS) (EXPERIMENTAL)"
 754         depends on INET && EXPERIMENTAL
 755         select AF_RXRPC
 756         help
 757           If you say Y here, you will get an experimental Andrew File System
 758           driver. It currently only supports unsecured read-only AFS access.
 759
 760           See <file:Documentation/filesystems/afs.txt> for more information.
 761
 762           If unsure, say N.
 763
 764 config AFS_DEBUG
 765         bool "AFS dynamic debugging"
 766         depends on AFS_FS
 767         help
 768           Say Y here to make runtime controllable debugging messages appear.
 769
 770           See <file:Documentation/filesystems/afs.txt> for more information.
 771
 772           If unsure, say N.
 773
 774 config 9P_FS
 775         tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
 776         depends on INET && NET_9P && EXPERIMENTAL
 777         help
 778           If you say Y here, you will get experimental support for
 779           Plan 9 resource sharing via the 9P2000 protocol.
 780
 781           See <http://v9fs.sf.net> for more information.
 782
 783           If unsure, say N.
 784
 785 endif # NETWORK_FILESYSTEMS
 786
 787 if BLOCK
 788 menu "Partition Types"
 789
 790 source "fs/partitions/Kconfig"
 791
 792 endmenu
 793 endif
 794
 795 source "fs/nls/Kconfig"
 796 source "fs/dlm/Kconfig"
 797
 798 endmenu