ia64/xen-unstable

view linux-2.6-xen-sparse/fs/Kconfig @ 12938:b58670602d35

[POWERPC][XEN] Builtin cmdline dependency rule
Rebuild cmdline.o when the user changes the CMDLINE=X argument passed to
the make invocation. I couldn't find an example of another project that
handles this case properly, so I came up with this.
Signed-off-by: Amos Waterland <apw@us.ibm.com>
Signed-off-by: Hollis Blanchard <hollisb@us.ibm.com>
author Hollis Blanchard <hollisb@us.ibm.com>
date Thu Oct 05 15:48:26 2006 -0500 (2006-10-05)
parents 1ca3d63e7008
children 4fad820a2233
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
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 && 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 MINIX_FS
360 tristate "Minix fs support"
361 help
362 Minix is a simple operating system used in many classes about OS's.
363 The minix file system (method to organize files on a hard disk
364 partition or a floppy disk) was the original file system for Linux,
365 but has been superseded by the second extended file system ext2fs.
366 You don't want to use the minix file system on your hard disk
367 because of certain built-in restrictions, but it is sometimes found
368 on older Linux floppy disks. This option will enlarge your kernel
369 by about 28 KB. If unsure, say N.
371 To compile this file system support as a module, choose M here: the
372 module will be called minix. Note that the file system of your root
373 partition (the one containing the directory /) cannot be compiled as
374 a module.
376 config ROMFS_FS
377 tristate "ROM file system support"
378 ---help---
379 This is a very small read-only file system mainly intended for
380 initial ram disks of installation disks, but it could be used for
381 other read-only media as well. Read
382 <file:Documentation/filesystems/romfs.txt> for details.
384 To compile this file system support as a module, choose M here: the
385 module will be called romfs. Note that the file system of your
386 root partition (the one containing the directory /) cannot be a
387 module.
389 If you don't know whether you need it, then you don't need it:
390 answer N.
392 config INOTIFY
393 bool "Inotify file change notification support"
394 default y
395 ---help---
396 Say Y here to enable inotify support and the associated system
397 calls. Inotify is a file change notification system and a
398 replacement for dnotify. Inotify fixes numerous shortcomings in
399 dnotify and introduces several new features. It allows monitoring
400 of both files and directories via a single open fd. Other features
401 include multiple file events, one-shot support, and unmount
402 notification.
404 For more information, see Documentation/filesystems/inotify.txt
406 If unsure, say Y.
408 config QUOTA
409 bool "Quota support"
410 help
411 If you say Y here, you will be able to set per user limits for disk
412 usage (also called disk quotas). Currently, it works for the
413 ext2, ext3, and reiserfs file system. ext3 also supports journalled
414 quotas for which you don't need to run quotacheck(8) after an unclean
415 shutdown.
416 For further details, read the Quota mini-HOWTO, available from
417 <http://www.tldp.org/docs.html#howto>, or the documentation provided
418 with the quota tools. Probably the quota support is only useful for
419 multi user systems. If unsure, say N.
421 config QFMT_V1
422 tristate "Old quota format support"
423 depends on QUOTA
424 help
425 This quota format was (is) used by kernels earlier than 2.4.22. If
426 you have quota working and you don't want to convert to new quota
427 format say Y here.
429 config QFMT_V2
430 tristate "Quota format v2 support"
431 depends on QUOTA
432 help
433 This quota format allows using quotas with 32-bit UIDs/GIDs. If you
434 need this functionality say Y here.
436 config QUOTACTL
437 bool
438 depends on XFS_QUOTA || QUOTA
439 default y
441 config DNOTIFY
442 bool "Dnotify support" if EMBEDDED
443 default y
444 help
445 Dnotify is a directory-based per-fd file change notification system
446 that uses signals to communicate events to user-space. There exist
447 superior alternatives, but some applications may still rely on
448 dnotify.
450 Because of this, if unsure, say Y.
452 config AUTOFS_FS
453 tristate "Kernel automounter support"
454 help
455 The automounter is a tool to automatically mount remote file systems
456 on demand. This implementation is partially kernel-based to reduce
457 overhead in the already-mounted case; this is unlike the BSD
458 automounter (amd), which is a pure user space daemon.
460 To use the automounter you need the user-space tools from the autofs
461 package; you can find the location in <file:Documentation/Changes>.
462 You also want to answer Y to "NFS file system support", below.
464 If you want to use the newer version of the automounter with more
465 features, say N here and say Y to "Kernel automounter v4 support",
466 below.
468 To compile this support as a module, choose M here: the module will be
469 called autofs.
471 If you are not a part of a fairly large, distributed network, you
472 probably do not need an automounter, and can say N here.
474 config AUTOFS4_FS
475 tristate "Kernel automounter version 4 support (also supports v3)"
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
483 <ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4/>; you also
484 want to answer Y to "NFS file system support", below.
486 To compile this support as a module, choose M here: the module will be
487 called autofs4. You will need to add "alias autofs autofs4" to your
488 modules configuration file.
490 If you are not a part of a fairly large, distributed network or
491 don't have a laptop which needs to dynamically reconfigure to the
492 local network, you probably do not need an automounter, and can say
493 N here.
495 config FUSE_FS
496 tristate "Filesystem in Userspace support"
497 help
498 With FUSE it is possible to implement a fully functional filesystem
499 in a userspace program.
501 There's also companion library: libfuse. This library along with
502 utilities is available from the FUSE homepage:
503 <http://fuse.sourceforge.net/>
505 See <file:Documentation/filesystems/fuse.txt> for more information.
506 See <file:Documentation/Changes> for needed library/utility version.
508 If you want to develop a userspace FS, or if you want to use
509 a filesystem based on FUSE, answer Y or M.
511 menu "CD-ROM/DVD Filesystems"
513 config ISO9660_FS
514 tristate "ISO 9660 CDROM file system support"
515 help
516 This is the standard file system used on CD-ROMs. It was previously
517 known as "High Sierra File System" and is called "hsfs" on other
518 Unix systems. The so-called Rock-Ridge extensions which allow for
519 long Unix filenames and symbolic links are also supported by this
520 driver. If you have a CD-ROM drive and want to do more with it than
521 just listen to audio CDs and watch its LEDs, say Y (and read
522 <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO,
523 available from <http://www.tldp.org/docs.html#howto>), thereby
524 enlarging your kernel by about 27 KB; otherwise say N.
526 To compile this file system support as a module, choose M here: the
527 module will be called isofs.
529 config JOLIET
530 bool "Microsoft Joliet CDROM extensions"
531 depends on ISO9660_FS
532 select NLS
533 help
534 Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system
535 which allows for long filenames in unicode format (unicode is the
536 new 16 bit character code, successor to ASCII, which encodes the
537 characters of almost all languages of the world; see
538 <http://www.unicode.org/> for more information). Say Y here if you
539 want to be able to read Joliet CD-ROMs under Linux.
541 config ZISOFS
542 bool "Transparent decompression extension"
543 depends on ISO9660_FS
544 select ZLIB_INFLATE
545 help
546 This is a Linux-specific extension to RockRidge which lets you store
547 data in compressed form on a CD-ROM and have it transparently
548 decompressed when the CD-ROM is accessed. See
549 <http://www.kernel.org/pub/linux/utils/fs/zisofs/> for the tools
550 necessary to create such a filesystem. Say Y here if you want to be
551 able to read such compressed CD-ROMs.
553 config ZISOFS_FS
554 # for fs/nls/Config.in
555 tristate
556 depends on ZISOFS
557 default ISO9660_FS
559 config UDF_FS
560 tristate "UDF file system support"
561 help
562 This is the new file system used on some CD-ROMs and DVDs. Say Y if
563 you intend to mount DVD discs or CDRW's written in packet mode, or
564 if written to by other UDF utilities, such as DirectCD.
565 Please read <file:Documentation/filesystems/udf.txt>.
567 To compile this file system support as a module, choose M here: the
568 module will be called udf.
570 If unsure, say N.
572 config UDF_NLS
573 bool
574 default y
575 depends on (UDF_FS=m && NLS) || (UDF_FS=y && NLS=y)
577 endmenu
579 menu "DOS/FAT/NT Filesystems"
581 config FAT_FS
582 tristate
583 select NLS
584 help
585 If you want to use one of the FAT-based file systems (the MS-DOS and
586 VFAT (Windows 95) file systems), then you must say Y or M here
587 to include FAT support. You will then be able to mount partitions or
588 diskettes with FAT-based file systems and transparently access the
589 files on them, i.e. MSDOS files will look and behave just like all
590 other Unix files.
592 This FAT support is not a file system in itself, it only provides
593 the foundation for the other file systems. You will have to say Y or
594 M to at least one of "MSDOS fs support" or "VFAT fs support" in
595 order to make use of it.
597 Another way to read and write MSDOS floppies and hard drive
598 partitions from within Linux (but not transparently) is with the
599 mtools ("man mtools") program suite. You don't need to say Y here in
600 order to do that.
602 If you need to move large files on floppies between a DOS and a
603 Linux box, say Y here, mount the floppy under Linux with an MSDOS
604 file system and use GNU tar's M option. GNU tar is a program
605 available for Unix and DOS ("man tar" or "info tar").
607 It is now also becoming possible to read and write compressed FAT
608 file systems; read <file:Documentation/filesystems/fat_cvf.txt> for
609 details.
611 The FAT support will enlarge your kernel by about 37 KB. If unsure,
612 say Y.
614 To compile this as a module, choose M here: the module will be called
615 fat. Note that if you compile the FAT support as a module, you
616 cannot compile any of the FAT-based file systems into the kernel
617 -- they will have to be modules as well.
619 config MSDOS_FS
620 tristate "MSDOS fs support"
621 select FAT_FS
622 help
623 This allows you to mount MSDOS partitions of your hard drive (unless
624 they are compressed; to access compressed MSDOS partitions under
625 Linux, you can either use the DOS emulator DOSEMU, described in the
626 DOSEMU-HOWTO, available from
627 <http://www.tldp.org/docs.html#howto>, or try dmsdosfs in
628 <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you
629 intend to use dosemu with a non-compressed MSDOS partition, say Y
630 here) and MSDOS floppies. This means that file access becomes
631 transparent, i.e. the MSDOS files look and behave just like all
632 other Unix files.
634 If you have Windows 95 or Windows NT installed on your MSDOS
635 partitions, you should use the VFAT file system (say Y to "VFAT fs
636 support" below), or you will not be able to see the long filenames
637 generated by Windows 95 / Windows NT.
639 This option will enlarge your kernel by about 7 KB. If unsure,
640 answer Y. This will only work if you said Y to "DOS FAT fs support"
641 as well. To compile this as a module, choose M here: the module will
642 be called msdos.
644 config VFAT_FS
645 tristate "VFAT (Windows-95) fs support"
646 select FAT_FS
647 help
648 This option provides support for normal Windows file systems with
649 long filenames. That includes non-compressed FAT-based file systems
650 used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
651 programs from the mtools package.
653 The VFAT support enlarges your kernel by about 10 KB and it only
654 works if you said Y to the "DOS FAT fs support" above. Please read
655 the file <file:Documentation/filesystems/vfat.txt> for details. If
656 unsure, say Y.
658 To compile this as a module, choose M here: the module will be called
659 vfat.
661 config FAT_DEFAULT_CODEPAGE
662 int "Default codepage for FAT"
663 depends on MSDOS_FS || VFAT_FS
664 default 437
665 help
666 This option should be set to the codepage of your FAT filesystems.
667 It can be overridden with the "codepage" mount option.
668 See <file:Documentation/filesystems/vfat.txt> for more information.
670 config FAT_DEFAULT_IOCHARSET
671 string "Default iocharset for FAT"
672 depends on VFAT_FS
673 default "iso8859-1"
674 help
675 Set this to the default input/output character set you'd
676 like FAT to use. It should probably match the character set
677 that most of your FAT filesystems use, and can be overridden
678 with the "iocharset" mount option for FAT filesystems.
679 Note that "utf8" is not recommended for FAT filesystems.
680 If unsure, you shouldn't set "utf8" here.
681 See <file:Documentation/filesystems/vfat.txt> for more information.
683 config NTFS_FS
684 tristate "NTFS file system support"
685 select NLS
686 help
687 NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003.
689 Saying Y or M here enables read support. There is partial, but
690 safe, write support available. For write support you must also
691 say Y to "NTFS write support" below.
693 There are also a number of user-space tools available, called
694 ntfsprogs. These include ntfsundelete and ntfsresize, that work
695 without NTFS support enabled in the kernel.
697 This is a rewrite from scratch of Linux NTFS support and replaced
698 the old NTFS code starting with Linux 2.5.11. A backport to
699 the Linux 2.4 kernel series is separately available as a patch
700 from the project web site.
702 For more information see <file:Documentation/filesystems/ntfs.txt>
703 and <http://linux-ntfs.sourceforge.net/>.
705 To compile this file system support as a module, choose M here: the
706 module will be called ntfs.
708 If you are not using Windows NT, 2000, XP or 2003 in addition to
709 Linux on your computer it is safe to say N.
711 config NTFS_DEBUG
712 bool "NTFS debugging support"
713 depends on NTFS_FS
714 help
715 If you are experiencing any problems with the NTFS file system, say
716 Y here. This will result in additional consistency checks to be
717 performed by the driver as well as additional debugging messages to
718 be written to the system log. Note that debugging messages are
719 disabled by default. To enable them, supply the option debug_msgs=1
720 at the kernel command line when booting the kernel or as an option
721 to insmod when loading the ntfs module. Once the driver is active,
722 you can enable debugging messages by doing (as root):
723 echo 1 > /proc/sys/fs/ntfs-debug
724 Replacing the "1" with "0" would disable debug messages.
726 If you leave debugging messages disabled, this results in little
727 overhead, but enabling debug messages results in very significant
728 slowdown of the system.
730 When reporting bugs, please try to have available a full dump of
731 debugging messages while the misbehaviour was occurring.
733 config NTFS_RW
734 bool "NTFS write support"
735 depends on NTFS_FS
736 help
737 This enables the partial, but safe, write support in the NTFS driver.
739 The only supported operation is overwriting existing files, without
740 changing the file length. No file or directory creation, deletion or
741 renaming is possible. Note only non-resident files can be written to
742 so you may find that some very small files (<500 bytes or so) cannot
743 be written to.
745 While we cannot guarantee that it will not damage any data, we have
746 so far not received a single report where the driver would have
747 damaged someones data so we assume it is perfectly safe to use.
749 Note: While write support is safe in this version (a rewrite from
750 scratch of the NTFS support), it should be noted that the old NTFS
751 write support, included in Linux 2.5.10 and before (since 1997),
752 is not safe.
754 This is currently useful with TopologiLinux. TopologiLinux is run
755 on top of any DOS/Microsoft Windows system without partitioning your
756 hard disk. Unlike other Linux distributions TopologiLinux does not
757 need its own partition. For more information see
758 <http://topologi-linux.sourceforge.net/>
760 It is perfectly safe to say N here.
762 endmenu
764 menu "Pseudo filesystems"
766 config PROC_FS
767 bool "/proc file system support"
768 help
769 This is a virtual file system providing information about the status
770 of the system. "Virtual" means that it doesn't take up any space on
771 your hard disk: the files are created on the fly by the kernel when
772 you try to access them. Also, you cannot read the files with older
773 version of the program less: you need to use more or cat.
775 It's totally cool; for example, "cat /proc/interrupts" gives
776 information about what the different IRQs are used for at the moment
777 (there is a small number of Interrupt ReQuest lines in your computer
778 that are used by the attached devices to gain the CPU's attention --
779 often a source of trouble if two devices are mistakenly configured
780 to use the same IRQ). The program procinfo to display some
781 information about your system gathered from the /proc file system.
783 Before you can use the /proc file system, it has to be mounted,
784 meaning it has to be given a location in the directory hierarchy.
785 That location should be /proc. A command such as "mount -t proc proc
786 /proc" or the equivalent line in /etc/fstab does the job.
788 The /proc file system is explained in the file
789 <file:Documentation/filesystems/proc.txt> and on the proc(5) manpage
790 ("man 5 proc").
792 This option will enlarge your kernel by about 67 KB. Several
793 programs depend on this, so everyone should say Y here.
795 config PROC_KCORE
796 bool "/proc/kcore support" if !ARM
797 depends on PROC_FS && MMU
799 config PROC_VMCORE
800 bool "/proc/vmcore support (EXPERIMENTAL)"
801 depends on PROC_FS && EXPERIMENTAL && CRASH_DUMP
802 help
803 Exports the dump image of crashed kernel in ELF format.
805 config SYSFS
806 bool "sysfs file system support" if EMBEDDED
807 default y
808 help
809 The sysfs filesystem is a virtual filesystem that the kernel uses to
810 export internal kernel objects, their attributes, and their
811 relationships to one another.
813 Users can use sysfs to ascertain useful information about the running
814 kernel, such as the devices the kernel has discovered on each bus and
815 which driver each is bound to. sysfs can also be used to tune devices
816 and other kernel subsystems.
818 Some system agents rely on the information in sysfs to operate.
819 /sbin/hotplug uses device and object attributes in sysfs to assist in
820 delegating policy decisions, like persistantly naming devices.
822 sysfs is currently used by the block subsystem to mount the root
823 partition. If sysfs is disabled you must specify the boot device on
824 the kernel boot command line via its major and minor numbers. For
825 example, "root=03:01" for /dev/hda1.
827 Designers of embedded systems may wish to say N here to conserve space.
829 config TMPFS
830 bool "Virtual memory file system support (former shm fs)"
831 help
832 Tmpfs is a file system which keeps all files in virtual memory.
834 Everything in tmpfs is temporary in the sense that no files will be
835 created on your hard drive. The files live in memory and swap
836 space. If you unmount a tmpfs instance, everything stored therein is
837 lost.
839 See <file:Documentation/filesystems/tmpfs.txt> for details.
841 config HUGETLBFS
842 bool "HugeTLB file system support"
843 depends X86 || IA64 || PPC64 || SPARC64 || SUPERH || BROKEN
844 depends !XEN
846 config HUGETLB_PAGE
847 def_bool HUGETLBFS
849 config RAMFS
850 bool
851 default y
852 ---help---
853 Ramfs is a file system which keeps all files in RAM. It allows
854 read and write access.
856 It is more of an programming example than a useable file system. If
857 you need a file system which lives in RAM with limit checking use
858 tmpfs.
860 To compile this as a module, choose M here: the module will be called
861 ramfs.
863 config RELAYFS_FS
864 tristate "Relayfs file system support"
865 ---help---
866 Relayfs is a high-speed data relay filesystem designed to provide
867 an efficient mechanism for tools and facilities to relay large
868 amounts of data from kernel space to user space.
870 To compile this code as a module, choose M here: the module will be
871 called relayfs.
873 If unsure, say N.
875 config CONFIGFS_FS
876 tristate "Userspace-driven configuration filesystem (EXPERIMENTAL)"
877 depends on EXPERIMENTAL
878 help
879 configfs is a ram-based filesystem that provides the converse
880 of sysfs's functionality. Where sysfs is a filesystem-based
881 view of kernel objects, configfs is a filesystem-based manager
882 of kernel objects, or config_items.
884 Both sysfs and configfs can and should exist together on the
885 same system. One is not a replacement for the other.
887 endmenu
889 menu "Miscellaneous filesystems"
891 config ADFS_FS
892 tristate "ADFS file system support (EXPERIMENTAL)"
893 depends on EXPERIMENTAL
894 help
895 The Acorn Disc Filing System is the standard file system of the
896 RiscOS operating system which runs on Acorn's ARM-based Risc PC
897 systems and the Acorn Archimedes range of machines. If you say Y
898 here, Linux will be able to read from ADFS partitions on hard drives
899 and from ADFS-formatted floppy discs. If you also want to be able to
900 write to those devices, say Y to "ADFS write support" below.
902 The ADFS partition should be the first partition (i.e.,
903 /dev/[hs]d?1) on each of your drives. Please read the file
904 <file:Documentation/filesystems/adfs.txt> for further details.
906 To compile this code as a module, choose M here: the module will be
907 called adfs.
909 If unsure, say N.
911 config ADFS_FS_RW
912 bool "ADFS write support (DANGEROUS)"
913 depends on ADFS_FS
914 help
915 If you say Y here, you will be able to write to ADFS partitions on
916 hard drives and ADFS-formatted floppy disks. This is experimental
917 codes, so if you're unsure, say N.
919 config AFFS_FS
920 tristate "Amiga FFS file system support (EXPERIMENTAL)"
921 depends on EXPERIMENTAL
922 help
923 The Fast File System (FFS) is the common file system used on hard
924 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
925 if you want to be able to read and write files from and to an Amiga
926 FFS partition on your hard drive. Amiga floppies however cannot be
927 read with this driver due to an incompatibility of the floppy
928 controller used in an Amiga and the standard floppy controller in
929 PCs and workstations. Read <file:Documentation/filesystems/affs.txt>
930 and <file:fs/affs/Changes>.
932 With this driver you can also mount disk files used by Bernd
933 Schmidt's Un*X Amiga Emulator
934 (<http://www.freiburg.linux.de/~uae/>).
935 If you want to do this, you will also need to say Y or M to "Loop
936 device support", above.
938 To compile this file system support as a module, choose M here: the
939 module will be called affs. If unsure, say N.
941 config HFS_FS
942 tristate "Apple Macintosh file system support (EXPERIMENTAL)"
943 depends on EXPERIMENTAL
944 select NLS
945 help
946 If you say Y here, you will be able to mount Macintosh-formatted
947 floppy disks and hard drive partitions with full read-write access.
948 Please read <file:fs/hfs/HFS.txt> to learn about the available mount
949 options.
951 To compile this file system support as a module, choose M here: the
952 module will be called hfs.
954 config HFSPLUS_FS
955 tristate "Apple Extended HFS file system support"
956 select NLS
957 select NLS_UTF8
958 help
959 If you say Y here, you will be able to mount extended format
960 Macintosh-formatted hard drive partitions with full read-write access.
962 This file system is often called HFS+ and was introduced with
963 MacOS 8. It includes all Mac specific filesystem data such as
964 data forks and creator codes, but it also has several UNIX
965 style features such as file ownership and permissions.
967 config BEFS_FS
968 tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)"
969 depends on EXPERIMENTAL
970 select NLS
971 help
972 The BeOS File System (BeFS) is the native file system of Be, Inc's
973 BeOS. Notable features include support for arbitrary attributes
974 on files and directories, and database-like indeces on selected
975 attributes. (Also note that this driver doesn't make those features
976 available at this time). It is a 64 bit filesystem, so it supports
977 extremly large volumes and files.
979 If you use this filesystem, you should also say Y to at least one
980 of the NLS (native language support) options below.
982 If you don't know what this is about, say N.
984 To compile this as a module, choose M here: the module will be
985 called befs.
987 config BEFS_DEBUG
988 bool "Debug BeFS"
989 depends on BEFS_FS
990 help
991 If you say Y here, you can use the 'debug' mount option to enable
992 debugging output from the driver.
994 config BFS_FS
995 tristate "BFS file system support (EXPERIMENTAL)"
996 depends on EXPERIMENTAL
997 help
998 Boot File System (BFS) is a file system used under SCO UnixWare to
999 allow the bootloader access to the kernel image and other important
1000 files during the boot process. It is usually mounted under /stand
1001 and corresponds to the slice marked as "STAND" in the UnixWare
1002 partition. You should say Y if you want to read or write the files
1003 on your /stand slice from within Linux. You then also need to say Y
1004 to "UnixWare slices support", below. More information about the BFS
1005 file system is contained in the file
1006 <file:Documentation/filesystems/bfs.txt>.
1008 If you don't know what this is about, say N.
1010 To compile this as a module, choose M here: the module will be called
1011 bfs. Note that the file system of your root partition (the one
1012 containing the directory /) cannot be compiled as a module.
1016 config EFS_FS
1017 tristate "EFS file system support (read only) (EXPERIMENTAL)"
1018 depends on EXPERIMENTAL
1019 help
1020 EFS is an older file system used for non-ISO9660 CD-ROMs and hard
1021 disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
1022 uses the XFS file system for hard disk partitions however).
1024 This implementation only offers read-only access. If you don't know
1025 what all this is about, it's safe to say N. For more information
1026 about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
1028 To compile the EFS file system support as a module, choose M here: the
1029 module will be called efs.
1031 config JFFS_FS
1032 tristate "Journalling Flash File System (JFFS) support"
1033 depends on MTD
1034 help
1035 JFFS is the Journaling Flash File System developed by Axis
1036 Communications in Sweden, aimed at providing a crash/powerdown-safe
1037 file system for disk-less embedded devices. Further information is
1038 available at (<http://developer.axis.com/software/jffs/>).
1040 config JFFS_FS_VERBOSE
1041 int "JFFS debugging verbosity (0 = quiet, 3 = noisy)"
1042 depends on JFFS_FS
1043 default "0"
1044 help
1045 Determines the verbosity level of the JFFS debugging messages.
1047 config JFFS_PROC_FS
1048 bool "JFFS stats available in /proc filesystem"
1049 depends on JFFS_FS && PROC_FS
1050 help
1051 Enabling this option will cause statistics from mounted JFFS file systems
1052 to be made available to the user in the /proc/fs/jffs/ directory.
1054 config JFFS2_FS
1055 tristate "Journalling Flash File System v2 (JFFS2) support"
1056 select CRC32
1057 depends on MTD
1058 help
1059 JFFS2 is the second generation of the Journalling Flash File System
1060 for use on diskless embedded devices. It provides improved wear
1061 levelling, compression and support for hard links. You cannot use
1062 this on normal block devices, only on 'MTD' devices.
1064 Further information on the design and implementation of JFFS2 is
1065 available at <http://sources.redhat.com/jffs2/>.
1067 config JFFS2_FS_DEBUG
1068 int "JFFS2 debugging verbosity (0 = quiet, 2 = noisy)"
1069 depends on JFFS2_FS
1070 default "0"
1071 help
1072 This controls the amount of debugging messages produced by the JFFS2
1073 code. Set it to zero for use in production systems. For evaluation,
1074 testing and debugging, it's advisable to set it to one. This will
1075 enable a few assertions and will print debugging messages at the
1076 KERN_DEBUG loglevel, where they won't normally be visible. Level 2
1077 is unlikely to be useful - it enables extra debugging in certain
1078 areas which at one point needed debugging, but when the bugs were
1079 located and fixed, the detailed messages were relegated to level 2.
1081 If reporting bugs, please try to have available a full dump of the
1082 messages at debug level 1 while the misbehaviour was occurring.
1084 config JFFS2_FS_WRITEBUFFER
1085 bool "JFFS2 write-buffering support"
1086 depends on JFFS2_FS
1087 default y
1088 help
1089 This enables the write-buffering support in JFFS2.
1091 This functionality is required to support JFFS2 on the following
1092 types of flash devices:
1093 - NAND flash
1094 - NOR flash with transparent ECC
1095 - DataFlash
1097 config JFFS2_SUMMARY
1098 bool "JFFS2 summary support (EXPERIMENTAL)"
1099 depends on JFFS2_FS && EXPERIMENTAL
1100 default n
1101 help
1102 This feature makes it possible to use summary information
1103 for faster filesystem mount.
1105 The summary information can be inserted into a filesystem image
1106 by the utility 'sumtool'.
1108 If unsure, say 'N'.
1110 config JFFS2_COMPRESSION_OPTIONS
1111 bool "Advanced compression options for JFFS2"
1112 depends on JFFS2_FS
1113 default n
1114 help
1115 Enabling this option allows you to explicitly choose which
1116 compression modules, if any, are enabled in JFFS2. Removing
1117 compressors and mean you cannot read existing file systems,
1118 and enabling experimental compressors can mean that you
1119 write a file system which cannot be read by a standard kernel.
1121 If unsure, you should _definitely_ say 'N'.
1123 config JFFS2_ZLIB
1124 bool "JFFS2 ZLIB compression support" if JFFS2_COMPRESSION_OPTIONS
1125 select ZLIB_INFLATE
1126 select ZLIB_DEFLATE
1127 depends on JFFS2_FS
1128 default y
1129 help
1130 Zlib is designed to be a free, general-purpose, legally unencumbered,
1131 lossless data-compression library for use on virtually any computer
1132 hardware and operating system. See <http://www.gzip.org/zlib/> for
1133 further information.
1135 Say 'Y' if unsure.
1137 config JFFS2_RTIME
1138 bool "JFFS2 RTIME compression support" if JFFS2_COMPRESSION_OPTIONS
1139 depends on JFFS2_FS
1140 default y
1141 help
1142 Rtime does manage to recompress already-compressed data. Say 'Y' if unsure.
1144 config JFFS2_RUBIN
1145 bool "JFFS2 RUBIN compression support" if JFFS2_COMPRESSION_OPTIONS
1146 depends on JFFS2_FS
1147 default n
1148 help
1149 RUBINMIPS and DYNRUBIN compressors. Say 'N' if unsure.
1151 choice
1152 prompt "JFFS2 default compression mode" if JFFS2_COMPRESSION_OPTIONS
1153 default JFFS2_CMODE_PRIORITY
1154 depends on JFFS2_FS
1155 help
1156 You can set here the default compression mode of JFFS2 from
1157 the available compression modes. Don't touch if unsure.
1159 config JFFS2_CMODE_NONE
1160 bool "no compression"
1161 help
1162 Uses no compression.
1164 config JFFS2_CMODE_PRIORITY
1165 bool "priority"
1166 help
1167 Tries the compressors in a predefinied order and chooses the first
1168 successful one.
1170 config JFFS2_CMODE_SIZE
1171 bool "size (EXPERIMENTAL)"
1172 help
1173 Tries all compressors and chooses the one which has the smallest
1174 result.
1176 endchoice
1178 config CRAMFS
1179 tristate "Compressed ROM file system support (cramfs)"
1180 select ZLIB_INFLATE
1181 help
1182 Saying Y here includes support for CramFs (Compressed ROM File
1183 System). CramFs is designed to be a simple, small, and compressed
1184 file system for ROM based embedded systems. CramFs is read-only,
1185 limited to 256MB file systems (with 16MB files), and doesn't support
1186 16/32 bits uid/gid, hard links and timestamps.
1188 See <file:Documentation/filesystems/cramfs.txt> and
1189 <file:fs/cramfs/README> for further information.
1191 To compile this as a module, choose M here: the module will be called
1192 cramfs. Note that the root file system (the one containing the
1193 directory /) cannot be compiled as a module.
1195 If unsure, say N.
1197 config VXFS_FS
1198 tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
1199 help
1200 FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
1201 file system format. VERITAS VxFS(TM) is the standard file system
1202 of SCO UnixWare (and possibly others) and optionally available
1203 for Sunsoft Solaris, HP-UX and many other operating systems.
1204 Currently only readonly access is supported.
1206 NOTE: the file system type as used by mount(1), mount(2) and
1207 fstab(5) is 'vxfs' as it describes the file system format, not
1208 the actual driver.
1210 To compile this as a module, choose M here: the module will be
1211 called freevxfs. If unsure, say N.
1214 config HPFS_FS
1215 tristate "OS/2 HPFS file system support"
1216 help
1217 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
1218 is the file system used for organizing files on OS/2 hard disk
1219 partitions. Say Y if you want to be able to read files from and
1220 write files to an OS/2 HPFS partition on your hard drive. OS/2
1221 floppies however are in regular MSDOS format, so you don't need this
1222 option in order to be able to read them. Read
1223 <file:Documentation/filesystems/hpfs.txt>.
1225 To compile this file system support as a module, choose M here: the
1226 module will be called hpfs. If unsure, say N.
1230 config QNX4FS_FS
1231 tristate "QNX4 file system support (read only)"
1232 help
1233 This is the file system used by the real-time operating systems
1234 QNX 4 and QNX 6 (the latter is also called QNX RTP).
1235 Further information is available at <http://www.qnx.com/>.
1236 Say Y if you intend to mount QNX hard disks or floppies.
1237 Unless you say Y to "QNX4FS read-write support" below, you will
1238 only be able to read these file systems.
1240 To compile this file system support as a module, choose M here: the
1241 module will be called qnx4.
1243 If you don't know whether you need it, then you don't need it:
1244 answer N.
1246 config QNX4FS_RW
1247 bool "QNX4FS write support (DANGEROUS)"
1248 depends on QNX4FS_FS && EXPERIMENTAL && BROKEN
1249 help
1250 Say Y if you want to test write support for QNX4 file systems.
1252 It's currently broken, so for now:
1253 answer N.
1257 config SYSV_FS
1258 tristate "System V/Xenix/V7/Coherent file system support"
1259 help
1260 SCO, Xenix and Coherent are commercial Unix systems for Intel
1261 machines, and Version 7 was used on the DEC PDP-11. Saying Y
1262 here would allow you to read from their floppies and hard disk
1263 partitions.
1265 If you have floppies or hard disk partitions like that, it is likely
1266 that they contain binaries from those other Unix systems; in order
1267 to run these binaries, you will want to install linux-abi which is a
1268 a set of kernel modules that lets you run SCO, Xenix, Wyse,
1269 UnixWare, Dell Unix and System V programs under Linux. It is
1270 available via FTP (user: ftp) from
1271 <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
1272 NOTE: that will work only for binaries from Intel-based systems;
1273 PDP ones will have to wait until somebody ports Linux to -11 ;-)
1275 If you only intend to mount files from some other Unix over the
1276 network using NFS, you don't need the System V file system support
1277 (but you need NFS file system support obviously).
1279 Note that this option is generally not needed for floppies, since a
1280 good portable way to transport files and directories between unixes
1281 (and even other operating systems) is given by the tar program ("man
1282 tar" or preferably "info tar"). Note also that this option has
1283 nothing whatsoever to do with the option "System V IPC". Read about
1284 the System V file system in
1285 <file:Documentation/filesystems/sysv-fs.txt>.
1286 Saying Y here will enlarge your kernel by about 27 KB.
1288 To compile this as a module, choose M here: the module will be called
1289 sysv.
1291 If you haven't heard about all of this before, it's safe to say N.
1295 config UFS_FS
1296 tristate "UFS file system support (read only)"
1297 help
1298 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
1299 OpenBSD and NeXTstep) use a file system called UFS. Some System V
1300 Unixes can create and mount hard disk partitions and diskettes using
1301 this file system as well. Saying Y here will allow you to read from
1302 these partitions; if you also want to write to them, say Y to the
1303 experimental "UFS file system write support", below. Please read the
1304 file <file:Documentation/filesystems/ufs.txt> for more information.
1306 The recently released UFS2 variant (used in FreeBSD 5.x) is
1307 READ-ONLY supported.
1309 If you only intend to mount files from some other Unix over the
1310 network using NFS, you don't need the UFS file system support (but
1311 you need NFS file system support obviously).
1313 Note that this option is generally not needed for floppies, since a
1314 good portable way to transport files and directories between unixes
1315 (and even other operating systems) is given by the tar program ("man
1316 tar" or preferably "info tar").
1318 When accessing NeXTstep files, you may need to convert them from the
1319 NeXT character set to the Latin1 character set; use the program
1320 recode ("info recode") for this purpose.
1322 To compile the UFS file system support as a module, choose M here: the
1323 module will be called ufs.
1325 If you haven't heard about all of this before, it's safe to say N.
1327 config UFS_FS_WRITE
1328 bool "UFS file system write support (DANGEROUS)"
1329 depends on UFS_FS && EXPERIMENTAL && BROKEN
1330 help
1331 Say Y here if you want to try writing to UFS partitions. This is
1332 experimental, so you should back up your UFS partitions beforehand.
1334 endmenu
1336 menu "Network File Systems"
1337 depends on NET
1339 config NFS_FS
1340 tristate "NFS file system support"
1341 depends on INET
1342 select LOCKD
1343 select SUNRPC
1344 select NFS_ACL_SUPPORT if NFS_V3_ACL
1345 help
1346 If you are connected to some other (usually local) Unix computer
1347 (using SLIP, PLIP, PPP or Ethernet) and want to mount files residing
1348 on that computer (the NFS server) using the Network File Sharing
1349 protocol, say Y. "Mounting files" means that the client can access
1350 the files with usual UNIX commands as if they were sitting on the
1351 client's hard disk. For this to work, the server must run the
1352 programs nfsd and mountd (but does not need to have NFS file system
1353 support enabled in its kernel). NFS is explained in the Network
1354 Administrator's Guide, available from
1355 <http://www.tldp.org/docs.html#guide>, on its man page: "man
1356 nfs", and in the NFS-HOWTO.
1358 A superior but less widely used alternative to NFS is provided by
1359 the Coda file system; see "Coda file system support" below.
1361 If you say Y here, you should have said Y to TCP/IP networking also.
1362 This option would enlarge your kernel by about 27 KB.
1364 To compile this file system support as a module, choose M here: the
1365 module will be called nfs.
1367 If you are configuring a diskless machine which will mount its root
1368 file system over NFS at boot time, say Y here and to "Kernel
1369 level IP autoconfiguration" above and to "Root file system on NFS"
1370 below. You cannot compile this driver as a module in this case.
1371 There are two packages designed for booting diskless machines over
1372 the net: netboot, available from
1373 <http://ftp1.sourceforge.net/netboot/>, and Etherboot,
1374 available from <http://ftp1.sourceforge.net/etherboot/>.
1376 If you don't know what all this is about, say N.
1378 config NFS_V3
1379 bool "Provide NFSv3 client support"
1380 depends on NFS_FS
1381 help
1382 Say Y here if you want your NFS client to be able to speak version
1383 3 of the NFS protocol.
1385 If unsure, say Y.
1387 config NFS_V3_ACL
1388 bool "Provide client support for the NFSv3 ACL protocol extension"
1389 depends on NFS_V3
1390 help
1391 Implement the NFSv3 ACL protocol extension for manipulating POSIX
1392 Access Control Lists. The server should also be compiled with
1393 the NFSv3 ACL protocol extension; see the CONFIG_NFSD_V3_ACL option.
1395 If unsure, say N.
1397 config NFS_V4
1398 bool "Provide NFSv4 client support (EXPERIMENTAL)"
1399 depends on NFS_FS && EXPERIMENTAL
1400 select RPCSEC_GSS_KRB5
1401 help
1402 Say Y here if you want your NFS client to be able to speak the newer
1403 version 4 of the NFS protocol.
1405 Note: Requires auxiliary userspace daemons which may be found on
1406 http://www.citi.umich.edu/projects/nfsv4/
1408 If unsure, say N.
1410 config NFS_DIRECTIO
1411 bool "Allow direct I/O on NFS files (EXPERIMENTAL)"
1412 depends on NFS_FS && EXPERIMENTAL
1413 help
1414 This option enables applications to perform uncached I/O on files
1415 in NFS file systems using the O_DIRECT open() flag. When O_DIRECT
1416 is set for a file, its data is not cached in the system's page
1417 cache. Data is moved to and from user-level application buffers
1418 directly. Unlike local disk-based file systems, NFS O_DIRECT has
1419 no alignment restrictions.
1421 Unless your program is designed to use O_DIRECT properly, you are
1422 much better off allowing the NFS client to manage data caching for
1423 you. Misusing O_DIRECT can cause poor server performance or network
1424 storms. This kernel build option defaults OFF to avoid exposing
1425 system administrators unwittingly to a potentially hazardous
1426 feature.
1428 For more details on NFS O_DIRECT, see fs/nfs/direct.c.
1430 If unsure, say N. This reduces the size of the NFS client, and
1431 causes open() to return EINVAL if a file residing in NFS is
1432 opened with the O_DIRECT flag.
1434 config NFSD
1435 tristate "NFS server support"
1436 depends on INET
1437 select LOCKD
1438 select SUNRPC
1439 select EXPORTFS
1440 select NFS_ACL_SUPPORT if NFSD_V3_ACL || NFSD_V2_ACL
1441 help
1442 If you want your Linux box to act as an NFS *server*, so that other
1443 computers on your local network which support NFS can access certain
1444 directories on your box transparently, you have two options: you can
1445 use the self-contained user space program nfsd, in which case you
1446 should say N here, or you can say Y and use the kernel based NFS
1447 server. The advantage of the kernel based solution is that it is
1448 faster.
1450 In either case, you will need support software; the respective
1451 locations are given in the file <file:Documentation/Changes> in the
1452 NFS section.
1454 If you say Y here, you will get support for version 2 of the NFS
1455 protocol (NFSv2). If you also want NFSv3, say Y to the next question
1456 as well.
1458 Please read the NFS-HOWTO, available from
1459 <http://www.tldp.org/docs.html#howto>.
1461 To compile the NFS server support as a module, choose M here: the
1462 module will be called nfsd. If unsure, say N.
1464 config NFSD_V2_ACL
1465 bool
1466 depends on NFSD
1468 config NFSD_V3
1469 bool "Provide NFSv3 server support"
1470 depends on NFSD
1471 help
1472 If you would like to include the NFSv3 server as well as the NFSv2
1473 server, say Y here. If unsure, say Y.
1475 config NFSD_V3_ACL
1476 bool "Provide server support for the NFSv3 ACL protocol extension"
1477 depends on NFSD_V3
1478 select NFSD_V2_ACL
1479 help
1480 Implement the NFSv3 ACL protocol extension for manipulating POSIX
1481 Access Control Lists on exported file systems. NFS clients should
1482 be compiled with the NFSv3 ACL protocol extension; see the
1483 CONFIG_NFS_V3_ACL option. If unsure, say N.
1485 config NFSD_V4
1486 bool "Provide NFSv4 server support (EXPERIMENTAL)"
1487 depends on NFSD_V3 && EXPERIMENTAL
1488 select NFSD_TCP
1489 select CRYPTO_MD5
1490 select CRYPTO
1491 select FS_POSIX_ACL
1492 help
1493 If you would like to include the NFSv4 server as well as the NFSv2
1494 and NFSv3 servers, say Y here. This feature is experimental, and
1495 should only be used if you are interested in helping to test NFSv4.
1496 If unsure, say N.
1498 config NFSD_TCP
1499 bool "Provide NFS server over TCP support"
1500 depends on NFSD
1501 default y
1502 help
1503 If you want your NFS server to support TCP connections, say Y here.
1504 TCP connections usually perform better than the default UDP when
1505 the network is lossy or congested. If unsure, say Y.
1507 config ROOT_NFS
1508 bool "Root file system on NFS"
1509 depends on NFS_FS=y && IP_PNP
1510 help
1511 If you want your Linux box to mount its whole root file system (the
1512 one containing the directory /) from some other computer over the
1513 net via NFS (presumably because your box doesn't have a hard disk),
1514 say Y. Read <file:Documentation/nfsroot.txt> for details. It is
1515 likely that in this case, you also want to say Y to "Kernel level IP
1516 autoconfiguration" so that your box can discover its network address
1517 at boot time.
1519 Most people say N here.
1521 config LOCKD
1522 tristate
1524 config LOCKD_V4
1525 bool
1526 depends on NFSD_V3 || NFS_V3
1527 default y
1529 config EXPORTFS
1530 tristate
1532 config NFS_ACL_SUPPORT
1533 tristate
1534 select FS_POSIX_ACL
1536 config NFS_COMMON
1537 bool
1538 depends on NFSD || NFS_FS
1539 default y
1541 config SUNRPC
1542 tristate
1544 config SUNRPC_GSS
1545 tristate
1547 config RPCSEC_GSS_KRB5
1548 tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
1549 depends on SUNRPC && EXPERIMENTAL
1550 select SUNRPC_GSS
1551 select CRYPTO
1552 select CRYPTO_MD5
1553 select CRYPTO_DES
1554 help
1555 Provides for secure RPC calls by means of a gss-api
1556 mechanism based on Kerberos V5. This is required for
1557 NFSv4.
1559 Note: Requires an auxiliary userspace daemon which may be found on
1560 http://www.citi.umich.edu/projects/nfsv4/
1562 If unsure, say N.
1564 config RPCSEC_GSS_SPKM3
1565 tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
1566 depends on SUNRPC && EXPERIMENTAL
1567 select SUNRPC_GSS
1568 select CRYPTO
1569 select CRYPTO_MD5
1570 select CRYPTO_DES
1571 help
1572 Provides for secure RPC calls by means of a gss-api
1573 mechanism based on the SPKM3 public-key mechanism.
1575 Note: Requires an auxiliary userspace daemon which may be found on
1576 http://www.citi.umich.edu/projects/nfsv4/
1578 If unsure, say N.
1580 config SMB_FS
1581 tristate "SMB file system support (to mount Windows shares etc.)"
1582 depends on INET
1583 select NLS
1584 help
1585 SMB (Server Message Block) is the protocol Windows for Workgroups
1586 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
1587 files and printers over local networks. Saying Y here allows you to
1588 mount their file systems (often called "shares" in this context) and
1589 access them just like any other Unix directory. Currently, this
1590 works only if the Windows machines use TCP/IP as the underlying
1591 transport protocol, and not NetBEUI. For details, read
1592 <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
1593 available from <http://www.tldp.org/docs.html#howto>.
1595 Note: if you just want your box to act as an SMB *server* and make
1596 files and printing services available to Windows clients (which need
1597 to have a TCP/IP stack), you don't need to say Y here; you can use
1598 the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
1599 for that.
1601 General information about how to connect Linux, Windows machines and
1602 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1604 To compile the SMB support as a module, choose M here: the module will
1605 be called smbfs. Most people say N, however.
1607 config SMB_NLS_DEFAULT
1608 bool "Use a default NLS"
1609 depends on SMB_FS
1610 help
1611 Enabling this will make smbfs use nls translations by default. You
1612 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
1613 settings and you need to give the default nls for the SMB server as
1614 CONFIG_SMB_NLS_REMOTE.
1616 The nls settings can be changed at mount time, if your smbmount
1617 supports that, using the codepage and iocharset parameters.
1619 smbmount from samba 2.2.0 or later supports this.
1621 config SMB_NLS_REMOTE
1622 string "Default Remote NLS Option"
1623 depends on SMB_NLS_DEFAULT
1624 default "cp437"
1625 help
1626 This setting allows you to specify a default value for which
1627 codepage the server uses. If this field is left blank no
1628 translations will be done by default. The local codepage/charset
1629 default to CONFIG_NLS_DEFAULT.
1631 The nls settings can be changed at mount time, if your smbmount
1632 supports that, using the codepage and iocharset parameters.
1634 smbmount from samba 2.2.0 or later supports this.
1636 config CIFS
1637 tristate "CIFS support (advanced network filesystem for Samba, Window and other CIFS compliant servers)"
1638 depends on INET
1639 select NLS
1640 help
1641 This is the client VFS module for the Common Internet File System
1642 (CIFS) protocol which is the successor to the Server Message Block
1643 (SMB) protocol, the native file sharing mechanism for most early
1644 PC operating systems. The CIFS protocol is fully supported by
1645 file servers such as Windows 2000 (including Windows 2003, NT 4
1646 and Windows XP) as well by Samba (which provides excellent CIFS
1647 server support for Linux and many other operating systems). Limited
1648 support for Windows ME and similar servers is provided as well.
1649 You must use the smbfs client filesystem to access older SMB servers
1650 such as OS/2 and DOS.
1652 The intent of the cifs module is to provide an advanced
1653 network file system client for mounting to CIFS compliant servers,
1654 including support for dfs (hierarchical name space), secure per-user
1655 session establishment, safe distributed caching (oplock), optional
1656 packet signing, Unicode and other internationalization improvements,
1657 and optional Winbind (nsswitch) integration. You do not need to enable
1658 cifs if running only a (Samba) server. It is possible to enable both
1659 smbfs and cifs (e.g. if you are using CIFS for accessing Windows 2003
1660 and Samba 3 servers, and smbfs for accessing old servers). If you need
1661 to mount to Samba or Windows from this machine, say Y.
1663 config CIFS_STATS
1664 bool "CIFS statistics"
1665 depends on CIFS
1666 help
1667 Enabling this option will cause statistics for each server share
1668 mounted by the cifs client to be displayed in /proc/fs/cifs/Stats
1670 config CIFS_STATS2
1671 bool "CIFS extended statistics"
1672 depends on CIFS_STATS
1673 help
1674 Enabling this option will allow more detailed statistics on SMB
1675 request timing to be displayed in /proc/fs/cifs/DebugData and also
1676 allow optional logging of slow responses to dmesg (depending on the
1677 value of /proc/fs/cifs/cifsFYI, see fs/cifs/README for more details).
1678 These additional statistics may have a minor effect on performance
1679 and memory utilization.
1681 Unless you are a developer or are doing network performance analysis
1682 or tuning, say N.
1684 config CIFS_XATTR
1685 bool "CIFS extended attributes"
1686 depends on CIFS
1687 help
1688 Extended attributes are name:value pairs associated with inodes by
1689 the kernel or by users (see the attr(5) manual page, or visit
1690 <http://acl.bestbits.at/> for details). CIFS maps the name of
1691 extended attributes beginning with the user namespace prefix
1692 to SMB/CIFS EAs. EAs are stored on Windows servers without the
1693 user namespace prefix, but their names are seen by Linux cifs clients
1694 prefaced by the user namespace prefix. The system namespace
1695 (used by some filesystems to store ACLs) is not supported at
1696 this time.
1698 If unsure, say N.
1700 config CIFS_POSIX
1701 bool "CIFS POSIX Extensions"
1702 depends on CIFS_XATTR
1703 help
1704 Enabling this option will cause the cifs client to attempt to
1705 negotiate a newer dialect with servers, such as Samba 3.0.5
1706 or later, that optionally can handle more POSIX like (rather
1707 than Windows like) file behavior. It also enables
1708 support for POSIX ACLs (getfacl and setfacl) to servers
1709 (such as Samba 3.10 and later) which can negotiate
1710 CIFS POSIX ACL support. If unsure, say N.
1712 config CIFS_EXPERIMENTAL
1713 bool "CIFS Experimental Features (EXPERIMENTAL)"
1714 depends on CIFS && EXPERIMENTAL
1715 help
1716 Enables cifs features under testing. These features are
1717 experimental and currently include support for writepages
1718 (multipage writebehind performance improvements) and directory
1719 change notification ie fcntl(F_DNOTIFY) as well as some security
1720 improvements. Some also depend on setting at runtime the
1721 pseudo-file /proc/fs/cifs/Experimental (which is disabled by
1722 default). See the file fs/cifs/README for more details.
1724 If unsure, say N.
1726 config CIFS_UPCALL
1727 bool "CIFS Kerberos/SPNEGO advanced session setup (EXPERIMENTAL)"
1728 depends on CIFS_EXPERIMENTAL
1729 select CONNECTOR
1730 help
1731 Enables an upcall mechanism for CIFS which will be used to contact
1732 userspace helper utilities to provide SPNEGO packaged Kerberos
1733 tickets which are needed to mount to certain secure servers
1734 (for which more secure Kerberos authentication is required). If
1735 unsure, say N.
1737 config NCP_FS
1738 tristate "NCP file system support (to mount NetWare volumes)"
1739 depends on IPX!=n || INET
1740 help
1741 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
1742 used by Novell NetWare clients to talk to file servers. It is to
1743 IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
1744 to mount NetWare file server volumes and to access them just like
1745 any other Unix directory. For details, please read the file
1746 <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
1747 the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
1749 You do not have to say Y here if you want your Linux box to act as a
1750 file *server* for Novell NetWare clients.
1752 General information about how to connect Linux, Windows machines and
1753 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1755 To compile this as a module, choose M here: the module will be called
1756 ncpfs. Say N unless you are connected to a Novell network.
1758 source "fs/ncpfs/Kconfig"
1760 config CODA_FS
1761 tristate "Coda file system support (advanced network fs)"
1762 depends on INET
1763 help
1764 Coda is an advanced network file system, similar to NFS in that it
1765 enables you to mount file systems of a remote server and access them
1766 with regular Unix commands as if they were sitting on your hard
1767 disk. Coda has several advantages over NFS: support for
1768 disconnected operation (e.g. for laptops), read/write server
1769 replication, security model for authentication and encryption,
1770 persistent client caches and write back caching.
1772 If you say Y here, your Linux box will be able to act as a Coda
1773 *client*. You will need user level code as well, both for the
1774 client and server. Servers are currently user level, i.e. they need
1775 no kernel support. Please read
1776 <file:Documentation/filesystems/coda.txt> and check out the Coda
1777 home page <http://www.coda.cs.cmu.edu/>.
1779 To compile the coda client support as a module, choose M here: the
1780 module will be called coda.
1782 config CODA_FS_OLD_API
1783 bool "Use 96-bit Coda file identifiers"
1784 depends on CODA_FS
1785 help
1786 A new kernel-userspace API had to be introduced for Coda v6.0
1787 to support larger 128-bit file identifiers as needed by the
1788 new realms implementation.
1790 However this new API is not backward compatible with older
1791 clients. If you really need to run the old Coda userspace
1792 cache manager then say Y.
1794 For most cases you probably want to say N.
1796 config AFS_FS
1797 # for fs/nls/Config.in
1798 tristate "Andrew File System support (AFS) (Experimental)"
1799 depends on INET && EXPERIMENTAL
1800 select RXRPC
1801 help
1802 If you say Y here, you will get an experimental Andrew File System
1803 driver. It currently only supports unsecured read-only AFS access.
1805 See <file:Documentation/filesystems/afs.txt> for more intormation.
1807 If unsure, say N.
1809 config RXRPC
1810 tristate
1812 config 9P_FS
1813 tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
1814 depends on INET && EXPERIMENTAL
1815 help
1816 If you say Y here, you will get experimental support for
1817 Plan 9 resource sharing via the 9P2000 protocol.
1819 See <http://v9fs.sf.net> for more information.
1821 If unsure, say N.
1823 endmenu
1825 menu "Partition Types"
1827 source "fs/partitions/Kconfig"
1829 endmenu
1831 source "fs/nls/Kconfig"
1833 endmenu