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