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