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