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