ia64/linux-2.6.18-xen.hg

view fs/Kconfig @ 452:c7ed6fe5dca0

kexec: dont initialise regions in reserve_memory()

There is no need to initialise efi_memmap_res and boot_param_res in
reserve_memory() for the initial xen domain as it is done in
machine_kexec_setup_resources() using values from the kexec hypercall.

Signed-off-by: Simon Horman <horms@verge.net.au>
author Keir Fraser <keir.fraser@citrix.com>
date Thu Feb 28 10:55:18 2008 +0000 (2008-02-28)
parents 21a40e77044b
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 PROC_IOMEM_MACHINE
830 bool
831 depends on PROC_FS && EXPERIMENTAL && KEXEC && XEN && IA64
832 default y
834 config SYSFS
835 bool "sysfs file system support" if EMBEDDED
836 default y
837 help
838 The sysfs filesystem is a virtual filesystem that the kernel uses to
839 export internal kernel objects, their attributes, and their
840 relationships to one another.
842 Users can use sysfs to ascertain useful information about the running
843 kernel, such as the devices the kernel has discovered on each bus and
844 which driver each is bound to. sysfs can also be used to tune devices
845 and other kernel subsystems.
847 Some system agents rely on the information in sysfs to operate.
848 /sbin/hotplug uses device and object attributes in sysfs to assist in
849 delegating policy decisions, like persistantly naming devices.
851 sysfs is currently used by the block subsystem to mount the root
852 partition. If sysfs is disabled you must specify the boot device on
853 the kernel boot command line via its major and minor numbers. For
854 example, "root=03:01" for /dev/hda1.
856 Designers of embedded systems may wish to say N here to conserve space.
858 config TMPFS
859 bool "Virtual memory file system support (former shm fs)"
860 help
861 Tmpfs is a file system which keeps all files in virtual memory.
863 Everything in tmpfs is temporary in the sense that no files will be
864 created on your hard drive. The files live in memory and swap
865 space. If you unmount a tmpfs instance, everything stored therein is
866 lost.
868 See <file:Documentation/filesystems/tmpfs.txt> for details.
870 config HUGETLBFS
871 bool "HugeTLB file system support"
872 depends X86 || IA64 || PPC64 || SPARC64 || SUPERH || BROKEN
873 depends on !XEN
874 help
875 hugetlbfs is a filesystem backing for HugeTLB pages, based on
876 ramfs. For architectures that support it, say Y here and read
877 <file:Documentation/vm/hugetlbpage.txt> for details.
879 If unsure, say N.
881 config HUGETLB_PAGE
882 def_bool HUGETLBFS
884 config RAMFS
885 bool
886 default y
887 ---help---
888 Ramfs is a file system which keeps all files in RAM. It allows
889 read and write access.
891 It is more of an programming example than a useable file system. If
892 you need a file system which lives in RAM with limit checking use
893 tmpfs.
895 To compile this as a module, choose M here: the module will be called
896 ramfs.
898 config CONFIGFS_FS
899 tristate "Userspace-driven configuration filesystem (EXPERIMENTAL)"
900 depends on SYSFS && EXPERIMENTAL
901 help
902 configfs is a ram-based filesystem that provides the converse
903 of sysfs's functionality. Where sysfs is a filesystem-based
904 view of kernel objects, configfs is a filesystem-based manager
905 of kernel objects, or config_items.
907 Both sysfs and configfs can and should exist together on the
908 same system. One is not a replacement for the other.
910 endmenu
912 menu "Miscellaneous filesystems"
914 config ADFS_FS
915 tristate "ADFS file system support (EXPERIMENTAL)"
916 depends on EXPERIMENTAL
917 help
918 The Acorn Disc Filing System is the standard file system of the
919 RiscOS operating system which runs on Acorn's ARM-based Risc PC
920 systems and the Acorn Archimedes range of machines. If you say Y
921 here, Linux will be able to read from ADFS partitions on hard drives
922 and from ADFS-formatted floppy discs. If you also want to be able to
923 write to those devices, say Y to "ADFS write support" below.
925 The ADFS partition should be the first partition (i.e.,
926 /dev/[hs]d?1) on each of your drives. Please read the file
927 <file:Documentation/filesystems/adfs.txt> for further details.
929 To compile this code as a module, choose M here: the module will be
930 called adfs.
932 If unsure, say N.
934 config ADFS_FS_RW
935 bool "ADFS write support (DANGEROUS)"
936 depends on ADFS_FS
937 help
938 If you say Y here, you will be able to write to ADFS partitions on
939 hard drives and ADFS-formatted floppy disks. This is experimental
940 codes, so if you're unsure, say N.
942 config AFFS_FS
943 tristate "Amiga FFS file system support (EXPERIMENTAL)"
944 depends on EXPERIMENTAL
945 help
946 The Fast File System (FFS) is the common file system used on hard
947 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
948 if you want to be able to read and write files from and to an Amiga
949 FFS partition on your hard drive. Amiga floppies however cannot be
950 read with this driver due to an incompatibility of the floppy
951 controller used in an Amiga and the standard floppy controller in
952 PCs and workstations. Read <file:Documentation/filesystems/affs.txt>
953 and <file:fs/affs/Changes>.
955 With this driver you can also mount disk files used by Bernd
956 Schmidt's Un*X Amiga Emulator
957 (<http://www.freiburg.linux.de/~uae/>).
958 If you want to do this, you will also need to say Y or M to "Loop
959 device support", above.
961 To compile this file system support as a module, choose M here: the
962 module will be called affs. If unsure, say N.
964 config HFS_FS
965 tristate "Apple Macintosh file system support (EXPERIMENTAL)"
966 depends on EXPERIMENTAL
967 select NLS
968 help
969 If you say Y here, you will be able to mount Macintosh-formatted
970 floppy disks and hard drive partitions with full read-write access.
971 Please read <file:fs/hfs/HFS.txt> to learn about the available mount
972 options.
974 To compile this file system support as a module, choose M here: the
975 module will be called hfs.
977 config HFSPLUS_FS
978 tristate "Apple Extended HFS file system support"
979 select NLS
980 select NLS_UTF8
981 help
982 If you say Y here, you will be able to mount extended format
983 Macintosh-formatted hard drive partitions with full read-write access.
985 This file system is often called HFS+ and was introduced with
986 MacOS 8. It includes all Mac specific filesystem data such as
987 data forks and creator codes, but it also has several UNIX
988 style features such as file ownership and permissions.
990 config BEFS_FS
991 tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)"
992 depends on EXPERIMENTAL
993 select NLS
994 help
995 The BeOS File System (BeFS) is the native file system of Be, Inc's
996 BeOS. Notable features include support for arbitrary attributes
997 on files and directories, and database-like indeces on selected
998 attributes. (Also note that this driver doesn't make those features
999 available at this time). It is a 64 bit filesystem, so it supports
1000 extremly large volumes and files.
1002 If you use this filesystem, you should also say Y to at least one
1003 of the NLS (native language support) options below.
1005 If you don't know what this is about, say N.
1007 To compile this as a module, choose M here: the module will be
1008 called befs.
1010 config BEFS_DEBUG
1011 bool "Debug BeFS"
1012 depends on BEFS_FS
1013 help
1014 If you say Y here, you can use the 'debug' mount option to enable
1015 debugging output from the driver.
1017 config BFS_FS
1018 tristate "BFS file system support (EXPERIMENTAL)"
1019 depends on EXPERIMENTAL
1020 help
1021 Boot File System (BFS) is a file system used under SCO UnixWare to
1022 allow the bootloader access to the kernel image and other important
1023 files during the boot process. It is usually mounted under /stand
1024 and corresponds to the slice marked as "STAND" in the UnixWare
1025 partition. You should say Y if you want to read or write the files
1026 on your /stand slice from within Linux. You then also need to say Y
1027 to "UnixWare slices support", below. More information about the BFS
1028 file system is contained in the file
1029 <file:Documentation/filesystems/bfs.txt>.
1031 If you don't know what this is about, say N.
1033 To compile this as a module, choose M here: the module will be called
1034 bfs. Note that the file system of your root partition (the one
1035 containing the directory /) cannot be compiled as a module.
1039 config EFS_FS
1040 tristate "EFS file system support (read only) (EXPERIMENTAL)"
1041 depends on EXPERIMENTAL
1042 help
1043 EFS is an older file system used for non-ISO9660 CD-ROMs and hard
1044 disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
1045 uses the XFS file system for hard disk partitions however).
1047 This implementation only offers read-only access. If you don't know
1048 what all this is about, it's safe to say N. For more information
1049 about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
1051 To compile the EFS file system support as a module, choose M here: the
1052 module will be called efs.
1054 config JFFS_FS
1055 tristate "Journalling Flash File System (JFFS) support"
1056 depends on MTD
1057 help
1058 JFFS is the Journaling Flash File System developed by Axis
1059 Communications in Sweden, aimed at providing a crash/powerdown-safe
1060 file system for disk-less embedded devices. Further information is
1061 available at (<http://developer.axis.com/software/jffs/>).
1063 config JFFS_FS_VERBOSE
1064 int "JFFS debugging verbosity (0 = quiet, 3 = noisy)"
1065 depends on JFFS_FS
1066 default "0"
1067 help
1068 Determines the verbosity level of the JFFS debugging messages.
1070 config JFFS_PROC_FS
1071 bool "JFFS stats available in /proc filesystem"
1072 depends on JFFS_FS && PROC_FS
1073 help
1074 Enabling this option will cause statistics from mounted JFFS file systems
1075 to be made available to the user in the /proc/fs/jffs/ directory.
1077 config JFFS2_FS
1078 tristate "Journalling Flash File System v2 (JFFS2) support"
1079 select CRC32
1080 depends on MTD
1081 help
1082 JFFS2 is the second generation of the Journalling Flash File System
1083 for use on diskless embedded devices. It provides improved wear
1084 levelling, compression and support for hard links. You cannot use
1085 this on normal block devices, only on 'MTD' devices.
1087 Further information on the design and implementation of JFFS2 is
1088 available at <http://sources.redhat.com/jffs2/>.
1090 config JFFS2_FS_DEBUG
1091 int "JFFS2 debugging verbosity (0 = quiet, 2 = noisy)"
1092 depends on JFFS2_FS
1093 default "0"
1094 help
1095 This controls the amount of debugging messages produced by the JFFS2
1096 code. Set it to zero for use in production systems. For evaluation,
1097 testing and debugging, it's advisable to set it to one. This will
1098 enable a few assertions and will print debugging messages at the
1099 KERN_DEBUG loglevel, where they won't normally be visible. Level 2
1100 is unlikely to be useful - it enables extra debugging in certain
1101 areas which at one point needed debugging, but when the bugs were
1102 located and fixed, the detailed messages were relegated to level 2.
1104 If reporting bugs, please try to have available a full dump of the
1105 messages at debug level 1 while the misbehaviour was occurring.
1107 config JFFS2_FS_WRITEBUFFER
1108 bool "JFFS2 write-buffering support"
1109 depends on JFFS2_FS
1110 default y
1111 help
1112 This enables the write-buffering support in JFFS2.
1114 This functionality is required to support JFFS2 on the following
1115 types of flash devices:
1116 - NAND flash
1117 - NOR flash with transparent ECC
1118 - DataFlash
1120 config JFFS2_SUMMARY
1121 bool "JFFS2 summary support (EXPERIMENTAL)"
1122 depends on JFFS2_FS && EXPERIMENTAL
1123 default n
1124 help
1125 This feature makes it possible to use summary information
1126 for faster filesystem mount.
1128 The summary information can be inserted into a filesystem image
1129 by the utility 'sumtool'.
1131 If unsure, say 'N'.
1133 config JFFS2_FS_XATTR
1134 bool "JFFS2 XATTR support (EXPERIMENTAL)"
1135 depends on JFFS2_FS && EXPERIMENTAL
1136 default n
1137 help
1138 Extended attributes are name:value pairs associated with inodes by
1139 the kernel or by users (see the attr(5) manual page, or visit
1140 <http://acl.bestbits.at/> for details).
1142 If unsure, say N.
1144 config JFFS2_FS_POSIX_ACL
1145 bool "JFFS2 POSIX Access Control Lists"
1146 depends on JFFS2_FS_XATTR
1147 default y
1148 select FS_POSIX_ACL
1149 help
1150 Posix Access Control Lists (ACLs) support permissions for users and
1151 groups beyond the owner/group/world scheme.
1153 To learn more about Access Control Lists, visit the Posix ACLs for
1154 Linux website <http://acl.bestbits.at/>.
1156 If you don't know what Access Control Lists are, say N
1158 config JFFS2_FS_SECURITY
1159 bool "JFFS2 Security Labels"
1160 depends on JFFS2_FS_XATTR
1161 default y
1162 help
1163 Security labels support alternative access control models
1164 implemented by security modules like SELinux. This option
1165 enables an extended attribute handler for file security
1166 labels in the jffs2 filesystem.
1168 If you are not using a security module that requires using
1169 extended attributes for file security labels, say N.
1171 config JFFS2_COMPRESSION_OPTIONS
1172 bool "Advanced compression options for JFFS2"
1173 depends on JFFS2_FS
1174 default n
1175 help
1176 Enabling this option allows you to explicitly choose which
1177 compression modules, if any, are enabled in JFFS2. Removing
1178 compressors and mean you cannot read existing file systems,
1179 and enabling experimental compressors can mean that you
1180 write a file system which cannot be read by a standard kernel.
1182 If unsure, you should _definitely_ say 'N'.
1184 config JFFS2_ZLIB
1185 bool "JFFS2 ZLIB compression support" if JFFS2_COMPRESSION_OPTIONS
1186 select ZLIB_INFLATE
1187 select ZLIB_DEFLATE
1188 depends on JFFS2_FS
1189 default y
1190 help
1191 Zlib is designed to be a free, general-purpose, legally unencumbered,
1192 lossless data-compression library for use on virtually any computer
1193 hardware and operating system. See <http://www.gzip.org/zlib/> for
1194 further information.
1196 Say 'Y' if unsure.
1198 config JFFS2_RTIME
1199 bool "JFFS2 RTIME compression support" if JFFS2_COMPRESSION_OPTIONS
1200 depends on JFFS2_FS
1201 default y
1202 help
1203 Rtime does manage to recompress already-compressed data. Say 'Y' if unsure.
1205 config JFFS2_RUBIN
1206 bool "JFFS2 RUBIN compression support" if JFFS2_COMPRESSION_OPTIONS
1207 depends on JFFS2_FS
1208 default n
1209 help
1210 RUBINMIPS and DYNRUBIN compressors. Say 'N' if unsure.
1212 choice
1213 prompt "JFFS2 default compression mode" if JFFS2_COMPRESSION_OPTIONS
1214 default JFFS2_CMODE_PRIORITY
1215 depends on JFFS2_FS
1216 help
1217 You can set here the default compression mode of JFFS2 from
1218 the available compression modes. Don't touch if unsure.
1220 config JFFS2_CMODE_NONE
1221 bool "no compression"
1222 help
1223 Uses no compression.
1225 config JFFS2_CMODE_PRIORITY
1226 bool "priority"
1227 help
1228 Tries the compressors in a predefinied order and chooses the first
1229 successful one.
1231 config JFFS2_CMODE_SIZE
1232 bool "size (EXPERIMENTAL)"
1233 help
1234 Tries all compressors and chooses the one which has the smallest
1235 result.
1237 endchoice
1239 config CRAMFS
1240 tristate "Compressed ROM file system support (cramfs)"
1241 select ZLIB_INFLATE
1242 help
1243 Saying Y here includes support for CramFs (Compressed ROM File
1244 System). CramFs is designed to be a simple, small, and compressed
1245 file system for ROM based embedded systems. CramFs is read-only,
1246 limited to 256MB file systems (with 16MB files), and doesn't support
1247 16/32 bits uid/gid, hard links and timestamps.
1249 See <file:Documentation/filesystems/cramfs.txt> and
1250 <file:fs/cramfs/README> for further information.
1252 To compile this as a module, choose M here: the module will be called
1253 cramfs. Note that the root file system (the one containing the
1254 directory /) cannot be compiled as a module.
1256 If unsure, say N.
1258 config VXFS_FS
1259 tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
1260 help
1261 FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
1262 file system format. VERITAS VxFS(TM) is the standard file system
1263 of SCO UnixWare (and possibly others) and optionally available
1264 for Sunsoft Solaris, HP-UX and many other operating systems.
1265 Currently only readonly access is supported.
1267 NOTE: the file system type as used by mount(1), mount(2) and
1268 fstab(5) is 'vxfs' as it describes the file system format, not
1269 the actual driver.
1271 To compile this as a module, choose M here: the module will be
1272 called freevxfs. If unsure, say N.
1275 config HPFS_FS
1276 tristate "OS/2 HPFS file system support"
1277 help
1278 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
1279 is the file system used for organizing files on OS/2 hard disk
1280 partitions. Say Y if you want to be able to read files from and
1281 write files to an OS/2 HPFS partition on your hard drive. OS/2
1282 floppies however are in regular MSDOS format, so you don't need this
1283 option in order to be able to read them. Read
1284 <file:Documentation/filesystems/hpfs.txt>.
1286 To compile this file system support as a module, choose M here: the
1287 module will be called hpfs. If unsure, say N.
1291 config QNX4FS_FS
1292 tristate "QNX4 file system support (read only)"
1293 help
1294 This is the file system used by the real-time operating systems
1295 QNX 4 and QNX 6 (the latter is also called QNX RTP).
1296 Further information is available at <http://www.qnx.com/>.
1297 Say Y if you intend to mount QNX hard disks or floppies.
1298 Unless you say Y to "QNX4FS read-write support" below, you will
1299 only be able to read these file systems.
1301 To compile this file system support as a module, choose M here: the
1302 module will be called qnx4.
1304 If you don't know whether you need it, then you don't need it:
1305 answer N.
1307 config QNX4FS_RW
1308 bool "QNX4FS write support (DANGEROUS)"
1309 depends on QNX4FS_FS && EXPERIMENTAL && BROKEN
1310 help
1311 Say Y if you want to test write support for QNX4 file systems.
1313 It's currently broken, so for now:
1314 answer N.
1318 config SYSV_FS
1319 tristate "System V/Xenix/V7/Coherent file system support"
1320 help
1321 SCO, Xenix and Coherent are commercial Unix systems for Intel
1322 machines, and Version 7 was used on the DEC PDP-11. Saying Y
1323 here would allow you to read from their floppies and hard disk
1324 partitions.
1326 If you have floppies or hard disk partitions like that, it is likely
1327 that they contain binaries from those other Unix systems; in order
1328 to run these binaries, you will want to install linux-abi which is a
1329 a set of kernel modules that lets you run SCO, Xenix, Wyse,
1330 UnixWare, Dell Unix and System V programs under Linux. It is
1331 available via FTP (user: ftp) from
1332 <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
1333 NOTE: that will work only for binaries from Intel-based systems;
1334 PDP ones will have to wait until somebody ports Linux to -11 ;-)
1336 If you only intend to mount files from some other Unix over the
1337 network using NFS, you don't need the System V file system support
1338 (but you need NFS file system support obviously).
1340 Note that this option is generally not needed for floppies, since a
1341 good portable way to transport files and directories between unixes
1342 (and even other operating systems) is given by the tar program ("man
1343 tar" or preferably "info tar"). Note also that this option has
1344 nothing whatsoever to do with the option "System V IPC". Read about
1345 the System V file system in
1346 <file:Documentation/filesystems/sysv-fs.txt>.
1347 Saying Y here will enlarge your kernel by about 27 KB.
1349 To compile this as a module, choose M here: the module will be called
1350 sysv.
1352 If you haven't heard about all of this before, it's safe to say N.
1356 config UFS_FS
1357 tristate "UFS file system support (read only)"
1358 help
1359 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
1360 OpenBSD and NeXTstep) use a file system called UFS. Some System V
1361 Unixes can create and mount hard disk partitions and diskettes using
1362 this file system as well. Saying Y here will allow you to read from
1363 these partitions; if you also want to write to them, say Y to the
1364 experimental "UFS file system write support", below. Please read the
1365 file <file:Documentation/filesystems/ufs.txt> for more information.
1367 The recently released UFS2 variant (used in FreeBSD 5.x) is
1368 READ-ONLY supported.
1370 If you only intend to mount files from some other Unix over the
1371 network using NFS, you don't need the UFS file system support (but
1372 you need NFS file system support obviously).
1374 Note that this option is generally not needed for floppies, since a
1375 good portable way to transport files and directories between unixes
1376 (and even other operating systems) is given by the tar program ("man
1377 tar" or preferably "info tar").
1379 When accessing NeXTstep files, you may need to convert them from the
1380 NeXT character set to the Latin1 character set; use the program
1381 recode ("info recode") for this purpose.
1383 To compile the UFS file system support as a module, choose M here: the
1384 module will be called ufs.
1386 If you haven't heard about all of this before, it's safe to say N.
1388 config UFS_FS_WRITE
1389 bool "UFS file system write support (DANGEROUS)"
1390 depends on UFS_FS && EXPERIMENTAL
1391 help
1392 Say Y here if you want to try writing to UFS partitions. This is
1393 experimental, so you should back up your UFS partitions beforehand.
1395 config UFS_DEBUG
1396 bool "UFS debugging"
1397 depends on UFS_FS
1398 help
1399 If you are experiencing any problems with the UFS filesystem, say
1400 Y here. This will result in _many_ additional debugging messages to be
1401 written to the system log.
1403 endmenu
1405 menu "Network File Systems"
1406 depends on NET
1408 config NFS_FS
1409 tristate "NFS file system support"
1410 depends on INET
1411 select LOCKD
1412 select SUNRPC
1413 select NFS_ACL_SUPPORT if NFS_V3_ACL
1414 help
1415 If you are connected to some other (usually local) Unix computer
1416 (using SLIP, PLIP, PPP or Ethernet) and want to mount files residing
1417 on that computer (the NFS server) using the Network File Sharing
1418 protocol, say Y. "Mounting files" means that the client can access
1419 the files with usual UNIX commands as if they were sitting on the
1420 client's hard disk. For this to work, the server must run the
1421 programs nfsd and mountd (but does not need to have NFS file system
1422 support enabled in its kernel). NFS is explained in the Network
1423 Administrator's Guide, available from
1424 <http://www.tldp.org/docs.html#guide>, on its man page: "man
1425 nfs", and in the NFS-HOWTO.
1427 A superior but less widely used alternative to NFS is provided by
1428 the Coda file system; see "Coda file system support" below.
1430 If you say Y here, you should have said Y to TCP/IP networking also.
1431 This option would enlarge your kernel by about 27 KB.
1433 To compile this file system support as a module, choose M here: the
1434 module will be called nfs.
1436 If you are configuring a diskless machine which will mount its root
1437 file system over NFS at boot time, say Y here and to "Kernel
1438 level IP autoconfiguration" above and to "Root file system on NFS"
1439 below. You cannot compile this driver as a module in this case.
1440 There are two packages designed for booting diskless machines over
1441 the net: netboot, available from
1442 <http://ftp1.sourceforge.net/netboot/>, and Etherboot,
1443 available from <http://ftp1.sourceforge.net/etherboot/>.
1445 If you don't know what all this is about, say N.
1447 config NFS_V3
1448 bool "Provide NFSv3 client support"
1449 depends on NFS_FS
1450 help
1451 Say Y here if you want your NFS client to be able to speak version
1452 3 of the NFS protocol.
1454 If unsure, say Y.
1456 config NFS_V3_ACL
1457 bool "Provide client support for the NFSv3 ACL protocol extension"
1458 depends on NFS_V3
1459 help
1460 Implement the NFSv3 ACL protocol extension for manipulating POSIX
1461 Access Control Lists. The server should also be compiled with
1462 the NFSv3 ACL protocol extension; see the CONFIG_NFSD_V3_ACL option.
1464 If unsure, say N.
1466 config NFS_V4
1467 bool "Provide NFSv4 client support (EXPERIMENTAL)"
1468 depends on NFS_FS && EXPERIMENTAL
1469 select RPCSEC_GSS_KRB5
1470 help
1471 Say Y here if you want your NFS client to be able to speak the newer
1472 version 4 of the NFS protocol.
1474 Note: Requires auxiliary userspace daemons which may be found on
1475 http://www.citi.umich.edu/projects/nfsv4/
1477 If unsure, say N.
1479 config NFS_DIRECTIO
1480 bool "Allow direct I/O on NFS files (EXPERIMENTAL)"
1481 depends on NFS_FS && EXPERIMENTAL
1482 help
1483 This option enables applications to perform uncached I/O on files
1484 in NFS file systems using the O_DIRECT open() flag. When O_DIRECT
1485 is set for a file, its data is not cached in the system's page
1486 cache. Data is moved to and from user-level application buffers
1487 directly. Unlike local disk-based file systems, NFS O_DIRECT has
1488 no alignment restrictions.
1490 Unless your program is designed to use O_DIRECT properly, you are
1491 much better off allowing the NFS client to manage data caching for
1492 you. Misusing O_DIRECT can cause poor server performance or network
1493 storms. This kernel build option defaults OFF to avoid exposing
1494 system administrators unwittingly to a potentially hazardous
1495 feature.
1497 For more details on NFS O_DIRECT, see fs/nfs/direct.c.
1499 If unsure, say N. This reduces the size of the NFS client, and
1500 causes open() to return EINVAL if a file residing in NFS is
1501 opened with the O_DIRECT flag.
1503 config NFSD
1504 tristate "NFS server support"
1505 depends on INET
1506 select LOCKD
1507 select SUNRPC
1508 select EXPORTFS
1509 select NFSD_V2_ACL if NFSD_V3_ACL
1510 select NFS_ACL_SUPPORT if NFSD_V2_ACL
1511 select NFSD_TCP if NFSD_V4
1512 select CRYPTO_MD5 if NFSD_V4
1513 select CRYPTO if NFSD_V4
1514 select FS_POSIX_ACL if NFSD_V4
1515 help
1516 If you want your Linux box to act as an NFS *server*, so that other
1517 computers on your local network which support NFS can access certain
1518 directories on your box transparently, you have two options: you can
1519 use the self-contained user space program nfsd, in which case you
1520 should say N here, or you can say Y and use the kernel based NFS
1521 server. The advantage of the kernel based solution is that it is
1522 faster.
1524 In either case, you will need support software; the respective
1525 locations are given in the file <file:Documentation/Changes> in the
1526 NFS section.
1528 If you say Y here, you will get support for version 2 of the NFS
1529 protocol (NFSv2). If you also want NFSv3, say Y to the next question
1530 as well.
1532 Please read the NFS-HOWTO, available from
1533 <http://www.tldp.org/docs.html#howto>.
1535 To compile the NFS server support as a module, choose M here: the
1536 module will be called nfsd. If unsure, say N.
1538 config NFSD_V2_ACL
1539 bool
1540 depends on NFSD
1542 config NFSD_V3
1543 bool "Provide NFSv3 server support"
1544 depends on NFSD
1545 help
1546 If you would like to include the NFSv3 server as well as the NFSv2
1547 server, say Y here. If unsure, say Y.
1549 config NFSD_V3_ACL
1550 bool "Provide server support for the NFSv3 ACL protocol extension"
1551 depends on NFSD_V3
1552 help
1553 Implement the NFSv3 ACL protocol extension for manipulating POSIX
1554 Access Control Lists on exported file systems. NFS clients should
1555 be compiled with the NFSv3 ACL protocol extension; see the
1556 CONFIG_NFS_V3_ACL option. If unsure, say N.
1558 config NFSD_V4
1559 bool "Provide NFSv4 server support (EXPERIMENTAL)"
1560 depends on NFSD_V3 && EXPERIMENTAL
1561 help
1562 If you would like to include the NFSv4 server as well as the NFSv2
1563 and NFSv3 servers, say Y here. This feature is experimental, and
1564 should only be used if you are interested in helping to test NFSv4.
1565 If unsure, say N.
1567 config NFSD_TCP
1568 bool "Provide NFS server over TCP support"
1569 depends on NFSD
1570 default y
1571 help
1572 If you want your NFS server to support TCP connections, say Y here.
1573 TCP connections usually perform better than the default UDP when
1574 the network is lossy or congested. If unsure, say Y.
1576 config ROOT_NFS
1577 bool "Root file system on NFS"
1578 depends on NFS_FS=y && IP_PNP
1579 help
1580 If you want your Linux box to mount its whole root file system (the
1581 one containing the directory /) from some other computer over the
1582 net via NFS (presumably because your box doesn't have a hard disk),
1583 say Y. Read <file:Documentation/nfsroot.txt> for details. It is
1584 likely that in this case, you also want to say Y to "Kernel level IP
1585 autoconfiguration" so that your box can discover its network address
1586 at boot time.
1588 Most people say N here.
1590 config LOCKD
1591 tristate
1593 config LOCKD_V4
1594 bool
1595 depends on NFSD_V3 || NFS_V3
1596 default y
1598 config EXPORTFS
1599 tristate
1601 config NFS_ACL_SUPPORT
1602 tristate
1603 select FS_POSIX_ACL
1605 config NFS_COMMON
1606 bool
1607 depends on NFSD || NFS_FS
1608 default y
1610 config SUNRPC
1611 tristate
1613 config SUNRPC_GSS
1614 tristate
1616 config RPCSEC_GSS_KRB5
1617 tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
1618 depends on SUNRPC && EXPERIMENTAL
1619 select SUNRPC_GSS
1620 select CRYPTO
1621 select CRYPTO_MD5
1622 select CRYPTO_DES
1623 help
1624 Provides for secure RPC calls by means of a gss-api
1625 mechanism based on Kerberos V5. This is required for
1626 NFSv4.
1628 Note: Requires an auxiliary userspace daemon which may be found on
1629 http://www.citi.umich.edu/projects/nfsv4/
1631 If unsure, say N.
1633 config RPCSEC_GSS_SPKM3
1634 tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
1635 depends on SUNRPC && EXPERIMENTAL
1636 select SUNRPC_GSS
1637 select CRYPTO
1638 select CRYPTO_MD5
1639 select CRYPTO_DES
1640 select CRYPTO_CAST5
1641 help
1642 Provides for secure RPC calls by means of a gss-api
1643 mechanism based on the SPKM3 public-key mechanism.
1645 Note: Requires an auxiliary userspace daemon which may be found on
1646 http://www.citi.umich.edu/projects/nfsv4/
1648 If unsure, say N.
1650 config SMB_FS
1651 tristate "SMB file system support (to mount Windows shares etc.)"
1652 depends on INET
1653 select NLS
1654 help
1655 SMB (Server Message Block) is the protocol Windows for Workgroups
1656 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
1657 files and printers over local networks. Saying Y here allows you to
1658 mount their file systems (often called "shares" in this context) and
1659 access them just like any other Unix directory. Currently, this
1660 works only if the Windows machines use TCP/IP as the underlying
1661 transport protocol, and not NetBEUI. For details, read
1662 <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
1663 available from <http://www.tldp.org/docs.html#howto>.
1665 Note: if you just want your box to act as an SMB *server* and make
1666 files and printing services available to Windows clients (which need
1667 to have a TCP/IP stack), you don't need to say Y here; you can use
1668 the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
1669 for that.
1671 General information about how to connect Linux, Windows machines and
1672 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1674 To compile the SMB support as a module, choose M here: the module will
1675 be called smbfs. Most people say N, however.
1677 config SMB_NLS_DEFAULT
1678 bool "Use a default NLS"
1679 depends on SMB_FS
1680 help
1681 Enabling this will make smbfs use nls translations by default. You
1682 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
1683 settings and you need to give the default nls for the SMB server as
1684 CONFIG_SMB_NLS_REMOTE.
1686 The nls settings can be changed at mount time, if your smbmount
1687 supports that, using the codepage and iocharset parameters.
1689 smbmount from samba 2.2.0 or later supports this.
1691 config SMB_NLS_REMOTE
1692 string "Default Remote NLS Option"
1693 depends on SMB_NLS_DEFAULT
1694 default "cp437"
1695 help
1696 This setting allows you to specify a default value for which
1697 codepage the server uses. If this field is left blank no
1698 translations will be done by default. The local codepage/charset
1699 default to CONFIG_NLS_DEFAULT.
1701 The nls settings can be changed at mount time, if your smbmount
1702 supports that, using the codepage and iocharset parameters.
1704 smbmount from samba 2.2.0 or later supports this.
1706 config CIFS
1707 tristate "CIFS support (advanced network filesystem for Samba, Window and other CIFS compliant servers)"
1708 depends on INET
1709 select NLS
1710 help
1711 This is the client VFS module for the Common Internet File System
1712 (CIFS) protocol which is the successor to the Server Message Block
1713 (SMB) protocol, the native file sharing mechanism for most early
1714 PC operating systems. The CIFS protocol is fully supported by
1715 file servers such as Windows 2000 (including Windows 2003, NT 4
1716 and Windows XP) as well by Samba (which provides excellent CIFS
1717 server support for Linux and many other operating systems). Limited
1718 support for Windows ME and similar servers is provided as well.
1719 You must use the smbfs client filesystem to access older SMB servers
1720 such as OS/2 and DOS.
1722 The intent of the cifs module is to provide an advanced
1723 network file system client for mounting to CIFS compliant servers,
1724 including support for dfs (hierarchical name space), secure per-user
1725 session establishment, safe distributed caching (oplock), optional
1726 packet signing, Unicode and other internationalization improvements,
1727 and optional Winbind (nsswitch) integration. You do not need to enable
1728 cifs if running only a (Samba) server. It is possible to enable both
1729 smbfs and cifs (e.g. if you are using CIFS for accessing Windows 2003
1730 and Samba 3 servers, and smbfs for accessing old servers). If you need
1731 to mount to Samba or Windows from this machine, say Y.
1733 config CIFS_STATS
1734 bool "CIFS statistics"
1735 depends on CIFS
1736 help
1737 Enabling this option will cause statistics for each server share
1738 mounted by the cifs client to be displayed in /proc/fs/cifs/Stats
1740 config CIFS_STATS2
1741 bool "Extended statistics"
1742 depends on CIFS_STATS
1743 help
1744 Enabling this option will allow more detailed statistics on SMB
1745 request timing to be displayed in /proc/fs/cifs/DebugData and also
1746 allow optional logging of slow responses to dmesg (depending on the
1747 value of /proc/fs/cifs/cifsFYI, see fs/cifs/README for more details).
1748 These additional statistics may have a minor effect on performance
1749 and memory utilization.
1751 Unless you are a developer or are doing network performance analysis
1752 or tuning, say N.
1754 config CIFS_WEAK_PW_HASH
1755 bool "Support legacy servers which use weaker LANMAN security"
1756 depends on CIFS
1757 help
1758 Modern CIFS servers including Samba and most Windows versions
1759 (since 1997) support stronger NTLM (and even NTLMv2 and Kerberos)
1760 security mechanisms. These hash the password more securely
1761 than the mechanisms used in the older LANMAN version of the
1762 SMB protocol needed to establish sessions with old SMB servers.
1764 Enabling this option allows the cifs module to mount to older
1765 LANMAN based servers such as OS/2 and Windows 95, but such
1766 mounts may be less secure than mounts using NTLM or more recent
1767 security mechanisms if you are on a public network. Unless you
1768 have a need to access old SMB servers (and are on a private
1769 network) you probably want to say N. Even if this support
1770 is enabled in the kernel build, they will not be used
1771 automatically. At runtime LANMAN mounts are disabled but
1772 can be set to required (or optional) either in
1773 /proc/fs/cifs (see fs/cifs/README for more detail) or via an
1774 option on the mount command. This support is disabled by
1775 default in order to reduce the possibility of a downgrade
1776 attack.
1778 If unsure, say N.
1780 config CIFS_XATTR
1781 bool "CIFS extended attributes"
1782 depends on CIFS
1783 help
1784 Extended attributes are name:value pairs associated with inodes by
1785 the kernel or by users (see the attr(5) manual page, or visit
1786 <http://acl.bestbits.at/> for details). CIFS maps the name of
1787 extended attributes beginning with the user namespace prefix
1788 to SMB/CIFS EAs. EAs are stored on Windows servers without the
1789 user namespace prefix, but their names are seen by Linux cifs clients
1790 prefaced by the user namespace prefix. The system namespace
1791 (used by some filesystems to store ACLs) is not supported at
1792 this time.
1794 If unsure, say N.
1796 config CIFS_POSIX
1797 bool "CIFS POSIX Extensions"
1798 depends on CIFS_XATTR
1799 help
1800 Enabling this option will cause the cifs client to attempt to
1801 negotiate a newer dialect with servers, such as Samba 3.0.5
1802 or later, that optionally can handle more POSIX like (rather
1803 than Windows like) file behavior. It also enables
1804 support for POSIX ACLs (getfacl and setfacl) to servers
1805 (such as Samba 3.10 and later) which can negotiate
1806 CIFS POSIX ACL support. If unsure, say N.
1808 config CIFS_DEBUG2
1809 bool "Enable additional CIFS debugging routines"
1810 depends on CIFS
1811 help
1812 Enabling this option adds a few more debugging routines
1813 to the cifs code which slightly increases the size of
1814 the cifs module and can cause additional logging of debug
1815 messages in some error paths, slowing performance. This
1816 option can be turned off unless you are debugging
1817 cifs problems. If unsure, say N.
1819 config CIFS_EXPERIMENTAL
1820 bool "CIFS Experimental Features (EXPERIMENTAL)"
1821 depends on CIFS && EXPERIMENTAL
1822 help
1823 Enables cifs features under testing. These features are
1824 experimental and currently include support for writepages
1825 (multipage writebehind performance improvements) and directory
1826 change notification ie fcntl(F_DNOTIFY) as well as some security
1827 improvements. Some also depend on setting at runtime the
1828 pseudo-file /proc/fs/cifs/Experimental (which is disabled by
1829 default). See the file fs/cifs/README for more details.
1831 If unsure, say N.
1833 config CIFS_UPCALL
1834 bool "Kerberos/SPNEGO advanced session setup (EXPERIMENTAL)"
1835 depends on CIFS_EXPERIMENTAL
1836 select CONNECTOR
1837 help
1838 Enables an upcall mechanism for CIFS which will be used to contact
1839 userspace helper utilities to provide SPNEGO packaged Kerberos
1840 tickets which are needed to mount to certain secure servers
1841 (for which more secure Kerberos authentication is required). If
1842 unsure, say N.
1844 config NCP_FS
1845 tristate "NCP file system support (to mount NetWare volumes)"
1846 depends on IPX!=n || INET
1847 help
1848 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
1849 used by Novell NetWare clients to talk to file servers. It is to
1850 IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
1851 to mount NetWare file server volumes and to access them just like
1852 any other Unix directory. For details, please read the file
1853 <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
1854 the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
1856 You do not have to say Y here if you want your Linux box to act as a
1857 file *server* for Novell NetWare clients.
1859 General information about how to connect Linux, Windows machines and
1860 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1862 To compile this as a module, choose M here: the module will be called
1863 ncpfs. Say N unless you are connected to a Novell network.
1865 source "fs/ncpfs/Kconfig"
1867 config CODA_FS
1868 tristate "Coda file system support (advanced network fs)"
1869 depends on INET
1870 help
1871 Coda is an advanced network file system, similar to NFS in that it
1872 enables you to mount file systems of a remote server and access them
1873 with regular Unix commands as if they were sitting on your hard
1874 disk. Coda has several advantages over NFS: support for
1875 disconnected operation (e.g. for laptops), read/write server
1876 replication, security model for authentication and encryption,
1877 persistent client caches and write back caching.
1879 If you say Y here, your Linux box will be able to act as a Coda
1880 *client*. You will need user level code as well, both for the
1881 client and server. Servers are currently user level, i.e. they need
1882 no kernel support. Please read
1883 <file:Documentation/filesystems/coda.txt> and check out the Coda
1884 home page <http://www.coda.cs.cmu.edu/>.
1886 To compile the coda client support as a module, choose M here: the
1887 module will be called coda.
1889 config CODA_FS_OLD_API
1890 bool "Use 96-bit Coda file identifiers"
1891 depends on CODA_FS
1892 help
1893 A new kernel-userspace API had to be introduced for Coda v6.0
1894 to support larger 128-bit file identifiers as needed by the
1895 new realms implementation.
1897 However this new API is not backward compatible with older
1898 clients. If you really need to run the old Coda userspace
1899 cache manager then say Y.
1901 For most cases you probably want to say N.
1903 config AFS_FS
1904 # for fs/nls/Config.in
1905 tristate "Andrew File System support (AFS) (Experimental)"
1906 depends on INET && EXPERIMENTAL
1907 select RXRPC
1908 help
1909 If you say Y here, you will get an experimental Andrew File System
1910 driver. It currently only supports unsecured read-only AFS access.
1912 See <file:Documentation/filesystems/afs.txt> for more intormation.
1914 If unsure, say N.
1916 config RXRPC
1917 tristate
1919 config 9P_FS
1920 tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
1921 depends on INET && EXPERIMENTAL
1922 help
1923 If you say Y here, you will get experimental support for
1924 Plan 9 resource sharing via the 9P2000 protocol.
1926 See <http://v9fs.sf.net> for more information.
1928 If unsure, say N.
1930 endmenu
1932 menu "Partition Types"
1934 source "fs/partitions/Kconfig"
1936 endmenu
1938 source "fs/nls/Kconfig"
1940 endmenu