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