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"
250 This is a port of IBM's Journaled Filesystem . More information is
251 available in the file Documentation/filesystems/jfs.txt.
253 If you do not intend to use the JFS filesystem, say N.
256 bool "JFS POSIX Access Control Lists"
259 Posix Access Control Lists (ACLs) support permissions for users and
260 groups beyond the owner/group/world scheme.
262 To learn more about Access Control Lists, visit the Posix ACLs for
263 Linux website <http://acl.bestbits.at/>.
265 If you don't know what Access Control Lists are, say N
271 If you are experiencing any problems with the JFS filesystem, say
272 Y here. This will result in additional debugging messages to be
273 written to the system log. Under normal circumstances, this
274 results in very little overhead.
276 config JFS_STATISTICS
277 bool "JFS statistics"
280 Enabling this option will cause statistics from the JFS file system
281 to be made available to the user in the /proc/fs/jfs/ directory.
284 # Posix ACL utility routines (for now, only ext2/ext3/jfs)
286 # NOTE: you can implement Posix ACLs without these helpers (XFS does).
287 # Never use this symbol for ifdefs.
290 depends on EXT2_FS_POSIX_ACL || EXT3_FS_POSIX_ACL || JFS_POSIX_ACL
294 tristate "XFS filesystem support"
296 XFS is a high performance journaling filesystem which originated
297 on the SGI IRIX platform. It is completely multi-threaded, can
298 support large files and large filesystems, extended attributes,
299 variable block sizes, is extent based, and makes extensive use of
300 Btrees (directories, extents, free space) to aid both performance
303 Refer to the documentation at <http://oss.sgi.com/projects/xfs/>
304 for complete details. This implementation is on-disk compatible
305 with the IRIX version of XFS.
307 To compile this file system support as a module, choose M here: the
308 module will be called xfs. Be aware, however, that if the file
309 system of your root partition is compiled as a module, you'll need
310 to use an initial ramdisk (initrd) to boot.
313 bool "Realtime support (EXPERIMENTAL)"
314 depends on XFS_FS && EXPERIMENTAL
316 If you say Y here you will be able to mount and use XFS filesystems
317 which contain a realtime subvolume. The realtime subvolume is a
318 separate area of disk space where only file data is stored. The
319 realtime subvolume is designed to provide very deterministic
320 data rates suitable for media streaming applications.
322 See the xfs man page in section 5 for a bit more information.
324 This feature is unsupported at this time, is not yet fully
325 functional, and may cause serious problems.
333 If you say Y here, you will be able to set limits for disk usage on
334 a per user and/or a per group basis under XFS. XFS considers quota
335 information as filesystem metadata and uses journaling to provide a
336 higher level guarantee of consistency. The on-disk data format for
337 quota is also compatible with the IRIX version of XFS, allowing a
338 filesystem to be migrated between Linux and IRIX without any need
341 If unsure, say N. More comprehensive documentation can be found in
342 README.quota in the xfsprogs package. XFS quota can be used either
343 with or without the generic quota support enabled (CONFIG_QUOTA) -
344 they are completely independent subsystems.
350 Posix Access Control Lists (ACLs) support permissions for users and
351 groups beyond the owner/group/world scheme.
353 To learn more about Access Control Lists, visit the Posix ACLs for
354 Linux website <http://acl.bestbits.at/>.
356 If you don't know what Access Control Lists are, say N
359 tristate "Minix fs support"
361 Minix is a simple operating system used in many classes about OS's.
362 The minix file system (method to organize files on a hard disk
363 partition or a floppy disk) was the original file system for Linux,
364 but has been superseded by the second extended file system ext2fs.
365 You don't want to use the minix file system on your hard disk
366 because of certain built-in restrictions, but it is sometimes found
367 on older Linux floppy disks. This option will enlarge your kernel
368 by about 28 KB. If unsure, say N.
370 To compile this file system support as a module, choose M here: the
371 module will be called minix. Note that the file system of your root
372 partition (the one containing the directory /) cannot be compiled as
376 tristate "ROM file system support"
378 This is a very small read-only file system mainly intended for
379 initial ram disks of installation disks, but it could be used for
380 other read-only media as well. Read
381 <file:Documentation/filesystems/romfs.txt> for details.
383 To compile this file system support as a module, choose M here: the
384 module will be called romfs. Note that the file system of your
385 root partition (the one containing the directory /) cannot be a
388 If you don't know whether you need it, then you don't need it:
394 If you say Y here, you will be able to set per user limits for disk
395 usage (also called disk quotas). Currently, it works for the
396 ext2, ext3, and reiserfs file system. You need additional software
397 in order to use quota support (you can download sources from
398 <http://www.sf.net/projects/linuxquota/>). For further details, read
399 the Quota mini-HOWTO, available from
400 <http://www.tldp.org/docs.html#howto>. Probably the quota
401 support is only useful for multi user systems. If unsure, say N.
404 tristate "Old quota format support"
407 This quota format was (is) used by kernels earlier than 2.4.??. If
408 you have quota working and you don't want to convert to new quota
412 tristate "Quota format v2 support"
415 This quota format allows using quotas with 32-bit UIDs/GIDs. If you
416 need this functionality say Y here. Note that you will need latest
417 quota utilities for new quota format with this kernel.
421 depends on XFS_QUOTA || QUOTA
425 tristate "Kernel automounter support"
427 The automounter is a tool to automatically mount remote file systems
428 on demand. This implementation is partially kernel-based to reduce
429 overhead in the already-mounted case; this is unlike the BSD
430 automounter (amd), which is a pure user space daemon.
432 To use the automounter you need the user-space tools from the autofs
433 package; you can find the location in <file:Documentation/Changes>.
434 You also want to answer Y to "NFS file system support", below.
436 If you want to use the newer version of the automounter with more
437 features, say N here and say Y to "Kernel automounter v4 support",
440 To compile this support as a module, choose M here: the module will be
443 If you are not a part of a fairly large, distributed network, you
444 probably do not need an automounter, and can say N here.
447 tristate "Kernel automounter version 4 support (also supports v3)"
449 The automounter is a tool to automatically mount remote file systems
450 on demand. This implementation is partially kernel-based to reduce
451 overhead in the already-mounted case; this is unlike the BSD
452 automounter (amd), which is a pure user space daemon.
454 To use the automounter you need the user-space tools from
455 <ftp://ftp.kernel.org/pub/linux/daemons/autofs/testing-v4/>; you also
456 want to answer Y to "NFS file system support", below.
458 To compile this support as a module, choose M here: the module will be
459 called autofs4. You will need to add "alias autofs autofs4" to your
460 modules configuration file.
462 If you are not a part of a fairly large, distributed network or
463 don't have a laptop which needs to dynamically reconfigure to the
464 local network, you probably do not need an automounter, and can say
467 menu "CD-ROM/DVD Filesystems"
470 tristate "ISO 9660 CDROM file system support"
472 This is the standard file system used on CD-ROMs. It was previously
473 known as "High Sierra File System" and is called "hsfs" on other
474 Unix systems. The so-called Rock-Ridge extensions which allow for
475 long Unix filenames and symbolic links are also supported by this
476 driver. If you have a CD-ROM drive and want to do more with it than
477 just listen to audio CDs and watch its LEDs, say Y (and read
478 <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO,
479 available from <http://www.tldp.org/docs.html#howto>), thereby
480 enlarging your kernel by about 27 KB; otherwise say N.
482 To compile this file system support as a module, choose M here: the
483 module will be called isofs.
486 bool "Microsoft Joliet CDROM extensions"
487 depends on ISO9660_FS
489 Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system
490 which allows for long filenames in unicode format (unicode is the
491 new 16 bit character code, successor to ASCII, which encodes the
492 characters of almost all languages of the world; see
493 <http://www.unicode.org/> for more information). Say Y here if you
494 want to be able to read Joliet CD-ROMs under Linux.
497 bool "Transparent decompression extension"
498 depends on ISO9660_FS
501 This is a Linux-specific extension to RockRidge which lets you store
502 data in compressed form on a CD-ROM and have it transparently
503 decompressed when the CD-ROM is accessed. See
504 <http://www.kernel.org/pub/linux/utils/fs/zisofs/> for the tools
505 necessary to create such a filesystem. Say Y here if you want to be
506 able to read such compressed CD-ROMs.
509 # for fs/nls/Config.in
515 tristate "UDF file system support"
517 This is the new file system used on some CD-ROMs and DVDs. Say Y if
518 you intend to mount DVD discs or CDRW's written in packet mode, or
519 if written to by other UDF utilities, such as DirectCD.
520 Please read <file:Documentation/filesystems/udf.txt>.
522 To compile this file system support as a module, choose M here: the
523 module will be called udf.
529 menu "DOS/FAT/NT Filesystems"
532 tristate "DOS FAT fs support"
534 If you want to use one of the FAT-based file systems (the MS-DOS,
535 VFAT (Windows 95) and UMSDOS (used to run Linux on top of an
536 ordinary DOS partition) file systems), then you must say Y or M here
537 to include FAT support. You will then be able to mount partitions or
538 diskettes with FAT-based file systems and transparently access the
539 files on them, i.e. MSDOS files will look and behave just like all
542 This FAT support is not a file system in itself, it only provides
543 the foundation for the other file systems. You will have to say Y or
544 M to at least one of "MSDOS fs support" or "VFAT fs support" in
545 order to make use of it.
547 Another way to read and write MSDOS floppies and hard drive
548 partitions from within Linux (but not transparently) is with the
549 mtools ("man mtools") program suite. You don't need to say Y here in
552 If you need to move large files on floppies between a DOS and a
553 Linux box, say Y here, mount the floppy under Linux with an MSDOS
554 file system and use GNU tar's M option. GNU tar is a program
555 available for Unix and DOS ("man tar" or "info tar").
557 It is now also becoming possible to read and write compressed FAT
558 file systems; read <file:Documentation/filesystems/fat_cvf.txt> for
561 The FAT support will enlarge your kernel by about 37 KB. If unsure,
564 To compile this as a module, choose M here: the module will be called
565 fat. Note that if you compile the FAT support as a module, you
566 cannot compile any of the FAT-based file systems into the kernel
567 -- they will have to be modules as well.
568 The file system of your root partition (the one containing the
569 directory /) cannot be a module, so don't say M here if you intend
570 to use UMSDOS as your root file system.
573 tristate "MSDOS fs support"
576 This allows you to mount MSDOS partitions of your hard drive (unless
577 they are compressed; to access compressed MSDOS partitions under
578 Linux, you can either use the DOS emulator DOSEMU, described in the
579 DOSEMU-HOWTO, available from
580 <http://www.tldp.org/docs.html#howto>, or try dmsdosfs in
581 <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you
582 intend to use dosemu with a non-compressed MSDOS partition, say Y
583 here) and MSDOS floppies. This means that file access becomes
584 transparent, i.e. the MSDOS files look and behave just like all
587 If you want to use UMSDOS, the Unix-like file system on top of a
588 DOS file system, which allows you to run Linux from within a DOS
589 partition without repartitioning, you'll have to say Y or M here.
591 If you have Windows 95 or Windows NT installed on your MSDOS
592 partitions, you should use the VFAT file system (say Y to "VFAT fs
593 support" below), or you will not be able to see the long filenames
594 generated by Windows 95 / Windows NT.
596 This option will enlarge your kernel by about 7 KB. If unsure,
597 answer Y. This will only work if you said Y to "DOS FAT fs support"
598 as well. To compile this as a module, choose M here: the module will
602 tristate "VFAT (Windows-95) fs support"
605 This option provides support for normal Windows file systems with
606 long filenames. That includes non-compressed FAT-based file systems
607 used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
608 programs from the mtools package.
610 You cannot use the VFAT file system for your Linux root partition
611 (the one containing the directory /); use UMSDOS instead if you
612 want to run Linux from within a DOS partition (i.e. say Y to
613 "Unix like fs on top of std MSDOS fs", below).
615 The VFAT support enlarges your kernel by about 10 KB and it only
616 works if you said Y to the "DOS FAT fs support" above. Please read
617 the file <file:Documentation/filesystems/vfat.txt> for details. If
620 To compile this as a module, choose M here: the module will be called
624 #dep_tristate ' UMSDOS: Unix-like file system on top of standard MSDOS fs' CONFIG_UMSDOS_FS $CONFIG_MSDOS_FS
625 # UMSDOS is temprory broken
628 Say Y here if you want to run Linux from within an existing DOS
629 partition of your hard drive. The advantage of this is that you can
630 get away without repartitioning your hard drive (which often implies
631 backing everything up and restoring afterwards) and hence you're
632 able to quickly try out Linux or show it to your friends; the
633 disadvantage is that Linux becomes susceptible to DOS viruses and
634 that UMSDOS is somewhat slower than ext2fs. Another use of UMSDOS
635 is to write files with long unix filenames to MSDOS floppies; it
636 also allows Unix-style soft-links and owner/permissions of files on
637 MSDOS floppies. You will need a program called umssync in order to
638 make use of UMSDOS; read
639 <file:Documentation/filesystems/umsdos.txt>.
641 To get utilities for initializing/checking UMSDOS file system, or
642 latest patches and/or information, visit the UMSDOS home page at
643 <http://www.voyager.hr/~mnalis/umsdos/>.
645 This option enlarges your kernel by about 28 KB and it only works if
646 you said Y to both "DOS FAT fs support" and "MSDOS fs support"
647 above. To compile this as a module, choose M here: the module will be
648 called umsdos. Note that the file system of your root partition
649 (the one containing the directory /) cannot be a module, so saying M
650 could be dangerous. If unsure, say N.
653 tristate "NTFS file system support"
655 NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003.
657 Saying Y or M here enables read support. There is partial, but
658 safe, write support available. For write support you must also
659 say Y to "NTFS write support" below.
661 There are also a number of user-space tools available, called
662 ntfsprogs. These include ntfsundelete and ntfsresize, that work
663 without NTFS support enabled in the kernel.
665 This is a rewrite from scratch of Linux NTFS support and replaced
666 the old NTFS code starting with Linux 2.5.11. A backport to
667 the Linux 2.4 kernel series is separately available as a patch
668 from the project web site.
670 For more information see <file:Documentation/filesystems/ntfs.txt>
671 and <http://linux-ntfs.sourceforge.net/>.
673 To compile this file system support as a module, choose M here: the
674 module will be called ntfs.
676 If you are not using Windows NT, 2000, XP or 2003 in addition to
677 Linux on your computer it is safe to say N.
680 bool "NTFS debugging support"
683 If you are experiencing any problems with the NTFS file system, say
684 Y here. This will result in additional consistency checks to be
685 performed by the driver as well as additional debugging messages to
686 be written to the system log. Note that debugging messages are
687 disabled by default. To enable them, supply the option debug_msgs=1
688 at the kernel command line when booting the kernel or as an option
689 to insmod when loading the ntfs module. Once the driver is active,
690 you can enable debugging messages by doing (as root):
691 echo 1 > /proc/sys/fs/ntfs-debug
692 Replacing the "1" with "0" would disable debug messages.
694 If you leave debugging messages disabled, this results in little
695 overhead, but enabling debug messages results in very significant
696 slowdown of the system.
698 When reporting bugs, please try to have available a full dump of
699 debugging messages while the misbehaviour was occurring.
702 bool "NTFS write support"
705 This enables the partial, but safe, write support in the NTFS driver.
707 The only supported operation is overwriting existing files, without
708 changing the file length. No file or directory creation, deletion or
709 renaming is possible. Note only non-resident files can be written to
710 so you may find that some very small files (<500 bytes or so) cannot
713 While we cannot guarantee that it will not damage any data, we have
714 so far not received a single report where the driver would have
715 damaged someones data so we assume it is perfectly safe to use.
717 Note: While write support is safe in this version (a rewrite from
718 scratch of the NTFS support), it should be noted that the old NTFS
719 write support, included in Linux 2.5.10 and before (since 1997),
722 This is currently useful with TopologiLinux. TopologiLinux is run
723 on top of any DOS/Microsoft Windows system without partitioning your
724 hard disk. Unlike other Linux distributions TopologiLinux does not
725 need its own partition. For more information see
726 <http://topologi-linux.sourceforge.net/>
728 It is perfectly safe to say N here.
732 menu "Pseudo filesystems"
735 bool "/proc file system support"
737 This is a virtual file system providing information about the status
738 of the system. "Virtual" means that it doesn't take up any space on
739 your hard disk: the files are created on the fly by the kernel when
740 you try to access them. Also, you cannot read the files with older
741 version of the program less: you need to use more or cat.
743 It's totally cool; for example, "cat /proc/interrupts" gives
744 information about what the different IRQs are used for at the moment
745 (there is a small number of Interrupt ReQuest lines in your computer
746 that are used by the attached devices to gain the CPU's attention --
747 often a source of trouble if two devices are mistakenly configured
748 to use the same IRQ). The program procinfo to display some
749 information about your system gathered from the /proc file system.
751 Before you can use the /proc file system, it has to be mounted,
752 meaning it has to be given a location in the directory hierarchy.
753 That location should be /proc. A command such as "mount -t proc proc
754 /proc" or the equivalent line in /etc/fstab does the job.
756 The /proc file system is explained in the file
757 <file:Documentation/filesystems/proc.txt> and on the proc(5) manpage
760 This option will enlarge your kernel by about 67 KB. Several
761 programs depend on this, so everyone should say Y here.
768 bool "/dev file system support (OBSOLETE)"
769 depends on EXPERIMENTAL
771 This is support for devfs, a virtual file system (like /proc) which
772 provides the file system interface to device drivers, normally found
773 in /dev. Devfs does not depend on major and minor number
774 allocations. Device drivers register entries in /dev which then
775 appear automatically, which means that the system administrator does
776 not have to create character and block special device files in the
777 /dev directory using the mknod command (or MAKEDEV script) anymore.
779 This is work in progress. If you want to use this, you *must* read
780 the material in <file:Documentation/filesystems/devfs/>, especially
781 the file README there.
783 Note that devfs no longer manages /dev/pts! If you are using UNIX98
784 ptys, you will also need to enable (and mount) the /dev/pts
785 filesystem (CONFIG_DEVPTS_FS).
787 Note that devfs has been obsoleted by udev,
788 <http://www.kernel.org/pub/linux/utils/kernel/hotplug/>.
789 It has been stripped down to a bare minimum and is only provided for
790 legacy installations that use its naming scheme which is
791 unfortunately different from the names normal Linux installations
797 bool "Automatically mount at boot"
800 This option appears if you have CONFIG_DEVFS_FS enabled. Setting
801 this to 'Y' will make the kernel automatically mount devfs onto /dev
802 when the system is booted, before the init thread is started.
803 You can override this with the "devfs=nomount" boot option.
811 If you say Y here, then the /dev file system code will generate
812 debugging messages. See the file
813 <file:Documentation/filesystems/devfs/boot-options> for more
819 # It compiles as a module for testing only. It should not be used
820 # as a module in general. If we make this "tristate", a bunch of people
821 # who don't know what they are doing turn it on and complain when it
823 bool "/dev/pts file system for Unix98 PTYs"
824 depends on UNIX98_PTYS
826 You should say Y here if you said Y to "Unix98 PTY support" above.
827 You'll then get a virtual file system which can be mounted on
828 /dev/pts with "mount -t devpts". This, together with the pseudo
829 terminal master multiplexer /dev/ptmx, is used for pseudo terminal
830 support as described in The Open Group's Unix98 standard: in order
831 to acquire a pseudo terminal, a process opens /dev/ptmx; the number
832 of the pseudo terminal is then made available to the process and the
833 pseudo terminal slave can be accessed as /dev/pts/<number>. What was
834 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
836 The GNU C library glibc 2.1 contains the requisite support for this
837 mode of operation; you also need client programs that use the Unix98
838 API. Please read <file:Documentation/Changes> for more information
839 about the Unix98 pty devices.
841 config DEVPTS_FS_XATTR
842 bool "/dev/pts Extended Attributes"
845 Extended attributes are name:value pairs associated with inodes by
846 the kernel or by users (see the attr(5) manual page, or visit
847 <http://acl.bestbits.at/> for details).
851 config DEVPTS_FS_SECURITY
852 bool "/dev/pts Security Labels"
853 depends on DEVPTS_FS_XATTR
855 Security labels support alternative access control models
856 implemented by security modules like SELinux. This option
857 enables an extended attribute handler for file security
858 labels in the /dev/pts filesystem.
860 If you are not using a security module that requires using
861 extended attributes for file security labels, say N.
864 bool "Virtual memory file system support (former shm fs)"
866 Tmpfs is a file system which keeps all files in virtual memory.
868 Everything in tmpfs is temporary in the sense that no files will be
869 created on your hard drive. The files live in memory and swap
870 space. If you unmount a tmpfs instance, everything stored therein is
873 See <file:Documentation/filesystems/tmpfs.txt> for details.
876 bool "HugeTLB file system support"
877 depends X86 || IA64 || PPC64 || SPARC64 || X86_64 || BROKEN
886 Ramfs is a file system which keeps all files in RAM. It allows
887 read and write access.
889 It is more of an programming example than a useable file system. If
890 you need a file system which lives in RAM with limit checking use
893 To compile this as a module, choose M here: the module will be called
898 menu "Miscellaneous filesystems"
901 tristate "ADFS file system support (EXPERIMENTAL)"
902 depends on EXPERIMENTAL
904 The Acorn Disc Filing System is the standard file system of the
905 RiscOS operating system which runs on Acorn's ARM-based Risc PC
906 systems and the Acorn Archimedes range of machines. If you say Y
907 here, Linux will be able to read from ADFS partitions on hard drives
908 and from ADFS-formatted floppy discs. If you also want to be able to
909 write to those devices, say Y to "ADFS write support" below.
911 The ADFS partition should be the first partition (i.e.,
912 /dev/[hs]d?1) on each of your drives. Please read the file
913 <file:Documentation/filesystems/adfs.txt> for further details.
915 To compile this code as a module, choose M here: the module will be
921 bool "ADFS write support (DANGEROUS)"
924 If you say Y here, you will be able to write to ADFS partitions on
925 hard drives and ADFS-formatted floppy disks. This is experimental
926 codes, so if you're unsure, say N.
929 tristate "Amiga FFS file system support (EXPERIMENTAL)"
930 depends on EXPERIMENTAL
932 The Fast File System (FFS) is the common file system used on hard
933 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
934 if you want to be able to read and write files from and to an Amiga
935 FFS partition on your hard drive. Amiga floppies however cannot be
936 read with this driver due to an incompatibility of the floppy
937 controller used in an Amiga and the standard floppy controller in
938 PCs and workstations. Read <file:Documentation/filesystems/affs.txt>
939 and <file:fs/affs/Changes>.
941 With this driver you can also mount disk files used by Bernd
942 Schmidt's Un*X Amiga Emulator
943 (<http://www.freiburg.linux.de/~uae/>).
944 If you want to do this, you will also need to say Y or M to "Loop
945 device support", above.
947 To compile this file system support as a module, choose M here: the
948 module will be called affs. If unsure, say N.
951 tristate "Apple Macintosh file system support (EXPERIMENTAL)"
952 depends on EXPERIMENTAL
954 If you say Y here, you will be able to mount Macintosh-formatted
955 floppy disks and hard drive partitions with full read-write access.
956 Please read <file:fs/hfs/HFS.txt> to learn about the available mount
959 To compile this file system support as a module, choose M here: the
960 module will be called hfs.
963 tristate "BeOS file systemv(BeFS) support (read only) (EXPERIMENTAL)"
964 depends on EXPERIMENTAL
966 The BeOS File System (BeFS) is the native file system of Be, Inc's
967 BeOS. Notable features include support for arbitrary attributes
968 on files and directories, and database-like indices on selected
969 attributes. (Also note that this driver doesn't make those features
970 available at this time). It is a 64 bit filesystem, so it supports
971 extreemly large volumes and files.
973 If you use this filesystem, you should also say Y to at least one
974 of the NLS (native language support) options below.
976 If you don't know what this is about, say N.
978 To compile this as a module, choose M here: the module will be
985 If you say Y here, you can use the 'debug' mount option to enable
986 debugging output from the driver.
989 tristate "BFS file system support (EXPERIMENTAL)"
990 depends on EXPERIMENTAL
992 Boot File System (BFS) is a file system used under SCO UnixWare to
993 allow the bootloader access to the kernel image and other important
994 files during the boot process. It is usually mounted under /stand
995 and corresponds to the slice marked as "STAND" in the UnixWare
996 partition. You should say Y if you want to read or write the files
997 on your /stand slice from within Linux. You then also need to say Y
998 to "UnixWare slices support", below. More information about the BFS
999 file system is contained in the file
1000 <file:Documentation/filesystems/bfs.txt>.
1002 If you don't know what this is about, say N.
1004 To compile this as a module, choose M here: the module will be called
1005 bfs. Note that the file system of your root partition (the one
1006 containing the directory /) cannot be compiled as a module.
1011 tristate "EFS file system support (read only) (EXPERIMENTAL)"
1012 depends on EXPERIMENTAL
1014 EFS is an older file system used for non-ISO9660 CD-ROMs and hard
1015 disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
1016 uses the XFS file system for hard disk partitions however).
1018 This implementation only offers read-only access. If you don't know
1019 what all this is about, it's safe to say N. For more information
1020 about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
1022 To compile the EFS file system support as a module, choose M here: the
1023 module will be called efs.
1026 tristate "Journalling Flash File System (JFFS) support"
1029 JFFS is the Journaling Flash File System developed by Axis
1030 Communications in Sweden, aimed at providing a crash/powerdown-safe
1031 file system for disk-less embedded devices. Further information is
1032 available at (<http://developer.axis.com/software/jffs/>).
1034 config JFFS_FS_VERBOSE
1035 int "JFFS debugging verbosity (0 = quiet, 3 = noisy)"
1039 Determines the verbosity level of the JFFS debugging messages.
1042 bool "JFFS stats available in /proc filesystem"
1043 depends on JFFS_FS && PROC
1045 Enabling this option will cause statistics from mounted JFFS file systems
1046 to be made available to the user in the /proc/fs/jffs/ directory.
1049 tristate "Journalling Flash File System v2 (JFFS2) support"
1055 JFFS2 is the second generation of the Journalling Flash File System
1056 for use on diskless embedded devices. It provides improved wear
1057 levelling, compression and support for hard links. You cannot use
1058 this on normal block devices, only on 'MTD' devices.
1060 Further information on the design and implementation of JFFS2 is
1061 available at <http://sources.redhat.com/jffs2/>.
1063 config JFFS2_FS_DEBUG
1064 int "JFFS2 debugging verbosity (0 = quiet, 2 = noisy)"
1068 This controls the amount of debugging messages produced by the JFFS2
1069 code. Set it to zero for use in production systems. For evaluation,
1070 testing and debugging, it's advisable to set it to one. This will
1071 enable a few assertions and will print debugging messages at the
1072 KERN_DEBUG loglevel, where they won't normally be visible. Level 2
1073 is unlikely to be useful - it enables extra debugging in certain
1074 areas which at one point needed debugging, but when the bugs were
1075 located and fixed, the detailed messages were relegated to level 2.
1077 If reporting bugs, please try to have available a full dump of the
1078 messages at debug level 1 while the misbehaviour was occurring.
1080 config JFFS2_FS_NAND
1081 bool "JFFS2 support for NAND flash (EXPERIMENTAL)"
1082 depends on JFFS2_FS && EXPERIMENTAL
1085 This enables the experimental support for NAND flash in JFFS2. NAND
1086 is a newer type of flash chip design than the traditional NOR flash,
1087 with higher density but a handful of characteristics which make it
1088 more interesting for the file system to use. Support for NAND flash
1089 is not yet complete and may corrupt data. For further information,
1090 including a link to the mailing list where details of the remaining
1091 work to be completed for NAND flash support can be found, see the
1092 JFFS2 web site at <http://sources.redhat.com/jffs2>.
1094 Say 'N' unless you have NAND flash and you are willing to test and
1095 develop JFFS2 support for it.
1098 tristate "Compressed ROM file system support"
1101 Saying Y here includes support for CramFs (Compressed ROM File
1102 System). CramFs is designed to be a simple, small, and compressed
1103 file system for ROM based embedded systems. CramFs is read-only,
1104 limited to 256MB file systems (with 16MB files), and doesn't support
1105 16/32 bits uid/gid, hard links and timestamps.
1107 See <file:Documentation/filesystems/cramfs.txt> and
1108 <file:fs/cramfs/README> for further information.
1110 To compile this as a module, choose M here: the module will be called
1111 cramfs. Note that the root file system (the one containing the
1112 directory /) cannot be compiled as a module.
1117 tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
1119 FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
1120 file system format. VERITAS VxFS(TM) is the standard file system
1121 of SCO UnixWare (and possibly others) and optionally available
1122 for Sunsoft Solaris, HP-UX and many other operating systems.
1123 Currently only readonly access is supported.
1125 NOTE: the file system type as used by mount(1), mount(2) and
1126 fstab(5) is 'vxfs' as it describes the file system format, not
1129 To compile this as a module, choose M here: the module will be
1130 called freevxfs. If unsure, say N.
1134 tristate "OS/2 HPFS file system support"
1136 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
1137 is the file system used for organizing files on OS/2 hard disk
1138 partitions. Say Y if you want to be able to read files from and
1139 write files to an OS/2 HPFS partition on your hard drive. OS/2
1140 floppies however are in regular MSDOS format, so you don't need this
1141 option in order to be able to read them. Read
1142 <file:Documentation/filesystems/hpfs.txt>.
1144 To compile this file system support as a module, choose M here: the
1145 module will be called hpfs. If unsure, say N.
1150 tristate "QNX4 file system support (read only)"
1152 This is the file system used by the real-time operating systems
1153 QNX 4 and QNX 6 (the latter is also called QNX RTP).
1154 Further information is available at <http://www.qnx.com/>.
1155 Say Y if you intend to mount QNX hard disks or floppies.
1156 Unless you say Y to "QNX4FS read-write support" below, you will
1157 only be able to read these file systems.
1159 To compile this file system support as a module, choose M here: the
1160 module will be called qnx4.
1162 If you don't know whether you need it, then you don't need it:
1166 bool "QNX4FS write support (DANGEROUS)"
1167 depends on QNX4FS_FS && EXPERIMENTAL
1169 Say Y if you want to test write support for QNX4 file systems.
1171 It's currently broken, so for now:
1177 tristate "System V/Xenix/V7/Coherent file system support"
1179 SCO, Xenix and Coherent are commercial Unix systems for Intel
1180 machines, and Version 7 was used on the DEC PDP-11. Saying Y
1181 here would allow you to read from their floppies and hard disk
1184 If you have floppies or hard disk partitions like that, it is likely
1185 that they contain binaries from those other Unix systems; in order
1186 to run these binaries, you will want to install linux-abi which is a
1187 a set of kernel modules that lets you run SCO, Xenix, Wyse,
1188 UnixWare, Dell Unix and System V programs under Linux. It is
1189 available via FTP (user: ftp) from
1190 <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
1191 NOTE: that will work only for binaries from Intel-based systems;
1192 PDP ones will have to wait until somebody ports Linux to -11 ;-)
1194 If you only intend to mount files from some other Unix over the
1195 network using NFS, you don't need the System V file system support
1196 (but you need NFS file system support obviously).
1198 Note that this option is generally not needed for floppies, since a
1199 good portable way to transport files and directories between unixes
1200 (and even other operating systems) is given by the tar program ("man
1201 tar" or preferably "info tar"). Note also that this option has
1202 nothing whatsoever to do with the option "System V IPC". Read about
1203 the System V file system in
1204 <file:Documentation/filesystems/sysv-fs.txt>.
1205 Saying Y here will enlarge your kernel by about 27 KB.
1207 To compile this as a module, choose M here: the module will be called
1210 If you haven't heard about all of this before, it's safe to say N.
1215 tristate "UFS file system support (read only)"
1217 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
1218 OpenBSD and NeXTstep) use a file system called UFS. Some System V
1219 Unixes can create and mount hard disk partitions and diskettes using
1220 this file system as well. Saying Y here will allow you to read from
1221 these partitions; if you also want to write to them, say Y to the
1222 experimental "UFS file system write support", below. Please read the
1223 file <file:Documentation/filesystems/ufs.txt> for more information.
1225 If you only intend to mount files from some other Unix over the
1226 network using NFS, you don't need the UFS file system support (but
1227 you need NFS file system support obviously).
1229 Note that this option is generally not needed for floppies, since a
1230 good portable way to transport files and directories between unixes
1231 (and even other operating systems) is given by the tar program ("man
1232 tar" or preferably "info tar").
1234 When accessing NeXTstep files, you may need to convert them from the
1235 NeXT character set to the Latin1 character set; use the program
1236 recode ("info recode") for this purpose.
1238 To compile the UFS file system support as a module, choose M here: the
1239 module will be called ufs.
1241 If you haven't heard about all of this before, it's safe to say N.
1244 bool "UFS file system write support (DANGEROUS)"
1245 depends on UFS_FS && EXPERIMENTAL
1247 Say Y here if you want to try writing to UFS partitions. This is
1248 experimental, so you should back up your UFS partitions beforehand.
1252 menu "Network File Systems"
1256 tristate "NFS file system support"
1261 If you are connected to some other (usually local) Unix computer
1262 (using SLIP, PLIP, PPP or Ethernet) and want to mount files residing
1263 on that computer (the NFS server) using the Network File Sharing
1264 protocol, say Y. "Mounting files" means that the client can access
1265 the files with usual UNIX commands as if they were sitting on the
1266 client's hard disk. For this to work, the server must run the
1267 programs nfsd and mountd (but does not need to have NFS file system
1268 support enabled in its kernel). NFS is explained in the Network
1269 Administrator's Guide, available from
1270 <http://www.tldp.org/docs.html#guide>, on its man page: "man
1271 nfs", and in the NFS-HOWTO.
1273 A superior but less widely used alternative to NFS is provided by
1274 the Coda file system; see "Coda file system support" below.
1276 If you say Y here, you should have said Y to TCP/IP networking also.
1277 This option would enlarge your kernel by about 27 KB.
1279 To compile this file system support as a module, choose M here: the
1280 module will be called nfs.
1282 If you are configuring a diskless machine which will mount its root
1283 file system over NFS at boot time, say Y here and to "Kernel
1284 level IP autoconfiguration" above and to "Root file system on NFS"
1285 below. You cannot compile this driver as a module in this case.
1286 There are two packages designed for booting diskless machines over
1287 the net: netboot, available from
1288 <http://ftp1.sourceforge.net/netboot/>, and Etherboot,
1289 available from <http://ftp1.sourceforge.net/etherboot/>.
1291 If you don't know what all this is about, say N.
1294 bool "Provide NFSv3 client support"
1297 Say Y here if you want your NFS client to be able to speak the newer
1298 version 3 of the NFS protocol.
1303 bool "Provide NFSv4 client support (EXPERIMENTAL)"
1304 depends on NFS_FS && EXPERIMENTAL
1306 Say Y here if you want your NFS client to be able to speak the newer
1307 version 4 of the NFS protocol. This feature is experimental, and
1308 should only be used if you are interested in helping to test NFSv4.
1313 bool "Allow direct I/O on NFS files (EXPERIMENTAL)"
1314 depends on NFS_FS && EXPERIMENTAL
1316 This option enables applications to perform uncached I/O on files
1317 in NFS file systems using the O_DIRECT open() flag. When O_DIRECT
1318 is set for a file, its data is not cached in the system's page
1319 cache. Data is moved to and from user-level application buffers
1320 directly. Unlike local disk-based file systems, NFS O_DIRECT has
1321 no alignment restrictions.
1323 Unless your program is designed to use O_DIRECT properly, you are
1324 much better off allowing the NFS client to manage data caching for
1325 you. Misusing O_DIRECT can cause poor server performance or network
1326 storms. This kernel build option defaults OFF to avoid exposing
1327 system administrators unwittingly to a potentially hazardous
1330 For more details on NFS O_DIRECT, see fs/nfs/direct.c.
1332 If unsure, say N. This reduces the size of the NFS client, and
1333 causes open() to return EINVAL if a file residing in NFS is
1334 opened with the O_DIRECT flag.
1337 tristate "NFS server support"
1342 If you want your Linux box to act as an NFS *server*, so that other
1343 computers on your local network which support NFS can access certain
1344 directories on your box transparently, you have two options: you can
1345 use the self-contained user space program nfsd, in which case you
1346 should say N here, or you can say Y and use the kernel based NFS
1347 server. The advantage of the kernel based solution is that it is
1350 In either case, you will need support software; the respective
1351 locations are given in the file <file:Documentation/Changes> in the
1354 If you say Y here, you will get support for version 2 of the NFS
1355 protocol (NFSv2). If you also want NFSv3, say Y to the next question
1358 Please read the NFS-HOWTO, available from
1359 <http://www.tldp.org/docs.html#howto>.
1361 To compile the NFS server support as a module, choose M here: the
1362 module will be called nfsd. If unsure, say N.
1365 bool "Provide NFSv3 server support"
1368 If you would like to include the NFSv3 server as well as the NFSv2
1369 server, say Y here. If unsure, say Y.
1372 bool "Provide NFSv4 server support (EXPERIMENTAL)"
1373 depends on NFSD_V3 && EXPERIMENTAL
1375 If you would like to include the NFSv4 server as well as the NFSv2
1376 and NFSv3 servers, say Y here. This feature is experimental, and
1377 should only be used if you are interested in helping to test NFSv4.
1381 bool "Provide NFS server over TCP support (EXPERIMENTAL)"
1382 depends on NFSD && EXPERIMENTAL
1384 Enable NFS service over TCP connections. This the officially
1385 still experimental, but seems to work well.
1388 bool "Root file system on NFS"
1389 depends on NFS_FS=y && IP_PNP
1391 If you want your Linux box to mount its whole root file system (the
1392 one containing the directory /) from some other computer over the
1393 net via NFS (presumably because your box doesn't have a hard disk),
1394 say Y. Read <file:Documentation/nfsroot.txt> for details. It is
1395 likely that in this case, you also want to say Y to "Kernel level IP
1396 autoconfiguration" so that your box can discover its network address
1399 Most people say N here.
1406 depends on NFSD_V3 || NFS_V3
1417 tristate "Provide RPCSEC_GSS authentication (EXPERIMENTAL)"
1418 depends on SUNRPC && EXPERIMENTAL
1419 default SUNRPC if NFS_V4=y
1421 Provides cryptographic authentication for NFS rpc requests. To
1422 make this useful, you must also select at least one rpcsec_gss
1424 Note: You should always select this option if you wish to use
1427 config RPCSEC_GSS_KRB5
1428 tristate "Kerberos V mechanism for RPCSEC_GSS (EXPERIMENTAL)"
1429 depends on SUNRPC_GSS && CRYPTO_DES && CRYPTO_MD5
1430 default SUNRPC_GSS if NFS_V4=y
1432 Provides a gss-api mechanism based on Kerberos V5 (this is
1433 mandatory for RFC3010-compliant NFSv4 implementations).
1434 Requires a userspace daemon;
1435 see http://www.citi.umich.edu/projects/nfsv4/.
1437 Note: If you select this option, please ensure that you also
1438 enable the MD5 and DES crypto ciphers.
1441 tristate "SMB file system support (to mount Windows shares etc.)"
1444 SMB (Server Message Block) is the protocol Windows for Workgroups
1445 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
1446 files and printers over local networks. Saying Y here allows you to
1447 mount their file systems (often called "shares" in this context) and
1448 access them just like any other Unix directory. Currently, this
1449 works only if the Windows machines use TCP/IP as the underlying
1450 transport protocol, and not NetBEUI. For details, read
1451 <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
1452 available from <http://www.tldp.org/docs.html#howto>.
1454 Note: if you just want your box to act as an SMB *server* and make
1455 files and printing services available to Windows clients (which need
1456 to have a TCP/IP stack), you don't need to say Y here; you can use
1457 the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
1460 General information about how to connect Linux, Windows machines and
1461 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1463 To compile the SMB support as a module, choose M here: the module will
1464 be called smbfs. Most people say N, however.
1466 config SMB_NLS_DEFAULT
1467 bool "Use a default NLS"
1470 Enabling this will make smbfs use nls translations by default. You
1471 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
1472 settings and you need to give the default nls for the SMB server as
1473 CONFIG_SMB_NLS_REMOTE.
1475 The nls settings can be changed at mount time, if your smbmount
1476 supports that, using the codepage and iocharset parameters.
1478 smbmount from samba 2.2.0 or later supports this.
1480 config SMB_NLS_REMOTE
1481 string "Default Remote NLS Option"
1482 depends on SMB_NLS_DEFAULT
1485 This setting allows you to specify a default value for which
1486 codepage the server uses. If this field is left blank no
1487 translations will be done by default. The local codepage/charset
1488 default to CONFIG_NLS_DEFAULT.
1490 The nls settings can be changed at mount time, if your smbmount
1491 supports that, using the codepage and iocharset parameters.
1493 smbmount from samba 2.2.0 or later supports this.
1496 tristate "CIFS support (advanced network filesystem for Samba, Window and other CIFS compliant servers)(EXPERIMENTAL)"
1499 This is the client VFS module for the Common Internet File System
1500 (CIFS) protocol which is the successor to the Server Message Block
1501 (SMB) protocol, the native file sharing mechanism for most early
1502 PC operating systems. CIFS is fully supported by current network
1503 file servers such as Windows 2000 (including Windows NT version 4
1504 and Windows XP) as well by Samba (which provides excellent CIFS
1505 server support for Linux and many other operating systems). For
1506 production systems the smbfs module may be used instead of this
1507 cifs module since smbfs is currently more stable and provides
1508 support for older servers. The intent of this module is to provide the
1509 most advanced network file system function for CIFS compliant servers,
1510 including support for dfs (hierarchical name space), secure per-user
1511 session establishment, safe distributed caching (oplock), optional
1512 packet signing, Unicode and other internationalization improvements, and
1513 optional Winbind (nsswitch) integration. This module is in an early
1514 development stage, so unless you are specifically interested in this
1515 filesystem, just say N.
1518 tristate "NCP file system support (to mount NetWare volumes)"
1519 depends on IPX!=n || INET
1521 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
1522 used by Novell NetWare clients to talk to file servers. It is to
1523 IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
1524 to mount NetWare file server volumes and to access them just like
1525 any other Unix directory. For details, please read the file
1526 <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
1527 the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
1529 You do not have to say Y here if you want your Linux box to act as a
1530 file *server* for Novell NetWare clients.
1532 General information about how to connect Linux, Windows machines and
1533 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1535 To compile this as a module, choose M here: the module will be called
1536 ncpfs. Say N unless you are connected to a Novell network.
1538 source "fs/ncpfs/Kconfig"
1541 tristate "Coda file system support (advanced network fs)"
1544 Coda is an advanced network file system, similar to NFS in that it
1545 enables you to mount file systems of a remote server and access them
1546 with regular Unix commands as if they were sitting on your hard
1547 disk. Coda has several advantages over NFS: support for
1548 disconnected operation (e.g. for laptops), read/write server
1549 replication, security model for authentication and encryption,
1550 persistent client caches and write back caching.
1552 If you say Y here, your Linux box will be able to act as a Coda
1553 *client*. You will need user level code as well, both for the
1554 client and server. Servers are currently user level, i.e. they need
1555 no kernel support. Please read
1556 <file:Documentation/filesystems/coda.txt> and check out the Coda
1557 home page <http://www.coda.cs.cmu.edu/>.
1559 To compile the coda client support as a module, choose M here: the
1560 module will be called coda.
1562 config CODA_FS_OLD_API
1563 bool "Use 96-bit Coda file identifiers"
1566 A new kernel-userspace API had to be introduced for Coda v6.0
1567 to support larger 128-bit file identifiers as needed by the
1568 new realms implementation.
1570 However this new API is not backward compatible with older
1571 clients. If you really need to run the old Coda userspace
1572 cache manager then say Y.
1574 For most cases you probably want to say N.
1576 config INTERMEZZO_FS
1577 tristate "InterMezzo file system support (replicating fs) (EXPERIMENTAL)"
1578 depends on INET && EXPERIMENTAL
1580 InterMezzo is a networked file system with disconnected operation
1581 and kernel level write back caching. It is most often used for
1582 replicating potentially large trees or keeping laptop/desktop copies
1585 If you say Y or M your kernel or module will provide InterMezzo
1586 support. You will also need a file server daemon, which you can get
1587 from <http://www.inter-mezzo.org/>.
1590 # for fs/nls/Config.in
1591 tristate "Andrew File System support (AFS) (Experimental)"
1592 depends on INET && EXPERIMENTAL
1595 If you say Y here, you will get an experimental Andrew File System
1596 driver. It currently only supports unsecured read-only AFS access.
1598 See Documentation/filesystems/afs.txt for more intormation.
1607 menu "Partition Types"
1609 source "fs/partitions/Kconfig"
1613 source "fs/nls/Kconfig"