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