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"
74 This is the journaling version of the Second extended file system
75 (often called ext3), the de facto standard Linux file system
76 (method to organize files on a storage device) for hard disks.
78 The journaling code included in this driver means you do not have
79 to run e2fsck (file system checker) on your file systems after a
80 crash. The journal keeps track of any changes that were being made
81 at the time the system crashed, and can ensure that your file system
82 is consistent without the need for a lengthy check.
84 Other than adding the journal to the file system, the on-disk format
85 of ext3 is identical to ext2. It is possible to freely switch
86 between using the ext3 driver and the ext2 driver, as long as the
87 file system has been cleanly unmounted, or e2fsck is run on the file
90 To add a journal on an existing ext2 file system or change the
91 behavior of ext3 file systems, you can use the tune2fs utility ("man
92 tune2fs"). To modify attributes of files and directories on ext3
93 file systems, use chattr ("man chattr"). You need to be using
94 e2fsprogs version 1.20 or later in order to create ext3 journals
95 (available at <http://sourceforge.net/projects/e2fsprogs/>).
97 To compile this file system support as a module, choose M here: the
98 module will be called ext3. Be aware however that the file system
99 of your root partition (the one containing the directory /) cannot
100 be compiled as a module, and so this may be dangerous.
103 bool "Ext3 extended attributes"
107 Extended attributes are name:value pairs associated with inodes by
108 the kernel or by users (see the attr(5) manual page, or visit
109 <http://acl.bestbits.at/> for details).
113 You need this for POSIX ACL support on ext3.
115 config EXT3_FS_POSIX_ACL
116 bool "Ext3 POSIX Access Control Lists"
117 depends on EXT3_FS_XATTR
120 Posix Access Control Lists (ACLs) support permissions for users and
121 groups beyond the owner/group/world scheme.
123 To learn more about Access Control Lists, visit the Posix ACLs for
124 Linux website <http://acl.bestbits.at/>.
126 If you don't know what Access Control Lists are, say N
128 config EXT3_FS_SECURITY
129 bool "Ext3 Security Labels"
130 depends on EXT3_FS_XATTR
132 Security labels support alternative access control models
133 implemented by security modules like SELinux. This option
134 enables an extended attribute handler for file security
135 labels in the ext3 filesystem.
137 If you are not using a security module that requires using
138 extended attributes for file security labels, say N.
141 # CONFIG_JBD could be its own option (even modular), but until there are
142 # other users than ext3, we will simply make it be the same as CONFIG_EXT3_FS
143 # dep_tristate ' Journal Block Device support (JBD for ext3)' CONFIG_JBD $CONFIG_EXT3_FS
147 This is a generic journaling layer for block devices. It is
148 currently used by the ext3 file system, but it could also be used to
149 add journal support to other file systems or block devices such as
152 If you are using the ext3 file system, you need to say Y here. If
153 you are not using ext3 then you will probably want to say N.
155 To compile this device as a module, choose M here: the module will be
156 called jbd. If you are compiling ext3 into the kernel, you cannot
157 compile this code as a module.
160 bool "JBD (ext3) debugging support"
163 If you are using the ext3 journaled file system (or potentially any
164 other file system/device using JBD), this option allows you to
165 enable debugging output while the system is running, in order to
166 help track down any problems you are having. By default the
167 debugging output will be turned off.
169 If you select Y here, then you will be able to turn on debugging
170 with "echo N > /proc/sys/fs/jbd-debug", where N is a number between
171 1 and 5, the higher the number, the more debugging output is
172 generated. To turn debugging off again, do
173 "echo 0 > /proc/sys/fs/jbd-debug".
176 # Meta block cache for Extended Attributes (ext2/ext3)
178 depends on EXT2_FS_XATTR || EXT3_FS_XATTR
179 default y if EXT2_FS=y || EXT3_FS=y
180 default m if EXT2_FS=m || EXT3_FS=m
183 tristate "Reiserfs support"
185 Stores not just filenames but the files themselves in a balanced
186 tree. Uses journaling.
188 Balanced trees are more efficient than traditional file system
189 architectural foundations.
191 In general, ReiserFS is as fast as ext2, but is very efficient with
192 large directories and small files. Additional patches are needed
193 for NFS and quotas, please see <http://www.namesys.com/> for links.
195 It is more easily extended to have features currently found in
196 database and keyword search systems than block allocation based file
197 systems are. The next version will be so extended, and will support
198 plugins consistent with our motto ``It takes more than a license to
199 make source code open.''
201 Read <http://www.namesys.com/> to learn more about reiserfs.
203 Sponsored by Threshold Networks, Emusic.com, and Bigstorage.com.
205 If you like it, you can pay us to add new features to it that you
206 need, buy a support contract, or pay us to port it to another OS.
208 config REISERFS_CHECK
209 bool "Enable reiserfs debug mode"
210 depends on REISERFS_FS
212 If you set this to Y, then ReiserFS will perform every check it can
213 possibly imagine of its internal consistency throughout its
214 operation. It will also go substantially slower. More than once we
215 have forgotten that this was on, and then gone despondent over the
216 latest benchmarks.:-) Use of this option allows our team to go all
217 out in checking for consistency when debugging without fear of its
218 effect on end users. If you are on the verge of sending in a bug
219 report, say Y and you might get a useful error message. Almost
220 everyone should say N.
222 config REISERFS_PROC_INFO
223 bool "Stats in /proc/fs/reiserfs"
224 depends on REISERFS_FS
226 Create under /proc/fs/reiserfs a hierarchy of files, displaying
227 various ReiserFS statistics and internal data at the expense of
228 making your kernel or module slightly larger (+8 KB). This also
229 increases the amount of kernel memory required for each mount.
230 Almost everyone but ReiserFS developers and people fine-tuning
231 reiserfs or tracing problems should say N.
233 config REISERFS_FS_XATTR
234 bool "ReiserFS extended attributes"
235 depends on REISERFS_FS
237 Extended attributes are name:value pairs associated with inodes by
238 the kernel or by users (see the attr(5) manual page, or visit
239 <http://acl.bestbits.at/> for details).
243 config REISERFS_FS_POSIX_ACL
244 bool "ReiserFS POSIX Access Control Lists"
245 depends on REISERFS_FS_XATTR
248 Posix Access Control Lists (ACLs) support permissions for users and
249 groups beyond the owner/group/world scheme.
251 To learn more about Access Control Lists, visit the Posix ACLs for
252 Linux website <http://acl.bestbits.at/>.
254 If you don't know what Access Control Lists are, say N
256 config REISERFS_FS_SECURITY
257 bool "ReiserFS Security Labels"
258 depends on REISERFS_FS_XATTR
260 Security labels support alternative access control models
261 implemented by security modules like SELinux. This option
262 enables an extended attribute handler for file security
263 labels in the ReiserFS filesystem.
265 If you are not using a security module that requires using
266 extended attributes for file security labels, say N.
269 tristate "JFS filesystem support"
272 This is a port of IBM's Journaled Filesystem . More information is
273 available in the file <file:Documentation/filesystems/jfs.txt>.
275 If you do not intend to use the JFS filesystem, say N.
278 bool "JFS POSIX Access Control Lists"
282 Posix Access Control Lists (ACLs) support permissions for users and
283 groups beyond the owner/group/world scheme.
285 To learn more about Access Control Lists, visit the Posix ACLs for
286 Linux website <http://acl.bestbits.at/>.
288 If you don't know what Access Control Lists are, say N
291 bool "JFS Security Labels"
294 Security labels support alternative access control models
295 implemented by security modules like SELinux. This option
296 enables an extended attribute handler for file security
297 labels in the jfs filesystem.
299 If you are not using a security module that requires using
300 extended attributes for file security labels, say N.
306 If you are experiencing any problems with the JFS filesystem, say
307 Y here. This will result in additional debugging messages to be
308 written to the system log. Under normal circumstances, this
309 results in very little overhead.
311 config JFS_STATISTICS
312 bool "JFS statistics"
315 Enabling this option will cause statistics from the JFS file system
316 to be made available to the user in the /proc/fs/jfs/ directory.
319 # Posix ACL utility routines (for now, only ext2/ext3/jfs/reiserfs)
321 # NOTE: you can implement Posix ACLs without these helpers (XFS does).
322 # Never use this symbol for ifdefs.
327 source "fs/xfs/Kconfig"
330 tristate "Minix fs support"
332 Minix is a simple operating system used in many classes about OS's.
333 The minix file system (method to organize files on a hard disk
334 partition or a floppy disk) was the original file system for Linux,
335 but has been superseded by the second extended file system ext2fs.
336 You don't want to use the minix file system on your hard disk
337 because of certain built-in restrictions, but it is sometimes found
338 on older Linux floppy disks. This option will enlarge your kernel
339 by about 28 KB. If unsure, say N.
341 To compile this file system support as a module, choose M here: the
342 module will be called minix. Note that the file system of your root
343 partition (the one containing the directory /) cannot be compiled as
347 tristate "ROM file system support"
349 This is a very small read-only file system mainly intended for
350 initial ram disks of installation disks, but it could be used for
351 other read-only media as well. Read
352 <file:Documentation/filesystems/romfs.txt> for details.
354 To compile this file system support as a module, choose M here: the
355 module will be called romfs. Note that the file system of your
356 root partition (the one containing the directory /) cannot be a
359 If you don't know whether you need it, then you don't need it:
363 bool "Inotify file change notification support"
366 Say Y here to enable inotify support and the associated system
367 calls. Inotify is a file change notification system and a
368 replacement for dnotify. Inotify fixes numerous shortcomings in
369 dnotify and introduces several new features. It allows monitoring
370 of both files and directories via a single open fd. Other features
371 include multiple file events, one-shot support, and unmount
374 For more information, see Documentation/filesystems/inotify.txt
381 If you say Y here, you will be able to set per user limits for disk
382 usage (also called disk quotas). Currently, it works for the
383 ext2, ext3, and reiserfs file system. ext3 also supports journalled
384 quotas for which you don't need to run quotacheck(8) after an unclean
385 shutdown. You need additional software in order to use quota support
386 (you can download sources from
387 <http://www.sf.net/projects/linuxquota/>). For further details, read
388 the Quota mini-HOWTO, available from
389 <http://www.tldp.org/docs.html#howto>, or the documentation provided
390 with the quota tools. Probably the quota support is only useful for
391 multi user systems. If unsure, say N.
394 tristate "Old quota format support"
397 This quota format was (is) used by kernels earlier than 2.4.22. If
398 you have quota working and you don't want to convert to new quota
402 tristate "Quota format v2 support"
405 This quota format allows using quotas with 32-bit UIDs/GIDs. If you
406 need this functionality say Y here. Note that you will need recent
407 quota utilities (>= 3.01) for new quota format with this kernel.
411 depends on XFS_QUOTA || QUOTA
415 bool "Dnotify support" if EMBEDDED
418 Dnotify is a directory-based per-fd file change notification system
419 that uses signals to communicate events to user-space. There exist
420 superior alternatives, but some applications may still rely on
423 Because of this, if unsure, say Y.
426 tristate "Kernel automounter support"
428 The automounter is a tool to automatically mount remote file systems
429 on demand. This implementation is partially kernel-based to reduce
430 overhead in the already-mounted case; this is unlike the BSD
431 automounter (amd), which is a pure user space daemon.
433 To use the automounter you need the user-space tools from the autofs
434 package; you can find the location in <file:Documentation/Changes>.
435 You also want to answer Y to "NFS file system support", below.
437 If you want to use the newer version of the automounter with more
438 features, say N here and say Y to "Kernel automounter v4 support",
441 To compile this support as a module, choose M here: the module will be
444 If you are not a part of a fairly large, distributed network, you
445 probably do not need an automounter, and can say N here.
448 tristate "Kernel automounter version 4 support (also supports v3)"
450 The automounter is a tool to automatically mount remote file systems
451 on demand. This implementation is partially kernel-based to reduce
452 overhead in the already-mounted case; this is unlike the BSD
453 automounter (amd), which is a pure user space daemon.
455 To use the automounter you need the user-space tools from
456 <ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4/>; you also
457 want to answer Y to "NFS file system support", below.
459 To compile this support as a module, choose M here: the module will be
460 called autofs4. You will need to add "alias autofs autofs4" to your
461 modules configuration file.
463 If you are not a part of a fairly large, distributed network or
464 don't have a laptop which needs to dynamically reconfigure to the
465 local network, you probably do not need an automounter, and can say
468 menu "CD-ROM/DVD Filesystems"
471 tristate "ISO 9660 CDROM file system support"
473 This is the standard file system used on CD-ROMs. It was previously
474 known as "High Sierra File System" and is called "hsfs" on other
475 Unix systems. The so-called Rock-Ridge extensions which allow for
476 long Unix filenames and symbolic links are also supported by this
477 driver. If you have a CD-ROM drive and want to do more with it than
478 just listen to audio CDs and watch its LEDs, say Y (and read
479 <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO,
480 available from <http://www.tldp.org/docs.html#howto>), thereby
481 enlarging your kernel by about 27 KB; otherwise say N.
483 To compile this file system support as a module, choose M here: the
484 module will be called isofs.
487 bool "Microsoft Joliet CDROM extensions"
488 depends on ISO9660_FS
491 Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system
492 which allows for long filenames in unicode format (unicode is the
493 new 16 bit character code, successor to ASCII, which encodes the
494 characters of almost all languages of the world; see
495 <http://www.unicode.org/> for more information). Say Y here if you
496 want to be able to read Joliet CD-ROMs under Linux.
499 bool "Transparent decompression extension"
500 depends on ISO9660_FS
503 This is a Linux-specific extension to RockRidge which lets you store
504 data in compressed form on a CD-ROM and have it transparently
505 decompressed when the CD-ROM is accessed. See
506 <http://www.kernel.org/pub/linux/utils/fs/zisofs/> for the tools
507 necessary to create such a filesystem. Say Y here if you want to be
508 able to read such compressed CD-ROMs.
511 # for fs/nls/Config.in
517 tristate "UDF file system support"
519 This is the new file system used on some CD-ROMs and DVDs. Say Y if
520 you intend to mount DVD discs or CDRW's written in packet mode, or
521 if written to by other UDF utilities, such as DirectCD.
522 Please read <file:Documentation/filesystems/udf.txt>.
524 To compile this file system support as a module, choose M here: the
525 module will be called udf.
532 depends on (UDF_FS=m && NLS) || (UDF_FS=y && NLS=y)
536 menu "DOS/FAT/NT Filesystems"
542 If you want to use one of the FAT-based file systems (the MS-DOS and
543 VFAT (Windows 95) file systems), then you must say Y or M here
544 to include FAT support. You will then be able to mount partitions or
545 diskettes with FAT-based file systems and transparently access the
546 files on them, i.e. MSDOS files will look and behave just like all
549 This FAT support is not a file system in itself, it only provides
550 the foundation for the other file systems. You will have to say Y or
551 M to at least one of "MSDOS fs support" or "VFAT fs support" in
552 order to make use of it.
554 Another way to read and write MSDOS floppies and hard drive
555 partitions from within Linux (but not transparently) is with the
556 mtools ("man mtools") program suite. You don't need to say Y here in
559 If you need to move large files on floppies between a DOS and a
560 Linux box, say Y here, mount the floppy under Linux with an MSDOS
561 file system and use GNU tar's M option. GNU tar is a program
562 available for Unix and DOS ("man tar" or "info tar").
564 It is now also becoming possible to read and write compressed FAT
565 file systems; read <file:Documentation/filesystems/fat_cvf.txt> for
568 The FAT support will enlarge your kernel by about 37 KB. If unsure,
571 To compile this as a module, choose M here: the module will be called
572 fat. Note that if you compile the FAT support as a module, you
573 cannot compile any of the FAT-based file systems into the kernel
574 -- they will have to be modules as well.
577 tristate "MSDOS fs support"
580 This allows you to mount MSDOS partitions of your hard drive (unless
581 they are compressed; to access compressed MSDOS partitions under
582 Linux, you can either use the DOS emulator DOSEMU, described in the
583 DOSEMU-HOWTO, available from
584 <http://www.tldp.org/docs.html#howto>, or try dmsdosfs in
585 <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you
586 intend to use dosemu with a non-compressed MSDOS partition, say Y
587 here) and MSDOS floppies. This means that file access becomes
588 transparent, i.e. the MSDOS files look and behave just like all
591 If you have Windows 95 or Windows NT installed on your MSDOS
592 partitions, you should use the VFAT file system (say Y to "VFAT fs
593 support" below), or you will not be able to see the long filenames
594 generated by Windows 95 / Windows NT.
596 This option will enlarge your kernel by about 7 KB. If unsure,
597 answer Y. This will only work if you said Y to "DOS FAT fs support"
598 as well. To compile this as a module, choose M here: the module will
602 tristate "VFAT (Windows-95) fs support"
605 This option provides support for normal Windows file systems with
606 long filenames. That includes non-compressed FAT-based file systems
607 used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
608 programs from the mtools package.
610 The VFAT support enlarges your kernel by about 10 KB and it only
611 works if you said Y to the "DOS FAT fs support" above. Please read
612 the file <file:Documentation/filesystems/vfat.txt> for details. If
615 To compile this as a module, choose M here: the module will be called
618 config FAT_DEFAULT_CODEPAGE
619 int "Default codepage for FAT"
620 depends on MSDOS_FS || VFAT_FS
623 This option should be set to the codepage of your FAT filesystems.
624 It can be overridden with the "codepage" mount option.
625 See <file:Documentation/filesystems/vfat.txt> for more information.
627 config FAT_DEFAULT_IOCHARSET
628 string "Default iocharset for FAT"
632 Set this to the default input/output character set you'd
633 like FAT to use. It should probably match the character set
634 that most of your FAT filesystems use, and can be overridden
635 with the "iocharset" mount option for FAT filesystems.
636 Note that "utf8" is not recommended for FAT filesystems.
637 If unsure, you shouldn't set "utf8" here.
638 See <file:Documentation/filesystems/vfat.txt> for more information.
641 tristate "NTFS file system support"
644 NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003.
646 Saying Y or M here enables read support. There is partial, but
647 safe, write support available. For write support you must also
648 say Y to "NTFS write support" below.
650 There are also a number of user-space tools available, called
651 ntfsprogs. These include ntfsundelete and ntfsresize, that work
652 without NTFS support enabled in the kernel.
654 This is a rewrite from scratch of Linux NTFS support and replaced
655 the old NTFS code starting with Linux 2.5.11. A backport to
656 the Linux 2.4 kernel series is separately available as a patch
657 from the project web site.
659 For more information see <file:Documentation/filesystems/ntfs.txt>
660 and <http://linux-ntfs.sourceforge.net/>.
662 To compile this file system support as a module, choose M here: the
663 module will be called ntfs.
665 If you are not using Windows NT, 2000, XP or 2003 in addition to
666 Linux on your computer it is safe to say N.
669 bool "NTFS debugging support"
672 If you are experiencing any problems with the NTFS file system, say
673 Y here. This will result in additional consistency checks to be
674 performed by the driver as well as additional debugging messages to
675 be written to the system log. Note that debugging messages are
676 disabled by default. To enable them, supply the option debug_msgs=1
677 at the kernel command line when booting the kernel or as an option
678 to insmod when loading the ntfs module. Once the driver is active,
679 you can enable debugging messages by doing (as root):
680 echo 1 > /proc/sys/fs/ntfs-debug
681 Replacing the "1" with "0" would disable debug messages.
683 If you leave debugging messages disabled, this results in little
684 overhead, but enabling debug messages results in very significant
685 slowdown of the system.
687 When reporting bugs, please try to have available a full dump of
688 debugging messages while the misbehaviour was occurring.
691 bool "NTFS write support"
694 This enables the partial, but safe, write support in the NTFS driver.
696 The only supported operation is overwriting existing files, without
697 changing the file length. No file or directory creation, deletion or
698 renaming is possible. Note only non-resident files can be written to
699 so you may find that some very small files (<500 bytes or so) cannot
702 While we cannot guarantee that it will not damage any data, we have
703 so far not received a single report where the driver would have
704 damaged someones data so we assume it is perfectly safe to use.
706 Note: While write support is safe in this version (a rewrite from
707 scratch of the NTFS support), it should be noted that the old NTFS
708 write support, included in Linux 2.5.10 and before (since 1997),
711 This is currently useful with TopologiLinux. TopologiLinux is run
712 on top of any DOS/Microsoft Windows system without partitioning your
713 hard disk. Unlike other Linux distributions TopologiLinux does not
714 need its own partition. For more information see
715 <http://topologi-linux.sourceforge.net/>
717 It is perfectly safe to say N here.
721 menu "Pseudo filesystems"
724 bool "/proc file system support"
726 This is a virtual file system providing information about the status
727 of the system. "Virtual" means that it doesn't take up any space on
728 your hard disk: the files are created on the fly by the kernel when
729 you try to access them. Also, you cannot read the files with older
730 version of the program less: you need to use more or cat.
732 It's totally cool; for example, "cat /proc/interrupts" gives
733 information about what the different IRQs are used for at the moment
734 (there is a small number of Interrupt ReQuest lines in your computer
735 that are used by the attached devices to gain the CPU's attention --
736 often a source of trouble if two devices are mistakenly configured
737 to use the same IRQ). The program procinfo to display some
738 information about your system gathered from the /proc file system.
740 Before you can use the /proc file system, it has to be mounted,
741 meaning it has to be given a location in the directory hierarchy.
742 That location should be /proc. A command such as "mount -t proc proc
743 /proc" or the equivalent line in /etc/fstab does the job.
745 The /proc file system is explained in the file
746 <file:Documentation/filesystems/proc.txt> and on the proc(5) manpage
749 This option will enlarge your kernel by about 67 KB. Several
750 programs depend on this, so everyone should say Y here.
753 bool "/proc/kcore support" if !ARM
754 depends on PROC_FS && MMU
757 bool "/proc/vmcore support (EXPERIMENTAL)"
758 depends on PROC_FS && EMBEDDED && EXPERIMENTAL && CRASH_DUMP
760 Exports the dump image of crashed kernel in ELF format.
763 bool "sysfs file system support" if EMBEDDED
766 The sysfs filesystem is a virtual filesystem that the kernel uses to
767 export internal kernel objects, their attributes, and their
768 relationships to one another.
770 Users can use sysfs to ascertain useful information about the running
771 kernel, such as the devices the kernel has discovered on each bus and
772 which driver each is bound to. sysfs can also be used to tune devices
773 and other kernel subsystems.
775 Some system agents rely on the information in sysfs to operate.
776 /sbin/hotplug uses device and object attributes in sysfs to assist in
777 delegating policy decisions, like persistantly naming devices.
779 sysfs is currently used by the block subsystem to mount the root
780 partition. If sysfs is disabled you must specify the boot device on
781 the kernel boot command line via its major and minor numbers. For
782 example, "root=03:01" for /dev/hda1.
784 Designers of embedded systems may wish to say N here to conserve space.
787 bool "Virtual memory file system support (former shm fs)"
789 Tmpfs is a file system which keeps all files in virtual memory.
791 Everything in tmpfs is temporary in the sense that no files will be
792 created on your hard drive. The files live in memory and swap
793 space. If you unmount a tmpfs instance, everything stored therein is
796 See <file:Documentation/filesystems/tmpfs.txt> for details.
799 bool "HugeTLB file system support"
800 depends X86 || IA64 || PPC64 || SPARC64 || SUPERH || X86_64 || BROKEN
809 Ramfs is a file system which keeps all files in RAM. It allows
810 read and write access.
812 It is more of an programming example than a useable file system. If
813 you need a file system which lives in RAM with limit checking use
816 To compile this as a module, choose M here: the module will be called
820 tristate "Relayfs file system support"
822 Relayfs is a high-speed data relay filesystem designed to provide
823 an efficient mechanism for tools and facilities to relay large
824 amounts of data from kernel space to user space.
826 To compile this code as a module, choose M here: the module will be
833 menu "Miscellaneous filesystems"
836 tristate "ADFS file system support (EXPERIMENTAL)"
837 depends on EXPERIMENTAL
839 The Acorn Disc Filing System is the standard file system of the
840 RiscOS operating system which runs on Acorn's ARM-based Risc PC
841 systems and the Acorn Archimedes range of machines. If you say Y
842 here, Linux will be able to read from ADFS partitions on hard drives
843 and from ADFS-formatted floppy discs. If you also want to be able to
844 write to those devices, say Y to "ADFS write support" below.
846 The ADFS partition should be the first partition (i.e.,
847 /dev/[hs]d?1) on each of your drives. Please read the file
848 <file:Documentation/filesystems/adfs.txt> for further details.
850 To compile this code as a module, choose M here: the module will be
856 bool "ADFS write support (DANGEROUS)"
859 If you say Y here, you will be able to write to ADFS partitions on
860 hard drives and ADFS-formatted floppy disks. This is experimental
861 codes, so if you're unsure, say N.
864 tristate "Amiga FFS file system support (EXPERIMENTAL)"
865 depends on EXPERIMENTAL
867 The Fast File System (FFS) is the common file system used on hard
868 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
869 if you want to be able to read and write files from and to an Amiga
870 FFS partition on your hard drive. Amiga floppies however cannot be
871 read with this driver due to an incompatibility of the floppy
872 controller used in an Amiga and the standard floppy controller in
873 PCs and workstations. Read <file:Documentation/filesystems/affs.txt>
874 and <file:fs/affs/Changes>.
876 With this driver you can also mount disk files used by Bernd
877 Schmidt's Un*X Amiga Emulator
878 (<http://www.freiburg.linux.de/~uae/>).
879 If you want to do this, you will also need to say Y or M to "Loop
880 device support", above.
882 To compile this file system support as a module, choose M here: the
883 module will be called affs. If unsure, say N.
886 tristate "Apple Macintosh file system support (EXPERIMENTAL)"
887 depends on EXPERIMENTAL
889 If you say Y here, you will be able to mount Macintosh-formatted
890 floppy disks and hard drive partitions with full read-write access.
891 Please read <file:fs/hfs/HFS.txt> to learn about the available mount
894 To compile this file system support as a module, choose M here: the
895 module will be called hfs.
898 tristate "Apple Extended HFS file system support"
902 If you say Y here, you will be able to mount extended format
903 Macintosh-formatted hard drive partitions with full read-write access.
905 This file system is often called HFS+ and was introduced with
906 MacOS 8. It includes all Mac specific filesystem data such as
907 data forks and creator codes, but it also has several UNIX
908 style features such as file ownership and permissions.
911 tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)"
912 depends on EXPERIMENTAL
915 The BeOS File System (BeFS) is the native file system of Be, Inc's
916 BeOS. Notable features include support for arbitrary attributes
917 on files and directories, and database-like indeces on selected
918 attributes. (Also note that this driver doesn't make those features
919 available at this time). It is a 64 bit filesystem, so it supports
920 extremly large volumes and files.
922 If you use this filesystem, you should also say Y to at least one
923 of the NLS (native language support) options below.
925 If you don't know what this is about, say N.
927 To compile this as a module, choose M here: the module will be
934 If you say Y here, you can use the 'debug' mount option to enable
935 debugging output from the driver.
938 tristate "BFS file system support (EXPERIMENTAL)"
939 depends on EXPERIMENTAL
941 Boot File System (BFS) is a file system used under SCO UnixWare to
942 allow the bootloader access to the kernel image and other important
943 files during the boot process. It is usually mounted under /stand
944 and corresponds to the slice marked as "STAND" in the UnixWare
945 partition. You should say Y if you want to read or write the files
946 on your /stand slice from within Linux. You then also need to say Y
947 to "UnixWare slices support", below. More information about the BFS
948 file system is contained in the file
949 <file:Documentation/filesystems/bfs.txt>.
951 If you don't know what this is about, say N.
953 To compile this as a module, choose M here: the module will be called
954 bfs. Note that the file system of your root partition (the one
955 containing the directory /) cannot be compiled as a module.
960 tristate "EFS file system support (read only) (EXPERIMENTAL)"
961 depends on EXPERIMENTAL
963 EFS is an older file system used for non-ISO9660 CD-ROMs and hard
964 disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
965 uses the XFS file system for hard disk partitions however).
967 This implementation only offers read-only access. If you don't know
968 what all this is about, it's safe to say N. For more information
969 about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
971 To compile the EFS file system support as a module, choose M here: the
972 module will be called efs.
975 tristate "Journalling Flash File System (JFFS) support"
978 JFFS is the Journaling Flash File System developed by Axis
979 Communications in Sweden, aimed at providing a crash/powerdown-safe
980 file system for disk-less embedded devices. Further information is
981 available at (<http://developer.axis.com/software/jffs/>).
983 config JFFS_FS_VERBOSE
984 int "JFFS debugging verbosity (0 = quiet, 3 = noisy)"
988 Determines the verbosity level of the JFFS debugging messages.
991 bool "JFFS stats available in /proc filesystem"
992 depends on JFFS_FS && PROC_FS
994 Enabling this option will cause statistics from mounted JFFS file systems
995 to be made available to the user in the /proc/fs/jffs/ directory.
998 tristate "Journalling Flash File System v2 (JFFS2) support"
1002 JFFS2 is the second generation of the Journalling Flash File System
1003 for use on diskless embedded devices. It provides improved wear
1004 levelling, compression and support for hard links. You cannot use
1005 this on normal block devices, only on 'MTD' devices.
1007 Further information on the design and implementation of JFFS2 is
1008 available at <http://sources.redhat.com/jffs2/>.
1010 config JFFS2_FS_DEBUG
1011 int "JFFS2 debugging verbosity (0 = quiet, 2 = noisy)"
1015 This controls the amount of debugging messages produced by the JFFS2
1016 code. Set it to zero for use in production systems. For evaluation,
1017 testing and debugging, it's advisable to set it to one. This will
1018 enable a few assertions and will print debugging messages at the
1019 KERN_DEBUG loglevel, where they won't normally be visible. Level 2
1020 is unlikely to be useful - it enables extra debugging in certain
1021 areas which at one point needed debugging, but when the bugs were
1022 located and fixed, the detailed messages were relegated to level 2.
1024 If reporting bugs, please try to have available a full dump of the
1025 messages at debug level 1 while the misbehaviour was occurring.
1027 config JFFS2_FS_WRITEBUFFER
1028 bool "JFFS2 write-buffering support"
1032 This enables the write-buffering support in JFFS2.
1034 This functionality is required to support JFFS2 on the following
1035 types of flash devices:
1037 - NOR flash with transparent ECC
1040 config JFFS2_COMPRESSION_OPTIONS
1041 bool "Advanced compression options for JFFS2"
1045 Enabling this option allows you to explicitly choose which
1046 compression modules, if any, are enabled in JFFS2. Removing
1047 compressors and mean you cannot read existing file systems,
1048 and enabling experimental compressors can mean that you
1049 write a file system which cannot be read by a standard kernel.
1051 If unsure, you should _definitely_ say 'N'.
1054 bool "JFFS2 ZLIB compression support" if JFFS2_COMPRESSION_OPTIONS
1060 Zlib is designed to be a free, general-purpose, legally unencumbered,
1061 lossless data-compression library for use on virtually any computer
1062 hardware and operating system. See <http://www.gzip.org/zlib/> for
1063 further information.
1068 bool "JFFS2 RTIME compression support" if JFFS2_COMPRESSION_OPTIONS
1072 Rtime does manage to recompress already-compressed data. Say 'Y' if unsure.
1075 bool "JFFS2 RUBIN compression support" if JFFS2_COMPRESSION_OPTIONS
1079 RUBINMIPS and DYNRUBIN compressors. Say 'N' if unsure.
1082 prompt "JFFS2 default compression mode" if JFFS2_COMPRESSION_OPTIONS
1083 default JFFS2_CMODE_PRIORITY
1086 You can set here the default compression mode of JFFS2 from
1087 the available compression modes. Don't touch if unsure.
1089 config JFFS2_CMODE_NONE
1090 bool "no compression"
1092 Uses no compression.
1094 config JFFS2_CMODE_PRIORITY
1097 Tries the compressors in a predefinied order and chooses the first
1100 config JFFS2_CMODE_SIZE
1101 bool "size (EXPERIMENTAL)"
1103 Tries all compressors and chooses the one which has the smallest
1109 tristate "Compressed ROM file system support (cramfs)"
1112 Saying Y here includes support for CramFs (Compressed ROM File
1113 System). CramFs is designed to be a simple, small, and compressed
1114 file system for ROM based embedded systems. CramFs is read-only,
1115 limited to 256MB file systems (with 16MB files), and doesn't support
1116 16/32 bits uid/gid, hard links and timestamps.
1118 See <file:Documentation/filesystems/cramfs.txt> and
1119 <file:fs/cramfs/README> for further information.
1121 To compile this as a module, choose M here: the module will be called
1122 cramfs. Note that the root file system (the one containing the
1123 directory /) cannot be compiled as a module.
1128 tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
1130 FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
1131 file system format. VERITAS VxFS(TM) is the standard file system
1132 of SCO UnixWare (and possibly others) and optionally available
1133 for Sunsoft Solaris, HP-UX and many other operating systems.
1134 Currently only readonly access is supported.
1136 NOTE: the file system type as used by mount(1), mount(2) and
1137 fstab(5) is 'vxfs' as it describes the file system format, not
1140 To compile this as a module, choose M here: the module will be
1141 called freevxfs. If unsure, say N.
1145 tristate "OS/2 HPFS file system support"
1147 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
1148 is the file system used for organizing files on OS/2 hard disk
1149 partitions. Say Y if you want to be able to read files from and
1150 write files to an OS/2 HPFS partition on your hard drive. OS/2
1151 floppies however are in regular MSDOS format, so you don't need this
1152 option in order to be able to read them. Read
1153 <file:Documentation/filesystems/hpfs.txt>.
1155 To compile this file system support as a module, choose M here: the
1156 module will be called hpfs. If unsure, say N.
1161 tristate "QNX4 file system support (read only)"
1163 This is the file system used by the real-time operating systems
1164 QNX 4 and QNX 6 (the latter is also called QNX RTP).
1165 Further information is available at <http://www.qnx.com/>.
1166 Say Y if you intend to mount QNX hard disks or floppies.
1167 Unless you say Y to "QNX4FS read-write support" below, you will
1168 only be able to read these file systems.
1170 To compile this file system support as a module, choose M here: the
1171 module will be called qnx4.
1173 If you don't know whether you need it, then you don't need it:
1177 bool "QNX4FS write support (DANGEROUS)"
1178 depends on QNX4FS_FS && EXPERIMENTAL && BROKEN
1180 Say Y if you want to test write support for QNX4 file systems.
1182 It's currently broken, so for now:
1188 tristate "System V/Xenix/V7/Coherent file system support"
1190 SCO, Xenix and Coherent are commercial Unix systems for Intel
1191 machines, and Version 7 was used on the DEC PDP-11. Saying Y
1192 here would allow you to read from their floppies and hard disk
1195 If you have floppies or hard disk partitions like that, it is likely
1196 that they contain binaries from those other Unix systems; in order
1197 to run these binaries, you will want to install linux-abi which is a
1198 a set of kernel modules that lets you run SCO, Xenix, Wyse,
1199 UnixWare, Dell Unix and System V programs under Linux. It is
1200 available via FTP (user: ftp) from
1201 <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
1202 NOTE: that will work only for binaries from Intel-based systems;
1203 PDP ones will have to wait until somebody ports Linux to -11 ;-)
1205 If you only intend to mount files from some other Unix over the
1206 network using NFS, you don't need the System V file system support
1207 (but you need NFS file system support obviously).
1209 Note that this option is generally not needed for floppies, since a
1210 good portable way to transport files and directories between unixes
1211 (and even other operating systems) is given by the tar program ("man
1212 tar" or preferably "info tar"). Note also that this option has
1213 nothing whatsoever to do with the option "System V IPC". Read about
1214 the System V file system in
1215 <file:Documentation/filesystems/sysv-fs.txt>.
1216 Saying Y here will enlarge your kernel by about 27 KB.
1218 To compile this as a module, choose M here: the module will be called
1221 If you haven't heard about all of this before, it's safe to say N.
1226 tristate "UFS file system support (read only)"
1228 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
1229 OpenBSD and NeXTstep) use a file system called UFS. Some System V
1230 Unixes can create and mount hard disk partitions and diskettes using
1231 this file system as well. Saying Y here will allow you to read from
1232 these partitions; if you also want to write to them, say Y to the
1233 experimental "UFS file system write support", below. Please read the
1234 file <file:Documentation/filesystems/ufs.txt> for more information.
1236 The recently released UFS2 variant (used in FreeBSD 5.x) is
1237 READ-ONLY supported.
1239 If you only intend to mount files from some other Unix over the
1240 network using NFS, you don't need the UFS file system support (but
1241 you need NFS file system support obviously).
1243 Note that this option is generally not needed for floppies, since a
1244 good portable way to transport files and directories between unixes
1245 (and even other operating systems) is given by the tar program ("man
1246 tar" or preferably "info tar").
1248 When accessing NeXTstep files, you may need to convert them from the
1249 NeXT character set to the Latin1 character set; use the program
1250 recode ("info recode") for this purpose.
1252 To compile the UFS file system support as a module, choose M here: the
1253 module will be called ufs.
1255 If you haven't heard about all of this before, it's safe to say N.
1258 bool "UFS file system write support (DANGEROUS)"
1259 depends on UFS_FS && EXPERIMENTAL
1261 Say Y here if you want to try writing to UFS partitions. This is
1262 experimental, so you should back up your UFS partitions beforehand.
1266 menu "Network File Systems"
1270 tristate "NFS file system support"
1274 select NFS_ACL_SUPPORT if NFS_V3_ACL
1276 If you are connected to some other (usually local) Unix computer
1277 (using SLIP, PLIP, PPP or Ethernet) and want to mount files residing
1278 on that computer (the NFS server) using the Network File Sharing
1279 protocol, say Y. "Mounting files" means that the client can access
1280 the files with usual UNIX commands as if they were sitting on the
1281 client's hard disk. For this to work, the server must run the
1282 programs nfsd and mountd (but does not need to have NFS file system
1283 support enabled in its kernel). NFS is explained in the Network
1284 Administrator's Guide, available from
1285 <http://www.tldp.org/docs.html#guide>, on its man page: "man
1286 nfs", and in the NFS-HOWTO.
1288 A superior but less widely used alternative to NFS is provided by
1289 the Coda file system; see "Coda file system support" below.
1291 If you say Y here, you should have said Y to TCP/IP networking also.
1292 This option would enlarge your kernel by about 27 KB.
1294 To compile this file system support as a module, choose M here: the
1295 module will be called nfs.
1297 If you are configuring a diskless machine which will mount its root
1298 file system over NFS at boot time, say Y here and to "Kernel
1299 level IP autoconfiguration" above and to "Root file system on NFS"
1300 below. You cannot compile this driver as a module in this case.
1301 There are two packages designed for booting diskless machines over
1302 the net: netboot, available from
1303 <http://ftp1.sourceforge.net/netboot/>, and Etherboot,
1304 available from <http://ftp1.sourceforge.net/etherboot/>.
1306 If you don't know what all this is about, say N.
1309 bool "Provide NFSv3 client support"
1312 Say Y here if you want your NFS client to be able to speak version
1313 3 of the NFS protocol.
1318 bool "Provide client support for the NFSv3 ACL protocol extension"
1321 Implement the NFSv3 ACL protocol extension for manipulating POSIX
1322 Access Control Lists. The server should also be compiled with
1323 the NFSv3 ACL protocol extension; see the CONFIG_NFSD_V3_ACL option.
1328 bool "Provide NFSv4 client support (EXPERIMENTAL)"
1329 depends on NFS_FS && EXPERIMENTAL
1330 select RPCSEC_GSS_KRB5
1332 Say Y here if you want your NFS client to be able to speak the newer
1333 version 4 of the NFS protocol.
1335 Note: Requires auxiliary userspace daemons which may be found on
1336 http://www.citi.umich.edu/projects/nfsv4/
1341 bool "Allow direct I/O on NFS files (EXPERIMENTAL)"
1342 depends on NFS_FS && EXPERIMENTAL
1344 This option enables applications to perform uncached I/O on files
1345 in NFS file systems using the O_DIRECT open() flag. When O_DIRECT
1346 is set for a file, its data is not cached in the system's page
1347 cache. Data is moved to and from user-level application buffers
1348 directly. Unlike local disk-based file systems, NFS O_DIRECT has
1349 no alignment restrictions.
1351 Unless your program is designed to use O_DIRECT properly, you are
1352 much better off allowing the NFS client to manage data caching for
1353 you. Misusing O_DIRECT can cause poor server performance or network
1354 storms. This kernel build option defaults OFF to avoid exposing
1355 system administrators unwittingly to a potentially hazardous
1358 For more details on NFS O_DIRECT, see fs/nfs/direct.c.
1360 If unsure, say N. This reduces the size of the NFS client, and
1361 causes open() to return EINVAL if a file residing in NFS is
1362 opened with the O_DIRECT flag.
1365 tristate "NFS server support"
1370 select NFS_ACL_SUPPORT if NFSD_V3_ACL || NFSD_V2_ACL
1372 If you want your Linux box to act as an NFS *server*, so that other
1373 computers on your local network which support NFS can access certain
1374 directories on your box transparently, you have two options: you can
1375 use the self-contained user space program nfsd, in which case you
1376 should say N here, or you can say Y and use the kernel based NFS
1377 server. The advantage of the kernel based solution is that it is
1380 In either case, you will need support software; the respective
1381 locations are given in the file <file:Documentation/Changes> in the
1384 If you say Y here, you will get support for version 2 of the NFS
1385 protocol (NFSv2). If you also want NFSv3, say Y to the next question
1388 Please read the NFS-HOWTO, available from
1389 <http://www.tldp.org/docs.html#howto>.
1391 To compile the NFS server support as a module, choose M here: the
1392 module will be called nfsd. If unsure, say N.
1399 bool "Provide NFSv3 server support"
1402 If you would like to include the NFSv3 server as well as the NFSv2
1403 server, say Y here. If unsure, say Y.
1406 bool "Provide server support for the NFSv3 ACL protocol extension"
1410 Implement the NFSv3 ACL protocol extension for manipulating POSIX
1411 Access Control Lists on exported file systems. NFS clients should
1412 be compiled with the NFSv3 ACL protocol extension; see the
1413 CONFIG_NFS_V3_ACL option. If unsure, say N.
1416 bool "Provide NFSv4 server support (EXPERIMENTAL)"
1417 depends on NFSD_V3 && EXPERIMENTAL
1423 If you would like to include the NFSv4 server as well as the NFSv2
1424 and NFSv3 servers, say Y here. This feature is experimental, and
1425 should only be used if you are interested in helping to test NFSv4.
1429 bool "Provide NFS server over TCP support"
1433 If you want your NFS server to support TCP connections, say Y here.
1434 TCP connections usually perform better than the default UDP when
1435 the network is lossy or congested. If unsure, say Y.
1438 bool "Root file system on NFS"
1439 depends on NFS_FS=y && IP_PNP
1441 If you want your Linux box to mount its whole root file system (the
1442 one containing the directory /) from some other computer over the
1443 net via NFS (presumably because your box doesn't have a hard disk),
1444 say Y. Read <file:Documentation/nfsroot.txt> for details. It is
1445 likely that in this case, you also want to say Y to "Kernel level IP
1446 autoconfiguration" so that your box can discover its network address
1449 Most people say N here.
1456 depends on NFSD_V3 || NFS_V3
1462 config NFS_ACL_SUPPORT
1468 depends on NFSD || NFS_FS
1477 config RPCSEC_GSS_KRB5
1478 tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
1479 depends on SUNRPC && EXPERIMENTAL
1485 Provides for secure RPC calls by means of a gss-api
1486 mechanism based on Kerberos V5. This is required for
1489 Note: Requires an auxiliary userspace daemon which may be found on
1490 http://www.citi.umich.edu/projects/nfsv4/
1494 config RPCSEC_GSS_SPKM3
1495 tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
1496 depends on SUNRPC && EXPERIMENTAL
1502 Provides for secure RPC calls by means of a gss-api
1503 mechanism based on the SPKM3 public-key mechanism.
1505 Note: Requires an auxiliary userspace daemon which may be found on
1506 http://www.citi.umich.edu/projects/nfsv4/
1511 tristate "SMB file system support (to mount Windows shares etc.)"
1515 SMB (Server Message Block) is the protocol Windows for Workgroups
1516 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
1517 files and printers over local networks. Saying Y here allows you to
1518 mount their file systems (often called "shares" in this context) and
1519 access them just like any other Unix directory. Currently, this
1520 works only if the Windows machines use TCP/IP as the underlying
1521 transport protocol, and not NetBEUI. For details, read
1522 <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
1523 available from <http://www.tldp.org/docs.html#howto>.
1525 Note: if you just want your box to act as an SMB *server* and make
1526 files and printing services available to Windows clients (which need
1527 to have a TCP/IP stack), you don't need to say Y here; you can use
1528 the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
1531 General information about how to connect Linux, Windows machines and
1532 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1534 To compile the SMB support as a module, choose M here: the module will
1535 be called smbfs. Most people say N, however.
1537 config SMB_NLS_DEFAULT
1538 bool "Use a default NLS"
1541 Enabling this will make smbfs use nls translations by default. You
1542 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
1543 settings and you need to give the default nls for the SMB server as
1544 CONFIG_SMB_NLS_REMOTE.
1546 The nls settings can be changed at mount time, if your smbmount
1547 supports that, using the codepage and iocharset parameters.
1549 smbmount from samba 2.2.0 or later supports this.
1551 config SMB_NLS_REMOTE
1552 string "Default Remote NLS Option"
1553 depends on SMB_NLS_DEFAULT
1556 This setting allows you to specify a default value for which
1557 codepage the server uses. If this field is left blank no
1558 translations will be done by default. The local codepage/charset
1559 default to CONFIG_NLS_DEFAULT.
1561 The nls settings can be changed at mount time, if your smbmount
1562 supports that, using the codepage and iocharset parameters.
1564 smbmount from samba 2.2.0 or later supports this.
1567 tristate "CIFS support (advanced network filesystem for Samba, Window and other CIFS compliant servers)"
1571 This is the client VFS module for the Common Internet File System
1572 (CIFS) protocol which is the successor to the Server Message Block
1573 (SMB) protocol, the native file sharing mechanism for most early
1574 PC operating systems. The CIFS protocol is fully supported by
1575 file servers such as Windows 2000 (including Windows 2003, NT 4
1576 and Windows XP) as well by Samba (which provides excellent CIFS
1577 server support for Linux and many other operating systems). Currently
1578 you must use the smbfs client filesystem to access older SMB servers
1579 such as Windows 9x and OS/2.
1581 The intent of the cifs module is to provide an advanced
1582 network file system client for mounting to CIFS compliant servers,
1583 including support for dfs (hierarchical name space), secure per-user
1584 session establishment, safe distributed caching (oplock), optional
1585 packet signing, Unicode and other internationalization improvements,
1586 and optional Winbind (nsswitch) integration. You do not need to enable
1587 cifs if running only a (Samba) server. It is possible to enable both
1588 smbfs and cifs (e.g. if you are using CIFS for accessing Windows 2003
1589 and Samba 3 servers, and smbfs for accessing old servers). If you need
1590 to mount to Samba or Windows 2003 servers from this machine, say Y.
1593 bool "CIFS statistics"
1596 Enabling this option will cause statistics for each server share
1597 mounted by the cifs client to be displayed in /proc/fs/cifs/Stats
1600 bool "CIFS extended attributes (EXPERIMENTAL)"
1603 Extended attributes are name:value pairs associated with inodes by
1604 the kernel or by users (see the attr(5) manual page, or visit
1605 <http://acl.bestbits.at/> for details). CIFS maps the name of
1606 extended attributes beginning with the user namespace prefix
1607 to SMB/CIFS EAs. EAs are stored on Windows servers without the
1608 user namespace prefix, but their names are seen by Linux cifs clients
1609 prefaced by the user namespace prefix. The system namespace
1610 (used by some filesystems to store ACLs) is not supported at
1616 bool "CIFS POSIX Extensions (EXPERIMENTAL)"
1617 depends on CIFS_XATTR
1619 Enabling this option will cause the cifs client to attempt to
1620 negotiate a newer dialect with servers, such as Samba 3.0.5
1621 or later, that optionally can handle more POSIX like (rather
1622 than Windows like) file behavior. It also enables
1623 support for POSIX ACLs (getfacl and setfacl) to servers
1624 (such as Samba 3.10 and later) which can negotiate
1625 CIFS POSIX ACL support. If unsure, say N.
1627 config CIFS_EXPERIMENTAL
1628 bool "CIFS Experimental Features (EXPERIMENTAL)"
1631 Enables cifs features under testing. These features
1632 are highly experimental. If unsure, say N.
1635 tristate "NCP file system support (to mount NetWare volumes)"
1636 depends on IPX!=n || INET
1638 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
1639 used by Novell NetWare clients to talk to file servers. It is to
1640 IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
1641 to mount NetWare file server volumes and to access them just like
1642 any other Unix directory. For details, please read the file
1643 <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
1644 the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
1646 You do not have to say Y here if you want your Linux box to act as a
1647 file *server* for Novell NetWare clients.
1649 General information about how to connect Linux, Windows machines and
1650 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1652 To compile this as a module, choose M here: the module will be called
1653 ncpfs. Say N unless you are connected to a Novell network.
1655 source "fs/ncpfs/Kconfig"
1658 tristate "Coda file system support (advanced network fs)"
1661 Coda is an advanced network file system, similar to NFS in that it
1662 enables you to mount file systems of a remote server and access them
1663 with regular Unix commands as if they were sitting on your hard
1664 disk. Coda has several advantages over NFS: support for
1665 disconnected operation (e.g. for laptops), read/write server
1666 replication, security model for authentication and encryption,
1667 persistent client caches and write back caching.
1669 If you say Y here, your Linux box will be able to act as a Coda
1670 *client*. You will need user level code as well, both for the
1671 client and server. Servers are currently user level, i.e. they need
1672 no kernel support. Please read
1673 <file:Documentation/filesystems/coda.txt> and check out the Coda
1674 home page <http://www.coda.cs.cmu.edu/>.
1676 To compile the coda client support as a module, choose M here: the
1677 module will be called coda.
1679 config CODA_FS_OLD_API
1680 bool "Use 96-bit Coda file identifiers"
1683 A new kernel-userspace API had to be introduced for Coda v6.0
1684 to support larger 128-bit file identifiers as needed by the
1685 new realms implementation.
1687 However this new API is not backward compatible with older
1688 clients. If you really need to run the old Coda userspace
1689 cache manager then say Y.
1691 For most cases you probably want to say N.
1694 # for fs/nls/Config.in
1695 tristate "Andrew File System support (AFS) (Experimental)"
1696 depends on INET && EXPERIMENTAL
1699 If you say Y here, you will get an experimental Andrew File System
1700 driver. It currently only supports unsecured read-only AFS access.
1702 See <file:Documentation/filesystems/afs.txt> for more intormation.
1711 menu "Partition Types"
1713 source "fs/partitions/Kconfig"
1717 source "fs/nls/Kconfig"