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