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