blob: a27002668bd36a7abb3074bfa41036ae16580b73 [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
Mark Fasheh02ed8412006-09-14 10:28:06 -0700328 tristate "OCFS2 file system support"
329 depends on NET && SYSFS
Mark Fashehb4e40a52005-12-15 14:31:24 -0800330 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
Joel Becker2b388c62006-05-10 18:28:59 -0700359config OCFS2_DEBUG_MASKLOG
360 bool "OCFS2 logging support"
361 depends on OCFS2_FS
362 default y
363 help
364 The ocfs2 filesystem has an extensive logging system. The system
365 allows selection of events to log via files in /sys/o2cb/logmask/.
366 This option will enlarge your kernel, but it allows debugging of
367 ocfs2 filesystem issues.
368
Linus Torvalds1da177e2005-04-16 15:20:36 -0700369config MINIX_FS
370 tristate "Minix fs support"
371 help
372 Minix is a simple operating system used in many classes about OS's.
373 The minix file system (method to organize files on a hard disk
374 partition or a floppy disk) was the original file system for Linux,
375 but has been superseded by the second extended file system ext2fs.
376 You don't want to use the minix file system on your hard disk
377 because of certain built-in restrictions, but it is sometimes found
378 on older Linux floppy disks. This option will enlarge your kernel
379 by about 28 KB. If unsure, say N.
380
381 To compile this file system support as a module, choose M here: the
382 module will be called minix. Note that the file system of your root
383 partition (the one containing the directory /) cannot be compiled as
384 a module.
385
386config ROMFS_FS
387 tristate "ROM file system support"
388 ---help---
389 This is a very small read-only file system mainly intended for
390 initial ram disks of installation disks, but it could be used for
391 other read-only media as well. Read
392 <file:Documentation/filesystems/romfs.txt> for details.
393
394 To compile this file system support as a module, choose M here: the
395 module will be called romfs. Note that the file system of your
396 root partition (the one containing the directory /) cannot be a
397 module.
398
399 If you don't know whether you need it, then you don't need it:
400 answer N.
401
Robert Love0eeca282005-07-12 17:06:03 -0400402config INOTIFY
403 bool "Inotify file change notification support"
404 default y
405 ---help---
Amy Griffis2d9048e2006-06-01 13:10:59 -0700406 Say Y here to enable inotify support. Inotify is a file change
407 notification system and a replacement for dnotify. Inotify fixes
408 numerous shortcomings in dnotify and introduces several new features
409 including multiple file events, one-shot support, and unmount
Robert Love3de11742005-08-04 13:07:08 -0700410 notification.
411
412 For more information, see Documentation/filesystems/inotify.txt
Robert Love0eeca282005-07-12 17:06:03 -0400413
414 If unsure, say Y.
415
Amy Griffis2d9048e2006-06-01 13:10:59 -0700416config INOTIFY_USER
417 bool "Inotify support for userspace"
418 depends on INOTIFY
419 default y
420 ---help---
421 Say Y here to enable inotify support for userspace, including the
422 associated system calls. Inotify allows monitoring of both files and
423 directories via a single open fd. Events are read from the file
424 descriptor, which is also select()- and poll()-able.
425
426 For more information, see Documentation/filesystems/inotify.txt
427
428 If unsure, say Y.
429
Linus Torvalds1da177e2005-04-16 15:20:36 -0700430config QUOTA
431 bool "Quota support"
432 help
433 If you say Y here, you will be able to set per user limits for disk
434 usage (also called disk quotas). Currently, it works for the
435 ext2, ext3, and reiserfs file system. ext3 also supports journalled
436 quotas for which you don't need to run quotacheck(8) after an unclean
Adrian Bunk919532a2005-09-06 15:17:22 -0700437 shutdown.
438 For further details, read the Quota mini-HOWTO, available from
Linus Torvalds1da177e2005-04-16 15:20:36 -0700439 <http://www.tldp.org/docs.html#howto>, or the documentation provided
440 with the quota tools. Probably the quota support is only useful for
441 multi user systems. If unsure, say N.
442
443config QFMT_V1
444 tristate "Old quota format support"
445 depends on QUOTA
446 help
447 This quota format was (is) used by kernels earlier than 2.4.22. If
448 you have quota working and you don't want to convert to new quota
449 format say Y here.
450
451config QFMT_V2
452 tristate "Quota format v2 support"
453 depends on QUOTA
454 help
455 This quota format allows using quotas with 32-bit UIDs/GIDs. If you
Adrian Bunk919532a2005-09-06 15:17:22 -0700456 need this functionality say Y here.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700457
458config QUOTACTL
459 bool
460 depends on XFS_QUOTA || QUOTA
461 default y
462
463config DNOTIFY
464 bool "Dnotify support" if EMBEDDED
465 default y
466 help
467 Dnotify is a directory-based per-fd file change notification system
468 that uses signals to communicate events to user-space. There exist
469 superior alternatives, but some applications may still rely on
470 dnotify.
471
472 Because of this, if unsure, say Y.
473
474config AUTOFS_FS
475 tristate "Kernel automounter support"
476 help
477 The automounter is a tool to automatically mount remote file systems
478 on demand. This implementation is partially kernel-based to reduce
479 overhead in the already-mounted case; this is unlike the BSD
480 automounter (amd), which is a pure user space daemon.
481
482 To use the automounter you need the user-space tools from the autofs
483 package; you can find the location in <file:Documentation/Changes>.
484 You also want to answer Y to "NFS file system support", below.
485
486 If you want to use the newer version of the automounter with more
487 features, say N here and say Y to "Kernel automounter v4 support",
488 below.
489
490 To compile this support as a module, choose M here: the module will be
491 called autofs.
492
493 If you are not a part of a fairly large, distributed network, you
494 probably do not need an automounter, and can say N here.
495
496config AUTOFS4_FS
497 tristate "Kernel automounter version 4 support (also supports v3)"
498 help
499 The automounter is a tool to automatically mount remote file systems
500 on demand. This implementation is partially kernel-based to reduce
501 overhead in the already-mounted case; this is unlike the BSD
502 automounter (amd), which is a pure user space daemon.
503
504 To use the automounter you need the user-space tools from
505 <ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4/>; you also
506 want to answer Y to "NFS file system support", below.
507
508 To compile this support as a module, choose M here: the module will be
509 called autofs4. You will need to add "alias autofs autofs4" to your
510 modules configuration file.
511
512 If you are not a part of a fairly large, distributed network or
513 don't have a laptop which needs to dynamically reconfigure to the
514 local network, you probably do not need an automounter, and can say
515 N here.
516
Miklos Szeredi04578f12005-09-09 13:10:22 -0700517config FUSE_FS
518 tristate "Filesystem in Userspace support"
519 help
520 With FUSE it is possible to implement a fully functional filesystem
521 in a userspace program.
522
523 There's also companion library: libfuse. This library along with
524 utilities is available from the FUSE homepage:
525 <http://fuse.sourceforge.net/>
526
Miklos Szeredi909021e2005-09-27 21:45:20 -0700527 See <file:Documentation/filesystems/fuse.txt> for more information.
528 See <file:Documentation/Changes> for needed library/utility version.
529
Miklos Szeredi04578f12005-09-09 13:10:22 -0700530 If you want to develop a userspace FS, or if you want to use
531 a filesystem based on FUSE, answer Y or M.
532
Linus Torvalds1da177e2005-04-16 15:20:36 -0700533menu "CD-ROM/DVD Filesystems"
534
535config ISO9660_FS
536 tristate "ISO 9660 CDROM file system support"
537 help
538 This is the standard file system used on CD-ROMs. It was previously
539 known as "High Sierra File System" and is called "hsfs" on other
540 Unix systems. The so-called Rock-Ridge extensions which allow for
541 long Unix filenames and symbolic links are also supported by this
542 driver. If you have a CD-ROM drive and want to do more with it than
543 just listen to audio CDs and watch its LEDs, say Y (and read
544 <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO,
545 available from <http://www.tldp.org/docs.html#howto>), thereby
546 enlarging your kernel by about 27 KB; otherwise say N.
547
548 To compile this file system support as a module, choose M here: the
549 module will be called isofs.
550
551config JOLIET
552 bool "Microsoft Joliet CDROM extensions"
553 depends on ISO9660_FS
554 select NLS
555 help
556 Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system
557 which allows for long filenames in unicode format (unicode is the
558 new 16 bit character code, successor to ASCII, which encodes the
559 characters of almost all languages of the world; see
560 <http://www.unicode.org/> for more information). Say Y here if you
561 want to be able to read Joliet CD-ROMs under Linux.
562
563config ZISOFS
564 bool "Transparent decompression extension"
565 depends on ISO9660_FS
566 select ZLIB_INFLATE
567 help
568 This is a Linux-specific extension to RockRidge which lets you store
569 data in compressed form on a CD-ROM and have it transparently
570 decompressed when the CD-ROM is accessed. See
571 <http://www.kernel.org/pub/linux/utils/fs/zisofs/> for the tools
572 necessary to create such a filesystem. Say Y here if you want to be
573 able to read such compressed CD-ROMs.
574
575config ZISOFS_FS
576# for fs/nls/Config.in
577 tristate
578 depends on ZISOFS
579 default ISO9660_FS
580
581config UDF_FS
582 tristate "UDF file system support"
583 help
584 This is the new file system used on some CD-ROMs and DVDs. Say Y if
585 you intend to mount DVD discs or CDRW's written in packet mode, or
586 if written to by other UDF utilities, such as DirectCD.
587 Please read <file:Documentation/filesystems/udf.txt>.
588
589 To compile this file system support as a module, choose M here: the
590 module will be called udf.
591
592 If unsure, say N.
593
594config UDF_NLS
595 bool
596 default y
597 depends on (UDF_FS=m && NLS) || (UDF_FS=y && NLS=y)
598
599endmenu
600
601menu "DOS/FAT/NT Filesystems"
602
603config FAT_FS
604 tristate
605 select NLS
606 help
607 If you want to use one of the FAT-based file systems (the MS-DOS and
608 VFAT (Windows 95) file systems), then you must say Y or M here
609 to include FAT support. You will then be able to mount partitions or
610 diskettes with FAT-based file systems and transparently access the
611 files on them, i.e. MSDOS files will look and behave just like all
612 other Unix files.
613
614 This FAT support is not a file system in itself, it only provides
615 the foundation for the other file systems. You will have to say Y or
616 M to at least one of "MSDOS fs support" or "VFAT fs support" in
617 order to make use of it.
618
619 Another way to read and write MSDOS floppies and hard drive
620 partitions from within Linux (but not transparently) is with the
621 mtools ("man mtools") program suite. You don't need to say Y here in
622 order to do that.
623
624 If you need to move large files on floppies between a DOS and a
625 Linux box, say Y here, mount the floppy under Linux with an MSDOS
626 file system and use GNU tar's M option. GNU tar is a program
627 available for Unix and DOS ("man tar" or "info tar").
628
629 It is now also becoming possible to read and write compressed FAT
630 file systems; read <file:Documentation/filesystems/fat_cvf.txt> for
631 details.
632
633 The FAT support will enlarge your kernel by about 37 KB. If unsure,
634 say Y.
635
636 To compile this as a module, choose M here: the module will be called
637 fat. Note that if you compile the FAT support as a module, you
638 cannot compile any of the FAT-based file systems into the kernel
639 -- they will have to be modules as well.
640
641config MSDOS_FS
642 tristate "MSDOS fs support"
643 select FAT_FS
644 help
645 This allows you to mount MSDOS partitions of your hard drive (unless
646 they are compressed; to access compressed MSDOS partitions under
647 Linux, you can either use the DOS emulator DOSEMU, described in the
648 DOSEMU-HOWTO, available from
649 <http://www.tldp.org/docs.html#howto>, or try dmsdosfs in
650 <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you
651 intend to use dosemu with a non-compressed MSDOS partition, say Y
652 here) and MSDOS floppies. This means that file access becomes
653 transparent, i.e. the MSDOS files look and behave just like all
654 other Unix files.
655
656 If you have Windows 95 or Windows NT installed on your MSDOS
657 partitions, you should use the VFAT file system (say Y to "VFAT fs
658 support" below), or you will not be able to see the long filenames
659 generated by Windows 95 / Windows NT.
660
661 This option will enlarge your kernel by about 7 KB. If unsure,
662 answer Y. This will only work if you said Y to "DOS FAT fs support"
663 as well. To compile this as a module, choose M here: the module will
664 be called msdos.
665
666config VFAT_FS
667 tristate "VFAT (Windows-95) fs support"
668 select FAT_FS
669 help
670 This option provides support for normal Windows file systems with
671 long filenames. That includes non-compressed FAT-based file systems
672 used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
673 programs from the mtools package.
674
675 The VFAT support enlarges your kernel by about 10 KB and it only
676 works if you said Y to the "DOS FAT fs support" above. Please read
677 the file <file:Documentation/filesystems/vfat.txt> for details. If
678 unsure, say Y.
679
680 To compile this as a module, choose M here: the module will be called
681 vfat.
682
683config FAT_DEFAULT_CODEPAGE
684 int "Default codepage for FAT"
685 depends on MSDOS_FS || VFAT_FS
686 default 437
687 help
688 This option should be set to the codepage of your FAT filesystems.
689 It can be overridden with the "codepage" mount option.
690 See <file:Documentation/filesystems/vfat.txt> for more information.
691
692config FAT_DEFAULT_IOCHARSET
693 string "Default iocharset for FAT"
694 depends on VFAT_FS
695 default "iso8859-1"
696 help
697 Set this to the default input/output character set you'd
698 like FAT to use. It should probably match the character set
699 that most of your FAT filesystems use, and can be overridden
700 with the "iocharset" mount option for FAT filesystems.
701 Note that "utf8" is not recommended for FAT filesystems.
702 If unsure, you shouldn't set "utf8" here.
703 See <file:Documentation/filesystems/vfat.txt> for more information.
704
705config NTFS_FS
706 tristate "NTFS file system support"
707 select NLS
708 help
709 NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003.
710
711 Saying Y or M here enables read support. There is partial, but
712 safe, write support available. For write support you must also
713 say Y to "NTFS write support" below.
714
715 There are also a number of user-space tools available, called
716 ntfsprogs. These include ntfsundelete and ntfsresize, that work
717 without NTFS support enabled in the kernel.
718
719 This is a rewrite from scratch of Linux NTFS support and replaced
720 the old NTFS code starting with Linux 2.5.11. A backport to
721 the Linux 2.4 kernel series is separately available as a patch
722 from the project web site.
723
724 For more information see <file:Documentation/filesystems/ntfs.txt>
725 and <http://linux-ntfs.sourceforge.net/>.
726
727 To compile this file system support as a module, choose M here: the
728 module will be called ntfs.
729
730 If you are not using Windows NT, 2000, XP or 2003 in addition to
731 Linux on your computer it is safe to say N.
732
733config NTFS_DEBUG
734 bool "NTFS debugging support"
735 depends on NTFS_FS
736 help
737 If you are experiencing any problems with the NTFS file system, say
738 Y here. This will result in additional consistency checks to be
739 performed by the driver as well as additional debugging messages to
740 be written to the system log. Note that debugging messages are
741 disabled by default. To enable them, supply the option debug_msgs=1
742 at the kernel command line when booting the kernel or as an option
743 to insmod when loading the ntfs module. Once the driver is active,
744 you can enable debugging messages by doing (as root):
745 echo 1 > /proc/sys/fs/ntfs-debug
746 Replacing the "1" with "0" would disable debug messages.
747
748 If you leave debugging messages disabled, this results in little
749 overhead, but enabling debug messages results in very significant
750 slowdown of the system.
751
752 When reporting bugs, please try to have available a full dump of
753 debugging messages while the misbehaviour was occurring.
754
755config NTFS_RW
756 bool "NTFS write support"
757 depends on NTFS_FS
758 help
759 This enables the partial, but safe, write support in the NTFS driver.
760
761 The only supported operation is overwriting existing files, without
762 changing the file length. No file or directory creation, deletion or
763 renaming is possible. Note only non-resident files can be written to
764 so you may find that some very small files (<500 bytes or so) cannot
765 be written to.
766
767 While we cannot guarantee that it will not damage any data, we have
768 so far not received a single report where the driver would have
769 damaged someones data so we assume it is perfectly safe to use.
770
771 Note: While write support is safe in this version (a rewrite from
772 scratch of the NTFS support), it should be noted that the old NTFS
773 write support, included in Linux 2.5.10 and before (since 1997),
774 is not safe.
775
776 This is currently useful with TopologiLinux. TopologiLinux is run
777 on top of any DOS/Microsoft Windows system without partitioning your
778 hard disk. Unlike other Linux distributions TopologiLinux does not
779 need its own partition. For more information see
780 <http://topologi-linux.sourceforge.net/>
781
782 It is perfectly safe to say N here.
783
784endmenu
785
786menu "Pseudo filesystems"
787
788config PROC_FS
H. Peter Anvin69755652006-06-25 05:48:08 -0700789 bool "/proc file system support" if EMBEDDED
790 default y
Linus Torvalds1da177e2005-04-16 15:20:36 -0700791 help
792 This is a virtual file system providing information about the status
793 of the system. "Virtual" means that it doesn't take up any space on
794 your hard disk: the files are created on the fly by the kernel when
795 you try to access them. Also, you cannot read the files with older
796 version of the program less: you need to use more or cat.
797
798 It's totally cool; for example, "cat /proc/interrupts" gives
799 information about what the different IRQs are used for at the moment
800 (there is a small number of Interrupt ReQuest lines in your computer
801 that are used by the attached devices to gain the CPU's attention --
802 often a source of trouble if two devices are mistakenly configured
803 to use the same IRQ). The program procinfo to display some
804 information about your system gathered from the /proc file system.
805
806 Before you can use the /proc file system, it has to be mounted,
807 meaning it has to be given a location in the directory hierarchy.
808 That location should be /proc. A command such as "mount -t proc proc
809 /proc" or the equivalent line in /etc/fstab does the job.
810
811 The /proc file system is explained in the file
812 <file:Documentation/filesystems/proc.txt> and on the proc(5) manpage
813 ("man 5 proc").
814
815 This option will enlarge your kernel by about 67 KB. Several
816 programs depend on this, so everyone should say Y here.
817
818config PROC_KCORE
819 bool "/proc/kcore support" if !ARM
820 depends on PROC_FS && MMU
821
Vivek Goyal666bfdd2005-06-25 14:58:21 -0700822config PROC_VMCORE
823 bool "/proc/vmcore support (EXPERIMENTAL)"
Maneesh Soni05970d42006-01-09 20:51:52 -0800824 depends on PROC_FS && EXPERIMENTAL && CRASH_DUMP
Vivek Goyal68250ba2006-04-10 22:54:30 -0700825 default y
Vivek Goyal666bfdd2005-06-25 14:58:21 -0700826 help
827 Exports the dump image of crashed kernel in ELF format.
828
Linus Torvalds1da177e2005-04-16 15:20:36 -0700829config SYSFS
830 bool "sysfs file system support" if EMBEDDED
831 default y
832 help
833 The sysfs filesystem is a virtual filesystem that the kernel uses to
834 export internal kernel objects, their attributes, and their
835 relationships to one another.
836
837 Users can use sysfs to ascertain useful information about the running
838 kernel, such as the devices the kernel has discovered on each bus and
839 which driver each is bound to. sysfs can also be used to tune devices
840 and other kernel subsystems.
841
842 Some system agents rely on the information in sysfs to operate.
843 /sbin/hotplug uses device and object attributes in sysfs to assist in
844 delegating policy decisions, like persistantly naming devices.
845
846 sysfs is currently used by the block subsystem to mount the root
847 partition. If sysfs is disabled you must specify the boot device on
848 the kernel boot command line via its major and minor numbers. For
849 example, "root=03:01" for /dev/hda1.
850
851 Designers of embedded systems may wish to say N here to conserve space.
852
Linus Torvalds1da177e2005-04-16 15:20:36 -0700853config TMPFS
854 bool "Virtual memory file system support (former shm fs)"
855 help
856 Tmpfs is a file system which keeps all files in virtual memory.
857
858 Everything in tmpfs is temporary in the sense that no files will be
859 created on your hard drive. The files live in memory and swap
860 space. If you unmount a tmpfs instance, everything stored therein is
861 lost.
862
863 See <file:Documentation/filesystems/tmpfs.txt> for details.
864
Linus Torvalds1da177e2005-04-16 15:20:36 -0700865config HUGETLBFS
866 bool "HugeTLB file system support"
Brian Gerst0d078f62005-10-30 14:59:20 -0800867 depends X86 || IA64 || PPC64 || SPARC64 || SUPERH || BROKEN
Arthur Othienodda27d12006-04-18 22:20:57 -0700868 help
869 hugetlbfs is a filesystem backing for HugeTLB pages, based on
870 ramfs. For architectures that support it, say Y here and read
871 <file:Documentation/vm/hugetlbpage.txt> for details.
872
873 If unsure, say N.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700874
875config HUGETLB_PAGE
876 def_bool HUGETLBFS
877
878config RAMFS
879 bool
880 default y
881 ---help---
882 Ramfs is a file system which keeps all files in RAM. It allows
883 read and write access.
884
885 It is more of an programming example than a useable file system. If
886 you need a file system which lives in RAM with limit checking use
887 tmpfs.
888
889 To compile this as a module, choose M here: the module will be called
890 ramfs.
891
Joel Becker7063fbf2005-12-15 14:29:43 -0800892config CONFIGFS_FS
893 tristate "Userspace-driven configuration filesystem (EXPERIMENTAL)"
Adrian Bunk65714b92006-03-26 14:25:52 +0200894 depends on SYSFS && EXPERIMENTAL
Joel Becker7063fbf2005-12-15 14:29:43 -0800895 help
896 configfs is a ram-based filesystem that provides the converse
897 of sysfs's functionality. Where sysfs is a filesystem-based
898 view of kernel objects, configfs is a filesystem-based manager
899 of kernel objects, or config_items.
900
901 Both sysfs and configfs can and should exist together on the
902 same system. One is not a replacement for the other.
903
Linus Torvalds1da177e2005-04-16 15:20:36 -0700904endmenu
905
906menu "Miscellaneous filesystems"
907
908config ADFS_FS
909 tristate "ADFS file system support (EXPERIMENTAL)"
910 depends on EXPERIMENTAL
911 help
912 The Acorn Disc Filing System is the standard file system of the
913 RiscOS operating system which runs on Acorn's ARM-based Risc PC
914 systems and the Acorn Archimedes range of machines. If you say Y
915 here, Linux will be able to read from ADFS partitions on hard drives
916 and from ADFS-formatted floppy discs. If you also want to be able to
917 write to those devices, say Y to "ADFS write support" below.
918
919 The ADFS partition should be the first partition (i.e.,
920 /dev/[hs]d?1) on each of your drives. Please read the file
921 <file:Documentation/filesystems/adfs.txt> for further details.
922
923 To compile this code as a module, choose M here: the module will be
924 called adfs.
925
926 If unsure, say N.
927
928config ADFS_FS_RW
929 bool "ADFS write support (DANGEROUS)"
930 depends on ADFS_FS
931 help
932 If you say Y here, you will be able to write to ADFS partitions on
933 hard drives and ADFS-formatted floppy disks. This is experimental
934 codes, so if you're unsure, say N.
935
936config AFFS_FS
937 tristate "Amiga FFS file system support (EXPERIMENTAL)"
938 depends on EXPERIMENTAL
939 help
940 The Fast File System (FFS) is the common file system used on hard
941 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
942 if you want to be able to read and write files from and to an Amiga
943 FFS partition on your hard drive. Amiga floppies however cannot be
944 read with this driver due to an incompatibility of the floppy
945 controller used in an Amiga and the standard floppy controller in
946 PCs and workstations. Read <file:Documentation/filesystems/affs.txt>
947 and <file:fs/affs/Changes>.
948
949 With this driver you can also mount disk files used by Bernd
950 Schmidt's Un*X Amiga Emulator
951 (<http://www.freiburg.linux.de/~uae/>).
952 If you want to do this, you will also need to say Y or M to "Loop
953 device support", above.
954
955 To compile this file system support as a module, choose M here: the
956 module will be called affs. If unsure, say N.
957
958config HFS_FS
959 tristate "Apple Macintosh file system support (EXPERIMENTAL)"
960 depends on EXPERIMENTAL
Lennert Buytenhek878129a2005-11-07 00:59:18 -0800961 select NLS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700962 help
963 If you say Y here, you will be able to mount Macintosh-formatted
964 floppy disks and hard drive partitions with full read-write access.
965 Please read <file:fs/hfs/HFS.txt> to learn about the available mount
966 options.
967
968 To compile this file system support as a module, choose M here: the
969 module will be called hfs.
970
971config HFSPLUS_FS
972 tristate "Apple Extended HFS file system support"
973 select NLS
974 select NLS_UTF8
975 help
976 If you say Y here, you will be able to mount extended format
977 Macintosh-formatted hard drive partitions with full read-write access.
978
979 This file system is often called HFS+ and was introduced with
980 MacOS 8. It includes all Mac specific filesystem data such as
981 data forks and creator codes, but it also has several UNIX
982 style features such as file ownership and permissions.
983
984config BEFS_FS
985 tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)"
986 depends on EXPERIMENTAL
987 select NLS
988 help
989 The BeOS File System (BeFS) is the native file system of Be, Inc's
990 BeOS. Notable features include support for arbitrary attributes
991 on files and directories, and database-like indeces on selected
992 attributes. (Also note that this driver doesn't make those features
993 available at this time). It is a 64 bit filesystem, so it supports
994 extremly large volumes and files.
995
996 If you use this filesystem, you should also say Y to at least one
997 of the NLS (native language support) options below.
998
999 If you don't know what this is about, say N.
1000
1001 To compile this as a module, choose M here: the module will be
1002 called befs.
1003
1004config BEFS_DEBUG
1005 bool "Debug BeFS"
1006 depends on BEFS_FS
1007 help
1008 If you say Y here, you can use the 'debug' mount option to enable
1009 debugging output from the driver.
1010
1011config BFS_FS
1012 tristate "BFS file system support (EXPERIMENTAL)"
1013 depends on EXPERIMENTAL
1014 help
1015 Boot File System (BFS) is a file system used under SCO UnixWare to
1016 allow the bootloader access to the kernel image and other important
1017 files during the boot process. It is usually mounted under /stand
1018 and corresponds to the slice marked as "STAND" in the UnixWare
1019 partition. You should say Y if you want to read or write the files
1020 on your /stand slice from within Linux. You then also need to say Y
1021 to "UnixWare slices support", below. More information about the BFS
1022 file system is contained in the file
1023 <file:Documentation/filesystems/bfs.txt>.
1024
1025 If you don't know what this is about, say N.
1026
1027 To compile this as a module, choose M here: the module will be called
1028 bfs. Note that the file system of your root partition (the one
1029 containing the directory /) cannot be compiled as a module.
1030
1031
1032
1033config EFS_FS
1034 tristate "EFS file system support (read only) (EXPERIMENTAL)"
1035 depends on EXPERIMENTAL
1036 help
1037 EFS is an older file system used for non-ISO9660 CD-ROMs and hard
1038 disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
1039 uses the XFS file system for hard disk partitions however).
1040
1041 This implementation only offers read-only access. If you don't know
1042 what all this is about, it's safe to say N. For more information
1043 about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
1044
1045 To compile the EFS file system support as a module, choose M here: the
1046 module will be called efs.
1047
1048config JFFS_FS
1049 tristate "Journalling Flash File System (JFFS) support"
1050 depends on MTD
1051 help
1052 JFFS is the Journaling Flash File System developed by Axis
1053 Communications in Sweden, aimed at providing a crash/powerdown-safe
1054 file system for disk-less embedded devices. Further information is
1055 available at (<http://developer.axis.com/software/jffs/>).
1056
1057config JFFS_FS_VERBOSE
1058 int "JFFS debugging verbosity (0 = quiet, 3 = noisy)"
1059 depends on JFFS_FS
1060 default "0"
1061 help
1062 Determines the verbosity level of the JFFS debugging messages.
1063
1064config JFFS_PROC_FS
1065 bool "JFFS stats available in /proc filesystem"
1066 depends on JFFS_FS && PROC_FS
1067 help
1068 Enabling this option will cause statistics from mounted JFFS file systems
1069 to be made available to the user in the /proc/fs/jffs/ directory.
1070
1071config JFFS2_FS
1072 tristate "Journalling Flash File System v2 (JFFS2) support"
1073 select CRC32
1074 depends on MTD
1075 help
1076 JFFS2 is the second generation of the Journalling Flash File System
1077 for use on diskless embedded devices. It provides improved wear
1078 levelling, compression and support for hard links. You cannot use
1079 this on normal block devices, only on 'MTD' devices.
1080
1081 Further information on the design and implementation of JFFS2 is
1082 available at <http://sources.redhat.com/jffs2/>.
1083
1084config JFFS2_FS_DEBUG
1085 int "JFFS2 debugging verbosity (0 = quiet, 2 = noisy)"
1086 depends on JFFS2_FS
1087 default "0"
1088 help
1089 This controls the amount of debugging messages produced by the JFFS2
1090 code. Set it to zero for use in production systems. For evaluation,
1091 testing and debugging, it's advisable to set it to one. This will
1092 enable a few assertions and will print debugging messages at the
1093 KERN_DEBUG loglevel, where they won't normally be visible. Level 2
1094 is unlikely to be useful - it enables extra debugging in certain
1095 areas which at one point needed debugging, but when the bugs were
1096 located and fixed, the detailed messages were relegated to level 2.
1097
1098 If reporting bugs, please try to have available a full dump of the
1099 messages at debug level 1 while the misbehaviour was occurring.
1100
David Woodhouse2ba72cb2006-06-18 10:22:40 +01001101config JFFS2_FS_WRITEBUFFER
1102 bool "JFFS2 write-buffering support"
KaiGai Koheiaa98d7c2006-05-13 15:09:47 +09001103 depends on JFFS2_FS
David Woodhouse2ba72cb2006-06-18 10:22:40 +01001104 default y
1105 help
1106 This enables the write-buffering support in JFFS2.
1107
1108 This functionality is required to support JFFS2 on the following
1109 types of flash devices:
1110 - NAND flash
1111 - NOR flash with transparent ECC
1112 - DataFlash
1113
1114config JFFS2_SUMMARY
1115 bool "JFFS2 summary support (EXPERIMENTAL)"
1116 depends on JFFS2_FS && EXPERIMENTAL
1117 default n
1118 help
1119 This feature makes it possible to use summary information
1120 for faster filesystem mount.
1121
1122 The summary information can be inserted into a filesystem image
1123 by the utility 'sumtool'.
1124
1125 If unsure, say 'N'.
1126
1127config JFFS2_FS_XATTR
1128 bool "JFFS2 XATTR support (EXPERIMENTAL)"
KaiGai Kohei04510de2006-06-24 09:21:13 +09001129 depends on JFFS2_FS && EXPERIMENTAL
KaiGai Koheiaa98d7c2006-05-13 15:09:47 +09001130 default n
1131 help
1132 Extended attributes are name:value pairs associated with inodes by
1133 the kernel or by users (see the attr(5) manual page, or visit
1134 <http://acl.bestbits.at/> for details).
1135
1136 If unsure, say N.
1137
1138config JFFS2_FS_POSIX_ACL
1139 bool "JFFS2 POSIX Access Control Lists"
1140 depends on JFFS2_FS_XATTR
1141 default y
1142 select FS_POSIX_ACL
1143 help
1144 Posix Access Control Lists (ACLs) support permissions for users and
1145 groups beyond the owner/group/world scheme.
1146
1147 To learn more about Access Control Lists, visit the Posix ACLs for
1148 Linux website <http://acl.bestbits.at/>.
1149
1150 If you don't know what Access Control Lists are, say N
1151
1152config JFFS2_FS_SECURITY
1153 bool "JFFS2 Security Labels"
1154 depends on JFFS2_FS_XATTR
1155 default y
1156 help
1157 Security labels support alternative access control models
1158 implemented by security modules like SELinux. This option
1159 enables an extended attribute handler for file security
1160 labels in the jffs2 filesystem.
1161
1162 If you are not using a security module that requires using
1163 extended attributes for file security labels, say N.
1164
Linus Torvalds1da177e2005-04-16 15:20:36 -07001165config JFFS2_COMPRESSION_OPTIONS
1166 bool "Advanced compression options for JFFS2"
1167 depends on JFFS2_FS
1168 default n
1169 help
1170 Enabling this option allows you to explicitly choose which
1171 compression modules, if any, are enabled in JFFS2. Removing
1172 compressors and mean you cannot read existing file systems,
1173 and enabling experimental compressors can mean that you
1174 write a file system which cannot be read by a standard kernel.
1175
1176 If unsure, you should _definitely_ say 'N'.
1177
1178config JFFS2_ZLIB
1179 bool "JFFS2 ZLIB compression support" if JFFS2_COMPRESSION_OPTIONS
1180 select ZLIB_INFLATE
1181 select ZLIB_DEFLATE
1182 depends on JFFS2_FS
1183 default y
1184 help
1185 Zlib is designed to be a free, general-purpose, legally unencumbered,
Thomas Gleixner182ec4e2005-11-07 11:16:07 +00001186 lossless data-compression library for use on virtually any computer
Linus Torvalds1da177e2005-04-16 15:20:36 -07001187 hardware and operating system. See <http://www.gzip.org/zlib/> for
1188 further information.
Thomas Gleixner182ec4e2005-11-07 11:16:07 +00001189
Linus Torvalds1da177e2005-04-16 15:20:36 -07001190 Say 'Y' if unsure.
1191
1192config JFFS2_RTIME
1193 bool "JFFS2 RTIME compression support" if JFFS2_COMPRESSION_OPTIONS
1194 depends on JFFS2_FS
1195 default y
1196 help
1197 Rtime does manage to recompress already-compressed data. Say 'Y' if unsure.
1198
1199config JFFS2_RUBIN
1200 bool "JFFS2 RUBIN compression support" if JFFS2_COMPRESSION_OPTIONS
1201 depends on JFFS2_FS
1202 default n
1203 help
1204 RUBINMIPS and DYNRUBIN compressors. Say 'N' if unsure.
1205
1206choice
1207 prompt "JFFS2 default compression mode" if JFFS2_COMPRESSION_OPTIONS
1208 default JFFS2_CMODE_PRIORITY
1209 depends on JFFS2_FS
1210 help
Thomas Gleixner182ec4e2005-11-07 11:16:07 +00001211 You can set here the default compression mode of JFFS2 from
Linus Torvalds1da177e2005-04-16 15:20:36 -07001212 the available compression modes. Don't touch if unsure.
1213
1214config JFFS2_CMODE_NONE
1215 bool "no compression"
1216 help
1217 Uses no compression.
1218
1219config JFFS2_CMODE_PRIORITY
1220 bool "priority"
1221 help
Thomas Gleixner182ec4e2005-11-07 11:16:07 +00001222 Tries the compressors in a predefinied order and chooses the first
Linus Torvalds1da177e2005-04-16 15:20:36 -07001223 successful one.
1224
1225config JFFS2_CMODE_SIZE
1226 bool "size (EXPERIMENTAL)"
1227 help
Thomas Gleixner182ec4e2005-11-07 11:16:07 +00001228 Tries all compressors and chooses the one which has the smallest
Linus Torvalds1da177e2005-04-16 15:20:36 -07001229 result.
1230
1231endchoice
1232
1233config CRAMFS
1234 tristate "Compressed ROM file system support (cramfs)"
1235 select ZLIB_INFLATE
1236 help
1237 Saying Y here includes support for CramFs (Compressed ROM File
1238 System). CramFs is designed to be a simple, small, and compressed
1239 file system for ROM based embedded systems. CramFs is read-only,
1240 limited to 256MB file systems (with 16MB files), and doesn't support
1241 16/32 bits uid/gid, hard links and timestamps.
1242
1243 See <file:Documentation/filesystems/cramfs.txt> and
1244 <file:fs/cramfs/README> for further information.
1245
1246 To compile this as a module, choose M here: the module will be called
1247 cramfs. Note that the root file system (the one containing the
1248 directory /) cannot be compiled as a module.
1249
1250 If unsure, say N.
1251
1252config VXFS_FS
1253 tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
1254 help
1255 FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
1256 file system format. VERITAS VxFS(TM) is the standard file system
1257 of SCO UnixWare (and possibly others) and optionally available
1258 for Sunsoft Solaris, HP-UX and many other operating systems.
1259 Currently only readonly access is supported.
1260
1261 NOTE: the file system type as used by mount(1), mount(2) and
1262 fstab(5) is 'vxfs' as it describes the file system format, not
1263 the actual driver.
1264
1265 To compile this as a module, choose M here: the module will be
1266 called freevxfs. If unsure, say N.
1267
1268
1269config HPFS_FS
1270 tristate "OS/2 HPFS file system support"
1271 help
1272 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
1273 is the file system used for organizing files on OS/2 hard disk
1274 partitions. Say Y if you want to be able to read files from and
1275 write files to an OS/2 HPFS partition on your hard drive. OS/2
1276 floppies however are in regular MSDOS format, so you don't need this
1277 option in order to be able to read them. Read
1278 <file:Documentation/filesystems/hpfs.txt>.
1279
1280 To compile this file system support as a module, choose M here: the
1281 module will be called hpfs. If unsure, say N.
1282
1283
1284
1285config QNX4FS_FS
1286 tristate "QNX4 file system support (read only)"
1287 help
1288 This is the file system used by the real-time operating systems
1289 QNX 4 and QNX 6 (the latter is also called QNX RTP).
1290 Further information is available at <http://www.qnx.com/>.
1291 Say Y if you intend to mount QNX hard disks or floppies.
1292 Unless you say Y to "QNX4FS read-write support" below, you will
1293 only be able to read these file systems.
1294
1295 To compile this file system support as a module, choose M here: the
1296 module will be called qnx4.
1297
1298 If you don't know whether you need it, then you don't need it:
1299 answer N.
1300
1301config QNX4FS_RW
1302 bool "QNX4FS write support (DANGEROUS)"
1303 depends on QNX4FS_FS && EXPERIMENTAL && BROKEN
1304 help
1305 Say Y if you want to test write support for QNX4 file systems.
1306
1307 It's currently broken, so for now:
1308 answer N.
1309
1310
1311
1312config SYSV_FS
1313 tristate "System V/Xenix/V7/Coherent file system support"
1314 help
1315 SCO, Xenix and Coherent are commercial Unix systems for Intel
1316 machines, and Version 7 was used on the DEC PDP-11. Saying Y
1317 here would allow you to read from their floppies and hard disk
1318 partitions.
1319
1320 If you have floppies or hard disk partitions like that, it is likely
1321 that they contain binaries from those other Unix systems; in order
1322 to run these binaries, you will want to install linux-abi which is a
1323 a set of kernel modules that lets you run SCO, Xenix, Wyse,
1324 UnixWare, Dell Unix and System V programs under Linux. It is
1325 available via FTP (user: ftp) from
1326 <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
1327 NOTE: that will work only for binaries from Intel-based systems;
1328 PDP ones will have to wait until somebody ports Linux to -11 ;-)
1329
1330 If you only intend to mount files from some other Unix over the
1331 network using NFS, you don't need the System V file system support
1332 (but you need NFS file system support obviously).
1333
1334 Note that this option is generally not needed for floppies, since a
1335 good portable way to transport files and directories between unixes
1336 (and even other operating systems) is given by the tar program ("man
1337 tar" or preferably "info tar"). Note also that this option has
1338 nothing whatsoever to do with the option "System V IPC". Read about
1339 the System V file system in
1340 <file:Documentation/filesystems/sysv-fs.txt>.
1341 Saying Y here will enlarge your kernel by about 27 KB.
1342
1343 To compile this as a module, choose M here: the module will be called
1344 sysv.
1345
1346 If you haven't heard about all of this before, it's safe to say N.
1347
1348
1349
1350config UFS_FS
1351 tristate "UFS file system support (read only)"
1352 help
1353 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
1354 OpenBSD and NeXTstep) use a file system called UFS. Some System V
1355 Unixes can create and mount hard disk partitions and diskettes using
1356 this file system as well. Saying Y here will allow you to read from
1357 these partitions; if you also want to write to them, say Y to the
1358 experimental "UFS file system write support", below. Please read the
1359 file <file:Documentation/filesystems/ufs.txt> for more information.
1360
1361 The recently released UFS2 variant (used in FreeBSD 5.x) is
1362 READ-ONLY supported.
1363
1364 If you only intend to mount files from some other Unix over the
1365 network using NFS, you don't need the UFS file system support (but
1366 you need NFS file system support obviously).
1367
1368 Note that this option is generally not needed for floppies, since a
1369 good portable way to transport files and directories between unixes
1370 (and even other operating systems) is given by the tar program ("man
1371 tar" or preferably "info tar").
1372
1373 When accessing NeXTstep files, you may need to convert them from the
1374 NeXT character set to the Latin1 character set; use the program
1375 recode ("info recode") for this purpose.
1376
1377 To compile the UFS file system support as a module, choose M here: the
1378 module will be called ufs.
1379
1380 If you haven't heard about all of this before, it's safe to say N.
1381
1382config UFS_FS_WRITE
1383 bool "UFS file system write support (DANGEROUS)"
Evgeniy Dushistov5afb3142006-06-25 05:47:24 -07001384 depends on UFS_FS && EXPERIMENTAL
Linus Torvalds1da177e2005-04-16 15:20:36 -07001385 help
1386 Say Y here if you want to try writing to UFS partitions. This is
1387 experimental, so you should back up your UFS partitions beforehand.
1388
Evgeniy Dushistovabf5d152006-06-25 05:47:24 -07001389config UFS_DEBUG
1390 bool "UFS debugging"
1391 depends on UFS_FS
1392 help
1393 If you are experiencing any problems with the UFS filesystem, say
1394 Y here. This will result in _many_ additional debugging messages to be
1395 written to the system log.
1396
Linus Torvalds1da177e2005-04-16 15:20:36 -07001397endmenu
1398
1399menu "Network File Systems"
1400 depends on NET
1401
1402config NFS_FS
1403 tristate "NFS file system support"
1404 depends on INET
1405 select LOCKD
1406 select SUNRPC
Andreas Gruenbacherb7fa0552005-06-22 17:16:27 +00001407 select NFS_ACL_SUPPORT if NFS_V3_ACL
Linus Torvalds1da177e2005-04-16 15:20:36 -07001408 help
1409 If you are connected to some other (usually local) Unix computer
1410 (using SLIP, PLIP, PPP or Ethernet) and want to mount files residing
1411 on that computer (the NFS server) using the Network File Sharing
1412 protocol, say Y. "Mounting files" means that the client can access
1413 the files with usual UNIX commands as if they were sitting on the
1414 client's hard disk. For this to work, the server must run the
1415 programs nfsd and mountd (but does not need to have NFS file system
1416 support enabled in its kernel). NFS is explained in the Network
1417 Administrator's Guide, available from
1418 <http://www.tldp.org/docs.html#guide>, on its man page: "man
1419 nfs", and in the NFS-HOWTO.
1420
1421 A superior but less widely used alternative to NFS is provided by
1422 the Coda file system; see "Coda file system support" below.
1423
1424 If you say Y here, you should have said Y to TCP/IP networking also.
1425 This option would enlarge your kernel by about 27 KB.
1426
1427 To compile this file system support as a module, choose M here: the
1428 module will be called nfs.
1429
1430 If you are configuring a diskless machine which will mount its root
1431 file system over NFS at boot time, say Y here and to "Kernel
1432 level IP autoconfiguration" above and to "Root file system on NFS"
1433 below. You cannot compile this driver as a module in this case.
1434 There are two packages designed for booting diskless machines over
1435 the net: netboot, available from
1436 <http://ftp1.sourceforge.net/netboot/>, and Etherboot,
1437 available from <http://ftp1.sourceforge.net/etherboot/>.
1438
1439 If you don't know what all this is about, say N.
1440
1441config NFS_V3
1442 bool "Provide NFSv3 client support"
1443 depends on NFS_FS
1444 help
1445 Say Y here if you want your NFS client to be able to speak version
1446 3 of the NFS protocol.
1447
1448 If unsure, say Y.
1449
Andreas Gruenbacherb7fa0552005-06-22 17:16:27 +00001450config NFS_V3_ACL
1451 bool "Provide client support for the NFSv3 ACL protocol extension"
1452 depends on NFS_V3
1453 help
1454 Implement the NFSv3 ACL protocol extension for manipulating POSIX
1455 Access Control Lists. The server should also be compiled with
1456 the NFSv3 ACL protocol extension; see the CONFIG_NFSD_V3_ACL option.
1457
1458 If unsure, say N.
1459
Linus Torvalds1da177e2005-04-16 15:20:36 -07001460config NFS_V4
1461 bool "Provide NFSv4 client support (EXPERIMENTAL)"
1462 depends on NFS_FS && EXPERIMENTAL
1463 select RPCSEC_GSS_KRB5
1464 help
1465 Say Y here if you want your NFS client to be able to speak the newer
1466 version 4 of the NFS protocol.
1467
1468 Note: Requires auxiliary userspace daemons which may be found on
1469 http://www.citi.umich.edu/projects/nfsv4/
1470
1471 If unsure, say N.
1472
1473config NFS_DIRECTIO
Chuck Lever026ed5c2006-09-20 14:33:07 -04001474 bool "Allow direct I/O on NFS files"
1475 depends on NFS_FS
Linus Torvalds1da177e2005-04-16 15:20:36 -07001476 help
1477 This option enables applications to perform uncached I/O on files
1478 in NFS file systems using the O_DIRECT open() flag. When O_DIRECT
1479 is set for a file, its data is not cached in the system's page
1480 cache. Data is moved to and from user-level application buffers
1481 directly. Unlike local disk-based file systems, NFS O_DIRECT has
1482 no alignment restrictions.
1483
1484 Unless your program is designed to use O_DIRECT properly, you are
1485 much better off allowing the NFS client to manage data caching for
1486 you. Misusing O_DIRECT can cause poor server performance or network
1487 storms. This kernel build option defaults OFF to avoid exposing
1488 system administrators unwittingly to a potentially hazardous
1489 feature.
1490
1491 For more details on NFS O_DIRECT, see fs/nfs/direct.c.
1492
1493 If unsure, say N. This reduces the size of the NFS client, and
1494 causes open() to return EINVAL if a file residing in NFS is
1495 opened with the O_DIRECT flag.
1496
1497config NFSD
1498 tristate "NFS server support"
1499 depends on INET
1500 select LOCKD
1501 select SUNRPC
1502 select EXPORTFS
Herbert Xuf05e15b2006-06-26 00:25:39 -07001503 select NFSD_V2_ACL if NFSD_V3_ACL
1504 select NFS_ACL_SUPPORT if NFSD_V2_ACL
1505 select NFSD_TCP if NFSD_V4
1506 select CRYPTO_MD5 if NFSD_V4
1507 select CRYPTO if NFSD_V4
1508 select FS_POSIX_ACL if NFSD_V4
Linus Torvalds1da177e2005-04-16 15:20:36 -07001509 help
1510 If you want your Linux box to act as an NFS *server*, so that other
1511 computers on your local network which support NFS can access certain
1512 directories on your box transparently, you have two options: you can
1513 use the self-contained user space program nfsd, in which case you
1514 should say N here, or you can say Y and use the kernel based NFS
1515 server. The advantage of the kernel based solution is that it is
1516 faster.
1517
1518 In either case, you will need support software; the respective
1519 locations are given in the file <file:Documentation/Changes> in the
1520 NFS section.
1521
1522 If you say Y here, you will get support for version 2 of the NFS
1523 protocol (NFSv2). If you also want NFSv3, say Y to the next question
1524 as well.
1525
1526 Please read the NFS-HOWTO, available from
1527 <http://www.tldp.org/docs.html#howto>.
1528
1529 To compile the NFS server support as a module, choose M here: the
1530 module will be called nfsd. If unsure, say N.
1531
Andreas Gruenbachera257cdd2005-06-22 17:16:26 +00001532config NFSD_V2_ACL
1533 bool
1534 depends on NFSD
1535
Linus Torvalds1da177e2005-04-16 15:20:36 -07001536config NFSD_V3
1537 bool "Provide NFSv3 server support"
1538 depends on NFSD
1539 help
1540 If you would like to include the NFSv3 server as well as the NFSv2
1541 server, say Y here. If unsure, say Y.
1542
Andreas Gruenbachera257cdd2005-06-22 17:16:26 +00001543config NFSD_V3_ACL
1544 bool "Provide server support for the NFSv3 ACL protocol extension"
1545 depends on NFSD_V3
Andreas Gruenbachera257cdd2005-06-22 17:16:26 +00001546 help
1547 Implement the NFSv3 ACL protocol extension for manipulating POSIX
1548 Access Control Lists on exported file systems. NFS clients should
1549 be compiled with the NFSv3 ACL protocol extension; see the
1550 CONFIG_NFS_V3_ACL option. If unsure, say N.
1551
Linus Torvalds1da177e2005-04-16 15:20:36 -07001552config NFSD_V4
1553 bool "Provide NFSv4 server support (EXPERIMENTAL)"
1554 depends on NFSD_V3 && EXPERIMENTAL
Linus Torvalds1da177e2005-04-16 15:20:36 -07001555 help
1556 If you would like to include the NFSv4 server as well as the NFSv2
1557 and NFSv3 servers, say Y here. This feature is experimental, and
1558 should only be used if you are interested in helping to test NFSv4.
1559 If unsure, say N.
1560
1561config NFSD_TCP
1562 bool "Provide NFS server over TCP support"
1563 depends on NFSD
1564 default y
1565 help
1566 If you want your NFS server to support TCP connections, say Y here.
1567 TCP connections usually perform better than the default UDP when
1568 the network is lossy or congested. If unsure, say Y.
1569
1570config ROOT_NFS
1571 bool "Root file system on NFS"
1572 depends on NFS_FS=y && IP_PNP
1573 help
1574 If you want your Linux box to mount its whole root file system (the
1575 one containing the directory /) from some other computer over the
1576 net via NFS (presumably because your box doesn't have a hard disk),
1577 say Y. Read <file:Documentation/nfsroot.txt> for details. It is
1578 likely that in this case, you also want to say Y to "Kernel level IP
1579 autoconfiguration" so that your box can discover its network address
1580 at boot time.
1581
1582 Most people say N here.
1583
1584config LOCKD
1585 tristate
1586
1587config LOCKD_V4
1588 bool
1589 depends on NFSD_V3 || NFS_V3
1590 default y
1591
1592config EXPORTFS
1593 tristate
1594
Andreas Gruenbachera257cdd2005-06-22 17:16:26 +00001595config NFS_ACL_SUPPORT
1596 tristate
1597 select FS_POSIX_ACL
1598
1599config NFS_COMMON
1600 bool
1601 depends on NFSD || NFS_FS
1602 default y
1603
Linus Torvalds1da177e2005-04-16 15:20:36 -07001604config SUNRPC
1605 tristate
1606
1607config SUNRPC_GSS
1608 tristate
1609
1610config RPCSEC_GSS_KRB5
1611 tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
1612 depends on SUNRPC && EXPERIMENTAL
1613 select SUNRPC_GSS
1614 select CRYPTO
1615 select CRYPTO_MD5
1616 select CRYPTO_DES
1617 help
1618 Provides for secure RPC calls by means of a gss-api
1619 mechanism based on Kerberos V5. This is required for
1620 NFSv4.
1621
1622 Note: Requires an auxiliary userspace daemon which may be found on
1623 http://www.citi.umich.edu/projects/nfsv4/
1624
1625 If unsure, say N.
1626
1627config RPCSEC_GSS_SPKM3
1628 tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
1629 depends on SUNRPC && EXPERIMENTAL
1630 select SUNRPC_GSS
1631 select CRYPTO
1632 select CRYPTO_MD5
1633 select CRYPTO_DES
J. Bruce Fieldsdf6db302006-03-20 23:25:10 -05001634 select CRYPTO_CAST5
Linus Torvalds1da177e2005-04-16 15:20:36 -07001635 help
1636 Provides for secure RPC calls by means of a gss-api
1637 mechanism based on the SPKM3 public-key mechanism.
1638
1639 Note: Requires an auxiliary userspace daemon which may be found on
1640 http://www.citi.umich.edu/projects/nfsv4/
1641
1642 If unsure, say N.
1643
1644config SMB_FS
1645 tristate "SMB file system support (to mount Windows shares etc.)"
1646 depends on INET
1647 select NLS
1648 help
1649 SMB (Server Message Block) is the protocol Windows for Workgroups
1650 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
1651 files and printers over local networks. Saying Y here allows you to
1652 mount their file systems (often called "shares" in this context) and
1653 access them just like any other Unix directory. Currently, this
1654 works only if the Windows machines use TCP/IP as the underlying
1655 transport protocol, and not NetBEUI. For details, read
1656 <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
1657 available from <http://www.tldp.org/docs.html#howto>.
1658
1659 Note: if you just want your box to act as an SMB *server* and make
1660 files and printing services available to Windows clients (which need
1661 to have a TCP/IP stack), you don't need to say Y here; you can use
1662 the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
1663 for that.
1664
1665 General information about how to connect Linux, Windows machines and
1666 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1667
1668 To compile the SMB support as a module, choose M here: the module will
1669 be called smbfs. Most people say N, however.
1670
1671config SMB_NLS_DEFAULT
1672 bool "Use a default NLS"
1673 depends on SMB_FS
1674 help
1675 Enabling this will make smbfs use nls translations by default. You
1676 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
1677 settings and you need to give the default nls for the SMB server as
1678 CONFIG_SMB_NLS_REMOTE.
1679
1680 The nls settings can be changed at mount time, if your smbmount
1681 supports that, using the codepage and iocharset parameters.
1682
1683 smbmount from samba 2.2.0 or later supports this.
1684
1685config SMB_NLS_REMOTE
1686 string "Default Remote NLS Option"
1687 depends on SMB_NLS_DEFAULT
1688 default "cp437"
1689 help
1690 This setting allows you to specify a default value for which
1691 codepage the server uses. If this field is left blank no
1692 translations will be done by default. The local codepage/charset
1693 default to CONFIG_NLS_DEFAULT.
1694
1695 The nls settings can be changed at mount time, if your smbmount
1696 supports that, using the codepage and iocharset parameters.
1697
1698 smbmount from samba 2.2.0 or later supports this.
1699
1700config CIFS
1701 tristate "CIFS support (advanced network filesystem for Samba, Window and other CIFS compliant servers)"
1702 depends on INET
1703 select NLS
1704 help
1705 This is the client VFS module for the Common Internet File System
1706 (CIFS) protocol which is the successor to the Server Message Block
1707 (SMB) protocol, the native file sharing mechanism for most early
1708 PC operating systems. The CIFS protocol is fully supported by
1709 file servers such as Windows 2000 (including Windows 2003, NT 4
1710 and Windows XP) as well by Samba (which provides excellent CIFS
Steve Frenchec58ef02005-11-04 09:44:33 -08001711 server support for Linux and many other operating systems). Limited
1712 support for Windows ME and similar servers is provided as well.
1713 You must use the smbfs client filesystem to access older SMB servers
1714 such as OS/2 and DOS.
Linus Torvalds1da177e2005-04-16 15:20:36 -07001715
1716 The intent of the cifs module is to provide an advanced
1717 network file system client for mounting to CIFS compliant servers,
1718 including support for dfs (hierarchical name space), secure per-user
1719 session establishment, safe distributed caching (oplock), optional
1720 packet signing, Unicode and other internationalization improvements,
1721 and optional Winbind (nsswitch) integration. You do not need to enable
1722 cifs if running only a (Samba) server. It is possible to enable both
1723 smbfs and cifs (e.g. if you are using CIFS for accessing Windows 2003
1724 and Samba 3 servers, and smbfs for accessing old servers). If you need
Steve Frenchec58ef02005-11-04 09:44:33 -08001725 to mount to Samba or Windows from this machine, say Y.
Linus Torvalds1da177e2005-04-16 15:20:36 -07001726
1727config CIFS_STATS
1728 bool "CIFS statistics"
1729 depends on CIFS
1730 help
1731 Enabling this option will cause statistics for each server share
1732 mounted by the cifs client to be displayed in /proc/fs/cifs/Stats
1733
Steve Frenchec58ef02005-11-04 09:44:33 -08001734config CIFS_STATS2
Steve French39798772006-05-31 22:40:51 +00001735 bool "Extended statistics"
Steve Frenchec58ef02005-11-04 09:44:33 -08001736 depends on CIFS_STATS
1737 help
1738 Enabling this option will allow more detailed statistics on SMB
1739 request timing to be displayed in /proc/fs/cifs/DebugData and also
1740 allow optional logging of slow responses to dmesg (depending on the
1741 value of /proc/fs/cifs/cifsFYI, see fs/cifs/README for more details).
1742 These additional statistics may have a minor effect on performance
1743 and memory utilization.
1744
1745 Unless you are a developer or are doing network performance analysis
1746 or tuning, say N.
1747
Steve French39798772006-05-31 22:40:51 +00001748config CIFS_WEAK_PW_HASH
1749 bool "Support legacy servers which use weaker LANMAN security"
1750 depends on CIFS
1751 help
1752 Modern CIFS servers including Samba and most Windows versions
1753 (since 1997) support stronger NTLM (and even NTLMv2 and Kerberos)
1754 security mechanisms. These hash the password more securely
1755 than the mechanisms used in the older LANMAN version of the
1756 SMB protocol needed to establish sessions with old SMB servers.
1757
1758 Enabling this option allows the cifs module to mount to older
1759 LANMAN based servers such as OS/2 and Windows 95, but such
1760 mounts may be less secure than mounts using NTLM or more recent
1761 security mechanisms if you are on a public network. Unless you
1762 have a need to access old SMB servers (and are on a private
1763 network) you probably want to say N. Even if this support
1764 is enabled in the kernel build, they will not be used
1765 automatically. At runtime LANMAN mounts are disabled but
1766 can be set to required (or optional) either in
1767 /proc/fs/cifs (see fs/cifs/README for more detail) or via an
1768 option on the mount command. This support is disabled by
1769 default in order to reduce the possibility of a downgrade
1770 attack.
1771
1772 If unsure, say N.
1773
Linus Torvalds1da177e2005-04-16 15:20:36 -07001774config CIFS_XATTR
Steve Frenchec58ef02005-11-04 09:44:33 -08001775 bool "CIFS extended attributes"
Linus Torvalds1da177e2005-04-16 15:20:36 -07001776 depends on CIFS
1777 help
1778 Extended attributes are name:value pairs associated with inodes by
1779 the kernel or by users (see the attr(5) manual page, or visit
1780 <http://acl.bestbits.at/> for details). CIFS maps the name of
1781 extended attributes beginning with the user namespace prefix
1782 to SMB/CIFS EAs. EAs are stored on Windows servers without the
1783 user namespace prefix, but their names are seen by Linux cifs clients
1784 prefaced by the user namespace prefix. The system namespace
1785 (used by some filesystems to store ACLs) is not supported at
1786 this time.
Steve Frenchec58ef02005-11-04 09:44:33 -08001787
Linus Torvalds1da177e2005-04-16 15:20:36 -07001788 If unsure, say N.
1789
1790config CIFS_POSIX
Steve Frenchec58ef02005-11-04 09:44:33 -08001791 bool "CIFS POSIX Extensions"
Linus Torvalds1da177e2005-04-16 15:20:36 -07001792 depends on CIFS_XATTR
1793 help
1794 Enabling this option will cause the cifs client to attempt to
1795 negotiate a newer dialect with servers, such as Samba 3.0.5
1796 or later, that optionally can handle more POSIX like (rather
1797 than Windows like) file behavior. It also enables
1798 support for POSIX ACLs (getfacl and setfacl) to servers
1799 (such as Samba 3.10 and later) which can negotiate
1800 CIFS POSIX ACL support. If unsure, say N.
1801
Steve French39798772006-05-31 22:40:51 +00001802config CIFS_DEBUG2
Steve French3856a9d2006-06-01 19:38:46 +00001803 bool "Enable additional CIFS debugging routines"
Steve French8ba10ab2006-07-08 02:17:40 +00001804 depends on CIFS
Steve French39798772006-05-31 22:40:51 +00001805 help
1806 Enabling this option adds a few more debugging routines
1807 to the cifs code which slightly increases the size of
1808 the cifs module and can cause additional logging of debug
1809 messages in some error paths, slowing performance. This
1810 option can be turned off unless you are debugging
1811 cifs problems. If unsure, say N.
1812
Linus Torvalds1da177e2005-04-16 15:20:36 -07001813config CIFS_EXPERIMENTAL
1814 bool "CIFS Experimental Features (EXPERIMENTAL)"
Steve Frenchcb9dbff2005-11-02 11:37:15 -08001815 depends on CIFS && EXPERIMENTAL
Linus Torvalds1da177e2005-04-16 15:20:36 -07001816 help
Steve Frenchec58ef02005-11-04 09:44:33 -08001817 Enables cifs features under testing. These features are
1818 experimental and currently include support for writepages
1819 (multipage writebehind performance improvements) and directory
1820 change notification ie fcntl(F_DNOTIFY) as well as some security
1821 improvements. Some also depend on setting at runtime the
1822 pseudo-file /proc/fs/cifs/Experimental (which is disabled by
1823 default). See the file fs/cifs/README for more details.
1824
1825 If unsure, say N.
Linus Torvalds1da177e2005-04-16 15:20:36 -07001826
Steve Frencha2653eb2005-11-10 15:33:38 -08001827config CIFS_UPCALL
Steve French39798772006-05-31 22:40:51 +00001828 bool "Kerberos/SPNEGO advanced session setup (EXPERIMENTAL)"
Steve Frencha2653eb2005-11-10 15:33:38 -08001829 depends on CIFS_EXPERIMENTAL
1830 select CONNECTOR
1831 help
1832 Enables an upcall mechanism for CIFS which will be used to contact
1833 userspace helper utilities to provide SPNEGO packaged Kerberos
1834 tickets which are needed to mount to certain secure servers
Steve French1b397f42005-11-10 19:36:39 -08001835 (for which more secure Kerberos authentication is required). If
1836 unsure, say N.
Steve Frencha2653eb2005-11-10 15:33:38 -08001837
Linus Torvalds1da177e2005-04-16 15:20:36 -07001838config NCP_FS
1839 tristate "NCP file system support (to mount NetWare volumes)"
1840 depends on IPX!=n || INET
1841 help
1842 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
1843 used by Novell NetWare clients to talk to file servers. It is to
1844 IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
1845 to mount NetWare file server volumes and to access them just like
1846 any other Unix directory. For details, please read the file
1847 <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
1848 the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
1849
1850 You do not have to say Y here if you want your Linux box to act as a
1851 file *server* for Novell NetWare clients.
1852
1853 General information about how to connect Linux, Windows machines and
1854 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1855
1856 To compile this as a module, choose M here: the module will be called
1857 ncpfs. Say N unless you are connected to a Novell network.
1858
1859source "fs/ncpfs/Kconfig"
1860
1861config CODA_FS
1862 tristate "Coda file system support (advanced network fs)"
1863 depends on INET
1864 help
1865 Coda is an advanced network file system, similar to NFS in that it
1866 enables you to mount file systems of a remote server and access them
1867 with regular Unix commands as if they were sitting on your hard
1868 disk. Coda has several advantages over NFS: support for
1869 disconnected operation (e.g. for laptops), read/write server
1870 replication, security model for authentication and encryption,
1871 persistent client caches and write back caching.
1872
1873 If you say Y here, your Linux box will be able to act as a Coda
1874 *client*. You will need user level code as well, both for the
1875 client and server. Servers are currently user level, i.e. they need
1876 no kernel support. Please read
1877 <file:Documentation/filesystems/coda.txt> and check out the Coda
1878 home page <http://www.coda.cs.cmu.edu/>.
1879
1880 To compile the coda client support as a module, choose M here: the
1881 module will be called coda.
1882
1883config CODA_FS_OLD_API
1884 bool "Use 96-bit Coda file identifiers"
1885 depends on CODA_FS
1886 help
1887 A new kernel-userspace API had to be introduced for Coda v6.0
1888 to support larger 128-bit file identifiers as needed by the
1889 new realms implementation.
1890
1891 However this new API is not backward compatible with older
1892 clients. If you really need to run the old Coda userspace
1893 cache manager then say Y.
1894
1895 For most cases you probably want to say N.
1896
1897config AFS_FS
1898# for fs/nls/Config.in
1899 tristate "Andrew File System support (AFS) (Experimental)"
1900 depends on INET && EXPERIMENTAL
1901 select RXRPC
1902 help
1903 If you say Y here, you will get an experimental Andrew File System
1904 driver. It currently only supports unsecured read-only AFS access.
1905
1906 See <file:Documentation/filesystems/afs.txt> for more intormation.
1907
1908 If unsure, say N.
1909
1910config RXRPC
1911 tristate
1912
Eric Van Hensbergen93fa58c2005-09-09 13:04:18 -07001913config 9P_FS
1914 tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
1915 depends on INET && EXPERIMENTAL
1916 help
1917 If you say Y here, you will get experimental support for
1918 Plan 9 resource sharing via the 9P2000 protocol.
1919
1920 See <http://v9fs.sf.net> for more information.
1921
1922 If unsure, say N.
1923
Linus Torvalds1da177e2005-04-16 15:20:36 -07001924endmenu
1925
1926menu "Partition Types"
1927
1928source "fs/partitions/Kconfig"
1929
1930endmenu
1931
1932source "fs/nls/Kconfig"
1933
1934endmenu
1935