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