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