]> git.proxmox.com Git - mirror_ubuntu-zesty-kernel.git/blob - fs/Kconfig
[PATCH] kdump: enable CONFIG_PROC_VMCORE by default
[mirror_ubuntu-zesty-kernel.git] / fs / Kconfig
1 #
2 # File system configuration
3 #
4
5 menu "File systems"
6
7 config EXT2_FS
8 tristate "Second extended fs support"
9 help
10 Ext2 is a standard Linux file system for hard disks.
11
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.
16
17 If unsure, say Y.
18
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).
26
27 If unsure, say N.
28
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.
36
37 To learn more about Access Control Lists, visit the Posix ACLs for
38 Linux website <http://acl.bestbits.at/>.
39
40 If you don't know what Access Control Lists are, say N
41
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.
50
51 If you are not using a security module that requires using
52 extended attributes for file security labels, say N.
53
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.
61
62 If you do not use a block device that is capable of using this,
63 or if unsure, say N.
64
65 config FS_XIP
66 # execute in place
67 bool
68 depends on EXT2_FS_XIP
69 default y
70
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.
78
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.
84
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.
90
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/>).
97
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.
102
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).
111
112 If unsure, say N.
113
114 You need this for POSIX ACL support on ext3.
115
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.
123
124 To learn more about Access Control Lists, visit the Posix ACLs for
125 Linux website <http://acl.bestbits.at/>.
126
127 If you don't know what Access Control Lists are, say N
128
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.
137
138 If you are not using a security module that requires using
139 extended attributes for file security labels, say N.
140
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.
148
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.
152
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.
156
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.
166
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".
172
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
179
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.
185
186 Balanced trees are more efficient than traditional file system
187 architectural foundations.
188
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.
192
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.''
198
199 Read <http://www.namesys.com/> to learn more about reiserfs.
200
201 Sponsored by Threshold Networks, Emusic.com, and Bigstorage.com.
202
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.
205
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.
219
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.
230
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).
238
239 If unsure, say N.
240
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.
248
249 To learn more about Access Control Lists, visit the Posix ACLs for
250 Linux website <http://acl.bestbits.at/>.
251
252 If you don't know what Access Control Lists are, say N
253
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.
262
263 If you are not using a security module that requires using
264 extended attributes for file security labels, say N.
265
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>.
272
273 If you do not intend to use the JFS filesystem, say N.
274
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.
282
283 To learn more about Access Control Lists, visit the Posix ACLs for
284 Linux website <http://acl.bestbits.at/>.
285
286 If you don't know what Access Control Lists are, say N
287
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.
296
297 If you are not using a security module that requires using
298 extended attributes for file security labels, say N.
299
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.
308
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.
315
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
324
325 source "fs/xfs/Kconfig"
326
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.
339
340 You'll want to install the ocfs2-tools package in order to at least
341 get "mount.ocfs2".
342
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/
346
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)
358
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.
370
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.
375
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.
383
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.
388
389 If you don't know whether you need it, then you don't need it:
390 answer N.
391
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.
403
404 For more information, see Documentation/filesystems/inotify.txt
405
406 If unsure, say Y.
407
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.
420
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.
428
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.
435
436 config QUOTACTL
437 bool
438 depends on XFS_QUOTA || QUOTA
439 default y
440
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.
449
450 Because of this, if unsure, say Y.
451
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.
459
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.
463
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.
467
468 To compile this support as a module, choose M here: the module will be
469 called autofs.
470
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.
473
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.
481
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.
485
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.
489
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.
494
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.
500
501 There's also companion library: libfuse. This library along with
502 utilities is available from the FUSE homepage:
503 <http://fuse.sourceforge.net/>
504
505 See <file:Documentation/filesystems/fuse.txt> for more information.
506 See <file:Documentation/Changes> for needed library/utility version.
507
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.
510
511 menu "CD-ROM/DVD Filesystems"
512
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.
525
526 To compile this file system support as a module, choose M here: the
527 module will be called isofs.
528
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.
540
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.
552
553 config ZISOFS_FS
554 # for fs/nls/Config.in
555 tristate
556 depends on ZISOFS
557 default ISO9660_FS
558
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>.
566
567 To compile this file system support as a module, choose M here: the
568 module will be called udf.
569
570 If unsure, say N.
571
572 config UDF_NLS
573 bool
574 default y
575 depends on (UDF_FS=m && NLS) || (UDF_FS=y && NLS=y)
576
577 endmenu
578
579 menu "DOS/FAT/NT Filesystems"
580
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.
591
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.
596
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.
601
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").
606
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.
610
611 The FAT support will enlarge your kernel by about 37 KB. If unsure,
612 say Y.
613
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.
618
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.
633
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.
638
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.
643
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.
652
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.
657
658 To compile this as a module, choose M here: the module will be called
659 vfat.
660
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.
669
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.
682
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.
688
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.
692
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.
696
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.
701
702 For more information see <file:Documentation/filesystems/ntfs.txt>
703 and <http://linux-ntfs.sourceforge.net/>.
704
705 To compile this file system support as a module, choose M here: the
706 module will be called ntfs.
707
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.
710
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.
725
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.
729
730 When reporting bugs, please try to have available a full dump of
731 debugging messages while the misbehaviour was occurring.
732
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.
738
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.
744
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.
748
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.
753
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/>
759
760 It is perfectly safe to say N here.
761
762 endmenu
763
764 menu "Pseudo filesystems"
765
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.
774
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.
782
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.
787
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").
791
792 This option will enlarge your kernel by about 67 KB. Several
793 programs depend on this, so everyone should say Y here.
794
795 config PROC_KCORE
796 bool "/proc/kcore support" if !ARM
797 depends on PROC_FS && MMU
798
799 config PROC_VMCORE
800 bool "/proc/vmcore support (EXPERIMENTAL)"
801 depends on PROC_FS && EXPERIMENTAL && CRASH_DUMP
802 default y
803 help
804 Exports the dump image of crashed kernel in ELF format.
805
806 config SYSFS
807 bool "sysfs file system support" if EMBEDDED
808 default y
809 help
810 The sysfs filesystem is a virtual filesystem that the kernel uses to
811 export internal kernel objects, their attributes, and their
812 relationships to one another.
813
814 Users can use sysfs to ascertain useful information about the running
815 kernel, such as the devices the kernel has discovered on each bus and
816 which driver each is bound to. sysfs can also be used to tune devices
817 and other kernel subsystems.
818
819 Some system agents rely on the information in sysfs to operate.
820 /sbin/hotplug uses device and object attributes in sysfs to assist in
821 delegating policy decisions, like persistantly naming devices.
822
823 sysfs is currently used by the block subsystem to mount the root
824 partition. If sysfs is disabled you must specify the boot device on
825 the kernel boot command line via its major and minor numbers. For
826 example, "root=03:01" for /dev/hda1.
827
828 Designers of embedded systems may wish to say N here to conserve space.
829
830 config TMPFS
831 bool "Virtual memory file system support (former shm fs)"
832 help
833 Tmpfs is a file system which keeps all files in virtual memory.
834
835 Everything in tmpfs is temporary in the sense that no files will be
836 created on your hard drive. The files live in memory and swap
837 space. If you unmount a tmpfs instance, everything stored therein is
838 lost.
839
840 See <file:Documentation/filesystems/tmpfs.txt> for details.
841
842 config HUGETLBFS
843 bool "HugeTLB file system support"
844 depends X86 || IA64 || PPC64 || SPARC64 || SUPERH || BROKEN
845
846 config HUGETLB_PAGE
847 def_bool HUGETLBFS
848
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.
855
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.
859
860 To compile this as a module, choose M here: the module will be called
861 ramfs.
862
863 config CONFIGFS_FS
864 tristate "Userspace-driven configuration filesystem (EXPERIMENTAL)"
865 depends on SYSFS && EXPERIMENTAL
866 help
867 configfs is a ram-based filesystem that provides the converse
868 of sysfs's functionality. Where sysfs is a filesystem-based
869 view of kernel objects, configfs is a filesystem-based manager
870 of kernel objects, or config_items.
871
872 Both sysfs and configfs can and should exist together on the
873 same system. One is not a replacement for the other.
874
875 endmenu
876
877 menu "Miscellaneous filesystems"
878
879 config ADFS_FS
880 tristate "ADFS file system support (EXPERIMENTAL)"
881 depends on EXPERIMENTAL
882 help
883 The Acorn Disc Filing System is the standard file system of the
884 RiscOS operating system which runs on Acorn's ARM-based Risc PC
885 systems and the Acorn Archimedes range of machines. If you say Y
886 here, Linux will be able to read from ADFS partitions on hard drives
887 and from ADFS-formatted floppy discs. If you also want to be able to
888 write to those devices, say Y to "ADFS write support" below.
889
890 The ADFS partition should be the first partition (i.e.,
891 /dev/[hs]d?1) on each of your drives. Please read the file
892 <file:Documentation/filesystems/adfs.txt> for further details.
893
894 To compile this code as a module, choose M here: the module will be
895 called adfs.
896
897 If unsure, say N.
898
899 config ADFS_FS_RW
900 bool "ADFS write support (DANGEROUS)"
901 depends on ADFS_FS
902 help
903 If you say Y here, you will be able to write to ADFS partitions on
904 hard drives and ADFS-formatted floppy disks. This is experimental
905 codes, so if you're unsure, say N.
906
907 config AFFS_FS
908 tristate "Amiga FFS file system support (EXPERIMENTAL)"
909 depends on EXPERIMENTAL
910 help
911 The Fast File System (FFS) is the common file system used on hard
912 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
913 if you want to be able to read and write files from and to an Amiga
914 FFS partition on your hard drive. Amiga floppies however cannot be
915 read with this driver due to an incompatibility of the floppy
916 controller used in an Amiga and the standard floppy controller in
917 PCs and workstations. Read <file:Documentation/filesystems/affs.txt>
918 and <file:fs/affs/Changes>.
919
920 With this driver you can also mount disk files used by Bernd
921 Schmidt's Un*X Amiga Emulator
922 (<http://www.freiburg.linux.de/~uae/>).
923 If you want to do this, you will also need to say Y or M to "Loop
924 device support", above.
925
926 To compile this file system support as a module, choose M here: the
927 module will be called affs. If unsure, say N.
928
929 config HFS_FS
930 tristate "Apple Macintosh file system support (EXPERIMENTAL)"
931 depends on EXPERIMENTAL
932 select NLS
933 help
934 If you say Y here, you will be able to mount Macintosh-formatted
935 floppy disks and hard drive partitions with full read-write access.
936 Please read <file:fs/hfs/HFS.txt> to learn about the available mount
937 options.
938
939 To compile this file system support as a module, choose M here: the
940 module will be called hfs.
941
942 config HFSPLUS_FS
943 tristate "Apple Extended HFS file system support"
944 select NLS
945 select NLS_UTF8
946 help
947 If you say Y here, you will be able to mount extended format
948 Macintosh-formatted hard drive partitions with full read-write access.
949
950 This file system is often called HFS+ and was introduced with
951 MacOS 8. It includes all Mac specific filesystem data such as
952 data forks and creator codes, but it also has several UNIX
953 style features such as file ownership and permissions.
954
955 config BEFS_FS
956 tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)"
957 depends on EXPERIMENTAL
958 select NLS
959 help
960 The BeOS File System (BeFS) is the native file system of Be, Inc's
961 BeOS. Notable features include support for arbitrary attributes
962 on files and directories, and database-like indeces on selected
963 attributes. (Also note that this driver doesn't make those features
964 available at this time). It is a 64 bit filesystem, so it supports
965 extremly large volumes and files.
966
967 If you use this filesystem, you should also say Y to at least one
968 of the NLS (native language support) options below.
969
970 If you don't know what this is about, say N.
971
972 To compile this as a module, choose M here: the module will be
973 called befs.
974
975 config BEFS_DEBUG
976 bool "Debug BeFS"
977 depends on BEFS_FS
978 help
979 If you say Y here, you can use the 'debug' mount option to enable
980 debugging output from the driver.
981
982 config BFS_FS
983 tristate "BFS file system support (EXPERIMENTAL)"
984 depends on EXPERIMENTAL
985 help
986 Boot File System (BFS) is a file system used under SCO UnixWare to
987 allow the bootloader access to the kernel image and other important
988 files during the boot process. It is usually mounted under /stand
989 and corresponds to the slice marked as "STAND" in the UnixWare
990 partition. You should say Y if you want to read or write the files
991 on your /stand slice from within Linux. You then also need to say Y
992 to "UnixWare slices support", below. More information about the BFS
993 file system is contained in the file
994 <file:Documentation/filesystems/bfs.txt>.
995
996 If you don't know what this is about, say N.
997
998 To compile this as a module, choose M here: the module will be called
999 bfs. Note that the file system of your root partition (the one
1000 containing the directory /) cannot be compiled as a module.
1001
1002
1003
1004 config EFS_FS
1005 tristate "EFS file system support (read only) (EXPERIMENTAL)"
1006 depends on EXPERIMENTAL
1007 help
1008 EFS is an older file system used for non-ISO9660 CD-ROMs and hard
1009 disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
1010 uses the XFS file system for hard disk partitions however).
1011
1012 This implementation only offers read-only access. If you don't know
1013 what all this is about, it's safe to say N. For more information
1014 about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
1015
1016 To compile the EFS file system support as a module, choose M here: the
1017 module will be called efs.
1018
1019 config JFFS_FS
1020 tristate "Journalling Flash File System (JFFS) support"
1021 depends on MTD
1022 help
1023 JFFS is the Journaling Flash File System developed by Axis
1024 Communications in Sweden, aimed at providing a crash/powerdown-safe
1025 file system for disk-less embedded devices. Further information is
1026 available at (<http://developer.axis.com/software/jffs/>).
1027
1028 config JFFS_FS_VERBOSE
1029 int "JFFS debugging verbosity (0 = quiet, 3 = noisy)"
1030 depends on JFFS_FS
1031 default "0"
1032 help
1033 Determines the verbosity level of the JFFS debugging messages.
1034
1035 config JFFS_PROC_FS
1036 bool "JFFS stats available in /proc filesystem"
1037 depends on JFFS_FS && PROC_FS
1038 help
1039 Enabling this option will cause statistics from mounted JFFS file systems
1040 to be made available to the user in the /proc/fs/jffs/ directory.
1041
1042 config JFFS2_FS
1043 tristate "Journalling Flash File System v2 (JFFS2) support"
1044 select CRC32
1045 depends on MTD
1046 help
1047 JFFS2 is the second generation of the Journalling Flash File System
1048 for use on diskless embedded devices. It provides improved wear
1049 levelling, compression and support for hard links. You cannot use
1050 this on normal block devices, only on 'MTD' devices.
1051
1052 Further information on the design and implementation of JFFS2 is
1053 available at <http://sources.redhat.com/jffs2/>.
1054
1055 config JFFS2_FS_DEBUG
1056 int "JFFS2 debugging verbosity (0 = quiet, 2 = noisy)"
1057 depends on JFFS2_FS
1058 default "0"
1059 help
1060 This controls the amount of debugging messages produced by the JFFS2
1061 code. Set it to zero for use in production systems. For evaluation,
1062 testing and debugging, it's advisable to set it to one. This will
1063 enable a few assertions and will print debugging messages at the
1064 KERN_DEBUG loglevel, where they won't normally be visible. Level 2
1065 is unlikely to be useful - it enables extra debugging in certain
1066 areas which at one point needed debugging, but when the bugs were
1067 located and fixed, the detailed messages were relegated to level 2.
1068
1069 If reporting bugs, please try to have available a full dump of the
1070 messages at debug level 1 while the misbehaviour was occurring.
1071
1072 config JFFS2_FS_WRITEBUFFER
1073 bool "JFFS2 write-buffering support"
1074 depends on JFFS2_FS
1075 default y
1076 help
1077 This enables the write-buffering support in JFFS2.
1078
1079 This functionality is required to support JFFS2 on the following
1080 types of flash devices:
1081 - NAND flash
1082 - NOR flash with transparent ECC
1083 - DataFlash
1084
1085 config JFFS2_SUMMARY
1086 bool "JFFS2 summary support (EXPERIMENTAL)"
1087 depends on JFFS2_FS && EXPERIMENTAL
1088 default n
1089 help
1090 This feature makes it possible to use summary information
1091 for faster filesystem mount.
1092
1093 The summary information can be inserted into a filesystem image
1094 by the utility 'sumtool'.
1095
1096 If unsure, say 'N'.
1097
1098 config JFFS2_COMPRESSION_OPTIONS
1099 bool "Advanced compression options for JFFS2"
1100 depends on JFFS2_FS
1101 default n
1102 help
1103 Enabling this option allows you to explicitly choose which
1104 compression modules, if any, are enabled in JFFS2. Removing
1105 compressors and mean you cannot read existing file systems,
1106 and enabling experimental compressors can mean that you
1107 write a file system which cannot be read by a standard kernel.
1108
1109 If unsure, you should _definitely_ say 'N'.
1110
1111 config JFFS2_ZLIB
1112 bool "JFFS2 ZLIB compression support" if JFFS2_COMPRESSION_OPTIONS
1113 select ZLIB_INFLATE
1114 select ZLIB_DEFLATE
1115 depends on JFFS2_FS
1116 default y
1117 help
1118 Zlib is designed to be a free, general-purpose, legally unencumbered,
1119 lossless data-compression library for use on virtually any computer
1120 hardware and operating system. See <http://www.gzip.org/zlib/> for
1121 further information.
1122
1123 Say 'Y' if unsure.
1124
1125 config JFFS2_RTIME
1126 bool "JFFS2 RTIME compression support" if JFFS2_COMPRESSION_OPTIONS
1127 depends on JFFS2_FS
1128 default y
1129 help
1130 Rtime does manage to recompress already-compressed data. Say 'Y' if unsure.
1131
1132 config JFFS2_RUBIN
1133 bool "JFFS2 RUBIN compression support" if JFFS2_COMPRESSION_OPTIONS
1134 depends on JFFS2_FS
1135 default n
1136 help
1137 RUBINMIPS and DYNRUBIN compressors. Say 'N' if unsure.
1138
1139 choice
1140 prompt "JFFS2 default compression mode" if JFFS2_COMPRESSION_OPTIONS
1141 default JFFS2_CMODE_PRIORITY
1142 depends on JFFS2_FS
1143 help
1144 You can set here the default compression mode of JFFS2 from
1145 the available compression modes. Don't touch if unsure.
1146
1147 config JFFS2_CMODE_NONE
1148 bool "no compression"
1149 help
1150 Uses no compression.
1151
1152 config JFFS2_CMODE_PRIORITY
1153 bool "priority"
1154 help
1155 Tries the compressors in a predefinied order and chooses the first
1156 successful one.
1157
1158 config JFFS2_CMODE_SIZE
1159 bool "size (EXPERIMENTAL)"
1160 help
1161 Tries all compressors and chooses the one which has the smallest
1162 result.
1163
1164 endchoice
1165
1166 config CRAMFS
1167 tristate "Compressed ROM file system support (cramfs)"
1168 select ZLIB_INFLATE
1169 help
1170 Saying Y here includes support for CramFs (Compressed ROM File
1171 System). CramFs is designed to be a simple, small, and compressed
1172 file system for ROM based embedded systems. CramFs is read-only,
1173 limited to 256MB file systems (with 16MB files), and doesn't support
1174 16/32 bits uid/gid, hard links and timestamps.
1175
1176 See <file:Documentation/filesystems/cramfs.txt> and
1177 <file:fs/cramfs/README> for further information.
1178
1179 To compile this as a module, choose M here: the module will be called
1180 cramfs. Note that the root file system (the one containing the
1181 directory /) cannot be compiled as a module.
1182
1183 If unsure, say N.
1184
1185 config VXFS_FS
1186 tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
1187 help
1188 FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
1189 file system format. VERITAS VxFS(TM) is the standard file system
1190 of SCO UnixWare (and possibly others) and optionally available
1191 for Sunsoft Solaris, HP-UX and many other operating systems.
1192 Currently only readonly access is supported.
1193
1194 NOTE: the file system type as used by mount(1), mount(2) and
1195 fstab(5) is 'vxfs' as it describes the file system format, not
1196 the actual driver.
1197
1198 To compile this as a module, choose M here: the module will be
1199 called freevxfs. If unsure, say N.
1200
1201
1202 config HPFS_FS
1203 tristate "OS/2 HPFS file system support"
1204 help
1205 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
1206 is the file system used for organizing files on OS/2 hard disk
1207 partitions. Say Y if you want to be able to read files from and
1208 write files to an OS/2 HPFS partition on your hard drive. OS/2
1209 floppies however are in regular MSDOS format, so you don't need this
1210 option in order to be able to read them. Read
1211 <file:Documentation/filesystems/hpfs.txt>.
1212
1213 To compile this file system support as a module, choose M here: the
1214 module will be called hpfs. If unsure, say N.
1215
1216
1217
1218 config QNX4FS_FS
1219 tristate "QNX4 file system support (read only)"
1220 help
1221 This is the file system used by the real-time operating systems
1222 QNX 4 and QNX 6 (the latter is also called QNX RTP).
1223 Further information is available at <http://www.qnx.com/>.
1224 Say Y if you intend to mount QNX hard disks or floppies.
1225 Unless you say Y to "QNX4FS read-write support" below, you will
1226 only be able to read these file systems.
1227
1228 To compile this file system support as a module, choose M here: the
1229 module will be called qnx4.
1230
1231 If you don't know whether you need it, then you don't need it:
1232 answer N.
1233
1234 config QNX4FS_RW
1235 bool "QNX4FS write support (DANGEROUS)"
1236 depends on QNX4FS_FS && EXPERIMENTAL && BROKEN
1237 help
1238 Say Y if you want to test write support for QNX4 file systems.
1239
1240 It's currently broken, so for now:
1241 answer N.
1242
1243
1244
1245 config SYSV_FS
1246 tristate "System V/Xenix/V7/Coherent file system support"
1247 help
1248 SCO, Xenix and Coherent are commercial Unix systems for Intel
1249 machines, and Version 7 was used on the DEC PDP-11. Saying Y
1250 here would allow you to read from their floppies and hard disk
1251 partitions.
1252
1253 If you have floppies or hard disk partitions like that, it is likely
1254 that they contain binaries from those other Unix systems; in order
1255 to run these binaries, you will want to install linux-abi which is a
1256 a set of kernel modules that lets you run SCO, Xenix, Wyse,
1257 UnixWare, Dell Unix and System V programs under Linux. It is
1258 available via FTP (user: ftp) from
1259 <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
1260 NOTE: that will work only for binaries from Intel-based systems;
1261 PDP ones will have to wait until somebody ports Linux to -11 ;-)
1262
1263 If you only intend to mount files from some other Unix over the
1264 network using NFS, you don't need the System V file system support
1265 (but you need NFS file system support obviously).
1266
1267 Note that this option is generally not needed for floppies, since a
1268 good portable way to transport files and directories between unixes
1269 (and even other operating systems) is given by the tar program ("man
1270 tar" or preferably "info tar"). Note also that this option has
1271 nothing whatsoever to do with the option "System V IPC". Read about
1272 the System V file system in
1273 <file:Documentation/filesystems/sysv-fs.txt>.
1274 Saying Y here will enlarge your kernel by about 27 KB.
1275
1276 To compile this as a module, choose M here: the module will be called
1277 sysv.
1278
1279 If you haven't heard about all of this before, it's safe to say N.
1280
1281
1282
1283 config UFS_FS
1284 tristate "UFS file system support (read only)"
1285 help
1286 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
1287 OpenBSD and NeXTstep) use a file system called UFS. Some System V
1288 Unixes can create and mount hard disk partitions and diskettes using
1289 this file system as well. Saying Y here will allow you to read from
1290 these partitions; if you also want to write to them, say Y to the
1291 experimental "UFS file system write support", below. Please read the
1292 file <file:Documentation/filesystems/ufs.txt> for more information.
1293
1294 The recently released UFS2 variant (used in FreeBSD 5.x) is
1295 READ-ONLY supported.
1296
1297 If you only intend to mount files from some other Unix over the
1298 network using NFS, you don't need the UFS file system support (but
1299 you need NFS file system support obviously).
1300
1301 Note that this option is generally not needed for floppies, since a
1302 good portable way to transport files and directories between unixes
1303 (and even other operating systems) is given by the tar program ("man
1304 tar" or preferably "info tar").
1305
1306 When accessing NeXTstep files, you may need to convert them from the
1307 NeXT character set to the Latin1 character set; use the program
1308 recode ("info recode") for this purpose.
1309
1310 To compile the UFS file system support as a module, choose M here: the
1311 module will be called ufs.
1312
1313 If you haven't heard about all of this before, it's safe to say N.
1314
1315 config UFS_FS_WRITE
1316 bool "UFS file system write support (DANGEROUS)"
1317 depends on UFS_FS && EXPERIMENTAL && BROKEN
1318 help
1319 Say Y here if you want to try writing to UFS partitions. This is
1320 experimental, so you should back up your UFS partitions beforehand.
1321
1322 endmenu
1323
1324 menu "Network File Systems"
1325 depends on NET
1326
1327 config NFS_FS
1328 tristate "NFS file system support"
1329 depends on INET
1330 select LOCKD
1331 select SUNRPC
1332 select NFS_ACL_SUPPORT if NFS_V3_ACL
1333 help
1334 If you are connected to some other (usually local) Unix computer
1335 (using SLIP, PLIP, PPP or Ethernet) and want to mount files residing
1336 on that computer (the NFS server) using the Network File Sharing
1337 protocol, say Y. "Mounting files" means that the client can access
1338 the files with usual UNIX commands as if they were sitting on the
1339 client's hard disk. For this to work, the server must run the
1340 programs nfsd and mountd (but does not need to have NFS file system
1341 support enabled in its kernel). NFS is explained in the Network
1342 Administrator's Guide, available from
1343 <http://www.tldp.org/docs.html#guide>, on its man page: "man
1344 nfs", and in the NFS-HOWTO.
1345
1346 A superior but less widely used alternative to NFS is provided by
1347 the Coda file system; see "Coda file system support" below.
1348
1349 If you say Y here, you should have said Y to TCP/IP networking also.
1350 This option would enlarge your kernel by about 27 KB.
1351
1352 To compile this file system support as a module, choose M here: the
1353 module will be called nfs.
1354
1355 If you are configuring a diskless machine which will mount its root
1356 file system over NFS at boot time, say Y here and to "Kernel
1357 level IP autoconfiguration" above and to "Root file system on NFS"
1358 below. You cannot compile this driver as a module in this case.
1359 There are two packages designed for booting diskless machines over
1360 the net: netboot, available from
1361 <http://ftp1.sourceforge.net/netboot/>, and Etherboot,
1362 available from <http://ftp1.sourceforge.net/etherboot/>.
1363
1364 If you don't know what all this is about, say N.
1365
1366 config NFS_V3
1367 bool "Provide NFSv3 client support"
1368 depends on NFS_FS
1369 help
1370 Say Y here if you want your NFS client to be able to speak version
1371 3 of the NFS protocol.
1372
1373 If unsure, say Y.
1374
1375 config NFS_V3_ACL
1376 bool "Provide client support for the NFSv3 ACL protocol extension"
1377 depends on NFS_V3
1378 help
1379 Implement the NFSv3 ACL protocol extension for manipulating POSIX
1380 Access Control Lists. The server should also be compiled with
1381 the NFSv3 ACL protocol extension; see the CONFIG_NFSD_V3_ACL option.
1382
1383 If unsure, say N.
1384
1385 config NFS_V4
1386 bool "Provide NFSv4 client support (EXPERIMENTAL)"
1387 depends on NFS_FS && EXPERIMENTAL
1388 select RPCSEC_GSS_KRB5
1389 help
1390 Say Y here if you want your NFS client to be able to speak the newer
1391 version 4 of the NFS protocol.
1392
1393 Note: Requires auxiliary userspace daemons which may be found on
1394 http://www.citi.umich.edu/projects/nfsv4/
1395
1396 If unsure, say N.
1397
1398 config NFS_DIRECTIO
1399 bool "Allow direct I/O on NFS files (EXPERIMENTAL)"
1400 depends on NFS_FS && EXPERIMENTAL
1401 help
1402 This option enables applications to perform uncached I/O on files
1403 in NFS file systems using the O_DIRECT open() flag. When O_DIRECT
1404 is set for a file, its data is not cached in the system's page
1405 cache. Data is moved to and from user-level application buffers
1406 directly. Unlike local disk-based file systems, NFS O_DIRECT has
1407 no alignment restrictions.
1408
1409 Unless your program is designed to use O_DIRECT properly, you are
1410 much better off allowing the NFS client to manage data caching for
1411 you. Misusing O_DIRECT can cause poor server performance or network
1412 storms. This kernel build option defaults OFF to avoid exposing
1413 system administrators unwittingly to a potentially hazardous
1414 feature.
1415
1416 For more details on NFS O_DIRECT, see fs/nfs/direct.c.
1417
1418 If unsure, say N. This reduces the size of the NFS client, and
1419 causes open() to return EINVAL if a file residing in NFS is
1420 opened with the O_DIRECT flag.
1421
1422 config NFSD
1423 tristate "NFS server support"
1424 depends on INET
1425 select LOCKD
1426 select SUNRPC
1427 select EXPORTFS
1428 select NFS_ACL_SUPPORT if NFSD_V3_ACL || NFSD_V2_ACL
1429 help
1430 If you want your Linux box to act as an NFS *server*, so that other
1431 computers on your local network which support NFS can access certain
1432 directories on your box transparently, you have two options: you can
1433 use the self-contained user space program nfsd, in which case you
1434 should say N here, or you can say Y and use the kernel based NFS
1435 server. The advantage of the kernel based solution is that it is
1436 faster.
1437
1438 In either case, you will need support software; the respective
1439 locations are given in the file <file:Documentation/Changes> in the
1440 NFS section.
1441
1442 If you say Y here, you will get support for version 2 of the NFS
1443 protocol (NFSv2). If you also want NFSv3, say Y to the next question
1444 as well.
1445
1446 Please read the NFS-HOWTO, available from
1447 <http://www.tldp.org/docs.html#howto>.
1448
1449 To compile the NFS server support as a module, choose M here: the
1450 module will be called nfsd. If unsure, say N.
1451
1452 config NFSD_V2_ACL
1453 bool
1454 depends on NFSD
1455
1456 config NFSD_V3
1457 bool "Provide NFSv3 server support"
1458 depends on NFSD
1459 help
1460 If you would like to include the NFSv3 server as well as the NFSv2
1461 server, say Y here. If unsure, say Y.
1462
1463 config NFSD_V3_ACL
1464 bool "Provide server support for the NFSv3 ACL protocol extension"
1465 depends on NFSD_V3
1466 select NFSD_V2_ACL
1467 help
1468 Implement the NFSv3 ACL protocol extension for manipulating POSIX
1469 Access Control Lists on exported file systems. NFS clients should
1470 be compiled with the NFSv3 ACL protocol extension; see the
1471 CONFIG_NFS_V3_ACL option. If unsure, say N.
1472
1473 config NFSD_V4
1474 bool "Provide NFSv4 server support (EXPERIMENTAL)"
1475 depends on NFSD_V3 && EXPERIMENTAL
1476 select NFSD_TCP
1477 select CRYPTO_MD5
1478 select CRYPTO
1479 select FS_POSIX_ACL
1480 help
1481 If you would like to include the NFSv4 server as well as the NFSv2
1482 and NFSv3 servers, say Y here. This feature is experimental, and
1483 should only be used if you are interested in helping to test NFSv4.
1484 If unsure, say N.
1485
1486 config NFSD_TCP
1487 bool "Provide NFS server over TCP support"
1488 depends on NFSD
1489 default y
1490 help
1491 If you want your NFS server to support TCP connections, say Y here.
1492 TCP connections usually perform better than the default UDP when
1493 the network is lossy or congested. If unsure, say Y.
1494
1495 config ROOT_NFS
1496 bool "Root file system on NFS"
1497 depends on NFS_FS=y && IP_PNP
1498 help
1499 If you want your Linux box to mount its whole root file system (the
1500 one containing the directory /) from some other computer over the
1501 net via NFS (presumably because your box doesn't have a hard disk),
1502 say Y. Read <file:Documentation/nfsroot.txt> for details. It is
1503 likely that in this case, you also want to say Y to "Kernel level IP
1504 autoconfiguration" so that your box can discover its network address
1505 at boot time.
1506
1507 Most people say N here.
1508
1509 config LOCKD
1510 tristate
1511
1512 config LOCKD_V4
1513 bool
1514 depends on NFSD_V3 || NFS_V3
1515 default y
1516
1517 config EXPORTFS
1518 tristate
1519
1520 config NFS_ACL_SUPPORT
1521 tristate
1522 select FS_POSIX_ACL
1523
1524 config NFS_COMMON
1525 bool
1526 depends on NFSD || NFS_FS
1527 default y
1528
1529 config SUNRPC
1530 tristate
1531
1532 config SUNRPC_GSS
1533 tristate
1534
1535 config RPCSEC_GSS_KRB5
1536 tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
1537 depends on SUNRPC && EXPERIMENTAL
1538 select SUNRPC_GSS
1539 select CRYPTO
1540 select CRYPTO_MD5
1541 select CRYPTO_DES
1542 help
1543 Provides for secure RPC calls by means of a gss-api
1544 mechanism based on Kerberos V5. This is required for
1545 NFSv4.
1546
1547 Note: Requires an auxiliary userspace daemon which may be found on
1548 http://www.citi.umich.edu/projects/nfsv4/
1549
1550 If unsure, say N.
1551
1552 config RPCSEC_GSS_SPKM3
1553 tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
1554 depends on SUNRPC && EXPERIMENTAL
1555 select SUNRPC_GSS
1556 select CRYPTO
1557 select CRYPTO_MD5
1558 select CRYPTO_DES
1559 select CRYPTO_CAST5
1560 help
1561 Provides for secure RPC calls by means of a gss-api
1562 mechanism based on the SPKM3 public-key mechanism.
1563
1564 Note: Requires an auxiliary userspace daemon which may be found on
1565 http://www.citi.umich.edu/projects/nfsv4/
1566
1567 If unsure, say N.
1568
1569 config SMB_FS
1570 tristate "SMB file system support (to mount Windows shares etc.)"
1571 depends on INET
1572 select NLS
1573 help
1574 SMB (Server Message Block) is the protocol Windows for Workgroups
1575 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
1576 files and printers over local networks. Saying Y here allows you to
1577 mount their file systems (often called "shares" in this context) and
1578 access them just like any other Unix directory. Currently, this
1579 works only if the Windows machines use TCP/IP as the underlying
1580 transport protocol, and not NetBEUI. For details, read
1581 <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
1582 available from <http://www.tldp.org/docs.html#howto>.
1583
1584 Note: if you just want your box to act as an SMB *server* and make
1585 files and printing services available to Windows clients (which need
1586 to have a TCP/IP stack), you don't need to say Y here; you can use
1587 the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
1588 for that.
1589
1590 General information about how to connect Linux, Windows machines and
1591 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1592
1593 To compile the SMB support as a module, choose M here: the module will
1594 be called smbfs. Most people say N, however.
1595
1596 config SMB_NLS_DEFAULT
1597 bool "Use a default NLS"
1598 depends on SMB_FS
1599 help
1600 Enabling this will make smbfs use nls translations by default. You
1601 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
1602 settings and you need to give the default nls for the SMB server as
1603 CONFIG_SMB_NLS_REMOTE.
1604
1605 The nls settings can be changed at mount time, if your smbmount
1606 supports that, using the codepage and iocharset parameters.
1607
1608 smbmount from samba 2.2.0 or later supports this.
1609
1610 config SMB_NLS_REMOTE
1611 string "Default Remote NLS Option"
1612 depends on SMB_NLS_DEFAULT
1613 default "cp437"
1614 help
1615 This setting allows you to specify a default value for which
1616 codepage the server uses. If this field is left blank no
1617 translations will be done by default. The local codepage/charset
1618 default to CONFIG_NLS_DEFAULT.
1619
1620 The nls settings can be changed at mount time, if your smbmount
1621 supports that, using the codepage and iocharset parameters.
1622
1623 smbmount from samba 2.2.0 or later supports this.
1624
1625 config CIFS
1626 tristate "CIFS support (advanced network filesystem for Samba, Window and other CIFS compliant servers)"
1627 depends on INET
1628 select NLS
1629 help
1630 This is the client VFS module for the Common Internet File System
1631 (CIFS) protocol which is the successor to the Server Message Block
1632 (SMB) protocol, the native file sharing mechanism for most early
1633 PC operating systems. The CIFS protocol is fully supported by
1634 file servers such as Windows 2000 (including Windows 2003, NT 4
1635 and Windows XP) as well by Samba (which provides excellent CIFS
1636 server support for Linux and many other operating systems). Limited
1637 support for Windows ME and similar servers is provided as well.
1638 You must use the smbfs client filesystem to access older SMB servers
1639 such as OS/2 and DOS.
1640
1641 The intent of the cifs module is to provide an advanced
1642 network file system client for mounting to CIFS compliant servers,
1643 including support for dfs (hierarchical name space), secure per-user
1644 session establishment, safe distributed caching (oplock), optional
1645 packet signing, Unicode and other internationalization improvements,
1646 and optional Winbind (nsswitch) integration. You do not need to enable
1647 cifs if running only a (Samba) server. It is possible to enable both
1648 smbfs and cifs (e.g. if you are using CIFS for accessing Windows 2003
1649 and Samba 3 servers, and smbfs for accessing old servers). If you need
1650 to mount to Samba or Windows from this machine, say Y.
1651
1652 config CIFS_STATS
1653 bool "CIFS statistics"
1654 depends on CIFS
1655 help
1656 Enabling this option will cause statistics for each server share
1657 mounted by the cifs client to be displayed in /proc/fs/cifs/Stats
1658
1659 config CIFS_STATS2
1660 bool "CIFS extended statistics"
1661 depends on CIFS_STATS
1662 help
1663 Enabling this option will allow more detailed statistics on SMB
1664 request timing to be displayed in /proc/fs/cifs/DebugData and also
1665 allow optional logging of slow responses to dmesg (depending on the
1666 value of /proc/fs/cifs/cifsFYI, see fs/cifs/README for more details).
1667 These additional statistics may have a minor effect on performance
1668 and memory utilization.
1669
1670 Unless you are a developer or are doing network performance analysis
1671 or tuning, say N.
1672
1673 config CIFS_XATTR
1674 bool "CIFS extended attributes"
1675 depends on CIFS
1676 help
1677 Extended attributes are name:value pairs associated with inodes by
1678 the kernel or by users (see the attr(5) manual page, or visit
1679 <http://acl.bestbits.at/> for details). CIFS maps the name of
1680 extended attributes beginning with the user namespace prefix
1681 to SMB/CIFS EAs. EAs are stored on Windows servers without the
1682 user namespace prefix, but their names are seen by Linux cifs clients
1683 prefaced by the user namespace prefix. The system namespace
1684 (used by some filesystems to store ACLs) is not supported at
1685 this time.
1686
1687 If unsure, say N.
1688
1689 config CIFS_POSIX
1690 bool "CIFS POSIX Extensions"
1691 depends on CIFS_XATTR
1692 help
1693 Enabling this option will cause the cifs client to attempt to
1694 negotiate a newer dialect with servers, such as Samba 3.0.5
1695 or later, that optionally can handle more POSIX like (rather
1696 than Windows like) file behavior. It also enables
1697 support for POSIX ACLs (getfacl and setfacl) to servers
1698 (such as Samba 3.10 and later) which can negotiate
1699 CIFS POSIX ACL support. If unsure, say N.
1700
1701 config CIFS_EXPERIMENTAL
1702 bool "CIFS Experimental Features (EXPERIMENTAL)"
1703 depends on CIFS && EXPERIMENTAL
1704 help
1705 Enables cifs features under testing. These features are
1706 experimental and currently include support for writepages
1707 (multipage writebehind performance improvements) and directory
1708 change notification ie fcntl(F_DNOTIFY) as well as some security
1709 improvements. Some also depend on setting at runtime the
1710 pseudo-file /proc/fs/cifs/Experimental (which is disabled by
1711 default). See the file fs/cifs/README for more details.
1712
1713 If unsure, say N.
1714
1715 config CIFS_UPCALL
1716 bool "CIFS Kerberos/SPNEGO advanced session setup (EXPERIMENTAL)"
1717 depends on CIFS_EXPERIMENTAL
1718 select CONNECTOR
1719 help
1720 Enables an upcall mechanism for CIFS which will be used to contact
1721 userspace helper utilities to provide SPNEGO packaged Kerberos
1722 tickets which are needed to mount to certain secure servers
1723 (for which more secure Kerberos authentication is required). If
1724 unsure, say N.
1725
1726 config NCP_FS
1727 tristate "NCP file system support (to mount NetWare volumes)"
1728 depends on IPX!=n || INET
1729 help
1730 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
1731 used by Novell NetWare clients to talk to file servers. It is to
1732 IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
1733 to mount NetWare file server volumes and to access them just like
1734 any other Unix directory. For details, please read the file
1735 <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
1736 the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
1737
1738 You do not have to say Y here if you want your Linux box to act as a
1739 file *server* for Novell NetWare clients.
1740
1741 General information about how to connect Linux, Windows machines and
1742 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1743
1744 To compile this as a module, choose M here: the module will be called
1745 ncpfs. Say N unless you are connected to a Novell network.
1746
1747 source "fs/ncpfs/Kconfig"
1748
1749 config CODA_FS
1750 tristate "Coda file system support (advanced network fs)"
1751 depends on INET
1752 help
1753 Coda is an advanced network file system, similar to NFS in that it
1754 enables you to mount file systems of a remote server and access them
1755 with regular Unix commands as if they were sitting on your hard
1756 disk. Coda has several advantages over NFS: support for
1757 disconnected operation (e.g. for laptops), read/write server
1758 replication, security model for authentication and encryption,
1759 persistent client caches and write back caching.
1760
1761 If you say Y here, your Linux box will be able to act as a Coda
1762 *client*. You will need user level code as well, both for the
1763 client and server. Servers are currently user level, i.e. they need
1764 no kernel support. Please read
1765 <file:Documentation/filesystems/coda.txt> and check out the Coda
1766 home page <http://www.coda.cs.cmu.edu/>.
1767
1768 To compile the coda client support as a module, choose M here: the
1769 module will be called coda.
1770
1771 config CODA_FS_OLD_API
1772 bool "Use 96-bit Coda file identifiers"
1773 depends on CODA_FS
1774 help
1775 A new kernel-userspace API had to be introduced for Coda v6.0
1776 to support larger 128-bit file identifiers as needed by the
1777 new realms implementation.
1778
1779 However this new API is not backward compatible with older
1780 clients. If you really need to run the old Coda userspace
1781 cache manager then say Y.
1782
1783 For most cases you probably want to say N.
1784
1785 config AFS_FS
1786 # for fs/nls/Config.in
1787 tristate "Andrew File System support (AFS) (Experimental)"
1788 depends on INET && EXPERIMENTAL
1789 select RXRPC
1790 help
1791 If you say Y here, you will get an experimental Andrew File System
1792 driver. It currently only supports unsecured read-only AFS access.
1793
1794 See <file:Documentation/filesystems/afs.txt> for more intormation.
1795
1796 If unsure, say N.
1797
1798 config RXRPC
1799 tristate
1800
1801 config 9P_FS
1802 tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
1803 depends on INET && EXPERIMENTAL
1804 help
1805 If you say Y here, you will get experimental support for
1806 Plan 9 resource sharing via the 9P2000 protocol.
1807
1808 See <http://v9fs.sf.net> for more information.
1809
1810 If unsure, say N.
1811
1812 endmenu
1813
1814 menu "Partition Types"
1815
1816 source "fs/partitions/Kconfig"
1817
1818 endmenu
1819
1820 source "fs/nls/Kconfig"
1821
1822 endmenu
1823