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"
56 depends on EXT2_FS && MMU
58 Execute in place can be used on memory-backed block devices. If you
59 enable this option, you can select to mount block devices which are
60 capable of this feature without using the page cache.
62 If you do not use a block device that is capable of using this,
68 depends on EXT2_FS_XIP
72 tristate "Ext3 journalling file system support"
75 This is the journaling version of the Second extended file system
76 (often called ext3), the de facto standard Linux file system
77 (method to organize files on a storage device) for hard disks.
79 The journaling code included in this driver means you do not have
80 to run e2fsck (file system checker) on your file systems after a
81 crash. The journal keeps track of any changes that were being made
82 at the time the system crashed, and can ensure that your file system
83 is consistent without the need for a lengthy check.
85 Other than adding the journal to the file system, the on-disk format
86 of ext3 is identical to ext2. It is possible to freely switch
87 between using the ext3 driver and the ext2 driver, as long as the
88 file system has been cleanly unmounted, or e2fsck is run on the file
91 To add a journal on an existing ext2 file system or change the
92 behavior of ext3 file systems, you can use the tune2fs utility ("man
93 tune2fs"). To modify attributes of files and directories on ext3
94 file systems, use chattr ("man chattr"). You need to be using
95 e2fsprogs version 1.20 or later in order to create ext3 journals
96 (available at <http://sourceforge.net/projects/e2fsprogs/>).
98 To compile this file system support as a module, choose M here: the
99 module will be called ext3. Be aware however that the file system
100 of your root partition (the one containing the directory /) cannot
101 be compiled as a module, and so this may be dangerous.
104 bool "Ext3 extended attributes"
108 Extended attributes are name:value pairs associated with inodes by
109 the kernel or by users (see the attr(5) manual page, or visit
110 <http://acl.bestbits.at/> for details).
114 You need this for POSIX ACL support on ext3.
116 config EXT3_FS_POSIX_ACL
117 bool "Ext3 POSIX Access Control Lists"
118 depends on EXT3_FS_XATTR
121 Posix Access Control Lists (ACLs) support permissions for users and
122 groups beyond the owner/group/world scheme.
124 To learn more about Access Control Lists, visit the Posix ACLs for
125 Linux website <http://acl.bestbits.at/>.
127 If you don't know what Access Control Lists are, say N
129 config EXT3_FS_SECURITY
130 bool "Ext3 Security Labels"
131 depends on EXT3_FS_XATTR
133 Security labels support alternative access control models
134 implemented by security modules like SELinux. This option
135 enables an extended attribute handler for file security
136 labels in the ext3 filesystem.
138 If you are not using a security module that requires using
139 extended attributes for file security labels, say N.
144 This is a generic journaling layer for block devices. It is
145 currently used by the ext3 and OCFS2 file systems, but it could
146 also be used to add journal support to other file systems or block
147 devices such as RAID or LVM.
149 If you are using the ext3 or OCFS2 file systems, you need to
150 say Y here. If you are not using ext3 OCFS2 then you will probably
153 To compile this device as a module, choose M here: the module will be
154 called jbd. If you are compiling ext3 or OCFS2 into the kernel,
155 you cannot compile this code as a module.
158 bool "JBD (ext3) debugging support"
161 If you are using the ext3 journaled file system (or potentially any
162 other file system/device using JBD), this option allows you to
163 enable debugging output while the system is running, in order to
164 help track down any problems you are having. By default the
165 debugging output will be turned off.
167 If you select Y here, then you will be able to turn on debugging
168 with "echo N > /proc/sys/fs/jbd-debug", where N is a number between
169 1 and 5, the higher the number, the more debugging output is
170 generated. To turn debugging off again, do
171 "echo 0 > /proc/sys/fs/jbd-debug".
174 # Meta block cache for Extended Attributes (ext2/ext3)
176 depends on EXT2_FS_XATTR || EXT3_FS_XATTR
177 default y if EXT2_FS=y || EXT3_FS=y
178 default m if EXT2_FS=m || EXT3_FS=m
181 tristate "Reiserfs support"
183 Stores not just filenames but the files themselves in a balanced
184 tree. Uses journaling.
186 Balanced trees are more efficient than traditional file system
187 architectural foundations.
189 In general, ReiserFS is as fast as ext2, but is very efficient with
190 large directories and small files. Additional patches are needed
191 for NFS and quotas, please see <http://www.namesys.com/> for links.
193 It is more easily extended to have features currently found in
194 database and keyword search systems than block allocation based file
195 systems are. The next version will be so extended, and will support
196 plugins consistent with our motto ``It takes more than a license to
197 make source code open.''
199 Read <http://www.namesys.com/> to learn more about reiserfs.
201 Sponsored by Threshold Networks, Emusic.com, and Bigstorage.com.
203 If you like it, you can pay us to add new features to it that you
204 need, buy a support contract, or pay us to port it to another OS.
206 config REISERFS_CHECK
207 bool "Enable reiserfs debug mode"
208 depends on REISERFS_FS
210 If you set this to Y, then ReiserFS will perform every check it can
211 possibly imagine of its internal consistency throughout its
212 operation. It will also go substantially slower. More than once we
213 have forgotten that this was on, and then gone despondent over the
214 latest benchmarks.:-) Use of this option allows our team to go all
215 out in checking for consistency when debugging without fear of its
216 effect on end users. If you are on the verge of sending in a bug
217 report, say Y and you might get a useful error message. Almost
218 everyone should say N.
220 config REISERFS_PROC_INFO
221 bool "Stats in /proc/fs/reiserfs"
222 depends on REISERFS_FS
224 Create under /proc/fs/reiserfs a hierarchy of files, displaying
225 various ReiserFS statistics and internal data at the expense of
226 making your kernel or module slightly larger (+8 KB). This also
227 increases the amount of kernel memory required for each mount.
228 Almost everyone but ReiserFS developers and people fine-tuning
229 reiserfs or tracing problems should say N.
231 config REISERFS_FS_XATTR
232 bool "ReiserFS extended attributes"
233 depends on REISERFS_FS
235 Extended attributes are name:value pairs associated with inodes by
236 the kernel or by users (see the attr(5) manual page, or visit
237 <http://acl.bestbits.at/> for details).
241 config REISERFS_FS_POSIX_ACL
242 bool "ReiserFS POSIX Access Control Lists"
243 depends on REISERFS_FS_XATTR
246 Posix Access Control Lists (ACLs) support permissions for users and
247 groups beyond the owner/group/world scheme.
249 To learn more about Access Control Lists, visit the Posix ACLs for
250 Linux website <http://acl.bestbits.at/>.
252 If you don't know what Access Control Lists are, say N
254 config REISERFS_FS_SECURITY
255 bool "ReiserFS Security Labels"
256 depends on REISERFS_FS_XATTR
258 Security labels support alternative access control models
259 implemented by security modules like SELinux. This option
260 enables an extended attribute handler for file security
261 labels in the ReiserFS filesystem.
263 If you are not using a security module that requires using
264 extended attributes for file security labels, say N.
267 tristate "JFS filesystem support"
270 This is a port of IBM's Journaled Filesystem . More information is
271 available in the file <file:Documentation/filesystems/jfs.txt>.
273 If you do not intend to use the JFS filesystem, say N.
276 bool "JFS POSIX Access Control Lists"
280 Posix Access Control Lists (ACLs) support permissions for users and
281 groups beyond the owner/group/world scheme.
283 To learn more about Access Control Lists, visit the Posix ACLs for
284 Linux website <http://acl.bestbits.at/>.
286 If you don't know what Access Control Lists are, say N
289 bool "JFS Security Labels"
292 Security labels support alternative access control models
293 implemented by security modules like SELinux. This option
294 enables an extended attribute handler for file security
295 labels in the jfs filesystem.
297 If you are not using a security module that requires using
298 extended attributes for file security labels, say N.
304 If you are experiencing any problems with the JFS filesystem, say
305 Y here. This will result in additional debugging messages to be
306 written to the system log. Under normal circumstances, this
307 results in very little overhead.
309 config JFS_STATISTICS
310 bool "JFS statistics"
313 Enabling this option will cause statistics from the JFS file system
314 to be made available to the user in the /proc/fs/jfs/ directory.
317 # Posix ACL utility routines (for now, only ext2/ext3/jfs/reiserfs)
319 # NOTE: you can implement Posix ACLs without these helpers (XFS does).
320 # Never use this symbol for ifdefs.
325 source "fs/xfs/Kconfig"
328 tristate "OCFS2 file system support (EXPERIMENTAL)"
329 depends on NET && SYSFS && EXPERIMENTAL
335 OCFS2 is a general purpose extent based shared disk cluster file
336 system with many similarities to ext3. It supports 64 bit inode
337 numbers, and has automatically extending metadata groups which may
338 also make it attractive for non-clustered use.
340 You'll want to install the ocfs2-tools package in order to at least
343 Project web page: http://oss.oracle.com/projects/ocfs2
344 Tools web page: http://oss.oracle.com/projects/ocfs2-tools
345 OCFS2 mailing lists: http://oss.oracle.com/projects/ocfs2/mailman/
347 Note: Features which OCFS2 does not support yet:
348 - extended attributes
349 - shared writeable mmap
350 - loopback is supported, but data written will not
353 - cluster aware flock
354 - Directory change notification (F_NOTIFY)
355 - Distributed Caching (F_SETLEASE/F_GETLEASE/break_lease)
357 - readpages / writepages (not user visible)
359 config OCFS2_DEBUG_MASKLOG
360 bool "OCFS2 logging support"
364 The ocfs2 filesystem has an extensive logging system. The system
365 allows selection of events to log via files in /sys/o2cb/logmask/.
366 This option will enlarge your kernel, but it allows debugging of
367 ocfs2 filesystem issues.
370 tristate "Minix fs support"
372 Minix is a simple operating system used in many classes about OS's.
373 The minix file system (method to organize files on a hard disk
374 partition or a floppy disk) was the original file system for Linux,
375 but has been superseded by the second extended file system ext2fs.
376 You don't want to use the minix file system on your hard disk
377 because of certain built-in restrictions, but it is sometimes found
378 on older Linux floppy disks. This option will enlarge your kernel
379 by about 28 KB. If unsure, say N.
381 To compile this file system support as a module, choose M here: the
382 module will be called minix. Note that the file system of your root
383 partition (the one containing the directory /) cannot be compiled as
387 tristate "ROM file system support"
389 This is a very small read-only file system mainly intended for
390 initial ram disks of installation disks, but it could be used for
391 other read-only media as well. Read
392 <file:Documentation/filesystems/romfs.txt> for details.
394 To compile this file system support as a module, choose M here: the
395 module will be called romfs. Note that the file system of your
396 root partition (the one containing the directory /) cannot be a
399 If you don't know whether you need it, then you don't need it:
403 bool "Inotify file change notification support"
406 Say Y here to enable inotify support. Inotify is a file change
407 notification system and a replacement for dnotify. Inotify fixes
408 numerous shortcomings in dnotify and introduces several new features
409 including multiple file events, one-shot support, and unmount
412 For more information, see Documentation/filesystems/inotify.txt
417 bool "Inotify support for userspace"
421 Say Y here to enable inotify support for userspace, including the
422 associated system calls. Inotify allows monitoring of both files and
423 directories via a single open fd. Events are read from the file
424 descriptor, which is also select()- and poll()-able.
426 For more information, see Documentation/filesystems/inotify.txt
433 If you say Y here, you will be able to set per user limits for disk
434 usage (also called disk quotas). Currently, it works for the
435 ext2, ext3, and reiserfs file system. ext3 also supports journalled
436 quotas for which you don't need to run quotacheck(8) after an unclean
438 For further details, read the Quota mini-HOWTO, available from
439 <http://www.tldp.org/docs.html#howto>, or the documentation provided
440 with the quota tools. Probably the quota support is only useful for
441 multi user systems. If unsure, say N.
444 tristate "Old quota format support"
447 This quota format was (is) used by kernels earlier than 2.4.22. If
448 you have quota working and you don't want to convert to new quota
452 tristate "Quota format v2 support"
455 This quota format allows using quotas with 32-bit UIDs/GIDs. If you
456 need this functionality say Y here.
460 depends on XFS_QUOTA || QUOTA
464 bool "Dnotify support" if EMBEDDED
467 Dnotify is a directory-based per-fd file change notification system
468 that uses signals to communicate events to user-space. There exist
469 superior alternatives, but some applications may still rely on
472 Because of this, if unsure, say Y.
475 tristate "Kernel automounter support"
477 The automounter is a tool to automatically mount remote file systems
478 on demand. This implementation is partially kernel-based to reduce
479 overhead in the already-mounted case; this is unlike the BSD
480 automounter (amd), which is a pure user space daemon.
482 To use the automounter you need the user-space tools from the autofs
483 package; you can find the location in <file:Documentation/Changes>.
484 You also want to answer Y to "NFS file system support", below.
486 If you want to use the newer version of the automounter with more
487 features, say N here and say Y to "Kernel automounter v4 support",
490 To compile this support as a module, choose M here: the module will be
493 If you are not a part of a fairly large, distributed network, you
494 probably do not need an automounter, and can say N here.
497 tristate "Kernel automounter version 4 support (also supports v3)"
499 The automounter is a tool to automatically mount remote file systems
500 on demand. This implementation is partially kernel-based to reduce
501 overhead in the already-mounted case; this is unlike the BSD
502 automounter (amd), which is a pure user space daemon.
504 To use the automounter you need the user-space tools from
505 <ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4/>; you also
506 want to answer Y to "NFS file system support", below.
508 To compile this support as a module, choose M here: the module will be
509 called autofs4. You will need to add "alias autofs autofs4" to your
510 modules configuration file.
512 If you are not a part of a fairly large, distributed network or
513 don't have a laptop which needs to dynamically reconfigure to the
514 local network, you probably do not need an automounter, and can say
518 tristate "Filesystem in Userspace support"
520 With FUSE it is possible to implement a fully functional filesystem
521 in a userspace program.
523 There's also companion library: libfuse. This library along with
524 utilities is available from the FUSE homepage:
525 <http://fuse.sourceforge.net/>
527 See <file:Documentation/filesystems/fuse.txt> for more information.
528 See <file:Documentation/Changes> for needed library/utility version.
530 If you want to develop a userspace FS, or if you want to use
531 a filesystem based on FUSE, answer Y or M.
536 tristate "General filesystem cache manager"
537 depends on EXPERIMENTAL
539 This option enables a generic filesystem caching manager that can be
540 used by various network and other filesystems to cache data
541 locally. Different sorts of caches can be plugged in, depending on the
544 See Documentation/filesystems/caching/fscache.txt for more information.
548 menu "CD-ROM/DVD Filesystems"
551 tristate "ISO 9660 CDROM file system support"
553 This is the standard file system used on CD-ROMs. It was previously
554 known as "High Sierra File System" and is called "hsfs" on other
555 Unix systems. The so-called Rock-Ridge extensions which allow for
556 long Unix filenames and symbolic links are also supported by this
557 driver. If you have a CD-ROM drive and want to do more with it than
558 just listen to audio CDs and watch its LEDs, say Y (and read
559 <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO,
560 available from <http://www.tldp.org/docs.html#howto>), thereby
561 enlarging your kernel by about 27 KB; otherwise say N.
563 To compile this file system support as a module, choose M here: the
564 module will be called isofs.
567 bool "Microsoft Joliet CDROM extensions"
568 depends on ISO9660_FS
571 Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system
572 which allows for long filenames in unicode format (unicode is the
573 new 16 bit character code, successor to ASCII, which encodes the
574 characters of almost all languages of the world; see
575 <http://www.unicode.org/> for more information). Say Y here if you
576 want to be able to read Joliet CD-ROMs under Linux.
579 bool "Transparent decompression extension"
580 depends on ISO9660_FS
583 This is a Linux-specific extension to RockRidge which lets you store
584 data in compressed form on a CD-ROM and have it transparently
585 decompressed when the CD-ROM is accessed. See
586 <http://www.kernel.org/pub/linux/utils/fs/zisofs/> for the tools
587 necessary to create such a filesystem. Say Y here if you want to be
588 able to read such compressed CD-ROMs.
591 # for fs/nls/Config.in
597 tristate "UDF file system support"
599 This is the new file system used on some CD-ROMs and DVDs. Say Y if
600 you intend to mount DVD discs or CDRW's written in packet mode, or
601 if written to by other UDF utilities, such as DirectCD.
602 Please read <file:Documentation/filesystems/udf.txt>.
604 To compile this file system support as a module, choose M here: the
605 module will be called udf.
612 depends on (UDF_FS=m && NLS) || (UDF_FS=y && NLS=y)
615 tristate "Filesystem caching on files"
618 This permits use of a mounted filesystem as a cache for other
619 filesystems - primarily networking filesystems - thus allowing fast
620 local disk to enhance the speed of slower devices.
622 See Documentation/filesystems/caching/cachefiles.txt for more
625 config CACHEFILES_DEBUG
626 bool "Debug CacheFiles"
627 depends on CACHEFILES
629 This permits debugging to be dynamically enabled in the filesystem
630 caching on files module. If this is set, the debugging output may be
631 enabled by setting bits in /proc/sys/fs/cachefiles/debug or by
632 including a debugging specifier in /etc/cachefilesd.conf.
636 menu "DOS/FAT/NT Filesystems"
642 If you want to use one of the FAT-based file systems (the MS-DOS and
643 VFAT (Windows 95) file systems), then you must say Y or M here
644 to include FAT support. You will then be able to mount partitions or
645 diskettes with FAT-based file systems and transparently access the
646 files on them, i.e. MSDOS files will look and behave just like all
649 This FAT support is not a file system in itself, it only provides
650 the foundation for the other file systems. You will have to say Y or
651 M to at least one of "MSDOS fs support" or "VFAT fs support" in
652 order to make use of it.
654 Another way to read and write MSDOS floppies and hard drive
655 partitions from within Linux (but not transparently) is with the
656 mtools ("man mtools") program suite. You don't need to say Y here in
659 If you need to move large files on floppies between a DOS and a
660 Linux box, say Y here, mount the floppy under Linux with an MSDOS
661 file system and use GNU tar's M option. GNU tar is a program
662 available for Unix and DOS ("man tar" or "info tar").
664 It is now also becoming possible to read and write compressed FAT
665 file systems; read <file:Documentation/filesystems/fat_cvf.txt> for
668 The FAT support will enlarge your kernel by about 37 KB. If unsure,
671 To compile this as a module, choose M here: the module will be called
672 fat. Note that if you compile the FAT support as a module, you
673 cannot compile any of the FAT-based file systems into the kernel
674 -- they will have to be modules as well.
677 tristate "MSDOS fs support"
680 This allows you to mount MSDOS partitions of your hard drive (unless
681 they are compressed; to access compressed MSDOS partitions under
682 Linux, you can either use the DOS emulator DOSEMU, described in the
683 DOSEMU-HOWTO, available from
684 <http://www.tldp.org/docs.html#howto>, or try dmsdosfs in
685 <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you
686 intend to use dosemu with a non-compressed MSDOS partition, say Y
687 here) and MSDOS floppies. This means that file access becomes
688 transparent, i.e. the MSDOS files look and behave just like all
691 If you have Windows 95 or Windows NT installed on your MSDOS
692 partitions, you should use the VFAT file system (say Y to "VFAT fs
693 support" below), or you will not be able to see the long filenames
694 generated by Windows 95 / Windows NT.
696 This option will enlarge your kernel by about 7 KB. If unsure,
697 answer Y. This will only work if you said Y to "DOS FAT fs support"
698 as well. To compile this as a module, choose M here: the module will
702 tristate "VFAT (Windows-95) fs support"
705 This option provides support for normal Windows file systems with
706 long filenames. That includes non-compressed FAT-based file systems
707 used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
708 programs from the mtools package.
710 The VFAT support enlarges your kernel by about 10 KB and it only
711 works if you said Y to the "DOS FAT fs support" above. Please read
712 the file <file:Documentation/filesystems/vfat.txt> for details. If
715 To compile this as a module, choose M here: the module will be called
718 config FAT_DEFAULT_CODEPAGE
719 int "Default codepage for FAT"
720 depends on MSDOS_FS || VFAT_FS
723 This option should be set to the codepage of your FAT filesystems.
724 It can be overridden with the "codepage" mount option.
725 See <file:Documentation/filesystems/vfat.txt> for more information.
727 config FAT_DEFAULT_IOCHARSET
728 string "Default iocharset for FAT"
732 Set this to the default input/output character set you'd
733 like FAT to use. It should probably match the character set
734 that most of your FAT filesystems use, and can be overridden
735 with the "iocharset" mount option for FAT filesystems.
736 Note that "utf8" is not recommended for FAT filesystems.
737 If unsure, you shouldn't set "utf8" here.
738 See <file:Documentation/filesystems/vfat.txt> for more information.
741 tristate "NTFS file system support"
744 NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003.
746 Saying Y or M here enables read support. There is partial, but
747 safe, write support available. For write support you must also
748 say Y to "NTFS write support" below.
750 There are also a number of user-space tools available, called
751 ntfsprogs. These include ntfsundelete and ntfsresize, that work
752 without NTFS support enabled in the kernel.
754 This is a rewrite from scratch of Linux NTFS support and replaced
755 the old NTFS code starting with Linux 2.5.11. A backport to
756 the Linux 2.4 kernel series is separately available as a patch
757 from the project web site.
759 For more information see <file:Documentation/filesystems/ntfs.txt>
760 and <http://linux-ntfs.sourceforge.net/>.
762 To compile this file system support as a module, choose M here: the
763 module will be called ntfs.
765 If you are not using Windows NT, 2000, XP or 2003 in addition to
766 Linux on your computer it is safe to say N.
769 bool "NTFS debugging support"
772 If you are experiencing any problems with the NTFS file system, say
773 Y here. This will result in additional consistency checks to be
774 performed by the driver as well as additional debugging messages to
775 be written to the system log. Note that debugging messages are
776 disabled by default. To enable them, supply the option debug_msgs=1
777 at the kernel command line when booting the kernel or as an option
778 to insmod when loading the ntfs module. Once the driver is active,
779 you can enable debugging messages by doing (as root):
780 echo 1 > /proc/sys/fs/ntfs-debug
781 Replacing the "1" with "0" would disable debug messages.
783 If you leave debugging messages disabled, this results in little
784 overhead, but enabling debug messages results in very significant
785 slowdown of the system.
787 When reporting bugs, please try to have available a full dump of
788 debugging messages while the misbehaviour was occurring.
791 bool "NTFS write support"
794 This enables the partial, but safe, write support in the NTFS driver.
796 The only supported operation is overwriting existing files, without
797 changing the file length. No file or directory creation, deletion or
798 renaming is possible. Note only non-resident files can be written to
799 so you may find that some very small files (<500 bytes or so) cannot
802 While we cannot guarantee that it will not damage any data, we have
803 so far not received a single report where the driver would have
804 damaged someones data so we assume it is perfectly safe to use.
806 Note: While write support is safe in this version (a rewrite from
807 scratch of the NTFS support), it should be noted that the old NTFS
808 write support, included in Linux 2.5.10 and before (since 1997),
811 This is currently useful with TopologiLinux. TopologiLinux is run
812 on top of any DOS/Microsoft Windows system without partitioning your
813 hard disk. Unlike other Linux distributions TopologiLinux does not
814 need its own partition. For more information see
815 <http://topologi-linux.sourceforge.net/>
817 It is perfectly safe to say N here.
821 menu "Pseudo filesystems"
824 bool "/proc file system support" if EMBEDDED
827 This is a virtual file system providing information about the status
828 of the system. "Virtual" means that it doesn't take up any space on
829 your hard disk: the files are created on the fly by the kernel when
830 you try to access them. Also, you cannot read the files with older
831 version of the program less: you need to use more or cat.
833 It's totally cool; for example, "cat /proc/interrupts" gives
834 information about what the different IRQs are used for at the moment
835 (there is a small number of Interrupt ReQuest lines in your computer
836 that are used by the attached devices to gain the CPU's attention --
837 often a source of trouble if two devices are mistakenly configured
838 to use the same IRQ). The program procinfo to display some
839 information about your system gathered from the /proc file system.
841 Before you can use the /proc file system, it has to be mounted,
842 meaning it has to be given a location in the directory hierarchy.
843 That location should be /proc. A command such as "mount -t proc proc
844 /proc" or the equivalent line in /etc/fstab does the job.
846 The /proc file system is explained in the file
847 <file:Documentation/filesystems/proc.txt> and on the proc(5) manpage
850 This option will enlarge your kernel by about 67 KB. Several
851 programs depend on this, so everyone should say Y here.
854 bool "/proc/kcore support" if !ARM
855 depends on PROC_FS && MMU
858 bool "/proc/vmcore support (EXPERIMENTAL)"
859 depends on PROC_FS && EXPERIMENTAL && CRASH_DUMP
862 Exports the dump image of crashed kernel in ELF format.
865 bool "sysfs file system support" if EMBEDDED
868 The sysfs filesystem is a virtual filesystem that the kernel uses to
869 export internal kernel objects, their attributes, and their
870 relationships to one another.
872 Users can use sysfs to ascertain useful information about the running
873 kernel, such as the devices the kernel has discovered on each bus and
874 which driver each is bound to. sysfs can also be used to tune devices
875 and other kernel subsystems.
877 Some system agents rely on the information in sysfs to operate.
878 /sbin/hotplug uses device and object attributes in sysfs to assist in
879 delegating policy decisions, like persistantly naming devices.
881 sysfs is currently used by the block subsystem to mount the root
882 partition. If sysfs is disabled you must specify the boot device on
883 the kernel boot command line via its major and minor numbers. For
884 example, "root=03:01" for /dev/hda1.
886 Designers of embedded systems may wish to say N here to conserve space.
889 bool "Virtual memory file system support (former shm fs)"
891 Tmpfs is a file system which keeps all files in virtual memory.
893 Everything in tmpfs is temporary in the sense that no files will be
894 created on your hard drive. The files live in memory and swap
895 space. If you unmount a tmpfs instance, everything stored therein is
898 See <file:Documentation/filesystems/tmpfs.txt> for details.
901 bool "HugeTLB file system support"
902 depends X86 || IA64 || PPC64 || SPARC64 || SUPERH || BROKEN
905 hugetlbfs is a filesystem backing for HugeTLB pages, based on
906 ramfs. For architectures that support it, say Y here and read
907 <file:Documentation/vm/hugetlbpage.txt> for details.
918 Ramfs is a file system which keeps all files in RAM. It allows
919 read and write access.
921 It is more of an programming example than a useable file system. If
922 you need a file system which lives in RAM with limit checking use
925 To compile this as a module, choose M here: the module will be called
929 tristate "Userspace-driven configuration filesystem (EXPERIMENTAL)"
930 depends on SYSFS && EXPERIMENTAL
932 configfs is a ram-based filesystem that provides the converse
933 of sysfs's functionality. Where sysfs is a filesystem-based
934 view of kernel objects, configfs is a filesystem-based manager
935 of kernel objects, or config_items.
937 Both sysfs and configfs can and should exist together on the
938 same system. One is not a replacement for the other.
942 menu "Miscellaneous filesystems"
945 tristate "ADFS file system support (EXPERIMENTAL)"
946 depends on EXPERIMENTAL
948 The Acorn Disc Filing System is the standard file system of the
949 RiscOS operating system which runs on Acorn's ARM-based Risc PC
950 systems and the Acorn Archimedes range of machines. If you say Y
951 here, Linux will be able to read from ADFS partitions on hard drives
952 and from ADFS-formatted floppy discs. If you also want to be able to
953 write to those devices, say Y to "ADFS write support" below.
955 The ADFS partition should be the first partition (i.e.,
956 /dev/[hs]d?1) on each of your drives. Please read the file
957 <file:Documentation/filesystems/adfs.txt> for further details.
959 To compile this code as a module, choose M here: the module will be
965 bool "ADFS write support (DANGEROUS)"
968 If you say Y here, you will be able to write to ADFS partitions on
969 hard drives and ADFS-formatted floppy disks. This is experimental
970 codes, so if you're unsure, say N.
973 tristate "Amiga FFS file system support (EXPERIMENTAL)"
974 depends on EXPERIMENTAL
976 The Fast File System (FFS) is the common file system used on hard
977 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
978 if you want to be able to read and write files from and to an Amiga
979 FFS partition on your hard drive. Amiga floppies however cannot be
980 read with this driver due to an incompatibility of the floppy
981 controller used in an Amiga and the standard floppy controller in
982 PCs and workstations. Read <file:Documentation/filesystems/affs.txt>
983 and <file:fs/affs/Changes>.
985 With this driver you can also mount disk files used by Bernd
986 Schmidt's Un*X Amiga Emulator
987 (<http://www.freiburg.linux.de/~uae/>).
988 If you want to do this, you will also need to say Y or M to "Loop
989 device support", above.
991 To compile this file system support as a module, choose M here: the
992 module will be called affs. If unsure, say N.
995 tristate "Apple Macintosh file system support (EXPERIMENTAL)"
996 depends on EXPERIMENTAL
999 If you say Y here, you will be able to mount Macintosh-formatted
1000 floppy disks and hard drive partitions with full read-write access.
1001 Please read <file:fs/hfs/HFS.txt> to learn about the available mount
1004 To compile this file system support as a module, choose M here: the
1005 module will be called hfs.
1008 tristate "Apple Extended HFS file system support"
1012 If you say Y here, you will be able to mount extended format
1013 Macintosh-formatted hard drive partitions with full read-write access.
1015 This file system is often called HFS+ and was introduced with
1016 MacOS 8. It includes all Mac specific filesystem data such as
1017 data forks and creator codes, but it also has several UNIX
1018 style features such as file ownership and permissions.
1021 tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)"
1022 depends on EXPERIMENTAL
1025 The BeOS File System (BeFS) is the native file system of Be, Inc's
1026 BeOS. Notable features include support for arbitrary attributes
1027 on files and directories, and database-like indeces on selected
1028 attributes. (Also note that this driver doesn't make those features
1029 available at this time). It is a 64 bit filesystem, so it supports
1030 extremly large volumes and files.
1032 If you use this filesystem, you should also say Y to at least one
1033 of the NLS (native language support) options below.
1035 If you don't know what this is about, say N.
1037 To compile this as a module, choose M here: the module will be
1044 If you say Y here, you can use the 'debug' mount option to enable
1045 debugging output from the driver.
1048 tristate "BFS file system support (EXPERIMENTAL)"
1049 depends on EXPERIMENTAL
1051 Boot File System (BFS) is a file system used under SCO UnixWare to
1052 allow the bootloader access to the kernel image and other important
1053 files during the boot process. It is usually mounted under /stand
1054 and corresponds to the slice marked as "STAND" in the UnixWare
1055 partition. You should say Y if you want to read or write the files
1056 on your /stand slice from within Linux. You then also need to say Y
1057 to "UnixWare slices support", below. More information about the BFS
1058 file system is contained in the file
1059 <file:Documentation/filesystems/bfs.txt>.
1061 If you don't know what this is about, say N.
1063 To compile this as a module, choose M here: the module will be called
1064 bfs. Note that the file system of your root partition (the one
1065 containing the directory /) cannot be compiled as a module.
1070 tristate "EFS file system support (read only) (EXPERIMENTAL)"
1071 depends on EXPERIMENTAL
1073 EFS is an older file system used for non-ISO9660 CD-ROMs and hard
1074 disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
1075 uses the XFS file system for hard disk partitions however).
1077 This implementation only offers read-only access. If you don't know
1078 what all this is about, it's safe to say N. For more information
1079 about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
1081 To compile the EFS file system support as a module, choose M here: the
1082 module will be called efs.
1085 tristate "Journalling Flash File System (JFFS) support"
1088 JFFS is the Journaling Flash File System developed by Axis
1089 Communications in Sweden, aimed at providing a crash/powerdown-safe
1090 file system for disk-less embedded devices. Further information is
1091 available at (<http://developer.axis.com/software/jffs/>).
1093 config JFFS_FS_VERBOSE
1094 int "JFFS debugging verbosity (0 = quiet, 3 = noisy)"
1098 Determines the verbosity level of the JFFS debugging messages.
1101 bool "JFFS stats available in /proc filesystem"
1102 depends on JFFS_FS && PROC_FS
1104 Enabling this option will cause statistics from mounted JFFS file systems
1105 to be made available to the user in the /proc/fs/jffs/ directory.
1108 tristate "Journalling Flash File System v2 (JFFS2) support"
1112 JFFS2 is the second generation of the Journalling Flash File System
1113 for use on diskless embedded devices. It provides improved wear
1114 levelling, compression and support for hard links. You cannot use
1115 this on normal block devices, only on 'MTD' devices.
1117 Further information on the design and implementation of JFFS2 is
1118 available at <http://sources.redhat.com/jffs2/>.
1120 config JFFS2_FS_DEBUG
1121 int "JFFS2 debugging verbosity (0 = quiet, 2 = noisy)"
1125 This controls the amount of debugging messages produced by the JFFS2
1126 code. Set it to zero for use in production systems. For evaluation,
1127 testing and debugging, it's advisable to set it to one. This will
1128 enable a few assertions and will print debugging messages at the
1129 KERN_DEBUG loglevel, where they won't normally be visible. Level 2
1130 is unlikely to be useful - it enables extra debugging in certain
1131 areas which at one point needed debugging, but when the bugs were
1132 located and fixed, the detailed messages were relegated to level 2.
1134 If reporting bugs, please try to have available a full dump of the
1135 messages at debug level 1 while the misbehaviour was occurring.
1137 config JFFS2_FS_WRITEBUFFER
1138 bool "JFFS2 write-buffering support"
1142 This enables the write-buffering support in JFFS2.
1144 This functionality is required to support JFFS2 on the following
1145 types of flash devices:
1147 - NOR flash with transparent ECC
1150 config JFFS2_SUMMARY
1151 bool "JFFS2 summary support (EXPERIMENTAL)"
1152 depends on JFFS2_FS && EXPERIMENTAL
1155 This feature makes it possible to use summary information
1156 for faster filesystem mount.
1158 The summary information can be inserted into a filesystem image
1159 by the utility 'sumtool'.
1163 config JFFS2_FS_XATTR
1164 bool "JFFS2 XATTR support (EXPERIMENTAL)"
1165 depends on JFFS2_FS && EXPERIMENTAL
1168 Extended attributes are name:value pairs associated with inodes by
1169 the kernel or by users (see the attr(5) manual page, or visit
1170 <http://acl.bestbits.at/> for details).
1174 config JFFS2_FS_POSIX_ACL
1175 bool "JFFS2 POSIX Access Control Lists"
1176 depends on JFFS2_FS_XATTR
1180 Posix Access Control Lists (ACLs) support permissions for users and
1181 groups beyond the owner/group/world scheme.
1183 To learn more about Access Control Lists, visit the Posix ACLs for
1184 Linux website <http://acl.bestbits.at/>.
1186 If you don't know what Access Control Lists are, say N
1188 config JFFS2_FS_SECURITY
1189 bool "JFFS2 Security Labels"
1190 depends on JFFS2_FS_XATTR
1193 Security labels support alternative access control models
1194 implemented by security modules like SELinux. This option
1195 enables an extended attribute handler for file security
1196 labels in the jffs2 filesystem.
1198 If you are not using a security module that requires using
1199 extended attributes for file security labels, say N.
1201 config JFFS2_COMPRESSION_OPTIONS
1202 bool "Advanced compression options for JFFS2"
1206 Enabling this option allows you to explicitly choose which
1207 compression modules, if any, are enabled in JFFS2. Removing
1208 compressors and mean you cannot read existing file systems,
1209 and enabling experimental compressors can mean that you
1210 write a file system which cannot be read by a standard kernel.
1212 If unsure, you should _definitely_ say 'N'.
1215 bool "JFFS2 ZLIB compression support" if JFFS2_COMPRESSION_OPTIONS
1221 Zlib is designed to be a free, general-purpose, legally unencumbered,
1222 lossless data-compression library for use on virtually any computer
1223 hardware and operating system. See <http://www.gzip.org/zlib/> for
1224 further information.
1229 bool "JFFS2 RTIME compression support" if JFFS2_COMPRESSION_OPTIONS
1233 Rtime does manage to recompress already-compressed data. Say 'Y' if unsure.
1236 bool "JFFS2 RUBIN compression support" if JFFS2_COMPRESSION_OPTIONS
1240 RUBINMIPS and DYNRUBIN compressors. Say 'N' if unsure.
1243 prompt "JFFS2 default compression mode" if JFFS2_COMPRESSION_OPTIONS
1244 default JFFS2_CMODE_PRIORITY
1247 You can set here the default compression mode of JFFS2 from
1248 the available compression modes. Don't touch if unsure.
1250 config JFFS2_CMODE_NONE
1251 bool "no compression"
1253 Uses no compression.
1255 config JFFS2_CMODE_PRIORITY
1258 Tries the compressors in a predefinied order and chooses the first
1261 config JFFS2_CMODE_SIZE
1262 bool "size (EXPERIMENTAL)"
1264 Tries all compressors and chooses the one which has the smallest
1270 tristate "Compressed ROM file system support (cramfs)"
1273 Saying Y here includes support for CramFs (Compressed ROM File
1274 System). CramFs is designed to be a simple, small, and compressed
1275 file system for ROM based embedded systems. CramFs is read-only,
1276 limited to 256MB file systems (with 16MB files), and doesn't support
1277 16/32 bits uid/gid, hard links and timestamps.
1279 See <file:Documentation/filesystems/cramfs.txt> and
1280 <file:fs/cramfs/README> for further information.
1282 To compile this as a module, choose M here: the module will be called
1283 cramfs. Note that the root file system (the one containing the
1284 directory /) cannot be compiled as a module.
1289 tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
1291 FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
1292 file system format. VERITAS VxFS(TM) is the standard file system
1293 of SCO UnixWare (and possibly others) and optionally available
1294 for Sunsoft Solaris, HP-UX and many other operating systems.
1295 Currently only readonly access is supported.
1297 NOTE: the file system type as used by mount(1), mount(2) and
1298 fstab(5) is 'vxfs' as it describes the file system format, not
1301 To compile this as a module, choose M here: the module will be
1302 called freevxfs. If unsure, say N.
1306 tristate "OS/2 HPFS file system support"
1308 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
1309 is the file system used for organizing files on OS/2 hard disk
1310 partitions. Say Y if you want to be able to read files from and
1311 write files to an OS/2 HPFS partition on your hard drive. OS/2
1312 floppies however are in regular MSDOS format, so you don't need this
1313 option in order to be able to read them. Read
1314 <file:Documentation/filesystems/hpfs.txt>.
1316 To compile this file system support as a module, choose M here: the
1317 module will be called hpfs. If unsure, say N.
1322 tristate "QNX4 file system support (read only)"
1324 This is the file system used by the real-time operating systems
1325 QNX 4 and QNX 6 (the latter is also called QNX RTP).
1326 Further information is available at <http://www.qnx.com/>.
1327 Say Y if you intend to mount QNX hard disks or floppies.
1328 Unless you say Y to "QNX4FS read-write support" below, you will
1329 only be able to read these file systems.
1331 To compile this file system support as a module, choose M here: the
1332 module will be called qnx4.
1334 If you don't know whether you need it, then you don't need it:
1338 bool "QNX4FS write support (DANGEROUS)"
1339 depends on QNX4FS_FS && EXPERIMENTAL && BROKEN
1341 Say Y if you want to test write support for QNX4 file systems.
1343 It's currently broken, so for now:
1349 tristate "System V/Xenix/V7/Coherent file system support"
1351 SCO, Xenix and Coherent are commercial Unix systems for Intel
1352 machines, and Version 7 was used on the DEC PDP-11. Saying Y
1353 here would allow you to read from their floppies and hard disk
1356 If you have floppies or hard disk partitions like that, it is likely
1357 that they contain binaries from those other Unix systems; in order
1358 to run these binaries, you will want to install linux-abi which is a
1359 a set of kernel modules that lets you run SCO, Xenix, Wyse,
1360 UnixWare, Dell Unix and System V programs under Linux. It is
1361 available via FTP (user: ftp) from
1362 <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
1363 NOTE: that will work only for binaries from Intel-based systems;
1364 PDP ones will have to wait until somebody ports Linux to -11 ;-)
1366 If you only intend to mount files from some other Unix over the
1367 network using NFS, you don't need the System V file system support
1368 (but you need NFS file system support obviously).
1370 Note that this option is generally not needed for floppies, since a
1371 good portable way to transport files and directories between unixes
1372 (and even other operating systems) is given by the tar program ("man
1373 tar" or preferably "info tar"). Note also that this option has
1374 nothing whatsoever to do with the option "System V IPC". Read about
1375 the System V file system in
1376 <file:Documentation/filesystems/sysv-fs.txt>.
1377 Saying Y here will enlarge your kernel by about 27 KB.
1379 To compile this as a module, choose M here: the module will be called
1382 If you haven't heard about all of this before, it's safe to say N.
1387 tristate "UFS file system support (read only)"
1389 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
1390 OpenBSD and NeXTstep) use a file system called UFS. Some System V
1391 Unixes can create and mount hard disk partitions and diskettes using
1392 this file system as well. Saying Y here will allow you to read from
1393 these partitions; if you also want to write to them, say Y to the
1394 experimental "UFS file system write support", below. Please read the
1395 file <file:Documentation/filesystems/ufs.txt> for more information.
1397 The recently released UFS2 variant (used in FreeBSD 5.x) is
1398 READ-ONLY supported.
1400 If you only intend to mount files from some other Unix over the
1401 network using NFS, you don't need the UFS file system support (but
1402 you need NFS file system support obviously).
1404 Note that this option is generally not needed for floppies, since a
1405 good portable way to transport files and directories between unixes
1406 (and even other operating systems) is given by the tar program ("man
1407 tar" or preferably "info tar").
1409 When accessing NeXTstep files, you may need to convert them from the
1410 NeXT character set to the Latin1 character set; use the program
1411 recode ("info recode") for this purpose.
1413 To compile the UFS file system support as a module, choose M here: the
1414 module will be called ufs.
1416 If you haven't heard about all of this before, it's safe to say N.
1419 bool "UFS file system write support (DANGEROUS)"
1420 depends on UFS_FS && EXPERIMENTAL
1422 Say Y here if you want to try writing to UFS partitions. This is
1423 experimental, so you should back up your UFS partitions beforehand.
1426 bool "UFS debugging"
1429 If you are experiencing any problems with the UFS filesystem, say
1430 Y here. This will result in _many_ additional debugging messages to be
1431 written to the system log.
1435 menu "Network File Systems"
1439 tristate "NFS file system support"
1443 select NFS_ACL_SUPPORT if NFS_V3_ACL
1445 If you are connected to some other (usually local) Unix computer
1446 (using SLIP, PLIP, PPP or Ethernet) and want to mount files residing
1447 on that computer (the NFS server) using the Network File Sharing
1448 protocol, say Y. "Mounting files" means that the client can access
1449 the files with usual UNIX commands as if they were sitting on the
1450 client's hard disk. For this to work, the server must run the
1451 programs nfsd and mountd (but does not need to have NFS file system
1452 support enabled in its kernel). NFS is explained in the Network
1453 Administrator's Guide, available from
1454 <http://www.tldp.org/docs.html#guide>, on its man page: "man
1455 nfs", and in the NFS-HOWTO.
1457 A superior but less widely used alternative to NFS is provided by
1458 the Coda file system; see "Coda file system support" below.
1460 If you say Y here, you should have said Y to TCP/IP networking also.
1461 This option would enlarge your kernel by about 27 KB.
1463 To compile this file system support as a module, choose M here: the
1464 module will be called nfs.
1466 If you are configuring a diskless machine which will mount its root
1467 file system over NFS at boot time, say Y here and to "Kernel
1468 level IP autoconfiguration" above and to "Root file system on NFS"
1469 below. You cannot compile this driver as a module in this case.
1470 There are two packages designed for booting diskless machines over
1471 the net: netboot, available from
1472 <http://ftp1.sourceforge.net/netboot/>, and Etherboot,
1473 available from <http://ftp1.sourceforge.net/etherboot/>.
1475 If you don't know what all this is about, say N.
1478 bool "Provide NFSv3 client support"
1481 Say Y here if you want your NFS client to be able to speak version
1482 3 of the NFS protocol.
1487 bool "Provide client support for the NFSv3 ACL protocol extension"
1490 Implement the NFSv3 ACL protocol extension for manipulating POSIX
1491 Access Control Lists. The server should also be compiled with
1492 the NFSv3 ACL protocol extension; see the CONFIG_NFSD_V3_ACL option.
1497 bool "Provide NFSv4 client support (EXPERIMENTAL)"
1498 depends on NFS_FS && EXPERIMENTAL
1499 select RPCSEC_GSS_KRB5
1501 Say Y here if you want your NFS client to be able to speak the newer
1502 version 4 of the NFS protocol.
1504 Note: Requires auxiliary userspace daemons which may be found on
1505 http://www.citi.umich.edu/projects/nfsv4/
1510 bool "Provide NFS client caching support (EXPERIMENTAL)"
1511 depends on NFS_FS && FSCACHE && EXPERIMENTAL
1513 Say Y here if you want NFS data to be cached locally on disc through
1514 the general filesystem cache manager
1517 bool "Allow direct I/O on NFS files (EXPERIMENTAL)"
1518 depends on NFS_FS && EXPERIMENTAL
1520 This option enables applications to perform uncached I/O on files
1521 in NFS file systems using the O_DIRECT open() flag. When O_DIRECT
1522 is set for a file, its data is not cached in the system's page
1523 cache. Data is moved to and from user-level application buffers
1524 directly. Unlike local disk-based file systems, NFS O_DIRECT has
1525 no alignment restrictions.
1527 Unless your program is designed to use O_DIRECT properly, you are
1528 much better off allowing the NFS client to manage data caching for
1529 you. Misusing O_DIRECT can cause poor server performance or network
1530 storms. This kernel build option defaults OFF to avoid exposing
1531 system administrators unwittingly to a potentially hazardous
1534 For more details on NFS O_DIRECT, see fs/nfs/direct.c.
1536 If unsure, say N. This reduces the size of the NFS client, and
1537 causes open() to return EINVAL if a file residing in NFS is
1538 opened with the O_DIRECT flag.
1541 tristate "NFS server support"
1546 select NFSD_V2_ACL if NFSD_V3_ACL
1547 select NFS_ACL_SUPPORT if NFSD_V2_ACL
1548 select NFSD_TCP if NFSD_V4
1549 select CRYPTO_MD5 if NFSD_V4
1550 select CRYPTO if NFSD_V4
1551 select FS_POSIX_ACL if NFSD_V4
1553 If you want your Linux box to act as an NFS *server*, so that other
1554 computers on your local network which support NFS can access certain
1555 directories on your box transparently, you have two options: you can
1556 use the self-contained user space program nfsd, in which case you
1557 should say N here, or you can say Y and use the kernel based NFS
1558 server. The advantage of the kernel based solution is that it is
1561 In either case, you will need support software; the respective
1562 locations are given in the file <file:Documentation/Changes> in the
1565 If you say Y here, you will get support for version 2 of the NFS
1566 protocol (NFSv2). If you also want NFSv3, say Y to the next question
1569 Please read the NFS-HOWTO, available from
1570 <http://www.tldp.org/docs.html#howto>.
1572 To compile the NFS server support as a module, choose M here: the
1573 module will be called nfsd. If unsure, say N.
1580 bool "Provide NFSv3 server support"
1583 If you would like to include the NFSv3 server as well as the NFSv2
1584 server, say Y here. If unsure, say Y.
1587 bool "Provide server support for the NFSv3 ACL protocol extension"
1590 Implement the NFSv3 ACL protocol extension for manipulating POSIX
1591 Access Control Lists on exported file systems. NFS clients should
1592 be compiled with the NFSv3 ACL protocol extension; see the
1593 CONFIG_NFS_V3_ACL option. If unsure, say N.
1596 bool "Provide NFSv4 server support (EXPERIMENTAL)"
1597 depends on NFSD_V3 && EXPERIMENTAL
1599 If you would like to include the NFSv4 server as well as the NFSv2
1600 and NFSv3 servers, say Y here. This feature is experimental, and
1601 should only be used if you are interested in helping to test NFSv4.
1605 bool "Provide NFS server over TCP support"
1609 If you want your NFS server to support TCP connections, say Y here.
1610 TCP connections usually perform better than the default UDP when
1611 the network is lossy or congested. If unsure, say Y.
1614 bool "Root file system on NFS"
1615 depends on NFS_FS=y && IP_PNP
1617 If you want your Linux box to mount its whole root file system (the
1618 one containing the directory /) from some other computer over the
1619 net via NFS (presumably because your box doesn't have a hard disk),
1620 say Y. Read <file:Documentation/nfsroot.txt> for details. It is
1621 likely that in this case, you also want to say Y to "Kernel level IP
1622 autoconfiguration" so that your box can discover its network address
1625 Most people say N here.
1632 depends on NFSD_V3 || NFS_V3
1638 config NFS_ACL_SUPPORT
1644 depends on NFSD || NFS_FS
1653 config RPCSEC_GSS_KRB5
1654 tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
1655 depends on SUNRPC && EXPERIMENTAL
1661 Provides for secure RPC calls by means of a gss-api
1662 mechanism based on Kerberos V5. This is required for
1665 Note: Requires an auxiliary userspace daemon which may be found on
1666 http://www.citi.umich.edu/projects/nfsv4/
1670 config RPCSEC_GSS_SPKM3
1671 tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
1672 depends on SUNRPC && EXPERIMENTAL
1679 Provides for secure RPC calls by means of a gss-api
1680 mechanism based on the SPKM3 public-key mechanism.
1682 Note: Requires an auxiliary userspace daemon which may be found on
1683 http://www.citi.umich.edu/projects/nfsv4/
1688 tristate "SMB file system support (to mount Windows shares etc.)"
1692 SMB (Server Message Block) is the protocol Windows for Workgroups
1693 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
1694 files and printers over local networks. Saying Y here allows you to
1695 mount their file systems (often called "shares" in this context) and
1696 access them just like any other Unix directory. Currently, this
1697 works only if the Windows machines use TCP/IP as the underlying
1698 transport protocol, and not NetBEUI. For details, read
1699 <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
1700 available from <http://www.tldp.org/docs.html#howto>.
1702 Note: if you just want your box to act as an SMB *server* and make
1703 files and printing services available to Windows clients (which need
1704 to have a TCP/IP stack), you don't need to say Y here; you can use
1705 the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
1708 General information about how to connect Linux, Windows machines and
1709 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1711 To compile the SMB support as a module, choose M here: the module will
1712 be called smbfs. Most people say N, however.
1714 config SMB_NLS_DEFAULT
1715 bool "Use a default NLS"
1718 Enabling this will make smbfs use nls translations by default. You
1719 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
1720 settings and you need to give the default nls for the SMB server as
1721 CONFIG_SMB_NLS_REMOTE.
1723 The nls settings can be changed at mount time, if your smbmount
1724 supports that, using the codepage and iocharset parameters.
1726 smbmount from samba 2.2.0 or later supports this.
1728 config SMB_NLS_REMOTE
1729 string "Default Remote NLS Option"
1730 depends on SMB_NLS_DEFAULT
1733 This setting allows you to specify a default value for which
1734 codepage the server uses. If this field is left blank no
1735 translations will be done by default. The local codepage/charset
1736 default to CONFIG_NLS_DEFAULT.
1738 The nls settings can be changed at mount time, if your smbmount
1739 supports that, using the codepage and iocharset parameters.
1741 smbmount from samba 2.2.0 or later supports this.
1744 tristate "CIFS support (advanced network filesystem for Samba, Window and other CIFS compliant servers)"
1748 This is the client VFS module for the Common Internet File System
1749 (CIFS) protocol which is the successor to the Server Message Block
1750 (SMB) protocol, the native file sharing mechanism for most early
1751 PC operating systems. The CIFS protocol is fully supported by
1752 file servers such as Windows 2000 (including Windows 2003, NT 4
1753 and Windows XP) as well by Samba (which provides excellent CIFS
1754 server support for Linux and many other operating systems). Limited
1755 support for Windows ME and similar servers is provided as well.
1756 You must use the smbfs client filesystem to access older SMB servers
1757 such as OS/2 and DOS.
1759 The intent of the cifs module is to provide an advanced
1760 network file system client for mounting to CIFS compliant servers,
1761 including support for dfs (hierarchical name space), secure per-user
1762 session establishment, safe distributed caching (oplock), optional
1763 packet signing, Unicode and other internationalization improvements,
1764 and optional Winbind (nsswitch) integration. You do not need to enable
1765 cifs if running only a (Samba) server. It is possible to enable both
1766 smbfs and cifs (e.g. if you are using CIFS for accessing Windows 2003
1767 and Samba 3 servers, and smbfs for accessing old servers). If you need
1768 to mount to Samba or Windows from this machine, say Y.
1771 bool "CIFS statistics"
1774 Enabling this option will cause statistics for each server share
1775 mounted by the cifs client to be displayed in /proc/fs/cifs/Stats
1778 bool "Extended statistics"
1779 depends on CIFS_STATS
1781 Enabling this option will allow more detailed statistics on SMB
1782 request timing to be displayed in /proc/fs/cifs/DebugData and also
1783 allow optional logging of slow responses to dmesg (depending on the
1784 value of /proc/fs/cifs/cifsFYI, see fs/cifs/README for more details).
1785 These additional statistics may have a minor effect on performance
1786 and memory utilization.
1788 Unless you are a developer or are doing network performance analysis
1791 config CIFS_WEAK_PW_HASH
1792 bool "Support legacy servers which use weaker LANMAN security"
1795 Modern CIFS servers including Samba and most Windows versions
1796 (since 1997) support stronger NTLM (and even NTLMv2 and Kerberos)
1797 security mechanisms. These hash the password more securely
1798 than the mechanisms used in the older LANMAN version of the
1799 SMB protocol needed to establish sessions with old SMB servers.
1801 Enabling this option allows the cifs module to mount to older
1802 LANMAN based servers such as OS/2 and Windows 95, but such
1803 mounts may be less secure than mounts using NTLM or more recent
1804 security mechanisms if you are on a public network. Unless you
1805 have a need to access old SMB servers (and are on a private
1806 network) you probably want to say N. Even if this support
1807 is enabled in the kernel build, they will not be used
1808 automatically. At runtime LANMAN mounts are disabled but
1809 can be set to required (or optional) either in
1810 /proc/fs/cifs (see fs/cifs/README for more detail) or via an
1811 option on the mount command. This support is disabled by
1812 default in order to reduce the possibility of a downgrade
1818 bool "CIFS extended attributes"
1821 Extended attributes are name:value pairs associated with inodes by
1822 the kernel or by users (see the attr(5) manual page, or visit
1823 <http://acl.bestbits.at/> for details). CIFS maps the name of
1824 extended attributes beginning with the user namespace prefix
1825 to SMB/CIFS EAs. EAs are stored on Windows servers without the
1826 user namespace prefix, but their names are seen by Linux cifs clients
1827 prefaced by the user namespace prefix. The system namespace
1828 (used by some filesystems to store ACLs) is not supported at
1834 bool "CIFS POSIX Extensions"
1835 depends on CIFS_XATTR
1837 Enabling this option will cause the cifs client to attempt to
1838 negotiate a newer dialect with servers, such as Samba 3.0.5
1839 or later, that optionally can handle more POSIX like (rather
1840 than Windows like) file behavior. It also enables
1841 support for POSIX ACLs (getfacl and setfacl) to servers
1842 (such as Samba 3.10 and later) which can negotiate
1843 CIFS POSIX ACL support. If unsure, say N.
1846 bool "Enable additional CIFS debugging routines"
1849 Enabling this option adds a few more debugging routines
1850 to the cifs code which slightly increases the size of
1851 the cifs module and can cause additional logging of debug
1852 messages in some error paths, slowing performance. This
1853 option can be turned off unless you are debugging
1854 cifs problems. If unsure, say N.
1856 config CIFS_EXPERIMENTAL
1857 bool "CIFS Experimental Features (EXPERIMENTAL)"
1858 depends on CIFS && EXPERIMENTAL
1860 Enables cifs features under testing. These features are
1861 experimental and currently include support for writepages
1862 (multipage writebehind performance improvements) and directory
1863 change notification ie fcntl(F_DNOTIFY) as well as some security
1864 improvements. Some also depend on setting at runtime the
1865 pseudo-file /proc/fs/cifs/Experimental (which is disabled by
1866 default). See the file fs/cifs/README for more details.
1871 bool "Kerberos/SPNEGO advanced session setup (EXPERIMENTAL)"
1872 depends on CIFS_EXPERIMENTAL
1875 Enables an upcall mechanism for CIFS which will be used to contact
1876 userspace helper utilities to provide SPNEGO packaged Kerberos
1877 tickets which are needed to mount to certain secure servers
1878 (for which more secure Kerberos authentication is required). If
1882 tristate "NCP file system support (to mount NetWare volumes)"
1883 depends on IPX!=n || INET
1885 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
1886 used by Novell NetWare clients to talk to file servers. It is to
1887 IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
1888 to mount NetWare file server volumes and to access them just like
1889 any other Unix directory. For details, please read the file
1890 <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
1891 the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
1893 You do not have to say Y here if you want your Linux box to act as a
1894 file *server* for Novell NetWare clients.
1896 General information about how to connect Linux, Windows machines and
1897 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1899 To compile this as a module, choose M here: the module will be called
1900 ncpfs. Say N unless you are connected to a Novell network.
1902 source "fs/ncpfs/Kconfig"
1905 tristate "Coda file system support (advanced network fs)"
1908 Coda is an advanced network file system, similar to NFS in that it
1909 enables you to mount file systems of a remote server and access them
1910 with regular Unix commands as if they were sitting on your hard
1911 disk. Coda has several advantages over NFS: support for
1912 disconnected operation (e.g. for laptops), read/write server
1913 replication, security model for authentication and encryption,
1914 persistent client caches and write back caching.
1916 If you say Y here, your Linux box will be able to act as a Coda
1917 *client*. You will need user level code as well, both for the
1918 client and server. Servers are currently user level, i.e. they need
1919 no kernel support. Please read
1920 <file:Documentation/filesystems/coda.txt> and check out the Coda
1921 home page <http://www.coda.cs.cmu.edu/>.
1923 To compile the coda client support as a module, choose M here: the
1924 module will be called coda.
1926 config CODA_FS_OLD_API
1927 bool "Use 96-bit Coda file identifiers"
1930 A new kernel-userspace API had to be introduced for Coda v6.0
1931 to support larger 128-bit file identifiers as needed by the
1932 new realms implementation.
1934 However this new API is not backward compatible with older
1935 clients. If you really need to run the old Coda userspace
1936 cache manager then say Y.
1938 For most cases you probably want to say N.
1941 # for fs/nls/Config.in
1942 tristate "Andrew File System support (AFS) (Experimental)"
1943 depends on INET && EXPERIMENTAL
1946 If you say Y here, you will get an experimental Andrew File System
1947 driver. It currently only supports unsecured read-only AFS access.
1949 See <file:Documentation/filesystems/afs.txt> for more intormation.
1954 bool "Provide AFS client caching support"
1955 depends on AFS_FS && FSCACHE && EXPERIMENTAL
1957 Say Y here if you want AFS data to be cached locally on through the
1958 generic filesystem cache manager
1964 tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
1965 depends on INET && EXPERIMENTAL
1967 If you say Y here, you will get experimental support for
1968 Plan 9 resource sharing via the 9P2000 protocol.
1970 See <http://v9fs.sf.net> for more information.
1976 menu "Partition Types"
1978 source "fs/partitions/Kconfig"
1982 source "fs/nls/Kconfig"