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_CC_REDUCE_OPTIMZE
207 bool "Reduce CC optimization level to workaround compiler bugs"
211 gcc -O2 (the kernel default) is overaggressive on ppc32 when many inline
212 functions are used. This causes the compiler to advance the stack
213 pointer out of the available stack space, corrupting kernel space,
214 and causing a panic. Since this behavior only affects ppc32, this ifeq
215 will work around it. If any other architecture displays this behavior,
218 config REISERFS_CHECK
219 bool "Enable reiserfs debug mode"
220 depends on REISERFS_FS
222 If you set this to Y, then ReiserFS will perform every check it can
223 possibly imagine of its internal consistency throughout its
224 operation. It will also go substantially slower. More than once we
225 have forgotten that this was on, and then gone despondent over the
226 latest benchmarks.:-) Use of this option allows our team to go all
227 out in checking for consistency when debugging without fear of its
228 effect on end users. If you are on the verge of sending in a bug
229 report, say Y and you might get a useful error message. Almost
230 everyone should say N.
232 config REISERFS_PROC_INFO
233 bool "Stats in /proc/fs/reiserfs"
234 depends on REISERFS_FS
236 Create under /proc/fs/reiserfs a hierarchy of files, displaying
237 various ReiserFS statistics and internal data at the expense of
238 making your kernel or module slightly larger (+8 KB). This also
239 increases the amount of kernel memory required for each mount.
240 Almost everyone but ReiserFS developers and people fine-tuning
241 reiserfs or tracing problems should say N.
243 config REISERFS_FS_XATTR
244 bool "ReiserFS extended attributes"
245 depends on REISERFS_FS
247 Extended attributes are name:value pairs associated with inodes by
248 the kernel or by users (see the attr(5) manual page, or visit
249 <http://acl.bestbits.at/> for details).
253 config REISERFS_FS_POSIX_ACL
254 bool "ReiserFS POSIX Access Control Lists"
255 depends on REISERFS_FS_XATTR
258 Posix Access Control Lists (ACLs) support permissions for users and
259 groups beyond the owner/group/world scheme.
261 To learn more about Access Control Lists, visit the Posix ACLs for
262 Linux website <http://acl.bestbits.at/>.
264 If you don't know what Access Control Lists are, say N
266 config REISERFS_FS_SECURITY
267 bool "ReiserFS Security Labels"
268 depends on REISERFS_FS_XATTR
270 Security labels support alternative access control models
271 implemented by security modules like SELinux. This option
272 enables an extended attribute handler for file security
273 labels in the ReiserFS filesystem.
275 If you are not using a security module that requires using
276 extended attributes for file security labels, say N.
279 tristate "JFS filesystem support"
282 This is a port of IBM's Journaled Filesystem . More information is
283 available in the file <file:Documentation/filesystems/jfs.txt>.
285 If you do not intend to use the JFS filesystem, say N.
288 bool "JFS POSIX Access Control Lists"
292 Posix Access Control Lists (ACLs) support permissions for users and
293 groups beyond the owner/group/world scheme.
295 To learn more about Access Control Lists, visit the Posix ACLs for
296 Linux website <http://acl.bestbits.at/>.
298 If you don't know what Access Control Lists are, say N
301 bool "JFS Security Labels"
304 Security labels support alternative access control models
305 implemented by security modules like SELinux. This option
306 enables an extended attribute handler for file security
307 labels in the jfs filesystem.
309 If you are not using a security module that requires using
310 extended attributes for file security labels, say N.
316 If you are experiencing any problems with the JFS filesystem, say
317 Y here. This will result in additional debugging messages to be
318 written to the system log. Under normal circumstances, this
319 results in very little overhead.
321 config JFS_STATISTICS
322 bool "JFS statistics"
325 Enabling this option will cause statistics from the JFS file system
326 to be made available to the user in the /proc/fs/jfs/ directory.
329 # Posix ACL utility routines (for now, only ext2/ext3/jfs/reiserfs)
331 # NOTE: you can implement Posix ACLs without these helpers (XFS does).
332 # Never use this symbol for ifdefs.
337 source "fs/xfs/Kconfig"
340 tristate "OCFS2 file system support (EXPERIMENTAL)"
341 depends on NET && EXPERIMENTAL
347 OCFS2 is a general purpose extent based shared disk cluster file
348 system with many similarities to ext3. It supports 64 bit inode
349 numbers, and has automatically extending metadata groups which may
350 also make it attractive for non-clustered use.
352 You'll want to install the ocfs2-tools package in order to at least
355 Project web page: http://oss.oracle.com/projects/ocfs2
356 Tools web page: http://oss.oracle.com/projects/ocfs2-tools
357 OCFS2 mailing lists: http://oss.oracle.com/projects/ocfs2/mailman/
359 Note: Features which OCFS2 does not support yet:
360 - extended attributes
361 - shared writeable mmap
362 - loopback is supported, but data written will not
365 - cluster aware flock
366 - Directory change notification (F_NOTIFY)
367 - Distributed Caching (F_SETLEASE/F_GETLEASE/break_lease)
369 - readpages / writepages (not user visible)
372 tristate "Minix fs support"
374 Minix is a simple operating system used in many classes about OS's.
375 The minix file system (method to organize files on a hard disk
376 partition or a floppy disk) was the original file system for Linux,
377 but has been superseded by the second extended file system ext2fs.
378 You don't want to use the minix file system on your hard disk
379 because of certain built-in restrictions, but it is sometimes found
380 on older Linux floppy disks. This option will enlarge your kernel
381 by about 28 KB. If unsure, say N.
383 To compile this file system support as a module, choose M here: the
384 module will be called minix. Note that the file system of your root
385 partition (the one containing the directory /) cannot be compiled as
389 tristate "ROM file system support"
391 This is a very small read-only file system mainly intended for
392 initial ram disks of installation disks, but it could be used for
393 other read-only media as well. Read
394 <file:Documentation/filesystems/romfs.txt> for details.
396 To compile this file system support as a module, choose M here: the
397 module will be called romfs. Note that the file system of your
398 root partition (the one containing the directory /) cannot be a
401 If you don't know whether you need it, then you don't need it:
405 bool "Inotify file change notification support"
408 Say Y here to enable inotify support and the associated system
409 calls. Inotify is a file change notification system and a
410 replacement for dnotify. Inotify fixes numerous shortcomings in
411 dnotify and introduces several new features. It allows monitoring
412 of both files and directories via a single open fd. Other features
413 include multiple file events, one-shot support, and unmount
416 For more information, see Documentation/filesystems/inotify.txt
423 If you say Y here, you will be able to set per user limits for disk
424 usage (also called disk quotas). Currently, it works for the
425 ext2, ext3, and reiserfs file system. ext3 also supports journalled
426 quotas for which you don't need to run quotacheck(8) after an unclean
428 For further details, read the Quota mini-HOWTO, available from
429 <http://www.tldp.org/docs.html#howto>, or the documentation provided
430 with the quota tools. Probably the quota support is only useful for
431 multi user systems. If unsure, say N.
434 tristate "Old quota format support"
437 This quota format was (is) used by kernels earlier than 2.4.22. If
438 you have quota working and you don't want to convert to new quota
442 tristate "Quota format v2 support"
445 This quota format allows using quotas with 32-bit UIDs/GIDs. If you
446 need this functionality say Y here.
450 depends on XFS_QUOTA || QUOTA
454 bool "Dnotify support" if EMBEDDED
457 Dnotify is a directory-based per-fd file change notification system
458 that uses signals to communicate events to user-space. There exist
459 superior alternatives, but some applications may still rely on
462 Because of this, if unsure, say Y.
465 tristate "Kernel automounter support"
467 The automounter is a tool to automatically mount remote file systems
468 on demand. This implementation is partially kernel-based to reduce
469 overhead in the already-mounted case; this is unlike the BSD
470 automounter (amd), which is a pure user space daemon.
472 To use the automounter you need the user-space tools from the autofs
473 package; you can find the location in <file:Documentation/Changes>.
474 You also want to answer Y to "NFS file system support", below.
476 If you want to use the newer version of the automounter with more
477 features, say N here and say Y to "Kernel automounter v4 support",
480 To compile this support as a module, choose M here: the module will be
483 If you are not a part of a fairly large, distributed network, you
484 probably do not need an automounter, and can say N here.
487 tristate "Kernel automounter version 4 support (also supports v3)"
489 The automounter is a tool to automatically mount remote file systems
490 on demand. This implementation is partially kernel-based to reduce
491 overhead in the already-mounted case; this is unlike the BSD
492 automounter (amd), which is a pure user space daemon.
494 To use the automounter you need the user-space tools from
495 <ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4/>; you also
496 want to answer Y to "NFS file system support", below.
498 To compile this support as a module, choose M here: the module will be
499 called autofs4. You will need to add "alias autofs autofs4" to your
500 modules configuration file.
502 If you are not a part of a fairly large, distributed network or
503 don't have a laptop which needs to dynamically reconfigure to the
504 local network, you probably do not need an automounter, and can say
508 tristate "Filesystem in Userspace support"
510 With FUSE it is possible to implement a fully functional filesystem
511 in a userspace program.
513 There's also companion library: libfuse. This library along with
514 utilities is available from the FUSE homepage:
515 <http://fuse.sourceforge.net/>
517 See <file:Documentation/filesystems/fuse.txt> for more information.
518 See <file:Documentation/Changes> for needed library/utility version.
520 If you want to develop a userspace FS, or if you want to use
521 a filesystem based on FUSE, answer Y or M.
523 menu "CD-ROM/DVD Filesystems"
526 tristate "ISO 9660 CDROM file system support"
528 This is the standard file system used on CD-ROMs. It was previously
529 known as "High Sierra File System" and is called "hsfs" on other
530 Unix systems. The so-called Rock-Ridge extensions which allow for
531 long Unix filenames and symbolic links are also supported by this
532 driver. If you have a CD-ROM drive and want to do more with it than
533 just listen to audio CDs and watch its LEDs, say Y (and read
534 <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO,
535 available from <http://www.tldp.org/docs.html#howto>), thereby
536 enlarging your kernel by about 27 KB; otherwise say N.
538 To compile this file system support as a module, choose M here: the
539 module will be called isofs.
542 bool "Microsoft Joliet CDROM extensions"
543 depends on ISO9660_FS
546 Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system
547 which allows for long filenames in unicode format (unicode is the
548 new 16 bit character code, successor to ASCII, which encodes the
549 characters of almost all languages of the world; see
550 <http://www.unicode.org/> for more information). Say Y here if you
551 want to be able to read Joliet CD-ROMs under Linux.
554 bool "Transparent decompression extension"
555 depends on ISO9660_FS
558 This is a Linux-specific extension to RockRidge which lets you store
559 data in compressed form on a CD-ROM and have it transparently
560 decompressed when the CD-ROM is accessed. See
561 <http://www.kernel.org/pub/linux/utils/fs/zisofs/> for the tools
562 necessary to create such a filesystem. Say Y here if you want to be
563 able to read such compressed CD-ROMs.
566 # for fs/nls/Config.in
572 tristate "UDF file system support"
574 This is the new file system used on some CD-ROMs and DVDs. Say Y if
575 you intend to mount DVD discs or CDRW's written in packet mode, or
576 if written to by other UDF utilities, such as DirectCD.
577 Please read <file:Documentation/filesystems/udf.txt>.
579 To compile this file system support as a module, choose M here: the
580 module will be called udf.
587 depends on (UDF_FS=m && NLS) || (UDF_FS=y && NLS=y)
591 menu "DOS/FAT/NT Filesystems"
597 If you want to use one of the FAT-based file systems (the MS-DOS and
598 VFAT (Windows 95) file systems), then you must say Y or M here
599 to include FAT support. You will then be able to mount partitions or
600 diskettes with FAT-based file systems and transparently access the
601 files on them, i.e. MSDOS files will look and behave just like all
604 This FAT support is not a file system in itself, it only provides
605 the foundation for the other file systems. You will have to say Y or
606 M to at least one of "MSDOS fs support" or "VFAT fs support" in
607 order to make use of it.
609 Another way to read and write MSDOS floppies and hard drive
610 partitions from within Linux (but not transparently) is with the
611 mtools ("man mtools") program suite. You don't need to say Y here in
614 If you need to move large files on floppies between a DOS and a
615 Linux box, say Y here, mount the floppy under Linux with an MSDOS
616 file system and use GNU tar's M option. GNU tar is a program
617 available for Unix and DOS ("man tar" or "info tar").
619 It is now also becoming possible to read and write compressed FAT
620 file systems; read <file:Documentation/filesystems/fat_cvf.txt> for
623 The FAT support will enlarge your kernel by about 37 KB. If unsure,
626 To compile this as a module, choose M here: the module will be called
627 fat. Note that if you compile the FAT support as a module, you
628 cannot compile any of the FAT-based file systems into the kernel
629 -- they will have to be modules as well.
632 tristate "MSDOS fs support"
635 This allows you to mount MSDOS partitions of your hard drive (unless
636 they are compressed; to access compressed MSDOS partitions under
637 Linux, you can either use the DOS emulator DOSEMU, described in the
638 DOSEMU-HOWTO, available from
639 <http://www.tldp.org/docs.html#howto>, or try dmsdosfs in
640 <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you
641 intend to use dosemu with a non-compressed MSDOS partition, say Y
642 here) and MSDOS floppies. This means that file access becomes
643 transparent, i.e. the MSDOS files look and behave just like all
646 If you have Windows 95 or Windows NT installed on your MSDOS
647 partitions, you should use the VFAT file system (say Y to "VFAT fs
648 support" below), or you will not be able to see the long filenames
649 generated by Windows 95 / Windows NT.
651 This option will enlarge your kernel by about 7 KB. If unsure,
652 answer Y. This will only work if you said Y to "DOS FAT fs support"
653 as well. To compile this as a module, choose M here: the module will
657 tristate "VFAT (Windows-95) fs support"
660 This option provides support for normal Windows file systems with
661 long filenames. That includes non-compressed FAT-based file systems
662 used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
663 programs from the mtools package.
665 The VFAT support enlarges your kernel by about 10 KB and it only
666 works if you said Y to the "DOS FAT fs support" above. Please read
667 the file <file:Documentation/filesystems/vfat.txt> for details. If
670 To compile this as a module, choose M here: the module will be called
673 config FAT_DEFAULT_CODEPAGE
674 int "Default codepage for FAT"
675 depends on MSDOS_FS || VFAT_FS
678 This option should be set to the codepage of your FAT filesystems.
679 It can be overridden with the "codepage" mount option.
680 See <file:Documentation/filesystems/vfat.txt> for more information.
682 config FAT_DEFAULT_IOCHARSET
683 string "Default iocharset for FAT"
687 Set this to the default input/output character set you'd
688 like FAT to use. It should probably match the character set
689 that most of your FAT filesystems use, and can be overridden
690 with the "iocharset" mount option for FAT filesystems.
691 Note that "utf8" is not recommended for FAT filesystems.
692 If unsure, you shouldn't set "utf8" here.
693 See <file:Documentation/filesystems/vfat.txt> for more information.
696 tristate "NTFS file system support"
699 NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003.
701 Saying Y or M here enables read support. There is partial, but
702 safe, write support available. For write support you must also
703 say Y to "NTFS write support" below.
705 There are also a number of user-space tools available, called
706 ntfsprogs. These include ntfsundelete and ntfsresize, that work
707 without NTFS support enabled in the kernel.
709 This is a rewrite from scratch of Linux NTFS support and replaced
710 the old NTFS code starting with Linux 2.5.11. A backport to
711 the Linux 2.4 kernel series is separately available as a patch
712 from the project web site.
714 For more information see <file:Documentation/filesystems/ntfs.txt>
715 and <http://linux-ntfs.sourceforge.net/>.
717 To compile this file system support as a module, choose M here: the
718 module will be called ntfs.
720 If you are not using Windows NT, 2000, XP or 2003 in addition to
721 Linux on your computer it is safe to say N.
724 bool "NTFS debugging support"
727 If you are experiencing any problems with the NTFS file system, say
728 Y here. This will result in additional consistency checks to be
729 performed by the driver as well as additional debugging messages to
730 be written to the system log. Note that debugging messages are
731 disabled by default. To enable them, supply the option debug_msgs=1
732 at the kernel command line when booting the kernel or as an option
733 to insmod when loading the ntfs module. Once the driver is active,
734 you can enable debugging messages by doing (as root):
735 echo 1 > /proc/sys/fs/ntfs-debug
736 Replacing the "1" with "0" would disable debug messages.
738 If you leave debugging messages disabled, this results in little
739 overhead, but enabling debug messages results in very significant
740 slowdown of the system.
742 When reporting bugs, please try to have available a full dump of
743 debugging messages while the misbehaviour was occurring.
746 bool "NTFS write support"
749 This enables the partial, but safe, write support in the NTFS driver.
751 The only supported operation is overwriting existing files, without
752 changing the file length. No file or directory creation, deletion or
753 renaming is possible. Note only non-resident files can be written to
754 so you may find that some very small files (<500 bytes or so) cannot
757 While we cannot guarantee that it will not damage any data, we have
758 so far not received a single report where the driver would have
759 damaged someones data so we assume it is perfectly safe to use.
761 Note: While write support is safe in this version (a rewrite from
762 scratch of the NTFS support), it should be noted that the old NTFS
763 write support, included in Linux 2.5.10 and before (since 1997),
766 This is currently useful with TopologiLinux. TopologiLinux is run
767 on top of any DOS/Microsoft Windows system without partitioning your
768 hard disk. Unlike other Linux distributions TopologiLinux does not
769 need its own partition. For more information see
770 <http://topologi-linux.sourceforge.net/>
772 It is perfectly safe to say N here.
776 menu "Pseudo filesystems"
779 bool "/proc file system support"
781 This is a virtual file system providing information about the status
782 of the system. "Virtual" means that it doesn't take up any space on
783 your hard disk: the files are created on the fly by the kernel when
784 you try to access them. Also, you cannot read the files with older
785 version of the program less: you need to use more or cat.
787 It's totally cool; for example, "cat /proc/interrupts" gives
788 information about what the different IRQs are used for at the moment
789 (there is a small number of Interrupt ReQuest lines in your computer
790 that are used by the attached devices to gain the CPU's attention --
791 often a source of trouble if two devices are mistakenly configured
792 to use the same IRQ). The program procinfo to display some
793 information about your system gathered from the /proc file system.
795 Before you can use the /proc file system, it has to be mounted,
796 meaning it has to be given a location in the directory hierarchy.
797 That location should be /proc. A command such as "mount -t proc proc
798 /proc" or the equivalent line in /etc/fstab does the job.
800 The /proc file system is explained in the file
801 <file:Documentation/filesystems/proc.txt> and on the proc(5) manpage
804 This option will enlarge your kernel by about 67 KB. Several
805 programs depend on this, so everyone should say Y here.
808 bool "/proc/kcore support" if !ARM
809 depends on PROC_FS && MMU
812 bool "/proc/vmcore support (EXPERIMENTAL)"
813 depends on PROC_FS && EXPERIMENTAL && CRASH_DUMP
816 Exports the dump image of crashed kernel in ELF format.
819 bool "sysfs file system support" if EMBEDDED
822 The sysfs filesystem is a virtual filesystem that the kernel uses to
823 export internal kernel objects, their attributes, and their
824 relationships to one another.
826 Users can use sysfs to ascertain useful information about the running
827 kernel, such as the devices the kernel has discovered on each bus and
828 which driver each is bound to. sysfs can also be used to tune devices
829 and other kernel subsystems.
831 Some system agents rely on the information in sysfs to operate.
832 /sbin/hotplug uses device and object attributes in sysfs to assist in
833 delegating policy decisions, like persistantly naming devices.
835 sysfs is currently used by the block subsystem to mount the root
836 partition. If sysfs is disabled you must specify the boot device on
837 the kernel boot command line via its major and minor numbers. For
838 example, "root=03:01" for /dev/hda1.
840 Designers of embedded systems may wish to say N here to conserve space.
843 bool "Virtual memory file system support (former shm fs)"
845 Tmpfs is a file system which keeps all files in virtual memory.
847 Everything in tmpfs is temporary in the sense that no files will be
848 created on your hard drive. The files live in memory and swap
849 space. If you unmount a tmpfs instance, everything stored therein is
852 See <file:Documentation/filesystems/tmpfs.txt> for details.
854 config TMPFS_POSIX_ACL
855 bool "Tmpfs POSIX Access Control Lists"
859 POSIX Access Control Lists (ACLs) support permissions for users and
860 groups beyond the owner/group/world scheme.
862 To learn more about Access Control Lists, visit the POSIX ACLs for
863 Linux website <http://acl.bestbits.at/>.
865 If you don't know what Access Control Lists are, say N.
868 bool "HugeTLB file system support"
869 depends X86 || IA64 || PPC64 || SPARC64 || SUPERH || BROKEN
872 hugetlbfs is a filesystem backing for HugeTLB pages, based on
873 ramfs. For architectures that support it, say Y here and read
874 <file:Documentation/vm/hugetlbpage.txt> for details.
885 Ramfs is a file system which keeps all files in RAM. It allows
886 read and write access.
888 It is more of an programming example than a useable file system. If
889 you need a file system which lives in RAM with limit checking use
892 To compile this as a module, choose M here: the module will be called
896 tristate "Userspace-driven configuration filesystem (EXPERIMENTAL)"
897 depends on SYSFS && EXPERIMENTAL
899 configfs is a ram-based filesystem that provides the converse
900 of sysfs's functionality. Where sysfs is a filesystem-based
901 view of kernel objects, configfs is a filesystem-based manager
902 of kernel objects, or config_items.
904 Both sysfs and configfs can and should exist together on the
905 same system. One is not a replacement for the other.
909 menu "Miscellaneous filesystems"
912 tristate "ADFS file system support (EXPERIMENTAL)"
913 depends on EXPERIMENTAL
915 The Acorn Disc Filing System is the standard file system of the
916 RiscOS operating system which runs on Acorn's ARM-based Risc PC
917 systems and the Acorn Archimedes range of machines. If you say Y
918 here, Linux will be able to read from ADFS partitions on hard drives
919 and from ADFS-formatted floppy discs. If you also want to be able to
920 write to those devices, say Y to "ADFS write support" below.
922 The ADFS partition should be the first partition (i.e.,
923 /dev/[hs]d?1) on each of your drives. Please read the file
924 <file:Documentation/filesystems/adfs.txt> for further details.
926 To compile this code as a module, choose M here: the module will be
932 bool "ADFS write support (DANGEROUS)"
935 If you say Y here, you will be able to write to ADFS partitions on
936 hard drives and ADFS-formatted floppy disks. This is experimental
937 codes, so if you're unsure, say N.
940 tristate "Amiga FFS file system support (EXPERIMENTAL)"
941 depends on EXPERIMENTAL
943 The Fast File System (FFS) is the common file system used on hard
944 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
945 if you want to be able to read and write files from and to an Amiga
946 FFS partition on your hard drive. Amiga floppies however cannot be
947 read with this driver due to an incompatibility of the floppy
948 controller used in an Amiga and the standard floppy controller in
949 PCs and workstations. Read <file:Documentation/filesystems/affs.txt>
950 and <file:fs/affs/Changes>.
952 With this driver you can also mount disk files used by Bernd
953 Schmidt's Un*X Amiga Emulator
954 (<http://www.freiburg.linux.de/~uae/>).
955 If you want to do this, you will also need to say Y or M to "Loop
956 device support", above.
958 To compile this file system support as a module, choose M here: the
959 module will be called affs. If unsure, say N.
962 tristate "Apple Macintosh file system support (EXPERIMENTAL)"
963 depends on EXPERIMENTAL
966 If you say Y here, you will be able to mount Macintosh-formatted
967 floppy disks and hard drive partitions with full read-write access.
968 Please read <file:fs/hfs/HFS.txt> to learn about the available mount
971 To compile this file system support as a module, choose M here: the
972 module will be called hfs.
975 tristate "Apple Extended HFS file system support"
979 If you say Y here, you will be able to mount extended format
980 Macintosh-formatted hard drive partitions with full read-write access.
982 This file system is often called HFS+ and was introduced with
983 MacOS 8. It includes all Mac specific filesystem data such as
984 data forks and creator codes, but it also has several UNIX
985 style features such as file ownership and permissions.
988 tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)"
989 depends on EXPERIMENTAL
992 The BeOS File System (BeFS) is the native file system of Be, Inc's
993 BeOS. Notable features include support for arbitrary attributes
994 on files and directories, and database-like indeces on selected
995 attributes. (Also note that this driver doesn't make those features
996 available at this time). It is a 64 bit filesystem, so it supports
997 extremly large volumes and files.
999 If you use this filesystem, you should also say Y to at least one
1000 of the NLS (native language support) options below.
1002 If you don't know what this is about, say N.
1004 To compile this as a module, choose M here: the module will be
1011 If you say Y here, you can use the 'debug' mount option to enable
1012 debugging output from the driver.
1015 tristate "BFS file system support (EXPERIMENTAL)"
1016 depends on EXPERIMENTAL
1018 Boot File System (BFS) is a file system used under SCO UnixWare to
1019 allow the bootloader access to the kernel image and other important
1020 files during the boot process. It is usually mounted under /stand
1021 and corresponds to the slice marked as "STAND" in the UnixWare
1022 partition. You should say Y if you want to read or write the files
1023 on your /stand slice from within Linux. You then also need to say Y
1024 to "UnixWare slices support", below. More information about the BFS
1025 file system is contained in the file
1026 <file:Documentation/filesystems/bfs.txt>.
1028 If you don't know what this is about, say N.
1030 To compile this as a module, choose M here: the module will be called
1031 bfs. Note that the file system of your root partition (the one
1032 containing the directory /) cannot be compiled as a module.
1037 tristate "EFS file system support (read only) (EXPERIMENTAL)"
1038 depends on EXPERIMENTAL
1040 EFS is an older file system used for non-ISO9660 CD-ROMs and hard
1041 disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
1042 uses the XFS file system for hard disk partitions however).
1044 This implementation only offers read-only access. If you don't know
1045 what all this is about, it's safe to say N. For more information
1046 about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
1048 To compile the EFS file system support as a module, choose M here: the
1049 module will be called efs.
1052 tristate "Journalling Flash File System (JFFS) support"
1055 JFFS is the Journaling Flash File System developed by Axis
1056 Communications in Sweden, aimed at providing a crash/powerdown-safe
1057 file system for disk-less embedded devices. Further information is
1058 available at (<http://developer.axis.com/software/jffs/>).
1060 config JFFS_FS_VERBOSE
1061 int "JFFS debugging verbosity (0 = quiet, 3 = noisy)"
1065 Determines the verbosity level of the JFFS debugging messages.
1068 bool "JFFS stats available in /proc filesystem"
1069 depends on JFFS_FS && PROC_FS
1071 Enabling this option will cause statistics from mounted JFFS file systems
1072 to be made available to the user in the /proc/fs/jffs/ directory.
1075 tristate "Journalling Flash File System v2 (JFFS2) support"
1079 JFFS2 is the second generation of the Journalling Flash File System
1080 for use on diskless embedded devices. It provides improved wear
1081 levelling, compression and support for hard links. You cannot use
1082 this on normal block devices, only on 'MTD' devices.
1084 Further information on the design and implementation of JFFS2 is
1085 available at <http://sources.redhat.com/jffs2/>.
1087 config JFFS2_FS_DEBUG
1088 int "JFFS2 debugging verbosity (0 = quiet, 2 = noisy)"
1092 This controls the amount of debugging messages produced by the JFFS2
1093 code. Set it to zero for use in production systems. For evaluation,
1094 testing and debugging, it's advisable to set it to one. This will
1095 enable a few assertions and will print debugging messages at the
1096 KERN_DEBUG loglevel, where they won't normally be visible. Level 2
1097 is unlikely to be useful - it enables extra debugging in certain
1098 areas which at one point needed debugging, but when the bugs were
1099 located and fixed, the detailed messages were relegated to level 2.
1101 If reporting bugs, please try to have available a full dump of the
1102 messages at debug level 1 while the misbehaviour was occurring.
1104 config JFFS2_FS_WRITEBUFFER
1105 bool "JFFS2 write-buffering support"
1109 This enables the write-buffering support in JFFS2.
1111 This functionality is required to support JFFS2 on the following
1112 types of flash devices:
1114 - NOR flash with transparent ECC
1117 config JFFS2_SUMMARY
1118 bool "JFFS2 summary support (EXPERIMENTAL)"
1119 depends on JFFS2_FS && EXPERIMENTAL
1122 This feature makes it possible to use summary information
1123 for faster filesystem mount.
1125 The summary information can be inserted into a filesystem image
1126 by the utility 'sumtool'.
1130 config JFFS2_COMPRESSION_OPTIONS
1131 bool "Advanced compression options for JFFS2"
1135 Enabling this option allows you to explicitly choose which
1136 compression modules, if any, are enabled in JFFS2. Removing
1137 compressors and mean you cannot read existing file systems,
1138 and enabling experimental compressors can mean that you
1139 write a file system which cannot be read by a standard kernel.
1141 If unsure, you should _definitely_ say 'N'.
1144 bool "JFFS2 ZLIB compression support" if JFFS2_COMPRESSION_OPTIONS
1150 Zlib is designed to be a free, general-purpose, legally unencumbered,
1151 lossless data-compression library for use on virtually any computer
1152 hardware and operating system. See <http://www.gzip.org/zlib/> for
1153 further information.
1158 bool "JFFS2 RTIME compression support" if JFFS2_COMPRESSION_OPTIONS
1162 Rtime does manage to recompress already-compressed data. Say 'Y' if unsure.
1165 bool "JFFS2 RUBIN compression support" if JFFS2_COMPRESSION_OPTIONS
1169 RUBINMIPS and DYNRUBIN compressors. Say 'N' if unsure.
1172 prompt "JFFS2 default compression mode" if JFFS2_COMPRESSION_OPTIONS
1173 default JFFS2_CMODE_PRIORITY
1176 You can set here the default compression mode of JFFS2 from
1177 the available compression modes. Don't touch if unsure.
1179 config JFFS2_CMODE_NONE
1180 bool "no compression"
1182 Uses no compression.
1184 config JFFS2_CMODE_PRIORITY
1187 Tries the compressors in a predefinied order and chooses the first
1190 config JFFS2_CMODE_SIZE
1191 bool "size (EXPERIMENTAL)"
1193 Tries all compressors and chooses the one which has the smallest
1199 tristate "Compressed ROM file system support (cramfs)"
1202 Saying Y here includes support for CramFs (Compressed ROM File
1203 System). CramFs is designed to be a simple, small, and compressed
1204 file system for ROM based embedded systems. CramFs is read-only,
1205 limited to 256MB file systems (with 16MB files), and doesn't support
1206 16/32 bits uid/gid, hard links and timestamps.
1208 See <file:Documentation/filesystems/cramfs.txt> and
1209 <file:fs/cramfs/README> for further information.
1211 To compile this as a module, choose M here: the module will be called
1212 cramfs. Note that the root file system (the one containing the
1213 directory /) cannot be compiled as a module.
1218 tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
1220 FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
1221 file system format. VERITAS VxFS(TM) is the standard file system
1222 of SCO UnixWare (and possibly others) and optionally available
1223 for Sunsoft Solaris, HP-UX and many other operating systems.
1224 Currently only readonly access is supported.
1226 NOTE: the file system type as used by mount(1), mount(2) and
1227 fstab(5) is 'vxfs' as it describes the file system format, not
1230 To compile this as a module, choose M here: the module will be
1231 called freevxfs. If unsure, say N.
1235 tristate "OS/2 HPFS file system support"
1237 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
1238 is the file system used for organizing files on OS/2 hard disk
1239 partitions. Say Y if you want to be able to read files from and
1240 write files to an OS/2 HPFS partition on your hard drive. OS/2
1241 floppies however are in regular MSDOS format, so you don't need this
1242 option in order to be able to read them. Read
1243 <file:Documentation/filesystems/hpfs.txt>.
1245 To compile this file system support as a module, choose M here: the
1246 module will be called hpfs. If unsure, say N.
1251 tristate "QNX4 file system support (read only)"
1253 This is the file system used by the real-time operating systems
1254 QNX 4 and QNX 6 (the latter is also called QNX RTP).
1255 Further information is available at <http://www.qnx.com/>.
1256 Say Y if you intend to mount QNX hard disks or floppies.
1257 Unless you say Y to "QNX4FS read-write support" below, you will
1258 only be able to read these file systems.
1260 To compile this file system support as a module, choose M here: the
1261 module will be called qnx4.
1263 If you don't know whether you need it, then you don't need it:
1267 bool "QNX4FS write support (DANGEROUS)"
1268 depends on QNX4FS_FS && EXPERIMENTAL && BROKEN
1270 Say Y if you want to test write support for QNX4 file systems.
1272 It's currently broken, so for now:
1278 tristate "System V/Xenix/V7/Coherent file system support"
1280 SCO, Xenix and Coherent are commercial Unix systems for Intel
1281 machines, and Version 7 was used on the DEC PDP-11. Saying Y
1282 here would allow you to read from their floppies and hard disk
1285 If you have floppies or hard disk partitions like that, it is likely
1286 that they contain binaries from those other Unix systems; in order
1287 to run these binaries, you will want to install linux-abi which is a
1288 a set of kernel modules that lets you run SCO, Xenix, Wyse,
1289 UnixWare, Dell Unix and System V programs under Linux. It is
1290 available via FTP (user: ftp) from
1291 <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
1292 NOTE: that will work only for binaries from Intel-based systems;
1293 PDP ones will have to wait until somebody ports Linux to -11 ;-)
1295 If you only intend to mount files from some other Unix over the
1296 network using NFS, you don't need the System V file system support
1297 (but you need NFS file system support obviously).
1299 Note that this option is generally not needed for floppies, since a
1300 good portable way to transport files and directories between unixes
1301 (and even other operating systems) is given by the tar program ("man
1302 tar" or preferably "info tar"). Note also that this option has
1303 nothing whatsoever to do with the option "System V IPC". Read about
1304 the System V file system in
1305 <file:Documentation/filesystems/sysv-fs.txt>.
1306 Saying Y here will enlarge your kernel by about 27 KB.
1308 To compile this as a module, choose M here: the module will be called
1311 If you haven't heard about all of this before, it's safe to say N.
1316 tristate "UFS file system support (read only)"
1318 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
1319 OpenBSD and NeXTstep) use a file system called UFS. Some System V
1320 Unixes can create and mount hard disk partitions and diskettes using
1321 this file system as well. Saying Y here will allow you to read from
1322 these partitions; if you also want to write to them, say Y to the
1323 experimental "UFS file system write support", below. Please read the
1324 file <file:Documentation/filesystems/ufs.txt> for more information.
1326 The recently released UFS2 variant (used in FreeBSD 5.x) is
1327 READ-ONLY supported.
1329 If you only intend to mount files from some other Unix over the
1330 network using NFS, you don't need the UFS file system support (but
1331 you need NFS file system support obviously).
1333 Note that this option is generally not needed for floppies, since a
1334 good portable way to transport files and directories between unixes
1335 (and even other operating systems) is given by the tar program ("man
1336 tar" or preferably "info tar").
1338 When accessing NeXTstep files, you may need to convert them from the
1339 NeXT character set to the Latin1 character set; use the program
1340 recode ("info recode") for this purpose.
1342 To compile the UFS file system support as a module, choose M here: the
1343 module will be called ufs.
1345 If you haven't heard about all of this before, it's safe to say N.
1348 bool "UFS file system write support (DANGEROUS)"
1349 depends on UFS_FS && EXPERIMENTAL && BROKEN
1351 Say Y here if you want to try writing to UFS partitions. This is
1352 experimental, so you should back up your UFS partitions beforehand.
1356 menu "Network File Systems"
1360 tristate "NFS file system support"
1364 select NFS_ACL_SUPPORT if NFS_V3_ACL
1366 If you are connected to some other (usually local) Unix computer
1367 (using SLIP, PLIP, PPP or Ethernet) and want to mount files residing
1368 on that computer (the NFS server) using the Network File Sharing
1369 protocol, say Y. "Mounting files" means that the client can access
1370 the files with usual UNIX commands as if they were sitting on the
1371 client's hard disk. For this to work, the server must run the
1372 programs nfsd and mountd (but does not need to have NFS file system
1373 support enabled in its kernel). NFS is explained in the Network
1374 Administrator's Guide, available from
1375 <http://www.tldp.org/docs.html#guide>, on its man page: "man
1376 nfs", and in the NFS-HOWTO.
1378 A superior but less widely used alternative to NFS is provided by
1379 the Coda file system; see "Coda file system support" below.
1381 If you say Y here, you should have said Y to TCP/IP networking also.
1382 This option would enlarge your kernel by about 27 KB.
1384 To compile this file system support as a module, choose M here: the
1385 module will be called nfs.
1387 If you are configuring a diskless machine which will mount its root
1388 file system over NFS at boot time, say Y here and to "Kernel
1389 level IP autoconfiguration" above and to "Root file system on NFS"
1390 below. You cannot compile this driver as a module in this case.
1391 There are two packages designed for booting diskless machines over
1392 the net: netboot, available from
1393 <http://ftp1.sourceforge.net/netboot/>, and Etherboot,
1394 available from <http://ftp1.sourceforge.net/etherboot/>.
1396 If you don't know what all this is about, say N.
1399 bool "Provide NFSv3 client support"
1402 Say Y here if you want your NFS client to be able to speak version
1403 3 of the NFS protocol.
1408 bool "Provide client support for the NFSv3 ACL protocol extension"
1411 Implement the NFSv3 ACL protocol extension for manipulating POSIX
1412 Access Control Lists. The server should also be compiled with
1413 the NFSv3 ACL protocol extension; see the CONFIG_NFSD_V3_ACL option.
1418 bool "Provide NFSv4 client support (EXPERIMENTAL)"
1419 depends on NFS_FS && EXPERIMENTAL
1420 select RPCSEC_GSS_KRB5
1422 Say Y here if you want your NFS client to be able to speak the newer
1423 version 4 of the NFS protocol.
1425 Note: Requires auxiliary userspace daemons which may be found on
1426 http://www.citi.umich.edu/projects/nfsv4/
1431 bool "Allow direct I/O on NFS files (EXPERIMENTAL)"
1432 depends on NFS_FS && EXPERIMENTAL
1434 This option enables applications to perform uncached I/O on files
1435 in NFS file systems using the O_DIRECT open() flag. When O_DIRECT
1436 is set for a file, its data is not cached in the system's page
1437 cache. Data is moved to and from user-level application buffers
1438 directly. Unlike local disk-based file systems, NFS O_DIRECT has
1439 no alignment restrictions.
1441 Unless your program is designed to use O_DIRECT properly, you are
1442 much better off allowing the NFS client to manage data caching for
1443 you. Misusing O_DIRECT can cause poor server performance or network
1444 storms. This kernel build option defaults OFF to avoid exposing
1445 system administrators unwittingly to a potentially hazardous
1448 For more details on NFS O_DIRECT, see fs/nfs/direct.c.
1450 If unsure, say N. This reduces the size of the NFS client, and
1451 causes open() to return EINVAL if a file residing in NFS is
1452 opened with the O_DIRECT flag.
1455 tristate "NFS server support"
1460 select NFS_ACL_SUPPORT if NFSD_V3_ACL || NFSD_V2_ACL
1462 If you want your Linux box to act as an NFS *server*, so that other
1463 computers on your local network which support NFS can access certain
1464 directories on your box transparently, you have two options: you can
1465 use the self-contained user space program nfsd, in which case you
1466 should say N here, or you can say Y and use the kernel based NFS
1467 server. The advantage of the kernel based solution is that it is
1470 In either case, you will need support software; the respective
1471 locations are given in the file <file:Documentation/Changes> in the
1474 If you say Y here, you will get support for version 2 of the NFS
1475 protocol (NFSv2). If you also want NFSv3, say Y to the next question
1478 Please read the NFS-HOWTO, available from
1479 <http://www.tldp.org/docs.html#howto>.
1481 To compile the NFS server support as a module, choose M here: the
1482 module will be called nfsd. If unsure, say N.
1489 bool "Provide NFSv3 server support"
1492 If you would like to include the NFSv3 server as well as the NFSv2
1493 server, say Y here. If unsure, say Y.
1496 bool "Provide server support for the NFSv3 ACL protocol extension"
1500 Implement the NFSv3 ACL protocol extension for manipulating POSIX
1501 Access Control Lists on exported file systems. NFS clients should
1502 be compiled with the NFSv3 ACL protocol extension; see the
1503 CONFIG_NFS_V3_ACL option. If unsure, say N.
1506 bool "Provide NFSv4 server support (EXPERIMENTAL)"
1507 depends on NFSD_V3 && EXPERIMENTAL
1513 If you would like to include the NFSv4 server as well as the NFSv2
1514 and NFSv3 servers, say Y here. This feature is experimental, and
1515 should only be used if you are interested in helping to test NFSv4.
1519 bool "Provide NFS server over TCP support"
1523 If you want your NFS server to support TCP connections, say Y here.
1524 TCP connections usually perform better than the default UDP when
1525 the network is lossy or congested. If unsure, say Y.
1528 bool "Root file system on NFS"
1529 depends on NFS_FS=y && IP_PNP
1531 If you want your Linux box to mount its whole root file system (the
1532 one containing the directory /) from some other computer over the
1533 net via NFS (presumably because your box doesn't have a hard disk),
1534 say Y. Read <file:Documentation/nfsroot.txt> for details. It is
1535 likely that in this case, you also want to say Y to "Kernel level IP
1536 autoconfiguration" so that your box can discover its network address
1539 Most people say N here.
1546 depends on NFSD_V3 || NFS_V3
1552 config NFS_ACL_SUPPORT
1558 depends on NFSD || NFS_FS
1567 config RPCSEC_GSS_KRB5
1568 tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
1569 depends on SUNRPC && EXPERIMENTAL
1575 Provides for secure RPC calls by means of a gss-api
1576 mechanism based on Kerberos V5. This is required for
1579 Note: Requires an auxiliary userspace daemon which may be found on
1580 http://www.citi.umich.edu/projects/nfsv4/
1584 config RPCSEC_GSS_SPKM3
1585 tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
1586 depends on SUNRPC && EXPERIMENTAL
1593 Provides for secure RPC calls by means of a gss-api
1594 mechanism based on the SPKM3 public-key mechanism.
1596 Note: Requires an auxiliary userspace daemon which may be found on
1597 http://www.citi.umich.edu/projects/nfsv4/
1602 tristate "SMB file system support (to mount Windows shares etc.)"
1606 SMB (Server Message Block) is the protocol Windows for Workgroups
1607 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
1608 files and printers over local networks. Saying Y here allows you to
1609 mount their file systems (often called "shares" in this context) and
1610 access them just like any other Unix directory. Currently, this
1611 works only if the Windows machines use TCP/IP as the underlying
1612 transport protocol, and not NetBEUI. For details, read
1613 <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
1614 available from <http://www.tldp.org/docs.html#howto>.
1616 Note: if you just want your box to act as an SMB *server* and make
1617 files and printing services available to Windows clients (which need
1618 to have a TCP/IP stack), you don't need to say Y here; you can use
1619 the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
1622 General information about how to connect Linux, Windows machines and
1623 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1625 To compile the SMB support as a module, choose M here: the module will
1626 be called smbfs. Most people say N, however.
1628 config SMB_NLS_DEFAULT
1629 bool "Use a default NLS"
1632 Enabling this will make smbfs use nls translations by default. You
1633 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
1634 settings and you need to give the default nls for the SMB server as
1635 CONFIG_SMB_NLS_REMOTE.
1637 The nls settings can be changed at mount time, if your smbmount
1638 supports that, using the codepage and iocharset parameters.
1640 smbmount from samba 2.2.0 or later supports this.
1642 config SMB_NLS_REMOTE
1643 string "Default Remote NLS Option"
1644 depends on SMB_NLS_DEFAULT
1647 This setting allows you to specify a default value for which
1648 codepage the server uses. If this field is left blank no
1649 translations will be done by default. The local codepage/charset
1650 default to CONFIG_NLS_DEFAULT.
1652 The nls settings can be changed at mount time, if your smbmount
1653 supports that, using the codepage and iocharset parameters.
1655 smbmount from samba 2.2.0 or later supports this.
1658 tristate "CIFS support (advanced network filesystem for Samba, Window and other CIFS compliant servers)"
1662 This is the client VFS module for the Common Internet File System
1663 (CIFS) protocol which is the successor to the Server Message Block
1664 (SMB) protocol, the native file sharing mechanism for most early
1665 PC operating systems. The CIFS protocol is fully supported by
1666 file servers such as Windows 2000 (including Windows 2003, NT 4
1667 and Windows XP) as well by Samba (which provides excellent CIFS
1668 server support for Linux and many other operating systems). Limited
1669 support for Windows ME and similar servers is provided as well.
1670 You must use the smbfs client filesystem to access older SMB servers
1671 such as OS/2 and DOS.
1673 The intent of the cifs module is to provide an advanced
1674 network file system client for mounting to CIFS compliant servers,
1675 including support for dfs (hierarchical name space), secure per-user
1676 session establishment, safe distributed caching (oplock), optional
1677 packet signing, Unicode and other internationalization improvements,
1678 and optional Winbind (nsswitch) integration. You do not need to enable
1679 cifs if running only a (Samba) server. It is possible to enable both
1680 smbfs and cifs (e.g. if you are using CIFS for accessing Windows 2003
1681 and Samba 3 servers, and smbfs for accessing old servers). If you need
1682 to mount to Samba or Windows from this machine, say Y.
1685 bool "CIFS statistics"
1688 Enabling this option will cause statistics for each server share
1689 mounted by the cifs client to be displayed in /proc/fs/cifs/Stats
1692 bool "CIFS extended statistics"
1693 depends on CIFS_STATS
1695 Enabling this option will allow more detailed statistics on SMB
1696 request timing to be displayed in /proc/fs/cifs/DebugData and also
1697 allow optional logging of slow responses to dmesg (depending on the
1698 value of /proc/fs/cifs/cifsFYI, see fs/cifs/README for more details).
1699 These additional statistics may have a minor effect on performance
1700 and memory utilization.
1702 Unless you are a developer or are doing network performance analysis
1706 bool "CIFS extended attributes"
1709 Extended attributes are name:value pairs associated with inodes by
1710 the kernel or by users (see the attr(5) manual page, or visit
1711 <http://acl.bestbits.at/> for details). CIFS maps the name of
1712 extended attributes beginning with the user namespace prefix
1713 to SMB/CIFS EAs. EAs are stored on Windows servers without the
1714 user namespace prefix, but their names are seen by Linux cifs clients
1715 prefaced by the user namespace prefix. The system namespace
1716 (used by some filesystems to store ACLs) is not supported at
1722 bool "CIFS POSIX Extensions"
1723 depends on CIFS_XATTR
1725 Enabling this option will cause the cifs client to attempt to
1726 negotiate a newer dialect with servers, such as Samba 3.0.5
1727 or later, that optionally can handle more POSIX like (rather
1728 than Windows like) file behavior. It also enables
1729 support for POSIX ACLs (getfacl and setfacl) to servers
1730 (such as Samba 3.10 and later) which can negotiate
1731 CIFS POSIX ACL support. If unsure, say N.
1733 config CIFS_EXPERIMENTAL
1734 bool "CIFS Experimental Features (EXPERIMENTAL)"
1735 depends on CIFS && EXPERIMENTAL
1737 Enables cifs features under testing. These features are
1738 experimental and currently include support for writepages
1739 (multipage writebehind performance improvements) and directory
1740 change notification ie fcntl(F_DNOTIFY) as well as some security
1741 improvements. Some also depend on setting at runtime the
1742 pseudo-file /proc/fs/cifs/Experimental (which is disabled by
1743 default). See the file fs/cifs/README for more details.
1748 bool "CIFS Kerberos/SPNEGO advanced session setup (EXPERIMENTAL)"
1749 depends on CIFS_EXPERIMENTAL
1752 Enables an upcall mechanism for CIFS which will be used to contact
1753 userspace helper utilities to provide SPNEGO packaged Kerberos
1754 tickets which are needed to mount to certain secure servers
1755 (for which more secure Kerberos authentication is required). If
1759 tristate "NCP file system support (to mount NetWare volumes)"
1760 depends on IPX!=n || INET
1762 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
1763 used by Novell NetWare clients to talk to file servers. It is to
1764 IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
1765 to mount NetWare file server volumes and to access them just like
1766 any other Unix directory. For details, please read the file
1767 <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
1768 the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
1770 You do not have to say Y here if you want your Linux box to act as a
1771 file *server* for Novell NetWare clients.
1773 General information about how to connect Linux, Windows machines and
1774 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1776 To compile this as a module, choose M here: the module will be called
1777 ncpfs. Say N unless you are connected to a Novell network.
1779 source "fs/ncpfs/Kconfig"
1782 tristate "Coda file system support (advanced network fs)"
1785 Coda is an advanced network file system, similar to NFS in that it
1786 enables you to mount file systems of a remote server and access them
1787 with regular Unix commands as if they were sitting on your hard
1788 disk. Coda has several advantages over NFS: support for
1789 disconnected operation (e.g. for laptops), read/write server
1790 replication, security model for authentication and encryption,
1791 persistent client caches and write back caching.
1793 If you say Y here, your Linux box will be able to act as a Coda
1794 *client*. You will need user level code as well, both for the
1795 client and server. Servers are currently user level, i.e. they need
1796 no kernel support. Please read
1797 <file:Documentation/filesystems/coda.txt> and check out the Coda
1798 home page <http://www.coda.cs.cmu.edu/>.
1800 To compile the coda client support as a module, choose M here: the
1801 module will be called coda.
1803 config CODA_FS_OLD_API
1804 bool "Use 96-bit Coda file identifiers"
1807 A new kernel-userspace API had to be introduced for Coda v6.0
1808 to support larger 128-bit file identifiers as needed by the
1809 new realms implementation.
1811 However this new API is not backward compatible with older
1812 clients. If you really need to run the old Coda userspace
1813 cache manager then say Y.
1815 For most cases you probably want to say N.
1818 # for fs/nls/Config.in
1819 tristate "Andrew File System support (AFS) (Experimental)"
1820 depends on INET && EXPERIMENTAL
1823 If you say Y here, you will get an experimental Andrew File System
1824 driver. It currently only supports unsecured read-only AFS access.
1826 See <file:Documentation/filesystems/afs.txt> for more intormation.
1834 tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
1835 depends on INET && EXPERIMENTAL
1837 If you say Y here, you will get experimental support for
1838 Plan 9 resource sharing via the 9P2000 protocol.
1840 See <http://v9fs.sf.net> for more information.
1850 menu "Partition Types"
1852 source "fs/partitions/Kconfig"
1856 source "fs/nls/Kconfig"