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