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