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