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