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