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