blob: 062177956239b1c25c6199579e9f72faecc21212 [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001#
2# File system configuration
3#
4
5menu "File systems"
6
7config 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
19config 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
29config EXT2_FS_POSIX_ACL
30 bool "Ext2 POSIX Access Control Lists"
31 depends on EXT2_FS_XATTR
32 help
33 Posix Access Control Lists (ACLs) support permissions for users and
34 groups beyond the owner/group/world scheme.
35
36 To learn more about Access Control Lists, visit the Posix ACLs for
37 Linux website <http://acl.bestbits.at/>.
38
39 If you don't know what Access Control Lists are, say N
40
41config EXT2_FS_SECURITY
42 bool "Ext2 Security Labels"
43 depends on EXT2_FS_XATTR
44 help
45 Security labels support alternative access control models
46 implemented by security modules like SELinux. This option
47 enables an extended attribute handler for file security
48 labels in the ext2 filesystem.
49
50 If you are not using a security module that requires using
51 extended attributes for file security labels, say N.
52
Carsten Otte6d791252005-06-23 22:05:26 -070053config EXT2_FS_XIP
54 bool "Ext2 execute in place support"
55 depends on EXT2_FS
56 help
57 Execute in place can be used on memory-backed block devices. If you
58 enable this option, you can select to mount block devices which are
59 capable of this feature without using the page cache.
60
61 If you do not use a block device that is capable of using this,
62 or if unsure, say N.
63
64config FS_XIP
65# execute in place
66 bool
67 depends on EXT2_FS_XIP
68 default y
69
Linus Torvalds1da177e2005-04-16 15:20:36 -070070config EXT3_FS
71 tristate "Ext3 journalling file system support"
72 help
73 This is the journaling version of the Second extended file system
74 (often called ext3), the de facto standard Linux file system
75 (method to organize files on a storage device) for hard disks.
76
77 The journaling code included in this driver means you do not have
78 to run e2fsck (file system checker) on your file systems after a
79 crash. The journal keeps track of any changes that were being made
80 at the time the system crashed, and can ensure that your file system
81 is consistent without the need for a lengthy check.
82
83 Other than adding the journal to the file system, the on-disk format
84 of ext3 is identical to ext2. It is possible to freely switch
85 between using the ext3 driver and the ext2 driver, as long as the
86 file system has been cleanly unmounted, or e2fsck is run on the file
87 system.
88
89 To add a journal on an existing ext2 file system or change the
90 behavior of ext3 file systems, you can use the tune2fs utility ("man
91 tune2fs"). To modify attributes of files and directories on ext3
92 file systems, use chattr ("man chattr"). You need to be using
93 e2fsprogs version 1.20 or later in order to create ext3 journals
94 (available at <http://sourceforge.net/projects/e2fsprogs/>).
95
96 To compile this file system support as a module, choose M here: the
97 module will be called ext3. Be aware however that the file system
98 of your root partition (the one containing the directory /) cannot
99 be compiled as a module, and so this may be dangerous.
100
101config EXT3_FS_XATTR
102 bool "Ext3 extended attributes"
103 depends on EXT3_FS
104 default y
105 help
106 Extended attributes are name:value pairs associated with inodes by
107 the kernel or by users (see the attr(5) manual page, or visit
108 <http://acl.bestbits.at/> for details).
109
110 If unsure, say N.
111
112 You need this for POSIX ACL support on ext3.
113
114config EXT3_FS_POSIX_ACL
115 bool "Ext3 POSIX Access Control Lists"
116 depends on EXT3_FS_XATTR
117 help
118 Posix Access Control Lists (ACLs) support permissions for users and
119 groups beyond the owner/group/world scheme.
120
121 To learn more about Access Control Lists, visit the Posix ACLs for
122 Linux website <http://acl.bestbits.at/>.
123
124 If you don't know what Access Control Lists are, say N
125
126config EXT3_FS_SECURITY
127 bool "Ext3 Security Labels"
128 depends on EXT3_FS_XATTR
129 help
130 Security labels support alternative access control models
131 implemented by security modules like SELinux. This option
132 enables an extended attribute handler for file security
133 labels in the ext3 filesystem.
134
135 If you are not using a security module that requires using
136 extended attributes for file security labels, say N.
137
138config JBD
139# CONFIG_JBD could be its own option (even modular), but until there are
140# other users than ext3, we will simply make it be the same as CONFIG_EXT3_FS
141# dep_tristate ' Journal Block Device support (JBD for ext3)' CONFIG_JBD $CONFIG_EXT3_FS
142 tristate
143 default EXT3_FS
144 help
145 This is a generic journaling layer for block devices. It is
146 currently used by the ext3 file system, but it could also be used to
147 add journal support to other file systems or block devices such as
148 RAID or LVM.
149
150 If you are using the ext3 file system, you need to say Y here. If
151 you are not using ext3 then you will probably 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 into the kernel, you cannot
155 compile this code as a module.
156
157config 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
173config 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
180config 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
206config 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
220config 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
231config 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
241config REISERFS_FS_POSIX_ACL
242 bool "ReiserFS POSIX Access Control Lists"
243 depends on REISERFS_FS_XATTR
244 help
245 Posix Access Control Lists (ACLs) support permissions for users and
246 groups beyond the owner/group/world scheme.
247
248 To learn more about Access Control Lists, visit the Posix ACLs for
249 Linux website <http://acl.bestbits.at/>.
250
251 If you don't know what Access Control Lists are, say N
252
253config REISERFS_FS_SECURITY
254 bool "ReiserFS Security Labels"
255 depends on REISERFS_FS_XATTR
256 help
257 Security labels support alternative access control models
258 implemented by security modules like SELinux. This option
259 enables an extended attribute handler for file security
260 labels in the ReiserFS filesystem.
261
262 If you are not using a security module that requires using
263 extended attributes for file security labels, say N.
264
265config JFS_FS
266 tristate "JFS filesystem support"
267 select NLS
268 help
269 This is a port of IBM's Journaled Filesystem . More information is
270 available in the file <file:Documentation/filesystems/jfs.txt>.
271
272 If you do not intend to use the JFS filesystem, say N.
273
274config JFS_POSIX_ACL
275 bool "JFS POSIX Access Control Lists"
276 depends on JFS_FS
277 help
278 Posix Access Control Lists (ACLs) support permissions for users and
279 groups beyond the owner/group/world scheme.
280
281 To learn more about Access Control Lists, visit the Posix ACLs for
282 Linux website <http://acl.bestbits.at/>.
283
284 If you don't know what Access Control Lists are, say N
285
286config JFS_SECURITY
287 bool "JFS Security Labels"
288 depends on JFS_FS
289 help
290 Security labels support alternative access control models
291 implemented by security modules like SELinux. This option
292 enables an extended attribute handler for file security
293 labels in the jfs filesystem.
294
295 If you are not using a security module that requires using
296 extended attributes for file security labels, say N.
297
298config JFS_DEBUG
299 bool "JFS debugging"
300 depends on JFS_FS
301 help
302 If you are experiencing any problems with the JFS filesystem, say
303 Y here. This will result in additional debugging messages to be
304 written to the system log. Under normal circumstances, this
305 results in very little overhead.
306
307config JFS_STATISTICS
308 bool "JFS statistics"
309 depends on JFS_FS
310 help
311 Enabling this option will cause statistics from the JFS file system
312 to be made available to the user in the /proc/fs/jfs/ directory.
313
314config FS_POSIX_ACL
315# Posix ACL utility routines (for now, only ext2/ext3/jfs/reiserfs)
316#
317# NOTE: you can implement Posix ACLs without these helpers (XFS does).
318# Never use this symbol for ifdefs.
319#
320 bool
321 depends on EXT2_FS_POSIX_ACL || EXT3_FS_POSIX_ACL || JFS_POSIX_ACL || REISERFS_FS_POSIX_ACL || NFSD_V4
322 default y
323
324source "fs/xfs/Kconfig"
325
326config MINIX_FS
327 tristate "Minix fs support"
328 help
329 Minix is a simple operating system used in many classes about OS's.
330 The minix file system (method to organize files on a hard disk
331 partition or a floppy disk) was the original file system for Linux,
332 but has been superseded by the second extended file system ext2fs.
333 You don't want to use the minix file system on your hard disk
334 because of certain built-in restrictions, but it is sometimes found
335 on older Linux floppy disks. This option will enlarge your kernel
336 by about 28 KB. If unsure, say N.
337
338 To compile this file system support as a module, choose M here: the
339 module will be called minix. Note that the file system of your root
340 partition (the one containing the directory /) cannot be compiled as
341 a module.
342
343config ROMFS_FS
344 tristate "ROM file system support"
345 ---help---
346 This is a very small read-only file system mainly intended for
347 initial ram disks of installation disks, but it could be used for
348 other read-only media as well. Read
349 <file:Documentation/filesystems/romfs.txt> for details.
350
351 To compile this file system support as a module, choose M here: the
352 module will be called romfs. Note that the file system of your
353 root partition (the one containing the directory /) cannot be a
354 module.
355
356 If you don't know whether you need it, then you don't need it:
357 answer N.
358
359config QUOTA
360 bool "Quota support"
361 help
362 If you say Y here, you will be able to set per user limits for disk
363 usage (also called disk quotas). Currently, it works for the
364 ext2, ext3, and reiserfs file system. ext3 also supports journalled
365 quotas for which you don't need to run quotacheck(8) after an unclean
366 shutdown. You need additional software in order to use quota support
367 (you can download sources from
368 <http://www.sf.net/projects/linuxquota/>). For further details, read
369 the Quota mini-HOWTO, available from
370 <http://www.tldp.org/docs.html#howto>, or the documentation provided
371 with the quota tools. Probably the quota support is only useful for
372 multi user systems. If unsure, say N.
373
374config QFMT_V1
375 tristate "Old quota format support"
376 depends on QUOTA
377 help
378 This quota format was (is) used by kernels earlier than 2.4.22. If
379 you have quota working and you don't want to convert to new quota
380 format say Y here.
381
382config QFMT_V2
383 tristate "Quota format v2 support"
384 depends on QUOTA
385 help
386 This quota format allows using quotas with 32-bit UIDs/GIDs. If you
387 need this functionality say Y here. Note that you will need recent
388 quota utilities (>= 3.01) for new quota format with this kernel.
389
390config QUOTACTL
391 bool
392 depends on XFS_QUOTA || QUOTA
393 default y
394
395config DNOTIFY
396 bool "Dnotify support" if EMBEDDED
397 default y
398 help
399 Dnotify is a directory-based per-fd file change notification system
400 that uses signals to communicate events to user-space. There exist
401 superior alternatives, but some applications may still rely on
402 dnotify.
403
404 Because of this, if unsure, say Y.
405
406config AUTOFS_FS
407 tristate "Kernel automounter support"
408 help
409 The automounter is a tool to automatically mount remote file systems
410 on demand. This implementation is partially kernel-based to reduce
411 overhead in the already-mounted case; this is unlike the BSD
412 automounter (amd), which is a pure user space daemon.
413
414 To use the automounter you need the user-space tools from the autofs
415 package; you can find the location in <file:Documentation/Changes>.
416 You also want to answer Y to "NFS file system support", below.
417
418 If you want to use the newer version of the automounter with more
419 features, say N here and say Y to "Kernel automounter v4 support",
420 below.
421
422 To compile this support as a module, choose M here: the module will be
423 called autofs.
424
425 If you are not a part of a fairly large, distributed network, you
426 probably do not need an automounter, and can say N here.
427
428config AUTOFS4_FS
429 tristate "Kernel automounter version 4 support (also supports v3)"
430 help
431 The automounter is a tool to automatically mount remote file systems
432 on demand. This implementation is partially kernel-based to reduce
433 overhead in the already-mounted case; this is unlike the BSD
434 automounter (amd), which is a pure user space daemon.
435
436 To use the automounter you need the user-space tools from
437 <ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4/>; you also
438 want to answer Y to "NFS file system support", below.
439
440 To compile this support as a module, choose M here: the module will be
441 called autofs4. You will need to add "alias autofs autofs4" to your
442 modules configuration file.
443
444 If you are not a part of a fairly large, distributed network or
445 don't have a laptop which needs to dynamically reconfigure to the
446 local network, you probably do not need an automounter, and can say
447 N here.
448
449menu "CD-ROM/DVD Filesystems"
450
451config ISO9660_FS
452 tristate "ISO 9660 CDROM file system support"
453 help
454 This is the standard file system used on CD-ROMs. It was previously
455 known as "High Sierra File System" and is called "hsfs" on other
456 Unix systems. The so-called Rock-Ridge extensions which allow for
457 long Unix filenames and symbolic links are also supported by this
458 driver. If you have a CD-ROM drive and want to do more with it than
459 just listen to audio CDs and watch its LEDs, say Y (and read
460 <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO,
461 available from <http://www.tldp.org/docs.html#howto>), thereby
462 enlarging your kernel by about 27 KB; otherwise say N.
463
464 To compile this file system support as a module, choose M here: the
465 module will be called isofs.
466
467config JOLIET
468 bool "Microsoft Joliet CDROM extensions"
469 depends on ISO9660_FS
470 select NLS
471 help
472 Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system
473 which allows for long filenames in unicode format (unicode is the
474 new 16 bit character code, successor to ASCII, which encodes the
475 characters of almost all languages of the world; see
476 <http://www.unicode.org/> for more information). Say Y here if you
477 want to be able to read Joliet CD-ROMs under Linux.
478
479config ZISOFS
480 bool "Transparent decompression extension"
481 depends on ISO9660_FS
482 select ZLIB_INFLATE
483 help
484 This is a Linux-specific extension to RockRidge which lets you store
485 data in compressed form on a CD-ROM and have it transparently
486 decompressed when the CD-ROM is accessed. See
487 <http://www.kernel.org/pub/linux/utils/fs/zisofs/> for the tools
488 necessary to create such a filesystem. Say Y here if you want to be
489 able to read such compressed CD-ROMs.
490
491config ZISOFS_FS
492# for fs/nls/Config.in
493 tristate
494 depends on ZISOFS
495 default ISO9660_FS
496
497config UDF_FS
498 tristate "UDF file system support"
499 help
500 This is the new file system used on some CD-ROMs and DVDs. Say Y if
501 you intend to mount DVD discs or CDRW's written in packet mode, or
502 if written to by other UDF utilities, such as DirectCD.
503 Please read <file:Documentation/filesystems/udf.txt>.
504
505 To compile this file system support as a module, choose M here: the
506 module will be called udf.
507
508 If unsure, say N.
509
510config UDF_NLS
511 bool
512 default y
513 depends on (UDF_FS=m && NLS) || (UDF_FS=y && NLS=y)
514
515endmenu
516
517menu "DOS/FAT/NT Filesystems"
518
519config FAT_FS
520 tristate
521 select NLS
522 help
523 If you want to use one of the FAT-based file systems (the MS-DOS and
524 VFAT (Windows 95) file systems), then you must say Y or M here
525 to include FAT support. You will then be able to mount partitions or
526 diskettes with FAT-based file systems and transparently access the
527 files on them, i.e. MSDOS files will look and behave just like all
528 other Unix files.
529
530 This FAT support is not a file system in itself, it only provides
531 the foundation for the other file systems. You will have to say Y or
532 M to at least one of "MSDOS fs support" or "VFAT fs support" in
533 order to make use of it.
534
535 Another way to read and write MSDOS floppies and hard drive
536 partitions from within Linux (but not transparently) is with the
537 mtools ("man mtools") program suite. You don't need to say Y here in
538 order to do that.
539
540 If you need to move large files on floppies between a DOS and a
541 Linux box, say Y here, mount the floppy under Linux with an MSDOS
542 file system and use GNU tar's M option. GNU tar is a program
543 available for Unix and DOS ("man tar" or "info tar").
544
545 It is now also becoming possible to read and write compressed FAT
546 file systems; read <file:Documentation/filesystems/fat_cvf.txt> for
547 details.
548
549 The FAT support will enlarge your kernel by about 37 KB. If unsure,
550 say Y.
551
552 To compile this as a module, choose M here: the module will be called
553 fat. Note that if you compile the FAT support as a module, you
554 cannot compile any of the FAT-based file systems into the kernel
555 -- they will have to be modules as well.
556
557config MSDOS_FS
558 tristate "MSDOS fs support"
559 select FAT_FS
560 help
561 This allows you to mount MSDOS partitions of your hard drive (unless
562 they are compressed; to access compressed MSDOS partitions under
563 Linux, you can either use the DOS emulator DOSEMU, described in the
564 DOSEMU-HOWTO, available from
565 <http://www.tldp.org/docs.html#howto>, or try dmsdosfs in
566 <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you
567 intend to use dosemu with a non-compressed MSDOS partition, say Y
568 here) and MSDOS floppies. This means that file access becomes
569 transparent, i.e. the MSDOS files look and behave just like all
570 other Unix files.
571
572 If you have Windows 95 or Windows NT installed on your MSDOS
573 partitions, you should use the VFAT file system (say Y to "VFAT fs
574 support" below), or you will not be able to see the long filenames
575 generated by Windows 95 / Windows NT.
576
577 This option will enlarge your kernel by about 7 KB. If unsure,
578 answer Y. This will only work if you said Y to "DOS FAT fs support"
579 as well. To compile this as a module, choose M here: the module will
580 be called msdos.
581
582config VFAT_FS
583 tristate "VFAT (Windows-95) fs support"
584 select FAT_FS
585 help
586 This option provides support for normal Windows file systems with
587 long filenames. That includes non-compressed FAT-based file systems
588 used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
589 programs from the mtools package.
590
591 The VFAT support enlarges your kernel by about 10 KB and it only
592 works if you said Y to the "DOS FAT fs support" above. Please read
593 the file <file:Documentation/filesystems/vfat.txt> for details. If
594 unsure, say Y.
595
596 To compile this as a module, choose M here: the module will be called
597 vfat.
598
599config FAT_DEFAULT_CODEPAGE
600 int "Default codepage for FAT"
601 depends on MSDOS_FS || VFAT_FS
602 default 437
603 help
604 This option should be set to the codepage of your FAT filesystems.
605 It can be overridden with the "codepage" mount option.
606 See <file:Documentation/filesystems/vfat.txt> for more information.
607
608config FAT_DEFAULT_IOCHARSET
609 string "Default iocharset for FAT"
610 depends on VFAT_FS
611 default "iso8859-1"
612 help
613 Set this to the default input/output character set you'd
614 like FAT to use. It should probably match the character set
615 that most of your FAT filesystems use, and can be overridden
616 with the "iocharset" mount option for FAT filesystems.
617 Note that "utf8" is not recommended for FAT filesystems.
618 If unsure, you shouldn't set "utf8" here.
619 See <file:Documentation/filesystems/vfat.txt> for more information.
620
621config NTFS_FS
622 tristate "NTFS file system support"
623 select NLS
624 help
625 NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003.
626
627 Saying Y or M here enables read support. There is partial, but
628 safe, write support available. For write support you must also
629 say Y to "NTFS write support" below.
630
631 There are also a number of user-space tools available, called
632 ntfsprogs. These include ntfsundelete and ntfsresize, that work
633 without NTFS support enabled in the kernel.
634
635 This is a rewrite from scratch of Linux NTFS support and replaced
636 the old NTFS code starting with Linux 2.5.11. A backport to
637 the Linux 2.4 kernel series is separately available as a patch
638 from the project web site.
639
640 For more information see <file:Documentation/filesystems/ntfs.txt>
641 and <http://linux-ntfs.sourceforge.net/>.
642
643 To compile this file system support as a module, choose M here: the
644 module will be called ntfs.
645
646 If you are not using Windows NT, 2000, XP or 2003 in addition to
647 Linux on your computer it is safe to say N.
648
649config NTFS_DEBUG
650 bool "NTFS debugging support"
651 depends on NTFS_FS
652 help
653 If you are experiencing any problems with the NTFS file system, say
654 Y here. This will result in additional consistency checks to be
655 performed by the driver as well as additional debugging messages to
656 be written to the system log. Note that debugging messages are
657 disabled by default. To enable them, supply the option debug_msgs=1
658 at the kernel command line when booting the kernel or as an option
659 to insmod when loading the ntfs module. Once the driver is active,
660 you can enable debugging messages by doing (as root):
661 echo 1 > /proc/sys/fs/ntfs-debug
662 Replacing the "1" with "0" would disable debug messages.
663
664 If you leave debugging messages disabled, this results in little
665 overhead, but enabling debug messages results in very significant
666 slowdown of the system.
667
668 When reporting bugs, please try to have available a full dump of
669 debugging messages while the misbehaviour was occurring.
670
671config NTFS_RW
672 bool "NTFS write support"
673 depends on NTFS_FS
674 help
675 This enables the partial, but safe, write support in the NTFS driver.
676
677 The only supported operation is overwriting existing files, without
678 changing the file length. No file or directory creation, deletion or
679 renaming is possible. Note only non-resident files can be written to
680 so you may find that some very small files (<500 bytes or so) cannot
681 be written to.
682
683 While we cannot guarantee that it will not damage any data, we have
684 so far not received a single report where the driver would have
685 damaged someones data so we assume it is perfectly safe to use.
686
687 Note: While write support is safe in this version (a rewrite from
688 scratch of the NTFS support), it should be noted that the old NTFS
689 write support, included in Linux 2.5.10 and before (since 1997),
690 is not safe.
691
692 This is currently useful with TopologiLinux. TopologiLinux is run
693 on top of any DOS/Microsoft Windows system without partitioning your
694 hard disk. Unlike other Linux distributions TopologiLinux does not
695 need its own partition. For more information see
696 <http://topologi-linux.sourceforge.net/>
697
698 It is perfectly safe to say N here.
699
700endmenu
701
702menu "Pseudo filesystems"
703
704config PROC_FS
705 bool "/proc file system support"
706 help
707 This is a virtual file system providing information about the status
708 of the system. "Virtual" means that it doesn't take up any space on
709 your hard disk: the files are created on the fly by the kernel when
710 you try to access them. Also, you cannot read the files with older
711 version of the program less: you need to use more or cat.
712
713 It's totally cool; for example, "cat /proc/interrupts" gives
714 information about what the different IRQs are used for at the moment
715 (there is a small number of Interrupt ReQuest lines in your computer
716 that are used by the attached devices to gain the CPU's attention --
717 often a source of trouble if two devices are mistakenly configured
718 to use the same IRQ). The program procinfo to display some
719 information about your system gathered from the /proc file system.
720
721 Before you can use the /proc file system, it has to be mounted,
722 meaning it has to be given a location in the directory hierarchy.
723 That location should be /proc. A command such as "mount -t proc proc
724 /proc" or the equivalent line in /etc/fstab does the job.
725
726 The /proc file system is explained in the file
727 <file:Documentation/filesystems/proc.txt> and on the proc(5) manpage
728 ("man 5 proc").
729
730 This option will enlarge your kernel by about 67 KB. Several
731 programs depend on this, so everyone should say Y here.
732
733config PROC_KCORE
734 bool "/proc/kcore support" if !ARM
735 depends on PROC_FS && MMU
736
Vivek Goyal666bfdd2005-06-25 14:58:21 -0700737config PROC_VMCORE
738 bool "/proc/vmcore support (EXPERIMENTAL)"
739 depends on PROC_FS && EMBEDDED && EXPERIMENTAL && CRASH_DUMP
740 help
741 Exports the dump image of crashed kernel in ELF format.
742
Linus Torvalds1da177e2005-04-16 15:20:36 -0700743config SYSFS
744 bool "sysfs file system support" if EMBEDDED
745 default y
746 help
747 The sysfs filesystem is a virtual filesystem that the kernel uses to
748 export internal kernel objects, their attributes, and their
749 relationships to one another.
750
751 Users can use sysfs to ascertain useful information about the running
752 kernel, such as the devices the kernel has discovered on each bus and
753 which driver each is bound to. sysfs can also be used to tune devices
754 and other kernel subsystems.
755
756 Some system agents rely on the information in sysfs to operate.
757 /sbin/hotplug uses device and object attributes in sysfs to assist in
758 delegating policy decisions, like persistantly naming devices.
759
760 sysfs is currently used by the block subsystem to mount the root
761 partition. If sysfs is disabled you must specify the boot device on
762 the kernel boot command line via its major and minor numbers. For
763 example, "root=03:01" for /dev/hda1.
764
765 Designers of embedded systems may wish to say N here to conserve space.
766
Linus Torvalds1da177e2005-04-16 15:20:36 -0700767config DEVPTS_FS_XATTR
768 bool "/dev/pts Extended Attributes"
769 depends on UNIX98_PTYS
770 help
771 Extended attributes are name:value pairs associated with inodes by
772 the kernel or by users (see the attr(5) manual page, or visit
773 <http://acl.bestbits.at/> for details).
774
775 If unsure, say N.
776
777config DEVPTS_FS_SECURITY
778 bool "/dev/pts Security Labels"
779 depends on DEVPTS_FS_XATTR
780 help
781 Security labels support alternative access control models
782 implemented by security modules like SELinux. This option
783 enables an extended attribute handler for file security
784 labels in the /dev/pts filesystem.
785
786 If you are not using a security module that requires using
787 extended attributes for file security labels, say N.
788
789config TMPFS
790 bool "Virtual memory file system support (former shm fs)"
791 help
792 Tmpfs is a file system which keeps all files in virtual memory.
793
794 Everything in tmpfs is temporary in the sense that no files will be
795 created on your hard drive. The files live in memory and swap
796 space. If you unmount a tmpfs instance, everything stored therein is
797 lost.
798
799 See <file:Documentation/filesystems/tmpfs.txt> for details.
800
801config TMPFS_XATTR
802 bool "tmpfs Extended Attributes"
803 depends on TMPFS
804 help
805 Extended attributes are name:value pairs associated with inodes by
806 the kernel or by users (see the attr(5) manual page, or visit
807 <http://acl.bestbits.at/> for details).
808
809 If unsure, say N.
810
811config TMPFS_SECURITY
812 bool "tmpfs Security Labels"
813 depends on TMPFS_XATTR
814 help
815 Security labels support alternative access control models
816 implemented by security modules like SELinux. This option
817 enables an extended attribute handler for file security
818 labels in the tmpfs filesystem.
819 If you are not using a security module that requires using
820 extended attributes for file security labels, say N.
821
822config HUGETLBFS
823 bool "HugeTLB file system support"
824 depends X86 || IA64 || PPC64 || SPARC64 || SUPERH || X86_64 || BROKEN
825
826config HUGETLB_PAGE
827 def_bool HUGETLBFS
828
829config RAMFS
830 bool
831 default y
832 ---help---
833 Ramfs is a file system which keeps all files in RAM. It allows
834 read and write access.
835
836 It is more of an programming example than a useable file system. If
837 you need a file system which lives in RAM with limit checking use
838 tmpfs.
839
840 To compile this as a module, choose M here: the module will be called
841 ramfs.
842
843endmenu
844
845menu "Miscellaneous filesystems"
846
847config ADFS_FS
848 tristate "ADFS file system support (EXPERIMENTAL)"
849 depends on EXPERIMENTAL
850 help
851 The Acorn Disc Filing System is the standard file system of the
852 RiscOS operating system which runs on Acorn's ARM-based Risc PC
853 systems and the Acorn Archimedes range of machines. If you say Y
854 here, Linux will be able to read from ADFS partitions on hard drives
855 and from ADFS-formatted floppy discs. If you also want to be able to
856 write to those devices, say Y to "ADFS write support" below.
857
858 The ADFS partition should be the first partition (i.e.,
859 /dev/[hs]d?1) on each of your drives. Please read the file
860 <file:Documentation/filesystems/adfs.txt> for further details.
861
862 To compile this code as a module, choose M here: the module will be
863 called adfs.
864
865 If unsure, say N.
866
867config ADFS_FS_RW
868 bool "ADFS write support (DANGEROUS)"
869 depends on ADFS_FS
870 help
871 If you say Y here, you will be able to write to ADFS partitions on
872 hard drives and ADFS-formatted floppy disks. This is experimental
873 codes, so if you're unsure, say N.
874
875config AFFS_FS
876 tristate "Amiga FFS file system support (EXPERIMENTAL)"
877 depends on EXPERIMENTAL
878 help
879 The Fast File System (FFS) is the common file system used on hard
880 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
881 if you want to be able to read and write files from and to an Amiga
882 FFS partition on your hard drive. Amiga floppies however cannot be
883 read with this driver due to an incompatibility of the floppy
884 controller used in an Amiga and the standard floppy controller in
885 PCs and workstations. Read <file:Documentation/filesystems/affs.txt>
886 and <file:fs/affs/Changes>.
887
888 With this driver you can also mount disk files used by Bernd
889 Schmidt's Un*X Amiga Emulator
890 (<http://www.freiburg.linux.de/~uae/>).
891 If you want to do this, you will also need to say Y or M to "Loop
892 device support", above.
893
894 To compile this file system support as a module, choose M here: the
895 module will be called affs. If unsure, say N.
896
897config HFS_FS
898 tristate "Apple Macintosh file system support (EXPERIMENTAL)"
899 depends on EXPERIMENTAL
900 help
901 If you say Y here, you will be able to mount Macintosh-formatted
902 floppy disks and hard drive partitions with full read-write access.
903 Please read <file:fs/hfs/HFS.txt> to learn about the available mount
904 options.
905
906 To compile this file system support as a module, choose M here: the
907 module will be called hfs.
908
909config HFSPLUS_FS
910 tristate "Apple Extended HFS file system support"
911 select NLS
912 select NLS_UTF8
913 help
914 If you say Y here, you will be able to mount extended format
915 Macintosh-formatted hard drive partitions with full read-write access.
916
917 This file system is often called HFS+ and was introduced with
918 MacOS 8. It includes all Mac specific filesystem data such as
919 data forks and creator codes, but it also has several UNIX
920 style features such as file ownership and permissions.
921
922config BEFS_FS
923 tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)"
924 depends on EXPERIMENTAL
925 select NLS
926 help
927 The BeOS File System (BeFS) is the native file system of Be, Inc's
928 BeOS. Notable features include support for arbitrary attributes
929 on files and directories, and database-like indeces on selected
930 attributes. (Also note that this driver doesn't make those features
931 available at this time). It is a 64 bit filesystem, so it supports
932 extremly large volumes and files.
933
934 If you use this filesystem, you should also say Y to at least one
935 of the NLS (native language support) options below.
936
937 If you don't know what this is about, say N.
938
939 To compile this as a module, choose M here: the module will be
940 called befs.
941
942config BEFS_DEBUG
943 bool "Debug BeFS"
944 depends on BEFS_FS
945 help
946 If you say Y here, you can use the 'debug' mount option to enable
947 debugging output from the driver.
948
949config BFS_FS
950 tristate "BFS file system support (EXPERIMENTAL)"
951 depends on EXPERIMENTAL
952 help
953 Boot File System (BFS) is a file system used under SCO UnixWare to
954 allow the bootloader access to the kernel image and other important
955 files during the boot process. It is usually mounted under /stand
956 and corresponds to the slice marked as "STAND" in the UnixWare
957 partition. You should say Y if you want to read or write the files
958 on your /stand slice from within Linux. You then also need to say Y
959 to "UnixWare slices support", below. More information about the BFS
960 file system is contained in the file
961 <file:Documentation/filesystems/bfs.txt>.
962
963 If you don't know what this is about, say N.
964
965 To compile this as a module, choose M here: the module will be called
966 bfs. Note that the file system of your root partition (the one
967 containing the directory /) cannot be compiled as a module.
968
969
970
971config EFS_FS
972 tristate "EFS file system support (read only) (EXPERIMENTAL)"
973 depends on EXPERIMENTAL
974 help
975 EFS is an older file system used for non-ISO9660 CD-ROMs and hard
976 disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
977 uses the XFS file system for hard disk partitions however).
978
979 This implementation only offers read-only access. If you don't know
980 what all this is about, it's safe to say N. For more information
981 about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
982
983 To compile the EFS file system support as a module, choose M here: the
984 module will be called efs.
985
986config JFFS_FS
987 tristate "Journalling Flash File System (JFFS) support"
988 depends on MTD
989 help
990 JFFS is the Journaling Flash File System developed by Axis
991 Communications in Sweden, aimed at providing a crash/powerdown-safe
992 file system for disk-less embedded devices. Further information is
993 available at (<http://developer.axis.com/software/jffs/>).
994
995config JFFS_FS_VERBOSE
996 int "JFFS debugging verbosity (0 = quiet, 3 = noisy)"
997 depends on JFFS_FS
998 default "0"
999 help
1000 Determines the verbosity level of the JFFS debugging messages.
1001
1002config JFFS_PROC_FS
1003 bool "JFFS stats available in /proc filesystem"
1004 depends on JFFS_FS && PROC_FS
1005 help
1006 Enabling this option will cause statistics from mounted JFFS file systems
1007 to be made available to the user in the /proc/fs/jffs/ directory.
1008
1009config JFFS2_FS
1010 tristate "Journalling Flash File System v2 (JFFS2) support"
1011 select CRC32
1012 depends on MTD
1013 help
1014 JFFS2 is the second generation of the Journalling Flash File System
1015 for use on diskless embedded devices. It provides improved wear
1016 levelling, compression and support for hard links. You cannot use
1017 this on normal block devices, only on 'MTD' devices.
1018
1019 Further information on the design and implementation of JFFS2 is
1020 available at <http://sources.redhat.com/jffs2/>.
1021
1022config JFFS2_FS_DEBUG
1023 int "JFFS2 debugging verbosity (0 = quiet, 2 = noisy)"
1024 depends on JFFS2_FS
1025 default "0"
1026 help
1027 This controls the amount of debugging messages produced by the JFFS2
1028 code. Set it to zero for use in production systems. For evaluation,
1029 testing and debugging, it's advisable to set it to one. This will
1030 enable a few assertions and will print debugging messages at the
1031 KERN_DEBUG loglevel, where they won't normally be visible. Level 2
1032 is unlikely to be useful - it enables extra debugging in certain
1033 areas which at one point needed debugging, but when the bugs were
1034 located and fixed, the detailed messages were relegated to level 2.
1035
1036 If reporting bugs, please try to have available a full dump of the
1037 messages at debug level 1 while the misbehaviour was occurring.
1038
1039config JFFS2_FS_NAND
1040 bool "JFFS2 support for NAND flash"
1041 depends on JFFS2_FS
1042 default n
1043 help
1044 This enables the support for NAND flash in JFFS2. NAND is a newer
1045 type of flash chip design than the traditional NOR flash, with
1046 higher density but a handful of characteristics which make it more
1047 interesting for the file system to use.
1048
1049 Say 'N' unless you have NAND flash.
1050
1051config JFFS2_FS_NOR_ECC
1052 bool "JFFS2 support for ECC'd NOR flash (EXPERIMENTAL)"
1053 depends on JFFS2_FS && EXPERIMENTAL
1054 default n
1055 help
1056 This enables the experimental support for NOR flash with transparent
1057 ECC for JFFS2. This type of flash chip is not common, however it is
1058 available from ST Microelectronics.
1059
1060config JFFS2_COMPRESSION_OPTIONS
1061 bool "Advanced compression options for JFFS2"
1062 depends on JFFS2_FS
1063 default n
1064 help
1065 Enabling this option allows you to explicitly choose which
1066 compression modules, if any, are enabled in JFFS2. Removing
1067 compressors and mean you cannot read existing file systems,
1068 and enabling experimental compressors can mean that you
1069 write a file system which cannot be read by a standard kernel.
1070
1071 If unsure, you should _definitely_ say 'N'.
1072
1073config JFFS2_ZLIB
1074 bool "JFFS2 ZLIB compression support" if JFFS2_COMPRESSION_OPTIONS
1075 select ZLIB_INFLATE
1076 select ZLIB_DEFLATE
1077 depends on JFFS2_FS
1078 default y
1079 help
1080 Zlib is designed to be a free, general-purpose, legally unencumbered,
1081 lossless data-compression library for use on virtually any computer
1082 hardware and operating system. See <http://www.gzip.org/zlib/> for
1083 further information.
1084
1085 Say 'Y' if unsure.
1086
1087config JFFS2_RTIME
1088 bool "JFFS2 RTIME compression support" if JFFS2_COMPRESSION_OPTIONS
1089 depends on JFFS2_FS
1090 default y
1091 help
1092 Rtime does manage to recompress already-compressed data. Say 'Y' if unsure.
1093
1094config JFFS2_RUBIN
1095 bool "JFFS2 RUBIN compression support" if JFFS2_COMPRESSION_OPTIONS
1096 depends on JFFS2_FS
1097 default n
1098 help
1099 RUBINMIPS and DYNRUBIN compressors. Say 'N' if unsure.
1100
1101choice
1102 prompt "JFFS2 default compression mode" if JFFS2_COMPRESSION_OPTIONS
1103 default JFFS2_CMODE_PRIORITY
1104 depends on JFFS2_FS
1105 help
1106 You can set here the default compression mode of JFFS2 from
1107 the available compression modes. Don't touch if unsure.
1108
1109config JFFS2_CMODE_NONE
1110 bool "no compression"
1111 help
1112 Uses no compression.
1113
1114config JFFS2_CMODE_PRIORITY
1115 bool "priority"
1116 help
1117 Tries the compressors in a predefinied order and chooses the first
1118 successful one.
1119
1120config JFFS2_CMODE_SIZE
1121 bool "size (EXPERIMENTAL)"
1122 help
1123 Tries all compressors and chooses the one which has the smallest
1124 result.
1125
1126endchoice
1127
1128config CRAMFS
1129 tristate "Compressed ROM file system support (cramfs)"
1130 select ZLIB_INFLATE
1131 help
1132 Saying Y here includes support for CramFs (Compressed ROM File
1133 System). CramFs is designed to be a simple, small, and compressed
1134 file system for ROM based embedded systems. CramFs is read-only,
1135 limited to 256MB file systems (with 16MB files), and doesn't support
1136 16/32 bits uid/gid, hard links and timestamps.
1137
1138 See <file:Documentation/filesystems/cramfs.txt> and
1139 <file:fs/cramfs/README> for further information.
1140
1141 To compile this as a module, choose M here: the module will be called
1142 cramfs. Note that the root file system (the one containing the
1143 directory /) cannot be compiled as a module.
1144
1145 If unsure, say N.
1146
1147config VXFS_FS
1148 tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
1149 help
1150 FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
1151 file system format. VERITAS VxFS(TM) is the standard file system
1152 of SCO UnixWare (and possibly others) and optionally available
1153 for Sunsoft Solaris, HP-UX and many other operating systems.
1154 Currently only readonly access is supported.
1155
1156 NOTE: the file system type as used by mount(1), mount(2) and
1157 fstab(5) is 'vxfs' as it describes the file system format, not
1158 the actual driver.
1159
1160 To compile this as a module, choose M here: the module will be
1161 called freevxfs. If unsure, say N.
1162
1163
1164config HPFS_FS
1165 tristate "OS/2 HPFS file system support"
1166 help
1167 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
1168 is the file system used for organizing files on OS/2 hard disk
1169 partitions. Say Y if you want to be able to read files from and
1170 write files to an OS/2 HPFS partition on your hard drive. OS/2
1171 floppies however are in regular MSDOS format, so you don't need this
1172 option in order to be able to read them. Read
1173 <file:Documentation/filesystems/hpfs.txt>.
1174
1175 To compile this file system support as a module, choose M here: the
1176 module will be called hpfs. If unsure, say N.
1177
1178
1179
1180config QNX4FS_FS
1181 tristate "QNX4 file system support (read only)"
1182 help
1183 This is the file system used by the real-time operating systems
1184 QNX 4 and QNX 6 (the latter is also called QNX RTP).
1185 Further information is available at <http://www.qnx.com/>.
1186 Say Y if you intend to mount QNX hard disks or floppies.
1187 Unless you say Y to "QNX4FS read-write support" below, you will
1188 only be able to read these file systems.
1189
1190 To compile this file system support as a module, choose M here: the
1191 module will be called qnx4.
1192
1193 If you don't know whether you need it, then you don't need it:
1194 answer N.
1195
1196config QNX4FS_RW
1197 bool "QNX4FS write support (DANGEROUS)"
1198 depends on QNX4FS_FS && EXPERIMENTAL && BROKEN
1199 help
1200 Say Y if you want to test write support for QNX4 file systems.
1201
1202 It's currently broken, so for now:
1203 answer N.
1204
1205
1206
1207config SYSV_FS
1208 tristate "System V/Xenix/V7/Coherent file system support"
1209 help
1210 SCO, Xenix and Coherent are commercial Unix systems for Intel
1211 machines, and Version 7 was used on the DEC PDP-11. Saying Y
1212 here would allow you to read from their floppies and hard disk
1213 partitions.
1214
1215 If you have floppies or hard disk partitions like that, it is likely
1216 that they contain binaries from those other Unix systems; in order
1217 to run these binaries, you will want to install linux-abi which is a
1218 a set of kernel modules that lets you run SCO, Xenix, Wyse,
1219 UnixWare, Dell Unix and System V programs under Linux. It is
1220 available via FTP (user: ftp) from
1221 <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
1222 NOTE: that will work only for binaries from Intel-based systems;
1223 PDP ones will have to wait until somebody ports Linux to -11 ;-)
1224
1225 If you only intend to mount files from some other Unix over the
1226 network using NFS, you don't need the System V file system support
1227 (but you need NFS file system support obviously).
1228
1229 Note that this option is generally not needed for floppies, since a
1230 good portable way to transport files and directories between unixes
1231 (and even other operating systems) is given by the tar program ("man
1232 tar" or preferably "info tar"). Note also that this option has
1233 nothing whatsoever to do with the option "System V IPC". Read about
1234 the System V file system in
1235 <file:Documentation/filesystems/sysv-fs.txt>.
1236 Saying Y here will enlarge your kernel by about 27 KB.
1237
1238 To compile this as a module, choose M here: the module will be called
1239 sysv.
1240
1241 If you haven't heard about all of this before, it's safe to say N.
1242
1243
1244
1245config UFS_FS
1246 tristate "UFS file system support (read only)"
1247 help
1248 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
1249 OpenBSD and NeXTstep) use a file system called UFS. Some System V
1250 Unixes can create and mount hard disk partitions and diskettes using
1251 this file system as well. Saying Y here will allow you to read from
1252 these partitions; if you also want to write to them, say Y to the
1253 experimental "UFS file system write support", below. Please read the
1254 file <file:Documentation/filesystems/ufs.txt> for more information.
1255
1256 The recently released UFS2 variant (used in FreeBSD 5.x) is
1257 READ-ONLY supported.
1258
1259 If you only intend to mount files from some other Unix over the
1260 network using NFS, you don't need the UFS file system support (but
1261 you need NFS file system support obviously).
1262
1263 Note that this option is generally not needed for floppies, since a
1264 good portable way to transport files and directories between unixes
1265 (and even other operating systems) is given by the tar program ("man
1266 tar" or preferably "info tar").
1267
1268 When accessing NeXTstep files, you may need to convert them from the
1269 NeXT character set to the Latin1 character set; use the program
1270 recode ("info recode") for this purpose.
1271
1272 To compile the UFS file system support as a module, choose M here: the
1273 module will be called ufs.
1274
1275 If you haven't heard about all of this before, it's safe to say N.
1276
1277config UFS_FS_WRITE
1278 bool "UFS file system write support (DANGEROUS)"
1279 depends on UFS_FS && EXPERIMENTAL
1280 help
1281 Say Y here if you want to try writing to UFS partitions. This is
1282 experimental, so you should back up your UFS partitions beforehand.
1283
1284endmenu
1285
1286menu "Network File Systems"
1287 depends on NET
1288
1289config NFS_FS
1290 tristate "NFS file system support"
1291 depends on INET
1292 select LOCKD
1293 select SUNRPC
Andreas Gruenbacherb7fa0552005-06-22 17:16:27 +00001294 select NFS_ACL_SUPPORT if NFS_V3_ACL
Linus Torvalds1da177e2005-04-16 15:20:36 -07001295 help
1296 If you are connected to some other (usually local) Unix computer
1297 (using SLIP, PLIP, PPP or Ethernet) and want to mount files residing
1298 on that computer (the NFS server) using the Network File Sharing
1299 protocol, say Y. "Mounting files" means that the client can access
1300 the files with usual UNIX commands as if they were sitting on the
1301 client's hard disk. For this to work, the server must run the
1302 programs nfsd and mountd (but does not need to have NFS file system
1303 support enabled in its kernel). NFS is explained in the Network
1304 Administrator's Guide, available from
1305 <http://www.tldp.org/docs.html#guide>, on its man page: "man
1306 nfs", and in the NFS-HOWTO.
1307
1308 A superior but less widely used alternative to NFS is provided by
1309 the Coda file system; see "Coda file system support" below.
1310
1311 If you say Y here, you should have said Y to TCP/IP networking also.
1312 This option would enlarge your kernel by about 27 KB.
1313
1314 To compile this file system support as a module, choose M here: the
1315 module will be called nfs.
1316
1317 If you are configuring a diskless machine which will mount its root
1318 file system over NFS at boot time, say Y here and to "Kernel
1319 level IP autoconfiguration" above and to "Root file system on NFS"
1320 below. You cannot compile this driver as a module in this case.
1321 There are two packages designed for booting diskless machines over
1322 the net: netboot, available from
1323 <http://ftp1.sourceforge.net/netboot/>, and Etherboot,
1324 available from <http://ftp1.sourceforge.net/etherboot/>.
1325
1326 If you don't know what all this is about, say N.
1327
1328config NFS_V3
1329 bool "Provide NFSv3 client support"
1330 depends on NFS_FS
1331 help
1332 Say Y here if you want your NFS client to be able to speak version
1333 3 of the NFS protocol.
1334
1335 If unsure, say Y.
1336
Andreas Gruenbacherb7fa0552005-06-22 17:16:27 +00001337config NFS_V3_ACL
1338 bool "Provide client support for the NFSv3 ACL protocol extension"
1339 depends on NFS_V3
1340 help
1341 Implement the NFSv3 ACL protocol extension for manipulating POSIX
1342 Access Control Lists. The server should also be compiled with
1343 the NFSv3 ACL protocol extension; see the CONFIG_NFSD_V3_ACL option.
1344
1345 If unsure, say N.
1346
Linus Torvalds1da177e2005-04-16 15:20:36 -07001347config NFS_V4
1348 bool "Provide NFSv4 client support (EXPERIMENTAL)"
1349 depends on NFS_FS && EXPERIMENTAL
1350 select RPCSEC_GSS_KRB5
1351 help
1352 Say Y here if you want your NFS client to be able to speak the newer
1353 version 4 of the NFS protocol.
1354
1355 Note: Requires auxiliary userspace daemons which may be found on
1356 http://www.citi.umich.edu/projects/nfsv4/
1357
1358 If unsure, say N.
1359
1360config NFS_DIRECTIO
1361 bool "Allow direct I/O on NFS files (EXPERIMENTAL)"
1362 depends on NFS_FS && EXPERIMENTAL
1363 help
1364 This option enables applications to perform uncached I/O on files
1365 in NFS file systems using the O_DIRECT open() flag. When O_DIRECT
1366 is set for a file, its data is not cached in the system's page
1367 cache. Data is moved to and from user-level application buffers
1368 directly. Unlike local disk-based file systems, NFS O_DIRECT has
1369 no alignment restrictions.
1370
1371 Unless your program is designed to use O_DIRECT properly, you are
1372 much better off allowing the NFS client to manage data caching for
1373 you. Misusing O_DIRECT can cause poor server performance or network
1374 storms. This kernel build option defaults OFF to avoid exposing
1375 system administrators unwittingly to a potentially hazardous
1376 feature.
1377
1378 For more details on NFS O_DIRECT, see fs/nfs/direct.c.
1379
1380 If unsure, say N. This reduces the size of the NFS client, and
1381 causes open() to return EINVAL if a file residing in NFS is
1382 opened with the O_DIRECT flag.
1383
1384config NFSD
1385 tristate "NFS server support"
1386 depends on INET
1387 select LOCKD
1388 select SUNRPC
1389 select EXPORTFS
Andreas Gruenbachera257cdd2005-06-22 17:16:26 +00001390 select NFS_ACL_SUPPORT if NFSD_V3_ACL || NFSD_V2_ACL
Linus Torvalds1da177e2005-04-16 15:20:36 -07001391 help
1392 If you want your Linux box to act as an NFS *server*, so that other
1393 computers on your local network which support NFS can access certain
1394 directories on your box transparently, you have two options: you can
1395 use the self-contained user space program nfsd, in which case you
1396 should say N here, or you can say Y and use the kernel based NFS
1397 server. The advantage of the kernel based solution is that it is
1398 faster.
1399
1400 In either case, you will need support software; the respective
1401 locations are given in the file <file:Documentation/Changes> in the
1402 NFS section.
1403
1404 If you say Y here, you will get support for version 2 of the NFS
1405 protocol (NFSv2). If you also want NFSv3, say Y to the next question
1406 as well.
1407
1408 Please read the NFS-HOWTO, available from
1409 <http://www.tldp.org/docs.html#howto>.
1410
1411 To compile the NFS server support as a module, choose M here: the
1412 module will be called nfsd. If unsure, say N.
1413
Andreas Gruenbachera257cdd2005-06-22 17:16:26 +00001414config NFSD_V2_ACL
1415 bool
1416 depends on NFSD
1417
Linus Torvalds1da177e2005-04-16 15:20:36 -07001418config NFSD_V3
1419 bool "Provide NFSv3 server support"
1420 depends on NFSD
1421 help
1422 If you would like to include the NFSv3 server as well as the NFSv2
1423 server, say Y here. If unsure, say Y.
1424
Andreas Gruenbachera257cdd2005-06-22 17:16:26 +00001425config NFSD_V3_ACL
1426 bool "Provide server support for the NFSv3 ACL protocol extension"
1427 depends on NFSD_V3
1428 select NFSD_V2_ACL
1429 help
1430 Implement the NFSv3 ACL protocol extension for manipulating POSIX
1431 Access Control Lists on exported file systems. NFS clients should
1432 be compiled with the NFSv3 ACL protocol extension; see the
1433 CONFIG_NFS_V3_ACL option. If unsure, say N.
1434
Linus Torvalds1da177e2005-04-16 15:20:36 -07001435config NFSD_V4
1436 bool "Provide NFSv4 server support (EXPERIMENTAL)"
1437 depends on NFSD_V3 && EXPERIMENTAL
1438 select NFSD_TCP
NeilBrowna55370a2005-06-23 22:03:52 -07001439 select CRYPTO_MD5
1440 select CRYPTO
Linus Torvalds1da177e2005-04-16 15:20:36 -07001441 help
1442 If you would like to include the NFSv4 server as well as the NFSv2
1443 and NFSv3 servers, say Y here. This feature is experimental, and
1444 should only be used if you are interested in helping to test NFSv4.
1445 If unsure, say N.
1446
1447config NFSD_TCP
1448 bool "Provide NFS server over TCP support"
1449 depends on NFSD
1450 default y
1451 help
1452 If you want your NFS server to support TCP connections, say Y here.
1453 TCP connections usually perform better than the default UDP when
1454 the network is lossy or congested. If unsure, say Y.
1455
1456config ROOT_NFS
1457 bool "Root file system on NFS"
1458 depends on NFS_FS=y && IP_PNP
1459 help
1460 If you want your Linux box to mount its whole root file system (the
1461 one containing the directory /) from some other computer over the
1462 net via NFS (presumably because your box doesn't have a hard disk),
1463 say Y. Read <file:Documentation/nfsroot.txt> for details. It is
1464 likely that in this case, you also want to say Y to "Kernel level IP
1465 autoconfiguration" so that your box can discover its network address
1466 at boot time.
1467
1468 Most people say N here.
1469
1470config LOCKD
1471 tristate
1472
1473config LOCKD_V4
1474 bool
1475 depends on NFSD_V3 || NFS_V3
1476 default y
1477
1478config EXPORTFS
1479 tristate
1480
Andreas Gruenbachera257cdd2005-06-22 17:16:26 +00001481config NFS_ACL_SUPPORT
1482 tristate
1483 select FS_POSIX_ACL
1484
1485config NFS_COMMON
1486 bool
1487 depends on NFSD || NFS_FS
1488 default y
1489
Linus Torvalds1da177e2005-04-16 15:20:36 -07001490config SUNRPC
1491 tristate
1492
1493config SUNRPC_GSS
1494 tristate
1495
1496config RPCSEC_GSS_KRB5
1497 tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
1498 depends on SUNRPC && EXPERIMENTAL
1499 select SUNRPC_GSS
1500 select CRYPTO
1501 select CRYPTO_MD5
1502 select CRYPTO_DES
1503 help
1504 Provides for secure RPC calls by means of a gss-api
1505 mechanism based on Kerberos V5. This is required for
1506 NFSv4.
1507
1508 Note: Requires an auxiliary userspace daemon which may be found on
1509 http://www.citi.umich.edu/projects/nfsv4/
1510
1511 If unsure, say N.
1512
1513config RPCSEC_GSS_SPKM3
1514 tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
1515 depends on SUNRPC && EXPERIMENTAL
1516 select SUNRPC_GSS
1517 select CRYPTO
1518 select CRYPTO_MD5
1519 select CRYPTO_DES
1520 help
1521 Provides for secure RPC calls by means of a gss-api
1522 mechanism based on the SPKM3 public-key mechanism.
1523
1524 Note: Requires an auxiliary userspace daemon which may be found on
1525 http://www.citi.umich.edu/projects/nfsv4/
1526
1527 If unsure, say N.
1528
1529config SMB_FS
1530 tristate "SMB file system support (to mount Windows shares etc.)"
1531 depends on INET
1532 select NLS
1533 help
1534 SMB (Server Message Block) is the protocol Windows for Workgroups
1535 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
1536 files and printers over local networks. Saying Y here allows you to
1537 mount their file systems (often called "shares" in this context) and
1538 access them just like any other Unix directory. Currently, this
1539 works only if the Windows machines use TCP/IP as the underlying
1540 transport protocol, and not NetBEUI. For details, read
1541 <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
1542 available from <http://www.tldp.org/docs.html#howto>.
1543
1544 Note: if you just want your box to act as an SMB *server* and make
1545 files and printing services available to Windows clients (which need
1546 to have a TCP/IP stack), you don't need to say Y here; you can use
1547 the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
1548 for that.
1549
1550 General information about how to connect Linux, Windows machines and
1551 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1552
1553 To compile the SMB support as a module, choose M here: the module will
1554 be called smbfs. Most people say N, however.
1555
1556config SMB_NLS_DEFAULT
1557 bool "Use a default NLS"
1558 depends on SMB_FS
1559 help
1560 Enabling this will make smbfs use nls translations by default. You
1561 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
1562 settings and you need to give the default nls for the SMB server as
1563 CONFIG_SMB_NLS_REMOTE.
1564
1565 The nls settings can be changed at mount time, if your smbmount
1566 supports that, using the codepage and iocharset parameters.
1567
1568 smbmount from samba 2.2.0 or later supports this.
1569
1570config SMB_NLS_REMOTE
1571 string "Default Remote NLS Option"
1572 depends on SMB_NLS_DEFAULT
1573 default "cp437"
1574 help
1575 This setting allows you to specify a default value for which
1576 codepage the server uses. If this field is left blank no
1577 translations will be done by default. The local codepage/charset
1578 default to CONFIG_NLS_DEFAULT.
1579
1580 The nls settings can be changed at mount time, if your smbmount
1581 supports that, using the codepage and iocharset parameters.
1582
1583 smbmount from samba 2.2.0 or later supports this.
1584
1585config CIFS
1586 tristate "CIFS support (advanced network filesystem for Samba, Window and other CIFS compliant servers)"
1587 depends on INET
1588 select NLS
1589 help
1590 This is the client VFS module for the Common Internet File System
1591 (CIFS) protocol which is the successor to the Server Message Block
1592 (SMB) protocol, the native file sharing mechanism for most early
1593 PC operating systems. The CIFS protocol is fully supported by
1594 file servers such as Windows 2000 (including Windows 2003, NT 4
1595 and Windows XP) as well by Samba (which provides excellent CIFS
1596 server support for Linux and many other operating systems). Currently
1597 you must use the smbfs client filesystem to access older SMB servers
1598 such as Windows 9x and OS/2.
1599
1600 The intent of the cifs module is to provide an advanced
1601 network file system client for mounting to CIFS compliant servers,
1602 including support for dfs (hierarchical name space), secure per-user
1603 session establishment, safe distributed caching (oplock), optional
1604 packet signing, Unicode and other internationalization improvements,
1605 and optional Winbind (nsswitch) integration. You do not need to enable
1606 cifs if running only a (Samba) server. It is possible to enable both
1607 smbfs and cifs (e.g. if you are using CIFS for accessing Windows 2003
1608 and Samba 3 servers, and smbfs for accessing old servers). If you need
1609 to mount to Samba or Windows 2003 servers from this machine, say Y.
1610
1611config CIFS_STATS
1612 bool "CIFS statistics"
1613 depends on CIFS
1614 help
1615 Enabling this option will cause statistics for each server share
1616 mounted by the cifs client to be displayed in /proc/fs/cifs/Stats
1617
1618config CIFS_XATTR
1619 bool "CIFS extended attributes (EXPERIMENTAL)"
1620 depends on CIFS
1621 help
1622 Extended attributes are name:value pairs associated with inodes by
1623 the kernel or by users (see the attr(5) manual page, or visit
1624 <http://acl.bestbits.at/> for details). CIFS maps the name of
1625 extended attributes beginning with the user namespace prefix
1626 to SMB/CIFS EAs. EAs are stored on Windows servers without the
1627 user namespace prefix, but their names are seen by Linux cifs clients
1628 prefaced by the user namespace prefix. The system namespace
1629 (used by some filesystems to store ACLs) is not supported at
1630 this time.
1631
1632 If unsure, say N.
1633
1634config CIFS_POSIX
1635 bool "CIFS POSIX Extensions (EXPERIMENTAL)"
1636 depends on CIFS_XATTR
1637 help
1638 Enabling this option will cause the cifs client to attempt to
1639 negotiate a newer dialect with servers, such as Samba 3.0.5
1640 or later, that optionally can handle more POSIX like (rather
1641 than Windows like) file behavior. It also enables
1642 support for POSIX ACLs (getfacl and setfacl) to servers
1643 (such as Samba 3.10 and later) which can negotiate
1644 CIFS POSIX ACL support. If unsure, say N.
1645
1646config CIFS_EXPERIMENTAL
1647 bool "CIFS Experimental Features (EXPERIMENTAL)"
1648 depends on CIFS
1649 help
1650 Enables cifs features under testing. These features
1651 are highly experimental. If unsure, say N.
1652
1653config NCP_FS
1654 tristate "NCP file system support (to mount NetWare volumes)"
1655 depends on IPX!=n || INET
1656 help
1657 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
1658 used by Novell NetWare clients to talk to file servers. It is to
1659 IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
1660 to mount NetWare file server volumes and to access them just like
1661 any other Unix directory. For details, please read the file
1662 <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
1663 the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
1664
1665 You do not have to say Y here if you want your Linux box to act as a
1666 file *server* for Novell NetWare clients.
1667
1668 General information about how to connect Linux, Windows machines and
1669 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1670
1671 To compile this as a module, choose M here: the module will be called
1672 ncpfs. Say N unless you are connected to a Novell network.
1673
1674source "fs/ncpfs/Kconfig"
1675
1676config CODA_FS
1677 tristate "Coda file system support (advanced network fs)"
1678 depends on INET
1679 help
1680 Coda is an advanced network file system, similar to NFS in that it
1681 enables you to mount file systems of a remote server and access them
1682 with regular Unix commands as if they were sitting on your hard
1683 disk. Coda has several advantages over NFS: support for
1684 disconnected operation (e.g. for laptops), read/write server
1685 replication, security model for authentication and encryption,
1686 persistent client caches and write back caching.
1687
1688 If you say Y here, your Linux box will be able to act as a Coda
1689 *client*. You will need user level code as well, both for the
1690 client and server. Servers are currently user level, i.e. they need
1691 no kernel support. Please read
1692 <file:Documentation/filesystems/coda.txt> and check out the Coda
1693 home page <http://www.coda.cs.cmu.edu/>.
1694
1695 To compile the coda client support as a module, choose M here: the
1696 module will be called coda.
1697
1698config CODA_FS_OLD_API
1699 bool "Use 96-bit Coda file identifiers"
1700 depends on CODA_FS
1701 help
1702 A new kernel-userspace API had to be introduced for Coda v6.0
1703 to support larger 128-bit file identifiers as needed by the
1704 new realms implementation.
1705
1706 However this new API is not backward compatible with older
1707 clients. If you really need to run the old Coda userspace
1708 cache manager then say Y.
1709
1710 For most cases you probably want to say N.
1711
1712config AFS_FS
1713# for fs/nls/Config.in
1714 tristate "Andrew File System support (AFS) (Experimental)"
1715 depends on INET && EXPERIMENTAL
1716 select RXRPC
1717 help
1718 If you say Y here, you will get an experimental Andrew File System
1719 driver. It currently only supports unsecured read-only AFS access.
1720
1721 See <file:Documentation/filesystems/afs.txt> for more intormation.
1722
1723 If unsure, say N.
1724
1725config RXRPC
1726 tristate
1727
1728endmenu
1729
1730menu "Partition Types"
1731
1732source "fs/partitions/Kconfig"
1733
1734endmenu
1735
1736source "fs/nls/Kconfig"
1737
1738endmenu
1739