2 # File system configuration
9 source "fs/ext2/Kconfig"
10 source "fs/ext3/Kconfig"
11 source "fs/ext4/Kconfig"
16 depends on EXT2_FS_XIP
19 source "fs/jbd/Kconfig"
20 source "fs/jbd2/Kconfig"
23 # Meta block cache for Extended Attributes (ext2/ext3/ext4)
25 default y if EXT2_FS=y && EXT2_FS_XATTR
26 default y if EXT3_FS=y && EXT3_FS_XATTR
27 default y if EXT4_FS=y && EXT4_FS_XATTR
28 default m if EXT2_FS_XATTR || EXT3_FS_XATTR || EXT4_FS_XATTR
30 source "fs/reiserfs/Kconfig"
31 source "fs/jfs/Kconfig"
34 # Posix ACL utility routines (for now, only ext2/ext3/jfs/reiserfs/nfs4)
36 # NOTE: you can implement Posix ACLs without these helpers (XFS does).
37 # Never use this symbol for ifdefs.
43 bool "Enable POSIX file locking API" if EMBEDDED
46 This option enables standard file locking support, required
47 for filesystems like NFS and for the flock() system
48 call. Disabling this option saves about 11k.
50 source "fs/xfs/Kconfig"
51 source "fs/gfs2/Kconfig"
52 source "fs/ocfs2/Kconfig"
53 source "fs/btrfs/Kconfig"
57 source "fs/notify/Kconfig"
62 If you say Y here, you will be able to set per user limits for disk
63 usage (also called disk quotas). Currently, it works for the
64 ext2, ext3, and reiserfs file system. ext3 also supports journalled
65 quotas for which you don't need to run quotacheck(8) after an unclean
67 For further details, read the Quota mini-HOWTO, available from
68 <http://www.tldp.org/docs.html#howto>, or the documentation provided
69 with the quota tools. Probably the quota support is only useful for
70 multi user systems. If unsure, say N.
72 config QUOTA_NETLINK_INTERFACE
73 bool "Report quota messages through netlink interface"
74 depends on QUOTA && NET
76 If you say Y here, quota warnings (about exceeding softlimit, reaching
77 hardlimit, etc.) will be reported through netlink interface. If unsure,
80 config PRINT_QUOTA_WARNING
81 bool "Print quota warnings to console (OBSOLETE)"
85 If you say Y here, quota warnings (about exceeding softlimit, reaching
86 hardlimit, etc.) will be printed to the process' controlling terminal.
87 Note that this behavior is currently deprecated and may go away in
88 future. Please use notification via netlink socket instead.
90 # Generic support for tree structured quota files. Seleted when needed.
95 tristate "Old quota format support"
98 This quota format was (is) used by kernels earlier than 2.4.22. If
99 you have quota working and you don't want to convert to new quota
103 tristate "Quota format v2 support"
107 This quota format allows using quotas with 32-bit UIDs/GIDs. If you
108 need this functionality say Y here.
112 depends on XFS_QUOTA || QUOTA
115 source "fs/autofs/Kconfig"
116 source "fs/autofs4/Kconfig"
117 source "fs/fuse/Kconfig"
124 menu "CD-ROM/DVD Filesystems"
127 tristate "ISO 9660 CDROM file system support"
129 This is the standard file system used on CD-ROMs. It was previously
130 known as "High Sierra File System" and is called "hsfs" on other
131 Unix systems. The so-called Rock-Ridge extensions which allow for
132 long Unix filenames and symbolic links are also supported by this
133 driver. If you have a CD-ROM drive and want to do more with it than
134 just listen to audio CDs and watch its LEDs, say Y (and read
135 <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO,
136 available from <http://www.tldp.org/docs.html#howto>), thereby
137 enlarging your kernel by about 27 KB; otherwise say N.
139 To compile this file system support as a module, choose M here: the
140 module will be called isofs.
143 bool "Microsoft Joliet CDROM extensions"
144 depends on ISO9660_FS
147 Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system
148 which allows for long filenames in unicode format (unicode is the
149 new 16 bit character code, successor to ASCII, which encodes the
150 characters of almost all languages of the world; see
151 <http://www.unicode.org/> for more information). Say Y here if you
152 want to be able to read Joliet CD-ROMs under Linux.
155 bool "Transparent decompression extension"
156 depends on ISO9660_FS
159 This is a Linux-specific extension to RockRidge which lets you store
160 data in compressed form on a CD-ROM and have it transparently
161 decompressed when the CD-ROM is accessed. See
162 <http://www.kernel.org/pub/linux/utils/fs/zisofs/> for the tools
163 necessary to create such a filesystem. Say Y here if you want to be
164 able to read such compressed CD-ROMs.
167 tristate "UDF file system support"
170 This is the new file system used on some CD-ROMs and DVDs. Say Y if
171 you intend to mount DVD discs or CDRW's written in packet mode, or
172 if written to by other UDF utilities, such as DirectCD.
173 Please read <file:Documentation/filesystems/udf.txt>.
175 To compile this file system support as a module, choose M here: the
176 module will be called udf.
183 depends on (UDF_FS=m && NLS) || (UDF_FS=y && NLS=y)
189 menu "DOS/FAT/NT Filesystems"
195 If you want to use one of the FAT-based file systems (the MS-DOS and
196 VFAT (Windows 95) file systems), then you must say Y or M here
197 to include FAT support. You will then be able to mount partitions or
198 diskettes with FAT-based file systems and transparently access the
199 files on them, i.e. MSDOS files will look and behave just like all
202 This FAT support is not a file system in itself, it only provides
203 the foundation for the other file systems. You will have to say Y or
204 M to at least one of "MSDOS fs support" or "VFAT fs support" in
205 order to make use of it.
207 Another way to read and write MSDOS floppies and hard drive
208 partitions from within Linux (but not transparently) is with the
209 mtools ("man mtools") program suite. You don't need to say Y here in
212 If you need to move large files on floppies between a DOS and a
213 Linux box, say Y here, mount the floppy under Linux with an MSDOS
214 file system and use GNU tar's M option. GNU tar is a program
215 available for Unix and DOS ("man tar" or "info tar").
217 The FAT support will enlarge your kernel by about 37 KB. If unsure,
220 To compile this as a module, choose M here: the module will be called
221 fat. Note that if you compile the FAT support as a module, you
222 cannot compile any of the FAT-based file systems into the kernel
223 -- they will have to be modules as well.
226 tristate "MSDOS fs support"
229 This allows you to mount MSDOS partitions of your hard drive (unless
230 they are compressed; to access compressed MSDOS partitions under
231 Linux, you can either use the DOS emulator DOSEMU, described in the
232 DOSEMU-HOWTO, available from
233 <http://www.tldp.org/docs.html#howto>, or try dmsdosfs in
234 <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you
235 intend to use dosemu with a non-compressed MSDOS partition, say Y
236 here) and MSDOS floppies. This means that file access becomes
237 transparent, i.e. the MSDOS files look and behave just like all
240 If you have Windows 95 or Windows NT installed on your MSDOS
241 partitions, you should use the VFAT file system (say Y to "VFAT fs
242 support" below), or you will not be able to see the long filenames
243 generated by Windows 95 / Windows NT.
245 This option will enlarge your kernel by about 7 KB. If unsure,
246 answer Y. This will only work if you said Y to "DOS FAT fs support"
247 as well. To compile this as a module, choose M here: the module will
251 tristate "VFAT (Windows-95) fs support"
254 This option provides support for normal Windows file systems with
255 long filenames. That includes non-compressed FAT-based file systems
256 used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
257 programs from the mtools package.
259 The VFAT support enlarges your kernel by about 10 KB and it only
260 works if you said Y to the "DOS FAT fs support" above. Please read
261 the file <file:Documentation/filesystems/vfat.txt> for details. If
264 To compile this as a module, choose M here: the module will be called
267 config FAT_DEFAULT_CODEPAGE
268 int "Default codepage for FAT"
269 depends on MSDOS_FS || VFAT_FS
272 This option should be set to the codepage of your FAT filesystems.
273 It can be overridden with the "codepage" mount option.
274 See <file:Documentation/filesystems/vfat.txt> for more information.
276 config FAT_DEFAULT_IOCHARSET
277 string "Default iocharset for FAT"
281 Set this to the default input/output character set you'd
282 like FAT to use. It should probably match the character set
283 that most of your FAT filesystems use, and can be overridden
284 with the "iocharset" mount option for FAT filesystems.
285 Note that "utf8" is not recommended for FAT filesystems.
286 If unsure, you shouldn't set "utf8" here.
287 See <file:Documentation/filesystems/vfat.txt> for more information.
290 tristate "NTFS file system support"
293 NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003.
295 Saying Y or M here enables read support. There is partial, but
296 safe, write support available. For write support you must also
297 say Y to "NTFS write support" below.
299 There are also a number of user-space tools available, called
300 ntfsprogs. These include ntfsundelete and ntfsresize, that work
301 without NTFS support enabled in the kernel.
303 This is a rewrite from scratch of Linux NTFS support and replaced
304 the old NTFS code starting with Linux 2.5.11. A backport to
305 the Linux 2.4 kernel series is separately available as a patch
306 from the project web site.
308 For more information see <file:Documentation/filesystems/ntfs.txt>
309 and <http://www.linux-ntfs.org/>.
311 To compile this file system support as a module, choose M here: the
312 module will be called ntfs.
314 If you are not using Windows NT, 2000, XP or 2003 in addition to
315 Linux on your computer it is safe to say N.
318 bool "NTFS debugging support"
321 If you are experiencing any problems with the NTFS file system, say
322 Y here. This will result in additional consistency checks to be
323 performed by the driver as well as additional debugging messages to
324 be written to the system log. Note that debugging messages are
325 disabled by default. To enable them, supply the option debug_msgs=1
326 at the kernel command line when booting the kernel or as an option
327 to insmod when loading the ntfs module. Once the driver is active,
328 you can enable debugging messages by doing (as root):
329 echo 1 > /proc/sys/fs/ntfs-debug
330 Replacing the "1" with "0" would disable debug messages.
332 If you leave debugging messages disabled, this results in little
333 overhead, but enabling debug messages results in very significant
334 slowdown of the system.
336 When reporting bugs, please try to have available a full dump of
337 debugging messages while the misbehaviour was occurring.
340 bool "NTFS write support"
343 This enables the partial, but safe, write support in the NTFS driver.
345 The only supported operation is overwriting existing files, without
346 changing the file length. No file or directory creation, deletion or
347 renaming is possible. Note only non-resident files can be written to
348 so you may find that some very small files (<500 bytes or so) cannot
351 While we cannot guarantee that it will not damage any data, we have
352 so far not received a single report where the driver would have
353 damaged someones data so we assume it is perfectly safe to use.
355 Note: While write support is safe in this version (a rewrite from
356 scratch of the NTFS support), it should be noted that the old NTFS
357 write support, included in Linux 2.5.10 and before (since 1997),
360 This is currently useful with TopologiLinux. TopologiLinux is run
361 on top of any DOS/Microsoft Windows system without partitioning your
362 hard disk. Unlike other Linux distributions TopologiLinux does not
363 need its own partition. For more information see
364 <http://topologi-linux.sourceforge.net/>
366 It is perfectly safe to say N here.
371 menu "Pseudo filesystems"
373 source "fs/proc/Kconfig"
376 bool "sysfs file system support" if EMBEDDED
379 The sysfs filesystem is a virtual filesystem that the kernel uses to
380 export internal kernel objects, their attributes, and their
381 relationships to one another.
383 Users can use sysfs to ascertain useful information about the running
384 kernel, such as the devices the kernel has discovered on each bus and
385 which driver each is bound to. sysfs can also be used to tune devices
386 and other kernel subsystems.
388 Some system agents rely on the information in sysfs to operate.
389 /sbin/hotplug uses device and object attributes in sysfs to assist in
390 delegating policy decisions, like persistently naming devices.
392 sysfs is currently used by the block subsystem to mount the root
393 partition. If sysfs is disabled you must specify the boot device on
394 the kernel boot command line via its major and minor numbers. For
395 example, "root=03:01" for /dev/hda1.
397 Designers of embedded systems may wish to say N here to conserve space.
400 bool "Virtual memory file system support (former shm fs)"
402 Tmpfs is a file system which keeps all files in virtual memory.
404 Everything in tmpfs is temporary in the sense that no files will be
405 created on your hard drive. The files live in memory and swap
406 space. If you unmount a tmpfs instance, everything stored therein is
409 See <file:Documentation/filesystems/tmpfs.txt> for details.
411 config TMPFS_POSIX_ACL
412 bool "Tmpfs POSIX Access Control Lists"
416 POSIX Access Control Lists (ACLs) support permissions for users and
417 groups beyond the owner/group/world scheme.
419 To learn more about Access Control Lists, visit the POSIX ACLs for
420 Linux website <http://acl.bestbits.at/>.
422 If you don't know what Access Control Lists are, say N.
425 bool "HugeTLB file system support"
426 depends on X86 || IA64 || PPC64 || SPARC64 || (SUPERH && MMU) || \
427 (S390 && 64BIT) || BROKEN
429 hugetlbfs is a filesystem backing for HugeTLB pages, based on
430 ramfs. For architectures that support it, say Y here and read
431 <file:Documentation/vm/hugetlbpage.txt> for details.
439 tristate "Userspace-driven configuration filesystem"
442 configfs is a ram-based filesystem that provides the converse
443 of sysfs's functionality. Where sysfs is a filesystem-based
444 view of kernel objects, configfs is a filesystem-based manager
445 of kernel objects, or config_items.
447 Both sysfs and configfs can and should exist together on the
448 same system. One is not a replacement for the other.
452 menuconfig MISC_FILESYSTEMS
453 bool "Miscellaneous filesystems"
456 Say Y here to get to see options for various miscellaneous
457 filesystems, such as filesystems that came from other
460 This option alone does not add any kernel code.
462 If you say N, all options in this submenu will be skipped and
463 disabled; if unsure, say Y here.
468 tristate "ADFS file system support (EXPERIMENTAL)"
469 depends on BLOCK && EXPERIMENTAL
471 The Acorn Disc Filing System is the standard file system of the
472 RiscOS operating system which runs on Acorn's ARM-based Risc PC
473 systems and the Acorn Archimedes range of machines. If you say Y
474 here, Linux will be able to read from ADFS partitions on hard drives
475 and from ADFS-formatted floppy discs. If you also want to be able to
476 write to those devices, say Y to "ADFS write support" below.
478 The ADFS partition should be the first partition (i.e.,
479 /dev/[hs]d?1) on each of your drives. Please read the file
480 <file:Documentation/filesystems/adfs.txt> for further details.
482 To compile this code as a module, choose M here: the module will be
488 bool "ADFS write support (DANGEROUS)"
491 If you say Y here, you will be able to write to ADFS partitions on
492 hard drives and ADFS-formatted floppy disks. This is experimental
493 codes, so if you're unsure, say N.
496 tristate "Amiga FFS file system support (EXPERIMENTAL)"
497 depends on BLOCK && EXPERIMENTAL
499 The Fast File System (FFS) is the common file system used on hard
500 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
501 if you want to be able to read and write files from and to an Amiga
502 FFS partition on your hard drive. Amiga floppies however cannot be
503 read with this driver due to an incompatibility of the floppy
504 controller used in an Amiga and the standard floppy controller in
505 PCs and workstations. Read <file:Documentation/filesystems/affs.txt>
506 and <file:fs/affs/Changes>.
508 With this driver you can also mount disk files used by Bernd
509 Schmidt's Un*X Amiga Emulator
510 (<http://www.freiburg.linux.de/~uae/>).
511 If you want to do this, you will also need to say Y or M to "Loop
512 device support", above.
514 To compile this file system support as a module, choose M here: the
515 module will be called affs. If unsure, say N.
518 tristate "eCrypt filesystem layer support (EXPERIMENTAL)"
519 depends on EXPERIMENTAL && KEYS && CRYPTO && NET
521 Encrypted filesystem that operates on the VFS layer. See
522 <file:Documentation/filesystems/ecryptfs.txt> to learn more about
523 eCryptfs. Userspace components are required and can be
524 obtained from <http://ecryptfs.sf.net>.
526 To compile this file system support as a module, choose M here: the
527 module will be called ecryptfs.
530 tristate "Apple Macintosh file system support (EXPERIMENTAL)"
531 depends on BLOCK && EXPERIMENTAL
534 If you say Y here, you will be able to mount Macintosh-formatted
535 floppy disks and hard drive partitions with full read-write access.
536 Please read <file:Documentation/filesystems/hfs.txt> to learn about
537 the available mount options.
539 To compile this file system support as a module, choose M here: the
540 module will be called hfs.
543 tristate "Apple Extended HFS file system support"
548 If you say Y here, you will be able to mount extended format
549 Macintosh-formatted hard drive partitions with full read-write access.
551 This file system is often called HFS+ and was introduced with
552 MacOS 8. It includes all Mac specific filesystem data such as
553 data forks and creator codes, but it also has several UNIX
554 style features such as file ownership and permissions.
557 tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)"
558 depends on BLOCK && EXPERIMENTAL
561 The BeOS File System (BeFS) is the native file system of Be, Inc's
562 BeOS. Notable features include support for arbitrary attributes
563 on files and directories, and database-like indices on selected
564 attributes. (Also note that this driver doesn't make those features
565 available at this time). It is a 64 bit filesystem, so it supports
566 extremely large volumes and files.
568 If you use this filesystem, you should also say Y to at least one
569 of the NLS (native language support) options below.
571 If you don't know what this is about, say N.
573 To compile this as a module, choose M here: the module will be
580 If you say Y here, you can use the 'debug' mount option to enable
581 debugging output from the driver.
584 tristate "BFS file system support (EXPERIMENTAL)"
585 depends on BLOCK && EXPERIMENTAL
587 Boot File System (BFS) is a file system used under SCO UnixWare to
588 allow the bootloader access to the kernel image and other important
589 files during the boot process. It is usually mounted under /stand
590 and corresponds to the slice marked as "STAND" in the UnixWare
591 partition. You should say Y if you want to read or write the files
592 on your /stand slice from within Linux. You then also need to say Y
593 to "UnixWare slices support", below. More information about the BFS
594 file system is contained in the file
595 <file:Documentation/filesystems/bfs.txt>.
597 If you don't know what this is about, say N.
599 To compile this as a module, choose M here: the module will be called
600 bfs. Note that the file system of your root partition (the one
601 containing the directory /) cannot be compiled as a module.
606 tristate "EFS file system support (read only) (EXPERIMENTAL)"
607 depends on BLOCK && EXPERIMENTAL
609 EFS is an older file system used for non-ISO9660 CD-ROMs and hard
610 disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
611 uses the XFS file system for hard disk partitions however).
613 This implementation only offers read-only access. If you don't know
614 what all this is about, it's safe to say N. For more information
615 about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
617 To compile the EFS file system support as a module, choose M here: the
618 module will be called efs.
620 source "fs/jffs2/Kconfig"
621 # UBIFS File system configuration
622 source "fs/ubifs/Kconfig"
625 tristate "Compressed ROM file system support (cramfs)"
629 Saying Y here includes support for CramFs (Compressed ROM File
630 System). CramFs is designed to be a simple, small, and compressed
631 file system for ROM based embedded systems. CramFs is read-only,
632 limited to 256MB file systems (with 16MB files), and doesn't support
633 16/32 bits uid/gid, hard links and timestamps.
635 See <file:Documentation/filesystems/cramfs.txt> and
636 <file:fs/cramfs/README> for further information.
638 To compile this as a module, choose M here: the module will be called
639 cramfs. Note that the root file system (the one containing the
640 directory /) cannot be compiled as a module.
645 tristate "SquashFS 4.0 - Squashed file system support"
649 Saying Y here includes support for SquashFS 4.0 (a Compressed
650 Read-Only File System). Squashfs is a highly compressed read-only
651 filesystem for Linux. It uses zlib compression to compress both
652 files, inodes and directories. Inodes in the system are very small
653 and all blocks are packed to minimise data overhead. Block sizes
654 greater than 4K are supported up to a maximum of 1 Mbytes (default
655 block size 128K). SquashFS 4.0 supports 64 bit filesystems and files
656 (larger than 4GB), full uid/gid information, hard links and
659 Squashfs is intended for general read-only filesystem use, for
660 archival use (i.e. in cases where a .tar.gz file may be used), and in
661 embedded systems where low overhead is needed. Further information
662 and tools are available from http://squashfs.sourceforge.net.
664 If you want to compile this as a module ( = code which can be
665 inserted in and removed from the running kernel whenever you want),
666 say M here and read <file:Documentation/modules.txt>. The module
667 will be called squashfs. Note that the root file system (the one
668 containing the directory /) cannot be compiled as a module.
672 config SQUASHFS_EMBEDDED
674 bool "Additional option for memory-constrained systems"
678 Saying Y here allows you to specify cache size.
682 config SQUASHFS_FRAGMENT_CACHE_SIZE
683 int "Number of fragments cached" if SQUASHFS_EMBEDDED
687 By default SquashFS caches the last 3 fragments read from
688 the filesystem. Increasing this amount may mean SquashFS
689 has to re-read fragments less often from disk, at the expense
690 of extra system memory. Decreasing this amount will mean
691 SquashFS uses less memory at the expense of extra reads from disk.
693 Note there must be at least one cached fragment. Anything
694 much more than three will probably not make much difference.
697 tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
700 FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
701 file system format. VERITAS VxFS(TM) is the standard file system
702 of SCO UnixWare (and possibly others) and optionally available
703 for Sunsoft Solaris, HP-UX and many other operating systems.
704 Currently only readonly access is supported.
706 NOTE: the file system type as used by mount(1), mount(2) and
707 fstab(5) is 'vxfs' as it describes the file system format, not
710 To compile this as a module, choose M here: the module will be
711 called freevxfs. If unsure, say N.
714 tristate "Minix file system support"
717 Minix is a simple operating system used in many classes about OS's.
718 The minix file system (method to organize files on a hard disk
719 partition or a floppy disk) was the original file system for Linux,
720 but has been superseded by the second extended file system ext2fs.
721 You don't want to use the minix file system on your hard disk
722 because of certain built-in restrictions, but it is sometimes found
723 on older Linux floppy disks. This option will enlarge your kernel
724 by about 28 KB. If unsure, say N.
726 To compile this file system support as a module, choose M here: the
727 module will be called minix. Note that the file system of your root
728 partition (the one containing the directory /) cannot be compiled as
732 tristate "SonicBlue Optimized MPEG File System support"
736 This is the proprietary file system used by the Rio Karma music
737 player and ReplayTV DVR. Despite the name, this filesystem is not
738 more efficient than a standard FS for MPEG files, in fact likely
739 the opposite is true. Say Y if you have either of these devices
740 and wish to mount its disk.
742 To compile this file system support as a module, choose M here: the
743 module will be called omfs. If unsure, say N.
746 tristate "OS/2 HPFS file system support"
749 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
750 is the file system used for organizing files on OS/2 hard disk
751 partitions. Say Y if you want to be able to read files from and
752 write files to an OS/2 HPFS partition on your hard drive. OS/2
753 floppies however are in regular MSDOS format, so you don't need this
754 option in order to be able to read them. Read
755 <file:Documentation/filesystems/hpfs.txt>.
757 To compile this file system support as a module, choose M here: the
758 module will be called hpfs. If unsure, say N.
762 tristate "QNX4 file system support (read only)"
765 This is the file system used by the real-time operating systems
766 QNX 4 and QNX 6 (the latter is also called QNX RTP).
767 Further information is available at <http://www.qnx.com/>.
768 Say Y if you intend to mount QNX hard disks or floppies.
769 Unless you say Y to "QNX4FS read-write support" below, you will
770 only be able to read these file systems.
772 To compile this file system support as a module, choose M here: the
773 module will be called qnx4.
775 If you don't know whether you need it, then you don't need it:
779 bool "QNX4FS write support (DANGEROUS)"
780 depends on QNX4FS_FS && EXPERIMENTAL && BROKEN
782 Say Y if you want to test write support for QNX4 file systems.
784 It's currently broken, so for now:
788 tristate "ROM file system support"
791 This is a very small read-only file system mainly intended for
792 initial ram disks of installation disks, but it could be used for
793 other read-only media as well. Read
794 <file:Documentation/filesystems/romfs.txt> for details.
796 To compile this file system support as a module, choose M here: the
797 module will be called romfs. Note that the file system of your
798 root partition (the one containing the directory /) cannot be a
801 If you don't know whether you need it, then you don't need it:
806 tristate "System V/Xenix/V7/Coherent file system support"
809 SCO, Xenix and Coherent are commercial Unix systems for Intel
810 machines, and Version 7 was used on the DEC PDP-11. Saying Y
811 here would allow you to read from their floppies and hard disk
814 If you have floppies or hard disk partitions like that, it is likely
815 that they contain binaries from those other Unix systems; in order
816 to run these binaries, you will want to install linux-abi which is
817 a set of kernel modules that lets you run SCO, Xenix, Wyse,
818 UnixWare, Dell Unix and System V programs under Linux. It is
819 available via FTP (user: ftp) from
820 <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
821 NOTE: that will work only for binaries from Intel-based systems;
822 PDP ones will have to wait until somebody ports Linux to -11 ;-)
824 If you only intend to mount files from some other Unix over the
825 network using NFS, you don't need the System V file system support
826 (but you need NFS file system support obviously).
828 Note that this option is generally not needed for floppies, since a
829 good portable way to transport files and directories between unixes
830 (and even other operating systems) is given by the tar program ("man
831 tar" or preferably "info tar"). Note also that this option has
832 nothing whatsoever to do with the option "System V IPC". Read about
833 the System V file system in
834 <file:Documentation/filesystems/sysv-fs.txt>.
835 Saying Y here will enlarge your kernel by about 27 KB.
837 To compile this as a module, choose M here: the module will be called
840 If you haven't heard about all of this before, it's safe to say N.
844 tristate "UFS file system support (read only)"
847 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
848 OpenBSD and NeXTstep) use a file system called UFS. Some System V
849 Unixes can create and mount hard disk partitions and diskettes using
850 this file system as well. Saying Y here will allow you to read from
851 these partitions; if you also want to write to them, say Y to the
852 experimental "UFS file system write support", below. Please read the
853 file <file:Documentation/filesystems/ufs.txt> for more information.
855 The recently released UFS2 variant (used in FreeBSD 5.x) is
858 Note that this option is generally not needed for floppies, since a
859 good portable way to transport files and directories between unixes
860 (and even other operating systems) is given by the tar program ("man
861 tar" or preferably "info tar").
863 When accessing NeXTstep files, you may need to convert them from the
864 NeXT character set to the Latin1 character set; use the program
865 recode ("info recode") for this purpose.
867 To compile the UFS file system support as a module, choose M here: the
868 module will be called ufs.
870 If you haven't heard about all of this before, it's safe to say N.
873 bool "UFS file system write support (DANGEROUS)"
874 depends on UFS_FS && EXPERIMENTAL
876 Say Y here if you want to try writing to UFS partitions. This is
877 experimental, so you should back up your UFS partitions beforehand.
883 If you are experiencing any problems with the UFS filesystem, say
884 Y here. This will result in _many_ additional debugging messages to be
885 written to the system log.
887 endif # MISC_FILESYSTEMS
889 menuconfig NETWORK_FILESYSTEMS
890 bool "Network File Systems"
894 Say Y here to get to see options for network filesystems and
895 filesystem-related networking code, such as NFS daemon and
896 RPCSEC security modules.
898 This option alone does not add any kernel code.
900 If you say N, all options in this submenu will be skipped and
901 disabled; if unsure, say Y here.
903 if NETWORK_FILESYSTEMS
906 tristate "NFS client support"
910 select NFS_ACL_SUPPORT if NFS_V3_ACL
912 Choose Y here if you want to access files residing on other
913 computers using Sun's Network File System protocol. To compile
914 this file system support as a module, choose M here: the module
917 To mount file systems exported by NFS servers, you also need to
918 install the user space mount.nfs command which can be found in
919 the Linux nfs-utils package, available from http://linux-nfs.org/.
920 Information about using the mount command is available in the
921 mount(8) man page. More detail about the Linux NFS client
922 implementation is available via the nfs(5) man page.
924 Below you can choose which versions of the NFS protocol are
925 available in the kernel to mount NFS servers. Support for NFS
926 version 2 (RFC 1094) is always available when NFS_FS is selected.
928 To configure a system which mounts its root file system via NFS
929 at boot time, say Y here, select "Kernel level IP
930 autoconfiguration" in the NETWORK menu, and select "Root file
931 system on NFS" below. You cannot compile this file system as a
937 bool "NFS client support for NFS version 3"
940 This option enables support for version 3 of the NFS protocol
941 (RFC 1813) in the kernel's NFS client.
946 bool "NFS client support for the NFSv3 ACL protocol extension"
949 Some NFS servers support an auxiliary NFSv3 ACL protocol that
950 Sun added to Solaris but never became an official part of the
951 NFS version 3 protocol. This protocol extension allows
952 applications on NFS clients to manipulate POSIX Access Control
953 Lists on files residing on NFS servers. NFS servers enforce
954 ACLs on local files whether this protocol is available or not.
956 Choose Y here if your NFS server supports the Solaris NFSv3 ACL
957 protocol extension and you want your NFS client to allow
958 applications to access and modify ACLs on files on the server.
960 Most NFS servers don't support the Solaris NFSv3 ACL protocol
961 extension. You can choose N here or specify the "noacl" mount
962 option to prevent your NFS client from trying to use the NFSv3
968 bool "NFS client support for NFS version 4 (EXPERIMENTAL)"
969 depends on NFS_FS && EXPERIMENTAL
970 select RPCSEC_GSS_KRB5
972 This option enables support for version 4 of the NFS protocol
973 (RFC 3530) in the kernel's NFS client.
975 To mount NFS servers using NFSv4, you also need to install user
976 space programs which can be found in the Linux nfs-utils package,
977 available from http://linux-nfs.org/.
982 bool "Root file system on NFS"
983 depends on NFS_FS=y && IP_PNP
985 If you want your system to mount its root file system via NFS,
986 choose Y here. This is common practice for managing systems
987 without local permanent storage. For details, read
988 <file:Documentation/filesystems/nfsroot.txt>.
990 Most people say N here.
993 tristate "NFS server support"
998 select NFS_ACL_SUPPORT if NFSD_V2_ACL
1000 Choose Y here if you want to allow other computers to access
1001 files residing on this system using Sun's Network File System
1002 protocol. To compile the NFS server support as a module,
1003 choose M here: the module will be called nfsd.
1005 You may choose to use a user-space NFS server instead, in which
1006 case you can choose N here.
1008 To export local file systems using NFS, you also need to install
1009 user space programs which can be found in the Linux nfs-utils
1010 package, available from http://linux-nfs.org/. More detail about
1011 the Linux NFS server implementation is available via the
1012 exports(5) man page.
1014 Below you can choose which versions of the NFS protocol are
1015 available to clients mounting the NFS server on this system.
1016 Support for NFS version 2 (RFC 1094) is always available when
1017 CONFIG_NFSD is selected.
1026 bool "NFS server support for NFS version 3"
1029 This option enables support in your system's NFS server for
1030 version 3 of the NFS protocol (RFC 1813).
1035 bool "NFS server support for the NFSv3 ACL protocol extension"
1039 Solaris NFS servers support an auxiliary NFSv3 ACL protocol that
1040 never became an official part of the NFS version 3 protocol.
1041 This protocol extension allows applications on NFS clients to
1042 manipulate POSIX Access Control Lists on files residing on NFS
1043 servers. NFS servers enforce POSIX ACLs on local files whether
1044 this protocol is available or not.
1046 This option enables support in your system's NFS server for the
1047 NFSv3 ACL protocol extension allowing NFS clients to manipulate
1048 POSIX ACLs on files exported by your system's NFS server. NFS
1049 clients which support the Solaris NFSv3 ACL protocol can then
1050 access and modify ACLs on your NFS server.
1052 To store ACLs on your NFS server, you also need to enable ACL-
1053 related CONFIG options for your local file systems of choice.
1058 bool "NFS server support for NFS version 4 (EXPERIMENTAL)"
1059 depends on NFSD && PROC_FS && EXPERIMENTAL
1062 select RPCSEC_GSS_KRB5
1064 This option enables support in your system's NFS server for
1065 version 4 of the NFS protocol (RFC 3530).
1067 To export files using NFSv4, you need to install additional user
1068 space programs which can be found in the Linux nfs-utils package,
1069 available from http://linux-nfs.org/.
1078 depends on NFSD_V3 || NFS_V3
1084 config NFS_ACL_SUPPORT
1090 depends on NFSD || NFS_FS
1099 config SUNRPC_XPRT_RDMA
1101 depends on SUNRPC && INFINIBAND && EXPERIMENTAL
1102 default SUNRPC && INFINIBAND
1104 This option enables an RPC client transport capability that
1105 allows the NFS client to mount servers via an RDMA-enabled
1108 To compile RPC client RDMA transport support as a module,
1109 choose M here: the module will be called xprtrdma.
1113 config SUNRPC_REGISTER_V4
1114 bool "Register local RPC services via rpcbind v4 (EXPERIMENTAL)"
1115 depends on SUNRPC && EXPERIMENTAL
1118 Sun added support for registering RPC services at an IPv6
1119 address by creating two new versions of the rpcbind protocol
1122 This option enables support in the kernel RPC server for
1123 registering kernel RPC services via version 4 of the rpcbind
1124 protocol. If you enable this option, you must run a portmapper
1125 daemon that supports rpcbind protocol version 4.
1127 Serving NFS over IPv6 from knfsd (the kernel's NFS server)
1128 requires that you enable this option and use a portmapper that
1129 supports rpcbind version 4.
1131 If unsure, say N to get traditional behavior (register kernel
1132 RPC services using only rpcbind version 2). Distributions
1133 using the legacy Linux portmapper daemon must say N here.
1135 config RPCSEC_GSS_KRB5
1136 tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
1137 depends on SUNRPC && EXPERIMENTAL
1144 Choose Y here to enable Secure RPC using the Kerberos version 5
1145 GSS-API mechanism (RFC 1964).
1147 Secure RPC calls with Kerberos require an auxiliary user-space
1148 daemon which may be found in the Linux nfs-utils package
1149 available from http://linux-nfs.org/. In addition, user-space
1150 Kerberos support should be installed.
1154 config RPCSEC_GSS_SPKM3
1155 tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
1156 depends on SUNRPC && EXPERIMENTAL
1164 Choose Y here to enable Secure RPC using the SPKM3 public key
1165 GSS-API mechansim (RFC 2025).
1167 Secure RPC calls with SPKM3 require an auxiliary userspace
1168 daemon which may be found in the Linux nfs-utils package
1169 available from http://linux-nfs.org/.
1174 tristate "SMB file system support (OBSOLETE, please use CIFS)"
1178 SMB (Server Message Block) is the protocol Windows for Workgroups
1179 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
1180 files and printers over local networks. Saying Y here allows you to
1181 mount their file systems (often called "shares" in this context) and
1182 access them just like any other Unix directory. Currently, this
1183 works only if the Windows machines use TCP/IP as the underlying
1184 transport protocol, and not NetBEUI. For details, read
1185 <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
1186 available from <http://www.tldp.org/docs.html#howto>.
1188 Note: if you just want your box to act as an SMB *server* and make
1189 files and printing services available to Windows clients (which need
1190 to have a TCP/IP stack), you don't need to say Y here; you can use
1191 the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
1194 General information about how to connect Linux, Windows machines and
1195 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1197 To compile the SMB support as a module, choose M here:
1198 the module will be called smbfs. Most people say N, however.
1200 config SMB_NLS_DEFAULT
1201 bool "Use a default NLS"
1204 Enabling this will make smbfs use nls translations by default. You
1205 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
1206 settings and you need to give the default nls for the SMB server as
1207 CONFIG_SMB_NLS_REMOTE.
1209 The nls settings can be changed at mount time, if your smbmount
1210 supports that, using the codepage and iocharset parameters.
1212 smbmount from samba 2.2.0 or later supports this.
1214 config SMB_NLS_REMOTE
1215 string "Default Remote NLS Option"
1216 depends on SMB_NLS_DEFAULT
1219 This setting allows you to specify a default value for which
1220 codepage the server uses. If this field is left blank no
1221 translations will be done by default. The local codepage/charset
1222 default to CONFIG_NLS_DEFAULT.
1224 The nls settings can be changed at mount time, if your smbmount
1225 supports that, using the codepage and iocharset parameters.
1227 smbmount from samba 2.2.0 or later supports this.
1229 source "fs/cifs/Kconfig"
1232 tristate "NCP file system support (to mount NetWare volumes)"
1233 depends on IPX!=n || INET
1235 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
1236 used by Novell NetWare clients to talk to file servers. It is to
1237 IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
1238 to mount NetWare file server volumes and to access them just like
1239 any other Unix directory. For details, please read the file
1240 <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
1241 the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
1243 You do not have to say Y here if you want your Linux box to act as a
1244 file *server* for Novell NetWare clients.
1246 General information about how to connect Linux, Windows machines and
1247 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1249 To compile this as a module, choose M here: the module will be called
1250 ncpfs. Say N unless you are connected to a Novell network.
1252 source "fs/ncpfs/Kconfig"
1255 tristate "Coda file system support (advanced network fs)"
1258 Coda is an advanced network file system, similar to NFS in that it
1259 enables you to mount file systems of a remote server and access them
1260 with regular Unix commands as if they were sitting on your hard
1261 disk. Coda has several advantages over NFS: support for
1262 disconnected operation (e.g. for laptops), read/write server
1263 replication, security model for authentication and encryption,
1264 persistent client caches and write back caching.
1266 If you say Y here, your Linux box will be able to act as a Coda
1267 *client*. You will need user level code as well, both for the
1268 client and server. Servers are currently user level, i.e. they need
1269 no kernel support. Please read
1270 <file:Documentation/filesystems/coda.txt> and check out the Coda
1271 home page <http://www.coda.cs.cmu.edu/>.
1273 To compile the coda client support as a module, choose M here: the
1274 module will be called coda.
1277 tristate "Andrew File System support (AFS) (EXPERIMENTAL)"
1278 depends on INET && EXPERIMENTAL
1281 If you say Y here, you will get an experimental Andrew File System
1282 driver. It currently only supports unsecured read-only AFS access.
1284 See <file:Documentation/filesystems/afs.txt> for more information.
1289 bool "AFS dynamic debugging"
1292 Say Y here to make runtime controllable debugging messages appear.
1294 See <file:Documentation/filesystems/afs.txt> for more information.
1299 tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
1300 depends on INET && NET_9P && EXPERIMENTAL
1302 If you say Y here, you will get experimental support for
1303 Plan 9 resource sharing via the 9P2000 protocol.
1305 See <http://v9fs.sf.net> for more information.
1309 endif # NETWORK_FILESYSTEMS
1312 menu "Partition Types"
1314 source "fs/partitions/Kconfig"
1319 source "fs/nls/Kconfig"
1320 source "fs/dlm/Kconfig"