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
33 Posix Access Control Lists (ACLs) support permissions for users and
34 groups beyond the owner/group/world scheme.
36 To learn more about Access Control Lists, visit the Posix ACLs for
37 Linux website <http://acl.bestbits.at/>.
39 If you don't know what Access Control Lists are, say N
41 config EXT2_FS_SECURITY
42 bool "Ext2 Security Labels"
43 depends on EXT2_FS_XATTR
45 Security labels support alternative access control models
46 implemented by security modules like SELinux. This option
47 enables an extended attribute handler for file security
48 labels in the ext2 filesystem.
50 If you are not using a security module that requires using
51 extended attributes for file security labels, say N.
54 tristate "Ext3 journalling file system support"
56 This is the journaling version of the Second extended file system
57 (often called ext3), the de facto standard Linux file system
58 (method to organize files on a storage device) for hard disks.
60 The journaling code included in this driver means you do not have
61 to run e2fsck (file system checker) on your file systems after a
62 crash. The journal keeps track of any changes that were being made
63 at the time the system crashed, and can ensure that your file system
64 is consistent without the need for a lengthy check.
66 Other than adding the journal to the file system, the on-disk format
67 of ext3 is identical to ext2. It is possible to freely switch
68 between using the ext3 driver and the ext2 driver, as long as the
69 file system has been cleanly unmounted, or e2fsck is run on the file
72 To add a journal on an existing ext2 file system or change the
73 behavior of ext3 file systems, you can use the tune2fs utility ("man
74 tune2fs"). To modify attributes of files and directories on ext3
75 file systems, use chattr ("man chattr"). You need to be using
76 e2fsprogs version 1.20 or later in order to create ext3 journals
77 (available at <http://sourceforge.net/projects/e2fsprogs/>).
79 To compile this file system support as a module, choose M here: the
80 module will be called ext3. Be aware however that the file system
81 of your root partition (the one containing the directory /) cannot
82 be compiled as a module, and so this may be dangerous.
85 bool "Ext3 extended attributes"
89 Extended attributes are name:value pairs associated with inodes by
90 the kernel or by users (see the attr(5) manual page, or visit
91 <http://acl.bestbits.at/> for details).
95 You need this for POSIX ACL support on ext3.
97 config EXT3_FS_POSIX_ACL
98 bool "Ext3 POSIX Access Control Lists"
99 depends on EXT3_FS_XATTR
101 Posix Access Control Lists (ACLs) support permissions for users and
102 groups beyond the owner/group/world scheme.
104 To learn more about Access Control Lists, visit the Posix ACLs for
105 Linux website <http://acl.bestbits.at/>.
107 If you don't know what Access Control Lists are, say N
109 config EXT3_FS_SECURITY
110 bool "Ext3 Security Labels"
111 depends on EXT3_FS_XATTR
113 Security labels support alternative access control models
114 implemented by security modules like SELinux. This option
115 enables an extended attribute handler for file security
116 labels in the ext3 filesystem.
118 If you are not using a security module that requires using
119 extended attributes for file security labels, say N.
122 # CONFIG_JBD could be its own option (even modular), but until there are
123 # other users than ext3, we will simply make it be the same as CONFIG_EXT3_FS
124 # dep_tristate ' Journal Block Device support (JBD for ext3)' CONFIG_JBD $CONFIG_EXT3_FS
128 This is a generic journaling layer for block devices. It is
129 currently used by the ext3 file system, but it could also be used to
130 add journal support to other file systems or block devices such as
133 If you are using the ext3 file system, you need to say Y here. If
134 you are not using ext3 then you will probably want to say N.
136 To compile this device as a module, choose M here: the module will be
137 called jbd. If you are compiling ext3 into the kernel, you cannot
138 compile this code as a module.
141 bool "JBD (ext3) debugging support"
144 If you are using the ext3 journaled file system (or potentially any
145 other file system/device using JBD), this option allows you to
146 enable debugging output while the system is running, in order to
147 help track down any problems you are having. By default the
148 debugging output will be turned off.
150 If you select Y here, then you will be able to turn on debugging
151 with "echo N > /proc/sys/fs/jbd-debug", where N is a number between
152 1 and 5, the higher the number, the more debugging output is
153 generated. To turn debugging off again, do
154 "echo 0 > /proc/sys/fs/jbd-debug".
157 # Meta block cache for Extended Attributes (ext2/ext3)
159 depends on EXT2_FS_XATTR || EXT3_FS_XATTR
160 default y if EXT2_FS=y || EXT3_FS=y
161 default m if EXT2_FS=m || EXT3_FS=m
164 tristate "Reiserfs support"
166 Stores not just filenames but the files themselves in a balanced
167 tree. Uses journaling.
169 Balanced trees are more efficient than traditional file system
170 architectural foundations.
172 In general, ReiserFS is as fast as ext2, but is very efficient with
173 large directories and small files. Additional patches are needed
174 for NFS and quotas, please see <http://www.namesys.com/> for links.
176 It is more easily extended to have features currently found in
177 database and keyword search systems than block allocation based file
178 systems are. The next version will be so extended, and will support
179 plugins consistent with our motto ``It takes more than a license to
180 make source code open.''
182 Read <http://www.namesys.com/> to learn more about reiserfs.
184 Sponsored by Threshold Networks, Emusic.com, and Bigstorage.com.
186 If you like it, you can pay us to add new features to it that you
187 need, buy a support contract, or pay us to port it to another OS.
189 config REISERFS_CHECK
190 bool "Enable reiserfs debug mode"
191 depends on REISERFS_FS
193 If you set this to Y, then ReiserFS will perform every check it can
194 possibly imagine of its internal consistency throughout its
195 operation. It will also go substantially slower. More than once we
196 have forgotten that this was on, and then gone despondent over the
197 latest benchmarks.:-) Use of this option allows our team to go all
198 out in checking for consistency when debugging without fear of its
199 effect on end users. If you are on the verge of sending in a bug
200 report, say Y and you might get a useful error message. Almost
201 everyone should say N.
203 config REISERFS_PROC_INFO
204 bool "Stats in /proc/fs/reiserfs"
205 depends on REISERFS_FS
207 Create under /proc/fs/reiserfs a hierarchy of files, displaying
208 various ReiserFS statistics and internal data at the expense of
209 making your kernel or module slightly larger (+8 KB). This also
210 increases the amount of kernel memory required for each mount.
211 Almost everyone but ReiserFS developers and people fine-tuning
212 reiserfs or tracing problems should say N.
214 config REISERFS_FS_XATTR
215 bool "ReiserFS extended attributes"
216 depends on REISERFS_FS
218 Extended attributes are name:value pairs associated with inodes by
219 the kernel or by users (see the attr(5) manual page, or visit
220 <http://acl.bestbits.at/> for details).
224 config REISERFS_FS_POSIX_ACL
225 bool "ReiserFS POSIX Access Control Lists"
226 depends on REISERFS_FS_XATTR
228 Posix Access Control Lists (ACLs) support permissions for users and
229 groups beyond the owner/group/world scheme.
231 To learn more about Access Control Lists, visit the Posix ACLs for
232 Linux website <http://acl.bestbits.at/>.
234 If you don't know what Access Control Lists are, say N
236 config REISERFS_FS_SECURITY
237 bool "ReiserFS Security Labels"
238 depends on REISERFS_FS_XATTR
240 Security labels support alternative access control models
241 implemented by security modules like SELinux. This option
242 enables an extended attribute handler for file security
243 labels in the ReiserFS filesystem.
245 If you are not using a security module that requires using
246 extended attributes for file security labels, say N.
249 tristate "JFS filesystem support"
252 This is a port of IBM's Journaled Filesystem . More information is
253 available in the file Documentation/filesystems/jfs.txt.
255 If you do not intend to use the JFS filesystem, say N.
258 bool "JFS POSIX Access Control Lists"
261 Posix Access Control Lists (ACLs) support permissions for users and
262 groups beyond the owner/group/world scheme.
264 To learn more about Access Control Lists, visit the Posix ACLs for
265 Linux website <http://acl.bestbits.at/>.
267 If you don't know what Access Control Lists are, say N
273 If you are experiencing any problems with the JFS filesystem, say
274 Y here. This will result in additional debugging messages to be
275 written to the system log. Under normal circumstances, this
276 results in very little overhead.
278 config JFS_STATISTICS
279 bool "JFS statistics"
282 Enabling this option will cause statistics from the JFS file system
283 to be made available to the user in the /proc/fs/jfs/ directory.
286 # Posix ACL utility routines (for now, only ext2/ext3/jfs/reiserfs)
288 # NOTE: you can implement Posix ACLs without these helpers (XFS does).
289 # Never use this symbol for ifdefs.
292 depends on EXT2_FS_POSIX_ACL || EXT3_FS_POSIX_ACL || JFS_POSIX_ACL || REISERFS_FS_POSIX_ACL || NFSD_V4
296 tristate "XFS filesystem support"
298 XFS is a high performance journaling filesystem which originated
299 on the SGI IRIX platform. It is completely multi-threaded, can
300 support large files and large filesystems, extended attributes,
301 variable block sizes, is extent based, and makes extensive use of
302 Btrees (directories, extents, free space) to aid both performance
305 Refer to the documentation at <http://oss.sgi.com/projects/xfs/>
306 for complete details. This implementation is on-disk compatible
307 with the IRIX version of XFS.
309 To compile this file system support as a module, choose M here: the
310 module will be called xfs. Be aware, however, that if the file
311 system of your root partition is compiled as a module, you'll need
312 to use an initial ramdisk (initrd) to boot.
315 bool "Realtime support (EXPERIMENTAL)"
316 depends on XFS_FS && EXPERIMENTAL
318 If you say Y here you will be able to mount and use XFS filesystems
319 which contain a realtime subvolume. The realtime subvolume is a
320 separate area of disk space where only file data is stored. The
321 realtime subvolume is designed to provide very deterministic
322 data rates suitable for media streaming applications.
324 See the xfs man page in section 5 for a bit more information.
326 This feature is unsupported at this time, is not yet fully
327 functional, and may cause serious problems.
335 If you say Y here, you will be able to set limits for disk usage on
336 a per user and/or a per group basis under XFS. XFS considers quota
337 information as filesystem metadata and uses journaling to provide a
338 higher level guarantee of consistency. The on-disk data format for
339 quota is also compatible with the IRIX version of XFS, allowing a
340 filesystem to be migrated between Linux and IRIX without any need
343 If unsure, say N. More comprehensive documentation can be found in
344 README.quota in the xfsprogs package. XFS quota can be used either
345 with or without the generic quota support enabled (CONFIG_QUOTA) -
346 they are completely independent subsystems.
349 bool "Security Label support"
352 Security labels support alternative access control models
353 implemented by security modules like SELinux. This option
354 enables an extended attribute namespace for inode security
355 labels in the XFS filesystem.
357 If you are not using a security module that requires using
358 extended attributes for inode security labels, say N.
361 bool "POSIX ACL support"
364 POSIX Access Control Lists (ACLs) support permissions for users and
365 groups beyond the owner/group/world scheme.
367 To learn more about Access Control Lists, visit the POSIX ACLs for
368 Linux website <http://acl.bestbits.at/>.
370 If you don't know what Access Control Lists are, say N.
373 tristate "Minix fs support"
375 Minix is a simple operating system used in many classes about OS's.
376 The minix file system (method to organize files on a hard disk
377 partition or a floppy disk) was the original file system for Linux,
378 but has been superseded by the second extended file system ext2fs.
379 You don't want to use the minix file system on your hard disk
380 because of certain built-in restrictions, but it is sometimes found
381 on older Linux floppy disks. This option will enlarge your kernel
382 by about 28 KB. If unsure, say N.
384 To compile this file system support as a module, choose M here: the
385 module will be called minix. Note that the file system of your root
386 partition (the one containing the directory /) cannot be compiled as
390 tristate "ROM file system support"
392 This is a very small read-only file system mainly intended for
393 initial ram disks of installation disks, but it could be used for
394 other read-only media as well. Read
395 <file:Documentation/filesystems/romfs.txt> for details.
397 To compile this file system support as a module, choose M here: the
398 module will be called romfs. Note that the file system of your
399 root partition (the one containing the directory /) cannot be a
402 If you don't know whether you need it, then you don't need it:
408 If you say Y here, you will be able to set per user limits for disk
409 usage (also called disk quotas). Currently, it works for the
410 ext2, ext3, and reiserfs file system. ext3 also supports journalled
411 quotas for which you don't need to run quotacheck(8) after an unclean
412 shutdown. You need additional software in order to use quota support
413 (you can download sources from
414 <http://www.sf.net/projects/linuxquota/>). For further details, read
415 the Quota mini-HOWTO, available from
416 <http://www.tldp.org/docs.html#howto>, or the documentation provided
417 with the quota tools. Probably the quota support is only useful for
418 multi user systems. If unsure, say N.
421 tristate "Old quota format support"
424 This quota format was (is) used by kernels earlier than 2.4.22. If
425 you have quota working and you don't want to convert to new quota
429 tristate "Quota format v2 support"
432 This quota format allows using quotas with 32-bit UIDs/GIDs. If you
433 need this functionality say Y here. Note that you will need recent
434 quota utilities (>= 3.01) for new quota format with this kernel.
438 depends on XFS_QUOTA || QUOTA
442 bool "Dnotify support" if EMBEDDED
445 Dnotify is a directory-based per-fd file change notification system
446 that uses signals to communicate events to user-space. There exist
447 superior alternatives, but some applications may still rely on
450 Because of this, if unsure, say Y.
453 tristate "Kernel automounter support"
455 The automounter is a tool to automatically mount remote file systems
456 on demand. This implementation is partially kernel-based to reduce
457 overhead in the already-mounted case; this is unlike the BSD
458 automounter (amd), which is a pure user space daemon.
460 To use the automounter you need the user-space tools from the autofs
461 package; you can find the location in <file:Documentation/Changes>.
462 You also want to answer Y to "NFS file system support", below.
464 If you want to use the newer version of the automounter with more
465 features, say N here and say Y to "Kernel automounter v4 support",
468 To compile this support as a module, choose M here: the module will be
471 If you are not a part of a fairly large, distributed network, you
472 probably do not need an automounter, and can say N here.
475 tristate "Kernel automounter version 4 support (also supports v3)"
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
483 <ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4/>; you also
484 want to answer Y to "NFS file system support", below.
486 To compile this support as a module, choose M here: the module will be
487 called autofs4. You will need to add "alias autofs autofs4" to your
488 modules configuration file.
490 If you are not a part of a fairly large, distributed network or
491 don't have a laptop which needs to dynamically reconfigure to the
492 local network, you probably do not need an automounter, and can say
495 menu "CD-ROM/DVD Filesystems"
498 tristate "ISO 9660 CDROM file system support"
500 This is the standard file system used on CD-ROMs. It was previously
501 known as "High Sierra File System" and is called "hsfs" on other
502 Unix systems. The so-called Rock-Ridge extensions which allow for
503 long Unix filenames and symbolic links are also supported by this
504 driver. If you have a CD-ROM drive and want to do more with it than
505 just listen to audio CDs and watch its LEDs, say Y (and read
506 <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO,
507 available from <http://www.tldp.org/docs.html#howto>), thereby
508 enlarging your kernel by about 27 KB; otherwise say N.
510 To compile this file system support as a module, choose M here: the
511 module will be called isofs.
514 bool "Microsoft Joliet CDROM extensions"
515 depends on ISO9660_FS
518 Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system
519 which allows for long filenames in unicode format (unicode is the
520 new 16 bit character code, successor to ASCII, which encodes the
521 characters of almost all languages of the world; see
522 <http://www.unicode.org/> for more information). Say Y here if you
523 want to be able to read Joliet CD-ROMs under Linux.
526 bool "Transparent decompression extension"
527 depends on ISO9660_FS
530 This is a Linux-specific extension to RockRidge which lets you store
531 data in compressed form on a CD-ROM and have it transparently
532 decompressed when the CD-ROM is accessed. See
533 <http://www.kernel.org/pub/linux/utils/fs/zisofs/> for the tools
534 necessary to create such a filesystem. Say Y here if you want to be
535 able to read such compressed CD-ROMs.
538 # for fs/nls/Config.in
544 tristate "UDF file system support"
546 This is the new file system used on some CD-ROMs and DVDs. Say Y if
547 you intend to mount DVD discs or CDRW's written in packet mode, or
548 if written to by other UDF utilities, such as DirectCD.
549 Please read <file:Documentation/filesystems/udf.txt>.
551 To compile this file system support as a module, choose M here: the
552 module will be called udf.
559 depends on (UDF_FS=m && NLS) || (UDF_FS=y && NLS=y)
563 menu "DOS/FAT/NT Filesystems"
569 If you want to use one of the FAT-based file systems (the MS-DOS,
570 VFAT (Windows 95) and UMSDOS (used to run Linux on top of an
571 ordinary DOS partition) file systems), then you must say Y or M here
572 to include FAT support. You will then be able to mount partitions or
573 diskettes with FAT-based file systems and transparently access the
574 files on them, i.e. MSDOS files will look and behave just like all
577 This FAT support is not a file system in itself, it only provides
578 the foundation for the other file systems. You will have to say Y or
579 M to at least one of "MSDOS fs support" or "VFAT fs support" in
580 order to make use of it.
582 Another way to read and write MSDOS floppies and hard drive
583 partitions from within Linux (but not transparently) is with the
584 mtools ("man mtools") program suite. You don't need to say Y here in
587 If you need to move large files on floppies between a DOS and a
588 Linux box, say Y here, mount the floppy under Linux with an MSDOS
589 file system and use GNU tar's M option. GNU tar is a program
590 available for Unix and DOS ("man tar" or "info tar").
592 It is now also becoming possible to read and write compressed FAT
593 file systems; read <file:Documentation/filesystems/fat_cvf.txt> for
596 The FAT support will enlarge your kernel by about 37 KB. If unsure,
599 To compile this as a module, choose M here: the module will be called
600 fat. Note that if you compile the FAT support as a module, you
601 cannot compile any of the FAT-based file systems into the kernel
602 -- they will have to be modules as well.
603 The file system of your root partition (the one containing the
604 directory /) cannot be a module, so don't say M here if you intend
605 to use UMSDOS as your root file system.
608 tristate "MSDOS fs support"
611 This allows you to mount MSDOS partitions of your hard drive (unless
612 they are compressed; to access compressed MSDOS partitions under
613 Linux, you can either use the DOS emulator DOSEMU, described in the
614 DOSEMU-HOWTO, available from
615 <http://www.tldp.org/docs.html#howto>, or try dmsdosfs in
616 <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you
617 intend to use dosemu with a non-compressed MSDOS partition, say Y
618 here) and MSDOS floppies. This means that file access becomes
619 transparent, i.e. the MSDOS files look and behave just like all
622 If you want to use UMSDOS, the Unix-like file system on top of a
623 DOS file system, which allows you to run Linux from within a DOS
624 partition without repartitioning, you'll have to say Y or M here.
626 If you have Windows 95 or Windows NT installed on your MSDOS
627 partitions, you should use the VFAT file system (say Y to "VFAT fs
628 support" below), or you will not be able to see the long filenames
629 generated by Windows 95 / Windows NT.
631 This option will enlarge your kernel by about 7 KB. If unsure,
632 answer Y. This will only work if you said Y to "DOS FAT fs support"
633 as well. To compile this as a module, choose M here: the module will
637 tristate "VFAT (Windows-95) fs support"
640 This option provides support for normal Windows file systems with
641 long filenames. That includes non-compressed FAT-based file systems
642 used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
643 programs from the mtools package.
645 You cannot use the VFAT file system for your Linux root partition
646 (the one containing the directory /); use UMSDOS instead if you
647 want to run Linux from within a DOS partition (i.e. say Y to
648 "Unix like fs on top of std MSDOS fs", below).
650 The VFAT support enlarges your kernel by about 10 KB and it only
651 works if you said Y to the "DOS FAT fs support" above. Please read
652 the file <file:Documentation/filesystems/vfat.txt> for details. If
655 To compile this as a module, choose M here: the module will be called
658 config FAT_DEFAULT_CODEPAGE
659 int "Default codepage for FAT"
660 depends on MSDOS_FS || VFAT_FS
663 This option should be set to the codepage of your FAT filesystems.
664 It can be overridden with the "codepage" mount option.
665 See <file:Documentation/filesystems/vfat.txt> for more information.
667 config FAT_DEFAULT_IOCHARSET
668 string "Default iocharset for FAT"
672 Set this to the default input/output character set you'd
673 like FAT to use. It should probably match the character set
674 that most of your FAT filesystems use, and can be overridden
675 with the "iocharset" mount option for FAT filesystems.
676 Note that "utf8" is not recommended for FAT filesystems.
677 If unsure, you shouldn't set "utf8" here.
678 See <file:Documentation/filesystems/vfat.txt> for more information.
681 #dep_tristate ' UMSDOS: Unix-like file system on top of standard MSDOS fs' CONFIG_UMSDOS_FS $CONFIG_MSDOS_FS
682 # UMSDOS is temprory broken
685 Say Y here if you want to run Linux from within an existing DOS
686 partition of your hard drive. The advantage of this is that you can
687 get away without repartitioning your hard drive (which often implies
688 backing everything up and restoring afterwards) and hence you're
689 able to quickly try out Linux or show it to your friends; the
690 disadvantage is that Linux becomes susceptible to DOS viruses and
691 that UMSDOS is somewhat slower than ext2fs. Another use of UMSDOS
692 is to write files with long unix filenames to MSDOS floppies; it
693 also allows Unix-style soft-links and owner/permissions of files on
694 MSDOS floppies. You will need a program called umssync in order to
695 make use of UMSDOS; read
696 <file:Documentation/filesystems/umsdos.txt>.
698 To get utilities for initializing/checking UMSDOS file system, or
699 latest patches and/or information, visit the UMSDOS home page at
700 <http://www.voyager.hr/~mnalis/umsdos/>.
702 This option enlarges your kernel by about 28 KB and it only works if
703 you said Y to both "DOS FAT fs support" and "MSDOS fs support"
704 above. To compile this as a module, choose M here: the module will be
705 called umsdos. Note that the file system of your root partition
706 (the one containing the directory /) cannot be a module, so saying M
707 could be dangerous. If unsure, say N.
710 tristate "NTFS file system support"
713 NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003.
715 Saying Y or M here enables read support. There is partial, but
716 safe, write support available. For write support you must also
717 say Y to "NTFS write support" below.
719 There are also a number of user-space tools available, called
720 ntfsprogs. These include ntfsundelete and ntfsresize, that work
721 without NTFS support enabled in the kernel.
723 This is a rewrite from scratch of Linux NTFS support and replaced
724 the old NTFS code starting with Linux 2.5.11. A backport to
725 the Linux 2.4 kernel series is separately available as a patch
726 from the project web site.
728 For more information see <file:Documentation/filesystems/ntfs.txt>
729 and <http://linux-ntfs.sourceforge.net/>.
731 To compile this file system support as a module, choose M here: the
732 module will be called ntfs.
734 If you are not using Windows NT, 2000, XP or 2003 in addition to
735 Linux on your computer it is safe to say N.
738 bool "NTFS debugging support"
741 If you are experiencing any problems with the NTFS file system, say
742 Y here. This will result in additional consistency checks to be
743 performed by the driver as well as additional debugging messages to
744 be written to the system log. Note that debugging messages are
745 disabled by default. To enable them, supply the option debug_msgs=1
746 at the kernel command line when booting the kernel or as an option
747 to insmod when loading the ntfs module. Once the driver is active,
748 you can enable debugging messages by doing (as root):
749 echo 1 > /proc/sys/fs/ntfs-debug
750 Replacing the "1" with "0" would disable debug messages.
752 If you leave debugging messages disabled, this results in little
753 overhead, but enabling debug messages results in very significant
754 slowdown of the system.
756 When reporting bugs, please try to have available a full dump of
757 debugging messages while the misbehaviour was occurring.
760 bool "NTFS write support"
763 This enables the partial, but safe, write support in the NTFS driver.
765 The only supported operation is overwriting existing files, without
766 changing the file length. No file or directory creation, deletion or
767 renaming is possible. Note only non-resident files can be written to
768 so you may find that some very small files (<500 bytes or so) cannot
771 While we cannot guarantee that it will not damage any data, we have
772 so far not received a single report where the driver would have
773 damaged someones data so we assume it is perfectly safe to use.
775 Note: While write support is safe in this version (a rewrite from
776 scratch of the NTFS support), it should be noted that the old NTFS
777 write support, included in Linux 2.5.10 and before (since 1997),
780 This is currently useful with TopologiLinux. TopologiLinux is run
781 on top of any DOS/Microsoft Windows system without partitioning your
782 hard disk. Unlike other Linux distributions TopologiLinux does not
783 need its own partition. For more information see
784 <http://topologi-linux.sourceforge.net/>
786 It is perfectly safe to say N here.
790 menu "Pseudo filesystems"
793 bool "/proc file system support"
795 This is a virtual file system providing information about the status
796 of the system. "Virtual" means that it doesn't take up any space on
797 your hard disk: the files are created on the fly by the kernel when
798 you try to access them. Also, you cannot read the files with older
799 version of the program less: you need to use more or cat.
801 It's totally cool; for example, "cat /proc/interrupts" gives
802 information about what the different IRQs are used for at the moment
803 (there is a small number of Interrupt ReQuest lines in your computer
804 that are used by the attached devices to gain the CPU's attention --
805 often a source of trouble if two devices are mistakenly configured
806 to use the same IRQ). The program procinfo to display some
807 information about your system gathered from the /proc file system.
809 Before you can use the /proc file system, it has to be mounted,
810 meaning it has to be given a location in the directory hierarchy.
811 That location should be /proc. A command such as "mount -t proc proc
812 /proc" or the equivalent line in /etc/fstab does the job.
814 The /proc file system is explained in the file
815 <file:Documentation/filesystems/proc.txt> and on the proc(5) manpage
818 This option will enlarge your kernel by about 67 KB. Several
819 programs depend on this, so everyone should say Y here.
822 bool "/proc/kcore support" if !ARM
823 depends on PROC_FS && MMU
826 bool "sysfs file system support" if EMBEDDED
829 The sysfs filesystem is a virtual filesystem that the kernel uses to
830 export internal kernel objects, their attributes, and their
831 relationships to one another.
833 Users can use sysfs to ascertain useful information about the running
834 kernel, such as the devices the kernel has discovered on each bus and
835 which driver each is bound to. sysfs can also be used to tune devices
836 and other kernel subsystems.
838 Some system agents rely on the information in sysfs to operate.
839 /sbin/hotplug uses device and object attributes in sysfs to assist in
840 delegating policy decisions, like persistantly naming devices.
842 sysfs is currently used by the block subsystem to mount the root
843 partition. If sysfs is disabled you must specify the boot device on
844 the kernel boot command line via its major and minor numbers. For
845 example, "root=03:01" for /dev/hda1.
847 Designers of embedded systems may wish to say N here to conserve space.
850 bool "/dev file system support (OBSOLETE)"
851 depends on EXPERIMENTAL
853 This is support for devfs, a virtual file system (like /proc) which
854 provides the file system interface to device drivers, normally found
855 in /dev. Devfs does not depend on major and minor number
856 allocations. Device drivers register entries in /dev which then
857 appear automatically, which means that the system administrator does
858 not have to create character and block special device files in the
859 /dev directory using the mknod command (or MAKEDEV script) anymore.
861 This is work in progress. If you want to use this, you *must* read
862 the material in <file:Documentation/filesystems/devfs/>, especially
863 the file README there.
865 Note that devfs no longer manages /dev/pts! If you are using UNIX98
866 ptys, you will also need to mount the /dev/pts filesystem (devpts).
868 Note that devfs has been obsoleted by udev,
869 <http://www.kernel.org/pub/linux/utils/kernel/hotplug/>.
870 It has been stripped down to a bare minimum and is only provided for
871 legacy installations that use its naming scheme which is
872 unfortunately different from the names normal Linux installations
878 bool "Automatically mount at boot"
881 This option appears if you have CONFIG_DEVFS_FS enabled. Setting
882 this to 'Y' will make the kernel automatically mount devfs onto /dev
883 when the system is booted, before the init thread is started.
884 You can override this with the "devfs=nomount" boot option.
892 If you say Y here, then the /dev file system code will generate
893 debugging messages. See the file
894 <file:Documentation/filesystems/devfs/boot-options> for more
899 config DEVPTS_FS_XATTR
900 bool "/dev/pts Extended Attributes"
901 depends on UNIX98_PTYS
903 Extended attributes are name:value pairs associated with inodes by
904 the kernel or by users (see the attr(5) manual page, or visit
905 <http://acl.bestbits.at/> for details).
909 config DEVPTS_FS_SECURITY
910 bool "/dev/pts Security Labels"
911 depends on DEVPTS_FS_XATTR
913 Security labels support alternative access control models
914 implemented by security modules like SELinux. This option
915 enables an extended attribute handler for file security
916 labels in the /dev/pts filesystem.
918 If you are not using a security module that requires using
919 extended attributes for file security labels, say N.
922 bool "Virtual memory file system support (former shm fs)"
924 Tmpfs is a file system which keeps all files in virtual memory.
926 Everything in tmpfs is temporary in the sense that no files will be
927 created on your hard drive. The files live in memory and swap
928 space. If you unmount a tmpfs instance, everything stored therein is
931 See <file:Documentation/filesystems/tmpfs.txt> for details.
934 bool "tmpfs Extended Attributes"
937 Extended attributes are name:value pairs associated with inodes by
938 the kernel or by users (see the attr(5) manual page, or visit
939 <http://acl.bestbits.at/> for details).
943 config TMPFS_SECURITY
944 bool "tmpfs Security Labels"
945 depends on TMPFS_XATTR
947 Security labels support alternative access control models
948 implemented by security modules like SELinux. This option
949 enables an extended attribute handler for file security
950 labels in the tmpfs filesystem.
951 If you are not using a security module that requires using
952 extended attributes for file security labels, say N.
955 bool "HugeTLB file system support"
956 depends X86 || IA64 || PPC64 || SPARC64 || SUPERH || X86_64 || BROKEN
965 Ramfs is a file system which keeps all files in RAM. It allows
966 read and write access.
968 It is more of an programming example than a useable file system. If
969 you need a file system which lives in RAM with limit checking use
972 To compile this as a module, choose M here: the module will be called
976 tristate "Relayfs file system support"
978 Relayfs is a high-speed data relay filesystem designed to provide
979 an efficient mechanism for tools and facilities to relay large
980 amounts of data from kernel space to user space. It's not useful
981 on its own, and should only be enabled if other facilities that
982 need it are enabled, such as for example klog or the Linux Trace
985 See <file:Documentation/filesystems/relayfs.txt> for further
988 This file system is also available as a module ( = code which can be
989 inserted in and removed from the running kernel whenever you want).
990 The module is called relayfs. If you want to compile it as a
991 module, say M here and read <file:Documentation/modules.txt>.
996 bool "Enable klog debugging support"
997 depends on RELAYFS_FS
999 If you say Y to this, a relayfs channel named klog will be created
1000 in the root of the relayfs file system. You can write to the klog
1001 channel using klog() or klog_raw() from within the kernel or
1002 kernel modules, and read from the klog channel by mounting relayfs
1003 and using read(2) to read from it (or using cat). If you're not
1006 config KLOG_CHANNEL_AUTOENABLE
1007 bool "Enable klog logging on startup"
1008 depends on KLOG_CHANNEL
1011 If you say Y to this, the klog channel will be automatically enabled
1012 on startup. Otherwise, to turn klog logging on, you need use
1013 sysctl (fs.relayfs.klog_enabled). This option is used in cases where
1014 you don't actually want the channel to be written to until it's
1015 enabled. If you're not sure, say Y.
1017 config KLOG_CHANNEL_SHIFT
1018 depends on KLOG_CHANNEL
1019 int "klog debugging channel size (14 => 16KB, 22 => 4MB)"
1023 Select klog debugging channel size as a power of 2.
1027 menu "Miscellaneous filesystems"
1030 tristate "ADFS file system support (EXPERIMENTAL)"
1031 depends on EXPERIMENTAL
1033 The Acorn Disc Filing System is the standard file system of the
1034 RiscOS operating system which runs on Acorn's ARM-based Risc PC
1035 systems and the Acorn Archimedes range of machines. If you say Y
1036 here, Linux will be able to read from ADFS partitions on hard drives
1037 and from ADFS-formatted floppy discs. If you also want to be able to
1038 write to those devices, say Y to "ADFS write support" below.
1040 The ADFS partition should be the first partition (i.e.,
1041 /dev/[hs]d?1) on each of your drives. Please read the file
1042 <file:Documentation/filesystems/adfs.txt> for further details.
1044 To compile this code as a module, choose M here: the module will be
1050 bool "ADFS write support (DANGEROUS)"
1053 If you say Y here, you will be able to write to ADFS partitions on
1054 hard drives and ADFS-formatted floppy disks. This is experimental
1055 codes, so if you're unsure, say N.
1058 tristate "Amiga FFS file system support (EXPERIMENTAL)"
1059 depends on EXPERIMENTAL
1061 The Fast File System (FFS) is the common file system used on hard
1062 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
1063 if you want to be able to read and write files from and to an Amiga
1064 FFS partition on your hard drive. Amiga floppies however cannot be
1065 read with this driver due to an incompatibility of the floppy
1066 controller used in an Amiga and the standard floppy controller in
1067 PCs and workstations. Read <file:Documentation/filesystems/affs.txt>
1068 and <file:fs/affs/Changes>.
1070 With this driver you can also mount disk files used by Bernd
1071 Schmidt's Un*X Amiga Emulator
1072 (<http://www.freiburg.linux.de/~uae/>).
1073 If you want to do this, you will also need to say Y or M to "Loop
1074 device support", above.
1076 To compile this file system support as a module, choose M here: the
1077 module will be called affs. If unsure, say N.
1080 tristate "Apple Macintosh file system support (EXPERIMENTAL)"
1081 depends on EXPERIMENTAL
1083 If you say Y here, you will be able to mount Macintosh-formatted
1084 floppy disks and hard drive partitions with full read-write access.
1085 Please read <file:fs/hfs/HFS.txt> to learn about the available mount
1088 To compile this file system support as a module, choose M here: the
1089 module will be called hfs.
1092 tristate "Apple Extended HFS file system support"
1095 If you say Y here, you will be able to mount extended format
1096 Macintosh-formatted hard drive partitions with full read-write access.
1098 This file system is often called HFS+ and was introduced with
1099 MacOS 8. It includes all Mac specific filesystem data such as
1100 data forks and creator codes, but it also has several UNIX
1101 style features such as file ownership and permissions.
1104 tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)"
1105 depends on EXPERIMENTAL
1108 The BeOS File System (BeFS) is the native file system of Be, Inc's
1109 BeOS. Notable features include support for arbitrary attributes
1110 on files and directories, and database-like indices on selected
1111 attributes. (Also note that this driver doesn't make those features
1112 available at this time). It is a 64 bit filesystem, so it supports
1113 extreemly large volumes and files.
1115 If you use this filesystem, you should also say Y to at least one
1116 of the NLS (native language support) options below.
1118 If you don't know what this is about, say N.
1120 To compile this as a module, choose M here: the module will be
1127 If you say Y here, you can use the 'debug' mount option to enable
1128 debugging output from the driver.
1131 tristate "BFS file system support (EXPERIMENTAL)"
1132 depends on EXPERIMENTAL
1134 Boot File System (BFS) is a file system used under SCO UnixWare to
1135 allow the bootloader access to the kernel image and other important
1136 files during the boot process. It is usually mounted under /stand
1137 and corresponds to the slice marked as "STAND" in the UnixWare
1138 partition. You should say Y if you want to read or write the files
1139 on your /stand slice from within Linux. You then also need to say Y
1140 to "UnixWare slices support", below. More information about the BFS
1141 file system is contained in the file
1142 <file:Documentation/filesystems/bfs.txt>.
1144 If you don't know what this is about, say N.
1146 To compile this as a module, choose M here: the module will be called
1147 bfs. Note that the file system of your root partition (the one
1148 containing the directory /) cannot be compiled as a module.
1153 tristate "EFS file system support (read only) (EXPERIMENTAL)"
1154 depends on EXPERIMENTAL
1156 EFS is an older file system used for non-ISO9660 CD-ROMs and hard
1157 disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
1158 uses the XFS file system for hard disk partitions however).
1160 This implementation only offers read-only access. If you don't know
1161 what all this is about, it's safe to say N. For more information
1162 about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
1164 To compile the EFS file system support as a module, choose M here: the
1165 module will be called efs.
1168 tristate "Journalling Flash File System (JFFS) support"
1171 JFFS is the Journaling Flash File System developed by Axis
1172 Communications in Sweden, aimed at providing a crash/powerdown-safe
1173 file system for disk-less embedded devices. Further information is
1174 available at (<http://developer.axis.com/software/jffs/>).
1176 config JFFS_FS_VERBOSE
1177 int "JFFS debugging verbosity (0 = quiet, 3 = noisy)"
1181 Determines the verbosity level of the JFFS debugging messages.
1184 bool "JFFS stats available in /proc filesystem"
1185 depends on JFFS_FS && PROC_FS
1187 Enabling this option will cause statistics from mounted JFFS file systems
1188 to be made available to the user in the /proc/fs/jffs/ directory.
1191 tristate "Journalling Flash File System v2 (JFFS2) support"
1195 JFFS2 is the second generation of the Journalling Flash File System
1196 for use on diskless embedded devices. It provides improved wear
1197 levelling, compression and support for hard links. You cannot use
1198 this on normal block devices, only on 'MTD' devices.
1200 Further information on the design and implementation of JFFS2 is
1201 available at <http://sources.redhat.com/jffs2/>.
1203 config JFFS2_FS_DEBUG
1204 int "JFFS2 debugging verbosity (0 = quiet, 2 = noisy)"
1208 This controls the amount of debugging messages produced by the JFFS2
1209 code. Set it to zero for use in production systems. For evaluation,
1210 testing and debugging, it's advisable to set it to one. This will
1211 enable a few assertions and will print debugging messages at the
1212 KERN_DEBUG loglevel, where they won't normally be visible. Level 2
1213 is unlikely to be useful - it enables extra debugging in certain
1214 areas which at one point needed debugging, but when the bugs were
1215 located and fixed, the detailed messages were relegated to level 2.
1217 If reporting bugs, please try to have available a full dump of the
1218 messages at debug level 1 while the misbehaviour was occurring.
1220 config JFFS2_FS_NAND
1221 bool "JFFS2 support for NAND flash"
1225 This enables the support for NAND flash in JFFS2. NAND is a newer
1226 type of flash chip design than the traditional NOR flash, with
1227 higher density but a handful of characteristics which make it more
1228 interesting for the file system to use.
1230 Say 'N' unless you have NAND flash.
1232 config JFFS2_COMPRESSION_OPTIONS
1233 bool "Advanced compression options for JFFS2"
1237 Enabling this option allows you to explicitly choose which
1238 compression modules, if any, are enabled in JFFS2. Removing
1239 compressors and mean you cannot read existing file systems,
1240 and enabling experimental compressors can mean that you
1241 write a file system which cannot be read by a standard kernel.
1243 If unsure, you should _definitely_ say 'N'.
1246 bool "JFFS2 ZLIB compression support" if JFFS2_COMPRESSION_OPTIONS
1252 Zlib is designed to be a free, general-purpose, legally unencumbered,
1253 lossless data-compression library for use on virtually any computer
1254 hardware and operating system. See http://www.gzip.org/zlib/ for
1255 further information.
1260 bool "JFFS2 RTIME compression support" if JFFS2_COMPRESSION_OPTIONS
1264 Rtime does manage to recompress already-compressed data. Say 'Y' if unsure.
1267 bool "JFFS2 RUBIN compression support" if JFFS2_COMPRESSION_OPTIONS
1271 RUBINMIPS and DYNRUBIN compressors. Say 'N' if unsure.
1274 prompt "JFFS2 default compression mode" if JFFS2_COMPRESSION_OPTIONS
1275 default JFFS2_CMODE_PRIORITY
1278 You can set here the default compression mode of JFFS2 from
1279 the avaiable compression modes. Don't touch if unsure.
1281 config JFFS2_CMODE_NONE
1282 bool "no compression"
1284 Uses no compression.
1286 config JFFS2_CMODE_PRIORITY
1289 Tries the compressors in a predefinied order and chooses the first
1292 config JFFS2_CMODE_SIZE
1293 bool "size (EXPERIMENTAL)"
1295 Tries all compressors and chooses the one which has the smallest
1301 tristate "Compressed ROM file system support (cramfs)"
1304 Saying Y here includes support for CramFs (Compressed ROM File
1305 System). CramFs is designed to be a simple, small, and compressed
1306 file system for ROM based embedded systems. CramFs is read-only,
1307 limited to 256MB file systems (with 16MB files), and doesn't support
1308 16/32 bits uid/gid, hard links and timestamps.
1310 See <file:Documentation/filesystems/cramfs.txt> and
1311 <file:fs/cramfs/README> for further information.
1313 To compile this as a module, choose M here: the module will be called
1314 cramfs. Note that the root file system (the one containing the
1315 directory /) cannot be compiled as a module.
1320 tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
1322 FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
1323 file system format. VERITAS VxFS(TM) is the standard file system
1324 of SCO UnixWare (and possibly others) and optionally available
1325 for Sunsoft Solaris, HP-UX and many other operating systems.
1326 Currently only readonly access is supported.
1328 NOTE: the file system type as used by mount(1), mount(2) and
1329 fstab(5) is 'vxfs' as it describes the file system format, not
1332 To compile this as a module, choose M here: the module will be
1333 called freevxfs. If unsure, say N.
1337 tristate "OS/2 HPFS file system support"
1339 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
1340 is the file system used for organizing files on OS/2 hard disk
1341 partitions. Say Y if you want to be able to read files from and
1342 write files to an OS/2 HPFS partition on your hard drive. OS/2
1343 floppies however are in regular MSDOS format, so you don't need this
1344 option in order to be able to read them. Read
1345 <file:Documentation/filesystems/hpfs.txt>.
1347 To compile this file system support as a module, choose M here: the
1348 module will be called hpfs. If unsure, say N.
1351 tristate "QNX4 file system support (read only)"
1353 This is the file system used by the real-time operating systems
1354 QNX 4 and QNX 6 (the latter is also called QNX RTP).
1355 Further information is available at <http://www.qnx.com/>.
1356 Say Y if you intend to mount QNX hard disks or floppies.
1357 Unless you say Y to "QNX4FS read-write support" below, you will
1358 only be able to read these file systems.
1360 To compile this file system support as a module, choose M here: the
1361 module will be called qnx4.
1363 If you don't know whether you need it, then you don't need it:
1367 bool "QNX4FS write support (DANGEROUS)"
1368 depends on QNX4FS_FS && EXPERIMENTAL
1370 Say Y if you want to test write support for QNX4 file systems.
1372 It's currently broken, so for now:
1376 tristate "System V/Xenix/V7/Coherent file system support"
1378 SCO, Xenix and Coherent are commercial Unix systems for Intel
1379 machines, and Version 7 was used on the DEC PDP-11. Saying Y
1380 here would allow you to read from their floppies and hard disk
1383 If you have floppies or hard disk partitions like that, it is likely
1384 that they contain binaries from those other Unix systems; in order
1385 to run these binaries, you will want to install linux-abi which is a
1386 a set of kernel modules that lets you run SCO, Xenix, Wyse,
1387 UnixWare, Dell Unix and System V programs under Linux. It is
1388 available via FTP (user: ftp) from
1389 <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
1390 NOTE: that will work only for binaries from Intel-based systems;
1391 PDP ones will have to wait until somebody ports Linux to -11 ;-)
1393 If you only intend to mount files from some other Unix over the
1394 network using NFS, you don't need the System V file system support
1395 (but you need NFS file system support obviously).
1397 Note that this option is generally not needed for floppies, since a
1398 good portable way to transport files and directories between unixes
1399 (and even other operating systems) is given by the tar program ("man
1400 tar" or preferably "info tar"). Note also that this option has
1401 nothing whatsoever to do with the option "System V IPC". Read about
1402 the System V file system in
1403 <file:Documentation/filesystems/sysv-fs.txt>.
1404 Saying Y here will enlarge your kernel by about 27 KB.
1406 To compile this as a module, choose M here: the module will be called
1409 If you haven't heard about all of this before, it's safe to say N.
1412 tristate "UFS file system support (read only)"
1414 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
1415 OpenBSD and NeXTstep) use a file system called UFS. Some System V
1416 Unixes can create and mount hard disk partitions and diskettes using
1417 this file system as well. Saying Y here will allow you to read from
1418 these partitions; if you also want to write to them, say Y to the
1419 experimental "UFS file system write support", below. Please read the
1420 file <file:Documentation/filesystems/ufs.txt> for more information.
1422 The recently released UFS2 variant (used in FreeBSD 5.x) is
1423 READ-ONLY supported.
1425 If you only intend to mount files from some other Unix over the
1426 network using NFS, you don't need the UFS file system support (but
1427 you need NFS file system support obviously).
1429 Note that this option is generally not needed for floppies, since a
1430 good portable way to transport files and directories between unixes
1431 (and even other operating systems) is given by the tar program ("man
1432 tar" or preferably "info tar").
1434 When accessing NeXTstep files, you may need to convert them from the
1435 NeXT character set to the Latin1 character set; use the program
1436 recode ("info recode") for this purpose.
1438 To compile the UFS file system support as a module, choose M here: the
1439 module will be called ufs.
1441 If you haven't heard about all of this before, it's safe to say N.
1444 bool "UFS file system write support (DANGEROUS)"
1445 depends on UFS_FS && EXPERIMENTAL
1447 Say Y here if you want to try writing to UFS partitions. This is
1448 experimental, so you should back up your UFS partitions beforehand.
1452 menu "Network File Systems"
1456 tristate "NFS file system support"
1461 If you are connected to some other (usually local) Unix computer
1462 (using SLIP, PLIP, PPP or Ethernet) and want to mount files residing
1463 on that computer (the NFS server) using the Network File Sharing
1464 protocol, say Y. "Mounting files" means that the client can access
1465 the files with usual UNIX commands as if they were sitting on the
1466 client's hard disk. For this to work, the server must run the
1467 programs nfsd and mountd (but does not need to have NFS file system
1468 support enabled in its kernel). NFS is explained in the Network
1469 Administrator's Guide, available from
1470 <http://www.tldp.org/docs.html#guide>, on its man page: "man
1471 nfs", and in the NFS-HOWTO.
1473 A superior but less widely used alternative to NFS is provided by
1474 the Coda file system; see "Coda file system support" below.
1476 If you say Y here, you should have said Y to TCP/IP networking also.
1477 This option would enlarge your kernel by about 27 KB.
1479 To compile this file system support as a module, choose M here: the
1480 module will be called nfs.
1482 If you are configuring a diskless machine which will mount its root
1483 file system over NFS at boot time, say Y here and to "Kernel
1484 level IP autoconfiguration" above and to "Root file system on NFS"
1485 below. You cannot compile this driver as a module in this case.
1486 There are two packages designed for booting diskless machines over
1487 the net: netboot, available from
1488 <http://ftp1.sourceforge.net/netboot/>, and Etherboot,
1489 available from <http://ftp1.sourceforge.net/etherboot/>.
1491 If you don't know what all this is about, say N.
1494 bool "Provide NFSv3 client support"
1497 Say Y here if you want your NFS client to be able to speak version
1498 3 of the NFS protocol.
1503 bool "Provide NFSv4 client support (EXPERIMENTAL)"
1504 depends on NFS_FS && EXPERIMENTAL
1505 select RPCSEC_GSS_KRB5
1507 Say Y here if you want your NFS client to be able to speak the newer
1508 version 4 of the NFS protocol.
1510 Note: Requires auxiliary userspace daemons which may be found on
1511 http://www.citi.umich.edu/projects/nfsv4/
1516 bool "Allow direct I/O on NFS files (EXPERIMENTAL)"
1517 depends on NFS_FS && EXPERIMENTAL
1519 This option enables applications to perform uncached I/O on files
1520 in NFS file systems using the O_DIRECT open() flag. When O_DIRECT
1521 is set for a file, its data is not cached in the system's page
1522 cache. Data is moved to and from user-level application buffers
1523 directly. Unlike local disk-based file systems, NFS O_DIRECT has
1524 no alignment restrictions.
1526 Unless your program is designed to use O_DIRECT properly, you are
1527 much better off allowing the NFS client to manage data caching for
1528 you. Misusing O_DIRECT can cause poor server performance or network
1529 storms. This kernel build option defaults OFF to avoid exposing
1530 system administrators unwittingly to a potentially hazardous
1533 For more details on NFS O_DIRECT, see fs/nfs/direct.c.
1535 If unsure, say N. This reduces the size of the NFS client, and
1536 causes open() to return EINVAL if a file residing in NFS is
1537 opened with the O_DIRECT flag.
1540 tristate "NFS server support"
1545 If you want your Linux box to act as an NFS *server*, so that other
1546 computers on your local network which support NFS can access certain
1547 directories on your box transparently, you have two options: you can
1548 use the self-contained user space program nfsd, in which case you
1549 should say N here, or you can say Y and use the kernel based NFS
1550 server. The advantage of the kernel based solution is that it is
1553 In either case, you will need support software; the respective
1554 locations are given in the file <file:Documentation/Changes> in the
1557 If you say Y here, you will get support for version 2 of the NFS
1558 protocol (NFSv2). If you also want NFSv3, say Y to the next question
1561 Please read the NFS-HOWTO, available from
1562 <http://www.tldp.org/docs.html#howto>.
1564 To compile the NFS server support as a module, choose M here: the
1565 module will be called nfsd. If unsure, say N.
1568 bool "Provide NFSv3 server support"
1571 If you would like to include the NFSv3 server as well as the NFSv2
1572 server, say Y here. If unsure, say Y.
1575 bool "Provide NFSv4 server support (EXPERIMENTAL)"
1576 depends on NFSD_V3 && EXPERIMENTAL
1579 If you would like to include the NFSv4 server as well as the NFSv2
1580 and NFSv3 servers, say Y here. This feature is experimental, and
1581 should only be used if you are interested in helping to test NFSv4.
1585 bool "Provide NFS server over TCP support"
1589 If you want your NFS server to support TCP connections, say Y here.
1590 TCP connections usually perform better than the default UDP when
1591 the network is lossy or congested. If unsure, say Y.
1594 bool "Root file system on NFS"
1595 depends on NFS_FS=y && IP_PNP
1597 If you want your Linux box to mount its whole root file system (the
1598 one containing the directory /) from some other computer over the
1599 net via NFS (presumably because your box doesn't have a hard disk),
1600 say Y. Read <file:Documentation/nfsroot.txt> for details. It is
1601 likely that in this case, you also want to say Y to "Kernel level IP
1602 autoconfiguration" so that your box can discover its network address
1605 Most people say N here.
1612 depends on NFSD_V3 || NFS_V3
1625 config RPCSEC_GSS_KRB5
1626 tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
1627 depends on SUNRPC && EXPERIMENTAL
1633 Provides for secure RPC calls by means of a gss-api
1634 mechanism based on Kerberos V5. This is required for
1637 Note: Requires an auxiliary userspace daemon which may be found on
1638 http://www.citi.umich.edu/projects/nfsv4/
1642 config RPCSEC_GSS_SPKM3
1643 tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
1644 depends on SUNRPC && EXPERIMENTAL
1650 Provides for secure RPC calls by means of a gss-api
1651 mechanism based on the SPKM3 public-key mechanism.
1653 Note: Requires an auxiliary userspace daemon which may be found on
1654 http://www.citi.umich.edu/projects/nfsv4/
1659 tristate "SMB file system support (to mount Windows shares etc.)"
1663 SMB (Server Message Block) is the protocol Windows for Workgroups
1664 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
1665 files and printers over local networks. Saying Y here allows you to
1666 mount their file systems (often called "shares" in this context) and
1667 access them just like any other Unix directory. Currently, this
1668 works only if the Windows machines use TCP/IP as the underlying
1669 transport protocol, and not NetBEUI. For details, read
1670 <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
1671 available from <http://www.tldp.org/docs.html#howto>.
1673 Note: if you just want your box to act as an SMB *server* and make
1674 files and printing services available to Windows clients (which need
1675 to have a TCP/IP stack), you don't need to say Y here; you can use
1676 the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
1679 General information about how to connect Linux, Windows machines and
1680 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1682 To compile the SMB support as a module, choose M here: the module will
1683 be called smbfs. Most people say N, however.
1685 config SMB_NLS_DEFAULT
1686 bool "Use a default NLS"
1689 Enabling this will make smbfs use nls translations by default. You
1690 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
1691 settings and you need to give the default nls for the SMB server as
1692 CONFIG_SMB_NLS_REMOTE.
1694 The nls settings can be changed at mount time, if your smbmount
1695 supports that, using the codepage and iocharset parameters.
1697 smbmount from samba 2.2.0 or later supports this.
1699 config SMB_NLS_REMOTE
1700 string "Default Remote NLS Option"
1701 depends on SMB_NLS_DEFAULT
1704 This setting allows you to specify a default value for which
1705 codepage the server uses. If this field is left blank no
1706 translations will be done by default. The local codepage/charset
1707 default to CONFIG_NLS_DEFAULT.
1709 The nls settings can be changed at mount time, if your smbmount
1710 supports that, using the codepage and iocharset parameters.
1712 smbmount from samba 2.2.0 or later supports this.
1715 tristate "CIFS support (advanced network filesystem for Samba, Window and other CIFS compliant servers)"
1719 This is the client VFS module for the Common Internet File System
1720 (CIFS) protocol which is the successor to the Server Message Block
1721 (SMB) protocol, the native file sharing mechanism for most early
1722 PC operating systems. The CIFS protocol is fully supported by
1723 file servers such as Windows 2000 (including Windows 2003, NT 4
1724 and Windows XP) as well by Samba (which provides excellent CIFS
1725 server support for Linux and many other operating systems). Currently
1726 you must use the smbfs client filesystem to access older SMB servers
1727 such as Windows 9x and OS/2.
1729 The intent of the cifs module is to provide an advanced
1730 network file system client for mounting to CIFS compliant servers,
1731 including support for dfs (hierarchical name space), secure per-user
1732 session establishment, safe distributed caching (oplock), optional
1733 packet signing, Unicode and other internationalization improvements,
1734 and optional Winbind (nsswitch) integration. You do not need to enable
1735 cifs if running only a (Samba) server. It is possible to enable both
1736 smbfs and cifs (e.g. if you are using CIFS for accessing Windows 2003
1737 and Samba 3 servers, and smbfs for accessing old servers). If you need
1738 to mount to Samba or Windows 2003 servers from this machine, say Y.
1741 bool "CIFS statistics"
1744 Enabling this option will cause statistics for each server share
1745 mounted by the cifs client to be displayed in /proc/fs/cifs/Stats
1748 bool "CIFS extended attributes (EXPERIMENTAL)"
1751 Extended attributes are name:value pairs associated with inodes by
1752 the kernel or by users (see the attr(5) manual page, or visit
1753 <http://acl.bestbits.at/> for details). CIFS maps the name of
1754 extended attributes beginning with the user namespace prefix
1755 to SMB/CIFS EAs. EAs are stored on Windows servers without the
1756 user namespace prefix, but their names are seen by Linux cifs clients
1757 prefaced by the user namespace prefix. The system namespace
1758 (used by some filesystems to store ACLs) is not supported at
1764 bool "CIFS POSIX Extensions (EXPERIMENTAL)"
1765 depends on CIFS_XATTR
1767 Enabling this option will cause the cifs client to attempt to
1768 negotiate a newer dialect with servers, such as Samba 3.0.5
1769 or later, that optionally can handle more POSIX like (rather
1770 than Windows like) file behavior. It also enables
1771 support for POSIX ACLs (getfacl and setfacl) to servers
1772 (such as Samba 3.10 and later) which can negotiate
1773 CIFS POSIX ACL support. If unsure, say N.
1775 config CIFS_EXPERIMENTAL
1776 bool "CIFS Experimental Features (EXPERIMENTAL)"
1779 Enables cifs features under testing. These features
1780 are highly experimental. If unsure, say N.
1783 tristate "NCP file system support (to mount NetWare volumes)"
1784 depends on IPX!=n || INET
1786 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
1787 used by Novell NetWare clients to talk to file servers. It is to
1788 IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
1789 to mount NetWare file server volumes and to access them just like
1790 any other Unix directory. For details, please read the file
1791 <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
1792 the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
1794 You do not have to say Y here if you want your Linux box to act as a
1795 file *server* for Novell NetWare clients.
1797 General information about how to connect Linux, Windows machines and
1798 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1800 To compile this as a module, choose M here: the module will be called
1801 ncpfs. Say N unless you are connected to a Novell network.
1803 source "fs/ncpfs/Kconfig"
1806 tristate "Coda file system support (advanced network fs)"
1809 Coda is an advanced network file system, similar to NFS in that it
1810 enables you to mount file systems of a remote server and access them
1811 with regular Unix commands as if they were sitting on your hard
1812 disk. Coda has several advantages over NFS: support for
1813 disconnected operation (e.g. for laptops), read/write server
1814 replication, security model for authentication and encryption,
1815 persistent client caches and write back caching.
1817 If you say Y here, your Linux box will be able to act as a Coda
1818 *client*. You will need user level code as well, both for the
1819 client and server. Servers are currently user level, i.e. they need
1820 no kernel support. Please read
1821 <file:Documentation/filesystems/coda.txt> and check out the Coda
1822 home page <http://www.coda.cs.cmu.edu/>.
1824 To compile the coda client support as a module, choose M here: the
1825 module will be called coda.
1827 config CODA_FS_OLD_API
1828 bool "Use 96-bit Coda file identifiers"
1831 A new kernel-userspace API had to be introduced for Coda v6.0
1832 to support larger 128-bit file identifiers as needed by the
1833 new realms implementation.
1835 However this new API is not backward compatible with older
1836 clients. If you really need to run the old Coda userspace
1837 cache manager then say Y.
1839 For most cases you probably want to say N.
1842 # for fs/nls/Config.in
1843 tristate "Andrew File System support (AFS) (Experimental)"
1844 depends on INET && EXPERIMENTAL
1847 If you say Y here, you will get an experimental Andrew File System
1848 driver. It currently only supports unsecured read-only AFS access.
1850 See Documentation/filesystems/afs.txt for more intormation.
1859 menu "Partition Types"
1861 source "fs/partitions/Kconfig"
1865 source "fs/nls/Kconfig"