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