ia64/xen-unstable

view linux-2.6-xen-sparse/fs/Kconfig @ 14321:f421ccd1141f

Added section on references vs UUIDs.

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