2 # File system configuration
8 tristate "Second extended fs support"
10 Ext2 is a standard Linux file system for hard disks.
12 To compile this file system support as a module, choose M here: the
13 module will be called ext2. Be aware however that the file system
14 of your root partition (the one containing the directory /) cannot
15 be compiled as a module, and so this could be dangerous.
20 bool "Ext2 extended attributes"
23 Extended attributes are name:value pairs associated with inodes by
24 the kernel or by users (see the attr(5) manual page, or visit
25 <http://acl.bestbits.at/> for details).
29 config EXT2_FS_POSIX_ACL
30 bool "Ext2 POSIX Access Control Lists"
31 depends on EXT2_FS_XATTR
33 Posix Access Control Lists (ACLs) support permissions for users and
34 groups beyond the owner/group/world scheme.
36 To learn more about Access Control Lists, visit the Posix ACLs for
37 Linux website <http://acl.bestbits.at/>.
39 If you don't know what Access Control Lists are, say N
41 config EXT2_FS_SECURITY
42 bool "Ext2 Security Labels"
43 depends on EXT2_FS_XATTR
45 Security labels support alternative access control models
46 implemented by security modules like SELinux. This option
47 enables an extended attribute handler for file security
48 labels in the ext2 filesystem.
50 If you are not using a security module that requires using
51 extended attributes for file security labels, say N.
54 tristate "Ext3 journalling file system support"
56 This is the journaling version of the Second extended file system
57 (often called ext3), the de facto standard Linux file system
58 (method to organize files on a storage device) for hard disks.
60 The journaling code included in this driver means you do not have
61 to run e2fsck (file system checker) on your file systems after a
62 crash. The journal keeps track of any changes that were being made
63 at the time the system crashed, and can ensure that your file system
64 is consistent without the need for a lengthy check.
66 Other than adding the journal to the file system, the on-disk format
67 of ext3 is identical to ext2. It is possible to freely switch
68 between using the ext3 driver and the ext2 driver, as long as the
69 file system has been cleanly unmounted, or e2fsck is run on the file
72 To add a journal on an existing ext2 file system or change the
73 behavior of ext3 file systems, you can use the tune2fs utility ("man
74 tune2fs"). To modify attributes of files and directories on ext3
75 file systems, use chattr ("man chattr"). You need to be using
76 e2fsprogs version 1.20 or later in order to create ext3 journals
77 (available at <http://sourceforge.net/projects/e2fsprogs/>).
79 To compile this file system support as a module, choose M here: the
80 module will be called ext3. Be aware however that the file system
81 of your root partition (the one containing the directory /) cannot
82 be compiled as a module, and so this may be dangerous.
85 bool "Ext3 extended attributes"
89 Extended attributes are name:value pairs associated with inodes by
90 the kernel or by users (see the attr(5) manual page, or visit
91 <http://acl.bestbits.at/> for details).
95 You need this for POSIX ACL support on ext3.
97 config EXT3_FS_POSIX_ACL
98 bool "Ext3 POSIX Access Control Lists"
99 depends on EXT3_FS_XATTR
101 Posix Access Control Lists (ACLs) support permissions for users and
102 groups beyond the owner/group/world scheme.
104 To learn more about Access Control Lists, visit the Posix ACLs for
105 Linux website <http://acl.bestbits.at/>.
107 If you don't know what Access Control Lists are, say N
109 config EXT3_FS_SECURITY
110 bool "Ext3 Security Labels"
111 depends on EXT3_FS_XATTR
113 Security labels support alternative access control models
114 implemented by security modules like SELinux. This option
115 enables an extended attribute handler for file security
116 labels in the ext3 filesystem.
118 If you are not using a security module that requires using
119 extended attributes for file security labels, say N.
122 # CONFIG_JBD could be its own option (even modular), but until there are
123 # other users than ext3, we will simply make it be the same as CONFIG_EXT3_FS
124 # dep_tristate ' Journal Block Device support (JBD for ext3)' CONFIG_JBD $CONFIG_EXT3_FS
128 This is a generic journaling layer for block devices. It is
129 currently used by the ext3 file system, but it could also be used to
130 add journal support to other file systems or block devices such as
133 If you are using the ext3 file system, you need to say Y here. If
134 you are not using ext3 then you will probably want to say N.
136 To compile this device as a module, choose M here: the module will be
137 called jbd. If you are compiling ext3 into the kernel, you cannot
138 compile this code as a module.
141 bool "JBD (ext3) debugging support"
144 If you are using the ext3 journaled file system (or potentially any
145 other file system/device using JBD), this option allows you to
146 enable debugging output while the system is running, in order to
147 help track down any problems you are having. By default the
148 debugging output will be turned off.
150 If you select Y here, then you will be able to turn on debugging
151 with "echo N > /proc/sys/fs/jbd-debug", where N is a number between
152 1 and 5, the higher the number, the more debugging output is
153 generated. To turn debugging off again, do
154 "echo 0 > /proc/sys/fs/jbd-debug".
157 # Meta block cache for Extended Attributes (ext2/ext3)
159 depends on EXT2_FS_XATTR || EXT3_FS_XATTR
160 default y if EXT2_FS=y || EXT3_FS=y
161 default m if EXT2_FS=m || EXT3_FS=m
164 tristate "Reiserfs support"
166 Stores not just filenames but the files themselves in a balanced
167 tree. Uses journaling.
169 Balanced trees are more efficient than traditional file system
170 architectural foundations.
172 In general, ReiserFS is as fast as ext2, but is very efficient with
173 large directories and small files. Additional patches are needed
174 for NFS and quotas, please see <http://www.namesys.com/> for links.
176 It is more easily extended to have features currently found in
177 database and keyword search systems than block allocation based file
178 systems are. The next version will be so extended, and will support
179 plugins consistent with our motto ``It takes more than a license to
180 make source code open.''
182 Read <http://www.namesys.com/> to learn more about reiserfs.
184 Sponsored by Threshold Networks, Emusic.com, and Bigstorage.com.
186 If you like it, you can pay us to add new features to it that you
187 need, buy a support contract, or pay us to port it to another OS.
189 config REISERFS_CHECK
190 bool "Enable reiserfs debug mode"
191 depends on REISERFS_FS
193 If you set this to Y, then ReiserFS will perform every check it can
194 possibly imagine of its internal consistency throughout its
195 operation. It will also go substantially slower. More than once we
196 have forgotten that this was on, and then gone despondent over the
197 latest benchmarks.:-) Use of this option allows our team to go all
198 out in checking for consistency when debugging without fear of its
199 effect on end users. If you are on the verge of sending in a bug
200 report, say Y and you might get a useful error message. Almost
201 everyone should say N.
203 config REISERFS_PROC_INFO
204 bool "Stats in /proc/fs/reiserfs"
205 depends on REISERFS_FS
207 Create under /proc/fs/reiserfs a hierarchy of files, displaying
208 various ReiserFS statistics and internal data at the expense of
209 making your kernel or module slightly larger (+8 KB). This also
210 increases the amount of kernel memory required for each mount.
211 Almost everyone but ReiserFS developers and people fine-tuning
212 reiserfs or tracing problems should say N.
214 config REISERFS_FS_XATTR
215 bool "ReiserFS extended attributes"
216 depends on REISERFS_FS
218 Extended attributes are name:value pairs associated with inodes by
219 the kernel or by users (see the attr(5) manual page, or visit
220 <http://acl.bestbits.at/> for details).
224 config REISERFS_FS_POSIX_ACL
225 bool "ReiserFS POSIX Access Control Lists"
226 depends on REISERFS_FS_XATTR
228 Posix Access Control Lists (ACLs) support permissions for users and
229 groups beyond the owner/group/world scheme.
231 To learn more about Access Control Lists, visit the Posix ACLs for
232 Linux website <http://acl.bestbits.at/>.
234 If you don't know what Access Control Lists are, say N
236 config REISERFS_FS_SECURITY
237 bool "ReiserFS Security Labels"
238 depends on REISERFS_FS_XATTR
240 Security labels support alternative access control models
241 implemented by security modules like SELinux. This option
242 enables an extended attribute handler for file security
243 labels in the ReiserFS filesystem.
245 If you are not using a security module that requires using
246 extended attributes for file security labels, say N.
249 tristate "JFS filesystem support"
252 This is a port of IBM's Journaled Filesystem . More information is
253 available in the file Documentation/filesystems/jfs.txt.
255 If you do not intend to use the JFS filesystem, say N.
258 bool "JFS POSIX Access Control Lists"
261 Posix Access Control Lists (ACLs) support permissions for users and
262 groups beyond the owner/group/world scheme.
264 To learn more about Access Control Lists, visit the Posix ACLs for
265 Linux website <http://acl.bestbits.at/>.
267 If you don't know what Access Control Lists are, say N
273 If you are experiencing any problems with the JFS filesystem, say
274 Y here. This will result in additional debugging messages to be
275 written to the system log. Under normal circumstances, this
276 results in very little overhead.
278 config JFS_STATISTICS
279 bool "JFS statistics"
282 Enabling this option will cause statistics from the JFS file system
283 to be made available to the user in the /proc/fs/jfs/ directory.
286 # Posix ACL utility routines (for now, only ext2/ext3/jfs/reiserfs)
288 # NOTE: you can implement Posix ACLs without these helpers (XFS does).
289 # Never use this symbol for ifdefs.
292 depends on EXT2_FS_POSIX_ACL || EXT3_FS_POSIX_ACL || JFS_POSIX_ACL || REISERFS_FS_POSIX_ACL
296 tristate "XFS filesystem support"
298 XFS is a high performance journaling filesystem which originated
299 on the SGI IRIX platform. It is completely multi-threaded, can
300 support large files and large filesystems, extended attributes,
301 variable block sizes, is extent based, and makes extensive use of
302 Btrees (directories, extents, free space) to aid both performance
305 Refer to the documentation at <http://oss.sgi.com/projects/xfs/>
306 for complete details. This implementation is on-disk compatible
307 with the IRIX version of XFS.
309 To compile this file system support as a module, choose M here: the
310 module will be called xfs. Be aware, however, that if the file
311 system of your root partition is compiled as a module, you'll need
312 to use an initial ramdisk (initrd) to boot.
315 bool "Realtime support (EXPERIMENTAL)"
316 depends on XFS_FS && EXPERIMENTAL
318 If you say Y here you will be able to mount and use XFS filesystems
319 which contain a realtime subvolume. The realtime subvolume is a
320 separate area of disk space where only file data is stored. The
321 realtime subvolume is designed to provide very deterministic
322 data rates suitable for media streaming applications.
324 See the xfs man page in section 5 for a bit more information.
326 This feature is unsupported at this time, is not yet fully
327 functional, and may cause serious problems.
335 If you say Y here, you will be able to set limits for disk usage on
336 a per user and/or a per group basis under XFS. XFS considers quota
337 information as filesystem metadata and uses journaling to provide a
338 higher level guarantee of consistency. The on-disk data format for
339 quota is also compatible with the IRIX version of XFS, allowing a
340 filesystem to be migrated between Linux and IRIX without any need
343 If unsure, say N. More comprehensive documentation can be found in
344 README.quota in the xfsprogs package. XFS quota can be used either
345 with or without the generic quota support enabled (CONFIG_QUOTA) -
346 they are completely independent subsystems.
349 bool "Security Label support"
352 Security labels support alternative access control models
353 implemented by security modules like SELinux. This option
354 enables an extended attribute namespace for inode security
355 labels in the XFS filesystem.
357 If you are not using a security module that requires using
358 extended attributes for inode security labels, say N.
361 bool "POSIX ACL support"
364 POSIX Access Control Lists (ACLs) support permissions for users and
365 groups beyond the owner/group/world scheme.
367 To learn more about Access Control Lists, visit the POSIX ACLs for
368 Linux website <http://acl.bestbits.at/>.
370 If you don't know what Access Control Lists are, say N.
373 tristate "Minix fs support"
375 Minix is a simple operating system used in many classes about OS's.
376 The minix file system (method to organize files on a hard disk
377 partition or a floppy disk) was the original file system for Linux,
378 but has been superseded by the second extended file system ext2fs.
379 You don't want to use the minix file system on your hard disk
380 because of certain built-in restrictions, but it is sometimes found
381 on older Linux floppy disks. This option will enlarge your kernel
382 by about 28 KB. If unsure, say N.
384 To compile this file system support as a module, choose M here: the
385 module will be called minix. Note that the file system of your root
386 partition (the one containing the directory /) cannot be compiled as
390 tristate "ROM file system support"
392 This is a very small read-only file system mainly intended for
393 initial ram disks of installation disks, but it could be used for
394 other read-only media as well. Read
395 <file:Documentation/filesystems/romfs.txt> for details.
397 To compile this file system support as a module, choose M here: the
398 module will be called romfs. Note that the file system of your
399 root partition (the one containing the directory /) cannot be a
402 If you don't know whether you need it, then you don't need it:
408 If you say Y here, you will be able to set per user limits for disk
409 usage (also called disk quotas). Currently, it works for the
410 ext2, ext3, and reiserfs file system. ext3 also supports journalled
411 quotas for which you don't need to run quotacheck(8) after an unclean
412 shutdown. You need additional software in order to use quota support
413 (you can download sources from
414 <http://www.sf.net/projects/linuxquota/>). For further details, read
415 the Quota mini-HOWTO, available from
416 <http://www.tldp.org/docs.html#howto>, or the documentation provided
417 with the quota tools. Probably the quota support is only useful for
418 multi user systems. If unsure, say N.
421 tristate "Old quota format support"
424 This quota format was (is) used by kernels earlier than 2.4.22. If
425 you have quota working and you don't want to convert to new quota
429 tristate "Quota format v2 support"
432 This quota format allows using quotas with 32-bit UIDs/GIDs. If you
433 need this functionality say Y here. Note that you will need recent
434 quota utilities (>= 3.01) for new quota format with this kernel.
438 depends on XFS_QUOTA || QUOTA
442 tristate "Kernel automounter support"
444 The automounter is a tool to automatically mount remote file systems
445 on demand. This implementation is partially kernel-based to reduce
446 overhead in the already-mounted case; this is unlike the BSD
447 automounter (amd), which is a pure user space daemon.
449 To use the automounter you need the user-space tools from the autofs
450 package; you can find the location in <file:Documentation/Changes>.
451 You also want to answer Y to "NFS file system support", below.
453 If you want to use the newer version of the automounter with more
454 features, say N here and say Y to "Kernel automounter v4 support",
457 To compile this support as a module, choose M here: the module will be
460 If you are not a part of a fairly large, distributed network, you
461 probably do not need an automounter, and can say N here.
464 tristate "Kernel automounter version 4 support (also supports v3)"
466 The automounter is a tool to automatically mount remote file systems
467 on demand. This implementation is partially kernel-based to reduce
468 overhead in the already-mounted case; this is unlike the BSD
469 automounter (amd), which is a pure user space daemon.
471 To use the automounter you need the user-space tools from
472 <ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4/>; you also
473 want to answer Y to "NFS file system support", below.
475 To compile this support as a module, choose M here: the module will be
476 called autofs4. You will need to add "alias autofs autofs4" to your
477 modules configuration file.
479 If you are not a part of a fairly large, distributed network or
480 don't have a laptop which needs to dynamically reconfigure to the
481 local network, you probably do not need an automounter, and can say
484 menu "CD-ROM/DVD Filesystems"
487 tristate "ISO 9660 CDROM file system support"
489 This is the standard file system used on CD-ROMs. It was previously
490 known as "High Sierra File System" and is called "hsfs" on other
491 Unix systems. The so-called Rock-Ridge extensions which allow for
492 long Unix filenames and symbolic links are also supported by this
493 driver. If you have a CD-ROM drive and want to do more with it than
494 just listen to audio CDs and watch its LEDs, say Y (and read
495 <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO,
496 available from <http://www.tldp.org/docs.html#howto>), thereby
497 enlarging your kernel by about 27 KB; otherwise say N.
499 To compile this file system support as a module, choose M here: the
500 module will be called isofs.
503 bool "Microsoft Joliet CDROM extensions"
504 depends on ISO9660_FS
507 Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system
508 which allows for long filenames in unicode format (unicode is the
509 new 16 bit character code, successor to ASCII, which encodes the
510 characters of almost all languages of the world; see
511 <http://www.unicode.org/> for more information). Say Y here if you
512 want to be able to read Joliet CD-ROMs under Linux.
515 bool "Transparent decompression extension"
516 depends on ISO9660_FS
519 This is a Linux-specific extension to RockRidge which lets you store
520 data in compressed form on a CD-ROM and have it transparently
521 decompressed when the CD-ROM is accessed. See
522 <http://www.kernel.org/pub/linux/utils/fs/zisofs/> for the tools
523 necessary to create such a filesystem. Say Y here if you want to be
524 able to read such compressed CD-ROMs.
527 # for fs/nls/Config.in
533 tristate "UDF file system support"
535 This is the new file system used on some CD-ROMs and DVDs. Say Y if
536 you intend to mount DVD discs or CDRW's written in packet mode, or
537 if written to by other UDF utilities, such as DirectCD.
538 Please read <file:Documentation/filesystems/udf.txt>.
540 To compile this file system support as a module, choose M here: the
541 module will be called udf.
548 depends on (UDF_FS=m && NLS) || (UDF_FS=y && NLS=y)
552 menu "DOS/FAT/NT Filesystems"
558 If you want to use one of the FAT-based file systems (the MS-DOS,
559 VFAT (Windows 95) and UMSDOS (used to run Linux on top of an
560 ordinary DOS partition) file systems), then you must say Y or M here
561 to include FAT support. You will then be able to mount partitions or
562 diskettes with FAT-based file systems and transparently access the
563 files on them, i.e. MSDOS files will look and behave just like all
566 This FAT support is not a file system in itself, it only provides
567 the foundation for the other file systems. You will have to say Y or
568 M to at least one of "MSDOS fs support" or "VFAT fs support" in
569 order to make use of it.
571 Another way to read and write MSDOS floppies and hard drive
572 partitions from within Linux (but not transparently) is with the
573 mtools ("man mtools") program suite. You don't need to say Y here in
576 If you need to move large files on floppies between a DOS and a
577 Linux box, say Y here, mount the floppy under Linux with an MSDOS
578 file system and use GNU tar's M option. GNU tar is a program
579 available for Unix and DOS ("man tar" or "info tar").
581 It is now also becoming possible to read and write compressed FAT
582 file systems; read <file:Documentation/filesystems/fat_cvf.txt> for
585 The FAT support will enlarge your kernel by about 37 KB. If unsure,
588 To compile this as a module, choose M here: the module will be called
589 fat. Note that if you compile the FAT support as a module, you
590 cannot compile any of the FAT-based file systems into the kernel
591 -- they will have to be modules as well.
592 The file system of your root partition (the one containing the
593 directory /) cannot be a module, so don't say M here if you intend
594 to use UMSDOS as your root file system.
597 tristate "MSDOS fs support"
600 This allows you to mount MSDOS partitions of your hard drive (unless
601 they are compressed; to access compressed MSDOS partitions under
602 Linux, you can either use the DOS emulator DOSEMU, described in the
603 DOSEMU-HOWTO, available from
604 <http://www.tldp.org/docs.html#howto>, or try dmsdosfs in
605 <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you
606 intend to use dosemu with a non-compressed MSDOS partition, say Y
607 here) and MSDOS floppies. This means that file access becomes
608 transparent, i.e. the MSDOS files look and behave just like all
611 If you want to use UMSDOS, the Unix-like file system on top of a
612 DOS file system, which allows you to run Linux from within a DOS
613 partition without repartitioning, you'll have to say Y or M here.
615 If you have Windows 95 or Windows NT installed on your MSDOS
616 partitions, you should use the VFAT file system (say Y to "VFAT fs
617 support" below), or you will not be able to see the long filenames
618 generated by Windows 95 / Windows NT.
620 This option will enlarge your kernel by about 7 KB. If unsure,
621 answer Y. This will only work if you said Y to "DOS FAT fs support"
622 as well. To compile this as a module, choose M here: the module will
626 tristate "VFAT (Windows-95) fs support"
629 This option provides support for normal Windows file systems with
630 long filenames. That includes non-compressed FAT-based file systems
631 used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
632 programs from the mtools package.
634 You cannot use the VFAT file system for your Linux root partition
635 (the one containing the directory /); use UMSDOS instead if you
636 want to run Linux from within a DOS partition (i.e. say Y to
637 "Unix like fs on top of std MSDOS fs", below).
639 The VFAT support enlarges your kernel by about 10 KB and it only
640 works if you said Y to the "DOS FAT fs support" above. Please read
641 the file <file:Documentation/filesystems/vfat.txt> for details. If
644 To compile this as a module, choose M here: the module will be called
647 config FAT_DEFAULT_CODEPAGE
648 int "Default codepage for FAT"
649 depends on MSDOS_FS || VFAT_FS
652 This option should be set to the codepage of your FAT filesystems.
653 It can be overridden with the 'codepage' mount option.
655 config FAT_DEFAULT_IOCHARSET
656 string "Default iocharset for FAT"
660 Set this to the default I/O character set you'd like FAT to use.
661 It should probably match the character set that most of your
662 FAT filesystems use, and can be overridded with the 'iocharset'
663 mount option for FAT filesystems. Note that UTF8 is *not* a
664 supported charset for FAT filesystems.
667 #dep_tristate ' UMSDOS: Unix-like file system on top of standard MSDOS fs' CONFIG_UMSDOS_FS $CONFIG_MSDOS_FS
668 # UMSDOS is temprory broken
671 Say Y here if you want to run Linux from within an existing DOS
672 partition of your hard drive. The advantage of this is that you can
673 get away without repartitioning your hard drive (which often implies
674 backing everything up and restoring afterwards) and hence you're
675 able to quickly try out Linux or show it to your friends; the
676 disadvantage is that Linux becomes susceptible to DOS viruses and
677 that UMSDOS is somewhat slower than ext2fs. Another use of UMSDOS
678 is to write files with long unix filenames to MSDOS floppies; it
679 also allows Unix-style soft-links and owner/permissions of files on
680 MSDOS floppies. You will need a program called umssync in order to
681 make use of UMSDOS; read
682 <file:Documentation/filesystems/umsdos.txt>.
684 To get utilities for initializing/checking UMSDOS file system, or
685 latest patches and/or information, visit the UMSDOS home page at
686 <http://www.voyager.hr/~mnalis/umsdos/>.
688 This option enlarges your kernel by about 28 KB and it only works if
689 you said Y to both "DOS FAT fs support" and "MSDOS fs support"
690 above. To compile this as a module, choose M here: the module will be
691 called umsdos. Note that the file system of your root partition
692 (the one containing the directory /) cannot be a module, so saying M
693 could be dangerous. If unsure, say N.
696 tristate "NTFS file system support"
699 NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003.
701 Saying Y or M here enables read support. There is partial, but
702 safe, write support available. For write support you must also
703 say Y to "NTFS write support" below.
705 There are also a number of user-space tools available, called
706 ntfsprogs. These include ntfsundelete and ntfsresize, that work
707 without NTFS support enabled in the kernel.
709 This is a rewrite from scratch of Linux NTFS support and replaced
710 the old NTFS code starting with Linux 2.5.11. A backport to
711 the Linux 2.4 kernel series is separately available as a patch
712 from the project web site.
714 For more information see <file:Documentation/filesystems/ntfs.txt>
715 and <http://linux-ntfs.sourceforge.net/>.
717 To compile this file system support as a module, choose M here: the
718 module will be called ntfs.
720 If you are not using Windows NT, 2000, XP or 2003 in addition to
721 Linux on your computer it is safe to say N.
724 bool "NTFS debugging support"
727 If you are experiencing any problems with the NTFS file system, say
728 Y here. This will result in additional consistency checks to be
729 performed by the driver as well as additional debugging messages to
730 be written to the system log. Note that debugging messages are
731 disabled by default. To enable them, supply the option debug_msgs=1
732 at the kernel command line when booting the kernel or as an option
733 to insmod when loading the ntfs module. Once the driver is active,
734 you can enable debugging messages by doing (as root):
735 echo 1 > /proc/sys/fs/ntfs-debug
736 Replacing the "1" with "0" would disable debug messages.
738 If you leave debugging messages disabled, this results in little
739 overhead, but enabling debug messages results in very significant
740 slowdown of the system.
742 When reporting bugs, please try to have available a full dump of
743 debugging messages while the misbehaviour was occurring.
746 bool "NTFS write support"
749 This enables the partial, but safe, write support in the NTFS driver.
751 The only supported operation is overwriting existing files, without
752 changing the file length. No file or directory creation, deletion or
753 renaming is possible. Note only non-resident files can be written to
754 so you may find that some very small files (<500 bytes or so) cannot
757 While we cannot guarantee that it will not damage any data, we have
758 so far not received a single report where the driver would have
759 damaged someones data so we assume it is perfectly safe to use.
761 Note: While write support is safe in this version (a rewrite from
762 scratch of the NTFS support), it should be noted that the old NTFS
763 write support, included in Linux 2.5.10 and before (since 1997),
766 This is currently useful with TopologiLinux. TopologiLinux is run
767 on top of any DOS/Microsoft Windows system without partitioning your
768 hard disk. Unlike other Linux distributions TopologiLinux does not
769 need its own partition. For more information see
770 <http://topologi-linux.sourceforge.net/>
772 It is perfectly safe to say N here.
776 menu "Pseudo filesystems"
779 bool "/proc file system support"
781 This is a virtual file system providing information about the status
782 of the system. "Virtual" means that it doesn't take up any space on
783 your hard disk: the files are created on the fly by the kernel when
784 you try to access them. Also, you cannot read the files with older
785 version of the program less: you need to use more or cat.
787 It's totally cool; for example, "cat /proc/interrupts" gives
788 information about what the different IRQs are used for at the moment
789 (there is a small number of Interrupt ReQuest lines in your computer
790 that are used by the attached devices to gain the CPU's attention --
791 often a source of trouble if two devices are mistakenly configured
792 to use the same IRQ). The program procinfo to display some
793 information about your system gathered from the /proc file system.
795 Before you can use the /proc file system, it has to be mounted,
796 meaning it has to be given a location in the directory hierarchy.
797 That location should be /proc. A command such as "mount -t proc proc
798 /proc" or the equivalent line in /etc/fstab does the job.
800 The /proc file system is explained in the file
801 <file:Documentation/filesystems/proc.txt> and on the proc(5) manpage
804 This option will enlarge your kernel by about 67 KB. Several
805 programs depend on this, so everyone should say Y here.
812 bool "sysfs file system support" if EMBEDDED
815 The sysfs filesystem is a virtual filesystem that the kernel uses to
816 export internal kernel objects, their attributes, and their
817 relationships to one another.
819 Users can use sysfs to ascertain useful information about the running
820 kernel, such as the devices the kernel has discovered on each bus and
821 which driver each is bound to. sysfs can also be used to tune devices
822 and other kernel subsystems.
824 Some system agents rely on the information in sysfs to operate.
825 /sbin/hotplug uses device and object attributes in sysfs to assist in
826 delegating policy decisions, like persistantly naming devices.
828 sysfs is currently used by the block subsystem to mount the root
829 partition. If sysfs is disabled you must specify the boot device on
830 the kernel boot command line via its major and minor numbers. For
831 example, "root=03:01" for /dev/hda1.
833 Designers of embedded systems may wish to say N here to conserve space.
836 bool "/dev file system support (OBSOLETE)"
837 depends on EXPERIMENTAL
839 This is support for devfs, a virtual file system (like /proc) which
840 provides the file system interface to device drivers, normally found
841 in /dev. Devfs does not depend on major and minor number
842 allocations. Device drivers register entries in /dev which then
843 appear automatically, which means that the system administrator does
844 not have to create character and block special device files in the
845 /dev directory using the mknod command (or MAKEDEV script) anymore.
847 This is work in progress. If you want to use this, you *must* read
848 the material in <file:Documentation/filesystems/devfs/>, especially
849 the file README there.
851 Note that devfs no longer manages /dev/pts! If you are using UNIX98
852 ptys, you will also need to mount the /dev/pts filesystem (devpts).
854 Note that devfs has been obsoleted by udev,
855 <http://www.kernel.org/pub/linux/utils/kernel/hotplug/>.
856 It has been stripped down to a bare minimum and is only provided for
857 legacy installations that use its naming scheme which is
858 unfortunately different from the names normal Linux installations
864 bool "Automatically mount at boot"
867 This option appears if you have CONFIG_DEVFS_FS enabled. Setting
868 this to 'Y' will make the kernel automatically mount devfs onto /dev
869 when the system is booted, before the init thread is started.
870 You can override this with the "devfs=nomount" boot option.
878 If you say Y here, then the /dev file system code will generate
879 debugging messages. See the file
880 <file:Documentation/filesystems/devfs/boot-options> for more
885 config DEVPTS_FS_XATTR
886 bool "/dev/pts Extended Attributes"
887 depends on UNIX98_PTYS
889 Extended attributes are name:value pairs associated with inodes by
890 the kernel or by users (see the attr(5) manual page, or visit
891 <http://acl.bestbits.at/> for details).
895 config DEVPTS_FS_SECURITY
896 bool "/dev/pts Security Labels"
897 depends on DEVPTS_FS_XATTR
899 Security labels support alternative access control models
900 implemented by security modules like SELinux. This option
901 enables an extended attribute handler for file security
902 labels in the /dev/pts filesystem.
904 If you are not using a security module that requires using
905 extended attributes for file security labels, say N.
908 bool "Virtual memory file system support (former shm fs)"
910 Tmpfs is a file system which keeps all files in virtual memory.
912 Everything in tmpfs is temporary in the sense that no files will be
913 created on your hard drive. The files live in memory and swap
914 space. If you unmount a tmpfs instance, everything stored therein is
917 See <file:Documentation/filesystems/tmpfs.txt> for details.
920 bool "HugeTLB file system support"
921 depends X86 || IA64 || PPC64 || SPARC64 || SUPERH || X86_64 || BROKEN
930 Ramfs is a file system which keeps all files in RAM. It allows
931 read and write access.
933 It is more of an programming example than a useable file system. If
934 you need a file system which lives in RAM with limit checking use
937 To compile this as a module, choose M here: the module will be called
942 menu "Miscellaneous filesystems"
945 tristate "ADFS file system support (EXPERIMENTAL)"
946 depends on EXPERIMENTAL
948 The Acorn Disc Filing System is the standard file system of the
949 RiscOS operating system which runs on Acorn's ARM-based Risc PC
950 systems and the Acorn Archimedes range of machines. If you say Y
951 here, Linux will be able to read from ADFS partitions on hard drives
952 and from ADFS-formatted floppy discs. If you also want to be able to
953 write to those devices, say Y to "ADFS write support" below.
955 The ADFS partition should be the first partition (i.e.,
956 /dev/[hs]d?1) on each of your drives. Please read the file
957 <file:Documentation/filesystems/adfs.txt> for further details.
959 To compile this code as a module, choose M here: the module will be
965 bool "ADFS write support (DANGEROUS)"
968 If you say Y here, you will be able to write to ADFS partitions on
969 hard drives and ADFS-formatted floppy disks. This is experimental
970 codes, so if you're unsure, say N.
973 tristate "Amiga FFS file system support (EXPERIMENTAL)"
974 depends on EXPERIMENTAL
976 The Fast File System (FFS) is the common file system used on hard
977 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
978 if you want to be able to read and write files from and to an Amiga
979 FFS partition on your hard drive. Amiga floppies however cannot be
980 read with this driver due to an incompatibility of the floppy
981 controller used in an Amiga and the standard floppy controller in
982 PCs and workstations. Read <file:Documentation/filesystems/affs.txt>
983 and <file:fs/affs/Changes>.
985 With this driver you can also mount disk files used by Bernd
986 Schmidt's Un*X Amiga Emulator
987 (<http://www.freiburg.linux.de/~uae/>).
988 If you want to do this, you will also need to say Y or M to "Loop
989 device support", above.
991 To compile this file system support as a module, choose M here: the
992 module will be called affs. If unsure, say N.
995 tristate "Apple Macintosh file system support (EXPERIMENTAL)"
996 depends on EXPERIMENTAL
998 If you say Y here, you will be able to mount Macintosh-formatted
999 floppy disks and hard drive partitions with full read-write access.
1000 Please read <file:fs/hfs/HFS.txt> to learn about the available mount
1003 To compile this file system support as a module, choose M here: the
1004 module will be called hfs.
1007 tristate "Apple Extended HFS file system support"
1010 If you say Y here, you will be able to mount extended format
1011 Macintosh-formatted hard drive partitions with full read-write access.
1013 This file system is often called HFS+ and was introduced with
1014 MacOS 8. It includes all Mac specific filesystem data such as
1015 data forks and creator codes, but it also has several UNIX
1016 style features such as file ownership and permissions.
1019 tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)"
1020 depends on EXPERIMENTAL
1023 The BeOS File System (BeFS) is the native file system of Be, Inc's
1024 BeOS. Notable features include support for arbitrary attributes
1025 on files and directories, and database-like indices on selected
1026 attributes. (Also note that this driver doesn't make those features
1027 available at this time). It is a 64 bit filesystem, so it supports
1028 extreemly large volumes and files.
1030 If you use this filesystem, you should also say Y to at least one
1031 of the NLS (native language support) options below.
1033 If you don't know what this is about, say N.
1035 To compile this as a module, choose M here: the module will be
1042 If you say Y here, you can use the 'debug' mount option to enable
1043 debugging output from the driver.
1046 tristate "BFS file system support (EXPERIMENTAL)"
1047 depends on EXPERIMENTAL
1049 Boot File System (BFS) is a file system used under SCO UnixWare to
1050 allow the bootloader access to the kernel image and other important
1051 files during the boot process. It is usually mounted under /stand
1052 and corresponds to the slice marked as "STAND" in the UnixWare
1053 partition. You should say Y if you want to read or write the files
1054 on your /stand slice from within Linux. You then also need to say Y
1055 to "UnixWare slices support", below. More information about the BFS
1056 file system is contained in the file
1057 <file:Documentation/filesystems/bfs.txt>.
1059 If you don't know what this is about, say N.
1061 To compile this as a module, choose M here: the module will be called
1062 bfs. Note that the file system of your root partition (the one
1063 containing the directory /) cannot be compiled as a module.
1068 tristate "EFS file system support (read only) (EXPERIMENTAL)"
1069 depends on EXPERIMENTAL
1071 EFS is an older file system used for non-ISO9660 CD-ROMs and hard
1072 disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
1073 uses the XFS file system for hard disk partitions however).
1075 This implementation only offers read-only access. If you don't know
1076 what all this is about, it's safe to say N. For more information
1077 about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
1079 To compile the EFS file system support as a module, choose M here: the
1080 module will be called efs.
1083 tristate "Journalling Flash File System (JFFS) support"
1086 JFFS is the Journaling Flash File System developed by Axis
1087 Communications in Sweden, aimed at providing a crash/powerdown-safe
1088 file system for disk-less embedded devices. Further information is
1089 available at (<http://developer.axis.com/software/jffs/>).
1091 config JFFS_FS_VERBOSE
1092 int "JFFS debugging verbosity (0 = quiet, 3 = noisy)"
1096 Determines the verbosity level of the JFFS debugging messages.
1099 bool "JFFS stats available in /proc filesystem"
1100 depends on JFFS_FS && PROC_FS
1102 Enabling this option will cause statistics from mounted JFFS file systems
1103 to be made available to the user in the /proc/fs/jffs/ directory.
1106 tristate "Journalling Flash File System v2 (JFFS2) support"
1110 JFFS2 is the second generation of the Journalling Flash File System
1111 for use on diskless embedded devices. It provides improved wear
1112 levelling, compression and support for hard links. You cannot use
1113 this on normal block devices, only on 'MTD' devices.
1115 Further information on the design and implementation of JFFS2 is
1116 available at <http://sources.redhat.com/jffs2/>.
1118 config JFFS2_FS_DEBUG
1119 int "JFFS2 debugging verbosity (0 = quiet, 2 = noisy)"
1123 This controls the amount of debugging messages produced by the JFFS2
1124 code. Set it to zero for use in production systems. For evaluation,
1125 testing and debugging, it's advisable to set it to one. This will
1126 enable a few assertions and will print debugging messages at the
1127 KERN_DEBUG loglevel, where they won't normally be visible. Level 2
1128 is unlikely to be useful - it enables extra debugging in certain
1129 areas which at one point needed debugging, but when the bugs were
1130 located and fixed, the detailed messages were relegated to level 2.
1132 If reporting bugs, please try to have available a full dump of the
1133 messages at debug level 1 while the misbehaviour was occurring.
1135 config JFFS2_FS_NAND
1136 bool "JFFS2 support for NAND flash"
1140 This enables the support for NAND flash in JFFS2. NAND is a newer
1141 type of flash chip design than the traditional NOR flash, with
1142 higher density but a handful of characteristics which make it more
1143 interesting for the file system to use.
1145 Say 'N' unless you have NAND flash.
1147 config JFFS2_COMPRESSION_OPTIONS
1148 bool "Advanced compression options for JFFS2"
1152 Enabling this option allows you to explicitly choose which
1153 compression modules, if any, are enabled in JFFS2. Removing
1154 compressors and mean you cannot read existing file systems,
1155 and enabling experimental compressors can mean that you
1156 write a file system which cannot be read by a standard kernel.
1158 If unsure, you should _definitely_ say 'N'.
1161 bool "JFFS2 ZLIB compression support" if JFFS2_COMPRESSION_OPTIONS
1167 Zlib is designed to be a free, general-purpose, legally unencumbered,
1168 lossless data-compression library for use on virtually any computer
1169 hardware and operating system. See http://www.gzip.org/zlib/ for
1170 further information.
1175 bool "JFFS2 RTIME compression support" if JFFS2_COMPRESSION_OPTIONS
1179 Rtime does manage to recompress already-compressed data. Say 'Y' if unsure.
1182 bool "JFFS2 RUBIN compression support" if JFFS2_COMPRESSION_OPTIONS
1186 RUBINMIPS and DYNRUBIN compressors. Say 'N' if unsure.
1189 prompt "JFFS2 default compression mode" if JFFS2_COMPRESSION_OPTIONS
1190 default JFFS2_CMODE_PRIORITY
1193 You can set here the default compression mode of JFFS2 from
1194 the avaiable compression modes. Don't touch if unsure.
1196 config JFFS2_CMODE_NONE
1197 bool "no compression"
1199 Uses no compression.
1201 config JFFS2_CMODE_PRIORITY
1204 Tries the compressors in a predefinied order and chooses the first
1207 config JFFS2_CMODE_SIZE
1208 bool "size (EXPERIMENTAL)"
1210 Tries all compressors and chooses the one which has the smallest
1216 tristate "Compressed ROM file system support"
1219 Saying Y here includes support for CramFs (Compressed ROM File
1220 System). CramFs is designed to be a simple, small, and compressed
1221 file system for ROM based embedded systems. CramFs is read-only,
1222 limited to 256MB file systems (with 16MB files), and doesn't support
1223 16/32 bits uid/gid, hard links and timestamps.
1225 See <file:Documentation/filesystems/cramfs.txt> and
1226 <file:fs/cramfs/README> for further information.
1228 To compile this as a module, choose M here: the module will be called
1229 cramfs. Note that the root file system (the one containing the
1230 directory /) cannot be compiled as a module.
1235 tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
1237 FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
1238 file system format. VERITAS VxFS(TM) is the standard file system
1239 of SCO UnixWare (and possibly others) and optionally available
1240 for Sunsoft Solaris, HP-UX and many other operating systems.
1241 Currently only readonly access is supported.
1243 NOTE: the file system type as used by mount(1), mount(2) and
1244 fstab(5) is 'vxfs' as it describes the file system format, not
1247 To compile this as a module, choose M here: the module will be
1248 called freevxfs. If unsure, say N.
1252 tristate "OS/2 HPFS file system support"
1254 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
1255 is the file system used for organizing files on OS/2 hard disk
1256 partitions. Say Y if you want to be able to read files from and
1257 write files to an OS/2 HPFS partition on your hard drive. OS/2
1258 floppies however are in regular MSDOS format, so you don't need this
1259 option in order to be able to read them. Read
1260 <file:Documentation/filesystems/hpfs.txt>.
1262 To compile this file system support as a module, choose M here: the
1263 module will be called hpfs. If unsure, say N.
1268 tristate "QNX4 file system support (read only)"
1270 This is the file system used by the real-time operating systems
1271 QNX 4 and QNX 6 (the latter is also called QNX RTP).
1272 Further information is available at <http://www.qnx.com/>.
1273 Say Y if you intend to mount QNX hard disks or floppies.
1274 Unless you say Y to "QNX4FS read-write support" below, you will
1275 only be able to read these file systems.
1277 To compile this file system support as a module, choose M here: the
1278 module will be called qnx4.
1280 If you don't know whether you need it, then you don't need it:
1284 bool "QNX4FS write support (DANGEROUS)"
1285 depends on QNX4FS_FS && EXPERIMENTAL
1287 Say Y if you want to test write support for QNX4 file systems.
1289 It's currently broken, so for now:
1295 tristate "System V/Xenix/V7/Coherent file system support"
1297 SCO, Xenix and Coherent are commercial Unix systems for Intel
1298 machines, and Version 7 was used on the DEC PDP-11. Saying Y
1299 here would allow you to read from their floppies and hard disk
1302 If you have floppies or hard disk partitions like that, it is likely
1303 that they contain binaries from those other Unix systems; in order
1304 to run these binaries, you will want to install linux-abi which is a
1305 a set of kernel modules that lets you run SCO, Xenix, Wyse,
1306 UnixWare, Dell Unix and System V programs under Linux. It is
1307 available via FTP (user: ftp) from
1308 <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
1309 NOTE: that will work only for binaries from Intel-based systems;
1310 PDP ones will have to wait until somebody ports Linux to -11 ;-)
1312 If you only intend to mount files from some other Unix over the
1313 network using NFS, you don't need the System V file system support
1314 (but you need NFS file system support obviously).
1316 Note that this option is generally not needed for floppies, since a
1317 good portable way to transport files and directories between unixes
1318 (and even other operating systems) is given by the tar program ("man
1319 tar" or preferably "info tar"). Note also that this option has
1320 nothing whatsoever to do with the option "System V IPC". Read about
1321 the System V file system in
1322 <file:Documentation/filesystems/sysv-fs.txt>.
1323 Saying Y here will enlarge your kernel by about 27 KB.
1325 To compile this as a module, choose M here: the module will be called
1328 If you haven't heard about all of this before, it's safe to say N.
1333 tristate "UFS file system support (read only)"
1335 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
1336 OpenBSD and NeXTstep) use a file system called UFS. Some System V
1337 Unixes can create and mount hard disk partitions and diskettes using
1338 this file system as well. Saying Y here will allow you to read from
1339 these partitions; if you also want to write to them, say Y to the
1340 experimental "UFS file system write support", below. Please read the
1341 file <file:Documentation/filesystems/ufs.txt> for more information.
1343 The recently released UFS2 variant (used in FreeBSD 5.x) is
1344 READ-ONLY supported.
1346 If you only intend to mount files from some other Unix over the
1347 network using NFS, you don't need the UFS file system support (but
1348 you need NFS file system support obviously).
1350 Note that this option is generally not needed for floppies, since a
1351 good portable way to transport files and directories between unixes
1352 (and even other operating systems) is given by the tar program ("man
1353 tar" or preferably "info tar").
1355 When accessing NeXTstep files, you may need to convert them from the
1356 NeXT character set to the Latin1 character set; use the program
1357 recode ("info recode") for this purpose.
1359 To compile the UFS file system support as a module, choose M here: the
1360 module will be called ufs.
1362 If you haven't heard about all of this before, it's safe to say N.
1365 bool "UFS file system write support (DANGEROUS)"
1366 depends on UFS_FS && EXPERIMENTAL
1368 Say Y here if you want to try writing to UFS partitions. This is
1369 experimental, so you should back up your UFS partitions beforehand.
1373 menu "Network File Systems"
1377 tristate "NFS file system support"
1382 If you are connected to some other (usually local) Unix computer
1383 (using SLIP, PLIP, PPP or Ethernet) and want to mount files residing
1384 on that computer (the NFS server) using the Network File Sharing
1385 protocol, say Y. "Mounting files" means that the client can access
1386 the files with usual UNIX commands as if they were sitting on the
1387 client's hard disk. For this to work, the server must run the
1388 programs nfsd and mountd (but does not need to have NFS file system
1389 support enabled in its kernel). NFS is explained in the Network
1390 Administrator's Guide, available from
1391 <http://www.tldp.org/docs.html#guide>, on its man page: "man
1392 nfs", and in the NFS-HOWTO.
1394 A superior but less widely used alternative to NFS is provided by
1395 the Coda file system; see "Coda file system support" below.
1397 If you say Y here, you should have said Y to TCP/IP networking also.
1398 This option would enlarge your kernel by about 27 KB.
1400 To compile this file system support as a module, choose M here: the
1401 module will be called nfs.
1403 If you are configuring a diskless machine which will mount its root
1404 file system over NFS at boot time, say Y here and to "Kernel
1405 level IP autoconfiguration" above and to "Root file system on NFS"
1406 below. You cannot compile this driver as a module in this case.
1407 There are two packages designed for booting diskless machines over
1408 the net: netboot, available from
1409 <http://ftp1.sourceforge.net/netboot/>, and Etherboot,
1410 available from <http://ftp1.sourceforge.net/etherboot/>.
1412 If you don't know what all this is about, say N.
1415 bool "Provide NFSv3 client support"
1418 Say Y here if you want your NFS client to be able to speak the newer
1419 version 3 of the NFS protocol.
1424 bool "Provide NFSv4 client support (EXPERIMENTAL)"
1425 depends on NFS_FS && EXPERIMENTAL
1426 select RPCSEC_GSS_KRB5
1428 Say Y here if you want your NFS client to be able to speak the newer
1429 version 4 of the NFS protocol.
1431 Note: Requires auxiliary userspace daemons which may be found on
1432 http://www.citi.umich.edu/projects/nfsv4/
1437 bool "Allow direct I/O on NFS files (EXPERIMENTAL)"
1438 depends on NFS_FS && EXPERIMENTAL
1440 This option enables applications to perform uncached I/O on files
1441 in NFS file systems using the O_DIRECT open() flag. When O_DIRECT
1442 is set for a file, its data is not cached in the system's page
1443 cache. Data is moved to and from user-level application buffers
1444 directly. Unlike local disk-based file systems, NFS O_DIRECT has
1445 no alignment restrictions.
1447 Unless your program is designed to use O_DIRECT properly, you are
1448 much better off allowing the NFS client to manage data caching for
1449 you. Misusing O_DIRECT can cause poor server performance or network
1450 storms. This kernel build option defaults OFF to avoid exposing
1451 system administrators unwittingly to a potentially hazardous
1454 For more details on NFS O_DIRECT, see fs/nfs/direct.c.
1456 If unsure, say N. This reduces the size of the NFS client, and
1457 causes open() to return EINVAL if a file residing in NFS is
1458 opened with the O_DIRECT flag.
1461 tristate "NFS server support"
1466 If you want your Linux box to act as an NFS *server*, so that other
1467 computers on your local network which support NFS can access certain
1468 directories on your box transparently, you have two options: you can
1469 use the self-contained user space program nfsd, in which case you
1470 should say N here, or you can say Y and use the kernel based NFS
1471 server. The advantage of the kernel based solution is that it is
1474 In either case, you will need support software; the respective
1475 locations are given in the file <file:Documentation/Changes> in the
1478 If you say Y here, you will get support for version 2 of the NFS
1479 protocol (NFSv2). If you also want NFSv3, say Y to the next question
1482 Please read the NFS-HOWTO, available from
1483 <http://www.tldp.org/docs.html#howto>.
1485 To compile the NFS server support as a module, choose M here: the
1486 module will be called nfsd. If unsure, say N.
1489 bool "Provide NFSv3 server support"
1492 If you would like to include the NFSv3 server as well as the NFSv2
1493 server, say Y here. If unsure, say Y.
1496 bool "Provide NFSv4 server support (EXPERIMENTAL)"
1497 depends on NFSD_V3 && EXPERIMENTAL
1499 If you would like to include the NFSv4 server as well as the NFSv2
1500 and NFSv3 servers, say Y here. This feature is experimental, and
1501 should only be used if you are interested in helping to test NFSv4.
1505 bool "Provide NFS server over TCP support"
1509 If you want your NFS server to support TCP connections, say Y here.
1510 TCP connections usually perform better than the default UDP when
1511 the network is lossy or congested. If unsure, say Y.
1514 bool "Root file system on NFS"
1515 depends on NFS_FS=y && IP_PNP
1517 If you want your Linux box to mount its whole root file system (the
1518 one containing the directory /) from some other computer over the
1519 net via NFS (presumably because your box doesn't have a hard disk),
1520 say Y. Read <file:Documentation/nfsroot.txt> for details. It is
1521 likely that in this case, you also want to say Y to "Kernel level IP
1522 autoconfiguration" so that your box can discover its network address
1525 Most people say N here.
1532 depends on NFSD_V3 || NFS_V3
1545 config RPCSEC_GSS_KRB5
1546 tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
1547 depends on SUNRPC && EXPERIMENTAL
1553 Provides for secure RPC calls by means of a gss-api
1554 mechanism based on Kerberos V5. This is required for
1557 Note: Requires an auxiliary userspace daemon which may be found on
1558 http://www.citi.umich.edu/projects/nfsv4/
1563 tristate "SMB file system support (to mount Windows shares etc.)"
1567 SMB (Server Message Block) is the protocol Windows for Workgroups
1568 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
1569 files and printers over local networks. Saying Y here allows you to
1570 mount their file systems (often called "shares" in this context) and
1571 access them just like any other Unix directory. Currently, this
1572 works only if the Windows machines use TCP/IP as the underlying
1573 transport protocol, and not NetBEUI. For details, read
1574 <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
1575 available from <http://www.tldp.org/docs.html#howto>.
1577 Note: if you just want your box to act as an SMB *server* and make
1578 files and printing services available to Windows clients (which need
1579 to have a TCP/IP stack), you don't need to say Y here; you can use
1580 the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
1583 General information about how to connect Linux, Windows machines and
1584 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1586 To compile the SMB support as a module, choose M here: the module will
1587 be called smbfs. Most people say N, however.
1589 config SMB_NLS_DEFAULT
1590 bool "Use a default NLS"
1593 Enabling this will make smbfs use nls translations by default. You
1594 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
1595 settings and you need to give the default nls for the SMB server as
1596 CONFIG_SMB_NLS_REMOTE.
1598 The nls settings can be changed at mount time, if your smbmount
1599 supports that, using the codepage and iocharset parameters.
1601 smbmount from samba 2.2.0 or later supports this.
1603 config SMB_NLS_REMOTE
1604 string "Default Remote NLS Option"
1605 depends on SMB_NLS_DEFAULT
1608 This setting allows you to specify a default value for which
1609 codepage the server uses. If this field is left blank no
1610 translations will be done by default. The local codepage/charset
1611 default to CONFIG_NLS_DEFAULT.
1613 The nls settings can be changed at mount time, if your smbmount
1614 supports that, using the codepage and iocharset parameters.
1616 smbmount from samba 2.2.0 or later supports this.
1619 tristate "CIFS support (advanced network filesystem for Samba, Window and other CIFS compliant servers)"
1623 This is the client VFS module for the Common Internet File System
1624 (CIFS) protocol which is the successor to the Server Message Block
1625 (SMB) protocol, the native file sharing mechanism for most early
1626 PC operating systems. The CIFS protocol is fully supported by
1627 file servers such as Windows 2000 (including Windows 2003, NT 4
1628 and Windows XP) as well by Samba (which provides excellent CIFS
1629 server support for Linux and many other operating systems). Currently
1630 you must use the smbfs client filesystem to access older SMB servers
1631 such as Windows 9x and OS/2.
1633 The intent of the cifs module is to provide an advanced
1634 network file system client for mounting to CIFS compliant servers,
1635 including support for dfs (hierarchical name space), secure per-user
1636 session establishment, safe distributed caching (oplock), optional
1637 packet signing, Unicode and other internationalization improvements,
1638 and optional Winbind (nsswitch) integration. You do not need to enable
1639 cifs if running only a (Samba) server. It is possible to enable both
1640 smbfs and cifs (e.g. if you are using CIFS for accessing Windows 2003
1641 and Samba 3 servers, and smbfs for accessing old servers). If you need
1642 to mount to Samba or Windows 2003 servers from this machine, say Y.
1645 bool "CIFS statistics"
1648 Enabling this option will cause statistics for each server share
1649 mounted by the cifs client to be displayed in /proc/fs/cifs/Stats
1652 bool "CIFS extended attributes (EXPERIMENTAL)"
1655 Extended attributes are name:value pairs associated with inodes by
1656 the kernel or by users (see the attr(5) manual page, or visit
1657 <http://acl.bestbits.at/> for details). CIFS maps the name of
1658 extended attributes beginning with the user namespace prefix
1659 to SMB/CIFS EAs. EAs are stored on Windows servers without the
1660 user namespace prefix, but their names are seen by Linux cifs clients
1661 prefaced by the user namespace prefix. The system namespace
1662 (used by some filesystems to store ACLs) is not supported at
1668 bool "CIFS POSIX Extensions (EXPERIMENTAL)"
1671 Enabling this option will cause the cifs client to attempt to
1672 negotiate a newer dialect with servers, such as Samba 3.0.5
1673 or later, that optionally can handle more POSIX like (rather
1674 than Windows like) file behavior. If unsure, say N.
1677 tristate "NCP file system support (to mount NetWare volumes)"
1678 depends on IPX!=n || INET
1680 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
1681 used by Novell NetWare clients to talk to file servers. It is to
1682 IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
1683 to mount NetWare file server volumes and to access them just like
1684 any other Unix directory. For details, please read the file
1685 <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
1686 the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
1688 You do not have to say Y here if you want your Linux box to act as a
1689 file *server* for Novell NetWare clients.
1691 General information about how to connect Linux, Windows machines and
1692 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1694 To compile this as a module, choose M here: the module will be called
1695 ncpfs. Say N unless you are connected to a Novell network.
1697 source "fs/ncpfs/Kconfig"
1700 tristate "Coda file system support (advanced network fs)"
1703 Coda is an advanced network file system, similar to NFS in that it
1704 enables you to mount file systems of a remote server and access them
1705 with regular Unix commands as if they were sitting on your hard
1706 disk. Coda has several advantages over NFS: support for
1707 disconnected operation (e.g. for laptops), read/write server
1708 replication, security model for authentication and encryption,
1709 persistent client caches and write back caching.
1711 If you say Y here, your Linux box will be able to act as a Coda
1712 *client*. You will need user level code as well, both for the
1713 client and server. Servers are currently user level, i.e. they need
1714 no kernel support. Please read
1715 <file:Documentation/filesystems/coda.txt> and check out the Coda
1716 home page <http://www.coda.cs.cmu.edu/>.
1718 To compile the coda client support as a module, choose M here: the
1719 module will be called coda.
1721 config CODA_FS_OLD_API
1722 bool "Use 96-bit Coda file identifiers"
1725 A new kernel-userspace API had to be introduced for Coda v6.0
1726 to support larger 128-bit file identifiers as needed by the
1727 new realms implementation.
1729 However this new API is not backward compatible with older
1730 clients. If you really need to run the old Coda userspace
1731 cache manager then say Y.
1733 For most cases you probably want to say N.
1736 # for fs/nls/Config.in
1737 tristate "Andrew File System support (AFS) (Experimental)"
1738 depends on INET && EXPERIMENTAL
1741 If you say Y here, you will get an experimental Andrew File System
1742 driver. It currently only supports unsecured read-only AFS access.
1744 See Documentation/filesystems/afs.txt for more intormation.
1753 menu "Partition Types"
1755 source "fs/partitions/Kconfig"
1759 source "fs/nls/Kconfig"