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"
126 source "fs/isofs/Kconfig"
127 source "fs/udf/Kconfig"
133 menu "DOS/FAT/NT Filesystems"
139 If you want to use one of the FAT-based file systems (the MS-DOS and
140 VFAT (Windows 95) file systems), then you must say Y or M here
141 to include FAT support. You will then be able to mount partitions or
142 diskettes with FAT-based file systems and transparently access the
143 files on them, i.e. MSDOS files will look and behave just like all
146 This FAT support is not a file system in itself, it only provides
147 the foundation for the other file systems. You will have to say Y or
148 M to at least one of "MSDOS fs support" or "VFAT fs support" in
149 order to make use of it.
151 Another way to read and write MSDOS floppies and hard drive
152 partitions from within Linux (but not transparently) is with the
153 mtools ("man mtools") program suite. You don't need to say Y here in
156 If you need to move large files on floppies between a DOS and a
157 Linux box, say Y here, mount the floppy under Linux with an MSDOS
158 file system and use GNU tar's M option. GNU tar is a program
159 available for Unix and DOS ("man tar" or "info tar").
161 The FAT support will enlarge your kernel by about 37 KB. If unsure,
164 To compile this as a module, choose M here: the module will be called
165 fat. Note that if you compile the FAT support as a module, you
166 cannot compile any of the FAT-based file systems into the kernel
167 -- they will have to be modules as well.
170 tristate "MSDOS fs support"
173 This allows you to mount MSDOS partitions of your hard drive (unless
174 they are compressed; to access compressed MSDOS partitions under
175 Linux, you can either use the DOS emulator DOSEMU, described in the
176 DOSEMU-HOWTO, available from
177 <http://www.tldp.org/docs.html#howto>, or try dmsdosfs in
178 <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you
179 intend to use dosemu with a non-compressed MSDOS partition, say Y
180 here) and MSDOS floppies. This means that file access becomes
181 transparent, i.e. the MSDOS files look and behave just like all
184 If you have Windows 95 or Windows NT installed on your MSDOS
185 partitions, you should use the VFAT file system (say Y to "VFAT fs
186 support" below), or you will not be able to see the long filenames
187 generated by Windows 95 / Windows NT.
189 This option will enlarge your kernel by about 7 KB. If unsure,
190 answer Y. This will only work if you said Y to "DOS FAT fs support"
191 as well. To compile this as a module, choose M here: the module will
195 tristate "VFAT (Windows-95) fs support"
198 This option provides support for normal Windows file systems with
199 long filenames. That includes non-compressed FAT-based file systems
200 used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
201 programs from the mtools package.
203 The VFAT support enlarges your kernel by about 10 KB and it only
204 works if you said Y to the "DOS FAT fs support" above. Please read
205 the file <file:Documentation/filesystems/vfat.txt> for details. If
208 To compile this as a module, choose M here: the module will be called
211 config FAT_DEFAULT_CODEPAGE
212 int "Default codepage for FAT"
213 depends on MSDOS_FS || VFAT_FS
216 This option should be set to the codepage of your FAT filesystems.
217 It can be overridden with the "codepage" mount option.
218 See <file:Documentation/filesystems/vfat.txt> for more information.
220 config FAT_DEFAULT_IOCHARSET
221 string "Default iocharset for FAT"
225 Set this to the default input/output character set you'd
226 like FAT to use. It should probably match the character set
227 that most of your FAT filesystems use, and can be overridden
228 with the "iocharset" mount option for FAT filesystems.
229 Note that "utf8" is not recommended for FAT filesystems.
230 If unsure, you shouldn't set "utf8" here.
231 See <file:Documentation/filesystems/vfat.txt> for more information.
234 tristate "NTFS file system support"
237 NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003.
239 Saying Y or M here enables read support. There is partial, but
240 safe, write support available. For write support you must also
241 say Y to "NTFS write support" below.
243 There are also a number of user-space tools available, called
244 ntfsprogs. These include ntfsundelete and ntfsresize, that work
245 without NTFS support enabled in the kernel.
247 This is a rewrite from scratch of Linux NTFS support and replaced
248 the old NTFS code starting with Linux 2.5.11. A backport to
249 the Linux 2.4 kernel series is separately available as a patch
250 from the project web site.
252 For more information see <file:Documentation/filesystems/ntfs.txt>
253 and <http://www.linux-ntfs.org/>.
255 To compile this file system support as a module, choose M here: the
256 module will be called ntfs.
258 If you are not using Windows NT, 2000, XP or 2003 in addition to
259 Linux on your computer it is safe to say N.
262 bool "NTFS debugging support"
265 If you are experiencing any problems with the NTFS file system, say
266 Y here. This will result in additional consistency checks to be
267 performed by the driver as well as additional debugging messages to
268 be written to the system log. Note that debugging messages are
269 disabled by default. To enable them, supply the option debug_msgs=1
270 at the kernel command line when booting the kernel or as an option
271 to insmod when loading the ntfs module. Once the driver is active,
272 you can enable debugging messages by doing (as root):
273 echo 1 > /proc/sys/fs/ntfs-debug
274 Replacing the "1" with "0" would disable debug messages.
276 If you leave debugging messages disabled, this results in little
277 overhead, but enabling debug messages results in very significant
278 slowdown of the system.
280 When reporting bugs, please try to have available a full dump of
281 debugging messages while the misbehaviour was occurring.
284 bool "NTFS write support"
287 This enables the partial, but safe, write support in the NTFS driver.
289 The only supported operation is overwriting existing files, without
290 changing the file length. No file or directory creation, deletion or
291 renaming is possible. Note only non-resident files can be written to
292 so you may find that some very small files (<500 bytes or so) cannot
295 While we cannot guarantee that it will not damage any data, we have
296 so far not received a single report where the driver would have
297 damaged someones data so we assume it is perfectly safe to use.
299 Note: While write support is safe in this version (a rewrite from
300 scratch of the NTFS support), it should be noted that the old NTFS
301 write support, included in Linux 2.5.10 and before (since 1997),
304 This is currently useful with TopologiLinux. TopologiLinux is run
305 on top of any DOS/Microsoft Windows system without partitioning your
306 hard disk. Unlike other Linux distributions TopologiLinux does not
307 need its own partition. For more information see
308 <http://topologi-linux.sourceforge.net/>
310 It is perfectly safe to say N here.
315 menu "Pseudo filesystems"
317 source "fs/proc/Kconfig"
320 bool "sysfs file system support" if EMBEDDED
323 The sysfs filesystem is a virtual filesystem that the kernel uses to
324 export internal kernel objects, their attributes, and their
325 relationships to one another.
327 Users can use sysfs to ascertain useful information about the running
328 kernel, such as the devices the kernel has discovered on each bus and
329 which driver each is bound to. sysfs can also be used to tune devices
330 and other kernel subsystems.
332 Some system agents rely on the information in sysfs to operate.
333 /sbin/hotplug uses device and object attributes in sysfs to assist in
334 delegating policy decisions, like persistently naming devices.
336 sysfs is currently used by the block subsystem to mount the root
337 partition. If sysfs is disabled you must specify the boot device on
338 the kernel boot command line via its major and minor numbers. For
339 example, "root=03:01" for /dev/hda1.
341 Designers of embedded systems may wish to say N here to conserve space.
344 bool "Virtual memory file system support (former shm fs)"
346 Tmpfs is a file system which keeps all files in virtual memory.
348 Everything in tmpfs is temporary in the sense that no files will be
349 created on your hard drive. The files live in memory and swap
350 space. If you unmount a tmpfs instance, everything stored therein is
353 See <file:Documentation/filesystems/tmpfs.txt> for details.
355 config TMPFS_POSIX_ACL
356 bool "Tmpfs POSIX Access Control Lists"
360 POSIX Access Control Lists (ACLs) support permissions for users and
361 groups beyond the owner/group/world scheme.
363 To learn more about Access Control Lists, visit the POSIX ACLs for
364 Linux website <http://acl.bestbits.at/>.
366 If you don't know what Access Control Lists are, say N.
369 bool "HugeTLB file system support"
370 depends on X86 || IA64 || PPC64 || SPARC64 || (SUPERH && MMU) || \
371 (S390 && 64BIT) || BROKEN
373 hugetlbfs is a filesystem backing for HugeTLB pages, based on
374 ramfs. For architectures that support it, say Y here and read
375 <file:Documentation/vm/hugetlbpage.txt> for details.
383 tristate "Userspace-driven configuration filesystem"
386 configfs is a ram-based filesystem that provides the converse
387 of sysfs's functionality. Where sysfs is a filesystem-based
388 view of kernel objects, configfs is a filesystem-based manager
389 of kernel objects, or config_items.
391 Both sysfs and configfs can and should exist together on the
392 same system. One is not a replacement for the other.
396 menuconfig MISC_FILESYSTEMS
397 bool "Miscellaneous filesystems"
400 Say Y here to get to see options for various miscellaneous
401 filesystems, such as filesystems that came from other
404 This option alone does not add any kernel code.
406 If you say N, all options in this submenu will be skipped and
407 disabled; if unsure, say Y here.
412 tristate "ADFS file system support (EXPERIMENTAL)"
413 depends on BLOCK && EXPERIMENTAL
415 The Acorn Disc Filing System is the standard file system of the
416 RiscOS operating system which runs on Acorn's ARM-based Risc PC
417 systems and the Acorn Archimedes range of machines. If you say Y
418 here, Linux will be able to read from ADFS partitions on hard drives
419 and from ADFS-formatted floppy discs. If you also want to be able to
420 write to those devices, say Y to "ADFS write support" below.
422 The ADFS partition should be the first partition (i.e.,
423 /dev/[hs]d?1) on each of your drives. Please read the file
424 <file:Documentation/filesystems/adfs.txt> for further details.
426 To compile this code as a module, choose M here: the module will be
432 bool "ADFS write support (DANGEROUS)"
435 If you say Y here, you will be able to write to ADFS partitions on
436 hard drives and ADFS-formatted floppy disks. This is experimental
437 codes, so if you're unsure, say N.
440 tristate "Amiga FFS file system support (EXPERIMENTAL)"
441 depends on BLOCK && EXPERIMENTAL
443 The Fast File System (FFS) is the common file system used on hard
444 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
445 if you want to be able to read and write files from and to an Amiga
446 FFS partition on your hard drive. Amiga floppies however cannot be
447 read with this driver due to an incompatibility of the floppy
448 controller used in an Amiga and the standard floppy controller in
449 PCs and workstations. Read <file:Documentation/filesystems/affs.txt>
450 and <file:fs/affs/Changes>.
452 With this driver you can also mount disk files used by Bernd
453 Schmidt's Un*X Amiga Emulator
454 (<http://www.freiburg.linux.de/~uae/>).
455 If you want to do this, you will also need to say Y or M to "Loop
456 device support", above.
458 To compile this file system support as a module, choose M here: the
459 module will be called affs. If unsure, say N.
462 tristate "eCrypt filesystem layer support (EXPERIMENTAL)"
463 depends on EXPERIMENTAL && KEYS && CRYPTO && NET
465 Encrypted filesystem that operates on the VFS layer. See
466 <file:Documentation/filesystems/ecryptfs.txt> to learn more about
467 eCryptfs. Userspace components are required and can be
468 obtained from <http://ecryptfs.sf.net>.
470 To compile this file system support as a module, choose M here: the
471 module will be called ecryptfs.
474 tristate "Apple Macintosh file system support (EXPERIMENTAL)"
475 depends on BLOCK && EXPERIMENTAL
478 If you say Y here, you will be able to mount Macintosh-formatted
479 floppy disks and hard drive partitions with full read-write access.
480 Please read <file:Documentation/filesystems/hfs.txt> to learn about
481 the available mount options.
483 To compile this file system support as a module, choose M here: the
484 module will be called hfs.
487 tristate "Apple Extended HFS file system support"
492 If you say Y here, you will be able to mount extended format
493 Macintosh-formatted hard drive partitions with full read-write access.
495 This file system is often called HFS+ and was introduced with
496 MacOS 8. It includes all Mac specific filesystem data such as
497 data forks and creator codes, but it also has several UNIX
498 style features such as file ownership and permissions.
501 tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)"
502 depends on BLOCK && EXPERIMENTAL
505 The BeOS File System (BeFS) is the native file system of Be, Inc's
506 BeOS. Notable features include support for arbitrary attributes
507 on files and directories, and database-like indices on selected
508 attributes. (Also note that this driver doesn't make those features
509 available at this time). It is a 64 bit filesystem, so it supports
510 extremely large volumes and files.
512 If you use this filesystem, you should also say Y to at least one
513 of the NLS (native language support) options below.
515 If you don't know what this is about, say N.
517 To compile this as a module, choose M here: the module will be
524 If you say Y here, you can use the 'debug' mount option to enable
525 debugging output from the driver.
528 tristate "BFS file system support (EXPERIMENTAL)"
529 depends on BLOCK && EXPERIMENTAL
531 Boot File System (BFS) is a file system used under SCO UnixWare to
532 allow the bootloader access to the kernel image and other important
533 files during the boot process. It is usually mounted under /stand
534 and corresponds to the slice marked as "STAND" in the UnixWare
535 partition. You should say Y if you want to read or write the files
536 on your /stand slice from within Linux. You then also need to say Y
537 to "UnixWare slices support", below. More information about the BFS
538 file system is contained in the file
539 <file:Documentation/filesystems/bfs.txt>.
541 If you don't know what this is about, say N.
543 To compile this as a module, choose M here: the module will be called
544 bfs. Note that the file system of your root partition (the one
545 containing the directory /) cannot be compiled as a module.
550 tristate "EFS file system support (read only) (EXPERIMENTAL)"
551 depends on BLOCK && EXPERIMENTAL
553 EFS is an older file system used for non-ISO9660 CD-ROMs and hard
554 disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
555 uses the XFS file system for hard disk partitions however).
557 This implementation only offers read-only access. If you don't know
558 what all this is about, it's safe to say N. For more information
559 about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
561 To compile the EFS file system support as a module, choose M here: the
562 module will be called efs.
564 source "fs/jffs2/Kconfig"
565 # UBIFS File system configuration
566 source "fs/ubifs/Kconfig"
569 tristate "Compressed ROM file system support (cramfs)"
573 Saying Y here includes support for CramFs (Compressed ROM File
574 System). CramFs is designed to be a simple, small, and compressed
575 file system for ROM based embedded systems. CramFs is read-only,
576 limited to 256MB file systems (with 16MB files), and doesn't support
577 16/32 bits uid/gid, hard links and timestamps.
579 See <file:Documentation/filesystems/cramfs.txt> and
580 <file:fs/cramfs/README> for further information.
582 To compile this as a module, choose M here: the module will be called
583 cramfs. Note that the root file system (the one containing the
584 directory /) cannot be compiled as a module.
589 tristate "SquashFS 4.0 - Squashed file system support"
593 Saying Y here includes support for SquashFS 4.0 (a Compressed
594 Read-Only File System). Squashfs is a highly compressed read-only
595 filesystem for Linux. It uses zlib compression to compress both
596 files, inodes and directories. Inodes in the system are very small
597 and all blocks are packed to minimise data overhead. Block sizes
598 greater than 4K are supported up to a maximum of 1 Mbytes (default
599 block size 128K). SquashFS 4.0 supports 64 bit filesystems and files
600 (larger than 4GB), full uid/gid information, hard links and
603 Squashfs is intended for general read-only filesystem use, for
604 archival use (i.e. in cases where a .tar.gz file may be used), and in
605 embedded systems where low overhead is needed. Further information
606 and tools are available from http://squashfs.sourceforge.net.
608 If you want to compile this as a module ( = code which can be
609 inserted in and removed from the running kernel whenever you want),
610 say M here and read <file:Documentation/modules.txt>. The module
611 will be called squashfs. Note that the root file system (the one
612 containing the directory /) cannot be compiled as a module.
616 config SQUASHFS_EMBEDDED
618 bool "Additional option for memory-constrained systems"
622 Saying Y here allows you to specify cache size.
626 config SQUASHFS_FRAGMENT_CACHE_SIZE
627 int "Number of fragments cached" if SQUASHFS_EMBEDDED
631 By default SquashFS caches the last 3 fragments read from
632 the filesystem. Increasing this amount may mean SquashFS
633 has to re-read fragments less often from disk, at the expense
634 of extra system memory. Decreasing this amount will mean
635 SquashFS uses less memory at the expense of extra reads from disk.
637 Note there must be at least one cached fragment. Anything
638 much more than three will probably not make much difference.
641 tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
644 FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
645 file system format. VERITAS VxFS(TM) is the standard file system
646 of SCO UnixWare (and possibly others) and optionally available
647 for Sunsoft Solaris, HP-UX and many other operating systems.
648 Currently only readonly access is supported.
650 NOTE: the file system type as used by mount(1), mount(2) and
651 fstab(5) is 'vxfs' as it describes the file system format, not
654 To compile this as a module, choose M here: the module will be
655 called freevxfs. If unsure, say N.
658 tristate "Minix file system support"
661 Minix is a simple operating system used in many classes about OS's.
662 The minix file system (method to organize files on a hard disk
663 partition or a floppy disk) was the original file system for Linux,
664 but has been superseded by the second extended file system ext2fs.
665 You don't want to use the minix file system on your hard disk
666 because of certain built-in restrictions, but it is sometimes found
667 on older Linux floppy disks. This option will enlarge your kernel
668 by about 28 KB. If unsure, say N.
670 To compile this file system support as a module, choose M here: the
671 module will be called minix. Note that the file system of your root
672 partition (the one containing the directory /) cannot be compiled as
676 tristate "SonicBlue Optimized MPEG File System support"
680 This is the proprietary file system used by the Rio Karma music
681 player and ReplayTV DVR. Despite the name, this filesystem is not
682 more efficient than a standard FS for MPEG files, in fact likely
683 the opposite is true. Say Y if you have either of these devices
684 and wish to mount its disk.
686 To compile this file system support as a module, choose M here: the
687 module will be called omfs. If unsure, say N.
690 tristate "OS/2 HPFS file system support"
693 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
694 is the file system used for organizing files on OS/2 hard disk
695 partitions. Say Y if you want to be able to read files from and
696 write files to an OS/2 HPFS partition on your hard drive. OS/2
697 floppies however are in regular MSDOS format, so you don't need this
698 option in order to be able to read them. Read
699 <file:Documentation/filesystems/hpfs.txt>.
701 To compile this file system support as a module, choose M here: the
702 module will be called hpfs. If unsure, say N.
706 tristate "QNX4 file system support (read only)"
709 This is the file system used by the real-time operating systems
710 QNX 4 and QNX 6 (the latter is also called QNX RTP).
711 Further information is available at <http://www.qnx.com/>.
712 Say Y if you intend to mount QNX hard disks or floppies.
713 Unless you say Y to "QNX4FS read-write support" below, you will
714 only be able to read these file systems.
716 To compile this file system support as a module, choose M here: the
717 module will be called qnx4.
719 If you don't know whether you need it, then you don't need it:
723 bool "QNX4FS write support (DANGEROUS)"
724 depends on QNX4FS_FS && EXPERIMENTAL && BROKEN
726 Say Y if you want to test write support for QNX4 file systems.
728 It's currently broken, so for now:
732 tristate "ROM file system support"
735 This is a very small read-only file system mainly intended for
736 initial ram disks of installation disks, but it could be used for
737 other read-only media as well. Read
738 <file:Documentation/filesystems/romfs.txt> for details.
740 To compile this file system support as a module, choose M here: the
741 module will be called romfs. Note that the file system of your
742 root partition (the one containing the directory /) cannot be a
745 If you don't know whether you need it, then you don't need it:
750 tristate "System V/Xenix/V7/Coherent file system support"
753 SCO, Xenix and Coherent are commercial Unix systems for Intel
754 machines, and Version 7 was used on the DEC PDP-11. Saying Y
755 here would allow you to read from their floppies and hard disk
758 If you have floppies or hard disk partitions like that, it is likely
759 that they contain binaries from those other Unix systems; in order
760 to run these binaries, you will want to install linux-abi which is
761 a set of kernel modules that lets you run SCO, Xenix, Wyse,
762 UnixWare, Dell Unix and System V programs under Linux. It is
763 available via FTP (user: ftp) from
764 <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
765 NOTE: that will work only for binaries from Intel-based systems;
766 PDP ones will have to wait until somebody ports Linux to -11 ;-)
768 If you only intend to mount files from some other Unix over the
769 network using NFS, you don't need the System V file system support
770 (but you need NFS file system support obviously).
772 Note that this option is generally not needed for floppies, since a
773 good portable way to transport files and directories between unixes
774 (and even other operating systems) is given by the tar program ("man
775 tar" or preferably "info tar"). Note also that this option has
776 nothing whatsoever to do with the option "System V IPC". Read about
777 the System V file system in
778 <file:Documentation/filesystems/sysv-fs.txt>.
779 Saying Y here will enlarge your kernel by about 27 KB.
781 To compile this as a module, choose M here: the module will be called
784 If you haven't heard about all of this before, it's safe to say N.
788 tristate "UFS file system support (read only)"
791 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
792 OpenBSD and NeXTstep) use a file system called UFS. Some System V
793 Unixes can create and mount hard disk partitions and diskettes using
794 this file system as well. Saying Y here will allow you to read from
795 these partitions; if you also want to write to them, say Y to the
796 experimental "UFS file system write support", below. Please read the
797 file <file:Documentation/filesystems/ufs.txt> for more information.
799 The recently released UFS2 variant (used in FreeBSD 5.x) is
802 Note that this option is generally not needed for floppies, since a
803 good portable way to transport files and directories between unixes
804 (and even other operating systems) is given by the tar program ("man
805 tar" or preferably "info tar").
807 When accessing NeXTstep files, you may need to convert them from the
808 NeXT character set to the Latin1 character set; use the program
809 recode ("info recode") for this purpose.
811 To compile the UFS file system support as a module, choose M here: the
812 module will be called ufs.
814 If you haven't heard about all of this before, it's safe to say N.
817 bool "UFS file system write support (DANGEROUS)"
818 depends on UFS_FS && EXPERIMENTAL
820 Say Y here if you want to try writing to UFS partitions. This is
821 experimental, so you should back up your UFS partitions beforehand.
827 If you are experiencing any problems with the UFS filesystem, say
828 Y here. This will result in _many_ additional debugging messages to be
829 written to the system log.
831 endif # MISC_FILESYSTEMS
833 menuconfig NETWORK_FILESYSTEMS
834 bool "Network File Systems"
838 Say Y here to get to see options for network filesystems and
839 filesystem-related networking code, such as NFS daemon and
840 RPCSEC security modules.
842 This option alone does not add any kernel code.
844 If you say N, all options in this submenu will be skipped and
845 disabled; if unsure, say Y here.
847 if NETWORK_FILESYSTEMS
850 tristate "NFS client support"
854 select NFS_ACL_SUPPORT if NFS_V3_ACL
856 Choose Y here if you want to access files residing on other
857 computers using Sun's Network File System protocol. To compile
858 this file system support as a module, choose M here: the module
861 To mount file systems exported by NFS servers, you also need to
862 install the user space mount.nfs command which can be found in
863 the Linux nfs-utils package, available from http://linux-nfs.org/.
864 Information about using the mount command is available in the
865 mount(8) man page. More detail about the Linux NFS client
866 implementation is available via the nfs(5) man page.
868 Below you can choose which versions of the NFS protocol are
869 available in the kernel to mount NFS servers. Support for NFS
870 version 2 (RFC 1094) is always available when NFS_FS is selected.
872 To configure a system which mounts its root file system via NFS
873 at boot time, say Y here, select "Kernel level IP
874 autoconfiguration" in the NETWORK menu, and select "Root file
875 system on NFS" below. You cannot compile this file system as a
881 bool "NFS client support for NFS version 3"
884 This option enables support for version 3 of the NFS protocol
885 (RFC 1813) in the kernel's NFS client.
890 bool "NFS client support for the NFSv3 ACL protocol extension"
893 Some NFS servers support an auxiliary NFSv3 ACL protocol that
894 Sun added to Solaris but never became an official part of the
895 NFS version 3 protocol. This protocol extension allows
896 applications on NFS clients to manipulate POSIX Access Control
897 Lists on files residing on NFS servers. NFS servers enforce
898 ACLs on local files whether this protocol is available or not.
900 Choose Y here if your NFS server supports the Solaris NFSv3 ACL
901 protocol extension and you want your NFS client to allow
902 applications to access and modify ACLs on files on the server.
904 Most NFS servers don't support the Solaris NFSv3 ACL protocol
905 extension. You can choose N here or specify the "noacl" mount
906 option to prevent your NFS client from trying to use the NFSv3
912 bool "NFS client support for NFS version 4 (EXPERIMENTAL)"
913 depends on NFS_FS && EXPERIMENTAL
914 select RPCSEC_GSS_KRB5
916 This option enables support for version 4 of the NFS protocol
917 (RFC 3530) in the kernel's NFS client.
919 To mount NFS servers using NFSv4, you also need to install user
920 space programs which can be found in the Linux nfs-utils package,
921 available from http://linux-nfs.org/.
926 bool "Root file system on NFS"
927 depends on NFS_FS=y && IP_PNP
929 If you want your system to mount its root file system via NFS,
930 choose Y here. This is common practice for managing systems
931 without local permanent storage. For details, read
932 <file:Documentation/filesystems/nfsroot.txt>.
934 Most people say N here.
937 tristate "NFS server support"
942 select NFS_ACL_SUPPORT if NFSD_V2_ACL
944 Choose Y here if you want to allow other computers to access
945 files residing on this system using Sun's Network File System
946 protocol. To compile the NFS server support as a module,
947 choose M here: the module will be called nfsd.
949 You may choose to use a user-space NFS server instead, in which
950 case you can choose N here.
952 To export local file systems using NFS, you also need to install
953 user space programs which can be found in the Linux nfs-utils
954 package, available from http://linux-nfs.org/. More detail about
955 the Linux NFS server implementation is available via the
958 Below you can choose which versions of the NFS protocol are
959 available to clients mounting the NFS server on this system.
960 Support for NFS version 2 (RFC 1094) is always available when
961 CONFIG_NFSD is selected.
970 bool "NFS server support for NFS version 3"
973 This option enables support in your system's NFS server for
974 version 3 of the NFS protocol (RFC 1813).
979 bool "NFS server support for the NFSv3 ACL protocol extension"
983 Solaris NFS servers support an auxiliary NFSv3 ACL protocol that
984 never became an official part of the NFS version 3 protocol.
985 This protocol extension allows applications on NFS clients to
986 manipulate POSIX Access Control Lists on files residing on NFS
987 servers. NFS servers enforce POSIX ACLs on local files whether
988 this protocol is available or not.
990 This option enables support in your system's NFS server for the
991 NFSv3 ACL protocol extension allowing NFS clients to manipulate
992 POSIX ACLs on files exported by your system's NFS server. NFS
993 clients which support the Solaris NFSv3 ACL protocol can then
994 access and modify ACLs on your NFS server.
996 To store ACLs on your NFS server, you also need to enable ACL-
997 related CONFIG options for your local file systems of choice.
1002 bool "NFS server support for NFS version 4 (EXPERIMENTAL)"
1003 depends on NFSD && PROC_FS && EXPERIMENTAL
1006 select RPCSEC_GSS_KRB5
1008 This option enables support in your system's NFS server for
1009 version 4 of the NFS protocol (RFC 3530).
1011 To export files using NFSv4, you need to install additional user
1012 space programs which can be found in the Linux nfs-utils package,
1013 available from http://linux-nfs.org/.
1022 depends on NFSD_V3 || NFS_V3
1028 config NFS_ACL_SUPPORT
1034 depends on NFSD || NFS_FS
1043 config SUNRPC_XPRT_RDMA
1045 depends on SUNRPC && INFINIBAND && EXPERIMENTAL
1046 default SUNRPC && INFINIBAND
1048 This option enables an RPC client transport capability that
1049 allows the NFS client to mount servers via an RDMA-enabled
1052 To compile RPC client RDMA transport support as a module,
1053 choose M here: the module will be called xprtrdma.
1057 config SUNRPC_REGISTER_V4
1058 bool "Register local RPC services via rpcbind v4 (EXPERIMENTAL)"
1059 depends on SUNRPC && EXPERIMENTAL
1062 Sun added support for registering RPC services at an IPv6
1063 address by creating two new versions of the rpcbind protocol
1066 This option enables support in the kernel RPC server for
1067 registering kernel RPC services via version 4 of the rpcbind
1068 protocol. If you enable this option, you must run a portmapper
1069 daemon that supports rpcbind protocol version 4.
1071 Serving NFS over IPv6 from knfsd (the kernel's NFS server)
1072 requires that you enable this option and use a portmapper that
1073 supports rpcbind version 4.
1075 If unsure, say N to get traditional behavior (register kernel
1076 RPC services using only rpcbind version 2). Distributions
1077 using the legacy Linux portmapper daemon must say N here.
1079 config RPCSEC_GSS_KRB5
1080 tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
1081 depends on SUNRPC && EXPERIMENTAL
1088 Choose Y here to enable Secure RPC using the Kerberos version 5
1089 GSS-API mechanism (RFC 1964).
1091 Secure RPC calls with Kerberos require an auxiliary user-space
1092 daemon which may be found in the Linux nfs-utils package
1093 available from http://linux-nfs.org/. In addition, user-space
1094 Kerberos support should be installed.
1098 config RPCSEC_GSS_SPKM3
1099 tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
1100 depends on SUNRPC && EXPERIMENTAL
1108 Choose Y here to enable Secure RPC using the SPKM3 public key
1109 GSS-API mechansim (RFC 2025).
1111 Secure RPC calls with SPKM3 require an auxiliary userspace
1112 daemon which may be found in the Linux nfs-utils package
1113 available from http://linux-nfs.org/.
1118 tristate "SMB file system support (OBSOLETE, please use CIFS)"
1122 SMB (Server Message Block) is the protocol Windows for Workgroups
1123 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
1124 files and printers over local networks. Saying Y here allows you to
1125 mount their file systems (often called "shares" in this context) and
1126 access them just like any other Unix directory. Currently, this
1127 works only if the Windows machines use TCP/IP as the underlying
1128 transport protocol, and not NetBEUI. For details, read
1129 <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
1130 available from <http://www.tldp.org/docs.html#howto>.
1132 Note: if you just want your box to act as an SMB *server* and make
1133 files and printing services available to Windows clients (which need
1134 to have a TCP/IP stack), you don't need to say Y here; you can use
1135 the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
1138 General information about how to connect Linux, Windows machines and
1139 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1141 To compile the SMB support as a module, choose M here:
1142 the module will be called smbfs. Most people say N, however.
1144 config SMB_NLS_DEFAULT
1145 bool "Use a default NLS"
1148 Enabling this will make smbfs use nls translations by default. You
1149 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
1150 settings and you need to give the default nls for the SMB server as
1151 CONFIG_SMB_NLS_REMOTE.
1153 The nls settings can be changed at mount time, if your smbmount
1154 supports that, using the codepage and iocharset parameters.
1156 smbmount from samba 2.2.0 or later supports this.
1158 config SMB_NLS_REMOTE
1159 string "Default Remote NLS Option"
1160 depends on SMB_NLS_DEFAULT
1163 This setting allows you to specify a default value for which
1164 codepage the server uses. If this field is left blank no
1165 translations will be done by default. The local codepage/charset
1166 default to CONFIG_NLS_DEFAULT.
1168 The nls settings can be changed at mount time, if your smbmount
1169 supports that, using the codepage and iocharset parameters.
1171 smbmount from samba 2.2.0 or later supports this.
1173 source "fs/cifs/Kconfig"
1176 tristate "NCP file system support (to mount NetWare volumes)"
1177 depends on IPX!=n || INET
1179 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
1180 used by Novell NetWare clients to talk to file servers. It is to
1181 IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
1182 to mount NetWare file server volumes and to access them just like
1183 any other Unix directory. For details, please read the file
1184 <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
1185 the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
1187 You do not have to say Y here if you want your Linux box to act as a
1188 file *server* for Novell NetWare clients.
1190 General information about how to connect Linux, Windows machines and
1191 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1193 To compile this as a module, choose M here: the module will be called
1194 ncpfs. Say N unless you are connected to a Novell network.
1196 source "fs/ncpfs/Kconfig"
1199 tristate "Coda file system support (advanced network fs)"
1202 Coda is an advanced network file system, similar to NFS in that it
1203 enables you to mount file systems of a remote server and access them
1204 with regular Unix commands as if they were sitting on your hard
1205 disk. Coda has several advantages over NFS: support for
1206 disconnected operation (e.g. for laptops), read/write server
1207 replication, security model for authentication and encryption,
1208 persistent client caches and write back caching.
1210 If you say Y here, your Linux box will be able to act as a Coda
1211 *client*. You will need user level code as well, both for the
1212 client and server. Servers are currently user level, i.e. they need
1213 no kernel support. Please read
1214 <file:Documentation/filesystems/coda.txt> and check out the Coda
1215 home page <http://www.coda.cs.cmu.edu/>.
1217 To compile the coda client support as a module, choose M here: the
1218 module will be called coda.
1221 tristate "Andrew File System support (AFS) (EXPERIMENTAL)"
1222 depends on INET && EXPERIMENTAL
1225 If you say Y here, you will get an experimental Andrew File System
1226 driver. It currently only supports unsecured read-only AFS access.
1228 See <file:Documentation/filesystems/afs.txt> for more information.
1233 bool "AFS dynamic debugging"
1236 Say Y here to make runtime controllable debugging messages appear.
1238 See <file:Documentation/filesystems/afs.txt> for more information.
1243 tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
1244 depends on INET && NET_9P && EXPERIMENTAL
1246 If you say Y here, you will get experimental support for
1247 Plan 9 resource sharing via the 9P2000 protocol.
1249 See <http://v9fs.sf.net> for more information.
1253 endif # NETWORK_FILESYSTEMS
1256 menu "Partition Types"
1258 source "fs/partitions/Kconfig"
1263 source "fs/nls/Kconfig"
1264 source "fs/dlm/Kconfig"