2 # File system configuration
8 tristate "Second extended fs support"
10 Ext2 is a standard Linux file system for hard disks.
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.
20 bool "Ext2 extended attributes"
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).
29 config EXT2_FS_POSIX_ACL
30 bool "Ext2 POSIX Access Control Lists"
31 depends on EXT2_FS_XATTR
34 Posix Access Control Lists (ACLs) support permissions for users and
35 groups beyond the owner/group/world scheme.
37 To learn more about Access Control Lists, visit the Posix ACLs for
38 Linux website <http://acl.bestbits.at/>.
40 If you don't know what Access Control Lists are, say N
42 config EXT2_FS_SECURITY
43 bool "Ext2 Security Labels"
44 depends on EXT2_FS_XATTR
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.
51 If you are not using a security module that requires using
52 extended attributes for file security labels, say N.
55 bool "Ext2 execute in place support"
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.
62 If you do not use a block device that is capable of using this,
68 depends on EXT2_FS_XIP
72 tristate "Ext3 journalling file system support"
75 This is the journaling version of the Second extended file system
76 (often called ext3), the de facto standard Linux file system
77 (method to organize files on a storage device) for hard disks.
79 The journaling code included in this driver means you do not have
80 to run e2fsck (file system checker) on your file systems after a
81 crash. The journal keeps track of any changes that were being made
82 at the time the system crashed, and can ensure that your file system
83 is consistent without the need for a lengthy check.
85 Other than adding the journal to the file system, the on-disk format
86 of ext3 is identical to ext2. It is possible to freely switch
87 between using the ext3 driver and the ext2 driver, as long as the
88 file system has been cleanly unmounted, or e2fsck is run on the file
91 To add a journal on an existing ext2 file system or change the
92 behavior of ext3 file systems, you can use the tune2fs utility ("man
93 tune2fs"). To modify attributes of files and directories on ext3
94 file systems, use chattr ("man chattr"). You need to be using
95 e2fsprogs version 1.20 or later in order to create ext3 journals
96 (available at <http://sourceforge.net/projects/e2fsprogs/>).
98 To compile this file system support as a module, choose M here: the
99 module will be called ext3. Be aware however that the file system
100 of your root partition (the one containing the directory /) cannot
101 be compiled as a module, and so this may be dangerous.
104 bool "Ext3 extended attributes"
108 Extended attributes are name:value pairs associated with inodes by
109 the kernel or by users (see the attr(5) manual page, or visit
110 <http://acl.bestbits.at/> for details).
114 You need this for POSIX ACL support on ext3.
116 config EXT3_FS_POSIX_ACL
117 bool "Ext3 POSIX Access Control Lists"
118 depends on EXT3_FS_XATTR
121 Posix Access Control Lists (ACLs) support permissions for users and
122 groups beyond the owner/group/world scheme.
124 To learn more about Access Control Lists, visit the Posix ACLs for
125 Linux website <http://acl.bestbits.at/>.
127 If you don't know what Access Control Lists are, say N
129 config EXT3_FS_SECURITY
130 bool "Ext3 Security Labels"
131 depends on EXT3_FS_XATTR
133 Security labels support alternative access control models
134 implemented by security modules like SELinux. This option
135 enables an extended attribute handler for file security
136 labels in the ext3 filesystem.
138 If you are not using a security module that requires using
139 extended attributes for file security labels, say N.
144 This is a generic journaling layer for block devices. It is
145 currently used by the ext3 and OCFS2 file systems, but it could
146 also be used to add journal support to other file systems or block
147 devices such as RAID or LVM.
149 If you are using the ext3 or OCFS2 file systems, you need to
150 say Y here. If you are not using ext3 OCFS2 then you will probably
153 To compile this device as a module, choose M here: the module will be
154 called jbd. If you are compiling ext3 or OCFS2 into the kernel,
155 you cannot compile this code as a module.
158 bool "JBD (ext3) debugging support"
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.
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".
174 # Meta block cache for Extended Attributes (ext2/ext3)
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
181 tristate "Reiserfs support"
183 Stores not just filenames but the files themselves in a balanced
184 tree. Uses journaling.
186 Balanced trees are more efficient than traditional file system
187 architectural foundations.
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.
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.''
199 Read <http://www.namesys.com/> to learn more about reiserfs.
201 Sponsored by Threshold Networks, Emusic.com, and Bigstorage.com.
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.
206 config REISERFS_CHECK
207 bool "Enable reiserfs debug mode"
208 depends on REISERFS_FS
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.
220 config REISERFS_PROC_INFO
221 bool "Stats in /proc/fs/reiserfs"
222 depends on REISERFS_FS
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.
231 config REISERFS_FS_XATTR
232 bool "ReiserFS extended attributes"
233 depends on REISERFS_FS
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).
241 config REISERFS_FS_POSIX_ACL
242 bool "ReiserFS POSIX Access Control Lists"
243 depends on REISERFS_FS_XATTR
246 Posix Access Control Lists (ACLs) support permissions for users and
247 groups beyond the owner/group/world scheme.
249 To learn more about Access Control Lists, visit the Posix ACLs for
250 Linux website <http://acl.bestbits.at/>.
252 If you don't know what Access Control Lists are, say N
254 config REISERFS_FS_SECURITY
255 bool "ReiserFS Security Labels"
256 depends on REISERFS_FS_XATTR
258 Security labels support alternative access control models
259 implemented by security modules like SELinux. This option
260 enables an extended attribute handler for file security
261 labels in the ReiserFS filesystem.
263 If you are not using a security module that requires using
264 extended attributes for file security labels, say N.
267 tristate "JFS filesystem support"
270 This is a port of IBM's Journaled Filesystem . More information is
271 available in the file <file:Documentation/filesystems/jfs.txt>.
273 If you do not intend to use the JFS filesystem, say N.
276 bool "JFS POSIX Access Control Lists"
280 Posix Access Control Lists (ACLs) support permissions for users and
281 groups beyond the owner/group/world scheme.
283 To learn more about Access Control Lists, visit the Posix ACLs for
284 Linux website <http://acl.bestbits.at/>.
286 If you don't know what Access Control Lists are, say N
289 bool "JFS Security Labels"
292 Security labels support alternative access control models
293 implemented by security modules like SELinux. This option
294 enables an extended attribute handler for file security
295 labels in the jfs filesystem.
297 If you are not using a security module that requires using
298 extended attributes for file security labels, say N.
304 If you are experiencing any problems with the JFS filesystem, say
305 Y here. This will result in additional debugging messages to be
306 written to the system log. Under normal circumstances, this
307 results in very little overhead.
309 config JFS_STATISTICS
310 bool "JFS statistics"
313 Enabling this option will cause statistics from the JFS file system
314 to be made available to the user in the /proc/fs/jfs/ directory.
317 # Posix ACL utility routines (for now, only ext2/ext3/jfs/reiserfs)
319 # NOTE: you can implement Posix ACLs without these helpers (XFS does).
320 # Never use this symbol for ifdefs.
325 source "fs/xfs/Kconfig"
326 source "fs/gfs2/Kconfig"
329 tristate "OCFS2 file system support (EXPERIMENTAL)"
330 depends on NET && EXPERIMENTAL
336 OCFS2 is a general purpose extent based shared disk cluster file
337 system with many similarities to ext3. It supports 64 bit inode
338 numbers, and has automatically extending metadata groups which may
339 also make it attractive for non-clustered use.
341 You'll want to install the ocfs2-tools package in order to at least
344 Project web page: http://oss.oracle.com/projects/ocfs2
345 Tools web page: http://oss.oracle.com/projects/ocfs2-tools
346 OCFS2 mailing lists: http://oss.oracle.com/projects/ocfs2/mailman/
348 Note: Features which OCFS2 does not support yet:
349 - extended attributes
350 - shared writeable mmap
351 - loopback is supported, but data written will not
354 - cluster aware flock
355 - Directory change notification (F_NOTIFY)
356 - Distributed Caching (F_SETLEASE/F_GETLEASE/break_lease)
358 - readpages / writepages (not user visible)
361 tristate "Minix fs support"
363 Minix is a simple operating system used in many classes about OS's.
364 The minix file system (method to organize files on a hard disk
365 partition or a floppy disk) was the original file system for Linux,
366 but has been superseded by the second extended file system ext2fs.
367 You don't want to use the minix file system on your hard disk
368 because of certain built-in restrictions, but it is sometimes found
369 on older Linux floppy disks. This option will enlarge your kernel
370 by about 28 KB. If unsure, say N.
372 To compile this file system support as a module, choose M here: the
373 module will be called minix. Note that the file system of your root
374 partition (the one containing the directory /) cannot be compiled as
378 tristate "ROM file system support"
380 This is a very small read-only file system mainly intended for
381 initial ram disks of installation disks, but it could be used for
382 other read-only media as well. Read
383 <file:Documentation/filesystems/romfs.txt> for details.
385 To compile this file system support as a module, choose M here: the
386 module will be called romfs. Note that the file system of your
387 root partition (the one containing the directory /) cannot be a
390 If you don't know whether you need it, then you don't need it:
394 bool "Inotify file change notification support"
397 Say Y here to enable inotify support and the associated system
398 calls. Inotify is a file change notification system and a
399 replacement for dnotify. Inotify fixes numerous shortcomings in
400 dnotify and introduces several new features. It allows monitoring
401 of both files and directories via a single open fd. Other features
402 include multiple file events, one-shot support, and unmount
405 For more information, see Documentation/filesystems/inotify.txt
412 If you say Y here, you will be able to set per user limits for disk
413 usage (also called disk quotas). Currently, it works for the
414 ext2, ext3, and reiserfs file system. ext3 also supports journalled
415 quotas for which you don't need to run quotacheck(8) after an unclean
417 For further details, read the Quota mini-HOWTO, available from
418 <http://www.tldp.org/docs.html#howto>, or the documentation provided
419 with the quota tools. Probably the quota support is only useful for
420 multi user systems. If unsure, say N.
423 tristate "Old quota format support"
426 This quota format was (is) used by kernels earlier than 2.4.22. If
427 you have quota working and you don't want to convert to new quota
431 tristate "Quota format v2 support"
434 This quota format allows using quotas with 32-bit UIDs/GIDs. If you
435 need this functionality say Y here.
439 depends on XFS_QUOTA || QUOTA
443 bool "Dnotify support" if EMBEDDED
446 Dnotify is a directory-based per-fd file change notification system
447 that uses signals to communicate events to user-space. There exist
448 superior alternatives, but some applications may still rely on
451 Because of this, if unsure, say Y.
454 tristate "Kernel automounter support"
456 The automounter is a tool to automatically mount remote file systems
457 on demand. This implementation is partially kernel-based to reduce
458 overhead in the already-mounted case; this is unlike the BSD
459 automounter (amd), which is a pure user space daemon.
461 To use the automounter you need the user-space tools from the autofs
462 package; you can find the location in <file:Documentation/Changes>.
463 You also want to answer Y to "NFS file system support", below.
465 If you want to use the newer version of the automounter with more
466 features, say N here and say Y to "Kernel automounter v4 support",
469 To compile this support as a module, choose M here: the module will be
472 If you are not a part of a fairly large, distributed network, you
473 probably do not need an automounter, and can say N here.
476 tristate "Kernel automounter version 4 support (also supports v3)"
478 The automounter is a tool to automatically mount remote file systems
479 on demand. This implementation is partially kernel-based to reduce
480 overhead in the already-mounted case; this is unlike the BSD
481 automounter (amd), which is a pure user space daemon.
483 To use the automounter you need the user-space tools from
484 <ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4/>; you also
485 want to answer Y to "NFS file system support", below.
487 To compile this support as a module, choose M here: the module will be
488 called autofs4. You will need to add "alias autofs autofs4" to your
489 modules configuration file.
491 If you are not a part of a fairly large, distributed network or
492 don't have a laptop which needs to dynamically reconfigure to the
493 local network, you probably do not need an automounter, and can say
497 tristate "Filesystem in Userspace support"
499 With FUSE it is possible to implement a fully functional filesystem
500 in a userspace program.
502 There's also companion library: libfuse. This library along with
503 utilities is available from the FUSE homepage:
504 <http://fuse.sourceforge.net/>
506 See <file:Documentation/filesystems/fuse.txt> for more information.
507 See <file:Documentation/Changes> for needed library/utility version.
509 If you want to develop a userspace FS, or if you want to use
510 a filesystem based on FUSE, answer Y or M.
512 menu "CD-ROM/DVD Filesystems"
515 tristate "ISO 9660 CDROM file system support"
517 This is the standard file system used on CD-ROMs. It was previously
518 known as "High Sierra File System" and is called "hsfs" on other
519 Unix systems. The so-called Rock-Ridge extensions which allow for
520 long Unix filenames and symbolic links are also supported by this
521 driver. If you have a CD-ROM drive and want to do more with it than
522 just listen to audio CDs and watch its LEDs, say Y (and read
523 <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO,
524 available from <http://www.tldp.org/docs.html#howto>), thereby
525 enlarging your kernel by about 27 KB; otherwise say N.
527 To compile this file system support as a module, choose M here: the
528 module will be called isofs.
531 bool "Microsoft Joliet CDROM extensions"
532 depends on ISO9660_FS
535 Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system
536 which allows for long filenames in unicode format (unicode is the
537 new 16 bit character code, successor to ASCII, which encodes the
538 characters of almost all languages of the world; see
539 <http://www.unicode.org/> for more information). Say Y here if you
540 want to be able to read Joliet CD-ROMs under Linux.
543 bool "Transparent decompression extension"
544 depends on ISO9660_FS
547 This is a Linux-specific extension to RockRidge which lets you store
548 data in compressed form on a CD-ROM and have it transparently
549 decompressed when the CD-ROM is accessed. See
550 <http://www.kernel.org/pub/linux/utils/fs/zisofs/> for the tools
551 necessary to create such a filesystem. Say Y here if you want to be
552 able to read such compressed CD-ROMs.
555 # for fs/nls/Config.in
561 tristate "UDF file system support"
563 This is the new file system used on some CD-ROMs and DVDs. Say Y if
564 you intend to mount DVD discs or CDRW's written in packet mode, or
565 if written to by other UDF utilities, such as DirectCD.
566 Please read <file:Documentation/filesystems/udf.txt>.
568 To compile this file system support as a module, choose M here: the
569 module will be called udf.
576 depends on (UDF_FS=m && NLS) || (UDF_FS=y && NLS=y)
580 menu "DOS/FAT/NT Filesystems"
586 If you want to use one of the FAT-based file systems (the MS-DOS and
587 VFAT (Windows 95) file systems), then you must say Y or M here
588 to include FAT support. You will then be able to mount partitions or
589 diskettes with FAT-based file systems and transparently access the
590 files on them, i.e. MSDOS files will look and behave just like all
593 This FAT support is not a file system in itself, it only provides
594 the foundation for the other file systems. You will have to say Y or
595 M to at least one of "MSDOS fs support" or "VFAT fs support" in
596 order to make use of it.
598 Another way to read and write MSDOS floppies and hard drive
599 partitions from within Linux (but not transparently) is with the
600 mtools ("man mtools") program suite. You don't need to say Y here in
603 If you need to move large files on floppies between a DOS and a
604 Linux box, say Y here, mount the floppy under Linux with an MSDOS
605 file system and use GNU tar's M option. GNU tar is a program
606 available for Unix and DOS ("man tar" or "info tar").
608 It is now also becoming possible to read and write compressed FAT
609 file systems; read <file:Documentation/filesystems/fat_cvf.txt> for
612 The FAT support will enlarge your kernel by about 37 KB. If unsure,
615 To compile this as a module, choose M here: the module will be called
616 fat. Note that if you compile the FAT support as a module, you
617 cannot compile any of the FAT-based file systems into the kernel
618 -- they will have to be modules as well.
621 tristate "MSDOS fs support"
624 This allows you to mount MSDOS partitions of your hard drive (unless
625 they are compressed; to access compressed MSDOS partitions under
626 Linux, you can either use the DOS emulator DOSEMU, described in the
627 DOSEMU-HOWTO, available from
628 <http://www.tldp.org/docs.html#howto>, or try dmsdosfs in
629 <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you
630 intend to use dosemu with a non-compressed MSDOS partition, say Y
631 here) and MSDOS floppies. This means that file access becomes
632 transparent, i.e. the MSDOS files look and behave just like all
635 If you have Windows 95 or Windows NT installed on your MSDOS
636 partitions, you should use the VFAT file system (say Y to "VFAT fs
637 support" below), or you will not be able to see the long filenames
638 generated by Windows 95 / Windows NT.
640 This option will enlarge your kernel by about 7 KB. If unsure,
641 answer Y. This will only work if you said Y to "DOS FAT fs support"
642 as well. To compile this as a module, choose M here: the module will
646 tristate "VFAT (Windows-95) fs support"
649 This option provides support for normal Windows file systems with
650 long filenames. That includes non-compressed FAT-based file systems
651 used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
652 programs from the mtools package.
654 The VFAT support enlarges your kernel by about 10 KB and it only
655 works if you said Y to the "DOS FAT fs support" above. Please read
656 the file <file:Documentation/filesystems/vfat.txt> for details. If
659 To compile this as a module, choose M here: the module will be called
662 config FAT_DEFAULT_CODEPAGE
663 int "Default codepage for FAT"
664 depends on MSDOS_FS || VFAT_FS
667 This option should be set to the codepage of your FAT filesystems.
668 It can be overridden with the "codepage" mount option.
669 See <file:Documentation/filesystems/vfat.txt> for more information.
671 config FAT_DEFAULT_IOCHARSET
672 string "Default iocharset for FAT"
676 Set this to the default input/output character set you'd
677 like FAT to use. It should probably match the character set
678 that most of your FAT filesystems use, and can be overridden
679 with the "iocharset" mount option for FAT filesystems.
680 Note that "utf8" is not recommended for FAT filesystems.
681 If unsure, you shouldn't set "utf8" here.
682 See <file:Documentation/filesystems/vfat.txt> for more information.
685 tristate "NTFS file system support"
688 NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003.
690 Saying Y or M here enables read support. There is partial, but
691 safe, write support available. For write support you must also
692 say Y to "NTFS write support" below.
694 There are also a number of user-space tools available, called
695 ntfsprogs. These include ntfsundelete and ntfsresize, that work
696 without NTFS support enabled in the kernel.
698 This is a rewrite from scratch of Linux NTFS support and replaced
699 the old NTFS code starting with Linux 2.5.11. A backport to
700 the Linux 2.4 kernel series is separately available as a patch
701 from the project web site.
703 For more information see <file:Documentation/filesystems/ntfs.txt>
704 and <http://linux-ntfs.sourceforge.net/>.
706 To compile this file system support as a module, choose M here: the
707 module will be called ntfs.
709 If you are not using Windows NT, 2000, XP or 2003 in addition to
710 Linux on your computer it is safe to say N.
713 bool "NTFS debugging support"
716 If you are experiencing any problems with the NTFS file system, say
717 Y here. This will result in additional consistency checks to be
718 performed by the driver as well as additional debugging messages to
719 be written to the system log. Note that debugging messages are
720 disabled by default. To enable them, supply the option debug_msgs=1
721 at the kernel command line when booting the kernel or as an option
722 to insmod when loading the ntfs module. Once the driver is active,
723 you can enable debugging messages by doing (as root):
724 echo 1 > /proc/sys/fs/ntfs-debug
725 Replacing the "1" with "0" would disable debug messages.
727 If you leave debugging messages disabled, this results in little
728 overhead, but enabling debug messages results in very significant
729 slowdown of the system.
731 When reporting bugs, please try to have available a full dump of
732 debugging messages while the misbehaviour was occurring.
735 bool "NTFS write support"
738 This enables the partial, but safe, write support in the NTFS driver.
740 The only supported operation is overwriting existing files, without
741 changing the file length. No file or directory creation, deletion or
742 renaming is possible. Note only non-resident files can be written to
743 so you may find that some very small files (<500 bytes or so) cannot
746 While we cannot guarantee that it will not damage any data, we have
747 so far not received a single report where the driver would have
748 damaged someones data so we assume it is perfectly safe to use.
750 Note: While write support is safe in this version (a rewrite from
751 scratch of the NTFS support), it should be noted that the old NTFS
752 write support, included in Linux 2.5.10 and before (since 1997),
755 This is currently useful with TopologiLinux. TopologiLinux is run
756 on top of any DOS/Microsoft Windows system without partitioning your
757 hard disk. Unlike other Linux distributions TopologiLinux does not
758 need its own partition. For more information see
759 <http://topologi-linux.sourceforge.net/>
761 It is perfectly safe to say N here.
765 menu "Pseudo filesystems"
768 bool "/proc file system support"
770 This is a virtual file system providing information about the status
771 of the system. "Virtual" means that it doesn't take up any space on
772 your hard disk: the files are created on the fly by the kernel when
773 you try to access them. Also, you cannot read the files with older
774 version of the program less: you need to use more or cat.
776 It's totally cool; for example, "cat /proc/interrupts" gives
777 information about what the different IRQs are used for at the moment
778 (there is a small number of Interrupt ReQuest lines in your computer
779 that are used by the attached devices to gain the CPU's attention --
780 often a source of trouble if two devices are mistakenly configured
781 to use the same IRQ). The program procinfo to display some
782 information about your system gathered from the /proc file system.
784 Before you can use the /proc file system, it has to be mounted,
785 meaning it has to be given a location in the directory hierarchy.
786 That location should be /proc. A command such as "mount -t proc proc
787 /proc" or the equivalent line in /etc/fstab does the job.
789 The /proc file system is explained in the file
790 <file:Documentation/filesystems/proc.txt> and on the proc(5) manpage
793 This option will enlarge your kernel by about 67 KB. Several
794 programs depend on this, so everyone should say Y here.
797 bool "/proc/kcore support" if !ARM
798 depends on PROC_FS && MMU
801 bool "/proc/vmcore support (EXPERIMENTAL)"
802 depends on PROC_FS && EXPERIMENTAL && CRASH_DUMP
805 Exports the dump image of crashed kernel in ELF format.
808 bool "sysfs file system support" if EMBEDDED
811 The sysfs filesystem is a virtual filesystem that the kernel uses to
812 export internal kernel objects, their attributes, and their
813 relationships to one another.
815 Users can use sysfs to ascertain useful information about the running
816 kernel, such as the devices the kernel has discovered on each bus and
817 which driver each is bound to. sysfs can also be used to tune devices
818 and other kernel subsystems.
820 Some system agents rely on the information in sysfs to operate.
821 /sbin/hotplug uses device and object attributes in sysfs to assist in
822 delegating policy decisions, like persistantly naming devices.
824 sysfs is currently used by the block subsystem to mount the root
825 partition. If sysfs is disabled you must specify the boot device on
826 the kernel boot command line via its major and minor numbers. For
827 example, "root=03:01" for /dev/hda1.
829 Designers of embedded systems may wish to say N here to conserve space.
832 bool "Virtual memory file system support (former shm fs)"
834 Tmpfs is a file system which keeps all files in virtual memory.
836 Everything in tmpfs is temporary in the sense that no files will be
837 created on your hard drive. The files live in memory and swap
838 space. If you unmount a tmpfs instance, everything stored therein is
841 See <file:Documentation/filesystems/tmpfs.txt> for details.
844 bool "HugeTLB file system support"
845 depends X86 || IA64 || PPC64 || SPARC64 || SUPERH || BROKEN
847 hugetlbfs is a filesystem backing for HugeTLB pages, based on
848 ramfs. For architectures that support it, say Y here and read
849 <file:Documentation/vm/hugetlbpage.txt> for details.
860 Ramfs is a file system which keeps all files in RAM. It allows
861 read and write access.
863 It is more of an programming example than a useable file system. If
864 you need a file system which lives in RAM with limit checking use
867 To compile this as a module, choose M here: the module will be called
871 tristate "Userspace-driven configuration filesystem (EXPERIMENTAL)"
872 depends on SYSFS && EXPERIMENTAL
874 configfs is a ram-based filesystem that provides the converse
875 of sysfs's functionality. Where sysfs is a filesystem-based
876 view of kernel objects, configfs is a filesystem-based manager
877 of kernel objects, or config_items.
879 Both sysfs and configfs can and should exist together on the
880 same system. One is not a replacement for the other.
884 menu "Miscellaneous filesystems"
887 tristate "ADFS file system support (EXPERIMENTAL)"
888 depends on EXPERIMENTAL
890 The Acorn Disc Filing System is the standard file system of the
891 RiscOS operating system which runs on Acorn's ARM-based Risc PC
892 systems and the Acorn Archimedes range of machines. If you say Y
893 here, Linux will be able to read from ADFS partitions on hard drives
894 and from ADFS-formatted floppy discs. If you also want to be able to
895 write to those devices, say Y to "ADFS write support" below.
897 The ADFS partition should be the first partition (i.e.,
898 /dev/[hs]d?1) on each of your drives. Please read the file
899 <file:Documentation/filesystems/adfs.txt> for further details.
901 To compile this code as a module, choose M here: the module will be
907 bool "ADFS write support (DANGEROUS)"
910 If you say Y here, you will be able to write to ADFS partitions on
911 hard drives and ADFS-formatted floppy disks. This is experimental
912 codes, so if you're unsure, say N.
915 tristate "Amiga FFS file system support (EXPERIMENTAL)"
916 depends on EXPERIMENTAL
918 The Fast File System (FFS) is the common file system used on hard
919 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
920 if you want to be able to read and write files from and to an Amiga
921 FFS partition on your hard drive. Amiga floppies however cannot be
922 read with this driver due to an incompatibility of the floppy
923 controller used in an Amiga and the standard floppy controller in
924 PCs and workstations. Read <file:Documentation/filesystems/affs.txt>
925 and <file:fs/affs/Changes>.
927 With this driver you can also mount disk files used by Bernd
928 Schmidt's Un*X Amiga Emulator
929 (<http://www.freiburg.linux.de/~uae/>).
930 If you want to do this, you will also need to say Y or M to "Loop
931 device support", above.
933 To compile this file system support as a module, choose M here: the
934 module will be called affs. If unsure, say N.
937 tristate "Apple Macintosh file system support (EXPERIMENTAL)"
938 depends on EXPERIMENTAL
941 If you say Y here, you will be able to mount Macintosh-formatted
942 floppy disks and hard drive partitions with full read-write access.
943 Please read <file:fs/hfs/HFS.txt> to learn about the available mount
946 To compile this file system support as a module, choose M here: the
947 module will be called hfs.
950 tristate "Apple Extended HFS file system support"
954 If you say Y here, you will be able to mount extended format
955 Macintosh-formatted hard drive partitions with full read-write access.
957 This file system is often called HFS+ and was introduced with
958 MacOS 8. It includes all Mac specific filesystem data such as
959 data forks and creator codes, but it also has several UNIX
960 style features such as file ownership and permissions.
963 tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)"
964 depends on EXPERIMENTAL
967 The BeOS File System (BeFS) is the native file system of Be, Inc's
968 BeOS. Notable features include support for arbitrary attributes
969 on files and directories, and database-like indeces on selected
970 attributes. (Also note that this driver doesn't make those features
971 available at this time). It is a 64 bit filesystem, so it supports
972 extremly large volumes and files.
974 If you use this filesystem, you should also say Y to at least one
975 of the NLS (native language support) options below.
977 If you don't know what this is about, say N.
979 To compile this as a module, choose M here: the module will be
986 If you say Y here, you can use the 'debug' mount option to enable
987 debugging output from the driver.
990 tristate "BFS file system support (EXPERIMENTAL)"
991 depends on EXPERIMENTAL
993 Boot File System (BFS) is a file system used under SCO UnixWare to
994 allow the bootloader access to the kernel image and other important
995 files during the boot process. It is usually mounted under /stand
996 and corresponds to the slice marked as "STAND" in the UnixWare
997 partition. You should say Y if you want to read or write the files
998 on your /stand slice from within Linux. You then also need to say Y
999 to "UnixWare slices support", below. More information about the BFS
1000 file system is contained in the file
1001 <file:Documentation/filesystems/bfs.txt>.
1003 If you don't know what this is about, say N.
1005 To compile this as a module, choose M here: the module will be called
1006 bfs. Note that the file system of your root partition (the one
1007 containing the directory /) cannot be compiled as a module.
1012 tristate "EFS file system support (read only) (EXPERIMENTAL)"
1013 depends on EXPERIMENTAL
1015 EFS is an older file system used for non-ISO9660 CD-ROMs and hard
1016 disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
1017 uses the XFS file system for hard disk partitions however).
1019 This implementation only offers read-only access. If you don't know
1020 what all this is about, it's safe to say N. For more information
1021 about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
1023 To compile the EFS file system support as a module, choose M here: the
1024 module will be called efs.
1027 tristate "Journalling Flash File System (JFFS) support"
1030 JFFS is the Journaling Flash File System developed by Axis
1031 Communications in Sweden, aimed at providing a crash/powerdown-safe
1032 file system for disk-less embedded devices. Further information is
1033 available at (<http://developer.axis.com/software/jffs/>).
1035 config JFFS_FS_VERBOSE
1036 int "JFFS debugging verbosity (0 = quiet, 3 = noisy)"
1040 Determines the verbosity level of the JFFS debugging messages.
1043 bool "JFFS stats available in /proc filesystem"
1044 depends on JFFS_FS && PROC_FS
1046 Enabling this option will cause statistics from mounted JFFS file systems
1047 to be made available to the user in the /proc/fs/jffs/ directory.
1050 tristate "Journalling Flash File System v2 (JFFS2) support"
1054 JFFS2 is the second generation of the Journalling Flash File System
1055 for use on diskless embedded devices. It provides improved wear
1056 levelling, compression and support for hard links. You cannot use
1057 this on normal block devices, only on 'MTD' devices.
1059 Further information on the design and implementation of JFFS2 is
1060 available at <http://sources.redhat.com/jffs2/>.
1062 config JFFS2_FS_DEBUG
1063 int "JFFS2 debugging verbosity (0 = quiet, 2 = noisy)"
1067 This controls the amount of debugging messages produced by the JFFS2
1068 code. Set it to zero for use in production systems. For evaluation,
1069 testing and debugging, it's advisable to set it to one. This will
1070 enable a few assertions and will print debugging messages at the
1071 KERN_DEBUG loglevel, where they won't normally be visible. Level 2
1072 is unlikely to be useful - it enables extra debugging in certain
1073 areas which at one point needed debugging, but when the bugs were
1074 located and fixed, the detailed messages were relegated to level 2.
1076 If reporting bugs, please try to have available a full dump of the
1077 messages at debug level 1 while the misbehaviour was occurring.
1079 config JFFS2_FS_WRITEBUFFER
1080 bool "JFFS2 write-buffering support"
1084 This enables the write-buffering support in JFFS2.
1086 This functionality is required to support JFFS2 on the following
1087 types of flash devices:
1089 - NOR flash with transparent ECC
1092 config JFFS2_SUMMARY
1093 bool "JFFS2 summary support (EXPERIMENTAL)"
1094 depends on JFFS2_FS && EXPERIMENTAL
1097 This feature makes it possible to use summary information
1098 for faster filesystem mount.
1100 The summary information can be inserted into a filesystem image
1101 by the utility 'sumtool'.
1105 config JFFS2_COMPRESSION_OPTIONS
1106 bool "Advanced compression options for JFFS2"
1110 Enabling this option allows you to explicitly choose which
1111 compression modules, if any, are enabled in JFFS2. Removing
1112 compressors and mean you cannot read existing file systems,
1113 and enabling experimental compressors can mean that you
1114 write a file system which cannot be read by a standard kernel.
1116 If unsure, you should _definitely_ say 'N'.
1119 bool "JFFS2 ZLIB compression support" if JFFS2_COMPRESSION_OPTIONS
1125 Zlib is designed to be a free, general-purpose, legally unencumbered,
1126 lossless data-compression library for use on virtually any computer
1127 hardware and operating system. See <http://www.gzip.org/zlib/> for
1128 further information.
1133 bool "JFFS2 RTIME compression support" if JFFS2_COMPRESSION_OPTIONS
1137 Rtime does manage to recompress already-compressed data. Say 'Y' if unsure.
1140 bool "JFFS2 RUBIN compression support" if JFFS2_COMPRESSION_OPTIONS
1144 RUBINMIPS and DYNRUBIN compressors. Say 'N' if unsure.
1147 prompt "JFFS2 default compression mode" if JFFS2_COMPRESSION_OPTIONS
1148 default JFFS2_CMODE_PRIORITY
1151 You can set here the default compression mode of JFFS2 from
1152 the available compression modes. Don't touch if unsure.
1154 config JFFS2_CMODE_NONE
1155 bool "no compression"
1157 Uses no compression.
1159 config JFFS2_CMODE_PRIORITY
1162 Tries the compressors in a predefinied order and chooses the first
1165 config JFFS2_CMODE_SIZE
1166 bool "size (EXPERIMENTAL)"
1168 Tries all compressors and chooses the one which has the smallest
1174 tristate "Compressed ROM file system support (cramfs)"
1177 Saying Y here includes support for CramFs (Compressed ROM File
1178 System). CramFs is designed to be a simple, small, and compressed
1179 file system for ROM based embedded systems. CramFs is read-only,
1180 limited to 256MB file systems (with 16MB files), and doesn't support
1181 16/32 bits uid/gid, hard links and timestamps.
1183 See <file:Documentation/filesystems/cramfs.txt> and
1184 <file:fs/cramfs/README> for further information.
1186 To compile this as a module, choose M here: the module will be called
1187 cramfs. Note that the root file system (the one containing the
1188 directory /) cannot be compiled as a module.
1193 tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
1195 FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
1196 file system format. VERITAS VxFS(TM) is the standard file system
1197 of SCO UnixWare (and possibly others) and optionally available
1198 for Sunsoft Solaris, HP-UX and many other operating systems.
1199 Currently only readonly access is supported.
1201 NOTE: the file system type as used by mount(1), mount(2) and
1202 fstab(5) is 'vxfs' as it describes the file system format, not
1205 To compile this as a module, choose M here: the module will be
1206 called freevxfs. If unsure, say N.
1210 tristate "OS/2 HPFS file system support"
1212 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
1213 is the file system used for organizing files on OS/2 hard disk
1214 partitions. Say Y if you want to be able to read files from and
1215 write files to an OS/2 HPFS partition on your hard drive. OS/2
1216 floppies however are in regular MSDOS format, so you don't need this
1217 option in order to be able to read them. Read
1218 <file:Documentation/filesystems/hpfs.txt>.
1220 To compile this file system support as a module, choose M here: the
1221 module will be called hpfs. If unsure, say N.
1226 tristate "QNX4 file system support (read only)"
1228 This is the file system used by the real-time operating systems
1229 QNX 4 and QNX 6 (the latter is also called QNX RTP).
1230 Further information is available at <http://www.qnx.com/>.
1231 Say Y if you intend to mount QNX hard disks or floppies.
1232 Unless you say Y to "QNX4FS read-write support" below, you will
1233 only be able to read these file systems.
1235 To compile this file system support as a module, choose M here: the
1236 module will be called qnx4.
1238 If you don't know whether you need it, then you don't need it:
1242 bool "QNX4FS write support (DANGEROUS)"
1243 depends on QNX4FS_FS && EXPERIMENTAL && BROKEN
1245 Say Y if you want to test write support for QNX4 file systems.
1247 It's currently broken, so for now:
1253 tristate "System V/Xenix/V7/Coherent file system support"
1255 SCO, Xenix and Coherent are commercial Unix systems for Intel
1256 machines, and Version 7 was used on the DEC PDP-11. Saying Y
1257 here would allow you to read from their floppies and hard disk
1260 If you have floppies or hard disk partitions like that, it is likely
1261 that they contain binaries from those other Unix systems; in order
1262 to run these binaries, you will want to install linux-abi which is a
1263 a set of kernel modules that lets you run SCO, Xenix, Wyse,
1264 UnixWare, Dell Unix and System V programs under Linux. It is
1265 available via FTP (user: ftp) from
1266 <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
1267 NOTE: that will work only for binaries from Intel-based systems;
1268 PDP ones will have to wait until somebody ports Linux to -11 ;-)
1270 If you only intend to mount files from some other Unix over the
1271 network using NFS, you don't need the System V file system support
1272 (but you need NFS file system support obviously).
1274 Note that this option is generally not needed for floppies, since a
1275 good portable way to transport files and directories between unixes
1276 (and even other operating systems) is given by the tar program ("man
1277 tar" or preferably "info tar"). Note also that this option has
1278 nothing whatsoever to do with the option "System V IPC". Read about
1279 the System V file system in
1280 <file:Documentation/filesystems/sysv-fs.txt>.
1281 Saying Y here will enlarge your kernel by about 27 KB.
1283 To compile this as a module, choose M here: the module will be called
1286 If you haven't heard about all of this before, it's safe to say N.
1291 tristate "UFS file system support (read only)"
1293 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
1294 OpenBSD and NeXTstep) use a file system called UFS. Some System V
1295 Unixes can create and mount hard disk partitions and diskettes using
1296 this file system as well. Saying Y here will allow you to read from
1297 these partitions; if you also want to write to them, say Y to the
1298 experimental "UFS file system write support", below. Please read the
1299 file <file:Documentation/filesystems/ufs.txt> for more information.
1301 The recently released UFS2 variant (used in FreeBSD 5.x) is
1302 READ-ONLY supported.
1304 If you only intend to mount files from some other Unix over the
1305 network using NFS, you don't need the UFS file system support (but
1306 you need NFS file system support obviously).
1308 Note that this option is generally not needed for floppies, since a
1309 good portable way to transport files and directories between unixes
1310 (and even other operating systems) is given by the tar program ("man
1311 tar" or preferably "info tar").
1313 When accessing NeXTstep files, you may need to convert them from the
1314 NeXT character set to the Latin1 character set; use the program
1315 recode ("info recode") for this purpose.
1317 To compile the UFS file system support as a module, choose M here: the
1318 module will be called ufs.
1320 If you haven't heard about all of this before, it's safe to say N.
1323 bool "UFS file system write support (DANGEROUS)"
1324 depends on UFS_FS && EXPERIMENTAL && BROKEN
1326 Say Y here if you want to try writing to UFS partitions. This is
1327 experimental, so you should back up your UFS partitions beforehand.
1331 menu "Network File Systems"
1335 tristate "NFS file system support"
1339 select NFS_ACL_SUPPORT if NFS_V3_ACL
1341 If you are connected to some other (usually local) Unix computer
1342 (using SLIP, PLIP, PPP or Ethernet) and want to mount files residing
1343 on that computer (the NFS server) using the Network File Sharing
1344 protocol, say Y. "Mounting files" means that the client can access
1345 the files with usual UNIX commands as if they were sitting on the
1346 client's hard disk. For this to work, the server must run the
1347 programs nfsd and mountd (but does not need to have NFS file system
1348 support enabled in its kernel). NFS is explained in the Network
1349 Administrator's Guide, available from
1350 <http://www.tldp.org/docs.html#guide>, on its man page: "man
1351 nfs", and in the NFS-HOWTO.
1353 A superior but less widely used alternative to NFS is provided by
1354 the Coda file system; see "Coda file system support" below.
1356 If you say Y here, you should have said Y to TCP/IP networking also.
1357 This option would enlarge your kernel by about 27 KB.
1359 To compile this file system support as a module, choose M here: the
1360 module will be called nfs.
1362 If you are configuring a diskless machine which will mount its root
1363 file system over NFS at boot time, say Y here and to "Kernel
1364 level IP autoconfiguration" above and to "Root file system on NFS"
1365 below. You cannot compile this driver as a module in this case.
1366 There are two packages designed for booting diskless machines over
1367 the net: netboot, available from
1368 <http://ftp1.sourceforge.net/netboot/>, and Etherboot,
1369 available from <http://ftp1.sourceforge.net/etherboot/>.
1371 If you don't know what all this is about, say N.
1374 bool "Provide NFSv3 client support"
1377 Say Y here if you want your NFS client to be able to speak version
1378 3 of the NFS protocol.
1383 bool "Provide client support for the NFSv3 ACL protocol extension"
1386 Implement the NFSv3 ACL protocol extension for manipulating POSIX
1387 Access Control Lists. The server should also be compiled with
1388 the NFSv3 ACL protocol extension; see the CONFIG_NFSD_V3_ACL option.
1393 bool "Provide NFSv4 client support (EXPERIMENTAL)"
1394 depends on NFS_FS && EXPERIMENTAL
1395 select RPCSEC_GSS_KRB5
1397 Say Y here if you want your NFS client to be able to speak the newer
1398 version 4 of the NFS protocol.
1400 Note: Requires auxiliary userspace daemons which may be found on
1401 http://www.citi.umich.edu/projects/nfsv4/
1406 bool "Allow direct I/O on NFS files (EXPERIMENTAL)"
1407 depends on NFS_FS && EXPERIMENTAL
1409 This option enables applications to perform uncached I/O on files
1410 in NFS file systems using the O_DIRECT open() flag. When O_DIRECT
1411 is set for a file, its data is not cached in the system's page
1412 cache. Data is moved to and from user-level application buffers
1413 directly. Unlike local disk-based file systems, NFS O_DIRECT has
1414 no alignment restrictions.
1416 Unless your program is designed to use O_DIRECT properly, you are
1417 much better off allowing the NFS client to manage data caching for
1418 you. Misusing O_DIRECT can cause poor server performance or network
1419 storms. This kernel build option defaults OFF to avoid exposing
1420 system administrators unwittingly to a potentially hazardous
1423 For more details on NFS O_DIRECT, see fs/nfs/direct.c.
1425 If unsure, say N. This reduces the size of the NFS client, and
1426 causes open() to return EINVAL if a file residing in NFS is
1427 opened with the O_DIRECT flag.
1430 tristate "NFS server support"
1435 select NFS_ACL_SUPPORT if NFSD_V3_ACL || NFSD_V2_ACL
1437 If you want your Linux box to act as an NFS *server*, so that other
1438 computers on your local network which support NFS can access certain
1439 directories on your box transparently, you have two options: you can
1440 use the self-contained user space program nfsd, in which case you
1441 should say N here, or you can say Y and use the kernel based NFS
1442 server. The advantage of the kernel based solution is that it is
1445 In either case, you will need support software; the respective
1446 locations are given in the file <file:Documentation/Changes> in the
1449 If you say Y here, you will get support for version 2 of the NFS
1450 protocol (NFSv2). If you also want NFSv3, say Y to the next question
1453 Please read the NFS-HOWTO, available from
1454 <http://www.tldp.org/docs.html#howto>.
1456 To compile the NFS server support as a module, choose M here: the
1457 module will be called nfsd. If unsure, say N.
1464 bool "Provide NFSv3 server support"
1467 If you would like to include the NFSv3 server as well as the NFSv2
1468 server, say Y here. If unsure, say Y.
1471 bool "Provide server support for the NFSv3 ACL protocol extension"
1475 Implement the NFSv3 ACL protocol extension for manipulating POSIX
1476 Access Control Lists on exported file systems. NFS clients should
1477 be compiled with the NFSv3 ACL protocol extension; see the
1478 CONFIG_NFS_V3_ACL option. If unsure, say N.
1481 bool "Provide NFSv4 server support (EXPERIMENTAL)"
1482 depends on NFSD_V3 && EXPERIMENTAL
1488 If you would like to include the NFSv4 server as well as the NFSv2
1489 and NFSv3 servers, say Y here. This feature is experimental, and
1490 should only be used if you are interested in helping to test NFSv4.
1494 bool "Provide NFS server over TCP support"
1498 If you want your NFS server to support TCP connections, say Y here.
1499 TCP connections usually perform better than the default UDP when
1500 the network is lossy or congested. If unsure, say Y.
1503 bool "Root file system on NFS"
1504 depends on NFS_FS=y && IP_PNP
1506 If you want your Linux box to mount its whole root file system (the
1507 one containing the directory /) from some other computer over the
1508 net via NFS (presumably because your box doesn't have a hard disk),
1509 say Y. Read <file:Documentation/nfsroot.txt> for details. It is
1510 likely that in this case, you also want to say Y to "Kernel level IP
1511 autoconfiguration" so that your box can discover its network address
1514 Most people say N here.
1521 depends on NFSD_V3 || NFS_V3
1527 config NFS_ACL_SUPPORT
1533 depends on NFSD || NFS_FS
1542 config RPCSEC_GSS_KRB5
1543 tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
1544 depends on SUNRPC && EXPERIMENTAL
1550 Provides for secure RPC calls by means of a gss-api
1551 mechanism based on Kerberos V5. This is required for
1554 Note: Requires an auxiliary userspace daemon which may be found on
1555 http://www.citi.umich.edu/projects/nfsv4/
1559 config RPCSEC_GSS_SPKM3
1560 tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
1561 depends on SUNRPC && EXPERIMENTAL
1568 Provides for secure RPC calls by means of a gss-api
1569 mechanism based on the SPKM3 public-key mechanism.
1571 Note: Requires an auxiliary userspace daemon which may be found on
1572 http://www.citi.umich.edu/projects/nfsv4/
1577 tristate "SMB file system support (to mount Windows shares etc.)"
1581 SMB (Server Message Block) is the protocol Windows for Workgroups
1582 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
1583 files and printers over local networks. Saying Y here allows you to
1584 mount their file systems (often called "shares" in this context) and
1585 access them just like any other Unix directory. Currently, this
1586 works only if the Windows machines use TCP/IP as the underlying
1587 transport protocol, and not NetBEUI. For details, read
1588 <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
1589 available from <http://www.tldp.org/docs.html#howto>.
1591 Note: if you just want your box to act as an SMB *server* and make
1592 files and printing services available to Windows clients (which need
1593 to have a TCP/IP stack), you don't need to say Y here; you can use
1594 the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
1597 General information about how to connect Linux, Windows machines and
1598 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1600 To compile the SMB support as a module, choose M here: the module will
1601 be called smbfs. Most people say N, however.
1603 config SMB_NLS_DEFAULT
1604 bool "Use a default NLS"
1607 Enabling this will make smbfs use nls translations by default. You
1608 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
1609 settings and you need to give the default nls for the SMB server as
1610 CONFIG_SMB_NLS_REMOTE.
1612 The nls settings can be changed at mount time, if your smbmount
1613 supports that, using the codepage and iocharset parameters.
1615 smbmount from samba 2.2.0 or later supports this.
1617 config SMB_NLS_REMOTE
1618 string "Default Remote NLS Option"
1619 depends on SMB_NLS_DEFAULT
1622 This setting allows you to specify a default value for which
1623 codepage the server uses. If this field is left blank no
1624 translations will be done by default. The local codepage/charset
1625 default to CONFIG_NLS_DEFAULT.
1627 The nls settings can be changed at mount time, if your smbmount
1628 supports that, using the codepage and iocharset parameters.
1630 smbmount from samba 2.2.0 or later supports this.
1633 tristate "CIFS support (advanced network filesystem for Samba, Window and other CIFS compliant servers)"
1637 This is the client VFS module for the Common Internet File System
1638 (CIFS) protocol which is the successor to the Server Message Block
1639 (SMB) protocol, the native file sharing mechanism for most early
1640 PC operating systems. The CIFS protocol is fully supported by
1641 file servers such as Windows 2000 (including Windows 2003, NT 4
1642 and Windows XP) as well by Samba (which provides excellent CIFS
1643 server support for Linux and many other operating systems). Limited
1644 support for Windows ME and similar servers is provided as well.
1645 You must use the smbfs client filesystem to access older SMB servers
1646 such as OS/2 and DOS.
1648 The intent of the cifs module is to provide an advanced
1649 network file system client for mounting to CIFS compliant servers,
1650 including support for dfs (hierarchical name space), secure per-user
1651 session establishment, safe distributed caching (oplock), optional
1652 packet signing, Unicode and other internationalization improvements,
1653 and optional Winbind (nsswitch) integration. You do not need to enable
1654 cifs if running only a (Samba) server. It is possible to enable both
1655 smbfs and cifs (e.g. if you are using CIFS for accessing Windows 2003
1656 and Samba 3 servers, and smbfs for accessing old servers). If you need
1657 to mount to Samba or Windows from this machine, say Y.
1660 bool "CIFS statistics"
1663 Enabling this option will cause statistics for each server share
1664 mounted by the cifs client to be displayed in /proc/fs/cifs/Stats
1667 bool "CIFS extended statistics"
1668 depends on CIFS_STATS
1670 Enabling this option will allow more detailed statistics on SMB
1671 request timing to be displayed in /proc/fs/cifs/DebugData and also
1672 allow optional logging of slow responses to dmesg (depending on the
1673 value of /proc/fs/cifs/cifsFYI, see fs/cifs/README for more details).
1674 These additional statistics may have a minor effect on performance
1675 and memory utilization.
1677 Unless you are a developer or are doing network performance analysis
1681 bool "CIFS extended attributes"
1684 Extended attributes are name:value pairs associated with inodes by
1685 the kernel or by users (see the attr(5) manual page, or visit
1686 <http://acl.bestbits.at/> for details). CIFS maps the name of
1687 extended attributes beginning with the user namespace prefix
1688 to SMB/CIFS EAs. EAs are stored on Windows servers without the
1689 user namespace prefix, but their names are seen by Linux cifs clients
1690 prefaced by the user namespace prefix. The system namespace
1691 (used by some filesystems to store ACLs) is not supported at
1697 bool "CIFS POSIX Extensions"
1698 depends on CIFS_XATTR
1700 Enabling this option will cause the cifs client to attempt to
1701 negotiate a newer dialect with servers, such as Samba 3.0.5
1702 or later, that optionally can handle more POSIX like (rather
1703 than Windows like) file behavior. It also enables
1704 support for POSIX ACLs (getfacl and setfacl) to servers
1705 (such as Samba 3.10 and later) which can negotiate
1706 CIFS POSIX ACL support. If unsure, say N.
1708 config CIFS_EXPERIMENTAL
1709 bool "CIFS Experimental Features (EXPERIMENTAL)"
1710 depends on CIFS && EXPERIMENTAL
1712 Enables cifs features under testing. These features are
1713 experimental and currently include support for writepages
1714 (multipage writebehind performance improvements) and directory
1715 change notification ie fcntl(F_DNOTIFY) as well as some security
1716 improvements. Some also depend on setting at runtime the
1717 pseudo-file /proc/fs/cifs/Experimental (which is disabled by
1718 default). See the file fs/cifs/README for more details.
1723 bool "CIFS Kerberos/SPNEGO advanced session setup (EXPERIMENTAL)"
1724 depends on CIFS_EXPERIMENTAL
1727 Enables an upcall mechanism for CIFS which will be used to contact
1728 userspace helper utilities to provide SPNEGO packaged Kerberos
1729 tickets which are needed to mount to certain secure servers
1730 (for which more secure Kerberos authentication is required). If
1734 tristate "NCP file system support (to mount NetWare volumes)"
1735 depends on IPX!=n || INET
1737 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
1738 used by Novell NetWare clients to talk to file servers. It is to
1739 IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
1740 to mount NetWare file server volumes and to access them just like
1741 any other Unix directory. For details, please read the file
1742 <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
1743 the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
1745 You do not have to say Y here if you want your Linux box to act as a
1746 file *server* for Novell NetWare clients.
1748 General information about how to connect Linux, Windows machines and
1749 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1751 To compile this as a module, choose M here: the module will be called
1752 ncpfs. Say N unless you are connected to a Novell network.
1754 source "fs/ncpfs/Kconfig"
1757 tristate "Coda file system support (advanced network fs)"
1760 Coda is an advanced network file system, similar to NFS in that it
1761 enables you to mount file systems of a remote server and access them
1762 with regular Unix commands as if they were sitting on your hard
1763 disk. Coda has several advantages over NFS: support for
1764 disconnected operation (e.g. for laptops), read/write server
1765 replication, security model for authentication and encryption,
1766 persistent client caches and write back caching.
1768 If you say Y here, your Linux box will be able to act as a Coda
1769 *client*. You will need user level code as well, both for the
1770 client and server. Servers are currently user level, i.e. they need
1771 no kernel support. Please read
1772 <file:Documentation/filesystems/coda.txt> and check out the Coda
1773 home page <http://www.coda.cs.cmu.edu/>.
1775 To compile the coda client support as a module, choose M here: the
1776 module will be called coda.
1778 config CODA_FS_OLD_API
1779 bool "Use 96-bit Coda file identifiers"
1782 A new kernel-userspace API had to be introduced for Coda v6.0
1783 to support larger 128-bit file identifiers as needed by the
1784 new realms implementation.
1786 However this new API is not backward compatible with older
1787 clients. If you really need to run the old Coda userspace
1788 cache manager then say Y.
1790 For most cases you probably want to say N.
1793 # for fs/nls/Config.in
1794 tristate "Andrew File System support (AFS) (Experimental)"
1795 depends on INET && EXPERIMENTAL
1798 If you say Y here, you will get an experimental Andrew File System
1799 driver. It currently only supports unsecured read-only AFS access.
1801 See <file:Documentation/filesystems/afs.txt> for more intormation.
1809 tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
1810 depends on INET && EXPERIMENTAL
1812 If you say Y here, you will get experimental support for
1813 Plan 9 resource sharing via the 9P2000 protocol.
1815 See <http://v9fs.sf.net> for more information.
1821 menu "Partition Types"
1823 source "fs/partitions/Kconfig"
1827 source "fs/nls/Kconfig"
1828 source "fs/dlm/Kconfig"