2 # File system configuration
8 tristate "Second extended fs support"
10 This is the de facto standard Linux file system (method to organize
11 files on a storage device) for hard disks.
13 You want to say Y here, unless you intend to use Linux exclusively
14 from inside a DOS partition using the UMSDOS file system. The
15 advantage of the latter is that you can get away without
16 repartitioning your hard drive (which often implies backing
17 everything up and restoring afterwards); the disadvantage is that
18 Linux becomes susceptible to DOS viruses and that UMSDOS is somewhat
19 slower than ext2fs. Even if you want to run Linux in this fashion,
20 it might be a good idea to have ext2fs around: it enables you to
21 read more floppy disks and facilitates the transition to a *real*
22 Linux partition later. Another (rare) case which doesn't require
23 ext2fs is a diskless Linux box which mounts all files over the
24 network using NFS (in this case it's sufficient to say Y to "NFS
25 file system support" below). Saying Y here will enlarge your kernel
28 The Ext2fs-Undeletion mini-HOWTO, available from
29 <http://www.tldp.org/docs.html#howto>, gives information about
30 how to retrieve deleted files on ext2fs file systems.
32 To change the behavior of ext2 file systems, you can use the tune2fs
33 utility ("man tune2fs"). To modify attributes of files and
34 directories on ext2 file systems, use chattr ("man chattr").
36 Ext2fs partitions can be read from within DOS using the ext2tool
37 command line tool package (available from
38 <ftp://ibiblio.org/pub/Linux/system/filesystems/ext2/>) and from
39 within Windows NT using the ext2nt command line tool package from
40 <ftp://ibiblio.org/pub/Linux/utils/dos/>. Explore2fs is a
41 graphical explorer for ext2fs partitions which runs on Windows 95
42 and Windows NT and includes experimental write support; it is
44 <http://jnewbigin-pc.it.swin.edu.au/Linux/Explore2fs.htm>.
46 To compile this file system support as a module, choose M here: the
47 module will be called ext2. Be aware however that the file system
48 of your root partition (the one containing the directory /) cannot
49 be compiled as a module, and so this could be dangerous. Most
50 everyone wants to say Y here.
53 bool "Ext2 extended attributes"
56 Extended attributes are name:value pairs associated with inodes by
57 the kernel or by users (see the attr(5) manual page, or visit
58 <http://acl.bestbits.at/> for details).
62 config EXT2_FS_POSIX_ACL
63 bool "Ext2 POSIX Access Control Lists"
64 depends on EXT2_FS_XATTR
66 Posix Access Control Lists (ACLs) support permissions for users and
67 groups beyond the owner/group/world scheme.
69 To learn more about Access Control Lists, visit the Posix ACLs for
70 Linux website <http://acl.bestbits.at/>.
72 If you don't know what Access Control Lists are, say N
74 config EXT2_FS_SECURITY
75 bool "Ext2 Security Labels"
76 depends on EXT2_FS_XATTR
78 Security labels support alternative access control models
79 implemented by security modules like SELinux. This option
80 enables an extended attribute handler for file security
81 labels in the ext2 filesystem.
83 If you are not using a security module that requires using
84 extended attributes for file security labels, say N.
87 tristate "Ext3 journalling file system support"
89 This is the journaling version of the Second extended file system
90 (often called ext3), the de facto standard Linux file system
91 (method to organize files on a storage device) for hard disks.
93 The journaling code included in this driver means you do not have
94 to run e2fsck (file system checker) on your file systems after a
95 crash. The journal keeps track of any changes that were being made
96 at the time the system crashed, and can ensure that your file system
97 is consistent without the need for a lengthy check.
99 Other than adding the journal to the file system, the on-disk format
100 of ext3 is identical to ext2. It is possible to freely switch
101 between using the ext3 driver and the ext2 driver, as long as the
102 file system has been cleanly unmounted, or e2fsck is run on the file
105 To add a journal on an existing ext2 file system or change the
106 behavior of ext3 file systems, you can use the tune2fs utility ("man
107 tune2fs"). To modify attributes of files and directories on ext3
108 file systems, use chattr ("man chattr"). You need to be using
109 e2fsprogs version 1.20 or later in order to create ext3 journals
110 (available at <http://sourceforge.net/projects/e2fsprogs/>).
112 To compile this file system support as a module, choose M here: the
113 module will be called ext3. Be aware however that the file system
114 of your root partition (the one containing the directory /) cannot
115 be compiled as a module, and so this may be dangerous.
118 bool "Ext3 extended attributes"
122 Extended attributes are name:value pairs associated with inodes by
123 the kernel or by users (see the attr(5) manual page, or visit
124 <http://acl.bestbits.at/> for details).
128 You need this for POSIX ACL support on ext3.
130 config EXT3_FS_POSIX_ACL
131 bool "Ext3 POSIX Access Control Lists"
132 depends on EXT3_FS_XATTR
134 Posix Access Control Lists (ACLs) support permissions for users and
135 groups beyond the owner/group/world scheme.
137 To learn more about Access Control Lists, visit the Posix ACLs for
138 Linux website <http://acl.bestbits.at/>.
140 If you don't know what Access Control Lists are, say N
142 config EXT3_FS_SECURITY
143 bool "Ext3 Security Labels"
144 depends on EXT3_FS_XATTR
146 Security labels support alternative access control models
147 implemented by security modules like SELinux. This option
148 enables an extended attribute handler for file security
149 labels in the ext3 filesystem.
151 If you are not using a security module that requires using
152 extended attributes for file security labels, say N.
155 # CONFIG_JBD could be its own option (even modular), but until there are
156 # other users than ext3, we will simply make it be the same as CONFIG_EXT3_FS
157 # dep_tristate ' Journal Block Device support (JBD for ext3)' CONFIG_JBD $CONFIG_EXT3_FS
161 This is a generic journaling layer for block devices. It is
162 currently used by the ext3 file system, but it could also be used to
163 add journal support to other file systems or block devices such as
166 If you are using the ext3 file system, you need to say Y here. If
167 you are not using ext3 then you will probably want to say N.
169 To compile this device as a module, choose M here: the module will be
170 called jbd. If you are compiling ext3 into the kernel, you cannot
171 compile this code as a module.
174 bool "JBD (ext3) debugging support"
177 If you are using the ext3 journaled file system (or potentially any
178 other file system/device using JBD), this option allows you to
179 enable debugging output while the system is running, in order to
180 help track down any problems you are having. By default the
181 debugging output will be turned off.
183 If you select Y here, then you will be able to turn on debugging
184 with "echo N > /proc/sys/fs/jbd-debug", where N is a number between
185 1 and 5, the higher the number, the more debugging output is
186 generated. To turn debugging off again, do
187 "echo 0 > /proc/sys/fs/jbd-debug".
190 # Meta block cache for Extended Attributes (ext2/ext3)
192 depends on EXT2_FS_XATTR || EXT3_FS_XATTR
193 default y if EXT2_FS=y || EXT3_FS=y
194 default m if EXT2_FS=m || EXT3_FS=m
197 tristate "Reiserfs support"
199 Stores not just filenames but the files themselves in a balanced
200 tree. Uses journaling.
202 Balanced trees are more efficient than traditional file system
203 architectural foundations.
205 In general, ReiserFS is as fast as ext2, but is very efficient with
206 large directories and small files. Additional patches are needed
207 for NFS and quotas, please see <http://www.namesys.com/> for links.
209 It is more easily extended to have features currently found in
210 database and keyword search systems than block allocation based file
211 systems are. The next version will be so extended, and will support
212 plugins consistent with our motto ``It takes more than a license to
213 make source code open.''
215 Read <http://www.namesys.com/> to learn more about reiserfs.
217 Sponsored by Threshold Networks, Emusic.com, and Bigstorage.com.
219 If you like it, you can pay us to add new features to it that you
220 need, buy a support contract, or pay us to port it to another OS.
222 config REISERFS_CHECK
223 bool "Enable reiserfs debug mode"
224 depends on REISERFS_FS
226 If you set this to Y, then ReiserFS will perform every check it can
227 possibly imagine of its internal consistency throughout its
228 operation. It will also go substantially slower. More than once we
229 have forgotten that this was on, and then gone despondent over the
230 latest benchmarks.:-) Use of this option allows our team to go all
231 out in checking for consistency when debugging without fear of its
232 effect on end users. If you are on the verge of sending in a bug
233 report, say Y and you might get a useful error message. Almost
234 everyone should say N.
236 config REISERFS_PROC_INFO
237 bool "Stats in /proc/fs/reiserfs"
238 depends on REISERFS_FS
240 Create under /proc/fs/reiserfs a hierarchy of files, displaying
241 various ReiserFS statistics and internal data at the expense of
242 making your kernel or module slightly larger (+8 KB). This also
243 increases the amount of kernel memory required for each mount.
244 Almost everyone but ReiserFS developers and people fine-tuning
245 reiserfs or tracing problems should say N.
247 config REISERFS_FS_XATTR
248 bool "ReiserFS extended attributes"
249 depends on REISERFS_FS
251 Extended attributes are name:value pairs associated with inodes by
252 the kernel or by users (see the attr(5) manual page, or visit
253 <http://acl.bestbits.at/> for details).
257 config REISERFS_FS_POSIX_ACL
258 bool "ReiserFS POSIX Access Control Lists"
259 depends on REISERFS_FS_XATTR
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
269 config REISERFS_FS_SECURITY
270 bool "ReiserFS Security Labels"
271 depends on REISERFS_FS_XATTR
273 Security labels support alternative access control models
274 implemented by security modules like SELinux. This option
275 enables an extended attribute handler for file security
276 labels in the ReiserFS filesystem.
278 If you are not using a security module that requires using
279 extended attributes for file security labels, say N.
282 tristate "JFS filesystem support"
285 This is a port of IBM's Journaled Filesystem . More information is
286 available in the file Documentation/filesystems/jfs.txt.
288 If you do not intend to use the JFS filesystem, say N.
291 bool "JFS POSIX Access Control Lists"
294 Posix Access Control Lists (ACLs) support permissions for users and
295 groups beyond the owner/group/world scheme.
297 To learn more about Access Control Lists, visit the Posix ACLs for
298 Linux website <http://acl.bestbits.at/>.
300 If you don't know what Access Control Lists are, say N
306 If you are experiencing any problems with the JFS filesystem, say
307 Y here. This will result in additional debugging messages to be
308 written to the system log. Under normal circumstances, this
309 results in very little overhead.
311 config JFS_STATISTICS
312 bool "JFS statistics"
315 Enabling this option will cause statistics from the JFS file system
316 to be made available to the user in the /proc/fs/jfs/ directory.
319 # Posix ACL utility routines (for now, only ext2/ext3/jfs/reiserfs)
321 # NOTE: you can implement Posix ACLs without these helpers (XFS does).
322 # Never use this symbol for ifdefs.
325 depends on EXT2_FS_POSIX_ACL || EXT3_FS_POSIX_ACL || JFS_POSIX_ACL || REISERFS_FS_POSIX_ACL
329 tristate "XFS filesystem support"
331 XFS is a high performance journaling filesystem which originated
332 on the SGI IRIX platform. It is completely multi-threaded, can
333 support large files and large filesystems, extended attributes,
334 variable block sizes, is extent based, and makes extensive use of
335 Btrees (directories, extents, free space) to aid both performance
338 Refer to the documentation at <http://oss.sgi.com/projects/xfs/>
339 for complete details. This implementation is on-disk compatible
340 with the IRIX version of XFS.
342 To compile this file system support as a module, choose M here: the
343 module will be called xfs. Be aware, however, that if the file
344 system of your root partition is compiled as a module, you'll need
345 to use an initial ramdisk (initrd) to boot.
348 bool "Realtime support (EXPERIMENTAL)"
349 depends on XFS_FS && EXPERIMENTAL
351 If you say Y here you will be able to mount and use XFS filesystems
352 which contain a realtime subvolume. The realtime subvolume is a
353 separate area of disk space where only file data is stored. The
354 realtime subvolume is designed to provide very deterministic
355 data rates suitable for media streaming applications.
357 See the xfs man page in section 5 for a bit more information.
359 This feature is unsupported at this time, is not yet fully
360 functional, and may cause serious problems.
365 tristate "Quota support"
368 If you say Y here, you will be able to set limits for disk usage on
369 a per user and/or a per group basis under XFS. XFS considers quota
370 information as filesystem metadata and uses journaling to provide a
371 higher level guarantee of consistency. The on-disk data format for
372 quota is also compatible with the IRIX version of XFS, allowing a
373 filesystem to be migrated between Linux and IRIX without any need
376 If unsure, say N. More comprehensive documentation can be found in
377 README.quota in the xfsprogs package. XFS quota can be used either
378 with or without the generic quota support enabled (CONFIG_QUOTA) -
379 they are completely independent subsystems.
382 bool "Security Label support"
385 Security labels support alternative access control models
386 implemented by security modules like SELinux. This option
387 enables an extended attribute namespace for inode security
388 labels in the XFS filesystem.
390 If you are not using a security module that requires using
391 extended attributes for inode security labels, say N.
394 bool "POSIX ACL support"
397 POSIX Access Control Lists (ACLs) support permissions for users and
398 groups beyond the owner/group/world scheme.
400 To learn more about Access Control Lists, visit the POSIX ACLs for
401 Linux website <http://acl.bestbits.at/>.
403 If you don't know what Access Control Lists are, say N.
406 tristate "DMAPI support"
409 The Data Management API is a system interface used to implement
410 the interface defined in the X/Open document:
411 "Systems Management: Data Storage Management (XDSM) API",
412 dated February 1997. This interface is used by hierarchical
413 storage management systems.
418 bool "Debugging support (EXPERIMENTAL)"
419 depends on XFS_FS && EXPERIMENTAL
421 Say Y here to get an XFS build with many debugging features,
422 including ASSERT checks, function wrappers around macros,
423 and extra sanity-checking functions in various code paths.
425 Note that the resulting code will be HUGE and SLOW, and probably
426 not useful unless you are debugging a particular problem.
428 Say N unless you are an XFS developer, or you play one on TV.
431 bool "Tracing support (EXPERIMENTAL)"
432 depends on XFS_FS && EXPERIMENTAL
434 Say Y here to get an XFS build with activity tracing enabled.
435 Enabling this option will attach historical information to XFS
436 inodes, pagebufs, certain locks, the log, the IO path, and a
437 few other key areas within XFS. These traces can be examined
438 using the kdb kernel debugger.
440 Say N unless you are an XFS developer.
443 tristate "Minix fs support"
445 Minix is a simple operating system used in many classes about OS's.
446 The minix file system (method to organize files on a hard disk
447 partition or a floppy disk) was the original file system for Linux,
448 but has been superseded by the second extended file system ext2fs.
449 You don't want to use the minix file system on your hard disk
450 because of certain built-in restrictions, but it is sometimes found
451 on older Linux floppy disks. This option will enlarge your kernel
452 by about 28 KB. If unsure, say N.
454 To compile this file system support as a module, choose M here: the
455 module will be called minix. Note that the file system of your root
456 partition (the one containing the directory /) cannot be compiled as
460 tristate "ROM file system support"
462 This is a very small read-only file system mainly intended for
463 initial ram disks of installation disks, but it could be used for
464 other read-only media as well. Read
465 <file:Documentation/filesystems/romfs.txt> for details.
467 To compile this file system support as a module, choose M here: the
468 module will be called romfs. Note that the file system of your
469 root partition (the one containing the directory /) cannot be a
472 If you don't know whether you need it, then you don't need it:
478 If you say Y here, you will be able to set per user limits for disk
479 usage (also called disk quotas). Currently, it works for the
480 ext2, ext3, and reiserfs file system. You need additional software
481 in order to use quota support (you can download sources from
482 <http://www.sf.net/projects/linuxquota/>). For further details, read
483 the Quota mini-HOWTO, available from
484 <http://www.tldp.org/docs.html#howto>. Probably the quota
485 support is only useful for multi user systems. If unsure, say N.
488 tristate "Old quota format support"
491 This quota format was (is) used by kernels earlier than 2.4.??. If
492 you have quota working and you don't want to convert to new quota
496 tristate "Quota format v2 support"
499 This quota format allows using quotas with 32-bit UIDs/GIDs. If you
500 need this functionality say Y here. Note that you will need latest
501 quota utilities for new quota format with this kernel.
505 depends on XFS_QUOTA || QUOTA
509 tristate "Kernel automounter support"
511 The automounter is a tool to automatically mount remote file systems
512 on demand. This implementation is partially kernel-based to reduce
513 overhead in the already-mounted case; this is unlike the BSD
514 automounter (amd), which is a pure user space daemon.
516 To use the automounter you need the user-space tools from the autofs
517 package; you can find the location in <file:Documentation/Changes>.
518 You also want to answer Y to "NFS file system support", below.
520 If you want to use the newer version of the automounter with more
521 features, say N here and say Y to "Kernel automounter v4 support",
524 To compile this support as a module, choose M here: the module will be
527 If you are not a part of a fairly large, distributed network, you
528 probably do not need an automounter, and can say N here.
531 tristate "Kernel automounter version 4 support (also supports v3)"
533 The automounter is a tool to automatically mount remote file systems
534 on demand. This implementation is partially kernel-based to reduce
535 overhead in the already-mounted case; this is unlike the BSD
536 automounter (amd), which is a pure user space daemon.
538 To use the automounter you need the user-space tools from
539 <ftp://ftp.kernel.org/pub/linux/daemons/autofs/testing-v4/>; you also
540 want to answer Y to "NFS file system support", below.
542 To compile this support as a module, choose M here: the module will be
543 called autofs4. You will need to add "alias autofs autofs4" to your
544 modules configuration file.
546 If you are not a part of a fairly large, distributed network or
547 don't have a laptop which needs to dynamically reconfigure to the
548 local network, you probably do not need an automounter, and can say
551 menu "CD-ROM/DVD Filesystems"
554 tristate "ISO 9660 CDROM file system support"
556 This is the standard file system used on CD-ROMs. It was previously
557 known as "High Sierra File System" and is called "hsfs" on other
558 Unix systems. The so-called Rock-Ridge extensions which allow for
559 long Unix filenames and symbolic links are also supported by this
560 driver. If you have a CD-ROM drive and want to do more with it than
561 just listen to audio CDs and watch its LEDs, say Y (and read
562 <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO,
563 available from <http://www.tldp.org/docs.html#howto>), thereby
564 enlarging your kernel by about 27 KB; otherwise say N.
566 To compile this file system support as a module, choose M here: the
567 module will be called isofs.
570 bool "Microsoft Joliet CDROM extensions"
571 depends on ISO9660_FS
574 Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system
575 which allows for long filenames in unicode format (unicode is the
576 new 16 bit character code, successor to ASCII, which encodes the
577 characters of almost all languages of the world; see
578 <http://www.unicode.org/> for more information). Say Y here if you
579 want to be able to read Joliet CD-ROMs under Linux.
582 bool "Transparent decompression extension"
583 depends on ISO9660_FS
586 This is a Linux-specific extension to RockRidge which lets you store
587 data in compressed form on a CD-ROM and have it transparently
588 decompressed when the CD-ROM is accessed. See
589 <http://www.kernel.org/pub/linux/utils/fs/zisofs/> for the tools
590 necessary to create such a filesystem. Say Y here if you want to be
591 able to read such compressed CD-ROMs.
594 # for fs/nls/Config.in
600 tristate "UDF file system support"
602 This is the new file system used on some CD-ROMs and DVDs. Say Y if
603 you intend to mount DVD discs or CDRW's written in packet mode, or
604 if written to by other UDF utilities, such as DirectCD.
605 Please read <file:Documentation/filesystems/udf.txt>.
607 To compile this file system support as a module, choose M here: the
608 module will be called udf.
614 menu "DOS/FAT/NT Filesystems"
617 tristate "DOS FAT fs support"
620 If you want to use one of the FAT-based file systems (the MS-DOS,
621 VFAT (Windows 95) and UMSDOS (used to run Linux on top of an
622 ordinary DOS partition) file systems), then you must say Y or M here
623 to include FAT support. You will then be able to mount partitions or
624 diskettes with FAT-based file systems and transparently access the
625 files on them, i.e. MSDOS files will look and behave just like all
628 This FAT support is not a file system in itself, it only provides
629 the foundation for the other file systems. You will have to say Y or
630 M to at least one of "MSDOS fs support" or "VFAT fs support" in
631 order to make use of it.
633 Another way to read and write MSDOS floppies and hard drive
634 partitions from within Linux (but not transparently) is with the
635 mtools ("man mtools") program suite. You don't need to say Y here in
638 If you need to move large files on floppies between a DOS and a
639 Linux box, say Y here, mount the floppy under Linux with an MSDOS
640 file system and use GNU tar's M option. GNU tar is a program
641 available for Unix and DOS ("man tar" or "info tar").
643 It is now also becoming possible to read and write compressed FAT
644 file systems; read <file:Documentation/filesystems/fat_cvf.txt> for
647 The FAT support will enlarge your kernel by about 37 KB. If unsure,
650 To compile this as a module, choose M here: the module will be called
651 fat. Note that if you compile the FAT support as a module, you
652 cannot compile any of the FAT-based file systems into the kernel
653 -- they will have to be modules as well.
654 The file system of your root partition (the one containing the
655 directory /) cannot be a module, so don't say M here if you intend
656 to use UMSDOS as your root file system.
659 tristate "MSDOS fs support"
662 This allows you to mount MSDOS partitions of your hard drive (unless
663 they are compressed; to access compressed MSDOS partitions under
664 Linux, you can either use the DOS emulator DOSEMU, described in the
665 DOSEMU-HOWTO, available from
666 <http://www.tldp.org/docs.html#howto>, or try dmsdosfs in
667 <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you
668 intend to use dosemu with a non-compressed MSDOS partition, say Y
669 here) and MSDOS floppies. This means that file access becomes
670 transparent, i.e. the MSDOS files look and behave just like all
673 If you want to use UMSDOS, the Unix-like file system on top of a
674 DOS file system, which allows you to run Linux from within a DOS
675 partition without repartitioning, you'll have to say Y or M here.
677 If you have Windows 95 or Windows NT installed on your MSDOS
678 partitions, you should use the VFAT file system (say Y to "VFAT fs
679 support" below), or you will not be able to see the long filenames
680 generated by Windows 95 / Windows NT.
682 This option will enlarge your kernel by about 7 KB. If unsure,
683 answer Y. This will only work if you said Y to "DOS FAT fs support"
684 as well. To compile this as a module, choose M here: the module will
688 tristate "VFAT (Windows-95) fs support"
691 This option provides support for normal Windows file systems with
692 long filenames. That includes non-compressed FAT-based file systems
693 used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
694 programs from the mtools package.
696 You cannot use the VFAT file system for your Linux root partition
697 (the one containing the directory /); use UMSDOS instead if you
698 want to run Linux from within a DOS partition (i.e. say Y to
699 "Unix like fs on top of std MSDOS fs", below).
701 The VFAT support enlarges your kernel by about 10 KB and it only
702 works if you said Y to the "DOS FAT fs support" above. Please read
703 the file <file:Documentation/filesystems/vfat.txt> for details. If
706 To compile this as a module, choose M here: the module will be called
710 #dep_tristate ' UMSDOS: Unix-like file system on top of standard MSDOS fs' CONFIG_UMSDOS_FS $CONFIG_MSDOS_FS
711 # UMSDOS is temprory broken
714 Say Y here if you want to run Linux from within an existing DOS
715 partition of your hard drive. The advantage of this is that you can
716 get away without repartitioning your hard drive (which often implies
717 backing everything up and restoring afterwards) and hence you're
718 able to quickly try out Linux or show it to your friends; the
719 disadvantage is that Linux becomes susceptible to DOS viruses and
720 that UMSDOS is somewhat slower than ext2fs. Another use of UMSDOS
721 is to write files with long unix filenames to MSDOS floppies; it
722 also allows Unix-style soft-links and owner/permissions of files on
723 MSDOS floppies. You will need a program called umssync in order to
724 make use of UMSDOS; read
725 <file:Documentation/filesystems/umsdos.txt>.
727 To get utilities for initializing/checking UMSDOS file system, or
728 latest patches and/or information, visit the UMSDOS home page at
729 <http://www.voyager.hr/~mnalis/umsdos/>.
731 This option enlarges your kernel by about 28 KB and it only works if
732 you said Y to both "DOS FAT fs support" and "MSDOS fs support"
733 above. To compile this as a module, choose M here: the module will be
734 called umsdos. Note that the file system of your root partition
735 (the one containing the directory /) cannot be a module, so saying M
736 could be dangerous. If unsure, say N.
739 tristate "NTFS file system support"
742 NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003.
744 Saying Y or M here enables read support. There is partial, but
745 safe, write support available. For write support you must also
746 say Y to "NTFS write support" below.
748 There are also a number of user-space tools available, called
749 ntfsprogs. These include ntfsundelete and ntfsresize, that work
750 without NTFS support enabled in the kernel.
752 This is a rewrite from scratch of Linux NTFS support and replaced
753 the old NTFS code starting with Linux 2.5.11. A backport to
754 the Linux 2.4 kernel series is separately available as a patch
755 from the project web site.
757 For more information see <file:Documentation/filesystems/ntfs.txt>
758 and <http://linux-ntfs.sourceforge.net/>.
760 To compile this file system support as a module, choose M here: the
761 module will be called ntfs.
763 If you are not using Windows NT, 2000, XP or 2003 in addition to
764 Linux on your computer it is safe to say N.
767 bool "NTFS debugging support"
770 If you are experiencing any problems with the NTFS file system, say
771 Y here. This will result in additional consistency checks to be
772 performed by the driver as well as additional debugging messages to
773 be written to the system log. Note that debugging messages are
774 disabled by default. To enable them, supply the option debug_msgs=1
775 at the kernel command line when booting the kernel or as an option
776 to insmod when loading the ntfs module. Once the driver is active,
777 you can enable debugging messages by doing (as root):
778 echo 1 > /proc/sys/fs/ntfs-debug
779 Replacing the "1" with "0" would disable debug messages.
781 If you leave debugging messages disabled, this results in little
782 overhead, but enabling debug messages results in very significant
783 slowdown of the system.
785 When reporting bugs, please try to have available a full dump of
786 debugging messages while the misbehaviour was occurring.
789 bool "NTFS write support"
792 This enables the partial, but safe, write support in the NTFS driver.
794 The only supported operation is overwriting existing files, without
795 changing the file length. No file or directory creation, deletion or
796 renaming is possible. Note only non-resident files can be written to
797 so you may find that some very small files (<500 bytes or so) cannot
800 While we cannot guarantee that it will not damage any data, we have
801 so far not received a single report where the driver would have
802 damaged someones data so we assume it is perfectly safe to use.
804 Note: While write support is safe in this version (a rewrite from
805 scratch of the NTFS support), it should be noted that the old NTFS
806 write support, included in Linux 2.5.10 and before (since 1997),
809 This is currently useful with TopologiLinux. TopologiLinux is run
810 on top of any DOS/Microsoft Windows system without partitioning your
811 hard disk. Unlike other Linux distributions TopologiLinux does not
812 need its own partition. For more information see
813 <http://topologi-linux.sourceforge.net/>
815 It is perfectly safe to say N here.
819 menu "Pseudo filesystems"
822 bool "/proc file system support"
824 This is a virtual file system providing information about the status
825 of the system. "Virtual" means that it doesn't take up any space on
826 your hard disk: the files are created on the fly by the kernel when
827 you try to access them. Also, you cannot read the files with older
828 version of the program less: you need to use more or cat.
830 It's totally cool; for example, "cat /proc/interrupts" gives
831 information about what the different IRQs are used for at the moment
832 (there is a small number of Interrupt ReQuest lines in your computer
833 that are used by the attached devices to gain the CPU's attention --
834 often a source of trouble if two devices are mistakenly configured
835 to use the same IRQ). The program procinfo to display some
836 information about your system gathered from the /proc file system.
838 Before you can use the /proc file system, it has to be mounted,
839 meaning it has to be given a location in the directory hierarchy.
840 That location should be /proc. A command such as "mount -t proc proc
841 /proc" or the equivalent line in /etc/fstab does the job.
843 The /proc file system is explained in the file
844 <file:Documentation/filesystems/proc.txt> and on the proc(5) manpage
847 This option will enlarge your kernel by about 67 KB. Several
848 programs depend on this, so everyone should say Y here.
855 bool "/dev file system support (OBSOLETE)"
856 depends on EXPERIMENTAL
858 This is support for devfs, a virtual file system (like /proc) which
859 provides the file system interface to device drivers, normally found
860 in /dev. Devfs does not depend on major and minor number
861 allocations. Device drivers register entries in /dev which then
862 appear automatically, which means that the system administrator does
863 not have to create character and block special device files in the
864 /dev directory using the mknod command (or MAKEDEV script) anymore.
866 This is work in progress. If you want to use this, you *must* read
867 the material in <file:Documentation/filesystems/devfs/>, especially
868 the file README there.
870 Note that devfs no longer manages /dev/pts! If you are using UNIX98
871 ptys, you will also need to enable (and mount) the /dev/pts
872 filesystem (CONFIG_DEVPTS_FS).
874 Note that devfs has been obsoleted by udev,
875 <http://www.kernel.org/pub/linux/utils/kernel/hotplug/>.
876 It has been stripped down to a bare minimum and is only provided for
877 legacy installations that use its naming scheme which is
878 unfortunately different from the names normal Linux installations
884 bool "Automatically mount at boot"
887 This option appears if you have CONFIG_DEVFS_FS enabled. Setting
888 this to 'Y' will make the kernel automatically mount devfs onto /dev
889 when the system is booted, before the init thread is started.
890 You can override this with the "devfs=nomount" boot option.
898 If you say Y here, then the /dev file system code will generate
899 debugging messages. See the file
900 <file:Documentation/filesystems/devfs/boot-options> for more
906 # It compiles as a module for testing only. It should not be used
907 # as a module in general. If we make this "tristate", a bunch of people
908 # who don't know what they are doing turn it on and complain when it
910 bool "/dev/pts file system for Unix98 PTYs"
911 depends on UNIX98_PTYS
913 You should say Y here if you said Y to "Unix98 PTY support" above.
914 You'll then get a virtual file system which can be mounted on
915 /dev/pts with "mount -t devpts". This, together with the pseudo
916 terminal master multiplexer /dev/ptmx, is used for pseudo terminal
917 support as described in The Open Group's Unix98 standard: in order
918 to acquire a pseudo terminal, a process opens /dev/ptmx; the number
919 of the pseudo terminal is then made available to the process and the
920 pseudo terminal slave can be accessed as /dev/pts/<number>. What was
921 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
923 The GNU C library glibc 2.1 contains the requisite support for this
924 mode of operation; you also need client programs that use the Unix98
925 API. Please read <file:Documentation/Changes> for more information
926 about the Unix98 pty devices.
928 config DEVPTS_FS_XATTR
929 bool "/dev/pts Extended Attributes"
932 Extended attributes are name:value pairs associated with inodes by
933 the kernel or by users (see the attr(5) manual page, or visit
934 <http://acl.bestbits.at/> for details).
938 config DEVPTS_FS_SECURITY
939 bool "/dev/pts Security Labels"
940 depends on DEVPTS_FS_XATTR
942 Security labels support alternative access control models
943 implemented by security modules like SELinux. This option
944 enables an extended attribute handler for file security
945 labels in the /dev/pts filesystem.
947 If you are not using a security module that requires using
948 extended attributes for file security labels, say N.
951 bool "Virtual memory file system support (former shm fs)"
953 Tmpfs is a file system which keeps all files in virtual memory.
955 Everything in tmpfs is temporary in the sense that no files will be
956 created on your hard drive. The files live in memory and swap
957 space. If you unmount a tmpfs instance, everything stored therein is
960 See <file:Documentation/filesystems/tmpfs.txt> for details.
963 bool "HugeTLB file system support"
964 depends X86 || IA64 || PPC64 || SPARC64 || X86_64 || BROKEN
973 Ramfs is a file system which keeps all files in RAM. It allows
974 read and write access.
976 It is more of an programming example than a useable file system. If
977 you need a file system which lives in RAM with limit checking use
980 To compile this as a module, choose M here: the module will be called
985 menu "Miscellaneous filesystems"
988 tristate "ADFS file system support (EXPERIMENTAL)"
989 depends on EXPERIMENTAL
991 The Acorn Disc Filing System is the standard file system of the
992 RiscOS operating system which runs on Acorn's ARM-based Risc PC
993 systems and the Acorn Archimedes range of machines. If you say Y
994 here, Linux will be able to read from ADFS partitions on hard drives
995 and from ADFS-formatted floppy discs. If you also want to be able to
996 write to those devices, say Y to "ADFS write support" below.
998 The ADFS partition should be the first partition (i.e.,
999 /dev/[hs]d?1) on each of your drives. Please read the file
1000 <file:Documentation/filesystems/adfs.txt> for further details.
1002 To compile this code as a module, choose M here: the module will be
1008 bool "ADFS write support (DANGEROUS)"
1011 If you say Y here, you will be able to write to ADFS partitions on
1012 hard drives and ADFS-formatted floppy disks. This is experimental
1013 codes, so if you're unsure, say N.
1016 tristate "Amiga FFS file system support (EXPERIMENTAL)"
1017 depends on EXPERIMENTAL
1019 The Fast File System (FFS) is the common file system used on hard
1020 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
1021 if you want to be able to read and write files from and to an Amiga
1022 FFS partition on your hard drive. Amiga floppies however cannot be
1023 read with this driver due to an incompatibility of the floppy
1024 controller used in an Amiga and the standard floppy controller in
1025 PCs and workstations. Read <file:Documentation/filesystems/affs.txt>
1026 and <file:fs/affs/Changes>.
1028 With this driver you can also mount disk files used by Bernd
1029 Schmidt's Un*X Amiga Emulator
1030 (<http://www.freiburg.linux.de/~uae/>).
1031 If you want to do this, you will also need to say Y or M to "Loop
1032 device support", above.
1034 To compile this file system support as a module, choose M here: the
1035 module will be called affs. If unsure, say N.
1038 tristate "Apple Macintosh file system support (EXPERIMENTAL)"
1039 depends on EXPERIMENTAL
1041 If you say Y here, you will be able to mount Macintosh-formatted
1042 floppy disks and hard drive partitions with full read-write access.
1043 Please read <file:fs/hfs/HFS.txt> to learn about the available mount
1046 To compile this file system support as a module, choose M here: the
1047 module will be called hfs.
1050 tristate "Apple Extended HFS file system support (EXPERIMENTAL)"
1051 depends on EXPERIMENTAL
1054 If you say Y here, you will be able to mount extended format
1055 Macintosh-formatted hard drive partitions with full read-write access.
1057 This file system is often called HFS+ and was introduced with
1058 MacOS 8. It includes all Mac specific filesystem data such as
1059 data forks and creator codes, but it also has several UNIX
1060 style features such as file ownership and permissions.
1063 tristate "BeOS file systemv(BeFS) support (read only) (EXPERIMENTAL)"
1064 depends on EXPERIMENTAL
1067 The BeOS File System (BeFS) is the native file system of Be, Inc's
1068 BeOS. Notable features include support for arbitrary attributes
1069 on files and directories, and database-like indices on selected
1070 attributes. (Also note that this driver doesn't make those features
1071 available at this time). It is a 64 bit filesystem, so it supports
1072 extreemly large volumes and files.
1074 If you use this filesystem, you should also say Y to at least one
1075 of the NLS (native language support) options below.
1077 If you don't know what this is about, say N.
1079 To compile this as a module, choose M here: the module will be
1086 If you say Y here, you can use the 'debug' mount option to enable
1087 debugging output from the driver.
1090 tristate "BFS file system support (EXPERIMENTAL)"
1091 depends on EXPERIMENTAL
1093 Boot File System (BFS) is a file system used under SCO UnixWare to
1094 allow the bootloader access to the kernel image and other important
1095 files during the boot process. It is usually mounted under /stand
1096 and corresponds to the slice marked as "STAND" in the UnixWare
1097 partition. You should say Y if you want to read or write the files
1098 on your /stand slice from within Linux. You then also need to say Y
1099 to "UnixWare slices support", below. More information about the BFS
1100 file system is contained in the file
1101 <file:Documentation/filesystems/bfs.txt>.
1103 If you don't know what this is about, say N.
1105 To compile this as a module, choose M here: the module will be called
1106 bfs. Note that the file system of your root partition (the one
1107 containing the directory /) cannot be compiled as a module.
1112 tristate "EFS file system support (read only) (EXPERIMENTAL)"
1113 depends on EXPERIMENTAL
1115 EFS is an older file system used for non-ISO9660 CD-ROMs and hard
1116 disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
1117 uses the XFS file system for hard disk partitions however).
1119 This implementation only offers read-only access. If you don't know
1120 what all this is about, it's safe to say N. For more information
1121 about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
1123 To compile the EFS file system support as a module, choose M here: the
1124 module will be called efs.
1127 tristate "Journalling Flash File System (JFFS) support"
1130 JFFS is the Journaling Flash File System developed by Axis
1131 Communications in Sweden, aimed at providing a crash/powerdown-safe
1132 file system for disk-less embedded devices. Further information is
1133 available at (<http://developer.axis.com/software/jffs/>).
1135 config JFFS_FS_VERBOSE
1136 int "JFFS debugging verbosity (0 = quiet, 3 = noisy)"
1140 Determines the verbosity level of the JFFS debugging messages.
1143 bool "JFFS stats available in /proc filesystem"
1144 depends on JFFS_FS && PROC
1146 Enabling this option will cause statistics from mounted JFFS file systems
1147 to be made available to the user in the /proc/fs/jffs/ directory.
1150 tristate "Journalling Flash File System v2 (JFFS2) support"
1156 JFFS2 is the second generation of the Journalling Flash File System
1157 for use on diskless embedded devices. It provides improved wear
1158 levelling, compression and support for hard links. You cannot use
1159 this on normal block devices, only on 'MTD' devices.
1161 Further information on the design and implementation of JFFS2 is
1162 available at <http://sources.redhat.com/jffs2/>.
1164 config JFFS2_FS_DEBUG
1165 int "JFFS2 debugging verbosity (0 = quiet, 2 = noisy)"
1169 This controls the amount of debugging messages produced by the JFFS2
1170 code. Set it to zero for use in production systems. For evaluation,
1171 testing and debugging, it's advisable to set it to one. This will
1172 enable a few assertions and will print debugging messages at the
1173 KERN_DEBUG loglevel, where they won't normally be visible. Level 2
1174 is unlikely to be useful - it enables extra debugging in certain
1175 areas which at one point needed debugging, but when the bugs were
1176 located and fixed, the detailed messages were relegated to level 2.
1178 If reporting bugs, please try to have available a full dump of the
1179 messages at debug level 1 while the misbehaviour was occurring.
1181 config JFFS2_FS_NAND
1182 bool "JFFS2 support for NAND flash (EXPERIMENTAL)"
1183 depends on JFFS2_FS && EXPERIMENTAL
1186 This enables the experimental support for NAND flash in JFFS2. NAND
1187 is a newer type of flash chip design than the traditional NOR flash,
1188 with higher density but a handful of characteristics which make it
1189 more interesting for the file system to use. Support for NAND flash
1190 is not yet complete and may corrupt data. For further information,
1191 including a link to the mailing list where details of the remaining
1192 work to be completed for NAND flash support can be found, see the
1193 JFFS2 web site at <http://sources.redhat.com/jffs2>.
1195 Say 'N' unless you have NAND flash and you are willing to test and
1196 develop JFFS2 support for it.
1199 tristate "Compressed ROM file system support"
1202 Saying Y here includes support for CramFs (Compressed ROM File
1203 System). CramFs is designed to be a simple, small, and compressed
1204 file system for ROM based embedded systems. CramFs is read-only,
1205 limited to 256MB file systems (with 16MB files), and doesn't support
1206 16/32 bits uid/gid, hard links and timestamps.
1208 See <file:Documentation/filesystems/cramfs.txt> and
1209 <file:fs/cramfs/README> for further information.
1211 To compile this as a module, choose M here: the module will be called
1212 cramfs. Note that the root file system (the one containing the
1213 directory /) cannot be compiled as a module.
1218 tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
1220 FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
1221 file system format. VERITAS VxFS(TM) is the standard file system
1222 of SCO UnixWare (and possibly others) and optionally available
1223 for Sunsoft Solaris, HP-UX and many other operating systems.
1224 Currently only readonly access is supported.
1226 NOTE: the file system type as used by mount(1), mount(2) and
1227 fstab(5) is 'vxfs' as it describes the file system format, not
1230 To compile this as a module, choose M here: the module will be
1231 called freevxfs. If unsure, say N.
1235 tristate "OS/2 HPFS file system support"
1237 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
1238 is the file system used for organizing files on OS/2 hard disk
1239 partitions. Say Y if you want to be able to read files from and
1240 write files to an OS/2 HPFS partition on your hard drive. OS/2
1241 floppies however are in regular MSDOS format, so you don't need this
1242 option in order to be able to read them. Read
1243 <file:Documentation/filesystems/hpfs.txt>.
1245 To compile this file system support as a module, choose M here: the
1246 module will be called hpfs. If unsure, say N.
1251 tristate "QNX4 file system support (read only)"
1253 This is the file system used by the real-time operating systems
1254 QNX 4 and QNX 6 (the latter is also called QNX RTP).
1255 Further information is available at <http://www.qnx.com/>.
1256 Say Y if you intend to mount QNX hard disks or floppies.
1257 Unless you say Y to "QNX4FS read-write support" below, you will
1258 only be able to read these file systems.
1260 To compile this file system support as a module, choose M here: the
1261 module will be called qnx4.
1263 If you don't know whether you need it, then you don't need it:
1267 bool "QNX4FS write support (DANGEROUS)"
1268 depends on QNX4FS_FS && EXPERIMENTAL
1270 Say Y if you want to test write support for QNX4 file systems.
1272 It's currently broken, so for now:
1278 tristate "System V/Xenix/V7/Coherent file system support"
1280 SCO, Xenix and Coherent are commercial Unix systems for Intel
1281 machines, and Version 7 was used on the DEC PDP-11. Saying Y
1282 here would allow you to read from their floppies and hard disk
1285 If you have floppies or hard disk partitions like that, it is likely
1286 that they contain binaries from those other Unix systems; in order
1287 to run these binaries, you will want to install linux-abi which is a
1288 a set of kernel modules that lets you run SCO, Xenix, Wyse,
1289 UnixWare, Dell Unix and System V programs under Linux. It is
1290 available via FTP (user: ftp) from
1291 <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
1292 NOTE: that will work only for binaries from Intel-based systems;
1293 PDP ones will have to wait until somebody ports Linux to -11 ;-)
1295 If you only intend to mount files from some other Unix over the
1296 network using NFS, you don't need the System V file system support
1297 (but you need NFS file system support obviously).
1299 Note that this option is generally not needed for floppies, since a
1300 good portable way to transport files and directories between unixes
1301 (and even other operating systems) is given by the tar program ("man
1302 tar" or preferably "info tar"). Note also that this option has
1303 nothing whatsoever to do with the option "System V IPC". Read about
1304 the System V file system in
1305 <file:Documentation/filesystems/sysv-fs.txt>.
1306 Saying Y here will enlarge your kernel by about 27 KB.
1308 To compile this as a module, choose M here: the module will be called
1311 If you haven't heard about all of this before, it's safe to say N.
1316 tristate "UFS file system support (read only)"
1318 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
1319 OpenBSD and NeXTstep) use a file system called UFS. Some System V
1320 Unixes can create and mount hard disk partitions and diskettes using
1321 this file system as well. Saying Y here will allow you to read from
1322 these partitions; if you also want to write to them, say Y to the
1323 experimental "UFS file system write support", below. Please read the
1324 file <file:Documentation/filesystems/ufs.txt> for more information.
1326 If you only intend to mount files from some other Unix over the
1327 network using NFS, you don't need the UFS file system support (but
1328 you need NFS file system support obviously).
1330 Note that this option is generally not needed for floppies, since a
1331 good portable way to transport files and directories between unixes
1332 (and even other operating systems) is given by the tar program ("man
1333 tar" or preferably "info tar").
1335 When accessing NeXTstep files, you may need to convert them from the
1336 NeXT character set to the Latin1 character set; use the program
1337 recode ("info recode") for this purpose.
1339 To compile the UFS file system support as a module, choose M here: the
1340 module will be called ufs.
1342 If you haven't heard about all of this before, it's safe to say N.
1345 bool "UFS file system write support (DANGEROUS)"
1346 depends on UFS_FS && EXPERIMENTAL
1348 Say Y here if you want to try writing to UFS partitions. This is
1349 experimental, so you should back up your UFS partitions beforehand.
1353 menu "Network File Systems"
1357 tristate "NFS file system support"
1361 select NFS_ACL_SUPPORT if NFS_ACL
1363 If you are connected to some other (usually local) Unix computer
1364 (using SLIP, PLIP, PPP or Ethernet) and want to mount files residing
1365 on that computer (the NFS server) using the Network File Sharing
1366 protocol, say Y. "Mounting files" means that the client can access
1367 the files with usual UNIX commands as if they were sitting on the
1368 client's hard disk. For this to work, the server must run the
1369 programs nfsd and mountd (but does not need to have NFS file system
1370 support enabled in its kernel). NFS is explained in the Network
1371 Administrator's Guide, available from
1372 <http://www.tldp.org/docs.html#guide>, on its man page: "man
1373 nfs", and in the NFS-HOWTO.
1375 A superior but less widely used alternative to NFS is provided by
1376 the Coda file system; see "Coda file system support" below.
1378 If you say Y here, you should have said Y to TCP/IP networking also.
1379 This option would enlarge your kernel by about 27 KB.
1381 To compile this file system support as a module, choose M here: the
1382 module will be called nfs.
1384 If you are configuring a diskless machine which will mount its root
1385 file system over NFS at boot time, say Y here and to "Kernel
1386 level IP autoconfiguration" above and to "Root file system on NFS"
1387 below. You cannot compile this driver as a module in this case.
1388 There are two packages designed for booting diskless machines over
1389 the net: netboot, available from
1390 <http://ftp1.sourceforge.net/netboot/>, and Etherboot,
1391 available from <http://ftp1.sourceforge.net/etherboot/>.
1393 If you don't know what all this is about, say N.
1396 bool "Provide NFSv3 client support"
1399 Say Y here if you want your NFS client to be able to speak the newer
1400 version 3 of the NFS protocol.
1405 bool "NFS_ACL protocol extension"
1409 Implement the NFS_ACL protocol extension for manipulating POSIX
1410 Access Control Lists. The server must also implement the NFS_ACL
1411 protocol extension; see the CONFIG_NFSD_ACL option.
1416 bool "Provide NFSv4 client support (EXPERIMENTAL)"
1417 depends on NFS_FS && EXPERIMENTAL
1419 Say Y here if you want your NFS client to be able to speak the newer
1420 version 4 of the NFS protocol. This feature is experimental, and
1421 should only be used if you are interested in helping to test NFSv4.
1426 bool "Allow direct I/O on NFS files (EXPERIMENTAL)"
1427 depends on NFS_FS && EXPERIMENTAL
1429 This option enables applications to perform uncached I/O on files
1430 in NFS file systems using the O_DIRECT open() flag. When O_DIRECT
1431 is set for a file, its data is not cached in the system's page
1432 cache. Data is moved to and from user-level application buffers
1433 directly. Unlike local disk-based file systems, NFS O_DIRECT has
1434 no alignment restrictions.
1436 Unless your program is designed to use O_DIRECT properly, you are
1437 much better off allowing the NFS client to manage data caching for
1438 you. Misusing O_DIRECT can cause poor server performance or network
1439 storms. This kernel build option defaults OFF to avoid exposing
1440 system administrators unwittingly to a potentially hazardous
1443 For more details on NFS O_DIRECT, see fs/nfs/direct.c.
1445 If unsure, say N. This reduces the size of the NFS client, and
1446 causes open() to return EINVAL if a file residing in NFS is
1447 opened with the O_DIRECT flag.
1450 tristate "NFS server support"
1454 select NFS_ACL_SUPPORT if NFSD_ACL
1456 If you want your Linux box to act as an NFS *server*, so that other
1457 computers on your local network which support NFS can access certain
1458 directories on your box transparently, you have two options: you can
1459 use the self-contained user space program nfsd, in which case you
1460 should say N here, or you can say Y and use the kernel based NFS
1461 server. The advantage of the kernel based solution is that it is
1464 In either case, you will need support software; the respective
1465 locations are given in the file <file:Documentation/Changes> in the
1468 If you say Y here, you will get support for version 2 of the NFS
1469 protocol (NFSv2). If you also want NFSv3, say Y to the next question
1472 Please read the NFS-HOWTO, available from
1473 <http://www.tldp.org/docs.html#howto>.
1475 To compile the NFS server support as a module, choose M here: the
1476 module will be called nfsd. If unsure, say N.
1479 bool "Provide NFSv3 server support"
1482 If you would like to include the NFSv3 server as well as the NFSv2
1483 server, say Y here. If unsure, say Y.
1486 bool "NFS_ACL protocol extension"
1490 Implement the NFS_ACL protocol extension for manipulating POSIX
1491 Access Control Lists on exported file systems. The clients must
1492 also implement the NFS_ACL protocol extension; see the
1493 CONFIG_NFS_ACL option. If unsure, say N.
1495 config NFS_ACL_SUPPORT
1499 bool "Provide NFSv4 server support (EXPERIMENTAL)"
1500 depends on NFSD_V3 && EXPERIMENTAL
1502 If you would like to include the NFSv4 server as well as the NFSv2
1503 and NFSv3 servers, say Y here. This feature is experimental, and
1504 should only be used if you are interested in helping to test NFSv4.
1508 bool "Provide NFS server over TCP support (EXPERIMENTAL)"
1509 depends on NFSD && EXPERIMENTAL
1511 Enable NFS service over TCP connections. This the officially
1512 still experimental, but seems to work well.
1515 bool "Root file system on NFS"
1516 depends on NFS_FS=y && IP_PNP
1518 If you want your Linux box to mount its whole root file system (the
1519 one containing the directory /) from some other computer over the
1520 net via NFS (presumably because your box doesn't have a hard disk),
1521 say Y. Read <file:Documentation/nfsroot.txt> for details. It is
1522 likely that in this case, you also want to say Y to "Kernel level IP
1523 autoconfiguration" so that your box can discover its network address
1526 Most people say N here.
1532 bool "Use kernel statd implementation"
1533 depends on LOCKD && EXPERIMENTAL
1537 depends on NFSD_V3 || NFS_V3
1548 tristate "Provide RPCSEC_GSS authentication (EXPERIMENTAL)"
1549 depends on SUNRPC && EXPERIMENTAL
1550 default SUNRPC if NFS_V4=y
1552 Provides cryptographic authentication for NFS rpc requests. To
1553 make this useful, you must also select at least one rpcsec_gss
1555 Note: You should always select this option if you wish to use
1558 config RPCSEC_GSS_KRB5
1559 tristate "Kerberos V mechanism for RPCSEC_GSS (EXPERIMENTAL)"
1560 depends on SUNRPC_GSS && CRYPTO_DES && CRYPTO_MD5
1561 default SUNRPC_GSS if NFS_V4=y
1563 Provides a gss-api mechanism based on Kerberos V5 (this is
1564 mandatory for RFC3010-compliant NFSv4 implementations).
1565 Requires a userspace daemon;
1566 see http://www.citi.umich.edu/projects/nfsv4/.
1568 Note: If you select this option, please ensure that you also
1569 enable the MD5 and DES crypto ciphers.
1572 tristate "SMB file system support (to mount Windows shares etc.)"
1576 SMB (Server Message Block) is the protocol Windows for Workgroups
1577 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
1578 files and printers over local networks. Saying Y here allows you to
1579 mount their file systems (often called "shares" in this context) and
1580 access them just like any other Unix directory. Currently, this
1581 works only if the Windows machines use TCP/IP as the underlying
1582 transport protocol, and not NetBEUI. For details, read
1583 <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
1584 available from <http://www.tldp.org/docs.html#howto>.
1586 Note: if you just want your box to act as an SMB *server* and make
1587 files and printing services available to Windows clients (which need
1588 to have a TCP/IP stack), you don't need to say Y here; you can use
1589 the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
1592 General information about how to connect Linux, Windows machines and
1593 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1595 To compile the SMB support as a module, choose M here: the module will
1596 be called smbfs. Most people say N, however.
1598 config SMB_NLS_DEFAULT
1599 bool "Use a default NLS"
1602 Enabling this will make smbfs use nls translations by default. You
1603 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
1604 settings and you need to give the default nls for the SMB server as
1605 CONFIG_SMB_NLS_REMOTE.
1607 The nls settings can be changed at mount time, if your smbmount
1608 supports that, using the codepage and iocharset parameters.
1610 smbmount from samba 2.2.0 or later supports this.
1612 config SMB_NLS_REMOTE
1613 string "Default Remote NLS Option"
1614 depends on SMB_NLS_DEFAULT
1617 This setting allows you to specify a default value for which
1618 codepage the server uses. If this field is left blank no
1619 translations will be done by default. The local codepage/charset
1620 default to CONFIG_NLS_DEFAULT.
1622 The nls settings can be changed at mount time, if your smbmount
1623 supports that, using the codepage and iocharset parameters.
1625 smbmount from samba 2.2.0 or later supports this.
1628 tristate "CIFS support (advanced network filesystem for Samba, Window and other CIFS compliant servers)(EXPERIMENTAL)"
1632 This is the client VFS module for the Common Internet File System
1633 (CIFS) protocol which is the successor to the Server Message Block
1634 (SMB) protocol, the native file sharing mechanism for most early
1635 PC operating systems. CIFS is fully supported by current network
1636 file servers such as Windows 2000 (including Windows NT version 4
1637 and Windows XP) as well by Samba (which provides excellent CIFS
1638 server support for Linux and many other operating systems). For
1639 production systems the smbfs module may be used instead of this
1640 cifs module since smbfs is currently more stable and provides
1641 support for older servers. The intent of this module is to provide the
1642 most advanced network file system function for CIFS compliant servers,
1643 including support for dfs (hierarchical name space), secure per-user
1644 session establishment, safe distributed caching (oplock), optional
1645 packet signing, Unicode and other internationalization improvements, and
1646 optional Winbind (nsswitch) integration. This module is in an early
1647 development stage, so unless you are specifically interested in this
1648 filesystem, just say N.
1651 tristate "NCP file system support (to mount NetWare volumes)"
1652 depends on IPX!=n || INET
1654 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
1655 used by Novell NetWare clients to talk to file servers. It is to
1656 IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
1657 to mount NetWare file server volumes and to access them just like
1658 any other Unix directory. For details, please read the file
1659 <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
1660 the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
1662 You do not have to say Y here if you want your Linux box to act as a
1663 file *server* for Novell NetWare clients.
1665 General information about how to connect Linux, Windows machines and
1666 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1668 To compile this as a module, choose M here: the module will be called
1669 ncpfs. Say N unless you are connected to a Novell network.
1671 source "fs/ncpfs/Kconfig"
1674 tristate "Coda file system support (advanced network fs)"
1677 Coda is an advanced network file system, similar to NFS in that it
1678 enables you to mount file systems of a remote server and access them
1679 with regular Unix commands as if they were sitting on your hard
1680 disk. Coda has several advantages over NFS: support for
1681 disconnected operation (e.g. for laptops), read/write server
1682 replication, security model for authentication and encryption,
1683 persistent client caches and write back caching.
1685 If you say Y here, your Linux box will be able to act as a Coda
1686 *client*. You will need user level code as well, both for the
1687 client and server. Servers are currently user level, i.e. they need
1688 no kernel support. Please read
1689 <file:Documentation/filesystems/coda.txt> and check out the Coda
1690 home page <http://www.coda.cs.cmu.edu/>.
1692 To compile the coda client support as a module, choose M here: the
1693 module will be called coda.
1695 config CODA_FS_OLD_API
1696 bool "Use 96-bit Coda file identifiers"
1699 A new kernel-userspace API had to be introduced for Coda v6.0
1700 to support larger 128-bit file identifiers as needed by the
1701 new realms implementation.
1703 However this new API is not backward compatible with older
1704 clients. If you really need to run the old Coda userspace
1705 cache manager then say Y.
1707 For most cases you probably want to say N.
1709 config INTERMEZZO_FS
1710 tristate "InterMezzo file system support (replicating fs) (EXPERIMENTAL)"
1711 depends on INET && EXPERIMENTAL
1713 InterMezzo is a networked file system with disconnected operation
1714 and kernel level write back caching. It is most often used for
1715 replicating potentially large trees or keeping laptop/desktop copies
1718 If you say Y or M your kernel or module will provide InterMezzo
1719 support. You will also need a file server daemon, which you can get
1720 from <http://www.inter-mezzo.org/>.
1723 # for fs/nls/Config.in
1724 tristate "Andrew File System support (AFS) (Experimental)"
1725 depends on INET && EXPERIMENTAL
1728 If you say Y here, you will get an experimental Andrew File System
1729 driver. It currently only supports unsecured read-only AFS access.
1731 See Documentation/filesystems/afs.txt for more intormation.
1740 menu "Partition Types"
1742 source "fs/partitions/Kconfig"
1746 source "fs/nls/Kconfig"