blob: f9b5842c8d2de67e6f9258f65fad1fc6207b9242 [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"
326
Mark Fashehb4e40a52005-12-15 14:31:24 -0800327config OCFS2_FS
328 tristate "OCFS2 file system support (EXPERIMENTAL)"
329 depends on NET && EXPERIMENTAL
330 select CONFIGFS_FS
331 select JBD
332 select CRC32
333 select INET
334 help
335 OCFS2 is a general purpose extent based shared disk cluster file
336 system with many similarities to ext3. It supports 64 bit inode
337 numbers, and has automatically extending metadata groups which may
338 also make it attractive for non-clustered use.
339
340 You'll want to install the ocfs2-tools package in order to at least
341 get "mount.ocfs2".
342
343 Project web page: http://oss.oracle.com/projects/ocfs2
344 Tools web page: http://oss.oracle.com/projects/ocfs2-tools
345 OCFS2 mailing lists: http://oss.oracle.com/projects/ocfs2/mailman/
346
347 Note: Features which OCFS2 does not support yet:
348 - extended attributes
Mark Fashehb4e40a52005-12-15 14:31:24 -0800349 - shared writeable mmap
350 - loopback is supported, but data written will not
351 be cluster coherent.
352 - quotas
353 - cluster aware flock
354 - Directory change notification (F_NOTIFY)
355 - Distributed Caching (F_SETLEASE/F_GETLEASE/break_lease)
356 - POSIX ACLs
357 - readpages / writepages (not user visible)
358
Linus Torvalds1da177e2005-04-16 15:20:36 -0700359config MINIX_FS
360 tristate "Minix fs support"
361 help
362 Minix is a simple operating system used in many classes about OS's.
363 The minix file system (method to organize files on a hard disk
364 partition or a floppy disk) was the original file system for Linux,
365 but has been superseded by the second extended file system ext2fs.
366 You don't want to use the minix file system on your hard disk
367 because of certain built-in restrictions, but it is sometimes found
368 on older Linux floppy disks. This option will enlarge your kernel
369 by about 28 KB. If unsure, say N.
370
371 To compile this file system support as a module, choose M here: the
372 module will be called minix. Note that the file system of your root
373 partition (the one containing the directory /) cannot be compiled as
374 a module.
375
376config ROMFS_FS
377 tristate "ROM file system support"
378 ---help---
379 This is a very small read-only file system mainly intended for
380 initial ram disks of installation disks, but it could be used for
381 other read-only media as well. Read
382 <file:Documentation/filesystems/romfs.txt> for details.
383
384 To compile this file system support as a module, choose M here: the
385 module will be called romfs. Note that the file system of your
386 root partition (the one containing the directory /) cannot be a
387 module.
388
389 If you don't know whether you need it, then you don't need it:
390 answer N.
391
Robert Love0eeca282005-07-12 17:06:03 -0400392config INOTIFY
393 bool "Inotify file change notification support"
394 default y
395 ---help---
Robert Love3de11742005-08-04 13:07:08 -0700396 Say Y here to enable inotify support and the associated system
397 calls. Inotify is a file change notification system and a
Robert Love0eeca282005-07-12 17:06:03 -0400398 replacement for dnotify. Inotify fixes numerous shortcomings in
399 dnotify and introduces several new features. It allows monitoring
Robert Love3de11742005-08-04 13:07:08 -0700400 of both files and directories via a single open fd. Other features
401 include multiple file events, one-shot support, and unmount
402 notification.
403
404 For more information, see Documentation/filesystems/inotify.txt
Robert Love0eeca282005-07-12 17:06:03 -0400405
406 If unsure, say Y.
407
Linus Torvalds1da177e2005-04-16 15:20:36 -0700408config QUOTA
409 bool "Quota support"
410 help
411 If you say Y here, you will be able to set per user limits for disk
412 usage (also called disk quotas). Currently, it works for the
413 ext2, ext3, and reiserfs file system. ext3 also supports journalled
414 quotas for which you don't need to run quotacheck(8) after an unclean
Adrian Bunk919532a2005-09-06 15:17:22 -0700415 shutdown.
416 For further details, read the Quota mini-HOWTO, available from
Linus Torvalds1da177e2005-04-16 15:20:36 -0700417 <http://www.tldp.org/docs.html#howto>, or the documentation provided
418 with the quota tools. Probably the quota support is only useful for
419 multi user systems. If unsure, say N.
420
421config QFMT_V1
422 tristate "Old quota format support"
423 depends on QUOTA
424 help
425 This quota format was (is) used by kernels earlier than 2.4.22. If
426 you have quota working and you don't want to convert to new quota
427 format say Y here.
428
429config QFMT_V2
430 tristate "Quota format v2 support"
431 depends on QUOTA
432 help
433 This quota format allows using quotas with 32-bit UIDs/GIDs. If you
Adrian Bunk919532a2005-09-06 15:17:22 -0700434 need this functionality say Y here.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700435
436config QUOTACTL
437 bool
438 depends on XFS_QUOTA || QUOTA
439 default y
440
441config DNOTIFY
442 bool "Dnotify support" if EMBEDDED
443 default y
444 help
445 Dnotify is a directory-based per-fd file change notification system
446 that uses signals to communicate events to user-space. There exist
447 superior alternatives, but some applications may still rely on
448 dnotify.
449
450 Because of this, if unsure, say Y.
451
452config AUTOFS_FS
453 tristate "Kernel automounter support"
454 help
455 The automounter is a tool to automatically mount remote file systems
456 on demand. This implementation is partially kernel-based to reduce
457 overhead in the already-mounted case; this is unlike the BSD
458 automounter (amd), which is a pure user space daemon.
459
460 To use the automounter you need the user-space tools from the autofs
461 package; you can find the location in <file:Documentation/Changes>.
462 You also want to answer Y to "NFS file system support", below.
463
464 If you want to use the newer version of the automounter with more
465 features, say N here and say Y to "Kernel automounter v4 support",
466 below.
467
468 To compile this support as a module, choose M here: the module will be
469 called autofs.
470
471 If you are not a part of a fairly large, distributed network, you
472 probably do not need an automounter, and can say N here.
473
474config AUTOFS4_FS
475 tristate "Kernel automounter version 4 support (also supports v3)"
476 help
477 The automounter is a tool to automatically mount remote file systems
478 on demand. This implementation is partially kernel-based to reduce
479 overhead in the already-mounted case; this is unlike the BSD
480 automounter (amd), which is a pure user space daemon.
481
482 To use the automounter you need the user-space tools from
483 <ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4/>; you also
484 want to answer Y to "NFS file system support", below.
485
486 To compile this support as a module, choose M here: the module will be
487 called autofs4. You will need to add "alias autofs autofs4" to your
488 modules configuration file.
489
490 If you are not a part of a fairly large, distributed network or
491 don't have a laptop which needs to dynamically reconfigure to the
492 local network, you probably do not need an automounter, and can say
493 N here.
494
Miklos Szeredi04578f12005-09-09 13:10:22 -0700495config FUSE_FS
496 tristate "Filesystem in Userspace support"
497 help
498 With FUSE it is possible to implement a fully functional filesystem
499 in a userspace program.
500
501 There's also companion library: libfuse. This library along with
502 utilities is available from the FUSE homepage:
503 <http://fuse.sourceforge.net/>
504
Miklos Szeredi909021e2005-09-27 21:45:20 -0700505 See <file:Documentation/filesystems/fuse.txt> for more information.
506 See <file:Documentation/Changes> for needed library/utility version.
507
Miklos Szeredi04578f12005-09-09 13:10:22 -0700508 If you want to develop a userspace FS, or if you want to use
509 a filesystem based on FUSE, answer Y or M.
510
Linus Torvalds1da177e2005-04-16 15:20:36 -0700511menu "CD-ROM/DVD Filesystems"
512
513config ISO9660_FS
514 tristate "ISO 9660 CDROM file system support"
515 help
516 This is the standard file system used on CD-ROMs. It was previously
517 known as "High Sierra File System" and is called "hsfs" on other
518 Unix systems. The so-called Rock-Ridge extensions which allow for
519 long Unix filenames and symbolic links are also supported by this
520 driver. If you have a CD-ROM drive and want to do more with it than
521 just listen to audio CDs and watch its LEDs, say Y (and read
522 <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO,
523 available from <http://www.tldp.org/docs.html#howto>), thereby
524 enlarging your kernel by about 27 KB; otherwise say N.
525
526 To compile this file system support as a module, choose M here: the
527 module will be called isofs.
528
529config JOLIET
530 bool "Microsoft Joliet CDROM extensions"
531 depends on ISO9660_FS
532 select NLS
533 help
534 Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system
535 which allows for long filenames in unicode format (unicode is the
536 new 16 bit character code, successor to ASCII, which encodes the
537 characters of almost all languages of the world; see
538 <http://www.unicode.org/> for more information). Say Y here if you
539 want to be able to read Joliet CD-ROMs under Linux.
540
541config ZISOFS
542 bool "Transparent decompression extension"
543 depends on ISO9660_FS
544 select ZLIB_INFLATE
545 help
546 This is a Linux-specific extension to RockRidge which lets you store
547 data in compressed form on a CD-ROM and have it transparently
548 decompressed when the CD-ROM is accessed. See
549 <http://www.kernel.org/pub/linux/utils/fs/zisofs/> for the tools
550 necessary to create such a filesystem. Say Y here if you want to be
551 able to read such compressed CD-ROMs.
552
553config ZISOFS_FS
554# for fs/nls/Config.in
555 tristate
556 depends on ZISOFS
557 default ISO9660_FS
558
559config UDF_FS
560 tristate "UDF file system support"
561 help
562 This is the new file system used on some CD-ROMs and DVDs. Say Y if
563 you intend to mount DVD discs or CDRW's written in packet mode, or
564 if written to by other UDF utilities, such as DirectCD.
565 Please read <file:Documentation/filesystems/udf.txt>.
566
567 To compile this file system support as a module, choose M here: the
568 module will be called udf.
569
570 If unsure, say N.
571
572config UDF_NLS
573 bool
574 default y
575 depends on (UDF_FS=m && NLS) || (UDF_FS=y && NLS=y)
576
577endmenu
578
579menu "DOS/FAT/NT Filesystems"
580
581config FAT_FS
582 tristate
583 select NLS
584 help
585 If you want to use one of the FAT-based file systems (the MS-DOS and
586 VFAT (Windows 95) file systems), then you must say Y or M here
587 to include FAT support. You will then be able to mount partitions or
588 diskettes with FAT-based file systems and transparently access the
589 files on them, i.e. MSDOS files will look and behave just like all
590 other Unix files.
591
592 This FAT support is not a file system in itself, it only provides
593 the foundation for the other file systems. You will have to say Y or
594 M to at least one of "MSDOS fs support" or "VFAT fs support" in
595 order to make use of it.
596
597 Another way to read and write MSDOS floppies and hard drive
598 partitions from within Linux (but not transparently) is with the
599 mtools ("man mtools") program suite. You don't need to say Y here in
600 order to do that.
601
602 If you need to move large files on floppies between a DOS and a
603 Linux box, say Y here, mount the floppy under Linux with an MSDOS
604 file system and use GNU tar's M option. GNU tar is a program
605 available for Unix and DOS ("man tar" or "info tar").
606
607 It is now also becoming possible to read and write compressed FAT
608 file systems; read <file:Documentation/filesystems/fat_cvf.txt> for
609 details.
610
611 The FAT support will enlarge your kernel by about 37 KB. If unsure,
612 say Y.
613
614 To compile this as a module, choose M here: the module will be called
615 fat. Note that if you compile the FAT support as a module, you
616 cannot compile any of the FAT-based file systems into the kernel
617 -- they will have to be modules as well.
618
619config MSDOS_FS
620 tristate "MSDOS fs support"
621 select FAT_FS
622 help
623 This allows you to mount MSDOS partitions of your hard drive (unless
624 they are compressed; to access compressed MSDOS partitions under
625 Linux, you can either use the DOS emulator DOSEMU, described in the
626 DOSEMU-HOWTO, available from
627 <http://www.tldp.org/docs.html#howto>, or try dmsdosfs in
628 <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you
629 intend to use dosemu with a non-compressed MSDOS partition, say Y
630 here) and MSDOS floppies. This means that file access becomes
631 transparent, i.e. the MSDOS files look and behave just like all
632 other Unix files.
633
634 If you have Windows 95 or Windows NT installed on your MSDOS
635 partitions, you should use the VFAT file system (say Y to "VFAT fs
636 support" below), or you will not be able to see the long filenames
637 generated by Windows 95 / Windows NT.
638
639 This option will enlarge your kernel by about 7 KB. If unsure,
640 answer Y. This will only work if you said Y to "DOS FAT fs support"
641 as well. To compile this as a module, choose M here: the module will
642 be called msdos.
643
644config VFAT_FS
645 tristate "VFAT (Windows-95) fs support"
646 select FAT_FS
647 help
648 This option provides support for normal Windows file systems with
649 long filenames. That includes non-compressed FAT-based file systems
650 used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
651 programs from the mtools package.
652
653 The VFAT support enlarges your kernel by about 10 KB and it only
654 works if you said Y to the "DOS FAT fs support" above. Please read
655 the file <file:Documentation/filesystems/vfat.txt> for details. If
656 unsure, say Y.
657
658 To compile this as a module, choose M here: the module will be called
659 vfat.
660
661config FAT_DEFAULT_CODEPAGE
662 int "Default codepage for FAT"
663 depends on MSDOS_FS || VFAT_FS
664 default 437
665 help
666 This option should be set to the codepage of your FAT filesystems.
667 It can be overridden with the "codepage" mount option.
668 See <file:Documentation/filesystems/vfat.txt> for more information.
669
670config FAT_DEFAULT_IOCHARSET
671 string "Default iocharset for FAT"
672 depends on VFAT_FS
673 default "iso8859-1"
674 help
675 Set this to the default input/output character set you'd
676 like FAT to use. It should probably match the character set
677 that most of your FAT filesystems use, and can be overridden
678 with the "iocharset" mount option for FAT filesystems.
679 Note that "utf8" is not recommended for FAT filesystems.
680 If unsure, you shouldn't set "utf8" here.
681 See <file:Documentation/filesystems/vfat.txt> for more information.
682
683config NTFS_FS
684 tristate "NTFS file system support"
685 select NLS
686 help
687 NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003.
688
689 Saying Y or M here enables read support. There is partial, but
690 safe, write support available. For write support you must also
691 say Y to "NTFS write support" below.
692
693 There are also a number of user-space tools available, called
694 ntfsprogs. These include ntfsundelete and ntfsresize, that work
695 without NTFS support enabled in the kernel.
696
697 This is a rewrite from scratch of Linux NTFS support and replaced
698 the old NTFS code starting with Linux 2.5.11. A backport to
699 the Linux 2.4 kernel series is separately available as a patch
700 from the project web site.
701
702 For more information see <file:Documentation/filesystems/ntfs.txt>
703 and <http://linux-ntfs.sourceforge.net/>.
704
705 To compile this file system support as a module, choose M here: the
706 module will be called ntfs.
707
708 If you are not using Windows NT, 2000, XP or 2003 in addition to
709 Linux on your computer it is safe to say N.
710
711config NTFS_DEBUG
712 bool "NTFS debugging support"
713 depends on NTFS_FS
714 help
715 If you are experiencing any problems with the NTFS file system, say
716 Y here. This will result in additional consistency checks to be
717 performed by the driver as well as additional debugging messages to
718 be written to the system log. Note that debugging messages are
719 disabled by default. To enable them, supply the option debug_msgs=1
720 at the kernel command line when booting the kernel or as an option
721 to insmod when loading the ntfs module. Once the driver is active,
722 you can enable debugging messages by doing (as root):
723 echo 1 > /proc/sys/fs/ntfs-debug
724 Replacing the "1" with "0" would disable debug messages.
725
726 If you leave debugging messages disabled, this results in little
727 overhead, but enabling debug messages results in very significant
728 slowdown of the system.
729
730 When reporting bugs, please try to have available a full dump of
731 debugging messages while the misbehaviour was occurring.
732
733config NTFS_RW
734 bool "NTFS write support"
735 depends on NTFS_FS
736 help
737 This enables the partial, but safe, write support in the NTFS driver.
738
739 The only supported operation is overwriting existing files, without
740 changing the file length. No file or directory creation, deletion or
741 renaming is possible. Note only non-resident files can be written to
742 so you may find that some very small files (<500 bytes or so) cannot
743 be written to.
744
745 While we cannot guarantee that it will not damage any data, we have
746 so far not received a single report where the driver would have
747 damaged someones data so we assume it is perfectly safe to use.
748
749 Note: While write support is safe in this version (a rewrite from
750 scratch of the NTFS support), it should be noted that the old NTFS
751 write support, included in Linux 2.5.10 and before (since 1997),
752 is not safe.
753
754 This is currently useful with TopologiLinux. TopologiLinux is run
755 on top of any DOS/Microsoft Windows system without partitioning your
756 hard disk. Unlike other Linux distributions TopologiLinux does not
757 need its own partition. For more information see
758 <http://topologi-linux.sourceforge.net/>
759
760 It is perfectly safe to say N here.
761
762endmenu
763
764menu "Pseudo filesystems"
765
766config PROC_FS
767 bool "/proc file system support"
768 help
769 This is a virtual file system providing information about the status
770 of the system. "Virtual" means that it doesn't take up any space on
771 your hard disk: the files are created on the fly by the kernel when
772 you try to access them. Also, you cannot read the files with older
773 version of the program less: you need to use more or cat.
774
775 It's totally cool; for example, "cat /proc/interrupts" gives
776 information about what the different IRQs are used for at the moment
777 (there is a small number of Interrupt ReQuest lines in your computer
778 that are used by the attached devices to gain the CPU's attention --
779 often a source of trouble if two devices are mistakenly configured
780 to use the same IRQ). The program procinfo to display some
781 information about your system gathered from the /proc file system.
782
783 Before you can use the /proc file system, it has to be mounted,
784 meaning it has to be given a location in the directory hierarchy.
785 That location should be /proc. A command such as "mount -t proc proc
786 /proc" or the equivalent line in /etc/fstab does the job.
787
788 The /proc file system is explained in the file
789 <file:Documentation/filesystems/proc.txt> and on the proc(5) manpage
790 ("man 5 proc").
791
792 This option will enlarge your kernel by about 67 KB. Several
793 programs depend on this, so everyone should say Y here.
794
795config PROC_KCORE
796 bool "/proc/kcore support" if !ARM
797 depends on PROC_FS && MMU
798
Vivek Goyal666bfdd2005-06-25 14:58:21 -0700799config PROC_VMCORE
800 bool "/proc/vmcore support (EXPERIMENTAL)"
Maneesh Soni05970d42006-01-09 20:51:52 -0800801 depends on PROC_FS && EXPERIMENTAL && CRASH_DUMP
Vivek Goyal68250ba2006-04-10 22:54:30 -0700802 default y
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
Arthur Othienodda27d12006-04-18 22:20:57 -0700845 help
846 hugetlbfs is a filesystem backing for HugeTLB pages, based on
847 ramfs. For architectures that support it, say Y here and read
848 <file:Documentation/vm/hugetlbpage.txt> for details.
849
850 If unsure, say N.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700851
852config HUGETLB_PAGE
853 def_bool HUGETLBFS
854
855config RAMFS
856 bool
857 default y
858 ---help---
859 Ramfs is a file system which keeps all files in RAM. It allows
860 read and write access.
861
862 It is more of an programming example than a useable file system. If
863 you need a file system which lives in RAM with limit checking use
864 tmpfs.
865
866 To compile this as a module, choose M here: the module will be called
867 ramfs.
868
Joel Becker7063fbf2005-12-15 14:29:43 -0800869config CONFIGFS_FS
870 tristate "Userspace-driven configuration filesystem (EXPERIMENTAL)"
Adrian Bunk65714b92006-03-26 14:25:52 +0200871 depends on SYSFS && EXPERIMENTAL
Joel Becker7063fbf2005-12-15 14:29:43 -0800872 help
873 configfs is a ram-based filesystem that provides the converse
874 of sysfs's functionality. Where sysfs is a filesystem-based
875 view of kernel objects, configfs is a filesystem-based manager
876 of kernel objects, or config_items.
877
878 Both sysfs and configfs can and should exist together on the
879 same system. One is not a replacement for the other.
880
Linus Torvalds1da177e2005-04-16 15:20:36 -0700881endmenu
882
883menu "Miscellaneous filesystems"
884
885config ADFS_FS
886 tristate "ADFS file system support (EXPERIMENTAL)"
887 depends on EXPERIMENTAL
888 help
889 The Acorn Disc Filing System is the standard file system of the
890 RiscOS operating system which runs on Acorn's ARM-based Risc PC
891 systems and the Acorn Archimedes range of machines. If you say Y
892 here, Linux will be able to read from ADFS partitions on hard drives
893 and from ADFS-formatted floppy discs. If you also want to be able to
894 write to those devices, say Y to "ADFS write support" below.
895
896 The ADFS partition should be the first partition (i.e.,
897 /dev/[hs]d?1) on each of your drives. Please read the file
898 <file:Documentation/filesystems/adfs.txt> for further details.
899
900 To compile this code as a module, choose M here: the module will be
901 called adfs.
902
903 If unsure, say N.
904
905config ADFS_FS_RW
906 bool "ADFS write support (DANGEROUS)"
907 depends on ADFS_FS
908 help
909 If you say Y here, you will be able to write to ADFS partitions on
910 hard drives and ADFS-formatted floppy disks. This is experimental
911 codes, so if you're unsure, say N.
912
913config AFFS_FS
914 tristate "Amiga FFS file system support (EXPERIMENTAL)"
915 depends on EXPERIMENTAL
916 help
917 The Fast File System (FFS) is the common file system used on hard
918 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
919 if you want to be able to read and write files from and to an Amiga
920 FFS partition on your hard drive. Amiga floppies however cannot be
921 read with this driver due to an incompatibility of the floppy
922 controller used in an Amiga and the standard floppy controller in
923 PCs and workstations. Read <file:Documentation/filesystems/affs.txt>
924 and <file:fs/affs/Changes>.
925
926 With this driver you can also mount disk files used by Bernd
927 Schmidt's Un*X Amiga Emulator
928 (<http://www.freiburg.linux.de/~uae/>).
929 If you want to do this, you will also need to say Y or M to "Loop
930 device support", above.
931
932 To compile this file system support as a module, choose M here: the
933 module will be called affs. If unsure, say N.
934
935config HFS_FS
936 tristate "Apple Macintosh file system support (EXPERIMENTAL)"
937 depends on EXPERIMENTAL
Lennert Buytenhek878129a2005-11-07 00:59:18 -0800938 select NLS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700939 help
940 If you say Y here, you will be able to mount Macintosh-formatted
941 floppy disks and hard drive partitions with full read-write access.
942 Please read <file:fs/hfs/HFS.txt> to learn about the available mount
943 options.
944
945 To compile this file system support as a module, choose M here: the
946 module will be called hfs.
947
948config HFSPLUS_FS
949 tristate "Apple Extended HFS file system support"
950 select NLS
951 select NLS_UTF8
952 help
953 If you say Y here, you will be able to mount extended format
954 Macintosh-formatted hard drive partitions with full read-write access.
955
956 This file system is often called HFS+ and was introduced with
957 MacOS 8. It includes all Mac specific filesystem data such as
958 data forks and creator codes, but it also has several UNIX
959 style features such as file ownership and permissions.
960
961config BEFS_FS
962 tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)"
963 depends on EXPERIMENTAL
964 select NLS
965 help
966 The BeOS File System (BeFS) is the native file system of Be, Inc's
967 BeOS. Notable features include support for arbitrary attributes
968 on files and directories, and database-like indeces on selected
969 attributes. (Also note that this driver doesn't make those features
970 available at this time). It is a 64 bit filesystem, so it supports
971 extremly large volumes and files.
972
973 If you use this filesystem, you should also say Y to at least one
974 of the NLS (native language support) options below.
975
976 If you don't know what this is about, say N.
977
978 To compile this as a module, choose M here: the module will be
979 called befs.
980
981config BEFS_DEBUG
982 bool "Debug BeFS"
983 depends on BEFS_FS
984 help
985 If you say Y here, you can use the 'debug' mount option to enable
986 debugging output from the driver.
987
988config BFS_FS
989 tristate "BFS file system support (EXPERIMENTAL)"
990 depends on EXPERIMENTAL
991 help
992 Boot File System (BFS) is a file system used under SCO UnixWare to
993 allow the bootloader access to the kernel image and other important
994 files during the boot process. It is usually mounted under /stand
995 and corresponds to the slice marked as "STAND" in the UnixWare
996 partition. You should say Y if you want to read or write the files
997 on your /stand slice from within Linux. You then also need to say Y
998 to "UnixWare slices support", below. More information about the BFS
999 file system is contained in the file
1000 <file:Documentation/filesystems/bfs.txt>.
1001
1002 If you don't know what this is about, say N.
1003
1004 To compile this as a module, choose M here: the module will be called
1005 bfs. Note that the file system of your root partition (the one
1006 containing the directory /) cannot be compiled as a module.
1007
1008
1009
1010config EFS_FS
1011 tristate "EFS file system support (read only) (EXPERIMENTAL)"
1012 depends on EXPERIMENTAL
1013 help
1014 EFS is an older file system used for non-ISO9660 CD-ROMs and hard
1015 disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
1016 uses the XFS file system for hard disk partitions however).
1017
1018 This implementation only offers read-only access. If you don't know
1019 what all this is about, it's safe to say N. For more information
1020 about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
1021
1022 To compile the EFS file system support as a module, choose M here: the
1023 module will be called efs.
1024
1025config JFFS_FS
1026 tristate "Journalling Flash File System (JFFS) support"
1027 depends on MTD
1028 help
1029 JFFS is the Journaling Flash File System developed by Axis
1030 Communications in Sweden, aimed at providing a crash/powerdown-safe
1031 file system for disk-less embedded devices. Further information is
1032 available at (<http://developer.axis.com/software/jffs/>).
1033
1034config JFFS_FS_VERBOSE
1035 int "JFFS debugging verbosity (0 = quiet, 3 = noisy)"
1036 depends on JFFS_FS
1037 default "0"
1038 help
1039 Determines the verbosity level of the JFFS debugging messages.
1040
1041config JFFS_PROC_FS
1042 bool "JFFS stats available in /proc filesystem"
1043 depends on JFFS_FS && PROC_FS
1044 help
1045 Enabling this option will cause statistics from mounted JFFS file systems
1046 to be made available to the user in the /proc/fs/jffs/ directory.
1047
1048config JFFS2_FS
1049 tristate "Journalling Flash File System v2 (JFFS2) support"
1050 select CRC32
1051 depends on MTD
1052 help
1053 JFFS2 is the second generation of the Journalling Flash File System
1054 for use on diskless embedded devices. It provides improved wear
1055 levelling, compression and support for hard links. You cannot use
1056 this on normal block devices, only on 'MTD' devices.
1057
1058 Further information on the design and implementation of JFFS2 is
1059 available at <http://sources.redhat.com/jffs2/>.
1060
1061config JFFS2_FS_DEBUG
1062 int "JFFS2 debugging verbosity (0 = quiet, 2 = noisy)"
1063 depends on JFFS2_FS
1064 default "0"
1065 help
1066 This controls the amount of debugging messages produced by the JFFS2
1067 code. Set it to zero for use in production systems. For evaluation,
1068 testing and debugging, it's advisable to set it to one. This will
1069 enable a few assertions and will print debugging messages at the
1070 KERN_DEBUG loglevel, where they won't normally be visible. Level 2
1071 is unlikely to be useful - it enables extra debugging in certain
1072 areas which at one point needed debugging, but when the bugs were
1073 located and fixed, the detailed messages were relegated to level 2.
1074
1075 If reporting bugs, please try to have available a full dump of the
1076 messages at debug level 1 while the misbehaviour was occurring.
1077
Andrew Victor2f82ce12005-02-09 09:24:26 +00001078config JFFS2_FS_WRITEBUFFER
1079 bool "JFFS2 write-buffering support"
Linus Torvalds1da177e2005-04-16 15:20:36 -07001080 depends on JFFS2_FS
Andrew Victor2f82ce12005-02-09 09:24:26 +00001081 default y
Linus Torvalds1da177e2005-04-16 15:20:36 -07001082 help
Andrew Victor2f82ce12005-02-09 09:24:26 +00001083 This enables the write-buffering support in JFFS2.
Linus Torvalds1da177e2005-04-16 15:20:36 -07001084
Andrew Victor2f82ce12005-02-09 09:24:26 +00001085 This functionality is required to support JFFS2 on the following
1086 types of flash devices:
1087 - NAND flash
1088 - NOR flash with transparent ECC
1089 - DataFlash
Linus Torvalds1da177e2005-04-16 15:20:36 -07001090
Ferenc Havasie631ddb2005-09-07 09:35:26 +01001091config JFFS2_SUMMARY
1092 bool "JFFS2 summary support (EXPERIMENTAL)"
1093 depends on JFFS2_FS && EXPERIMENTAL
1094 default n
1095 help
1096 This feature makes it possible to use summary information
1097 for faster filesystem mount.
1098
1099 The summary information can be inserted into a filesystem image
1100 by the utility 'sumtool'.
1101
1102 If unsure, say 'N'.
1103
Linus Torvalds1da177e2005-04-16 15:20:36 -07001104config JFFS2_COMPRESSION_OPTIONS
1105 bool "Advanced compression options for JFFS2"
1106 depends on JFFS2_FS
1107 default n
1108 help
1109 Enabling this option allows you to explicitly choose which
1110 compression modules, if any, are enabled in JFFS2. Removing
1111 compressors and mean you cannot read existing file systems,
1112 and enabling experimental compressors can mean that you
1113 write a file system which cannot be read by a standard kernel.
1114
1115 If unsure, you should _definitely_ say 'N'.
1116
1117config JFFS2_ZLIB
1118 bool "JFFS2 ZLIB compression support" if JFFS2_COMPRESSION_OPTIONS
1119 select ZLIB_INFLATE
1120 select ZLIB_DEFLATE
1121 depends on JFFS2_FS
1122 default y
1123 help
1124 Zlib is designed to be a free, general-purpose, legally unencumbered,
Thomas Gleixner182ec4e2005-11-07 11:16:07 +00001125 lossless data-compression library for use on virtually any computer
Linus Torvalds1da177e2005-04-16 15:20:36 -07001126 hardware and operating system. See <http://www.gzip.org/zlib/> for
1127 further information.
Thomas Gleixner182ec4e2005-11-07 11:16:07 +00001128
Linus Torvalds1da177e2005-04-16 15:20:36 -07001129 Say 'Y' if unsure.
1130
1131config JFFS2_RTIME
1132 bool "JFFS2 RTIME compression support" if JFFS2_COMPRESSION_OPTIONS
1133 depends on JFFS2_FS
1134 default y
1135 help
1136 Rtime does manage to recompress already-compressed data. Say 'Y' if unsure.
1137
1138config JFFS2_RUBIN
1139 bool "JFFS2 RUBIN compression support" if JFFS2_COMPRESSION_OPTIONS
1140 depends on JFFS2_FS
1141 default n
1142 help
1143 RUBINMIPS and DYNRUBIN compressors. Say 'N' if unsure.
1144
1145choice
1146 prompt "JFFS2 default compression mode" if JFFS2_COMPRESSION_OPTIONS
1147 default JFFS2_CMODE_PRIORITY
1148 depends on JFFS2_FS
1149 help
Thomas Gleixner182ec4e2005-11-07 11:16:07 +00001150 You can set here the default compression mode of JFFS2 from
Linus Torvalds1da177e2005-04-16 15:20:36 -07001151 the available compression modes. Don't touch if unsure.
1152
1153config JFFS2_CMODE_NONE
1154 bool "no compression"
1155 help
1156 Uses no compression.
1157
1158config JFFS2_CMODE_PRIORITY
1159 bool "priority"
1160 help
Thomas Gleixner182ec4e2005-11-07 11:16:07 +00001161 Tries the compressors in a predefinied order and chooses the first
Linus Torvalds1da177e2005-04-16 15:20:36 -07001162 successful one.
1163
1164config JFFS2_CMODE_SIZE
1165 bool "size (EXPERIMENTAL)"
1166 help
Thomas Gleixner182ec4e2005-11-07 11:16:07 +00001167 Tries all compressors and chooses the one which has the smallest
Linus Torvalds1da177e2005-04-16 15:20:36 -07001168 result.
1169
1170endchoice
1171
1172config CRAMFS
1173 tristate "Compressed ROM file system support (cramfs)"
1174 select ZLIB_INFLATE
1175 help
1176 Saying Y here includes support for CramFs (Compressed ROM File
1177 System). CramFs is designed to be a simple, small, and compressed
1178 file system for ROM based embedded systems. CramFs is read-only,
1179 limited to 256MB file systems (with 16MB files), and doesn't support
1180 16/32 bits uid/gid, hard links and timestamps.
1181
1182 See <file:Documentation/filesystems/cramfs.txt> and
1183 <file:fs/cramfs/README> for further information.
1184
1185 To compile this as a module, choose M here: the module will be called
1186 cramfs. Note that the root file system (the one containing the
1187 directory /) cannot be compiled as a module.
1188
1189 If unsure, say N.
1190
1191config VXFS_FS
1192 tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
1193 help
1194 FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
1195 file system format. VERITAS VxFS(TM) is the standard file system
1196 of SCO UnixWare (and possibly others) and optionally available
1197 for Sunsoft Solaris, HP-UX and many other operating systems.
1198 Currently only readonly access is supported.
1199
1200 NOTE: the file system type as used by mount(1), mount(2) and
1201 fstab(5) is 'vxfs' as it describes the file system format, not
1202 the actual driver.
1203
1204 To compile this as a module, choose M here: the module will be
1205 called freevxfs. If unsure, say N.
1206
1207
1208config HPFS_FS
1209 tristate "OS/2 HPFS file system support"
1210 help
1211 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
1212 is the file system used for organizing files on OS/2 hard disk
1213 partitions. Say Y if you want to be able to read files from and
1214 write files to an OS/2 HPFS partition on your hard drive. OS/2
1215 floppies however are in regular MSDOS format, so you don't need this
1216 option in order to be able to read them. Read
1217 <file:Documentation/filesystems/hpfs.txt>.
1218
1219 To compile this file system support as a module, choose M here: the
1220 module will be called hpfs. If unsure, say N.
1221
1222
1223
1224config QNX4FS_FS
1225 tristate "QNX4 file system support (read only)"
1226 help
1227 This is the file system used by the real-time operating systems
1228 QNX 4 and QNX 6 (the latter is also called QNX RTP).
1229 Further information is available at <http://www.qnx.com/>.
1230 Say Y if you intend to mount QNX hard disks or floppies.
1231 Unless you say Y to "QNX4FS read-write support" below, you will
1232 only be able to read these file systems.
1233
1234 To compile this file system support as a module, choose M here: the
1235 module will be called qnx4.
1236
1237 If you don't know whether you need it, then you don't need it:
1238 answer N.
1239
1240config QNX4FS_RW
1241 bool "QNX4FS write support (DANGEROUS)"
1242 depends on QNX4FS_FS && EXPERIMENTAL && BROKEN
1243 help
1244 Say Y if you want to test write support for QNX4 file systems.
1245
1246 It's currently broken, so for now:
1247 answer N.
1248
1249
1250
1251config SYSV_FS
1252 tristate "System V/Xenix/V7/Coherent file system support"
1253 help
1254 SCO, Xenix and Coherent are commercial Unix systems for Intel
1255 machines, and Version 7 was used on the DEC PDP-11. Saying Y
1256 here would allow you to read from their floppies and hard disk
1257 partitions.
1258
1259 If you have floppies or hard disk partitions like that, it is likely
1260 that they contain binaries from those other Unix systems; in order
1261 to run these binaries, you will want to install linux-abi which is a
1262 a set of kernel modules that lets you run SCO, Xenix, Wyse,
1263 UnixWare, Dell Unix and System V programs under Linux. It is
1264 available via FTP (user: ftp) from
1265 <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
1266 NOTE: that will work only for binaries from Intel-based systems;
1267 PDP ones will have to wait until somebody ports Linux to -11 ;-)
1268
1269 If you only intend to mount files from some other Unix over the
1270 network using NFS, you don't need the System V file system support
1271 (but you need NFS file system support obviously).
1272
1273 Note that this option is generally not needed for floppies, since a
1274 good portable way to transport files and directories between unixes
1275 (and even other operating systems) is given by the tar program ("man
1276 tar" or preferably "info tar"). Note also that this option has
1277 nothing whatsoever to do with the option "System V IPC". Read about
1278 the System V file system in
1279 <file:Documentation/filesystems/sysv-fs.txt>.
1280 Saying Y here will enlarge your kernel by about 27 KB.
1281
1282 To compile this as a module, choose M here: the module will be called
1283 sysv.
1284
1285 If you haven't heard about all of this before, it's safe to say N.
1286
1287
1288
1289config UFS_FS
1290 tristate "UFS file system support (read only)"
1291 help
1292 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
1293 OpenBSD and NeXTstep) use a file system called UFS. Some System V
1294 Unixes can create and mount hard disk partitions and diskettes using
1295 this file system as well. Saying Y here will allow you to read from
1296 these partitions; if you also want to write to them, say Y to the
1297 experimental "UFS file system write support", below. Please read the
1298 file <file:Documentation/filesystems/ufs.txt> for more information.
1299
1300 The recently released UFS2 variant (used in FreeBSD 5.x) is
1301 READ-ONLY supported.
1302
1303 If you only intend to mount files from some other Unix over the
1304 network using NFS, you don't need the UFS file system support (but
1305 you need NFS file system support obviously).
1306
1307 Note that this option is generally not needed for floppies, since a
1308 good portable way to transport files and directories between unixes
1309 (and even other operating systems) is given by the tar program ("man
1310 tar" or preferably "info tar").
1311
1312 When accessing NeXTstep files, you may need to convert them from the
1313 NeXT character set to the Latin1 character set; use the program
1314 recode ("info recode") for this purpose.
1315
1316 To compile the UFS file system support as a module, choose M here: the
1317 module will be called ufs.
1318
1319 If you haven't heard about all of this before, it's safe to say N.
1320
1321config UFS_FS_WRITE
1322 bool "UFS file system write support (DANGEROUS)"
Alexey Dobriyan537421b2006-02-01 03:05:24 -08001323 depends on UFS_FS && EXPERIMENTAL && BROKEN
Linus Torvalds1da177e2005-04-16 15:20:36 -07001324 help
1325 Say Y here if you want to try writing to UFS partitions. This is
1326 experimental, so you should back up your UFS partitions beforehand.
1327
1328endmenu
1329
1330menu "Network File Systems"
1331 depends on NET
1332
1333config NFS_FS
1334 tristate "NFS file system support"
1335 depends on INET
1336 select LOCKD
1337 select SUNRPC
Andreas Gruenbacherb7fa0552005-06-22 17:16:27 +00001338 select NFS_ACL_SUPPORT if NFS_V3_ACL
Linus Torvalds1da177e2005-04-16 15:20:36 -07001339 help
1340 If you are connected to some other (usually local) Unix computer
1341 (using SLIP, PLIP, PPP or Ethernet) and want to mount files residing
1342 on that computer (the NFS server) using the Network File Sharing
1343 protocol, say Y. "Mounting files" means that the client can access
1344 the files with usual UNIX commands as if they were sitting on the
1345 client's hard disk. For this to work, the server must run the
1346 programs nfsd and mountd (but does not need to have NFS file system
1347 support enabled in its kernel). NFS is explained in the Network
1348 Administrator's Guide, available from
1349 <http://www.tldp.org/docs.html#guide>, on its man page: "man
1350 nfs", and in the NFS-HOWTO.
1351
1352 A superior but less widely used alternative to NFS is provided by
1353 the Coda file system; see "Coda file system support" below.
1354
1355 If you say Y here, you should have said Y to TCP/IP networking also.
1356 This option would enlarge your kernel by about 27 KB.
1357
1358 To compile this file system support as a module, choose M here: the
1359 module will be called nfs.
1360
1361 If you are configuring a diskless machine which will mount its root
1362 file system over NFS at boot time, say Y here and to "Kernel
1363 level IP autoconfiguration" above and to "Root file system on NFS"
1364 below. You cannot compile this driver as a module in this case.
1365 There are two packages designed for booting diskless machines over
1366 the net: netboot, available from
1367 <http://ftp1.sourceforge.net/netboot/>, and Etherboot,
1368 available from <http://ftp1.sourceforge.net/etherboot/>.
1369
1370 If you don't know what all this is about, say N.
1371
1372config NFS_V3
1373 bool "Provide NFSv3 client support"
1374 depends on NFS_FS
1375 help
1376 Say Y here if you want your NFS client to be able to speak version
1377 3 of the NFS protocol.
1378
1379 If unsure, say Y.
1380
Andreas Gruenbacherb7fa0552005-06-22 17:16:27 +00001381config NFS_V3_ACL
1382 bool "Provide client support for the NFSv3 ACL protocol extension"
1383 depends on NFS_V3
1384 help
1385 Implement the NFSv3 ACL protocol extension for manipulating POSIX
1386 Access Control Lists. The server should also be compiled with
1387 the NFSv3 ACL protocol extension; see the CONFIG_NFSD_V3_ACL option.
1388
1389 If unsure, say N.
1390
Linus Torvalds1da177e2005-04-16 15:20:36 -07001391config NFS_V4
1392 bool "Provide NFSv4 client support (EXPERIMENTAL)"
1393 depends on NFS_FS && EXPERIMENTAL
1394 select RPCSEC_GSS_KRB5
1395 help
1396 Say Y here if you want your NFS client to be able to speak the newer
1397 version 4 of the NFS protocol.
1398
1399 Note: Requires auxiliary userspace daemons which may be found on
1400 http://www.citi.umich.edu/projects/nfsv4/
1401
1402 If unsure, say N.
1403
1404config NFS_DIRECTIO
1405 bool "Allow direct I/O on NFS files (EXPERIMENTAL)"
1406 depends on NFS_FS && EXPERIMENTAL
1407 help
1408 This option enables applications to perform uncached I/O on files
1409 in NFS file systems using the O_DIRECT open() flag. When O_DIRECT
1410 is set for a file, its data is not cached in the system's page
1411 cache. Data is moved to and from user-level application buffers
1412 directly. Unlike local disk-based file systems, NFS O_DIRECT has
1413 no alignment restrictions.
1414
1415 Unless your program is designed to use O_DIRECT properly, you are
1416 much better off allowing the NFS client to manage data caching for
1417 you. Misusing O_DIRECT can cause poor server performance or network
1418 storms. This kernel build option defaults OFF to avoid exposing
1419 system administrators unwittingly to a potentially hazardous
1420 feature.
1421
1422 For more details on NFS O_DIRECT, see fs/nfs/direct.c.
1423
1424 If unsure, say N. This reduces the size of the NFS client, and
1425 causes open() to return EINVAL if a file residing in NFS is
1426 opened with the O_DIRECT flag.
1427
1428config NFSD
1429 tristate "NFS server support"
1430 depends on INET
1431 select LOCKD
1432 select SUNRPC
1433 select EXPORTFS
Andreas Gruenbachera257cdd2005-06-22 17:16:26 +00001434 select NFS_ACL_SUPPORT if NFSD_V3_ACL || NFSD_V2_ACL
Linus Torvalds1da177e2005-04-16 15:20:36 -07001435 help
1436 If you want your Linux box to act as an NFS *server*, so that other
1437 computers on your local network which support NFS can access certain
1438 directories on your box transparently, you have two options: you can
1439 use the self-contained user space program nfsd, in which case you
1440 should say N here, or you can say Y and use the kernel based NFS
1441 server. The advantage of the kernel based solution is that it is
1442 faster.
1443
1444 In either case, you will need support software; the respective
1445 locations are given in the file <file:Documentation/Changes> in the
1446 NFS section.
1447
1448 If you say Y here, you will get support for version 2 of the NFS
1449 protocol (NFSv2). If you also want NFSv3, say Y to the next question
1450 as well.
1451
1452 Please read the NFS-HOWTO, available from
1453 <http://www.tldp.org/docs.html#howto>.
1454
1455 To compile the NFS server support as a module, choose M here: the
1456 module will be called nfsd. If unsure, say N.
1457
Andreas Gruenbachera257cdd2005-06-22 17:16:26 +00001458config NFSD_V2_ACL
1459 bool
1460 depends on NFSD
1461
Linus Torvalds1da177e2005-04-16 15:20:36 -07001462config NFSD_V3
1463 bool "Provide NFSv3 server support"
1464 depends on NFSD
1465 help
1466 If you would like to include the NFSv3 server as well as the NFSv2
1467 server, say Y here. If unsure, say Y.
1468
Andreas Gruenbachera257cdd2005-06-22 17:16:26 +00001469config NFSD_V3_ACL
1470 bool "Provide server support for the NFSv3 ACL protocol extension"
1471 depends on NFSD_V3
1472 select NFSD_V2_ACL
1473 help
1474 Implement the NFSv3 ACL protocol extension for manipulating POSIX
1475 Access Control Lists on exported file systems. NFS clients should
1476 be compiled with the NFSv3 ACL protocol extension; see the
1477 CONFIG_NFS_V3_ACL option. If unsure, say N.
1478
Linus Torvalds1da177e2005-04-16 15:20:36 -07001479config NFSD_V4
1480 bool "Provide NFSv4 server support (EXPERIMENTAL)"
1481 depends on NFSD_V3 && EXPERIMENTAL
1482 select NFSD_TCP
NeilBrowna55370a2005-06-23 22:03:52 -07001483 select CRYPTO_MD5
1484 select CRYPTO
Andreas Gruenbacherb84c2152005-07-07 17:56:57 -07001485 select FS_POSIX_ACL
Linus Torvalds1da177e2005-04-16 15:20:36 -07001486 help
1487 If you would like to include the NFSv4 server as well as the NFSv2
1488 and NFSv3 servers, say Y here. This feature is experimental, and
1489 should only be used if you are interested in helping to test NFSv4.
1490 If unsure, say N.
1491
1492config NFSD_TCP
1493 bool "Provide NFS server over TCP support"
1494 depends on NFSD
1495 default y
1496 help
1497 If you want your NFS server to support TCP connections, say Y here.
1498 TCP connections usually perform better than the default UDP when
1499 the network is lossy or congested. If unsure, say Y.
1500
1501config ROOT_NFS
1502 bool "Root file system on NFS"
1503 depends on NFS_FS=y && IP_PNP
1504 help
1505 If you want your Linux box to mount its whole root file system (the
1506 one containing the directory /) from some other computer over the
1507 net via NFS (presumably because your box doesn't have a hard disk),
1508 say Y. Read <file:Documentation/nfsroot.txt> for details. It is
1509 likely that in this case, you also want to say Y to "Kernel level IP
1510 autoconfiguration" so that your box can discover its network address
1511 at boot time.
1512
1513 Most people say N here.
1514
1515config LOCKD
1516 tristate
1517
1518config LOCKD_V4
1519 bool
1520 depends on NFSD_V3 || NFS_V3
1521 default y
1522
1523config EXPORTFS
1524 tristate
1525
Andreas Gruenbachera257cdd2005-06-22 17:16:26 +00001526config NFS_ACL_SUPPORT
1527 tristate
1528 select FS_POSIX_ACL
1529
1530config NFS_COMMON
1531 bool
1532 depends on NFSD || NFS_FS
1533 default y
1534
Linus Torvalds1da177e2005-04-16 15:20:36 -07001535config SUNRPC
1536 tristate
1537
1538config SUNRPC_GSS
1539 tristate
1540
1541config RPCSEC_GSS_KRB5
1542 tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
1543 depends on SUNRPC && EXPERIMENTAL
1544 select SUNRPC_GSS
1545 select CRYPTO
1546 select CRYPTO_MD5
1547 select CRYPTO_DES
1548 help
1549 Provides for secure RPC calls by means of a gss-api
1550 mechanism based on Kerberos V5. This is required for
1551 NFSv4.
1552
1553 Note: Requires an auxiliary userspace daemon which may be found on
1554 http://www.citi.umich.edu/projects/nfsv4/
1555
1556 If unsure, say N.
1557
1558config RPCSEC_GSS_SPKM3
1559 tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
1560 depends on SUNRPC && EXPERIMENTAL
1561 select SUNRPC_GSS
1562 select CRYPTO
1563 select CRYPTO_MD5
1564 select CRYPTO_DES
J. Bruce Fieldsdf6db302006-03-20 23:25:10 -05001565 select CRYPTO_CAST5
Linus Torvalds1da177e2005-04-16 15:20:36 -07001566 help
1567 Provides for secure RPC calls by means of a gss-api
1568 mechanism based on the SPKM3 public-key mechanism.
1569
1570 Note: Requires an auxiliary userspace daemon which may be found on
1571 http://www.citi.umich.edu/projects/nfsv4/
1572
1573 If unsure, say N.
1574
1575config SMB_FS
1576 tristate "SMB file system support (to mount Windows shares etc.)"
1577 depends on INET
1578 select NLS
1579 help
1580 SMB (Server Message Block) is the protocol Windows for Workgroups
1581 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
1582 files and printers over local networks. Saying Y here allows you to
1583 mount their file systems (often called "shares" in this context) and
1584 access them just like any other Unix directory. Currently, this
1585 works only if the Windows machines use TCP/IP as the underlying
1586 transport protocol, and not NetBEUI. For details, read
1587 <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
1588 available from <http://www.tldp.org/docs.html#howto>.
1589
1590 Note: if you just want your box to act as an SMB *server* and make
1591 files and printing services available to Windows clients (which need
1592 to have a TCP/IP stack), you don't need to say Y here; you can use
1593 the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
1594 for that.
1595
1596 General information about how to connect Linux, Windows machines and
1597 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1598
1599 To compile the SMB support as a module, choose M here: the module will
1600 be called smbfs. Most people say N, however.
1601
1602config SMB_NLS_DEFAULT
1603 bool "Use a default NLS"
1604 depends on SMB_FS
1605 help
1606 Enabling this will make smbfs use nls translations by default. You
1607 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
1608 settings and you need to give the default nls for the SMB server as
1609 CONFIG_SMB_NLS_REMOTE.
1610
1611 The nls settings can be changed at mount time, if your smbmount
1612 supports that, using the codepage and iocharset parameters.
1613
1614 smbmount from samba 2.2.0 or later supports this.
1615
1616config SMB_NLS_REMOTE
1617 string "Default Remote NLS Option"
1618 depends on SMB_NLS_DEFAULT
1619 default "cp437"
1620 help
1621 This setting allows you to specify a default value for which
1622 codepage the server uses. If this field is left blank no
1623 translations will be done by default. The local codepage/charset
1624 default to CONFIG_NLS_DEFAULT.
1625
1626 The nls settings can be changed at mount time, if your smbmount
1627 supports that, using the codepage and iocharset parameters.
1628
1629 smbmount from samba 2.2.0 or later supports this.
1630
1631config CIFS
1632 tristate "CIFS support (advanced network filesystem for Samba, Window and other CIFS compliant servers)"
1633 depends on INET
1634 select NLS
1635 help
1636 This is the client VFS module for the Common Internet File System
1637 (CIFS) protocol which is the successor to the Server Message Block
1638 (SMB) protocol, the native file sharing mechanism for most early
1639 PC operating systems. The CIFS protocol is fully supported by
1640 file servers such as Windows 2000 (including Windows 2003, NT 4
1641 and Windows XP) as well by Samba (which provides excellent CIFS
Steve Frenchec58ef02005-11-04 09:44:33 -08001642 server support for Linux and many other operating systems). Limited
1643 support for Windows ME and similar servers is provided as well.
1644 You must use the smbfs client filesystem to access older SMB servers
1645 such as OS/2 and DOS.
Linus Torvalds1da177e2005-04-16 15:20:36 -07001646
1647 The intent of the cifs module is to provide an advanced
1648 network file system client for mounting to CIFS compliant servers,
1649 including support for dfs (hierarchical name space), secure per-user
1650 session establishment, safe distributed caching (oplock), optional
1651 packet signing, Unicode and other internationalization improvements,
1652 and optional Winbind (nsswitch) integration. You do not need to enable
1653 cifs if running only a (Samba) server. It is possible to enable both
1654 smbfs and cifs (e.g. if you are using CIFS for accessing Windows 2003
1655 and Samba 3 servers, and smbfs for accessing old servers). If you need
Steve Frenchec58ef02005-11-04 09:44:33 -08001656 to mount to Samba or Windows from this machine, say Y.
Linus Torvalds1da177e2005-04-16 15:20:36 -07001657
1658config CIFS_STATS
1659 bool "CIFS statistics"
1660 depends on CIFS
1661 help
1662 Enabling this option will cause statistics for each server share
1663 mounted by the cifs client to be displayed in /proc/fs/cifs/Stats
1664
Steve Frenchec58ef02005-11-04 09:44:33 -08001665config CIFS_STATS2
1666 bool "CIFS extended statistics"
1667 depends on CIFS_STATS
1668 help
1669 Enabling this option will allow more detailed statistics on SMB
1670 request timing to be displayed in /proc/fs/cifs/DebugData and also
1671 allow optional logging of slow responses to dmesg (depending on the
1672 value of /proc/fs/cifs/cifsFYI, see fs/cifs/README for more details).
1673 These additional statistics may have a minor effect on performance
1674 and memory utilization.
1675
1676 Unless you are a developer or are doing network performance analysis
1677 or tuning, say N.
1678
Linus Torvalds1da177e2005-04-16 15:20:36 -07001679config CIFS_XATTR
Steve Frenchec58ef02005-11-04 09:44:33 -08001680 bool "CIFS extended attributes"
Linus Torvalds1da177e2005-04-16 15:20:36 -07001681 depends on CIFS
1682 help
1683 Extended attributes are name:value pairs associated with inodes by
1684 the kernel or by users (see the attr(5) manual page, or visit
1685 <http://acl.bestbits.at/> for details). CIFS maps the name of
1686 extended attributes beginning with the user namespace prefix
1687 to SMB/CIFS EAs. EAs are stored on Windows servers without the
1688 user namespace prefix, but their names are seen by Linux cifs clients
1689 prefaced by the user namespace prefix. The system namespace
1690 (used by some filesystems to store ACLs) is not supported at
1691 this time.
Steve Frenchec58ef02005-11-04 09:44:33 -08001692
Linus Torvalds1da177e2005-04-16 15:20:36 -07001693 If unsure, say N.
1694
1695config CIFS_POSIX
Steve Frenchec58ef02005-11-04 09:44:33 -08001696 bool "CIFS POSIX Extensions"
Linus Torvalds1da177e2005-04-16 15:20:36 -07001697 depends on CIFS_XATTR
1698 help
1699 Enabling this option will cause the cifs client to attempt to
1700 negotiate a newer dialect with servers, such as Samba 3.0.5
1701 or later, that optionally can handle more POSIX like (rather
1702 than Windows like) file behavior. It also enables
1703 support for POSIX ACLs (getfacl and setfacl) to servers
1704 (such as Samba 3.10 and later) which can negotiate
1705 CIFS POSIX ACL support. If unsure, say N.
1706
1707config CIFS_EXPERIMENTAL
1708 bool "CIFS Experimental Features (EXPERIMENTAL)"
Steve Frenchcb9dbff2005-11-02 11:37:15 -08001709 depends on CIFS && EXPERIMENTAL
Linus Torvalds1da177e2005-04-16 15:20:36 -07001710 help
Steve Frenchec58ef02005-11-04 09:44:33 -08001711 Enables cifs features under testing. These features are
1712 experimental and currently include support for writepages
1713 (multipage writebehind performance improvements) and directory
1714 change notification ie fcntl(F_DNOTIFY) as well as some security
1715 improvements. Some also depend on setting at runtime the
1716 pseudo-file /proc/fs/cifs/Experimental (which is disabled by
1717 default). See the file fs/cifs/README for more details.
1718
1719 If unsure, say N.
Linus Torvalds1da177e2005-04-16 15:20:36 -07001720
Steve Frencha2653eb2005-11-10 15:33:38 -08001721config CIFS_UPCALL
1722 bool "CIFS Kerberos/SPNEGO advanced session setup (EXPERIMENTAL)"
1723 depends on CIFS_EXPERIMENTAL
1724 select CONNECTOR
1725 help
1726 Enables an upcall mechanism for CIFS which will be used to contact
1727 userspace helper utilities to provide SPNEGO packaged Kerberos
1728 tickets which are needed to mount to certain secure servers
Steve French1b397f42005-11-10 19:36:39 -08001729 (for which more secure Kerberos authentication is required). If
1730 unsure, say N.
Steve Frencha2653eb2005-11-10 15:33:38 -08001731
Linus Torvalds1da177e2005-04-16 15:20:36 -07001732config NCP_FS
1733 tristate "NCP file system support (to mount NetWare volumes)"
1734 depends on IPX!=n || INET
1735 help
1736 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
1737 used by Novell NetWare clients to talk to file servers. It is to
1738 IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
1739 to mount NetWare file server volumes and to access them just like
1740 any other Unix directory. For details, please read the file
1741 <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
1742 the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
1743
1744 You do not have to say Y here if you want your Linux box to act as a
1745 file *server* for Novell NetWare clients.
1746
1747 General information about how to connect Linux, Windows machines and
1748 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1749
1750 To compile this as a module, choose M here: the module will be called
1751 ncpfs. Say N unless you are connected to a Novell network.
1752
1753source "fs/ncpfs/Kconfig"
1754
1755config CODA_FS
1756 tristate "Coda file system support (advanced network fs)"
1757 depends on INET
1758 help
1759 Coda is an advanced network file system, similar to NFS in that it
1760 enables you to mount file systems of a remote server and access them
1761 with regular Unix commands as if they were sitting on your hard
1762 disk. Coda has several advantages over NFS: support for
1763 disconnected operation (e.g. for laptops), read/write server
1764 replication, security model for authentication and encryption,
1765 persistent client caches and write back caching.
1766
1767 If you say Y here, your Linux box will be able to act as a Coda
1768 *client*. You will need user level code as well, both for the
1769 client and server. Servers are currently user level, i.e. they need
1770 no kernel support. Please read
1771 <file:Documentation/filesystems/coda.txt> and check out the Coda
1772 home page <http://www.coda.cs.cmu.edu/>.
1773
1774 To compile the coda client support as a module, choose M here: the
1775 module will be called coda.
1776
1777config CODA_FS_OLD_API
1778 bool "Use 96-bit Coda file identifiers"
1779 depends on CODA_FS
1780 help
1781 A new kernel-userspace API had to be introduced for Coda v6.0
1782 to support larger 128-bit file identifiers as needed by the
1783 new realms implementation.
1784
1785 However this new API is not backward compatible with older
1786 clients. If you really need to run the old Coda userspace
1787 cache manager then say Y.
1788
1789 For most cases you probably want to say N.
1790
1791config AFS_FS
1792# for fs/nls/Config.in
1793 tristate "Andrew File System support (AFS) (Experimental)"
1794 depends on INET && EXPERIMENTAL
1795 select RXRPC
1796 help
1797 If you say Y here, you will get an experimental Andrew File System
1798 driver. It currently only supports unsecured read-only AFS access.
1799
1800 See <file:Documentation/filesystems/afs.txt> for more intormation.
1801
1802 If unsure, say N.
1803
1804config RXRPC
1805 tristate
1806
Eric Van Hensbergen93fa58c2005-09-09 13:04:18 -07001807config 9P_FS
1808 tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
1809 depends on INET && EXPERIMENTAL
1810 help
1811 If you say Y here, you will get experimental support for
1812 Plan 9 resource sharing via the 9P2000 protocol.
1813
1814 See <http://v9fs.sf.net> for more information.
1815
1816 If unsure, say N.
1817
Linus Torvalds1da177e2005-04-16 15:20:36 -07001818endmenu
1819
1820menu "Partition Types"
1821
1822source "fs/partitions/Kconfig"
1823
1824endmenu
1825
1826source "fs/nls/Kconfig"
1827
1828endmenu
1829