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.
248 tristate "JFS filesystem support"
251 This is a port of IBM's Journaled Filesystem . More information is
252 available in the file Documentation/filesystems/jfs.txt.
254 If you do not intend to use the JFS filesystem, say N.
257 bool "JFS POSIX Access Control Lists"
260 Posix Access Control Lists (ACLs) support permissions for users and
261 groups beyond the owner/group/world scheme.
263 To learn more about Access Control Lists, visit the Posix ACLs for
264 Linux website <http://acl.bestbits.at/>.
266 If you don't know what Access Control Lists are, say N
272 If you are experiencing any problems with the JFS filesystem, say
273 Y here. This will result in additional debugging messages to be
274 written to the system log. Under normal circumstances, this
275 results in very little overhead.
277 config JFS_STATISTICS
278 bool "JFS statistics"
281 Enabling this option will cause statistics from the JFS file system
282 to be made available to the user in the /proc/fs/jfs/ directory.
285 # Posix ACL utility routines (for now, only ext2/ext3/jfs)
287 # NOTE: you can implement Posix ACLs without these helpers (XFS does).
288 # Never use this symbol for ifdefs.
291 depends on EXT2_FS_POSIX_ACL || EXT3_FS_POSIX_ACL || JFS_POSIX_ACL
295 tristate "XFS filesystem support"
297 XFS is a high performance journaling filesystem which originated
298 on the SGI IRIX platform. It is completely multi-threaded, can
299 support large files and large filesystems, extended attributes,
300 variable block sizes, is extent based, and makes extensive use of
301 Btrees (directories, extents, free space) to aid both performance
304 Refer to the documentation at <http://oss.sgi.com/projects/xfs/>
305 for complete details. This implementation is on-disk compatible
306 with the IRIX version of XFS.
308 To compile this file system support as a module, choose M here: the
309 module will be called xfs. Be aware, however, that if the file
310 system of your root partition is compiled as a module, you'll need
311 to use an initial ramdisk (initrd) to boot.
314 bool "Realtime support (EXPERIMENTAL)"
315 depends on XFS_FS && EXPERIMENTAL
317 If you say Y here you will be able to mount and use XFS filesystems
318 which contain a realtime subvolume. The realtime subvolume is a
319 separate area of disk space where only file data is stored. The
320 realtime subvolume is designed to provide very deterministic
321 data rates suitable for media streaming applications.
323 See the xfs man page in section 5 for a bit more information.
325 This feature is unsupported at this time, is not yet fully
326 functional, and may cause serious problems.
334 If you say Y here, you will be able to set limits for disk usage on
335 a per user and/or a per group basis under XFS. XFS considers quota
336 information as filesystem metadata and uses journaling to provide a
337 higher level guarantee of consistency. The on-disk data format for
338 quota is also compatible with the IRIX version of XFS, allowing a
339 filesystem to be migrated between Linux and IRIX without any need
342 If unsure, say N. More comprehensive documentation can be found in
343 README.quota in the xfsprogs package. XFS quota can be used either
344 with or without the generic quota support enabled (CONFIG_QUOTA) -
345 they are completely independent subsystems.
348 bool "Security Label support"
351 Security labels support alternative access control models
352 implemented by security modules like SELinux. This option
353 enables an extended attribute namespace for inode security
354 labels in the XFS filesystem.
356 If you are not using a security module that requires using
357 extended attributes for inode security labels, say N.
360 bool "POSIX ACL support"
363 POSIX Access Control Lists (ACLs) support permissions for users and
364 groups beyond the owner/group/world scheme.
366 To learn more about Access Control Lists, visit the POSIX ACLs for
367 Linux website <http://acl.bestbits.at/>.
369 If you don't know what Access Control Lists are, say N.
372 tristate "Minix fs support"
374 Minix is a simple operating system used in many classes about OS's.
375 The minix file system (method to organize files on a hard disk
376 partition or a floppy disk) was the original file system for Linux,
377 but has been superseded by the second extended file system ext2fs.
378 You don't want to use the minix file system on your hard disk
379 because of certain built-in restrictions, but it is sometimes found
380 on older Linux floppy disks. This option will enlarge your kernel
381 by about 28 KB. If unsure, say N.
383 To compile this file system support as a module, choose M here: the
384 module will be called minix. Note that the file system of your root
385 partition (the one containing the directory /) cannot be compiled as
389 tristate "ROM file system support"
391 This is a very small read-only file system mainly intended for
392 initial ram disks of installation disks, but it could be used for
393 other read-only media as well. Read
394 <file:Documentation/filesystems/romfs.txt> for details.
396 To compile this file system support as a module, choose M here: the
397 module will be called romfs. Note that the file system of your
398 root partition (the one containing the directory /) cannot be a
401 If you don't know whether you need it, then you don't need it:
407 If you say Y here, you will be able to set per user limits for disk
408 usage (also called disk quotas). Currently, it works for the
409 ext2, ext3, and reiserfs file system. ext3 also supports journalled
410 quotas for which you don't need to run quotacheck(8) after an unclean
411 shutdown. You need additional software in order to use quota support
412 (you can download sources from
413 <http://www.sf.net/projects/linuxquota/>). For further details, read
414 the Quota mini-HOWTO, available from
415 <http://www.tldp.org/docs.html#howto>, or the documentation provided
416 with the quota tools. Probably the quota support is only useful for
417 multi user systems. If unsure, say N.
420 tristate "Old quota format support"
423 This quota format was (is) used by kernels earlier than 2.4.22. If
424 you have quota working and you don't want to convert to new quota
428 tristate "Quota format v2 support"
431 This quota format allows using quotas with 32-bit UIDs/GIDs. If you
432 need this functionality say Y here. Note that you will need recent
433 quota utilities (>= 3.01) for new quota format with this kernel.
437 depends on XFS_QUOTA || QUOTA
441 tristate "Kernel automounter support"
443 The automounter is a tool to automatically mount remote file systems
444 on demand. This implementation is partially kernel-based to reduce
445 overhead in the already-mounted case; this is unlike the BSD
446 automounter (amd), which is a pure user space daemon.
448 To use the automounter you need the user-space tools from the autofs
449 package; you can find the location in <file:Documentation/Changes>.
450 You also want to answer Y to "NFS file system support", below.
452 If you want to use the newer version of the automounter with more
453 features, say N here and say Y to "Kernel automounter v4 support",
456 To compile this support as a module, choose M here: the module will be
459 If you are not a part of a fairly large, distributed network, you
460 probably do not need an automounter, and can say N here.
463 tristate "Kernel automounter version 4 support (also supports v3)"
465 The automounter is a tool to automatically mount remote file systems
466 on demand. This implementation is partially kernel-based to reduce
467 overhead in the already-mounted case; this is unlike the BSD
468 automounter (amd), which is a pure user space daemon.
470 To use the automounter you need the user-space tools from
471 <ftp://ftp.kernel.org/pub/linux/daemons/autofs/testing-v4/>; you also
472 want to answer Y to "NFS file system support", below.
474 To compile this support as a module, choose M here: the module will be
475 called autofs4. You will need to add "alias autofs autofs4" to your
476 modules configuration file.
478 If you are not a part of a fairly large, distributed network or
479 don't have a laptop which needs to dynamically reconfigure to the
480 local network, you probably do not need an automounter, and can say
483 menu "CD-ROM/DVD Filesystems"
486 tristate "ISO 9660 CDROM file system support"
488 This is the standard file system used on CD-ROMs. It was previously
489 known as "High Sierra File System" and is called "hsfs" on other
490 Unix systems. The so-called Rock-Ridge extensions which allow for
491 long Unix filenames and symbolic links are also supported by this
492 driver. If you have a CD-ROM drive and want to do more with it than
493 just listen to audio CDs and watch its LEDs, say Y (and read
494 <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO,
495 available from <http://www.tldp.org/docs.html#howto>), thereby
496 enlarging your kernel by about 27 KB; otherwise say N.
498 To compile this file system support as a module, choose M here: the
499 module will be called isofs.
502 bool "Microsoft Joliet CDROM extensions"
503 depends on ISO9660_FS
506 Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system
507 which allows for long filenames in unicode format (unicode is the
508 new 16 bit character code, successor to ASCII, which encodes the
509 characters of almost all languages of the world; see
510 <http://www.unicode.org/> for more information). Say Y here if you
511 want to be able to read Joliet CD-ROMs under Linux.
514 bool "Transparent decompression extension"
515 depends on ISO9660_FS
518 This is a Linux-specific extension to RockRidge which lets you store
519 data in compressed form on a CD-ROM and have it transparently
520 decompressed when the CD-ROM is accessed. See
521 <http://www.kernel.org/pub/linux/utils/fs/zisofs/> for the tools
522 necessary to create such a filesystem. Say Y here if you want to be
523 able to read such compressed CD-ROMs.
526 # for fs/nls/Config.in
532 tristate "UDF file system support"
534 This is the new file system used on some CD-ROMs and DVDs. Say Y if
535 you intend to mount DVD discs or CDRW's written in packet mode, or
536 if written to by other UDF utilities, such as DirectCD.
537 Please read <file:Documentation/filesystems/udf.txt>.
539 To compile this file system support as a module, choose M here: the
540 module will be called udf.
546 menu "DOS/FAT/NT Filesystems"
549 tristate "DOS FAT fs support"
552 If you want to use one of the FAT-based file systems (the MS-DOS,
553 VFAT (Windows 95) and UMSDOS (used to run Linux on top of an
554 ordinary DOS partition) file systems), then you must say Y or M here
555 to include FAT support. You will then be able to mount partitions or
556 diskettes with FAT-based file systems and transparently access the
557 files on them, i.e. MSDOS files will look and behave just like all
560 This FAT support is not a file system in itself, it only provides
561 the foundation for the other file systems. You will have to say Y or
562 M to at least one of "MSDOS fs support" or "VFAT fs support" in
563 order to make use of it.
565 Another way to read and write MSDOS floppies and hard drive
566 partitions from within Linux (but not transparently) is with the
567 mtools ("man mtools") program suite. You don't need to say Y here in
570 If you need to move large files on floppies between a DOS and a
571 Linux box, say Y here, mount the floppy under Linux with an MSDOS
572 file system and use GNU tar's M option. GNU tar is a program
573 available for Unix and DOS ("man tar" or "info tar").
575 It is now also becoming possible to read and write compressed FAT
576 file systems; read <file:Documentation/filesystems/fat_cvf.txt> for
579 The FAT support will enlarge your kernel by about 37 KB. If unsure,
582 To compile this as a module, choose M here: the module will be called
583 fat. Note that if you compile the FAT support as a module, you
584 cannot compile any of the FAT-based file systems into the kernel
585 -- they will have to be modules as well.
586 The file system of your root partition (the one containing the
587 directory /) cannot be a module, so don't say M here if you intend
588 to use UMSDOS as your root file system.
591 tristate "MSDOS fs support"
594 This allows you to mount MSDOS partitions of your hard drive (unless
595 they are compressed; to access compressed MSDOS partitions under
596 Linux, you can either use the DOS emulator DOSEMU, described in the
597 DOSEMU-HOWTO, available from
598 <http://www.tldp.org/docs.html#howto>, or try dmsdosfs in
599 <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you
600 intend to use dosemu with a non-compressed MSDOS partition, say Y
601 here) and MSDOS floppies. This means that file access becomes
602 transparent, i.e. the MSDOS files look and behave just like all
605 If you want to use UMSDOS, the Unix-like file system on top of a
606 DOS file system, which allows you to run Linux from within a DOS
607 partition without repartitioning, you'll have to say Y or M here.
609 If you have Windows 95 or Windows NT installed on your MSDOS
610 partitions, you should use the VFAT file system (say Y to "VFAT fs
611 support" below), or you will not be able to see the long filenames
612 generated by Windows 95 / Windows NT.
614 This option will enlarge your kernel by about 7 KB. If unsure,
615 answer Y. This will only work if you said Y to "DOS FAT fs support"
616 as well. To compile this as a module, choose M here: the module will
620 tristate "VFAT (Windows-95) fs support"
623 This option provides support for normal Windows file systems with
624 long filenames. That includes non-compressed FAT-based file systems
625 used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
626 programs from the mtools package.
628 You cannot use the VFAT file system for your Linux root partition
629 (the one containing the directory /); use UMSDOS instead if you
630 want to run Linux from within a DOS partition (i.e. say Y to
631 "Unix like fs on top of std MSDOS fs", below).
633 The VFAT support enlarges your kernel by about 10 KB and it only
634 works if you said Y to the "DOS FAT fs support" above. Please read
635 the file <file:Documentation/filesystems/vfat.txt> for details. If
638 To compile this as a module, choose M here: the module will be called
642 #dep_tristate ' UMSDOS: Unix-like file system on top of standard MSDOS fs' CONFIG_UMSDOS_FS $CONFIG_MSDOS_FS
643 # UMSDOS is temprory broken
646 Say Y here if you want to run Linux from within an existing DOS
647 partition of your hard drive. The advantage of this is that you can
648 get away without repartitioning your hard drive (which often implies
649 backing everything up and restoring afterwards) and hence you're
650 able to quickly try out Linux or show it to your friends; the
651 disadvantage is that Linux becomes susceptible to DOS viruses and
652 that UMSDOS is somewhat slower than ext2fs. Another use of UMSDOS
653 is to write files with long unix filenames to MSDOS floppies; it
654 also allows Unix-style soft-links and owner/permissions of files on
655 MSDOS floppies. You will need a program called umssync in order to
656 make use of UMSDOS; read
657 <file:Documentation/filesystems/umsdos.txt>.
659 To get utilities for initializing/checking UMSDOS file system, or
660 latest patches and/or information, visit the UMSDOS home page at
661 <http://www.voyager.hr/~mnalis/umsdos/>.
663 This option enlarges your kernel by about 28 KB and it only works if
664 you said Y to both "DOS FAT fs support" and "MSDOS fs support"
665 above. To compile this as a module, choose M here: the module will be
666 called umsdos. Note that the file system of your root partition
667 (the one containing the directory /) cannot be a module, so saying M
668 could be dangerous. If unsure, say N.
671 tristate "NTFS file system support"
674 NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003.
676 Saying Y or M here enables read support. There is partial, but
677 safe, write support available. For write support you must also
678 say Y to "NTFS write support" below.
680 There are also a number of user-space tools available, called
681 ntfsprogs. These include ntfsundelete and ntfsresize, that work
682 without NTFS support enabled in the kernel.
684 This is a rewrite from scratch of Linux NTFS support and replaced
685 the old NTFS code starting with Linux 2.5.11. A backport to
686 the Linux 2.4 kernel series is separately available as a patch
687 from the project web site.
689 For more information see <file:Documentation/filesystems/ntfs.txt>
690 and <http://linux-ntfs.sourceforge.net/>.
692 To compile this file system support as a module, choose M here: the
693 module will be called ntfs.
695 If you are not using Windows NT, 2000, XP or 2003 in addition to
696 Linux on your computer it is safe to say N.
699 bool "NTFS debugging support"
702 If you are experiencing any problems with the NTFS file system, say
703 Y here. This will result in additional consistency checks to be
704 performed by the driver as well as additional debugging messages to
705 be written to the system log. Note that debugging messages are
706 disabled by default. To enable them, supply the option debug_msgs=1
707 at the kernel command line when booting the kernel or as an option
708 to insmod when loading the ntfs module. Once the driver is active,
709 you can enable debugging messages by doing (as root):
710 echo 1 > /proc/sys/fs/ntfs-debug
711 Replacing the "1" with "0" would disable debug messages.
713 If you leave debugging messages disabled, this results in little
714 overhead, but enabling debug messages results in very significant
715 slowdown of the system.
717 When reporting bugs, please try to have available a full dump of
718 debugging messages while the misbehaviour was occurring.
721 bool "NTFS write support"
724 This enables the partial, but safe, write support in the NTFS driver.
726 The only supported operation is overwriting existing files, without
727 changing the file length. No file or directory creation, deletion or
728 renaming is possible. Note only non-resident files can be written to
729 so you may find that some very small files (<500 bytes or so) cannot
732 While we cannot guarantee that it will not damage any data, we have
733 so far not received a single report where the driver would have
734 damaged someones data so we assume it is perfectly safe to use.
736 Note: While write support is safe in this version (a rewrite from
737 scratch of the NTFS support), it should be noted that the old NTFS
738 write support, included in Linux 2.5.10 and before (since 1997),
741 This is currently useful with TopologiLinux. TopologiLinux is run
742 on top of any DOS/Microsoft Windows system without partitioning your
743 hard disk. Unlike other Linux distributions TopologiLinux does not
744 need its own partition. For more information see
745 <http://topologi-linux.sourceforge.net/>
747 It is perfectly safe to say N here.
751 menu "Pseudo filesystems"
754 bool "/proc file system support"
756 This is a virtual file system providing information about the status
757 of the system. "Virtual" means that it doesn't take up any space on
758 your hard disk: the files are created on the fly by the kernel when
759 you try to access them. Also, you cannot read the files with older
760 version of the program less: you need to use more or cat.
762 It's totally cool; for example, "cat /proc/interrupts" gives
763 information about what the different IRQs are used for at the moment
764 (there is a small number of Interrupt ReQuest lines in your computer
765 that are used by the attached devices to gain the CPU's attention --
766 often a source of trouble if two devices are mistakenly configured
767 to use the same IRQ). The program procinfo to display some
768 information about your system gathered from the /proc file system.
770 Before you can use the /proc file system, it has to be mounted,
771 meaning it has to be given a location in the directory hierarchy.
772 That location should be /proc. A command such as "mount -t proc proc
773 /proc" or the equivalent line in /etc/fstab does the job.
775 The /proc file system is explained in the file
776 <file:Documentation/filesystems/proc.txt> and on the proc(5) manpage
779 This option will enlarge your kernel by about 67 KB. Several
780 programs depend on this, so everyone should say Y here.
787 bool "sysfs file system support" if EMBEDDED
790 The sysfs filesystem is a virtual filesystem that the kernel uses to
791 export internal kernel objects, their attributes, and their
792 relationships to one another.
794 Users can use sysfs to ascertain useful information about the running
795 kernel, such as the devices the kernel has discovered on each bus and
796 which driver each is bound to. sysfs can also be used to tune devices
797 and other kernel subsystems.
799 Some system agents rely on the information in sysfs to operate.
800 /sbin/hotplug uses device and object attributes in sysfs to assist in
801 delegating policy decisions, like persistantly naming devices.
803 sysfs is currently used by the block subsystem to mount the root
804 partition. If sysfs is disabled you must specify the boot device on
805 the kernel boot command line via its major and minor numbers. For
806 example, "root=03:01" for /dev/hda1.
808 Designers of embedded systems may wish to say N here to conserve space.
811 bool "/dev file system support (OBSOLETE)"
812 depends on EXPERIMENTAL
814 This is support for devfs, a virtual file system (like /proc) which
815 provides the file system interface to device drivers, normally found
816 in /dev. Devfs does not depend on major and minor number
817 allocations. Device drivers register entries in /dev which then
818 appear automatically, which means that the system administrator does
819 not have to create character and block special device files in the
820 /dev directory using the mknod command (or MAKEDEV script) anymore.
822 This is work in progress. If you want to use this, you *must* read
823 the material in <file:Documentation/filesystems/devfs/>, especially
824 the file README there.
826 Note that devfs no longer manages /dev/pts! If you are using UNIX98
827 ptys, you will also need to mount the /dev/pts filesystem (devpts).
829 Note that devfs has been obsoleted by udev,
830 <http://www.kernel.org/pub/linux/utils/kernel/hotplug/>.
831 It has been stripped down to a bare minimum and is only provided for
832 legacy installations that use its naming scheme which is
833 unfortunately different from the names normal Linux installations
839 bool "Automatically mount at boot"
842 This option appears if you have CONFIG_DEVFS_FS enabled. Setting
843 this to 'Y' will make the kernel automatically mount devfs onto /dev
844 when the system is booted, before the init thread is started.
845 You can override this with the "devfs=nomount" boot option.
853 If you say Y here, then the /dev file system code will generate
854 debugging messages. See the file
855 <file:Documentation/filesystems/devfs/boot-options> for more
860 config DEVPTS_FS_XATTR
861 bool "/dev/pts Extended Attributes"
862 depends on UNIX98_PTYS
864 Extended attributes are name:value pairs associated with inodes by
865 the kernel or by users (see the attr(5) manual page, or visit
866 <http://acl.bestbits.at/> for details).
870 config DEVPTS_FS_SECURITY
871 bool "/dev/pts Security Labels"
872 depends on DEVPTS_FS_XATTR
874 Security labels support alternative access control models
875 implemented by security modules like SELinux. This option
876 enables an extended attribute handler for file security
877 labels in the /dev/pts filesystem.
879 If you are not using a security module that requires using
880 extended attributes for file security labels, say N.
883 bool "Virtual memory file system support (former shm fs)"
885 Tmpfs is a file system which keeps all files in virtual memory.
887 Everything in tmpfs is temporary in the sense that no files will be
888 created on your hard drive. The files live in memory and swap
889 space. If you unmount a tmpfs instance, everything stored therein is
892 See <file:Documentation/filesystems/tmpfs.txt> for details.
895 bool "HugeTLB file system support"
896 depends X86 || IA64 || PPC64 || SPARC64 || SUPERH || X86_64 || BROKEN
905 Ramfs is a file system which keeps all files in RAM. It allows
906 read and write access.
908 It is more of an programming example than a useable file system. If
909 you need a file system which lives in RAM with limit checking use
912 To compile this as a module, choose M here: the module will be called
916 tristate "Relayfs file system support"
918 Relayfs is a high-speed data relay filesystem designed to provide
919 an efficient mechanism for tools and facilities to relay large
920 amounts of data from kernel space to user space. It's not useful
921 on its own, and should only be enabled if other facilities that
922 need it are enabled, such as for example klog or the Linux Trace
925 See <file:Documentation/filesystems/relayfs.txt> for further
928 This file system is also available as a module ( = code which can be
929 inserted in and removed from the running kernel whenever you want).
930 The module is called relayfs. If you want to compile it as a
931 module, say M here and read <file:Documentation/modules.txt>.
936 bool "Enable klog debugging support"
937 depends on RELAYFS_FS
939 If you say Y to this, a relayfs channel named klog will be created
940 in the root of the relayfs file system. You can write to the klog
941 channel using klog() or klog_raw() from within the kernel or
942 kernel modules, and read from the klog channel by mounting relayfs
943 and using read(2) to read from it (or using cat). If you're not
946 config KLOG_CHANNEL_AUTOENABLE
947 bool "Enable klog logging on startup"
948 depends on KLOG_CHANNEL
951 If you say Y to this, the klog channel will be automatically enabled
952 on startup. Otherwise, to turn klog logging on, you need use
953 sysctl (fs.relayfs.klog_enabled). This option is used in cases where
954 you don't actually want the channel to be written to until it's
955 enabled. If you're not sure, say Y.
957 config KLOG_CHANNEL_SHIFT
958 depends on KLOG_CHANNEL
959 int "klog debugging channel size (14 => 16KB, 22 => 4MB)"
963 Select klog debugging channel size as a power of 2.
967 menu "Miscellaneous filesystems"
970 tristate "ADFS file system support (EXPERIMENTAL)"
971 depends on EXPERIMENTAL
973 The Acorn Disc Filing System is the standard file system of the
974 RiscOS operating system which runs on Acorn's ARM-based Risc PC
975 systems and the Acorn Archimedes range of machines. If you say Y
976 here, Linux will be able to read from ADFS partitions on hard drives
977 and from ADFS-formatted floppy discs. If you also want to be able to
978 write to those devices, say Y to "ADFS write support" below.
980 The ADFS partition should be the first partition (i.e.,
981 /dev/[hs]d?1) on each of your drives. Please read the file
982 <file:Documentation/filesystems/adfs.txt> for further details.
984 To compile this code as a module, choose M here: the module will be
990 bool "ADFS write support (DANGEROUS)"
993 If you say Y here, you will be able to write to ADFS partitions on
994 hard drives and ADFS-formatted floppy disks. This is experimental
995 codes, so if you're unsure, say N.
998 tristate "Amiga FFS file system support (EXPERIMENTAL)"
999 depends on EXPERIMENTAL
1001 The Fast File System (FFS) is the common file system used on hard
1002 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
1003 if you want to be able to read and write files from and to an Amiga
1004 FFS partition on your hard drive. Amiga floppies however cannot be
1005 read with this driver due to an incompatibility of the floppy
1006 controller used in an Amiga and the standard floppy controller in
1007 PCs and workstations. Read <file:Documentation/filesystems/affs.txt>
1008 and <file:fs/affs/Changes>.
1010 With this driver you can also mount disk files used by Bernd
1011 Schmidt's Un*X Amiga Emulator
1012 (<http://www.freiburg.linux.de/~uae/>).
1013 If you want to do this, you will also need to say Y or M to "Loop
1014 device support", above.
1016 To compile this file system support as a module, choose M here: the
1017 module will be called affs. If unsure, say N.
1020 tristate "Apple Macintosh file system support (EXPERIMENTAL)"
1021 depends on EXPERIMENTAL
1023 If you say Y here, you will be able to mount Macintosh-formatted
1024 floppy disks and hard drive partitions with full read-write access.
1025 Please read <file:fs/hfs/HFS.txt> to learn about the available mount
1028 To compile this file system support as a module, choose M here: the
1029 module will be called hfs.
1032 tristate "Apple Extended HFS file system support"
1035 If you say Y here, you will be able to mount extended format
1036 Macintosh-formatted hard drive partitions with full read-write access.
1038 This file system is often called HFS+ and was introduced with
1039 MacOS 8. It includes all Mac specific filesystem data such as
1040 data forks and creator codes, but it also has several UNIX
1041 style features such as file ownership and permissions.
1044 tristate "BeOS file systemv(BeFS) support (read only) (EXPERIMENTAL)"
1045 depends on EXPERIMENTAL
1048 The BeOS File System (BeFS) is the native file system of Be, Inc's
1049 BeOS. Notable features include support for arbitrary attributes
1050 on files and directories, and database-like indices on selected
1051 attributes. (Also note that this driver doesn't make those features
1052 available at this time). It is a 64 bit filesystem, so it supports
1053 extreemly large volumes and files.
1055 If you use this filesystem, you should also say Y to at least one
1056 of the NLS (native language support) options below.
1058 If you don't know what this is about, say N.
1060 To compile this as a module, choose M here: the module will be
1067 If you say Y here, you can use the 'debug' mount option to enable
1068 debugging output from the driver.
1071 tristate "BFS file system support (EXPERIMENTAL)"
1072 depends on EXPERIMENTAL
1074 Boot File System (BFS) is a file system used under SCO UnixWare to
1075 allow the bootloader access to the kernel image and other important
1076 files during the boot process. It is usually mounted under /stand
1077 and corresponds to the slice marked as "STAND" in the UnixWare
1078 partition. You should say Y if you want to read or write the files
1079 on your /stand slice from within Linux. You then also need to say Y
1080 to "UnixWare slices support", below. More information about the BFS
1081 file system is contained in the file
1082 <file:Documentation/filesystems/bfs.txt>.
1084 If you don't know what this is about, say N.
1086 To compile this as a module, choose M here: the module will be called
1087 bfs. Note that the file system of your root partition (the one
1088 containing the directory /) cannot be compiled as a module.
1093 tristate "EFS file system support (read only) (EXPERIMENTAL)"
1094 depends on EXPERIMENTAL
1096 EFS is an older file system used for non-ISO9660 CD-ROMs and hard
1097 disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
1098 uses the XFS file system for hard disk partitions however).
1100 This implementation only offers read-only access. If you don't know
1101 what all this is about, it's safe to say N. For more information
1102 about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
1104 To compile the EFS file system support as a module, choose M here: the
1105 module will be called efs.
1108 tristate "Journalling Flash File System (JFFS) support"
1111 JFFS is the Journaling Flash File System developed by Axis
1112 Communications in Sweden, aimed at providing a crash/powerdown-safe
1113 file system for disk-less embedded devices. Further information is
1114 available at (<http://developer.axis.com/software/jffs/>).
1116 config JFFS_FS_VERBOSE
1117 int "JFFS debugging verbosity (0 = quiet, 3 = noisy)"
1121 Determines the verbosity level of the JFFS debugging messages.
1124 bool "JFFS stats available in /proc filesystem"
1125 depends on JFFS_FS && PROC
1127 Enabling this option will cause statistics from mounted JFFS file systems
1128 to be made available to the user in the /proc/fs/jffs/ directory.
1131 tristate "Journalling Flash File System v2 (JFFS2) support"
1137 JFFS2 is the second generation of the Journalling Flash File System
1138 for use on diskless embedded devices. It provides improved wear
1139 levelling, compression and support for hard links. You cannot use
1140 this on normal block devices, only on 'MTD' devices.
1142 Further information on the design and implementation of JFFS2 is
1143 available at <http://sources.redhat.com/jffs2/>.
1145 config JFFS2_FS_DEBUG
1146 int "JFFS2 debugging verbosity (0 = quiet, 2 = noisy)"
1150 This controls the amount of debugging messages produced by the JFFS2
1151 code. Set it to zero for use in production systems. For evaluation,
1152 testing and debugging, it's advisable to set it to one. This will
1153 enable a few assertions and will print debugging messages at the
1154 KERN_DEBUG loglevel, where they won't normally be visible. Level 2
1155 is unlikely to be useful - it enables extra debugging in certain
1156 areas which at one point needed debugging, but when the bugs were
1157 located and fixed, the detailed messages were relegated to level 2.
1159 If reporting bugs, please try to have available a full dump of the
1160 messages at debug level 1 while the misbehaviour was occurring.
1162 config JFFS2_FS_NAND
1163 bool "JFFS2 support for NAND flash (EXPERIMENTAL)"
1164 depends on JFFS2_FS && EXPERIMENTAL
1167 This enables the experimental support for NAND flash in JFFS2. NAND
1168 is a newer type of flash chip design than the traditional NOR flash,
1169 with higher density but a handful of characteristics which make it
1170 more interesting for the file system to use. Support for NAND flash
1171 is not yet complete and may corrupt data. For further information,
1172 including a link to the mailing list where details of the remaining
1173 work to be completed for NAND flash support can be found, see the
1174 JFFS2 web site at <http://sources.redhat.com/jffs2>.
1176 Say 'N' unless you have NAND flash and you are willing to test and
1177 develop JFFS2 support for it.
1180 tristate "Compressed ROM file system support"
1183 Saying Y here includes support for CramFs (Compressed ROM File
1184 System). CramFs is designed to be a simple, small, and compressed
1185 file system for ROM based embedded systems. CramFs is read-only,
1186 limited to 256MB file systems (with 16MB files), and doesn't support
1187 16/32 bits uid/gid, hard links and timestamps.
1189 See <file:Documentation/filesystems/cramfs.txt> and
1190 <file:fs/cramfs/README> for further information.
1192 To compile this as a module, choose M here: the module will be called
1193 cramfs. Note that the root file system (the one containing the
1194 directory /) cannot be compiled as a module.
1199 tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
1201 FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
1202 file system format. VERITAS VxFS(TM) is the standard file system
1203 of SCO UnixWare (and possibly others) and optionally available
1204 for Sunsoft Solaris, HP-UX and many other operating systems.
1205 Currently only readonly access is supported.
1207 NOTE: the file system type as used by mount(1), mount(2) and
1208 fstab(5) is 'vxfs' as it describes the file system format, not
1211 To compile this as a module, choose M here: the module will be
1212 called freevxfs. If unsure, say N.
1216 tristate "OS/2 HPFS file system support"
1218 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
1219 is the file system used for organizing files on OS/2 hard disk
1220 partitions. Say Y if you want to be able to read files from and
1221 write files to an OS/2 HPFS partition on your hard drive. OS/2
1222 floppies however are in regular MSDOS format, so you don't need this
1223 option in order to be able to read them. Read
1224 <file:Documentation/filesystems/hpfs.txt>.
1226 To compile this file system support as a module, choose M here: the
1227 module will be called hpfs. If unsure, say N.
1230 tristate "QNX4 file system support (read only)"
1232 This is the file system used by the real-time operating systems
1233 QNX 4 and QNX 6 (the latter is also called QNX RTP).
1234 Further information is available at <http://www.qnx.com/>.
1235 Say Y if you intend to mount QNX hard disks or floppies.
1236 Unless you say Y to "QNX4FS read-write support" below, you will
1237 only be able to read these file systems.
1239 To compile this file system support as a module, choose M here: the
1240 module will be called qnx4.
1242 If you don't know whether you need it, then you don't need it:
1246 bool "QNX4FS write support (DANGEROUS)"
1247 depends on QNX4FS_FS && EXPERIMENTAL
1249 Say Y if you want to test write support for QNX4 file systems.
1251 It's currently broken, so for now:
1255 tristate "System V/Xenix/V7/Coherent file system support"
1257 SCO, Xenix and Coherent are commercial Unix systems for Intel
1258 machines, and Version 7 was used on the DEC PDP-11. Saying Y
1259 here would allow you to read from their floppies and hard disk
1262 If you have floppies or hard disk partitions like that, it is likely
1263 that they contain binaries from those other Unix systems; in order
1264 to run these binaries, you will want to install linux-abi which is a
1265 a set of kernel modules that lets you run SCO, Xenix, Wyse,
1266 UnixWare, Dell Unix and System V programs under Linux. It is
1267 available via FTP (user: ftp) from
1268 <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
1269 NOTE: that will work only for binaries from Intel-based systems;
1270 PDP ones will have to wait until somebody ports Linux to -11 ;-)
1272 If you only intend to mount files from some other Unix over the
1273 network using NFS, you don't need the System V file system support
1274 (but you need NFS file system support obviously).
1276 Note that this option is generally not needed for floppies, since a
1277 good portable way to transport files and directories between unixes
1278 (and even other operating systems) is given by the tar program ("man
1279 tar" or preferably "info tar"). Note also that this option has
1280 nothing whatsoever to do with the option "System V IPC". Read about
1281 the System V file system in
1282 <file:Documentation/filesystems/sysv-fs.txt>.
1283 Saying Y here will enlarge your kernel by about 27 KB.
1285 To compile this as a module, choose M here: the module will be called
1288 If you haven't heard about all of this before, it's safe to say N.
1291 tristate "UFS file system support (read only)"
1293 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
1294 OpenBSD and NeXTstep) use a file system called UFS. Some System V
1295 Unixes can create and mount hard disk partitions and diskettes using
1296 this file system as well. Saying Y here will allow you to read from
1297 these partitions; if you also want to write to them, say Y to the
1298 experimental "UFS file system write support", below. Please read the
1299 file <file:Documentation/filesystems/ufs.txt> for more information.
1301 The recently released UFS2 variant (used in FreeBSD 5.x) is
1302 READ-ONLY supported.
1304 If you only intend to mount files from some other Unix over the
1305 network using NFS, you don't need the UFS file system support (but
1306 you need NFS file system support obviously).
1308 Note that this option is generally not needed for floppies, since a
1309 good portable way to transport files and directories between unixes
1310 (and even other operating systems) is given by the tar program ("man
1311 tar" or preferably "info tar").
1313 When accessing NeXTstep files, you may need to convert them from the
1314 NeXT character set to the Latin1 character set; use the program
1315 recode ("info recode") for this purpose.
1317 To compile the UFS file system support as a module, choose M here: the
1318 module will be called ufs.
1320 If you haven't heard about all of this before, it's safe to say N.
1323 bool "UFS file system write support (DANGEROUS)"
1324 depends on UFS_FS && EXPERIMENTAL
1326 Say Y here if you want to try writing to UFS partitions. This is
1327 experimental, so you should back up your UFS partitions beforehand.
1331 menu "Network File Systems"
1335 tristate "NFS file system support"
1340 If you are connected to some other (usually local) Unix computer
1341 (using SLIP, PLIP, PPP or Ethernet) and want to mount files residing
1342 on that computer (the NFS server) using the Network File Sharing
1343 protocol, say Y. "Mounting files" means that the client can access
1344 the files with usual UNIX commands as if they were sitting on the
1345 client's hard disk. For this to work, the server must run the
1346 programs nfsd and mountd (but does not need to have NFS file system
1347 support enabled in its kernel). NFS is explained in the Network
1348 Administrator's Guide, available from
1349 <http://www.tldp.org/docs.html#guide>, on its man page: "man
1350 nfs", and in the NFS-HOWTO.
1352 A superior but less widely used alternative to NFS is provided by
1353 the Coda file system; see "Coda file system support" below.
1355 If you say Y here, you should have said Y to TCP/IP networking also.
1356 This option would enlarge your kernel by about 27 KB.
1358 To compile this file system support as a module, choose M here: the
1359 module will be called nfs.
1361 If you are configuring a diskless machine which will mount its root
1362 file system over NFS at boot time, say Y here and to "Kernel
1363 level IP autoconfiguration" above and to "Root file system on NFS"
1364 below. You cannot compile this driver as a module in this case.
1365 There are two packages designed for booting diskless machines over
1366 the net: netboot, available from
1367 <http://ftp1.sourceforge.net/netboot/>, and Etherboot,
1368 available from <http://ftp1.sourceforge.net/etherboot/>.
1370 If you don't know what all this is about, say N.
1373 bool "Provide NFSv3 client support"
1376 Say Y here if you want your NFS client to be able to speak the newer
1377 version 3 of the NFS protocol.
1382 bool "Provide NFSv4 client support (EXPERIMENTAL)"
1383 depends on NFS_FS && EXPERIMENTAL
1384 select RPCSEC_GSS_KRB5
1386 Say Y here if you want your NFS client to be able to speak the newer
1387 version 4 of the NFS protocol.
1389 Note: Requires auxiliary userspace daemons which may be found on
1390 http://www.citi.umich.edu/projects/nfsv4/
1395 bool "Allow direct I/O on NFS files (EXPERIMENTAL)"
1396 depends on NFS_FS && EXPERIMENTAL
1398 This option enables applications to perform uncached I/O on files
1399 in NFS file systems using the O_DIRECT open() flag. When O_DIRECT
1400 is set for a file, its data is not cached in the system's page
1401 cache. Data is moved to and from user-level application buffers
1402 directly. Unlike local disk-based file systems, NFS O_DIRECT has
1403 no alignment restrictions.
1405 Unless your program is designed to use O_DIRECT properly, you are
1406 much better off allowing the NFS client to manage data caching for
1407 you. Misusing O_DIRECT can cause poor server performance or network
1408 storms. This kernel build option defaults OFF to avoid exposing
1409 system administrators unwittingly to a potentially hazardous
1412 For more details on NFS O_DIRECT, see fs/nfs/direct.c.
1414 If unsure, say N. This reduces the size of the NFS client, and
1415 causes open() to return EINVAL if a file residing in NFS is
1416 opened with the O_DIRECT flag.
1419 tristate "NFS server support"
1424 If you want your Linux box to act as an NFS *server*, so that other
1425 computers on your local network which support NFS can access certain
1426 directories on your box transparently, you have two options: you can
1427 use the self-contained user space program nfsd, in which case you
1428 should say N here, or you can say Y and use the kernel based NFS
1429 server. The advantage of the kernel based solution is that it is
1432 In either case, you will need support software; the respective
1433 locations are given in the file <file:Documentation/Changes> in the
1436 If you say Y here, you will get support for version 2 of the NFS
1437 protocol (NFSv2). If you also want NFSv3, say Y to the next question
1440 Please read the NFS-HOWTO, available from
1441 <http://www.tldp.org/docs.html#howto>.
1443 To compile the NFS server support as a module, choose M here: the
1444 module will be called nfsd. If unsure, say N.
1447 bool "Provide NFSv3 server support"
1450 If you would like to include the NFSv3 server as well as the NFSv2
1451 server, say Y here. If unsure, say Y.
1454 bool "Provide NFSv4 server support (EXPERIMENTAL)"
1455 depends on NFSD_V3 && EXPERIMENTAL
1457 If you would like to include the NFSv4 server as well as the NFSv2
1458 and NFSv3 servers, say Y here. This feature is experimental, and
1459 should only be used if you are interested in helping to test NFSv4.
1463 bool "Provide NFS server over TCP support (EXPERIMENTAL)"
1464 depends on NFSD && EXPERIMENTAL
1466 Enable NFS service over TCP connections. This the officially
1467 still experimental, but seems to work well.
1470 bool "Root file system on NFS"
1471 depends on NFS_FS=y && IP_PNP
1473 If you want your Linux box to mount its whole root file system (the
1474 one containing the directory /) from some other computer over the
1475 net via NFS (presumably because your box doesn't have a hard disk),
1476 say Y. Read <file:Documentation/nfsroot.txt> for details. It is
1477 likely that in this case, you also want to say Y to "Kernel level IP
1478 autoconfiguration" so that your box can discover its network address
1481 Most people say N here.
1488 depends on NFSD_V3 || NFS_V3
1501 config RPCSEC_GSS_KRB5
1502 tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
1503 depends on SUNRPC && EXPERIMENTAL
1509 Provides for secure RPC calls by means of a gss-api
1510 mechanism based on Kerberos V5. This is required for
1513 Note: Requires an auxiliary userspace daemon which may be found on
1514 http://www.citi.umich.edu/projects/nfsv4/
1519 tristate "SMB file system support (to mount Windows shares etc.)"
1523 SMB (Server Message Block) is the protocol Windows for Workgroups
1524 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
1525 files and printers over local networks. Saying Y here allows you to
1526 mount their file systems (often called "shares" in this context) and
1527 access them just like any other Unix directory. Currently, this
1528 works only if the Windows machines use TCP/IP as the underlying
1529 transport protocol, and not NetBEUI. For details, read
1530 <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
1531 available from <http://www.tldp.org/docs.html#howto>.
1533 Note: if you just want your box to act as an SMB *server* and make
1534 files and printing services available to Windows clients (which need
1535 to have a TCP/IP stack), you don't need to say Y here; you can use
1536 the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
1539 General information about how to connect Linux, Windows machines and
1540 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1542 To compile the SMB support as a module, choose M here: the module will
1543 be called smbfs. Most people say N, however.
1545 config SMB_NLS_DEFAULT
1546 bool "Use a default NLS"
1549 Enabling this will make smbfs use nls translations by default. You
1550 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
1551 settings and you need to give the default nls for the SMB server as
1552 CONFIG_SMB_NLS_REMOTE.
1554 The nls settings can be changed at mount time, if your smbmount
1555 supports that, using the codepage and iocharset parameters.
1557 smbmount from samba 2.2.0 or later supports this.
1559 config SMB_NLS_REMOTE
1560 string "Default Remote NLS Option"
1561 depends on SMB_NLS_DEFAULT
1564 This setting allows you to specify a default value for which
1565 codepage the server uses. If this field is left blank no
1566 translations will be done by default. The local codepage/charset
1567 default to CONFIG_NLS_DEFAULT.
1569 The nls settings can be changed at mount time, if your smbmount
1570 supports that, using the codepage and iocharset parameters.
1572 smbmount from samba 2.2.0 or later supports this.
1575 tristate "CIFS support (advanced network filesystem for Samba, Window and other CIFS compliant servers)(EXPERIMENTAL)"
1579 This is the client VFS module for the Common Internet File System
1580 (CIFS) protocol which is the successor to the Server Message Block
1581 (SMB) protocol, the native file sharing mechanism for most early
1582 PC operating systems. CIFS is fully supported by current network
1583 file servers such as Windows 2000 (including Windows NT version 4
1584 and Windows XP) as well by Samba (which provides excellent CIFS
1585 server support for Linux and many other operating systems). For
1586 production systems the smbfs module may be used instead of this
1587 cifs module since smbfs is currently more stable and provides
1588 support for older servers. The intent of this module is to provide the
1589 most advanced network file system function for CIFS compliant servers,
1590 including support for dfs (hierarchical name space), secure per-user
1591 session establishment, safe distributed caching (oplock), optional
1592 packet signing, Unicode and other internationalization improvements, and
1593 optional Winbind (nsswitch) integration. This module is in an early
1594 development stage, so unless you are specifically interested in this
1595 filesystem, just say N.
1598 tristate "NCP file system support (to mount NetWare volumes)"
1599 depends on IPX!=n || INET
1601 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
1602 used by Novell NetWare clients to talk to file servers. It is to
1603 IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
1604 to mount NetWare file server volumes and to access them just like
1605 any other Unix directory. For details, please read the file
1606 <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
1607 the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
1609 You do not have to say Y here if you want your Linux box to act as a
1610 file *server* for Novell NetWare clients.
1612 General information about how to connect Linux, Windows machines and
1613 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1615 To compile this as a module, choose M here: the module will be called
1616 ncpfs. Say N unless you are connected to a Novell network.
1618 source "fs/ncpfs/Kconfig"
1621 tristate "Coda file system support (advanced network fs)"
1624 Coda is an advanced network file system, similar to NFS in that it
1625 enables you to mount file systems of a remote server and access them
1626 with regular Unix commands as if they were sitting on your hard
1627 disk. Coda has several advantages over NFS: support for
1628 disconnected operation (e.g. for laptops), read/write server
1629 replication, security model for authentication and encryption,
1630 persistent client caches and write back caching.
1632 If you say Y here, your Linux box will be able to act as a Coda
1633 *client*. You will need user level code as well, both for the
1634 client and server. Servers are currently user level, i.e. they need
1635 no kernel support. Please read
1636 <file:Documentation/filesystems/coda.txt> and check out the Coda
1637 home page <http://www.coda.cs.cmu.edu/>.
1639 To compile the coda client support as a module, choose M here: the
1640 module will be called coda.
1642 config CODA_FS_OLD_API
1643 bool "Use 96-bit Coda file identifiers"
1646 A new kernel-userspace API had to be introduced for Coda v6.0
1647 to support larger 128-bit file identifiers as needed by the
1648 new realms implementation.
1650 However this new API is not backward compatible with older
1651 clients. If you really need to run the old Coda userspace
1652 cache manager then say Y.
1654 For most cases you probably want to say N.
1657 # Intermezzo broke when we added the expanded NGROUPS patches
1659 config INTERMEZZO_FS
1660 tristate "InterMezzo file system support (replicating fs) (EXPERIMENTAL)"
1661 depends on INET && EXPERIMENTAL
1663 InterMezzo is a networked file system with disconnected operation
1664 and kernel level write back caching. It is most often used for
1665 replicating potentially large trees or keeping laptop/desktop copies
1668 If you say Y or M your kernel or module will provide InterMezzo
1669 support. You will also need a file server daemon, which you can get
1670 from <http://www.inter-mezzo.org/>.
1673 # for fs/nls/Config.in
1674 tristate "Andrew File System support (AFS) (Experimental)"
1675 depends on INET && EXPERIMENTAL
1678 If you say Y here, you will get an experimental Andrew File System
1679 driver. It currently only supports unsecured read-only AFS access.
1681 See Documentation/filesystems/afs.txt for more intormation.
1690 menu "Partition Types"
1692 source "fs/partitions/Kconfig"
1696 source "fs/nls/Kconfig"