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