1# 2# File system configuration 3# 4 5menu "File systems" 6 7if BLOCK 8 9config EXT2_FS 10 tristate "Second extended fs support" 11 help 12 Ext2 is a standard Linux file system for hard disks. 13 14 To compile this file system support as a module, choose M here: the 15 module will be called ext2. 16 17 If unsure, say Y. 18 19config EXT2_FS_XATTR 20 bool "Ext2 extended attributes" 21 depends on EXT2_FS 22 help 23 Extended attributes are name:value pairs associated with inodes by 24 the kernel or by users (see the attr(5) manual page, or visit 25 <http://acl.bestbits.at/> for details). 26 27 If unsure, say N. 28 29config EXT2_FS_POSIX_ACL 30 bool "Ext2 POSIX Access Control Lists" 31 depends on EXT2_FS_XATTR 32 select FS_POSIX_ACL 33 help 34 Posix Access Control Lists (ACLs) support permissions for users and 35 groups beyond the owner/group/world scheme. 36 37 To learn more about Access Control Lists, visit the Posix ACLs for 38 Linux website <http://acl.bestbits.at/>. 39 40 If you don't know what Access Control Lists are, say N 41 42config EXT2_FS_SECURITY 43 bool "Ext2 Security Labels" 44 depends on EXT2_FS_XATTR 45 help 46 Security labels support alternative access control models 47 implemented by security modules like SELinux. This option 48 enables an extended attribute handler for file security 49 labels in the ext2 filesystem. 50 51 If you are not using a security module that requires using 52 extended attributes for file security labels, say N. 53 54config EXT2_FS_XIP 55 bool "Ext2 execute in place support" 56 depends on EXT2_FS && MMU 57 help 58 Execute in place can be used on memory-backed block devices. If you 59 enable this option, you can select to mount block devices which are 60 capable of this feature without using the page cache. 61 62 If you do not use a block device that is capable of using this, 63 or if unsure, say N. 64 65config FS_XIP 66# execute in place 67 bool 68 depends on EXT2_FS_XIP 69 default y 70 71config EXT3_FS 72 tristate "Ext3 journalling file system support" 73 select JBD 74 help 75 This is the journalling version of the Second extended file system 76 (often called ext3), the de facto standard Linux file system 77 (method to organize files on a storage device) for hard disks. 78 79 The journalling code included in this driver means you do not have 80 to run e2fsck (file system checker) on your file systems after a 81 crash. The journal keeps track of any changes that were being made 82 at the time the system crashed, and can ensure that your file system 83 is consistent without the need for a lengthy check. 84 85 Other than adding the journal to the file system, the on-disk format 86 of ext3 is identical to ext2. It is possible to freely switch 87 between using the ext3 driver and the ext2 driver, as long as the 88 file system has been cleanly unmounted, or e2fsck is run on the file 89 system. 90 91 To add a journal on an existing ext2 file system or change the 92 behavior of ext3 file systems, you can use the tune2fs utility ("man 93 tune2fs"). To modify attributes of files and directories on ext3 94 file systems, use chattr ("man chattr"). You need to be using 95 e2fsprogs version 1.20 or later in order to create ext3 journals 96 (available at <http://sourceforge.net/projects/e2fsprogs/>). 97 98 To compile this file system support as a module, choose M here: the 99 module will be called ext3. 100 101config EXT3_FS_XATTR 102 bool "Ext3 extended attributes" 103 depends on EXT3_FS 104 default y 105 help 106 Extended attributes are name:value pairs associated with inodes by 107 the kernel or by users (see the attr(5) manual page, or visit 108 <http://acl.bestbits.at/> for details). 109 110 If unsure, say N. 111 112 You need this for POSIX ACL support on ext3. 113 114config EXT3_FS_POSIX_ACL 115 bool "Ext3 POSIX Access Control Lists" 116 depends on EXT3_FS_XATTR 117 select FS_POSIX_ACL 118 help 119 Posix Access Control Lists (ACLs) support permissions for users and 120 groups beyond the owner/group/world scheme. 121 122 To learn more about Access Control Lists, visit the Posix ACLs for 123 Linux website <http://acl.bestbits.at/>. 124 125 If you don't know what Access Control Lists are, say N 126 127config EXT3_FS_SECURITY 128 bool "Ext3 Security Labels" 129 depends on EXT3_FS_XATTR 130 help 131 Security labels support alternative access control models 132 implemented by security modules like SELinux. This option 133 enables an extended attribute handler for file security 134 labels in the ext3 filesystem. 135 136 If you are not using a security module that requires using 137 extended attributes for file security labels, say N. 138 139config EXT4DEV_FS 140 tristate "Ext4dev/ext4 extended fs support development (EXPERIMENTAL)" 141 depends on EXPERIMENTAL 142 select JBD2 143 select CRC16 144 help 145 Ext4dev is a predecessor filesystem of the next generation 146 extended fs ext4, based on ext3 filesystem code. It will be 147 renamed ext4 fs later, once ext4dev is mature and stabilized. 148 149 Unlike the change from ext2 filesystem to ext3 filesystem, 150 the on-disk format of ext4dev is not the same as ext3 any more: 151 it is based on extent maps and it supports 48-bit physical block 152 numbers. These combined on-disk format changes will allow 153 ext4dev/ext4 to handle more than 16 TB filesystem volumes -- 154 a hard limit that ext3 cannot overcome without changing the 155 on-disk format. 156 157 Other than extent maps and 48-bit block numbers, ext4dev also is 158 likely to have other new features such as persistent preallocation, 159 high resolution time stamps, and larger file support etc. These 160 features will be added to ext4dev gradually. 161 162 To compile this file system support as a module, choose M here. The 163 module will be called ext4dev. 164 165 If unsure, say N. 166 167config EXT4DEV_FS_XATTR 168 bool "Ext4dev extended attributes" 169 depends on EXT4DEV_FS 170 default y 171 help 172 Extended attributes are name:value pairs associated with inodes by 173 the kernel or by users (see the attr(5) manual page, or visit 174 <http://acl.bestbits.at/> for details). 175 176 If unsure, say N. 177 178 You need this for POSIX ACL support on ext4dev/ext4. 179 180config EXT4DEV_FS_POSIX_ACL 181 bool "Ext4dev POSIX Access Control Lists" 182 depends on EXT4DEV_FS_XATTR 183 select FS_POSIX_ACL 184 help 185 POSIX Access Control Lists (ACLs) support permissions for users and 186 groups beyond the owner/group/world scheme. 187 188 To learn more about Access Control Lists, visit the POSIX ACLs for 189 Linux website <http://acl.bestbits.at/>. 190 191 If you don't know what Access Control Lists are, say N 192 193config EXT4DEV_FS_SECURITY 194 bool "Ext4dev Security Labels" 195 depends on EXT4DEV_FS_XATTR 196 help 197 Security labels support alternative access control models 198 implemented by security modules like SELinux. This option 199 enables an extended attribute handler for file security 200 labels in the ext4dev/ext4 filesystem. 201 202 If you are not using a security module that requires using 203 extended attributes for file security labels, say N. 204 205config JBD 206 tristate 207 help 208 This is a generic journalling layer for block devices. It is 209 currently used by the ext3 and OCFS2 file systems, but it could 210 also be used to add journal support to other file systems or block 211 devices such as RAID or LVM. 212 213 If you are using the ext3 or OCFS2 file systems, you need to 214 say Y here. If you are not using ext3 OCFS2 then you will probably 215 want to say N. 216 217 To compile this device as a module, choose M here: the module will be 218 called jbd. If you are compiling ext3 or OCFS2 into the kernel, 219 you cannot compile this code as a module. 220 221config JBD_DEBUG 222 bool "JBD (ext3) debugging support" 223 depends on JBD && DEBUG_FS 224 help 225 If you are using the ext3 journaled file system (or potentially any 226 other file system/device using JBD), this option allows you to 227 enable debugging output while the system is running, in order to 228 help track down any problems you are having. By default the 229 debugging output will be turned off. 230 231 If you select Y here, then you will be able to turn on debugging 232 with "echo N > /sys/kernel/debug/jbd/jbd-debug", where N is a 233 number between 1 and 5, the higher the number, the more debugging 234 output is generated. To turn debugging off again, do 235 "echo 0 > /sys/kernel/debug/jbd/jbd-debug". 236 237config JBD2 238 tristate 239 select CRC32 240 help 241 This is a generic journaling layer for block devices that support 242 both 32-bit and 64-bit block numbers. It is currently used by 243 the ext4dev/ext4 filesystem, but it could also be used to add 244 journal support to other file systems or block devices such 245 as RAID or LVM. 246 247 If you are using ext4dev/ext4, you need to say Y here. If you are not 248 using ext4dev/ext4 then you will probably want to say N. 249 250 To compile this device as a module, choose M here. The module will be 251 called jbd2. If you are compiling ext4dev/ext4 into the kernel, 252 you cannot compile this code as a module. 253 254config JBD2_DEBUG 255 bool "JBD2 (ext4dev/ext4) debugging support" 256 depends on JBD2 && DEBUG_FS 257 help 258 If you are using the ext4dev/ext4 journaled file system (or 259 potentially any other filesystem/device using JBD2), this option 260 allows you to enable debugging output while the system is running, 261 in order to help track down any problems you are having. 262 By default, the debugging output will be turned off. 263 264 If you select Y here, then you will be able to turn on debugging 265 with "echo N > /sys/kernel/debug/jbd2/jbd2-debug", where N is a 266 number between 1 and 5. The higher the number, the more debugging 267 output is generated. To turn debugging off again, do 268 "echo 0 > /sys/kernel/debug/jbd2/jbd2-debug". 269 270config FS_MBCACHE 271# Meta block cache for Extended Attributes (ext2/ext3/ext4) 272 tristate 273 depends on EXT2_FS_XATTR || EXT3_FS_XATTR || EXT4DEV_FS_XATTR 274 default y if EXT2_FS=y || EXT3_FS=y || EXT4DEV_FS=y 275 default m if EXT2_FS=m || EXT3_FS=m || EXT4DEV_FS=m 276 277config REISERFS_FS 278 tristate "Reiserfs support" 279 help 280 Stores not just filenames but the files themselves in a balanced 281 tree. Uses journalling. 282 283 Balanced trees are more efficient than traditional file system 284 architectural foundations. 285 286 In general, ReiserFS is as fast as ext2, but is very efficient with 287 large directories and small files. Additional patches are needed 288 for NFS and quotas, please see <http://www.namesys.com/> for links. 289 290 It is more easily extended to have features currently found in 291 database and keyword search systems than block allocation based file 292 systems are. The next version will be so extended, and will support 293 plugins consistent with our motto ``It takes more than a license to 294 make source code open.'' 295 296 Read <http://www.namesys.com/> to learn more about reiserfs. 297 298 Sponsored by Threshold Networks, Emusic.com, and Bigstorage.com. 299 300 If you like it, you can pay us to add new features to it that you 301 need, buy a support contract, or pay us to port it to another OS. 302 303config REISERFS_CHECK 304 bool "Enable reiserfs debug mode" 305 depends on REISERFS_FS 306 help 307 If you set this to Y, then ReiserFS will perform every check it can 308 possibly imagine of its internal consistency throughout its 309 operation. It will also go substantially slower. More than once we 310 have forgotten that this was on, and then gone despondent over the 311 latest benchmarks.:-) Use of this option allows our team to go all 312 out in checking for consistency when debugging without fear of its 313 effect on end users. If you are on the verge of sending in a bug 314 report, say Y and you might get a useful error message. Almost 315 everyone should say N. 316 317config REISERFS_PROC_INFO 318 bool "Stats in /proc/fs/reiserfs" 319 depends on REISERFS_FS && PROC_FS 320 help 321 Create under /proc/fs/reiserfs a hierarchy of files, displaying 322 various ReiserFS statistics and internal data at the expense of 323 making your kernel or module slightly larger (+8 KB). This also 324 increases the amount of kernel memory required for each mount. 325 Almost everyone but ReiserFS developers and people fine-tuning 326 reiserfs or tracing problems should say N. 327 328config REISERFS_FS_XATTR 329 bool "ReiserFS extended attributes" 330 depends on REISERFS_FS 331 help 332 Extended attributes are name:value pairs associated with inodes by 333 the kernel or by users (see the attr(5) manual page, or visit 334 <http://acl.bestbits.at/> for details). 335 336 If unsure, say N. 337 338config REISERFS_FS_POSIX_ACL 339 bool "ReiserFS POSIX Access Control Lists" 340 depends on REISERFS_FS_XATTR 341 select FS_POSIX_ACL 342 help 343 Posix Access Control Lists (ACLs) support permissions for users and 344 groups beyond the owner/group/world scheme. 345 346 To learn more about Access Control Lists, visit the Posix ACLs for 347 Linux website <http://acl.bestbits.at/>. 348 349 If you don't know what Access Control Lists are, say N 350 351config REISERFS_FS_SECURITY 352 bool "ReiserFS Security Labels" 353 depends on REISERFS_FS_XATTR 354 help 355 Security labels support alternative access control models 356 implemented by security modules like SELinux. This option 357 enables an extended attribute handler for file security 358 labels in the ReiserFS filesystem. 359 360 If you are not using a security module that requires using 361 extended attributes for file security labels, say N. 362 363config JFS_FS 364 tristate "JFS filesystem support" 365 select NLS 366 help 367 This is a port of IBM's Journaled Filesystem . More information is 368 available in the file <file:Documentation/filesystems/jfs.txt>. 369 370 If you do not intend to use the JFS filesystem, say N. 371 372config JFS_POSIX_ACL 373 bool "JFS POSIX Access Control Lists" 374 depends on JFS_FS 375 select FS_POSIX_ACL 376 help 377 Posix Access Control Lists (ACLs) support permissions for users and 378 groups beyond the owner/group/world scheme. 379 380 To learn more about Access Control Lists, visit the Posix ACLs for 381 Linux website <http://acl.bestbits.at/>. 382 383 If you don't know what Access Control Lists are, say N 384 385config JFS_SECURITY 386 bool "JFS Security Labels" 387 depends on JFS_FS 388 help 389 Security labels support alternative access control models 390 implemented by security modules like SELinux. This option 391 enables an extended attribute handler for file security 392 labels in the jfs filesystem. 393 394 If you are not using a security module that requires using 395 extended attributes for file security labels, say N. 396 397config JFS_DEBUG 398 bool "JFS debugging" 399 depends on JFS_FS 400 help 401 If you are experiencing any problems with the JFS filesystem, say 402 Y here. This will result in additional debugging messages to be 403 written to the system log. Under normal circumstances, this 404 results in very little overhead. 405 406config JFS_STATISTICS 407 bool "JFS statistics" 408 depends on JFS_FS 409 help 410 Enabling this option will cause statistics from the JFS file system 411 to be made available to the user in the /proc/fs/jfs/ directory. 412 413config FS_POSIX_ACL 414# Posix ACL utility routines (for now, only ext2/ext3/jfs/reiserfs/nfs4) 415# 416# NOTE: you can implement Posix ACLs without these helpers (XFS does). 417# Never use this symbol for ifdefs. 418# 419 bool 420 default n 421 422source "fs/xfs/Kconfig" 423source "fs/gfs2/Kconfig" 424 425config OCFS2_FS 426 tristate "OCFS2 file system support" 427 depends on NET && SYSFS 428 select CONFIGFS_FS 429 select JBD 430 select CRC32 431 help 432 OCFS2 is a general purpose extent based shared disk cluster file 433 system with many similarities to ext3. It supports 64 bit inode 434 numbers, and has automatically extending metadata groups which may 435 also make it attractive for non-clustered use. 436 437 You'll want to install the ocfs2-tools package in order to at least 438 get "mount.ocfs2". 439 440 Project web page: http://oss.oracle.com/projects/ocfs2 441 Tools web page: http://oss.oracle.com/projects/ocfs2-tools 442 OCFS2 mailing lists: http://oss.oracle.com/projects/ocfs2/mailman/ 443 444 For more information on OCFS2, see the file 445 <file:Documentation/filesystems/ocfs2.txt>. 446 447config OCFS2_FS_O2CB 448 tristate "O2CB Kernelspace Clustering" 449 depends on OCFS2_FS 450 default y 451 help 452 OCFS2 includes a simple kernelspace clustering package, the OCFS2 453 Cluster Base. It only requires a very small userspace component 454 to configure it. This comes with the standard ocfs2-tools package. 455 O2CB is limited to maintaining a cluster for OCFS2 file systems. 456 It cannot manage any other cluster applications. 457 458 It is always safe to say Y here, as the clustering method is 459 run-time selectable. 460 461config OCFS2_FS_USERSPACE_CLUSTER 462 tristate "OCFS2 Userspace Clustering" 463 depends on OCFS2_FS && DLM 464 default y 465 help 466 This option will allow OCFS2 to use userspace clustering services 467 in conjunction with the DLM in fs/dlm. If you are using a 468 userspace cluster manager, say Y here. 469 470 It is safe to say Y, as the clustering method is run-time 471 selectable. 472 473config OCFS2_FS_STATS 474 bool "OCFS2 statistics" 475 depends on OCFS2_FS 476 default y 477 help 478 This option allows some fs statistics to be captured. Enabling 479 this option may increase the memory consumption. 480 481config OCFS2_DEBUG_MASKLOG 482 bool "OCFS2 logging support" 483 depends on OCFS2_FS 484 default y 485 help 486 The ocfs2 filesystem has an extensive logging system. The system 487 allows selection of events to log via files in /sys/o2cb/logmask/. 488 This option will enlarge your kernel, but it allows debugging of 489 ocfs2 filesystem issues. 490 491config OCFS2_DEBUG_FS 492 bool "OCFS2 expensive checks" 493 depends on OCFS2_FS 494 default n 495 help 496 This option will enable expensive consistency checks. Enable 497 this option for debugging only as it is likely to decrease 498 performance of the filesystem. 499 500endif # BLOCK 501 502config DNOTIFY 503 bool "Dnotify support" 504 default y 505 help 506 Dnotify is a directory-based per-fd file change notification system 507 that uses signals to communicate events to user-space. There exist 508 superior alternatives, but some applications may still rely on 509 dnotify. 510 511 If unsure, say Y. 512 513config INOTIFY 514 bool "Inotify file change notification support" 515 default y 516 ---help--- 517 Say Y here to enable inotify support. Inotify is a file change 518 notification system and a replacement for dnotify. Inotify fixes 519 numerous shortcomings in dnotify and introduces several new features 520 including multiple file events, one-shot support, and unmount 521 notification. 522 523 For more information, see <file:Documentation/filesystems/inotify.txt> 524 525 If unsure, say Y. 526 527config INOTIFY_USER 528 bool "Inotify support for userspace" 529 depends on INOTIFY 530 default y 531 ---help--- 532 Say Y here to enable inotify support for userspace, including the 533 associated system calls. Inotify allows monitoring of both files and 534 directories via a single open fd. Events are read from the file 535 descriptor, which is also select()- and poll()-able. 536 537 For more information, see <file:Documentation/filesystems/inotify.txt> 538 539 If unsure, say Y. 540 541config QUOTA 542 bool "Quota support" 543 help 544 If you say Y here, you will be able to set per user limits for disk 545 usage (also called disk quotas). Currently, it works for the 546 ext2, ext3, and reiserfs file system. ext3 also supports journalled 547 quotas for which you don't need to run quotacheck(8) after an unclean 548 shutdown. 549 For further details, read the Quota mini-HOWTO, available from 550 <http://www.tldp.org/docs.html#howto>, or the documentation provided 551 with the quota tools. Probably the quota support is only useful for 552 multi user systems. If unsure, say N. 553 554config QUOTA_NETLINK_INTERFACE 555 bool "Report quota messages through netlink interface" 556 depends on QUOTA && NET 557 help 558 If you say Y here, quota warnings (about exceeding softlimit, reaching 559 hardlimit, etc.) will be reported through netlink interface. If unsure, 560 say Y. 561 562config PRINT_QUOTA_WARNING 563 bool "Print quota warnings to console (OBSOLETE)" 564 depends on QUOTA 565 default y 566 help 567 If you say Y here, quota warnings (about exceeding softlimit, reaching 568 hardlimit, etc.) will be printed to the process' controlling terminal. 569 Note that this behavior is currently deprecated and may go away in 570 future. Please use notification via netlink socket instead. 571 572config QFMT_V1 573 tristate "Old quota format support" 574 depends on QUOTA 575 help 576 This quota format was (is) used by kernels earlier than 2.4.22. If 577 you have quota working and you don't want to convert to new quota 578 format say Y here. 579 580config QFMT_V2 581 tristate "Quota format v2 support" 582 depends on QUOTA 583 help 584 This quota format allows using quotas with 32-bit UIDs/GIDs. If you 585 need this functionality say Y here. 586 587config QUOTACTL 588 bool 589 depends on XFS_QUOTA || QUOTA 590 default y 591 592config AUTOFS_FS 593 tristate "Kernel automounter support" 594 help 595 The automounter is a tool to automatically mount remote file systems 596 on demand. This implementation is partially kernel-based to reduce 597 overhead in the already-mounted case; this is unlike the BSD 598 automounter (amd), which is a pure user space daemon. 599 600 To use the automounter you need the user-space tools from the autofs 601 package; you can find the location in <file:Documentation/Changes>. 602 You also want to answer Y to "NFS file system support", below. 603 604 If you want to use the newer version of the automounter with more 605 features, say N here and say Y to "Kernel automounter v4 support", 606 below. 607 608 To compile this support as a module, choose M here: the module will be 609 called autofs. 610 611 If you are not a part of a fairly large, distributed network, you 612 probably do not need an automounter, and can say N here. 613 614config AUTOFS4_FS 615 tristate "Kernel automounter version 4 support (also supports v3)" 616 help 617 The automounter is a tool to automatically mount remote file systems 618 on demand. This implementation is partially kernel-based to reduce 619 overhead in the already-mounted case; this is unlike the BSD 620 automounter (amd), which is a pure user space daemon. 621 622 To use the automounter you need the user-space tools from 623 <ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4/>; you also 624 want to answer Y to "NFS file system support", below. 625 626 To compile this support as a module, choose M here: the module will be 627 called autofs4. You will need to add "alias autofs autofs4" to your 628 modules configuration file. 629 630 If you are not a part of a fairly large, distributed network or 631 don't have a laptop which needs to dynamically reconfigure to the 632 local network, you probably do not need an automounter, and can say 633 N here. 634 635config FUSE_FS 636 tristate "Filesystem in Userspace support" 637 help 638 With FUSE it is possible to implement a fully functional filesystem 639 in a userspace program. 640 641 There's also companion library: libfuse. This library along with 642 utilities is available from the FUSE homepage: 643 <http://fuse.sourceforge.net/> 644 645 See <file:Documentation/filesystems/fuse.txt> for more information. 646 See <file:Documentation/Changes> for needed library/utility version. 647 648 If you want to develop a userspace FS, or if you want to use 649 a filesystem based on FUSE, answer Y or M. 650 651config GENERIC_ACL 652 bool 653 select FS_POSIX_ACL 654 655if BLOCK 656menu "CD-ROM/DVD Filesystems" 657 658config ISO9660_FS 659 tristate "ISO 9660 CDROM file system support" 660 help 661 This is the standard file system used on CD-ROMs. It was previously 662 known as "High Sierra File System" and is called "hsfs" on other 663 Unix systems. The so-called Rock-Ridge extensions which allow for 664 long Unix filenames and symbolic links are also supported by this 665 driver. If you have a CD-ROM drive and want to do more with it than 666 just listen to audio CDs and watch its LEDs, say Y (and read 667 <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO, 668 available from <http://www.tldp.org/docs.html#howto>), thereby 669 enlarging your kernel by about 27 KB; otherwise say N. 670 671 To compile this file system support as a module, choose M here: the 672 module will be called isofs. 673 674config JOLIET 675 bool "Microsoft Joliet CDROM extensions" 676 depends on ISO9660_FS 677 select NLS 678 help 679 Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system 680 which allows for long filenames in unicode format (unicode is the 681 new 16 bit character code, successor to ASCII, which encodes the 682 characters of almost all languages of the world; see 683 <http://www.unicode.org/> for more information). Say Y here if you 684 want to be able to read Joliet CD-ROMs under Linux. 685 686config ZISOFS 687 bool "Transparent decompression extension" 688 depends on ISO9660_FS 689 select ZLIB_INFLATE 690 help 691 This is a Linux-specific extension to RockRidge which lets you store 692 data in compressed form on a CD-ROM and have it transparently 693 decompressed when the CD-ROM is accessed. See 694 <http://www.kernel.org/pub/linux/utils/fs/zisofs/> for the tools 695 necessary to create such a filesystem. Say Y here if you want to be 696 able to read such compressed CD-ROMs. 697 698config UDF_FS 699 tristate "UDF file system support" 700 select CRC_ITU_T 701 help 702 This is the new file system used on some CD-ROMs and DVDs. Say Y if 703 you intend to mount DVD discs or CDRW's written in packet mode, or 704 if written to by other UDF utilities, such as DirectCD. 705 Please read <file:Documentation/filesystems/udf.txt>. 706 707 To compile this file system support as a module, choose M here: the 708 module will be called udf. 709 710 If unsure, say N. 711 712config UDF_NLS 713 bool 714 default y 715 depends on (UDF_FS=m && NLS) || (UDF_FS=y && NLS=y) 716 717endmenu 718endif # BLOCK 719 720if BLOCK 721menu "DOS/FAT/NT Filesystems" 722 723config FAT_FS 724 tristate 725 select NLS 726 help 727 If you want to use one of the FAT-based file systems (the MS-DOS and 728 VFAT (Windows 95) file systems), then you must say Y or M here 729 to include FAT support. You will then be able to mount partitions or 730 diskettes with FAT-based file systems and transparently access the 731 files on them, i.e. MSDOS files will look and behave just like all 732 other Unix files. 733 734 This FAT support is not a file system in itself, it only provides 735 the foundation for the other file systems. You will have to say Y or 736 M to at least one of "MSDOS fs support" or "VFAT fs support" in 737 order to make use of it. 738 739 Another way to read and write MSDOS floppies and hard drive 740 partitions from within Linux (but not transparently) is with the 741 mtools ("man mtools") program suite. You don't need to say Y here in 742 order to do that. 743 744 If you need to move large files on floppies between a DOS and a 745 Linux box, say Y here, mount the floppy under Linux with an MSDOS 746 file system and use GNU tar's M option. GNU tar is a program 747 available for Unix and DOS ("man tar" or "info tar"). 748 749 The FAT support will enlarge your kernel by about 37 KB. If unsure, 750 say Y. 751 752 To compile this as a module, choose M here: the module will be called 753 fat. Note that if you compile the FAT support as a module, you 754 cannot compile any of the FAT-based file systems into the kernel 755 -- they will have to be modules as well. 756 757config MSDOS_FS 758 tristate "MSDOS fs support" 759 select FAT_FS 760 help 761 This allows you to mount MSDOS partitions of your hard drive (unless 762 they are compressed; to access compressed MSDOS partitions under 763 Linux, you can either use the DOS emulator DOSEMU, described in the 764 DOSEMU-HOWTO, available from 765 <http://www.tldp.org/docs.html#howto>, or try dmsdosfs in 766 <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you 767 intend to use dosemu with a non-compressed MSDOS partition, say Y 768 here) and MSDOS floppies. This means that file access becomes 769 transparent, i.e. the MSDOS files look and behave just like all 770 other Unix files. 771 772 If you have Windows 95 or Windows NT installed on your MSDOS 773 partitions, you should use the VFAT file system (say Y to "VFAT fs 774 support" below), or you will not be able to see the long filenames 775 generated by Windows 95 / Windows NT. 776 777 This option will enlarge your kernel by about 7 KB. If unsure, 778 answer Y. This will only work if you said Y to "DOS FAT fs support" 779 as well. To compile this as a module, choose M here: the module will 780 be called msdos. 781 782config VFAT_FS 783 tristate "VFAT (Windows-95) fs support" 784 select FAT_FS 785 help 786 This option provides support for normal Windows file systems with 787 long filenames. That includes non-compressed FAT-based file systems 788 used by Windows 95, Windows 98, Windows NT 4.0, and the Unix 789 programs from the mtools package. 790 791 The VFAT support enlarges your kernel by about 10 KB and it only 792 works if you said Y to the "DOS FAT fs support" above. Please read 793 the file <file:Documentation/filesystems/vfat.txt> for details. If 794 unsure, say Y. 795 796 To compile this as a module, choose M here: the module will be called 797 vfat. 798 799config FAT_DEFAULT_CODEPAGE 800 int "Default codepage for FAT" 801 depends on MSDOS_FS || VFAT_FS 802 default 437 803 help 804 This option should be set to the codepage of your FAT filesystems. 805 It can be overridden with the "codepage" mount option. 806 See <file:Documentation/filesystems/vfat.txt> for more information. 807 808config FAT_DEFAULT_IOCHARSET 809 string "Default iocharset for FAT" 810 depends on VFAT_FS 811 default "iso8859-1" 812 help 813 Set this to the default input/output character set you'd 814 like FAT to use. It should probably match the character set 815 that most of your FAT filesystems use, and can be overridden 816 with the "iocharset" mount option for FAT filesystems. 817 Note that "utf8" is not recommended for FAT filesystems. 818 If unsure, you shouldn't set "utf8" here. 819 See <file:Documentation/filesystems/vfat.txt> for more information. 820 821config NTFS_FS 822 tristate "NTFS file system support" 823 select NLS 824 help 825 NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003. 826 827 Saying Y or M here enables read support. There is partial, but 828 safe, write support available. For write support you must also 829 say Y to "NTFS write support" below. 830 831 There are also a number of user-space tools available, called 832 ntfsprogs. These include ntfsundelete and ntfsresize, that work 833 without NTFS support enabled in the kernel. 834 835 This is a rewrite from scratch of Linux NTFS support and replaced 836 the old NTFS code starting with Linux 2.5.11. A backport to 837 the Linux 2.4 kernel series is separately available as a patch 838 from the project web site. 839 840 For more information see <file:Documentation/filesystems/ntfs.txt> 841 and <http://www.linux-ntfs.org/>. 842 843 To compile this file system support as a module, choose M here: the 844 module will be called ntfs. 845 846 If you are not using Windows NT, 2000, XP or 2003 in addition to 847 Linux on your computer it is safe to say N. 848 849config NTFS_DEBUG 850 bool "NTFS debugging support" 851 depends on NTFS_FS 852 help 853 If you are experiencing any problems with the NTFS file system, say 854 Y here. This will result in additional consistency checks to be 855 performed by the driver as well as additional debugging messages to 856 be written to the system log. Note that debugging messages are 857 disabled by default. To enable them, supply the option debug_msgs=1 858 at the kernel command line when booting the kernel or as an option 859 to insmod when loading the ntfs module. Once the driver is active, 860 you can enable debugging messages by doing (as root): 861 echo 1 > /proc/sys/fs/ntfs-debug 862 Replacing the "1" with "0" would disable debug messages. 863 864 If you leave debugging messages disabled, this results in little 865 overhead, but enabling debug messages results in very significant 866 slowdown of the system. 867 868 When reporting bugs, please try to have available a full dump of 869 debugging messages while the misbehaviour was occurring. 870 871config NTFS_RW 872 bool "NTFS write support" 873 depends on NTFS_FS 874 help 875 This enables the partial, but safe, write support in the NTFS driver. 876 877 The only supported operation is overwriting existing files, without 878 changing the file length. No file or directory creation, deletion or 879 renaming is possible. Note only non-resident files can be written to 880 so you may find that some very small files (<500 bytes or so) cannot 881 be written to. 882 883 While we cannot guarantee that it will not damage any data, we have 884 so far not received a single report where the driver would have 885 damaged someones data so we assume it is perfectly safe to use. 886 887 Note: While write support is safe in this version (a rewrite from 888 scratch of the NTFS support), it should be noted that the old NTFS 889 write support, included in Linux 2.5.10 and before (since 1997), 890 is not safe. 891 892 This is currently useful with TopologiLinux. TopologiLinux is run 893 on top of any DOS/Microsoft Windows system without partitioning your 894 hard disk. Unlike other Linux distributions TopologiLinux does not 895 need its own partition. For more information see 896 <http://topologi-linux.sourceforge.net/> 897 898 It is perfectly safe to say N here. 899 900endmenu 901endif # BLOCK 902 903menu "Pseudo filesystems" 904 905source "fs/proc/Kconfig" 906 907config SYSFS 908 bool "sysfs file system support" if EMBEDDED 909 default y 910 help 911 The sysfs filesystem is a virtual filesystem that the kernel uses to 912 export internal kernel objects, their attributes, and their 913 relationships to one another. 914 915 Users can use sysfs to ascertain useful information about the running 916 kernel, such as the devices the kernel has discovered on each bus and 917 which driver each is bound to. sysfs can also be used to tune devices 918 and other kernel subsystems. 919 920 Some system agents rely on the information in sysfs to operate. 921 /sbin/hotplug uses device and object attributes in sysfs to assist in 922 delegating policy decisions, like persistently naming devices. 923 924 sysfs is currently used by the block subsystem to mount the root 925 partition. If sysfs is disabled you must specify the boot device on 926 the kernel boot command line via its major and minor numbers. For 927 example, "root=03:01" for /dev/hda1. 928 929 Designers of embedded systems may wish to say N here to conserve space. 930 931config TMPFS 932 bool "Virtual memory file system support (former shm fs)" 933 help 934 Tmpfs is a file system which keeps all files in virtual memory. 935 936 Everything in tmpfs is temporary in the sense that no files will be 937 created on your hard drive. The files live in memory and swap 938 space. If you unmount a tmpfs instance, everything stored therein is 939 lost. 940 941 See <file:Documentation/filesystems/tmpfs.txt> for details. 942 943config TMPFS_POSIX_ACL 944 bool "Tmpfs POSIX Access Control Lists" 945 depends on TMPFS 946 select GENERIC_ACL 947 help 948 POSIX Access Control Lists (ACLs) support permissions for users and 949 groups beyond the owner/group/world scheme. 950 951 To learn more about Access Control Lists, visit the POSIX ACLs for 952 Linux website <http://acl.bestbits.at/>. 953 954 If you don't know what Access Control Lists are, say N. 955 956config HUGETLBFS 957 bool "HugeTLB file system support" 958 depends on X86 || IA64 || PPC64 || SPARC64 || (SUPERH && MMU) || \ 959 (S390 && 64BIT) || BROKEN 960 help 961 hugetlbfs is a filesystem backing for HugeTLB pages, based on 962 ramfs. For architectures that support it, say Y here and read 963 <file:Documentation/vm/hugetlbpage.txt> for details. 964 965 If unsure, say N. 966 967config HUGETLB_PAGE 968 def_bool HUGETLBFS 969 970config CONFIGFS_FS 971 tristate "Userspace-driven configuration filesystem" 972 depends on SYSFS 973 help 974 configfs is a ram-based filesystem that provides the converse 975 of sysfs's functionality. Where sysfs is a filesystem-based 976 view of kernel objects, configfs is a filesystem-based manager 977 of kernel objects, or config_items. 978 979 Both sysfs and configfs can and should exist together on the 980 same system. One is not a replacement for the other. 981 982endmenu 983 984menu "Miscellaneous filesystems" 985 986config ADFS_FS 987 tristate "ADFS file system support (EXPERIMENTAL)" 988 depends on BLOCK && EXPERIMENTAL 989 help 990 The Acorn Disc Filing System is the standard file system of the 991 RiscOS operating system which runs on Acorn's ARM-based Risc PC 992 systems and the Acorn Archimedes range of machines. If you say Y 993 here, Linux will be able to read from ADFS partitions on hard drives 994 and from ADFS-formatted floppy discs. If you also want to be able to 995 write to those devices, say Y to "ADFS write support" below. 996 997 The ADFS partition should be the first partition (i.e., 998 /dev/[hs]d?1) on each of your drives. Please read the file 999 <file:Documentation/filesystems/adfs.txt> for further details. 1000
1001 To compile this code as a module, choose M here: the module will be 1002 called adfs. 1003 1004 If unsure, say N. 1005 1006config ADFS_FS_RW 1007 bool "ADFS write support (DANGEROUS)" 1008 depends on ADFS_FS 1009 help 1010 If you say Y here, you will be able to write to ADFS partitions on 1011 hard drives and ADFS-formatted floppy disks. This is experimental 1012 codes, so if you're unsure, say N. 1013 1014config AFFS_FS 1015 tristate "Amiga FFS file system support (EXPERIMENTAL)" 1016 depends on BLOCK && EXPERIMENTAL 1017 help 1018 The Fast File System (FFS) is the common file system used on hard 1019 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y 1020 if you want to be able to read and write files from and to an Amiga 1021 FFS partition on your hard drive. Amiga floppies however cannot be 1022 read with this driver due to an incompatibility of the floppy 1023 controller used in an Amiga and the standard floppy controller in 1024 PCs and workstations. Read <file:Documentation/filesystems/affs.txt> 1025 and <file:fs/affs/Changes>. 1026 1027 With this driver you can also mount disk files used by Bernd 1028 Schmidt's Un*X Amiga Emulator 1029 (<http://www.freiburg.linux.de/~uae/>). 1030 If you want to do this, you will also need to say Y or M to "Loop 1031 device support", above. 1032 1033 To compile this file system support as a module, choose M here: the 1034 module will be called affs. If unsure, say N. 1035 1036config ECRYPT_FS 1037 tristate "eCrypt filesystem layer support (EXPERIMENTAL)" 1038 depends on EXPERIMENTAL && KEYS && CRYPTO && NET 1039 help 1040 Encrypted filesystem that operates on the VFS layer. See 1041 <file:Documentation/filesystems/ecryptfs.txt> to learn more about 1042 eCryptfs. Userspace components are required and can be 1043 obtained from <http://ecryptfs.sf.net>. 1044 1045 To compile this file system support as a module, choose M here: the 1046 module will be called ecryptfs. 1047 1048config HFS_FS 1049 tristate "Apple Macintosh file system support (EXPERIMENTAL)" 1050 depends on BLOCK && EXPERIMENTAL 1051 select NLS 1052 help 1053 If you say Y here, you will be able to mount Macintosh-formatted 1054 floppy disks and hard drive partitions with full read-write access. 1055 Please read <file:Documentation/filesystems/hfs.txt> to learn about 1056 the available mount options. 1057 1058 To compile this file system support as a module, choose M here: the 1059 module will be called hfs. 1060 1061config HFSPLUS_FS 1062 tristate "Apple Extended HFS file system support" 1063 depends on BLOCK 1064 select NLS 1065 select NLS_UTF8 1066 help 1067 If you say Y here, you will be able to mount extended format 1068 Macintosh-formatted hard drive partitions with full read-write access. 1069 1070 This file system is often called HFS+ and was introduced with 1071 MacOS 8. It includes all Mac specific filesystem data such as 1072 data forks and creator codes, but it also has several UNIX 1073 style features such as file ownership and permissions. 1074 1075config BEFS_FS 1076 tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)" 1077 depends on BLOCK && EXPERIMENTAL 1078 select NLS 1079 help 1080 The BeOS File System (BeFS) is the native file system of Be, Inc's 1081 BeOS. Notable features include support for arbitrary attributes 1082 on files and directories, and database-like indices on selected 1083 attributes. (Also note that this driver doesn't make those features 1084 available at this time). It is a 64 bit filesystem, so it supports 1085 extremely large volumes and files. 1086 1087 If you use this filesystem, you should also say Y to at least one 1088 of the NLS (native language support) options below. 1089 1090 If you don't know what this is about, say N. 1091 1092 To compile this as a module, choose M here: the module will be 1093 called befs. 1094 1095config BEFS_DEBUG 1096 bool "Debug BeFS" 1097 depends on BEFS_FS 1098 help 1099 If you say Y here, you can use the 'debug' mount option to enable 1100 debugging output from the driver. 1101 1102config BFS_FS 1103 tristate "BFS file system support (EXPERIMENTAL)" 1104 depends on BLOCK && EXPERIMENTAL 1105 help 1106 Boot File System (BFS) is a file system used under SCO UnixWare to 1107 allow the bootloader access to the kernel image and other important 1108 files during the boot process. It is usually mounted under /stand 1109 and corresponds to the slice marked as "STAND" in the UnixWare 1110 partition. You should say Y if you want to read or write the files 1111 on your /stand slice from within Linux. You then also need to say Y 1112 to "UnixWare slices support", below. More information about the BFS 1113 file system is contained in the file 1114 <file:Documentation/filesystems/bfs.txt>. 1115 1116 If you don't know what this is about, say N. 1117 1118 To compile this as a module, choose M here: the module will be called 1119 bfs. Note that the file system of your root partition (the one 1120 containing the directory /) cannot be compiled as a module. 1121 1122 1123 1124config EFS_FS 1125 tristate "EFS file system support (read only) (EXPERIMENTAL)" 1126 depends on BLOCK && EXPERIMENTAL 1127 help 1128 EFS is an older file system used for non-ISO9660 CD-ROMs and hard 1129 disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer 1130 uses the XFS file system for hard disk partitions however). 1131 1132 This implementation only offers read-only access. If you don't know 1133 what all this is about, it's safe to say N. For more information 1134 about EFS see its home page at <http://aeschi.ch.eu.org/efs/>. 1135 1136 To compile the EFS file system support as a module, choose M here: the 1137 module will be called efs. 1138 1139config JFFS2_FS 1140 tristate "Journalling Flash File System v2 (JFFS2) support" 1141 select CRC32 1142 depends on MTD 1143 help 1144 JFFS2 is the second generation of the Journalling Flash File System 1145 for use on diskless embedded devices. It provides improved wear 1146 levelling, compression and support for hard links. You cannot use 1147 this on normal block devices, only on 'MTD' devices. 1148 1149 Further information on the design and implementation of JFFS2 is 1150 available at <http://sources.redhat.com/jffs2/>. 1151 1152config JFFS2_FS_DEBUG 1153 int "JFFS2 debugging verbosity (0 = quiet, 2 = noisy)" 1154 depends on JFFS2_FS 1155 default "0" 1156 help 1157 This controls the amount of debugging messages produced by the JFFS2 1158 code. Set it to zero for use in production systems. For evaluation, 1159 testing and debugging, it's advisable to set it to one. This will 1160 enable a few assertions and will print debugging messages at the 1161 KERN_DEBUG loglevel, where they won't normally be visible. Level 2 1162 is unlikely to be useful - it enables extra debugging in certain 1163 areas which at one point needed debugging, but when the bugs were 1164 located and fixed, the detailed messages were relegated to level 2. 1165 1166 If reporting bugs, please try to have available a full dump of the 1167 messages at debug level 1 while the misbehaviour was occurring. 1168 1169config JFFS2_FS_WRITEBUFFER 1170 bool "JFFS2 write-buffering support" 1171 depends on JFFS2_FS 1172 default y 1173 help 1174 This enables the write-buffering support in JFFS2. 1175 1176 This functionality is required to support JFFS2 on the following 1177 types of flash devices: 1178 - NAND flash 1179 - NOR flash with transparent ECC 1180 - DataFlash 1181 1182config JFFS2_FS_WBUF_VERIFY 1183 bool "Verify JFFS2 write-buffer reads" 1184 depends on JFFS2_FS_WRITEBUFFER 1185 default n 1186 help 1187 This causes JFFS2 to read back every page written through the 1188 write-buffer, and check for errors. 1189 1190config JFFS2_SUMMARY 1191 bool "JFFS2 summary support (EXPERIMENTAL)" 1192 depends on JFFS2_FS && EXPERIMENTAL 1193 default n 1194 help 1195 This feature makes it possible to use summary information 1196 for faster filesystem mount. 1197 1198 The summary information can be inserted into a filesystem image 1199 by the utility 'sumtool'. 1200 1201 If unsure, say 'N'. 1202 1203config JFFS2_FS_XATTR 1204 bool "JFFS2 XATTR support (EXPERIMENTAL)" 1205 depends on JFFS2_FS && EXPERIMENTAL 1206 default n 1207 help 1208 Extended attributes are name:value pairs associated with inodes by 1209 the kernel or by users (see the attr(5) manual page, or visit 1210 <http://acl.bestbits.at/> for details). 1211 1212 If unsure, say N. 1213 1214config JFFS2_FS_POSIX_ACL 1215 bool "JFFS2 POSIX Access Control Lists" 1216 depends on JFFS2_FS_XATTR 1217 default y 1218 select FS_POSIX_ACL 1219 help 1220 Posix Access Control Lists (ACLs) support permissions for users and 1221 groups beyond the owner/group/world scheme. 1222 1223 To learn more about Access Control Lists, visit the Posix ACLs for 1224 Linux website <http://acl.bestbits.at/>. 1225 1226 If you don't know what Access Control Lists are, say N 1227 1228config JFFS2_FS_SECURITY 1229 bool "JFFS2 Security Labels" 1230 depends on JFFS2_FS_XATTR 1231 default y 1232 help 1233 Security labels support alternative access control models 1234 implemented by security modules like SELinux. This option 1235 enables an extended attribute handler for file security 1236 labels in the jffs2 filesystem. 1237 1238 If you are not using a security module that requires using 1239 extended attributes for file security labels, say N. 1240 1241config JFFS2_COMPRESSION_OPTIONS 1242 bool "Advanced compression options for JFFS2" 1243 depends on JFFS2_FS 1244 default n 1245 help 1246 Enabling this option allows you to explicitly choose which 1247 compression modules, if any, are enabled in JFFS2. Removing 1248 compressors can mean you cannot read existing file systems, 1249 and enabling experimental compressors can mean that you 1250 write a file system which cannot be read by a standard kernel. 1251 1252 If unsure, you should _definitely_ say 'N'. 1253 1254config JFFS2_ZLIB 1255 bool "JFFS2 ZLIB compression support" if JFFS2_COMPRESSION_OPTIONS 1256 select ZLIB_INFLATE 1257 select ZLIB_DEFLATE 1258 depends on JFFS2_FS 1259 default y 1260 help 1261 Zlib is designed to be a free, general-purpose, legally unencumbered, 1262 lossless data-compression library for use on virtually any computer 1263 hardware and operating system. See <http://www.gzip.org/zlib/> for 1264 further information. 1265 1266 Say 'Y' if unsure. 1267 1268config JFFS2_LZO 1269 bool "JFFS2 LZO compression support" if JFFS2_COMPRESSION_OPTIONS 1270 select LZO_COMPRESS 1271 select LZO_DECOMPRESS 1272 depends on JFFS2_FS 1273 default n 1274 help 1275 minilzo-based compression. Generally works better than Zlib. 1276 1277 This feature was added in July, 2007. Say 'N' if you need 1278 compatibility with older bootloaders or kernels. 1279 1280config JFFS2_RTIME 1281 bool "JFFS2 RTIME compression support" if JFFS2_COMPRESSION_OPTIONS 1282 depends on JFFS2_FS 1283 default y 1284 help 1285 Rtime does manage to recompress already-compressed data. Say 'Y' if unsure. 1286 1287config JFFS2_RUBIN 1288 bool "JFFS2 RUBIN compression support" if JFFS2_COMPRESSION_OPTIONS 1289 depends on JFFS2_FS 1290 default n 1291 help 1292 RUBINMIPS and DYNRUBIN compressors. Say 'N' if unsure. 1293 1294choice 1295 prompt "JFFS2 default compression mode" if JFFS2_COMPRESSION_OPTIONS 1296 default JFFS2_CMODE_PRIORITY 1297 depends on JFFS2_FS 1298 help 1299 You can set here the default compression mode of JFFS2 from 1300 the available compression modes. Don't touch if unsure. 1301 1302config JFFS2_CMODE_NONE 1303 bool "no compression" 1304 help 1305 Uses no compression. 1306 1307config JFFS2_CMODE_PRIORITY 1308 bool "priority" 1309 help 1310 Tries the compressors in a predefined order and chooses the first 1311 successful one. 1312 1313config JFFS2_CMODE_SIZE 1314 bool "size (EXPERIMENTAL)" 1315 help 1316 Tries all compressors and chooses the one which has the smallest 1317 result. 1318 1319config JFFS2_CMODE_FAVOURLZO 1320 bool "Favour LZO" 1321 help 1322 Tries all compressors and chooses the one which has the smallest 1323 result but gives some preference to LZO (which has faster 1324 decompression) at the expense of size. 1325 1326endchoice 1327 1328# UBIFS File system configuration 1329source "fs/ubifs/Kconfig" 1330 1331config CRAMFS 1332 tristate "Compressed ROM file system support (cramfs)" 1333 depends on BLOCK 1334 select ZLIB_INFLATE 1335 help 1336 Saying Y here includes support for CramFs (Compressed ROM File 1337 System). CramFs is designed to be a simple, small, and compressed 1338 file system for ROM based embedded systems. CramFs is read-only, 1339 limited to 256MB file systems (with 16MB files), and doesn't support 1340 16/32 bits uid/gid, hard links and timestamps. 1341 1342 See <file:Documentation/filesystems/cramfs.txt> and 1343 <file:fs/cramfs/README> for further information. 1344 1345 To compile this as a module, choose M here: the module will be called 1346 cramfs. Note that the root file system (the one containing the 1347 directory /) cannot be compiled as a module. 1348 1349 If unsure, say N. 1350 1351config VXFS_FS 1352 tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)" 1353 depends on BLOCK 1354 help 1355 FreeVxFS is a file system driver that support the VERITAS VxFS(TM) 1356 file system format. VERITAS VxFS(TM) is the standard file system 1357 of SCO UnixWare (and possibly others) and optionally available 1358 for Sunsoft Solaris, HP-UX and many other operating systems. 1359 Currently only readonly access is supported. 1360 1361 NOTE: the file system type as used by mount(1), mount(2) and 1362 fstab(5) is 'vxfs' as it describes the file system format, not 1363 the actual driver. 1364 1365 To compile this as a module, choose M here: the module will be 1366 called freevxfs. If unsure, say N. 1367 1368config MINIX_FS 1369 tristate "Minix file system support" 1370 depends on BLOCK 1371 help 1372 Minix is a simple operating system used in many classes about OS's. 1373 The minix file system (method to organize files on a hard disk 1374 partition or a floppy disk) was the original file system for Linux, 1375 but has been superseded by the second extended file system ext2fs. 1376 You don't want to use the minix file system on your hard disk 1377 because of certain built-in restrictions, but it is sometimes found 1378 on older Linux floppy disks. This option will enlarge your kernel 1379 by about 28 KB. If unsure, say N. 1380 1381 To compile this file system support as a module, choose M here: the 1382 module will be called minix. Note that the file system of your root 1383 partition (the one containing the directory /) cannot be compiled as 1384 a module. 1385 1386config OMFS_FS 1387 tristate "SonicBlue Optimized MPEG File System support" 1388 depends on BLOCK 1389 select CRC_ITU_T 1390 help 1391 This is the proprietary file system used by the Rio Karma music 1392 player and ReplayTV DVR. Despite the name, this filesystem is not 1393 more efficient than a standard FS for MPEG files, in fact likely 1394 the opposite is true. Say Y if you have either of these devices 1395 and wish to mount its disk. 1396 1397 To compile this file system support as a module, choose M here: the 1398 module will be called omfs. If unsure, say N. 1399 1400config HPFS_FS 1401 tristate "OS/2 HPFS file system support" 1402 depends on BLOCK 1403 help 1404 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS 1405 is the file system used for organizing files on OS/2 hard disk 1406 partitions. Say Y if you want to be able to read files from and 1407 write files to an OS/2 HPFS partition on your hard drive. OS/2 1408 floppies however are in regular MSDOS format, so you don't need this 1409 option in order to be able to read them. Read 1410 <file:Documentation/filesystems/hpfs.txt>. 1411 1412 To compile this file system support as a module, choose M here: the 1413 module will be called hpfs. If unsure, say N. 1414 1415 1416config QNX4FS_FS 1417 tristate "QNX4 file system support (read only)" 1418 depends on BLOCK 1419 help 1420 This is the file system used by the real-time operating systems 1421 QNX 4 and QNX 6 (the latter is also called QNX RTP). 1422 Further information is available at <http://www.qnx.com/>. 1423 Say Y if you intend to mount QNX hard disks or floppies. 1424 Unless you say Y to "QNX4FS read-write support" below, you will 1425 only be able to read these file systems. 1426 1427 To compile this file system support as a module, choose M here: the 1428 module will be called qnx4. 1429 1430 If you don't know whether you need it, then you don't need it: 1431 answer N. 1432 1433config QNX4FS_RW 1434 bool "QNX4FS write support (DANGEROUS)" 1435 depends on QNX4FS_FS && EXPERIMENTAL && BROKEN 1436 help 1437 Say Y if you want to test write support for QNX4 file systems. 1438 1439 It's currently broken, so for now: 1440 answer N. 1441 1442config ROMFS_FS 1443 tristate "ROM file system support" 1444 depends on BLOCK 1445 ---help--- 1446 This is a very small read-only file system mainly intended for 1447 initial ram disks of installation disks, but it could be used for 1448 other read-only media as well. Read 1449 <file:Documentation/filesystems/romfs.txt> for details. 1450 1451 To compile this file system support as a module, choose M here: the 1452 module will be called romfs. Note that the file system of your 1453 root partition (the one containing the directory /) cannot be a 1454 module. 1455 1456 If you don't know whether you need it, then you don't need it: 1457 answer N. 1458 1459 1460config SYSV_FS 1461 tristate "System V/Xenix/V7/Coherent file system support" 1462 depends on BLOCK 1463 help 1464 SCO, Xenix and Coherent are commercial Unix systems for Intel 1465 machines, and Version 7 was used on the DEC PDP-11. Saying Y 1466 here would allow you to read from their floppies and hard disk 1467 partitions. 1468 1469 If you have floppies or hard disk partitions like that, it is likely 1470 that they contain binaries from those other Unix systems; in order 1471 to run these binaries, you will want to install linux-abi which is 1472 a set of kernel modules that lets you run SCO, Xenix, Wyse, 1473 UnixWare, Dell Unix and System V programs under Linux. It is 1474 available via FTP (user: ftp) from 1475 <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>). 1476 NOTE: that will work only for binaries from Intel-based systems; 1477 PDP ones will have to wait until somebody ports Linux to -11 ;-) 1478 1479 If you only intend to mount files from some other Unix over the 1480 network using NFS, you don't need the System V file system support 1481 (but you need NFS file system support obviously). 1482 1483 Note that this option is generally not needed for floppies, since a 1484 good portable way to transport files and directories between unixes 1485 (and even other operating systems) is given by the tar program ("man 1486 tar" or preferably "info tar"). Note also that this option has 1487 nothing whatsoever to do with the option "System V IPC". Read about 1488 the System V file system in 1489 <file:Documentation/filesystems/sysv-fs.txt>. 1490 Saying Y here will enlarge your kernel by about 27 KB. 1491 1492 To compile this as a module, choose M here: the module will be called 1493 sysv. 1494 1495 If you haven't heard about all of this before, it's safe to say N. 1496 1497 1498config UFS_FS 1499 tristate "UFS file system support (read only)" 1500 depends on BLOCK 1501 help 1502 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD, 1503 OpenBSD and NeXTstep) use a file system called UFS. Some System V 1504 Unixes can create and mount hard disk partitions and diskettes using 1505 this file system as well. Saying Y here will allow you to read from 1506 these partitions; if you also want to write to them, say Y to the 1507 experimental "UFS file system write support", below. Please read the 1508 file <file:Documentation/filesystems/ufs.txt> for more information. 1509 1510 The recently released UFS2 variant (used in FreeBSD 5.x) is 1511 READ-ONLY supported. 1512 1513 Note that this option is generally not needed for floppies, since a 1514 good portable way to transport files and directories between unixes 1515 (and even other operating systems) is given by the tar program ("man 1516 tar" or preferably "info tar"). 1517 1518 When accessing NeXTstep files, you may need to convert them from the 1519 NeXT character set to the Latin1 character set; use the program 1520 recode ("info recode") for this purpose. 1521 1522 To compile the UFS file system support as a module, choose M here: the 1523 module will be called ufs. 1524 1525 If you haven't heard about all of this before, it's safe to say N. 1526 1527config UFS_FS_WRITE 1528 bool "UFS file system write support (DANGEROUS)" 1529 depends on UFS_FS && EXPERIMENTAL 1530 help 1531 Say Y here if you want to try writing to UFS partitions. This is 1532 experimental, so you should back up your UFS partitions beforehand. 1533 1534config UFS_DEBUG 1535 bool "UFS debugging" 1536 depends on UFS_FS 1537 help 1538 If you are experiencing any problems with the UFS filesystem, say 1539 Y here. This will result in _many_ additional debugging messages to be 1540 written to the system log. 1541 1542endmenu 1543 1544menuconfig NETWORK_FILESYSTEMS 1545 bool "Network File Systems" 1546 default y 1547 depends on NET 1548 ---help--- 1549 Say Y here to get to see options for network filesystems and 1550 filesystem-related networking code, such as NFS daemon and 1551 RPCSEC security modules. 1552 1553 This option alone does not add any kernel code. 1554 1555 If you say N, all options in this submenu will be skipped and 1556 disabled; if unsure, say Y here. 1557 1558if NETWORK_FILESYSTEMS 1559 1560config NFS_FS 1561 tristate "NFS client support" 1562 depends on INET 1563 select LOCKD 1564 select SUNRPC 1565 select NFS_ACL_SUPPORT if NFS_V3_ACL 1566 help 1567 Choose Y here if you want to access files residing on other 1568 computers using Sun's Network File System protocol. To compile 1569 this file system support as a module, choose M here: the module 1570 will be called nfs. 1571 1572 To mount file systems exported by NFS servers, you also need to 1573 install the user space mount.nfs command which can be found in 1574 the Linux nfs-utils package, available from http://linux-nfs.org/. 1575 Information about using the mount command is available in the 1576 mount(8) man page. More detail about the Linux NFS client 1577 implementation is available via the nfs(5) man page. 1578 1579 Below you can choose which versions of the NFS protocol are 1580 available in the kernel to mount NFS servers. Support for NFS 1581 version 2 (RFC 1094) is always available when NFS_FS is selected. 1582 1583 To configure a system which mounts its root file system via NFS 1584 at boot time, say Y here, select "Kernel level IP 1585 autoconfiguration" in the NETWORK menu, and select "Root file 1586 system on NFS" below. You cannot compile this file system as a 1587 module in this case. 1588 1589 If unsure, say N. 1590 1591config NFS_V3 1592 bool "NFS client support for NFS version 3" 1593 depends on NFS_FS 1594 help 1595 This option enables support for version 3 of the NFS protocol 1596 (RFC 1813) in the kernel's NFS client. 1597 1598 If unsure, say Y. 1599 1600config NFS_V3_ACL 1601 bool "NFS client support for the NFSv3 ACL protocol extension" 1602 depends on NFS_V3 1603 help 1604 Some NFS servers support an auxiliary NFSv3 ACL protocol that 1605 Sun added to Solaris but never became an official part of the 1606 NFS version 3 protocol. This protocol extension allows 1607 applications on NFS clients to manipulate POSIX Access Control 1608 Lists on files residing on NFS servers. NFS servers enforce 1609 ACLs on local files whether this protocol is available or not. 1610 1611 Choose Y here if your NFS server supports the Solaris NFSv3 ACL 1612 protocol extension and you want your NFS client to allow 1613 applications to access and modify ACLs on files on the server. 1614 1615 Most NFS servers don't support the Solaris NFSv3 ACL protocol 1616 extension. You can choose N here or specify the "noacl" mount 1617 option to prevent your NFS client from trying to use the NFSv3 1618 ACL protocol. 1619 1620 If unsure, say N. 1621 1622config NFS_V4 1623 bool "NFS client support for NFS version 4 (EXPERIMENTAL)" 1624 depends on NFS_FS && EXPERIMENTAL 1625 select RPCSEC_GSS_KRB5 1626 help 1627 This option enables support for version 4 of the NFS protocol 1628 (RFC 3530) in the kernel's NFS client. 1629 1630 To mount NFS servers using NFSv4, you also need to install user 1631 space programs which can be found in the Linux nfs-utils package, 1632 available from http://linux-nfs.org/. 1633 1634 If unsure, say N. 1635 1636config ROOT_NFS 1637 bool "Root file system on NFS" 1638 depends on NFS_FS=y && IP_PNP 1639 help 1640 If you want your system to mount its root file system via NFS, 1641 choose Y here. This is common practice for managing systems 1642 without local permanent storage. For details, read 1643 <file:Documentation/filesystems/nfsroot.txt>. 1644 1645 Most people say N here. 1646 1647config NFSD 1648 tristate "NFS server support" 1649 depends on INET 1650 select LOCKD 1651 select SUNRPC 1652 select EXPORTFS 1653 select NFS_ACL_SUPPORT if NFSD_V2_ACL 1654 help 1655 Choose Y here if you want to allow other computers to access 1656 files residing on this system using Sun's Network File System 1657 protocol. To compile the NFS server support as a module, 1658 choose M here: the module will be called nfsd. 1659 1660 You may choose to use a user-space NFS server instead, in which 1661 case you can choose N here. 1662 1663 To export local file systems using NFS, you also need to install 1664 user space programs which can be found in the Linux nfs-utils 1665 package, available from http://linux-nfs.org/. More detail about 1666 the Linux NFS server implementation is available via the 1667 exports(5) man page. 1668 1669 Below you can choose which versions of the NFS protocol are 1670 available to clients mounting the NFS server on this system. 1671 Support for NFS version 2 (RFC 1094) is always available when 1672 CONFIG_NFSD is selected. 1673 1674 If unsure, say N. 1675 1676config NFSD_V2_ACL 1677 bool 1678 depends on NFSD 1679 1680config NFSD_V3 1681 bool "NFS server support for NFS version 3" 1682 depends on NFSD 1683 help 1684 This option enables support in your system's NFS server for 1685 version 3 of the NFS protocol (RFC 1813). 1686 1687 If unsure, say Y. 1688 1689config NFSD_V3_ACL 1690 bool "NFS server support for the NFSv3 ACL protocol extension" 1691 depends on NFSD_V3 1692 select NFSD_V2_ACL 1693 help 1694 Solaris NFS servers support an auxiliary NFSv3 ACL protocol that 1695 never became an official part of the NFS version 3 protocol. 1696 This protocol extension allows applications on NFS clients to 1697 manipulate POSIX Access Control Lists on files residing on NFS 1698 servers. NFS servers enforce POSIX ACLs on local files whether 1699 this protocol is available or not. 1700 1701 This option enables support in your system's NFS server for the 1702 NFSv3 ACL protocol extension allowing NFS clients to manipulate 1703 POSIX ACLs on files exported by your system's NFS server. NFS 1704 clients which support the Solaris NFSv3 ACL protocol can then 1705 access and modify ACLs on your NFS server. 1706 1707 To store ACLs on your NFS server, you also need to enable ACL- 1708 related CONFIG options for your local file systems of choice. 1709 1710 If unsure, say N. 1711 1712config NFSD_V4 1713 bool "NFS server support for NFS version 4 (EXPERIMENTAL)" 1714 depends on NFSD && PROC_FS && EXPERIMENTAL 1715 select NFSD_V3 1716 select FS_POSIX_ACL 1717 select RPCSEC_GSS_KRB5 1718 help 1719 This option enables support in your system's NFS server for 1720 version 4 of the NFS protocol (RFC 3530). 1721 1722 To export files using NFSv4, you need to install additional user 1723 space programs which can be found in the Linux nfs-utils package, 1724 available from http://linux-nfs.org/. 1725 1726 If unsure, say N. 1727 1728config LOCKD 1729 tristate 1730 1731config LOCKD_V4 1732 bool 1733 depends on NFSD_V3 || NFS_V3 1734 default y 1735 1736config EXPORTFS 1737 tristate 1738 1739config NFS_ACL_SUPPORT 1740 tristate 1741 select FS_POSIX_ACL 1742 1743config NFS_COMMON 1744 bool 1745 depends on NFSD || NFS_FS 1746 default y 1747 1748config SUNRPC 1749 tristate 1750 1751config SUNRPC_GSS 1752 tristate 1753 1754config SUNRPC_XPRT_RDMA 1755 tristate 1756 depends on SUNRPC && INFINIBAND && EXPERIMENTAL 1757 default SUNRPC && INFINIBAND 1758 help 1759 This option enables an RPC client transport capability that 1760 allows the NFS client to mount servers via an RDMA-enabled 1761 transport. 1762 1763 To compile RPC client RDMA transport support as a module, 1764 choose M here: the module will be called xprtrdma. 1765 1766 If unsure, say N. 1767 1768config RPCSEC_GSS_KRB5 1769 tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)" 1770 depends on SUNRPC && EXPERIMENTAL 1771 select SUNRPC_GSS 1772 select CRYPTO 1773 select CRYPTO_MD5 1774 select CRYPTO_DES 1775 select CRYPTO_CBC 1776 help 1777 Choose Y here to enable Secure RPC using the Kerberos version 5 1778 GSS-API mechanism (RFC 1964). 1779 1780 Secure RPC calls with Kerberos require an auxiliary user-space 1781 daemon which may be found in the Linux nfs-utils package 1782 available from http://linux-nfs.org/. In addition, user-space 1783 Kerberos support should be installed. 1784 1785 If unsure, say N. 1786 1787config RPCSEC_GSS_SPKM3 1788 tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)" 1789 depends on SUNRPC && EXPERIMENTAL 1790 select SUNRPC_GSS 1791 select CRYPTO 1792 select CRYPTO_MD5 1793 select CRYPTO_DES 1794 select CRYPTO_CAST5 1795 select CRYPTO_CBC 1796 help 1797 Choose Y here to enable Secure RPC using the SPKM3 public key 1798 GSS-API mechansim (RFC 2025). 1799 1800 Secure RPC calls with SPKM3 require an auxiliary userspace 1801 daemon which may be found in the Linux nfs-utils package 1802 available from http://linux-nfs.org/. 1803 1804 If unsure, say N. 1805 1806config SMB_FS 1807 tristate "SMB file system support (OBSOLETE, please use CIFS)" 1808 depends on INET 1809 select NLS 1810 help 1811 SMB (Server Message Block) is the protocol Windows for Workgroups 1812 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share 1813 files and printers over local networks. Saying Y here allows you to 1814 mount their file systems (often called "shares" in this context) and 1815 access them just like any other Unix directory. Currently, this 1816 works only if the Windows machines use TCP/IP as the underlying 1817 transport protocol, and not NetBEUI. For details, read 1818 <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO, 1819 available from <http://www.tldp.org/docs.html#howto>. 1820 1821 Note: if you just want your box to act as an SMB *server* and make 1822 files and printing services available to Windows clients (which need 1823 to have a TCP/IP stack), you don't need to say Y here; you can use 1824 the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>) 1825 for that. 1826 1827 General information about how to connect Linux, Windows machines and 1828 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>. 1829 1830 To compile the SMB support as a module, choose M here: 1831 the module will be called smbfs. Most people say N, however. 1832 1833config SMB_NLS_DEFAULT 1834 bool "Use a default NLS" 1835 depends on SMB_FS 1836 help 1837 Enabling this will make smbfs use nls translations by default. You 1838 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls 1839 settings and you need to give the default nls for the SMB server as 1840 CONFIG_SMB_NLS_REMOTE. 1841 1842 The nls settings can be changed at mount time, if your smbmount 1843 supports that, using the codepage and iocharset parameters. 1844 1845 smbmount from samba 2.2.0 or later supports this. 1846 1847config SMB_NLS_REMOTE 1848 string "Default Remote NLS Option" 1849 depends on SMB_NLS_DEFAULT 1850 default "cp437" 1851 help 1852 This setting allows you to specify a default value for which 1853 codepage the server uses. If this field is left blank no 1854 translations will be done by default. The local codepage/charset 1855 default to CONFIG_NLS_DEFAULT. 1856 1857 The nls settings can be changed at mount time, if your smbmount 1858 supports that, using the codepage and iocharset parameters. 1859 1860 smbmount from samba 2.2.0 or later supports this. 1861 1862config CIFS 1863 tristate "CIFS support (advanced network filesystem, SMBFS successor)" 1864 depends on INET 1865 select NLS 1866 help 1867 This is the client VFS module for the Common Internet File System 1868 (CIFS) protocol which is the successor to the Server Message Block 1869 (SMB) protocol, the native file sharing mechanism for most early 1870 PC operating systems. The CIFS protocol is fully supported by 1871 file servers such as Windows 2000 (including Windows 2003, NT 4 1872 and Windows XP) as well by Samba (which provides excellent CIFS 1873 server support for Linux and many other operating systems). Limited 1874 support for OS/2 and Windows ME and similar servers is provided as 1875 well. 1876 1877 The cifs module provides an advanced network file system 1878 client for mounting to CIFS compliant servers. It includes 1879 support for DFS (hierarchical name space), secure per-user 1880 session establishment via Kerberos or NTLM or NTLMv2, 1881 safe distributed caching (oplock), optional packet 1882 signing, Unicode and other internationalization improvements. 1883 If you need to mount to Samba or Windows from this machine, say Y. 1884 1885config CIFS_STATS 1886 bool "CIFS statistics" 1887 depends on CIFS 1888 help 1889 Enabling this option will cause statistics for each server share 1890 mounted by the cifs client to be displayed in /proc/fs/cifs/Stats 1891 1892config CIFS_STATS2 1893 bool "Extended statistics" 1894 depends on CIFS_STATS 1895 help 1896 Enabling this option will allow more detailed statistics on SMB 1897 request timing to be displayed in /proc/fs/cifs/DebugData and also 1898 allow optional logging of slow responses to dmesg (depending on the 1899 value of /proc/fs/cifs/cifsFYI, see fs/cifs/README for more details). 1900 These additional statistics may have a minor effect on performance 1901 and memory utilization. 1902 1903 Unless you are a developer or are doing network performance analysis 1904 or tuning, say N. 1905 1906config CIFS_WEAK_PW_HASH 1907 bool "Support legacy servers which use weaker LANMAN security" 1908 depends on CIFS 1909 help 1910 Modern CIFS servers including Samba and most Windows versions 1911 (since 1997) support stronger NTLM (and even NTLMv2 and Kerberos) 1912 security mechanisms. These hash the password more securely 1913 than the mechanisms used in the older LANMAN version of the 1914 SMB protocol but LANMAN based authentication is needed to 1915 establish sessions with some old SMB servers. 1916 1917 Enabling this option allows the cifs module to mount to older 1918 LANMAN based servers such as OS/2 and Windows 95, but such 1919 mounts may be less secure than mounts using NTLM or more recent 1920 security mechanisms if you are on a public network. Unless you 1921 have a need to access old SMB servers (and are on a private 1922 network) you probably want to say N. Even if this support 1923 is enabled in the kernel build, LANMAN authentication will not be 1924 used automatically. At runtime LANMAN mounts are disabled but 1925 can be set to required (or optional) either in 1926 /proc/fs/cifs (see fs/cifs/README for more detail) or via an 1927 option on the mount command. This support is disabled by 1928 default in order to reduce the possibility of a downgrade 1929 attack. 1930 1931 If unsure, say N. 1932 1933config CIFS_UPCALL 1934 bool "Kerberos/SPNEGO advanced session setup" 1935 depends on CIFS && KEYS 1936 help 1937 Enables an upcall mechanism for CIFS which accesses 1938 userspace helper utilities to provide SPNEGO packaged (RFC 4178) 1939 Kerberos tickets which are needed to mount to certain secure servers 1940 (for which more secure Kerberos authentication is required). If 1941 unsure, say N. 1942 1943config CIFS_XATTR 1944 bool "CIFS extended attributes" 1945 depends on CIFS 1946 help 1947 Extended attributes are name:value pairs associated with inodes by 1948 the kernel or by users (see the attr(5) manual page, or visit 1949 <http://acl.bestbits.at/> for details). CIFS maps the name of 1950 extended attributes beginning with the user namespace prefix 1951 to SMB/CIFS EAs. EAs are stored on Windows servers without the 1952 user namespace prefix, but their names are seen by Linux cifs clients 1953 prefaced by the user namespace prefix. The system namespace 1954 (used by some filesystems to store ACLs) is not supported at 1955 this time. 1956 1957 If unsure, say N. 1958 1959config CIFS_POSIX 1960 bool "CIFS POSIX Extensions" 1961 depends on CIFS_XATTR 1962 help 1963 Enabling this option will cause the cifs client to attempt to 1964 negotiate a newer dialect with servers, such as Samba 3.0.5 1965 or later, that optionally can handle more POSIX like (rather 1966 than Windows like) file behavior. It also enables 1967 support for POSIX ACLs (getfacl and setfacl) to servers 1968 (such as Samba 3.10 and later) which can negotiate 1969 CIFS POSIX ACL support. If unsure, say N. 1970 1971config CIFS_DEBUG2 1972 bool "Enable additional CIFS debugging routines" 1973 depends on CIFS 1974 help 1975 Enabling this option adds a few more debugging routines 1976 to the cifs code which slightly increases the size of 1977 the cifs module and can cause additional logging of debug 1978 messages in some error paths, slowing performance. This 1979 option can be turned off unless you are debugging 1980 cifs problems. If unsure, say N. 1981 1982config CIFS_EXPERIMENTAL 1983 bool "CIFS Experimental Features (EXPERIMENTAL)" 1984 depends on CIFS && EXPERIMENTAL 1985 help 1986 Enables cifs features under testing. These features are 1987 experimental and currently include DFS support and directory 1988 change notification ie fcntl(F_DNOTIFY), as well as the upcall 1989 mechanism which will be used for Kerberos session negotiation 1990 and uid remapping. Some of these features also may depend on 1991 setting a value of 1 to the pseudo-file /proc/fs/cifs/Experimental 1992 (which is disabled by default). See the file fs/cifs/README 1993 for more details. If unsure, say N. 1994 1995config CIFS_DFS_UPCALL 1996 bool "DFS feature support (EXPERIMENTAL)" 1997 depends on CIFS_EXPERIMENTAL 1998 depends on KEYS 1999 help 2000 Enables an upcall mechanism for CIFS which contacts userspace
2001 helper utilities to provide server name resolution (host names to 2002 IP addresses) which is needed for implicit mounts of DFS junction 2003 points. If unsure, say N. 2004 2005config NCP_FS 2006 tristate "NCP file system support (to mount NetWare volumes)" 2007 depends on IPX!=n || INET 2008 help 2009 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is 2010 used by Novell NetWare clients to talk to file servers. It is to 2011 IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you 2012 to mount NetWare file server volumes and to access them just like 2013 any other Unix directory. For details, please read the file 2014 <file:Documentation/filesystems/ncpfs.txt> in the kernel source and 2015 the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>. 2016 2017 You do not have to say Y here if you want your Linux box to act as a 2018 file *server* for Novell NetWare clients. 2019 2020 General information about how to connect Linux, Windows machines and 2021 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>. 2022 2023 To compile this as a module, choose M here: the module will be called 2024 ncpfs. Say N unless you are connected to a Novell network. 2025 2026source "fs/ncpfs/Kconfig" 2027 2028config CODA_FS 2029 tristate "Coda file system support (advanced network fs)" 2030 depends on INET 2031 help 2032 Coda is an advanced network file system, similar to NFS in that it 2033 enables you to mount file systems of a remote server and access them 2034 with regular Unix commands as if they were sitting on your hard 2035 disk. Coda has several advantages over NFS: support for 2036 disconnected operation (e.g. for laptops), read/write server 2037 replication, security model for authentication and encryption, 2038 persistent client caches and write back caching. 2039 2040 If you say Y here, your Linux box will be able to act as a Coda 2041 *client*. You will need user level code as well, both for the 2042 client and server. Servers are currently user level, i.e. they need 2043 no kernel support. Please read 2044 <file:Documentation/filesystems/coda.txt> and check out the Coda 2045 home page <http://www.coda.cs.cmu.edu/>. 2046 2047 To compile the coda client support as a module, choose M here: the 2048 module will be called coda. 2049 2050config AFS_FS 2051 tristate "Andrew File System support (AFS) (EXPERIMENTAL)" 2052 depends on INET && EXPERIMENTAL 2053 select AF_RXRPC 2054 help 2055 If you say Y here, you will get an experimental Andrew File System 2056 driver. It currently only supports unsecured read-only AFS access. 2057 2058 See <file:Documentation/filesystems/afs.txt> for more information. 2059 2060 If unsure, say N. 2061 2062config AFS_DEBUG 2063 bool "AFS dynamic debugging" 2064 depends on AFS_FS 2065 help 2066 Say Y here to make runtime controllable debugging messages appear. 2067 2068 See <file:Documentation/filesystems/afs.txt> for more information. 2069 2070 If unsure, say N. 2071 2072config 9P_FS 2073 tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)" 2074 depends on INET && NET_9P && EXPERIMENTAL 2075 help 2076 If you say Y here, you will get experimental support for 2077 Plan 9 resource sharing via the 9P2000 protocol. 2078 2079 See <http://v9fs.sf.net> for more information. 2080 2081 If unsure, say N. 2082 2083endif # NETWORK_FILESYSTEMS 2084 2085if BLOCK 2086menu "Partition Types" 2087 2088source "fs/partitions/Kconfig" 2089 2090endmenu 2091endif 2092 2093source "fs/nls/Kconfig" 2094source "fs/dlm/Kconfig" 2095 2096endmenu 2097