blob: d311198bba439d812421331e7aea06a5046aa176 [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"
Al Viro0c426f22006-06-23 02:04:08 -070056 depends on EXT2_FS && MMU
Carsten Otte6d791252005-06-23 22:05:26 -070057 help
58 Execute in place can be used on memory-backed block devices. If you
59 enable this option, you can select to mount block devices which are
60 capable of this feature without using the page cache.
61
62 If you do not use a block device that is capable of using this,
63 or if unsure, say N.
64
65config FS_XIP
66# execute in place
67 bool
68 depends on EXT2_FS_XIP
69 default y
70
Linus Torvalds1da177e2005-04-16 15:20:36 -070071config EXT3_FS
72 tristate "Ext3 journalling file system support"
Mark Fashehb4e40a52005-12-15 14:31:24 -080073 select JBD
Linus Torvalds1da177e2005-04-16 15:20:36 -070074 help
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
Mark Fasheh02ed8412006-09-14 10:28:06 -0700328 tristate "OCFS2 file system support"
329 depends on NET && SYSFS
Mark Fashehb4e40a52005-12-15 14:31:24 -0800330 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
Joel Becker2b388c62006-05-10 18:28:59 -0700359config OCFS2_DEBUG_MASKLOG
360 bool "OCFS2 logging support"
361 depends on OCFS2_FS
362 default y
363 help
364 The ocfs2 filesystem has an extensive logging system. The system
365 allows selection of events to log via files in /sys/o2cb/logmask/.
366 This option will enlarge your kernel, but it allows debugging of
367 ocfs2 filesystem issues.
368
Linus Torvalds1da177e2005-04-16 15:20:36 -0700369config MINIX_FS
370 tristate "Minix fs support"
371 help
372 Minix is a simple operating system used in many classes about OS's.
373 The minix file system (method to organize files on a hard disk
374 partition or a floppy disk) was the original file system for Linux,
375 but has been superseded by the second extended file system ext2fs.
376 You don't want to use the minix file system on your hard disk
377 because of certain built-in restrictions, but it is sometimes found
378 on older Linux floppy disks. This option will enlarge your kernel
379 by about 28 KB. If unsure, say N.
380
381 To compile this file system support as a module, choose M here: the
382 module will be called minix. Note that the file system of your root
383 partition (the one containing the directory /) cannot be compiled as
384 a module.
385
386config ROMFS_FS
387 tristate "ROM file system support"
388 ---help---
389 This is a very small read-only file system mainly intended for
390 initial ram disks of installation disks, but it could be used for
391 other read-only media as well. Read
392 <file:Documentation/filesystems/romfs.txt> for details.
393
394 To compile this file system support as a module, choose M here: the
395 module will be called romfs. Note that the file system of your
396 root partition (the one containing the directory /) cannot be a
397 module.
398
399 If you don't know whether you need it, then you don't need it:
400 answer N.
401
Robert Love0eeca282005-07-12 17:06:03 -0400402config INOTIFY
403 bool "Inotify file change notification support"
404 default y
405 ---help---
Amy Griffis2d9048e2006-06-01 13:10:59 -0700406 Say Y here to enable inotify support. Inotify is a file change
407 notification system and a replacement for dnotify. Inotify fixes
408 numerous shortcomings in dnotify and introduces several new features
409 including multiple file events, one-shot support, and unmount
Robert Love3de11742005-08-04 13:07:08 -0700410 notification.
411
412 For more information, see Documentation/filesystems/inotify.txt
Robert Love0eeca282005-07-12 17:06:03 -0400413
414 If unsure, say Y.
415
Amy Griffis2d9048e2006-06-01 13:10:59 -0700416config INOTIFY_USER
417 bool "Inotify support for userspace"
418 depends on INOTIFY
419 default y
420 ---help---
421 Say Y here to enable inotify support for userspace, including the
422 associated system calls. Inotify allows monitoring of both files and
423 directories via a single open fd. Events are read from the file
424 descriptor, which is also select()- and poll()-able.
425
426 For more information, see Documentation/filesystems/inotify.txt
427
428 If unsure, say Y.
429
Linus Torvalds1da177e2005-04-16 15:20:36 -0700430config QUOTA
431 bool "Quota support"
432 help
433 If you say Y here, you will be able to set per user limits for disk
434 usage (also called disk quotas). Currently, it works for the
435 ext2, ext3, and reiserfs file system. ext3 also supports journalled
436 quotas for which you don't need to run quotacheck(8) after an unclean
Adrian Bunk919532a2005-09-06 15:17:22 -0700437 shutdown.
438 For further details, read the Quota mini-HOWTO, available from
Linus Torvalds1da177e2005-04-16 15:20:36 -0700439 <http://www.tldp.org/docs.html#howto>, or the documentation provided
440 with the quota tools. Probably the quota support is only useful for
441 multi user systems. If unsure, say N.
442
443config QFMT_V1
444 tristate "Old quota format support"
445 depends on QUOTA
446 help
447 This quota format was (is) used by kernels earlier than 2.4.22. If
448 you have quota working and you don't want to convert to new quota
449 format say Y here.
450
451config QFMT_V2
452 tristate "Quota format v2 support"
453 depends on QUOTA
454 help
455 This quota format allows using quotas with 32-bit UIDs/GIDs. If you
Adrian Bunk919532a2005-09-06 15:17:22 -0700456 need this functionality say Y here.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700457
458config QUOTACTL
459 bool
460 depends on XFS_QUOTA || QUOTA
461 default y
462
463config DNOTIFY
464 bool "Dnotify support" if EMBEDDED
465 default y
466 help
467 Dnotify is a directory-based per-fd file change notification system
468 that uses signals to communicate events to user-space. There exist
469 superior alternatives, but some applications may still rely on
470 dnotify.
471
472 Because of this, if unsure, say Y.
473
474config AUTOFS_FS
475 tristate "Kernel automounter support"
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 the autofs
483 package; you can find the location in <file:Documentation/Changes>.
484 You also want to answer Y to "NFS file system support", below.
485
486 If you want to use the newer version of the automounter with more
487 features, say N here and say Y to "Kernel automounter v4 support",
488 below.
489
490 To compile this support as a module, choose M here: the module will be
491 called autofs.
492
493 If you are not a part of a fairly large, distributed network, you
494 probably do not need an automounter, and can say N here.
495
496config AUTOFS4_FS
497 tristate "Kernel automounter version 4 support (also supports v3)"
498 help
499 The automounter is a tool to automatically mount remote file systems
500 on demand. This implementation is partially kernel-based to reduce
501 overhead in the already-mounted case; this is unlike the BSD
502 automounter (amd), which is a pure user space daemon.
503
504 To use the automounter you need the user-space tools from
505 <ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4/>; you also
506 want to answer Y to "NFS file system support", below.
507
508 To compile this support as a module, choose M here: the module will be
509 called autofs4. You will need to add "alias autofs autofs4" to your
510 modules configuration file.
511
512 If you are not a part of a fairly large, distributed network or
513 don't have a laptop which needs to dynamically reconfigure to the
514 local network, you probably do not need an automounter, and can say
515 N here.
516
Miklos Szeredi04578f12005-09-09 13:10:22 -0700517config FUSE_FS
518 tristate "Filesystem in Userspace support"
519 help
520 With FUSE it is possible to implement a fully functional filesystem
521 in a userspace program.
522
523 There's also companion library: libfuse. This library along with
524 utilities is available from the FUSE homepage:
525 <http://fuse.sourceforge.net/>
526
Miklos Szeredi909021e2005-09-27 21:45:20 -0700527 See <file:Documentation/filesystems/fuse.txt> for more information.
528 See <file:Documentation/Changes> for needed library/utility version.
529
Miklos Szeredi04578f12005-09-09 13:10:22 -0700530 If you want to develop a userspace FS, or if you want to use
531 a filesystem based on FUSE, answer Y or M.
532
Linus Torvalds1da177e2005-04-16 15:20:36 -0700533menu "CD-ROM/DVD Filesystems"
534
535config ISO9660_FS
536 tristate "ISO 9660 CDROM file system support"
537 help
538 This is the standard file system used on CD-ROMs. It was previously
539 known as "High Sierra File System" and is called "hsfs" on other
540 Unix systems. The so-called Rock-Ridge extensions which allow for
541 long Unix filenames and symbolic links are also supported by this
542 driver. If you have a CD-ROM drive and want to do more with it than
543 just listen to audio CDs and watch its LEDs, say Y (and read
544 <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO,
545 available from <http://www.tldp.org/docs.html#howto>), thereby
546 enlarging your kernel by about 27 KB; otherwise say N.
547
548 To compile this file system support as a module, choose M here: the
549 module will be called isofs.
550
551config JOLIET
552 bool "Microsoft Joliet CDROM extensions"
553 depends on ISO9660_FS
554 select NLS
555 help
556 Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system
557 which allows for long filenames in unicode format (unicode is the
558 new 16 bit character code, successor to ASCII, which encodes the
559 characters of almost all languages of the world; see
560 <http://www.unicode.org/> for more information). Say Y here if you
561 want to be able to read Joliet CD-ROMs under Linux.
562
563config ZISOFS
564 bool "Transparent decompression extension"
565 depends on ISO9660_FS
566 select ZLIB_INFLATE
567 help
568 This is a Linux-specific extension to RockRidge which lets you store
569 data in compressed form on a CD-ROM and have it transparently
570 decompressed when the CD-ROM is accessed. See
571 <http://www.kernel.org/pub/linux/utils/fs/zisofs/> for the tools
572 necessary to create such a filesystem. Say Y here if you want to be
573 able to read such compressed CD-ROMs.
574
575config ZISOFS_FS
576# for fs/nls/Config.in
577 tristate
578 depends on ZISOFS
579 default ISO9660_FS
580
581config UDF_FS
582 tristate "UDF file system support"
583 help
584 This is the new file system used on some CD-ROMs and DVDs. Say Y if
585 you intend to mount DVD discs or CDRW's written in packet mode, or
586 if written to by other UDF utilities, such as DirectCD.
587 Please read <file:Documentation/filesystems/udf.txt>.
588
589 To compile this file system support as a module, choose M here: the
590 module will be called udf.
591
592 If unsure, say N.
593
594config UDF_NLS
595 bool
596 default y
597 depends on (UDF_FS=m && NLS) || (UDF_FS=y && NLS=y)
598
599endmenu
600
601menu "DOS/FAT/NT Filesystems"
602
603config FAT_FS
604 tristate
605 select NLS
606 help
607 If you want to use one of the FAT-based file systems (the MS-DOS and
608 VFAT (Windows 95) file systems), then you must say Y or M here
609 to include FAT support. You will then be able to mount partitions or
610 diskettes with FAT-based file systems and transparently access the
611 files on them, i.e. MSDOS files will look and behave just like all
612 other Unix files.
613
614 This FAT support is not a file system in itself, it only provides
615 the foundation for the other file systems. You will have to say Y or
616 M to at least one of "MSDOS fs support" or "VFAT fs support" in
617 order to make use of it.
618
619 Another way to read and write MSDOS floppies and hard drive
620 partitions from within Linux (but not transparently) is with the
621 mtools ("man mtools") program suite. You don't need to say Y here in
622 order to do that.
623
624 If you need to move large files on floppies between a DOS and a
625 Linux box, say Y here, mount the floppy under Linux with an MSDOS
626 file system and use GNU tar's M option. GNU tar is a program
627 available for Unix and DOS ("man tar" or "info tar").
628
629 It is now also becoming possible to read and write compressed FAT
630 file systems; read <file:Documentation/filesystems/fat_cvf.txt> for
631 details.
632
633 The FAT support will enlarge your kernel by about 37 KB. If unsure,
634 say Y.
635
636 To compile this as a module, choose M here: the module will be called
637 fat. Note that if you compile the FAT support as a module, you
638 cannot compile any of the FAT-based file systems into the kernel
639 -- they will have to be modules as well.
640
641config MSDOS_FS
642 tristate "MSDOS fs support"
643 select FAT_FS
644 help
645 This allows you to mount MSDOS partitions of your hard drive (unless
646 they are compressed; to access compressed MSDOS partitions under
647 Linux, you can either use the DOS emulator DOSEMU, described in the
648 DOSEMU-HOWTO, available from
649 <http://www.tldp.org/docs.html#howto>, or try dmsdosfs in
650 <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you
651 intend to use dosemu with a non-compressed MSDOS partition, say Y
652 here) and MSDOS floppies. This means that file access becomes
653 transparent, i.e. the MSDOS files look and behave just like all
654 other Unix files.
655
656 If you have Windows 95 or Windows NT installed on your MSDOS
657 partitions, you should use the VFAT file system (say Y to "VFAT fs
658 support" below), or you will not be able to see the long filenames
659 generated by Windows 95 / Windows NT.
660
661 This option will enlarge your kernel by about 7 KB. If unsure,
662 answer Y. This will only work if you said Y to "DOS FAT fs support"
663 as well. To compile this as a module, choose M here: the module will
664 be called msdos.
665
666config VFAT_FS
667 tristate "VFAT (Windows-95) fs support"
668 select FAT_FS
669 help
670 This option provides support for normal Windows file systems with
671 long filenames. That includes non-compressed FAT-based file systems
672 used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
673 programs from the mtools package.
674
675 The VFAT support enlarges your kernel by about 10 KB and it only
676 works if you said Y to the "DOS FAT fs support" above. Please read
677 the file <file:Documentation/filesystems/vfat.txt> for details. If
678 unsure, say Y.
679
680 To compile this as a module, choose M here: the module will be called
681 vfat.
682
683config FAT_DEFAULT_CODEPAGE
684 int "Default codepage for FAT"
685 depends on MSDOS_FS || VFAT_FS
686 default 437
687 help
688 This option should be set to the codepage of your FAT filesystems.
689 It can be overridden with the "codepage" mount option.
690 See <file:Documentation/filesystems/vfat.txt> for more information.
691
692config FAT_DEFAULT_IOCHARSET
693 string "Default iocharset for FAT"
694 depends on VFAT_FS
695 default "iso8859-1"
696 help
697 Set this to the default input/output character set you'd
698 like FAT to use. It should probably match the character set
699 that most of your FAT filesystems use, and can be overridden
700 with the "iocharset" mount option for FAT filesystems.
701 Note that "utf8" is not recommended for FAT filesystems.
702 If unsure, you shouldn't set "utf8" here.
703 See <file:Documentation/filesystems/vfat.txt> for more information.
704
705config NTFS_FS
706 tristate "NTFS file system support"
707 select NLS
708 help
709 NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003.
710
711 Saying Y or M here enables read support. There is partial, but
712 safe, write support available. For write support you must also
713 say Y to "NTFS write support" below.
714
715 There are also a number of user-space tools available, called
716 ntfsprogs. These include ntfsundelete and ntfsresize, that work
717 without NTFS support enabled in the kernel.
718
719 This is a rewrite from scratch of Linux NTFS support and replaced
720 the old NTFS code starting with Linux 2.5.11. A backport to
721 the Linux 2.4 kernel series is separately available as a patch
722 from the project web site.
723
724 For more information see <file:Documentation/filesystems/ntfs.txt>
725 and <http://linux-ntfs.sourceforge.net/>.
726
727 To compile this file system support as a module, choose M here: the
728 module will be called ntfs.
729
730 If you are not using Windows NT, 2000, XP or 2003 in addition to
731 Linux on your computer it is safe to say N.
732
733config NTFS_DEBUG
734 bool "NTFS debugging support"
735 depends on NTFS_FS
736 help
737 If you are experiencing any problems with the NTFS file system, say
738 Y here. This will result in additional consistency checks to be
739 performed by the driver as well as additional debugging messages to
740 be written to the system log. Note that debugging messages are
741 disabled by default. To enable them, supply the option debug_msgs=1
742 at the kernel command line when booting the kernel or as an option
743 to insmod when loading the ntfs module. Once the driver is active,
744 you can enable debugging messages by doing (as root):
745 echo 1 > /proc/sys/fs/ntfs-debug
746 Replacing the "1" with "0" would disable debug messages.
747
748 If you leave debugging messages disabled, this results in little
749 overhead, but enabling debug messages results in very significant
750 slowdown of the system.
751
752 When reporting bugs, please try to have available a full dump of
753 debugging messages while the misbehaviour was occurring.
754
755config NTFS_RW
756 bool "NTFS write support"
757 depends on NTFS_FS
758 help
759 This enables the partial, but safe, write support in the NTFS driver.
760
761 The only supported operation is overwriting existing files, without
762 changing the file length. No file or directory creation, deletion or
763 renaming is possible. Note only non-resident files can be written to
764 so you may find that some very small files (<500 bytes or so) cannot
765 be written to.
766
767 While we cannot guarantee that it will not damage any data, we have
768 so far not received a single report where the driver would have
769 damaged someones data so we assume it is perfectly safe to use.
770
771 Note: While write support is safe in this version (a rewrite from
772 scratch of the NTFS support), it should be noted that the old NTFS
773 write support, included in Linux 2.5.10 and before (since 1997),
774 is not safe.
775
776 This is currently useful with TopologiLinux. TopologiLinux is run
777 on top of any DOS/Microsoft Windows system without partitioning your
778 hard disk. Unlike other Linux distributions TopologiLinux does not
779 need its own partition. For more information see
780 <http://topologi-linux.sourceforge.net/>
781
782 It is perfectly safe to say N here.
783
784endmenu
785
786menu "Pseudo filesystems"
787
788config PROC_FS
H. Peter Anvin69755652006-06-25 05:48:08 -0700789 bool "/proc file system support" if EMBEDDED
790 default y
Linus Torvalds1da177e2005-04-16 15:20:36 -0700791 help
792 This is a virtual file system providing information about the status
793 of the system. "Virtual" means that it doesn't take up any space on
794 your hard disk: the files are created on the fly by the kernel when
795 you try to access them. Also, you cannot read the files with older
796 version of the program less: you need to use more or cat.
797
798 It's totally cool; for example, "cat /proc/interrupts" gives
799 information about what the different IRQs are used for at the moment
800 (there is a small number of Interrupt ReQuest lines in your computer
801 that are used by the attached devices to gain the CPU's attention --
802 often a source of trouble if two devices are mistakenly configured
803 to use the same IRQ). The program procinfo to display some
804 information about your system gathered from the /proc file system.
805
806 Before you can use the /proc file system, it has to be mounted,
807 meaning it has to be given a location in the directory hierarchy.
808 That location should be /proc. A command such as "mount -t proc proc
809 /proc" or the equivalent line in /etc/fstab does the job.
810
811 The /proc file system is explained in the file
812 <file:Documentation/filesystems/proc.txt> and on the proc(5) manpage
813 ("man 5 proc").
814
815 This option will enlarge your kernel by about 67 KB. Several
816 programs depend on this, so everyone should say Y here.
817
818config PROC_KCORE
819 bool "/proc/kcore support" if !ARM
820 depends on PROC_FS && MMU
821
Vivek Goyal666bfdd2005-06-25 14:58:21 -0700822config PROC_VMCORE
823 bool "/proc/vmcore support (EXPERIMENTAL)"
Maneesh Soni05970d42006-01-09 20:51:52 -0800824 depends on PROC_FS && EXPERIMENTAL && CRASH_DUMP
Vivek Goyal68250ba2006-04-10 22:54:30 -0700825 default y
Vivek Goyal666bfdd2005-06-25 14:58:21 -0700826 help
827 Exports the dump image of crashed kernel in ELF format.
828
Eric W. Biedermanb89a8172006-09-27 01:51:04 -0700829config PROC_SYSCTL
830 bool "Sysctl support (/proc/sys)" if EMBEDDED
831 depends on PROC_FS
832 select SYSCTL
833 default y
834 ---help---
835 The sysctl interface provides a means of dynamically changing
836 certain kernel parameters and variables on the fly without requiring
837 a recompile of the kernel or reboot of the system. The primary
838 interface is through /proc/sys. If you say Y here a tree of
839 modifiable sysctl entries will be generated beneath the
840 /proc/sys directory. They are explained in the files
841 in <file:Documentation/sysctl/>. Note that enabling this
842 option will enlarge the kernel by at least 8 KB.
843
844 As it is generally a good thing, you should say Y here unless
845 building a kernel for install/rescue disks or your system is very
846 limited in memory.
847
Linus Torvalds1da177e2005-04-16 15:20:36 -0700848config SYSFS
849 bool "sysfs file system support" if EMBEDDED
850 default y
851 help
852 The sysfs filesystem is a virtual filesystem that the kernel uses to
853 export internal kernel objects, their attributes, and their
854 relationships to one another.
855
856 Users can use sysfs to ascertain useful information about the running
857 kernel, such as the devices the kernel has discovered on each bus and
858 which driver each is bound to. sysfs can also be used to tune devices
859 and other kernel subsystems.
860
861 Some system agents rely on the information in sysfs to operate.
862 /sbin/hotplug uses device and object attributes in sysfs to assist in
863 delegating policy decisions, like persistantly naming devices.
864
865 sysfs is currently used by the block subsystem to mount the root
866 partition. If sysfs is disabled you must specify the boot device on
867 the kernel boot command line via its major and minor numbers. For
868 example, "root=03:01" for /dev/hda1.
869
870 Designers of embedded systems may wish to say N here to conserve space.
871
Linus Torvalds1da177e2005-04-16 15:20:36 -0700872config TMPFS
873 bool "Virtual memory file system support (former shm fs)"
874 help
875 Tmpfs is a file system which keeps all files in virtual memory.
876
877 Everything in tmpfs is temporary in the sense that no files will be
878 created on your hard drive. The files live in memory and swap
879 space. If you unmount a tmpfs instance, everything stored therein is
880 lost.
881
882 See <file:Documentation/filesystems/tmpfs.txt> for details.
883
Linus Torvalds1da177e2005-04-16 15:20:36 -0700884config HUGETLBFS
885 bool "HugeTLB file system support"
Brian Gerst0d078f62005-10-30 14:59:20 -0800886 depends X86 || IA64 || PPC64 || SPARC64 || SUPERH || BROKEN
Arthur Othienodda27d12006-04-18 22:20:57 -0700887 help
888 hugetlbfs is a filesystem backing for HugeTLB pages, based on
889 ramfs. For architectures that support it, say Y here and read
890 <file:Documentation/vm/hugetlbpage.txt> for details.
891
892 If unsure, say N.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700893
894config HUGETLB_PAGE
895 def_bool HUGETLBFS
896
897config RAMFS
898 bool
899 default y
900 ---help---
901 Ramfs is a file system which keeps all files in RAM. It allows
902 read and write access.
903
904 It is more of an programming example than a useable file system. If
905 you need a file system which lives in RAM with limit checking use
906 tmpfs.
907
908 To compile this as a module, choose M here: the module will be called
909 ramfs.
910
Joel Becker7063fbf2005-12-15 14:29:43 -0800911config CONFIGFS_FS
912 tristate "Userspace-driven configuration filesystem (EXPERIMENTAL)"
Adrian Bunk65714b92006-03-26 14:25:52 +0200913 depends on SYSFS && EXPERIMENTAL
Joel Becker7063fbf2005-12-15 14:29:43 -0800914 help
915 configfs is a ram-based filesystem that provides the converse
916 of sysfs's functionality. Where sysfs is a filesystem-based
917 view of kernel objects, configfs is a filesystem-based manager
918 of kernel objects, or config_items.
919
920 Both sysfs and configfs can and should exist together on the
921 same system. One is not a replacement for the other.
922
Linus Torvalds1da177e2005-04-16 15:20:36 -0700923endmenu
924
925menu "Miscellaneous filesystems"
926
927config ADFS_FS
928 tristate "ADFS file system support (EXPERIMENTAL)"
929 depends on EXPERIMENTAL
930 help
931 The Acorn Disc Filing System is the standard file system of the
932 RiscOS operating system which runs on Acorn's ARM-based Risc PC
933 systems and the Acorn Archimedes range of machines. If you say Y
934 here, Linux will be able to read from ADFS partitions on hard drives
935 and from ADFS-formatted floppy discs. If you also want to be able to
936 write to those devices, say Y to "ADFS write support" below.
937
938 The ADFS partition should be the first partition (i.e.,
939 /dev/[hs]d?1) on each of your drives. Please read the file
940 <file:Documentation/filesystems/adfs.txt> for further details.
941
942 To compile this code as a module, choose M here: the module will be
943 called adfs.
944
945 If unsure, say N.
946
947config ADFS_FS_RW
948 bool "ADFS write support (DANGEROUS)"
949 depends on ADFS_FS
950 help
951 If you say Y here, you will be able to write to ADFS partitions on
952 hard drives and ADFS-formatted floppy disks. This is experimental
953 codes, so if you're unsure, say N.
954
955config AFFS_FS
956 tristate "Amiga FFS file system support (EXPERIMENTAL)"
957 depends on EXPERIMENTAL
958 help
959 The Fast File System (FFS) is the common file system used on hard
960 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
961 if you want to be able to read and write files from and to an Amiga
962 FFS partition on your hard drive. Amiga floppies however cannot be
963 read with this driver due to an incompatibility of the floppy
964 controller used in an Amiga and the standard floppy controller in
965 PCs and workstations. Read <file:Documentation/filesystems/affs.txt>
966 and <file:fs/affs/Changes>.
967
968 With this driver you can also mount disk files used by Bernd
969 Schmidt's Un*X Amiga Emulator
970 (<http://www.freiburg.linux.de/~uae/>).
971 If you want to do this, you will also need to say Y or M to "Loop
972 device support", above.
973
974 To compile this file system support as a module, choose M here: the
975 module will be called affs. If unsure, say N.
976
977config HFS_FS
978 tristate "Apple Macintosh file system support (EXPERIMENTAL)"
979 depends on EXPERIMENTAL
Lennert Buytenhek878129a2005-11-07 00:59:18 -0800980 select NLS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700981 help
982 If you say Y here, you will be able to mount Macintosh-formatted
983 floppy disks and hard drive partitions with full read-write access.
984 Please read <file:fs/hfs/HFS.txt> to learn about the available mount
985 options.
986
987 To compile this file system support as a module, choose M here: the
988 module will be called hfs.
989
990config HFSPLUS_FS
991 tristate "Apple Extended HFS file system support"
992 select NLS
993 select NLS_UTF8
994 help
995 If you say Y here, you will be able to mount extended format
996 Macintosh-formatted hard drive partitions with full read-write access.
997
998 This file system is often called HFS+ and was introduced with
999 MacOS 8. It includes all Mac specific filesystem data such as
1000 data forks and creator codes, but it also has several UNIX
1001 style features such as file ownership and permissions.
1002
1003config BEFS_FS
1004 tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)"
1005 depends on EXPERIMENTAL
1006 select NLS
1007 help
1008 The BeOS File System (BeFS) is the native file system of Be, Inc's
1009 BeOS. Notable features include support for arbitrary attributes
1010 on files and directories, and database-like indeces on selected
1011 attributes. (Also note that this driver doesn't make those features
1012 available at this time). It is a 64 bit filesystem, so it supports
1013 extremly large volumes and files.
1014
1015 If you use this filesystem, you should also say Y to at least one
1016 of the NLS (native language support) options below.
1017
1018 If you don't know what this is about, say N.
1019
1020 To compile this as a module, choose M here: the module will be
1021 called befs.
1022
1023config BEFS_DEBUG
1024 bool "Debug BeFS"
1025 depends on BEFS_FS
1026 help
1027 If you say Y here, you can use the 'debug' mount option to enable
1028 debugging output from the driver.
1029
1030config BFS_FS
1031 tristate "BFS file system support (EXPERIMENTAL)"
1032 depends on EXPERIMENTAL
1033 help
1034 Boot File System (BFS) is a file system used under SCO UnixWare to
1035 allow the bootloader access to the kernel image and other important
1036 files during the boot process. It is usually mounted under /stand
1037 and corresponds to the slice marked as "STAND" in the UnixWare
1038 partition. You should say Y if you want to read or write the files
1039 on your /stand slice from within Linux. You then also need to say Y
1040 to "UnixWare slices support", below. More information about the BFS
1041 file system is contained in the file
1042 <file:Documentation/filesystems/bfs.txt>.
1043
1044 If you don't know what this is about, say N.
1045
1046 To compile this as a module, choose M here: the module will be called
1047 bfs. Note that the file system of your root partition (the one
1048 containing the directory /) cannot be compiled as a module.
1049
1050
1051
1052config EFS_FS
1053 tristate "EFS file system support (read only) (EXPERIMENTAL)"
1054 depends on EXPERIMENTAL
1055 help
1056 EFS is an older file system used for non-ISO9660 CD-ROMs and hard
1057 disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
1058 uses the XFS file system for hard disk partitions however).
1059
1060 This implementation only offers read-only access. If you don't know
1061 what all this is about, it's safe to say N. For more information
1062 about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
1063
1064 To compile the EFS file system support as a module, choose M here: the
1065 module will be called efs.
1066
1067config JFFS_FS
1068 tristate "Journalling Flash File System (JFFS) support"
1069 depends on MTD
1070 help
1071 JFFS is the Journaling Flash File System developed by Axis
1072 Communications in Sweden, aimed at providing a crash/powerdown-safe
1073 file system for disk-less embedded devices. Further information is
1074 available at (<http://developer.axis.com/software/jffs/>).
1075
1076config JFFS_FS_VERBOSE
1077 int "JFFS debugging verbosity (0 = quiet, 3 = noisy)"
1078 depends on JFFS_FS
1079 default "0"
1080 help
1081 Determines the verbosity level of the JFFS debugging messages.
1082
1083config JFFS_PROC_FS
1084 bool "JFFS stats available in /proc filesystem"
1085 depends on JFFS_FS && PROC_FS
1086 help
1087 Enabling this option will cause statistics from mounted JFFS file systems
1088 to be made available to the user in the /proc/fs/jffs/ directory.
1089
1090config JFFS2_FS
1091 tristate "Journalling Flash File System v2 (JFFS2) support"
1092 select CRC32
1093 depends on MTD
1094 help
1095 JFFS2 is the second generation of the Journalling Flash File System
1096 for use on diskless embedded devices. It provides improved wear
1097 levelling, compression and support for hard links. You cannot use
1098 this on normal block devices, only on 'MTD' devices.
1099
1100 Further information on the design and implementation of JFFS2 is
1101 available at <http://sources.redhat.com/jffs2/>.
1102
1103config JFFS2_FS_DEBUG
1104 int "JFFS2 debugging verbosity (0 = quiet, 2 = noisy)"
1105 depends on JFFS2_FS
1106 default "0"
1107 help
1108 This controls the amount of debugging messages produced by the JFFS2
1109 code. Set it to zero for use in production systems. For evaluation,
1110 testing and debugging, it's advisable to set it to one. This will
1111 enable a few assertions and will print debugging messages at the
1112 KERN_DEBUG loglevel, where they won't normally be visible. Level 2
1113 is unlikely to be useful - it enables extra debugging in certain
1114 areas which at one point needed debugging, but when the bugs were
1115 located and fixed, the detailed messages were relegated to level 2.
1116
1117 If reporting bugs, please try to have available a full dump of the
1118 messages at debug level 1 while the misbehaviour was occurring.
1119
David Woodhouse2ba72cb2006-06-18 10:22:40 +01001120config JFFS2_FS_WRITEBUFFER
1121 bool "JFFS2 write-buffering support"
KaiGai Koheiaa98d7c2006-05-13 15:09:47 +09001122 depends on JFFS2_FS
David Woodhouse2ba72cb2006-06-18 10:22:40 +01001123 default y
1124 help
1125 This enables the write-buffering support in JFFS2.
1126
1127 This functionality is required to support JFFS2 on the following
1128 types of flash devices:
1129 - NAND flash
1130 - NOR flash with transparent ECC
1131 - DataFlash
1132
1133config JFFS2_SUMMARY
1134 bool "JFFS2 summary support (EXPERIMENTAL)"
1135 depends on JFFS2_FS && EXPERIMENTAL
1136 default n
1137 help
1138 This feature makes it possible to use summary information
1139 for faster filesystem mount.
1140
1141 The summary information can be inserted into a filesystem image
1142 by the utility 'sumtool'.
1143
1144 If unsure, say 'N'.
1145
1146config JFFS2_FS_XATTR
1147 bool "JFFS2 XATTR support (EXPERIMENTAL)"
KaiGai Kohei04510de2006-06-24 09:21:13 +09001148 depends on JFFS2_FS && EXPERIMENTAL
KaiGai Koheiaa98d7c2006-05-13 15:09:47 +09001149 default n
1150 help
1151 Extended attributes are name:value pairs associated with inodes by
1152 the kernel or by users (see the attr(5) manual page, or visit
1153 <http://acl.bestbits.at/> for details).
1154
1155 If unsure, say N.
1156
1157config JFFS2_FS_POSIX_ACL
1158 bool "JFFS2 POSIX Access Control Lists"
1159 depends on JFFS2_FS_XATTR
1160 default y
1161 select FS_POSIX_ACL
1162 help
1163 Posix Access Control Lists (ACLs) support permissions for users and
1164 groups beyond the owner/group/world scheme.
1165
1166 To learn more about Access Control Lists, visit the Posix ACLs for
1167 Linux website <http://acl.bestbits.at/>.
1168
1169 If you don't know what Access Control Lists are, say N
1170
1171config JFFS2_FS_SECURITY
1172 bool "JFFS2 Security Labels"
1173 depends on JFFS2_FS_XATTR
1174 default y
1175 help
1176 Security labels support alternative access control models
1177 implemented by security modules like SELinux. This option
1178 enables an extended attribute handler for file security
1179 labels in the jffs2 filesystem.
1180
1181 If you are not using a security module that requires using
1182 extended attributes for file security labels, say N.
1183
Linus Torvalds1da177e2005-04-16 15:20:36 -07001184config JFFS2_COMPRESSION_OPTIONS
1185 bool "Advanced compression options for JFFS2"
1186 depends on JFFS2_FS
1187 default n
1188 help
1189 Enabling this option allows you to explicitly choose which
1190 compression modules, if any, are enabled in JFFS2. Removing
1191 compressors and mean you cannot read existing file systems,
1192 and enabling experimental compressors can mean that you
1193 write a file system which cannot be read by a standard kernel.
1194
1195 If unsure, you should _definitely_ say 'N'.
1196
1197config JFFS2_ZLIB
1198 bool "JFFS2 ZLIB compression support" if JFFS2_COMPRESSION_OPTIONS
1199 select ZLIB_INFLATE
1200 select ZLIB_DEFLATE
1201 depends on JFFS2_FS
1202 default y
1203 help
1204 Zlib is designed to be a free, general-purpose, legally unencumbered,
Thomas Gleixner182ec4e2005-11-07 11:16:07 +00001205 lossless data-compression library for use on virtually any computer
Linus Torvalds1da177e2005-04-16 15:20:36 -07001206 hardware and operating system. See <http://www.gzip.org/zlib/> for
1207 further information.
Thomas Gleixner182ec4e2005-11-07 11:16:07 +00001208
Linus Torvalds1da177e2005-04-16 15:20:36 -07001209 Say 'Y' if unsure.
1210
1211config JFFS2_RTIME
1212 bool "JFFS2 RTIME compression support" if JFFS2_COMPRESSION_OPTIONS
1213 depends on JFFS2_FS
1214 default y
1215 help
1216 Rtime does manage to recompress already-compressed data. Say 'Y' if unsure.
1217
1218config JFFS2_RUBIN
1219 bool "JFFS2 RUBIN compression support" if JFFS2_COMPRESSION_OPTIONS
1220 depends on JFFS2_FS
1221 default n
1222 help
1223 RUBINMIPS and DYNRUBIN compressors. Say 'N' if unsure.
1224
1225choice
1226 prompt "JFFS2 default compression mode" if JFFS2_COMPRESSION_OPTIONS
1227 default JFFS2_CMODE_PRIORITY
1228 depends on JFFS2_FS
1229 help
Thomas Gleixner182ec4e2005-11-07 11:16:07 +00001230 You can set here the default compression mode of JFFS2 from
Linus Torvalds1da177e2005-04-16 15:20:36 -07001231 the available compression modes. Don't touch if unsure.
1232
1233config JFFS2_CMODE_NONE
1234 bool "no compression"
1235 help
1236 Uses no compression.
1237
1238config JFFS2_CMODE_PRIORITY
1239 bool "priority"
1240 help
Thomas Gleixner182ec4e2005-11-07 11:16:07 +00001241 Tries the compressors in a predefinied order and chooses the first
Linus Torvalds1da177e2005-04-16 15:20:36 -07001242 successful one.
1243
1244config JFFS2_CMODE_SIZE
1245 bool "size (EXPERIMENTAL)"
1246 help
Thomas Gleixner182ec4e2005-11-07 11:16:07 +00001247 Tries all compressors and chooses the one which has the smallest
Linus Torvalds1da177e2005-04-16 15:20:36 -07001248 result.
1249
1250endchoice
1251
1252config CRAMFS
1253 tristate "Compressed ROM file system support (cramfs)"
1254 select ZLIB_INFLATE
1255 help
1256 Saying Y here includes support for CramFs (Compressed ROM File
1257 System). CramFs is designed to be a simple, small, and compressed
1258 file system for ROM based embedded systems. CramFs is read-only,
1259 limited to 256MB file systems (with 16MB files), and doesn't support
1260 16/32 bits uid/gid, hard links and timestamps.
1261
1262 See <file:Documentation/filesystems/cramfs.txt> and
1263 <file:fs/cramfs/README> for further information.
1264
1265 To compile this as a module, choose M here: the module will be called
1266 cramfs. Note that the root file system (the one containing the
1267 directory /) cannot be compiled as a module.
1268
1269 If unsure, say N.
1270
1271config VXFS_FS
1272 tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
1273 help
1274 FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
1275 file system format. VERITAS VxFS(TM) is the standard file system
1276 of SCO UnixWare (and possibly others) and optionally available
1277 for Sunsoft Solaris, HP-UX and many other operating systems.
1278 Currently only readonly access is supported.
1279
1280 NOTE: the file system type as used by mount(1), mount(2) and
1281 fstab(5) is 'vxfs' as it describes the file system format, not
1282 the actual driver.
1283
1284 To compile this as a module, choose M here: the module will be
1285 called freevxfs. If unsure, say N.
1286
1287
1288config HPFS_FS
1289 tristate "OS/2 HPFS file system support"
1290 help
1291 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
1292 is the file system used for organizing files on OS/2 hard disk
1293 partitions. Say Y if you want to be able to read files from and
1294 write files to an OS/2 HPFS partition on your hard drive. OS/2
1295 floppies however are in regular MSDOS format, so you don't need this
1296 option in order to be able to read them. Read
1297 <file:Documentation/filesystems/hpfs.txt>.
1298
1299 To compile this file system support as a module, choose M here: the
1300 module will be called hpfs. If unsure, say N.
1301
1302
1303
1304config QNX4FS_FS
1305 tristate "QNX4 file system support (read only)"
1306 help
1307 This is the file system used by the real-time operating systems
1308 QNX 4 and QNX 6 (the latter is also called QNX RTP).
1309 Further information is available at <http://www.qnx.com/>.
1310 Say Y if you intend to mount QNX hard disks or floppies.
1311 Unless you say Y to "QNX4FS read-write support" below, you will
1312 only be able to read these file systems.
1313
1314 To compile this file system support as a module, choose M here: the
1315 module will be called qnx4.
1316
1317 If you don't know whether you need it, then you don't need it:
1318 answer N.
1319
1320config QNX4FS_RW
1321 bool "QNX4FS write support (DANGEROUS)"
1322 depends on QNX4FS_FS && EXPERIMENTAL && BROKEN
1323 help
1324 Say Y if you want to test write support for QNX4 file systems.
1325
1326 It's currently broken, so for now:
1327 answer N.
1328
1329
1330
1331config SYSV_FS
1332 tristate "System V/Xenix/V7/Coherent file system support"
1333 help
1334 SCO, Xenix and Coherent are commercial Unix systems for Intel
1335 machines, and Version 7 was used on the DEC PDP-11. Saying Y
1336 here would allow you to read from their floppies and hard disk
1337 partitions.
1338
1339 If you have floppies or hard disk partitions like that, it is likely
1340 that they contain binaries from those other Unix systems; in order
1341 to run these binaries, you will want to install linux-abi which is a
1342 a set of kernel modules that lets you run SCO, Xenix, Wyse,
1343 UnixWare, Dell Unix and System V programs under Linux. It is
1344 available via FTP (user: ftp) from
1345 <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
1346 NOTE: that will work only for binaries from Intel-based systems;
1347 PDP ones will have to wait until somebody ports Linux to -11 ;-)
1348
1349 If you only intend to mount files from some other Unix over the
1350 network using NFS, you don't need the System V file system support
1351 (but you need NFS file system support obviously).
1352
1353 Note that this option is generally not needed for floppies, since a
1354 good portable way to transport files and directories between unixes
1355 (and even other operating systems) is given by the tar program ("man
1356 tar" or preferably "info tar"). Note also that this option has
1357 nothing whatsoever to do with the option "System V IPC". Read about
1358 the System V file system in
1359 <file:Documentation/filesystems/sysv-fs.txt>.
1360 Saying Y here will enlarge your kernel by about 27 KB.
1361
1362 To compile this as a module, choose M here: the module will be called
1363 sysv.
1364
1365 If you haven't heard about all of this before, it's safe to say N.
1366
1367
1368
1369config UFS_FS
1370 tristate "UFS file system support (read only)"
1371 help
1372 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
1373 OpenBSD and NeXTstep) use a file system called UFS. Some System V
1374 Unixes can create and mount hard disk partitions and diskettes using
1375 this file system as well. Saying Y here will allow you to read from
1376 these partitions; if you also want to write to them, say Y to the
1377 experimental "UFS file system write support", below. Please read the
1378 file <file:Documentation/filesystems/ufs.txt> for more information.
1379
1380 The recently released UFS2 variant (used in FreeBSD 5.x) is
1381 READ-ONLY supported.
1382
1383 If you only intend to mount files from some other Unix over the
1384 network using NFS, you don't need the UFS file system support (but
1385 you need NFS file system support obviously).
1386
1387 Note that this option is generally not needed for floppies, since a
1388 good portable way to transport files and directories between unixes
1389 (and even other operating systems) is given by the tar program ("man
1390 tar" or preferably "info tar").
1391
1392 When accessing NeXTstep files, you may need to convert them from the
1393 NeXT character set to the Latin1 character set; use the program
1394 recode ("info recode") for this purpose.
1395
1396 To compile the UFS file system support as a module, choose M here: the
1397 module will be called ufs.
1398
1399 If you haven't heard about all of this before, it's safe to say N.
1400
1401config UFS_FS_WRITE
1402 bool "UFS file system write support (DANGEROUS)"
Evgeniy Dushistov5afb3142006-06-25 05:47:24 -07001403 depends on UFS_FS && EXPERIMENTAL
Linus Torvalds1da177e2005-04-16 15:20:36 -07001404 help
1405 Say Y here if you want to try writing to UFS partitions. This is
1406 experimental, so you should back up your UFS partitions beforehand.
1407
Evgeniy Dushistovabf5d152006-06-25 05:47:24 -07001408config UFS_DEBUG
1409 bool "UFS debugging"
1410 depends on UFS_FS
1411 help
1412 If you are experiencing any problems with the UFS filesystem, say
1413 Y here. This will result in _many_ additional debugging messages to be
1414 written to the system log.
1415
Linus Torvalds1da177e2005-04-16 15:20:36 -07001416endmenu
1417
1418menu "Network File Systems"
1419 depends on NET
1420
1421config NFS_FS
1422 tristate "NFS file system support"
1423 depends on INET
1424 select LOCKD
1425 select SUNRPC
Andreas Gruenbacherb7fa0552005-06-22 17:16:27 +00001426 select NFS_ACL_SUPPORT if NFS_V3_ACL
Linus Torvalds1da177e2005-04-16 15:20:36 -07001427 help
1428 If you are connected to some other (usually local) Unix computer
1429 (using SLIP, PLIP, PPP or Ethernet) and want to mount files residing
1430 on that computer (the NFS server) using the Network File Sharing
1431 protocol, say Y. "Mounting files" means that the client can access
1432 the files with usual UNIX commands as if they were sitting on the
1433 client's hard disk. For this to work, the server must run the
1434 programs nfsd and mountd (but does not need to have NFS file system
1435 support enabled in its kernel). NFS is explained in the Network
1436 Administrator's Guide, available from
1437 <http://www.tldp.org/docs.html#guide>, on its man page: "man
1438 nfs", and in the NFS-HOWTO.
1439
1440 A superior but less widely used alternative to NFS is provided by
1441 the Coda file system; see "Coda file system support" below.
1442
1443 If you say Y here, you should have said Y to TCP/IP networking also.
1444 This option would enlarge your kernel by about 27 KB.
1445
1446 To compile this file system support as a module, choose M here: the
1447 module will be called nfs.
1448
1449 If you are configuring a diskless machine which will mount its root
1450 file system over NFS at boot time, say Y here and to "Kernel
1451 level IP autoconfiguration" above and to "Root file system on NFS"
1452 below. You cannot compile this driver as a module in this case.
1453 There are two packages designed for booting diskless machines over
1454 the net: netboot, available from
1455 <http://ftp1.sourceforge.net/netboot/>, and Etherboot,
1456 available from <http://ftp1.sourceforge.net/etherboot/>.
1457
1458 If you don't know what all this is about, say N.
1459
1460config NFS_V3
1461 bool "Provide NFSv3 client support"
1462 depends on NFS_FS
1463 help
1464 Say Y here if you want your NFS client to be able to speak version
1465 3 of the NFS protocol.
1466
1467 If unsure, say Y.
1468
Andreas Gruenbacherb7fa0552005-06-22 17:16:27 +00001469config NFS_V3_ACL
1470 bool "Provide client support for the NFSv3 ACL protocol extension"
1471 depends on NFS_V3
1472 help
1473 Implement the NFSv3 ACL protocol extension for manipulating POSIX
1474 Access Control Lists. The server should also be compiled with
1475 the NFSv3 ACL protocol extension; see the CONFIG_NFSD_V3_ACL option.
1476
1477 If unsure, say N.
1478
Linus Torvalds1da177e2005-04-16 15:20:36 -07001479config NFS_V4
1480 bool "Provide NFSv4 client support (EXPERIMENTAL)"
1481 depends on NFS_FS && EXPERIMENTAL
1482 select RPCSEC_GSS_KRB5
1483 help
1484 Say Y here if you want your NFS client to be able to speak the newer
1485 version 4 of the NFS protocol.
1486
1487 Note: Requires auxiliary userspace daemons which may be found on
1488 http://www.citi.umich.edu/projects/nfsv4/
1489
1490 If unsure, say N.
1491
1492config NFS_DIRECTIO
Chuck Lever026ed5c2006-09-20 14:33:07 -04001493 bool "Allow direct I/O on NFS files"
1494 depends on NFS_FS
Linus Torvalds1da177e2005-04-16 15:20:36 -07001495 help
1496 This option enables applications to perform uncached I/O on files
1497 in NFS file systems using the O_DIRECT open() flag. When O_DIRECT
1498 is set for a file, its data is not cached in the system's page
1499 cache. Data is moved to and from user-level application buffers
1500 directly. Unlike local disk-based file systems, NFS O_DIRECT has
1501 no alignment restrictions.
1502
1503 Unless your program is designed to use O_DIRECT properly, you are
1504 much better off allowing the NFS client to manage data caching for
1505 you. Misusing O_DIRECT can cause poor server performance or network
1506 storms. This kernel build option defaults OFF to avoid exposing
1507 system administrators unwittingly to a potentially hazardous
1508 feature.
1509
1510 For more details on NFS O_DIRECT, see fs/nfs/direct.c.
1511
1512 If unsure, say N. This reduces the size of the NFS client, and
1513 causes open() to return EINVAL if a file residing in NFS is
1514 opened with the O_DIRECT flag.
1515
1516config NFSD
1517 tristate "NFS server support"
1518 depends on INET
1519 select LOCKD
1520 select SUNRPC
1521 select EXPORTFS
Herbert Xuf05e15b2006-06-26 00:25:39 -07001522 select NFSD_V2_ACL if NFSD_V3_ACL
1523 select NFS_ACL_SUPPORT if NFSD_V2_ACL
1524 select NFSD_TCP if NFSD_V4
1525 select CRYPTO_MD5 if NFSD_V4
1526 select CRYPTO if NFSD_V4
1527 select FS_POSIX_ACL if NFSD_V4
Linus Torvalds1da177e2005-04-16 15:20:36 -07001528 help
1529 If you want your Linux box to act as an NFS *server*, so that other
1530 computers on your local network which support NFS can access certain
1531 directories on your box transparently, you have two options: you can
1532 use the self-contained user space program nfsd, in which case you
1533 should say N here, or you can say Y and use the kernel based NFS
1534 server. The advantage of the kernel based solution is that it is
1535 faster.
1536
1537 In either case, you will need support software; the respective
1538 locations are given in the file <file:Documentation/Changes> in the
1539 NFS section.
1540
1541 If you say Y here, you will get support for version 2 of the NFS
1542 protocol (NFSv2). If you also want NFSv3, say Y to the next question
1543 as well.
1544
1545 Please read the NFS-HOWTO, available from
1546 <http://www.tldp.org/docs.html#howto>.
1547
1548 To compile the NFS server support as a module, choose M here: the
1549 module will be called nfsd. If unsure, say N.
1550
Andreas Gruenbachera257cdd2005-06-22 17:16:26 +00001551config NFSD_V2_ACL
1552 bool
1553 depends on NFSD
1554
Linus Torvalds1da177e2005-04-16 15:20:36 -07001555config NFSD_V3
1556 bool "Provide NFSv3 server support"
1557 depends on NFSD
1558 help
1559 If you would like to include the NFSv3 server as well as the NFSv2
1560 server, say Y here. If unsure, say Y.
1561
Andreas Gruenbachera257cdd2005-06-22 17:16:26 +00001562config NFSD_V3_ACL
1563 bool "Provide server support for the NFSv3 ACL protocol extension"
1564 depends on NFSD_V3
Andreas Gruenbachera257cdd2005-06-22 17:16:26 +00001565 help
1566 Implement the NFSv3 ACL protocol extension for manipulating POSIX
1567 Access Control Lists on exported file systems. NFS clients should
1568 be compiled with the NFSv3 ACL protocol extension; see the
1569 CONFIG_NFS_V3_ACL option. If unsure, say N.
1570
Linus Torvalds1da177e2005-04-16 15:20:36 -07001571config NFSD_V4
1572 bool "Provide NFSv4 server support (EXPERIMENTAL)"
1573 depends on NFSD_V3 && EXPERIMENTAL
Linus Torvalds1da177e2005-04-16 15:20:36 -07001574 help
1575 If you would like to include the NFSv4 server as well as the NFSv2
1576 and NFSv3 servers, say Y here. This feature is experimental, and
1577 should only be used if you are interested in helping to test NFSv4.
1578 If unsure, say N.
1579
1580config NFSD_TCP
1581 bool "Provide NFS server over TCP support"
1582 depends on NFSD
1583 default y
1584 help
1585 If you want your NFS server to support TCP connections, say Y here.
1586 TCP connections usually perform better than the default UDP when
1587 the network is lossy or congested. If unsure, say Y.
1588
1589config ROOT_NFS
1590 bool "Root file system on NFS"
1591 depends on NFS_FS=y && IP_PNP
1592 help
1593 If you want your Linux box to mount its whole root file system (the
1594 one containing the directory /) from some other computer over the
1595 net via NFS (presumably because your box doesn't have a hard disk),
1596 say Y. Read <file:Documentation/nfsroot.txt> for details. It is
1597 likely that in this case, you also want to say Y to "Kernel level IP
1598 autoconfiguration" so that your box can discover its network address
1599 at boot time.
1600
1601 Most people say N here.
1602
1603config LOCKD
1604 tristate
1605
1606config LOCKD_V4
1607 bool
1608 depends on NFSD_V3 || NFS_V3
1609 default y
1610
1611config EXPORTFS
1612 tristate
1613
Andreas Gruenbachera257cdd2005-06-22 17:16:26 +00001614config NFS_ACL_SUPPORT
1615 tristate
1616 select FS_POSIX_ACL
1617
1618config NFS_COMMON
1619 bool
1620 depends on NFSD || NFS_FS
1621 default y
1622
Linus Torvalds1da177e2005-04-16 15:20:36 -07001623config SUNRPC
1624 tristate
1625
1626config SUNRPC_GSS
1627 tristate
1628
1629config RPCSEC_GSS_KRB5
1630 tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
1631 depends on SUNRPC && EXPERIMENTAL
1632 select SUNRPC_GSS
1633 select CRYPTO
1634 select CRYPTO_MD5
1635 select CRYPTO_DES
1636 help
1637 Provides for secure RPC calls by means of a gss-api
1638 mechanism based on Kerberos V5. This is required for
1639 NFSv4.
1640
1641 Note: Requires an auxiliary userspace daemon which may be found on
1642 http://www.citi.umich.edu/projects/nfsv4/
1643
1644 If unsure, say N.
1645
1646config RPCSEC_GSS_SPKM3
1647 tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
1648 depends on SUNRPC && EXPERIMENTAL
1649 select SUNRPC_GSS
1650 select CRYPTO
1651 select CRYPTO_MD5
1652 select CRYPTO_DES
J. Bruce Fieldsdf6db302006-03-20 23:25:10 -05001653 select CRYPTO_CAST5
Linus Torvalds1da177e2005-04-16 15:20:36 -07001654 help
1655 Provides for secure RPC calls by means of a gss-api
1656 mechanism based on the SPKM3 public-key mechanism.
1657
1658 Note: Requires an auxiliary userspace daemon which may be found on
1659 http://www.citi.umich.edu/projects/nfsv4/
1660
1661 If unsure, say N.
1662
1663config SMB_FS
1664 tristate "SMB file system support (to mount Windows shares etc.)"
1665 depends on INET
1666 select NLS
1667 help
1668 SMB (Server Message Block) is the protocol Windows for Workgroups
1669 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
1670 files and printers over local networks. Saying Y here allows you to
1671 mount their file systems (often called "shares" in this context) and
1672 access them just like any other Unix directory. Currently, this
1673 works only if the Windows machines use TCP/IP as the underlying
1674 transport protocol, and not NetBEUI. For details, read
1675 <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
1676 available from <http://www.tldp.org/docs.html#howto>.
1677
1678 Note: if you just want your box to act as an SMB *server* and make
1679 files and printing services available to Windows clients (which need
1680 to have a TCP/IP stack), you don't need to say Y here; you can use
1681 the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
1682 for that.
1683
1684 General information about how to connect Linux, Windows machines and
1685 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1686
1687 To compile the SMB support as a module, choose M here: the module will
1688 be called smbfs. Most people say N, however.
1689
1690config SMB_NLS_DEFAULT
1691 bool "Use a default NLS"
1692 depends on SMB_FS
1693 help
1694 Enabling this will make smbfs use nls translations by default. You
1695 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
1696 settings and you need to give the default nls for the SMB server as
1697 CONFIG_SMB_NLS_REMOTE.
1698
1699 The nls settings can be changed at mount time, if your smbmount
1700 supports that, using the codepage and iocharset parameters.
1701
1702 smbmount from samba 2.2.0 or later supports this.
1703
1704config SMB_NLS_REMOTE
1705 string "Default Remote NLS Option"
1706 depends on SMB_NLS_DEFAULT
1707 default "cp437"
1708 help
1709 This setting allows you to specify a default value for which
1710 codepage the server uses. If this field is left blank no
1711 translations will be done by default. The local codepage/charset
1712 default to CONFIG_NLS_DEFAULT.
1713
1714 The nls settings can be changed at mount time, if your smbmount
1715 supports that, using the codepage and iocharset parameters.
1716
1717 smbmount from samba 2.2.0 or later supports this.
1718
1719config CIFS
1720 tristate "CIFS support (advanced network filesystem for Samba, Window and other CIFS compliant servers)"
1721 depends on INET
1722 select NLS
1723 help
1724 This is the client VFS module for the Common Internet File System
1725 (CIFS) protocol which is the successor to the Server Message Block
1726 (SMB) protocol, the native file sharing mechanism for most early
1727 PC operating systems. The CIFS protocol is fully supported by
1728 file servers such as Windows 2000 (including Windows 2003, NT 4
1729 and Windows XP) as well by Samba (which provides excellent CIFS
Steve Frenchec58ef02005-11-04 09:44:33 -08001730 server support for Linux and many other operating systems). Limited
1731 support for Windows ME and similar servers is provided as well.
1732 You must use the smbfs client filesystem to access older SMB servers
1733 such as OS/2 and DOS.
Linus Torvalds1da177e2005-04-16 15:20:36 -07001734
1735 The intent of the cifs module is to provide an advanced
1736 network file system client for mounting to CIFS compliant servers,
1737 including support for dfs (hierarchical name space), secure per-user
1738 session establishment, safe distributed caching (oplock), optional
1739 packet signing, Unicode and other internationalization improvements,
1740 and optional Winbind (nsswitch) integration. You do not need to enable
1741 cifs if running only a (Samba) server. It is possible to enable both
1742 smbfs and cifs (e.g. if you are using CIFS for accessing Windows 2003
1743 and Samba 3 servers, and smbfs for accessing old servers). If you need
Steve Frenchec58ef02005-11-04 09:44:33 -08001744 to mount to Samba or Windows from this machine, say Y.
Linus Torvalds1da177e2005-04-16 15:20:36 -07001745
1746config CIFS_STATS
1747 bool "CIFS statistics"
1748 depends on CIFS
1749 help
1750 Enabling this option will cause statistics for each server share
1751 mounted by the cifs client to be displayed in /proc/fs/cifs/Stats
1752
Steve Frenchec58ef02005-11-04 09:44:33 -08001753config CIFS_STATS2
Steve French39798772006-05-31 22:40:51 +00001754 bool "Extended statistics"
Steve Frenchec58ef02005-11-04 09:44:33 -08001755 depends on CIFS_STATS
1756 help
1757 Enabling this option will allow more detailed statistics on SMB
1758 request timing to be displayed in /proc/fs/cifs/DebugData and also
1759 allow optional logging of slow responses to dmesg (depending on the
1760 value of /proc/fs/cifs/cifsFYI, see fs/cifs/README for more details).
1761 These additional statistics may have a minor effect on performance
1762 and memory utilization.
1763
1764 Unless you are a developer or are doing network performance analysis
1765 or tuning, say N.
1766
Steve French39798772006-05-31 22:40:51 +00001767config CIFS_WEAK_PW_HASH
1768 bool "Support legacy servers which use weaker LANMAN security"
1769 depends on CIFS
1770 help
1771 Modern CIFS servers including Samba and most Windows versions
1772 (since 1997) support stronger NTLM (and even NTLMv2 and Kerberos)
1773 security mechanisms. These hash the password more securely
1774 than the mechanisms used in the older LANMAN version of the
1775 SMB protocol needed to establish sessions with old SMB servers.
1776
1777 Enabling this option allows the cifs module to mount to older
1778 LANMAN based servers such as OS/2 and Windows 95, but such
1779 mounts may be less secure than mounts using NTLM or more recent
1780 security mechanisms if you are on a public network. Unless you
1781 have a need to access old SMB servers (and are on a private
1782 network) you probably want to say N. Even if this support
1783 is enabled in the kernel build, they will not be used
1784 automatically. At runtime LANMAN mounts are disabled but
1785 can be set to required (or optional) either in
1786 /proc/fs/cifs (see fs/cifs/README for more detail) or via an
1787 option on the mount command. This support is disabled by
1788 default in order to reduce the possibility of a downgrade
1789 attack.
1790
1791 If unsure, say N.
1792
Linus Torvalds1da177e2005-04-16 15:20:36 -07001793config CIFS_XATTR
Steve Frenchec58ef02005-11-04 09:44:33 -08001794 bool "CIFS extended attributes"
Linus Torvalds1da177e2005-04-16 15:20:36 -07001795 depends on CIFS
1796 help
1797 Extended attributes are name:value pairs associated with inodes by
1798 the kernel or by users (see the attr(5) manual page, or visit
1799 <http://acl.bestbits.at/> for details). CIFS maps the name of
1800 extended attributes beginning with the user namespace prefix
1801 to SMB/CIFS EAs. EAs are stored on Windows servers without the
1802 user namespace prefix, but their names are seen by Linux cifs clients
1803 prefaced by the user namespace prefix. The system namespace
1804 (used by some filesystems to store ACLs) is not supported at
1805 this time.
Steve Frenchec58ef02005-11-04 09:44:33 -08001806
Linus Torvalds1da177e2005-04-16 15:20:36 -07001807 If unsure, say N.
1808
1809config CIFS_POSIX
Steve Frenchec58ef02005-11-04 09:44:33 -08001810 bool "CIFS POSIX Extensions"
Linus Torvalds1da177e2005-04-16 15:20:36 -07001811 depends on CIFS_XATTR
1812 help
1813 Enabling this option will cause the cifs client to attempt to
1814 negotiate a newer dialect with servers, such as Samba 3.0.5
1815 or later, that optionally can handle more POSIX like (rather
1816 than Windows like) file behavior. It also enables
1817 support for POSIX ACLs (getfacl and setfacl) to servers
1818 (such as Samba 3.10 and later) which can negotiate
1819 CIFS POSIX ACL support. If unsure, say N.
1820
Steve French39798772006-05-31 22:40:51 +00001821config CIFS_DEBUG2
Steve French3856a9d2006-06-01 19:38:46 +00001822 bool "Enable additional CIFS debugging routines"
Steve French8ba10ab2006-07-08 02:17:40 +00001823 depends on CIFS
Steve French39798772006-05-31 22:40:51 +00001824 help
1825 Enabling this option adds a few more debugging routines
1826 to the cifs code which slightly increases the size of
1827 the cifs module and can cause additional logging of debug
1828 messages in some error paths, slowing performance. This
1829 option can be turned off unless you are debugging
1830 cifs problems. If unsure, say N.
1831
Linus Torvalds1da177e2005-04-16 15:20:36 -07001832config CIFS_EXPERIMENTAL
1833 bool "CIFS Experimental Features (EXPERIMENTAL)"
Steve Frenchcb9dbff2005-11-02 11:37:15 -08001834 depends on CIFS && EXPERIMENTAL
Linus Torvalds1da177e2005-04-16 15:20:36 -07001835 help
Steve Frenchec58ef02005-11-04 09:44:33 -08001836 Enables cifs features under testing. These features are
1837 experimental and currently include support for writepages
1838 (multipage writebehind performance improvements) and directory
1839 change notification ie fcntl(F_DNOTIFY) as well as some security
1840 improvements. Some also depend on setting at runtime the
1841 pseudo-file /proc/fs/cifs/Experimental (which is disabled by
1842 default). See the file fs/cifs/README for more details.
1843
1844 If unsure, say N.
Linus Torvalds1da177e2005-04-16 15:20:36 -07001845
Steve Frencha2653eb2005-11-10 15:33:38 -08001846config CIFS_UPCALL
Steve French39798772006-05-31 22:40:51 +00001847 bool "Kerberos/SPNEGO advanced session setup (EXPERIMENTAL)"
Steve Frencha2653eb2005-11-10 15:33:38 -08001848 depends on CIFS_EXPERIMENTAL
1849 select CONNECTOR
1850 help
1851 Enables an upcall mechanism for CIFS which will be used to contact
1852 userspace helper utilities to provide SPNEGO packaged Kerberos
1853 tickets which are needed to mount to certain secure servers
Steve French1b397f42005-11-10 19:36:39 -08001854 (for which more secure Kerberos authentication is required). If
1855 unsure, say N.
Steve Frencha2653eb2005-11-10 15:33:38 -08001856
Linus Torvalds1da177e2005-04-16 15:20:36 -07001857config NCP_FS
1858 tristate "NCP file system support (to mount NetWare volumes)"
1859 depends on IPX!=n || INET
1860 help
1861 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
1862 used by Novell NetWare clients to talk to file servers. It is to
1863 IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
1864 to mount NetWare file server volumes and to access them just like
1865 any other Unix directory. For details, please read the file
1866 <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
1867 the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
1868
1869 You do not have to say Y here if you want your Linux box to act as a
1870 file *server* for Novell NetWare clients.
1871
1872 General information about how to connect Linux, Windows machines and
1873 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1874
1875 To compile this as a module, choose M here: the module will be called
1876 ncpfs. Say N unless you are connected to a Novell network.
1877
1878source "fs/ncpfs/Kconfig"
1879
1880config CODA_FS
1881 tristate "Coda file system support (advanced network fs)"
1882 depends on INET
1883 help
1884 Coda is an advanced network file system, similar to NFS in that it
1885 enables you to mount file systems of a remote server and access them
1886 with regular Unix commands as if they were sitting on your hard
1887 disk. Coda has several advantages over NFS: support for
1888 disconnected operation (e.g. for laptops), read/write server
1889 replication, security model for authentication and encryption,
1890 persistent client caches and write back caching.
1891
1892 If you say Y here, your Linux box will be able to act as a Coda
1893 *client*. You will need user level code as well, both for the
1894 client and server. Servers are currently user level, i.e. they need
1895 no kernel support. Please read
1896 <file:Documentation/filesystems/coda.txt> and check out the Coda
1897 home page <http://www.coda.cs.cmu.edu/>.
1898
1899 To compile the coda client support as a module, choose M here: the
1900 module will be called coda.
1901
1902config CODA_FS_OLD_API
1903 bool "Use 96-bit Coda file identifiers"
1904 depends on CODA_FS
1905 help
1906 A new kernel-userspace API had to be introduced for Coda v6.0
1907 to support larger 128-bit file identifiers as needed by the
1908 new realms implementation.
1909
1910 However this new API is not backward compatible with older
1911 clients. If you really need to run the old Coda userspace
1912 cache manager then say Y.
1913
1914 For most cases you probably want to say N.
1915
1916config AFS_FS
1917# for fs/nls/Config.in
1918 tristate "Andrew File System support (AFS) (Experimental)"
1919 depends on INET && EXPERIMENTAL
1920 select RXRPC
1921 help
1922 If you say Y here, you will get an experimental Andrew File System
1923 driver. It currently only supports unsecured read-only AFS access.
1924
1925 See <file:Documentation/filesystems/afs.txt> for more intormation.
1926
1927 If unsure, say N.
1928
1929config RXRPC
1930 tristate
1931
Eric Van Hensbergen93fa58c2005-09-09 13:04:18 -07001932config 9P_FS
1933 tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
1934 depends on INET && EXPERIMENTAL
1935 help
1936 If you say Y here, you will get experimental support for
1937 Plan 9 resource sharing via the 9P2000 protocol.
1938
1939 See <http://v9fs.sf.net> for more information.
1940
1941 If unsure, say N.
1942
Linus Torvalds1da177e2005-04-16 15:20:36 -07001943endmenu
1944
1945menu "Partition Types"
1946
1947source "fs/partitions/Kconfig"
1948
1949endmenu
1950
1951source "fs/nls/Kconfig"
1952
1953endmenu
1954