2 # File system configuration
9 source "fs/ext2/Kconfig"
10 source "fs/ext3/Kconfig"
11 source "fs/ext4/Kconfig"
16 depends on EXT2_FS_XIP
19 source "fs/jbd/Kconfig"
20 source "fs/jbd2/Kconfig"
23 # Meta block cache for Extended Attributes (ext2/ext3/ext4)
25 default y if EXT2_FS=y && EXT2_FS_XATTR
26 default y if EXT3_FS=y && EXT3_FS_XATTR
27 default y if EXT4_FS=y && EXT4_FS_XATTR
28 default m if EXT2_FS_XATTR || EXT3_FS_XATTR || EXT4_FS_XATTR
30 source "fs/reiserfs/Kconfig"
31 source "fs/jfs/Kconfig"
34 # Posix ACL utility routines (for now, only ext2/ext3/jfs/reiserfs/nfs4)
36 # NOTE: you can implement Posix ACLs without these helpers (XFS does).
37 # Never use this symbol for ifdefs.
43 bool "Enable POSIX file locking API" if EMBEDDED
46 This option enables standard file locking support, required
47 for filesystems like NFS and for the flock() system
48 call. Disabling this option saves about 11k.
50 source "fs/xfs/Kconfig"
51 source "fs/gfs2/Kconfig"
52 source "fs/ocfs2/Kconfig"
53 source "fs/btrfs/Kconfig"
57 source "fs/notify/Kconfig"
62 If you say Y here, you will be able to set per user limits for disk
63 usage (also called disk quotas). Currently, it works for the
64 ext2, ext3, and reiserfs file system. ext3 also supports journalled
65 quotas for which you don't need to run quotacheck(8) after an unclean
67 For further details, read the Quota mini-HOWTO, available from
68 <http://www.tldp.org/docs.html#howto>, or the documentation provided
69 with the quota tools. Probably the quota support is only useful for
70 multi user systems. If unsure, say N.
72 config QUOTA_NETLINK_INTERFACE
73 bool "Report quota messages through netlink interface"
74 depends on QUOTA && NET
76 If you say Y here, quota warnings (about exceeding softlimit, reaching
77 hardlimit, etc.) will be reported through netlink interface. If unsure,
80 config PRINT_QUOTA_WARNING
81 bool "Print quota warnings to console (OBSOLETE)"
85 If you say Y here, quota warnings (about exceeding softlimit, reaching
86 hardlimit, etc.) will be printed to the process' controlling terminal.
87 Note that this behavior is currently deprecated and may go away in
88 future. Please use notification via netlink socket instead.
90 # Generic support for tree structured quota files. Seleted when needed.
95 tristate "Old quota format support"
98 This quota format was (is) used by kernels earlier than 2.4.22. If
99 you have quota working and you don't want to convert to new quota
103 tristate "Quota format v2 support"
107 This quota format allows using quotas with 32-bit UIDs/GIDs. If you
108 need this functionality say Y here.
112 depends on XFS_QUOTA || QUOTA
115 source "fs/autofs/Kconfig"
116 source "fs/autofs4/Kconfig"
117 source "fs/fuse/Kconfig"
124 menu "CD-ROM/DVD Filesystems"
126 source "fs/isofs/Kconfig"
127 source "fs/udf/Kconfig"
133 menu "DOS/FAT/NT Filesystems"
135 source "fs/fat/Kconfig"
136 source "fs/ntfs/Kconfig"
141 menu "Pseudo filesystems"
143 source "fs/proc/Kconfig"
144 source "fs/sysfs/Kconfig"
147 bool "Virtual memory file system support (former shm fs)"
149 Tmpfs is a file system which keeps all files in virtual memory.
151 Everything in tmpfs is temporary in the sense that no files will be
152 created on your hard drive. The files live in memory and swap
153 space. If you unmount a tmpfs instance, everything stored therein is
156 See <file:Documentation/filesystems/tmpfs.txt> for details.
158 config TMPFS_POSIX_ACL
159 bool "Tmpfs POSIX Access Control Lists"
163 POSIX Access Control Lists (ACLs) support permissions for users and
164 groups beyond the owner/group/world scheme.
166 To learn more about Access Control Lists, visit the POSIX ACLs for
167 Linux website <http://acl.bestbits.at/>.
169 If you don't know what Access Control Lists are, say N.
172 bool "HugeTLB file system support"
173 depends on X86 || IA64 || PPC64 || SPARC64 || (SUPERH && MMU) || \
174 (S390 && 64BIT) || BROKEN
176 hugetlbfs is a filesystem backing for HugeTLB pages, based on
177 ramfs. For architectures that support it, say Y here and read
178 <file:Documentation/vm/hugetlbpage.txt> for details.
185 source "fs/configfs/Kconfig"
189 menuconfig MISC_FILESYSTEMS
190 bool "Miscellaneous filesystems"
193 Say Y here to get to see options for various miscellaneous
194 filesystems, such as filesystems that came from other
197 This option alone does not add any kernel code.
199 If you say N, all options in this submenu will be skipped and
200 disabled; if unsure, say Y here.
204 source "fs/adfs/Kconfig"
205 source "fs/affs/Kconfig"
206 source "fs/ecryptfs/Kconfig"
207 source "fs/hfs/Kconfig"
208 source "fs/hfsplus/Kconfig"
211 tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)"
212 depends on BLOCK && EXPERIMENTAL
215 The BeOS File System (BeFS) is the native file system of Be, Inc's
216 BeOS. Notable features include support for arbitrary attributes
217 on files and directories, and database-like indices on selected
218 attributes. (Also note that this driver doesn't make those features
219 available at this time). It is a 64 bit filesystem, so it supports
220 extremely large volumes and files.
222 If you use this filesystem, you should also say Y to at least one
223 of the NLS (native language support) options below.
225 If you don't know what this is about, say N.
227 To compile this as a module, choose M here: the module will be
234 If you say Y here, you can use the 'debug' mount option to enable
235 debugging output from the driver.
238 tristate "BFS file system support (EXPERIMENTAL)"
239 depends on BLOCK && EXPERIMENTAL
241 Boot File System (BFS) is a file system used under SCO UnixWare to
242 allow the bootloader access to the kernel image and other important
243 files during the boot process. It is usually mounted under /stand
244 and corresponds to the slice marked as "STAND" in the UnixWare
245 partition. You should say Y if you want to read or write the files
246 on your /stand slice from within Linux. You then also need to say Y
247 to "UnixWare slices support", below. More information about the BFS
248 file system is contained in the file
249 <file:Documentation/filesystems/bfs.txt>.
251 If you don't know what this is about, say N.
253 To compile this as a module, choose M here: the module will be called
254 bfs. Note that the file system of your root partition (the one
255 containing the directory /) cannot be compiled as a module.
260 tristate "EFS file system support (read only) (EXPERIMENTAL)"
261 depends on BLOCK && EXPERIMENTAL
263 EFS is an older file system used for non-ISO9660 CD-ROMs and hard
264 disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
265 uses the XFS file system for hard disk partitions however).
267 This implementation only offers read-only access. If you don't know
268 what all this is about, it's safe to say N. For more information
269 about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
271 To compile the EFS file system support as a module, choose M here: the
272 module will be called efs.
274 source "fs/jffs2/Kconfig"
275 # UBIFS File system configuration
276 source "fs/ubifs/Kconfig"
279 tristate "Compressed ROM file system support (cramfs)"
283 Saying Y here includes support for CramFs (Compressed ROM File
284 System). CramFs is designed to be a simple, small, and compressed
285 file system for ROM based embedded systems. CramFs is read-only,
286 limited to 256MB file systems (with 16MB files), and doesn't support
287 16/32 bits uid/gid, hard links and timestamps.
289 See <file:Documentation/filesystems/cramfs.txt> and
290 <file:fs/cramfs/README> for further information.
292 To compile this as a module, choose M here: the module will be called
293 cramfs. Note that the root file system (the one containing the
294 directory /) cannot be compiled as a module.
299 tristate "SquashFS 4.0 - Squashed file system support"
303 Saying Y here includes support for SquashFS 4.0 (a Compressed
304 Read-Only File System). Squashfs is a highly compressed read-only
305 filesystem for Linux. It uses zlib compression to compress both
306 files, inodes and directories. Inodes in the system are very small
307 and all blocks are packed to minimise data overhead. Block sizes
308 greater than 4K are supported up to a maximum of 1 Mbytes (default
309 block size 128K). SquashFS 4.0 supports 64 bit filesystems and files
310 (larger than 4GB), full uid/gid information, hard links and
313 Squashfs is intended for general read-only filesystem use, for
314 archival use (i.e. in cases where a .tar.gz file may be used), and in
315 embedded systems where low overhead is needed. Further information
316 and tools are available from http://squashfs.sourceforge.net.
318 If you want to compile this as a module ( = code which can be
319 inserted in and removed from the running kernel whenever you want),
320 say M here and read <file:Documentation/modules.txt>. The module
321 will be called squashfs. Note that the root file system (the one
322 containing the directory /) cannot be compiled as a module.
326 config SQUASHFS_EMBEDDED
328 bool "Additional option for memory-constrained systems"
332 Saying Y here allows you to specify cache size.
336 config SQUASHFS_FRAGMENT_CACHE_SIZE
337 int "Number of fragments cached" if SQUASHFS_EMBEDDED
341 By default SquashFS caches the last 3 fragments read from
342 the filesystem. Increasing this amount may mean SquashFS
343 has to re-read fragments less often from disk, at the expense
344 of extra system memory. Decreasing this amount will mean
345 SquashFS uses less memory at the expense of extra reads from disk.
347 Note there must be at least one cached fragment. Anything
348 much more than three will probably not make much difference.
351 tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
354 FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
355 file system format. VERITAS VxFS(TM) is the standard file system
356 of SCO UnixWare (and possibly others) and optionally available
357 for Sunsoft Solaris, HP-UX and many other operating systems.
358 Currently only readonly access is supported.
360 NOTE: the file system type as used by mount(1), mount(2) and
361 fstab(5) is 'vxfs' as it describes the file system format, not
364 To compile this as a module, choose M here: the module will be
365 called freevxfs. If unsure, say N.
368 tristate "Minix file system support"
371 Minix is a simple operating system used in many classes about OS's.
372 The minix file system (method to organize files on a hard disk
373 partition or a floppy disk) was the original file system for Linux,
374 but has been superseded by the second extended file system ext2fs.
375 You don't want to use the minix file system on your hard disk
376 because of certain built-in restrictions, but it is sometimes found
377 on older Linux floppy disks. This option will enlarge your kernel
378 by about 28 KB. If unsure, say N.
380 To compile this file system support as a module, choose M here: the
381 module will be called minix. Note that the file system of your root
382 partition (the one containing the directory /) cannot be compiled as
386 tristate "SonicBlue Optimized MPEG File System support"
390 This is the proprietary file system used by the Rio Karma music
391 player and ReplayTV DVR. Despite the name, this filesystem is not
392 more efficient than a standard FS for MPEG files, in fact likely
393 the opposite is true. Say Y if you have either of these devices
394 and wish to mount its disk.
396 To compile this file system support as a module, choose M here: the
397 module will be called omfs. If unsure, say N.
400 tristate "OS/2 HPFS file system support"
403 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
404 is the file system used for organizing files on OS/2 hard disk
405 partitions. Say Y if you want to be able to read files from and
406 write files to an OS/2 HPFS partition on your hard drive. OS/2
407 floppies however are in regular MSDOS format, so you don't need this
408 option in order to be able to read them. Read
409 <file:Documentation/filesystems/hpfs.txt>.
411 To compile this file system support as a module, choose M here: the
412 module will be called hpfs. If unsure, say N.
416 tristate "QNX4 file system support (read only)"
419 This is the file system used by the real-time operating systems
420 QNX 4 and QNX 6 (the latter is also called QNX RTP).
421 Further information is available at <http://www.qnx.com/>.
422 Say Y if you intend to mount QNX hard disks or floppies.
423 Unless you say Y to "QNX4FS read-write support" below, you will
424 only be able to read these file systems.
426 To compile this file system support as a module, choose M here: the
427 module will be called qnx4.
429 If you don't know whether you need it, then you don't need it:
433 bool "QNX4FS write support (DANGEROUS)"
434 depends on QNX4FS_FS && EXPERIMENTAL && BROKEN
436 Say Y if you want to test write support for QNX4 file systems.
438 It's currently broken, so for now:
442 tristate "ROM file system support"
445 This is a very small read-only file system mainly intended for
446 initial ram disks of installation disks, but it could be used for
447 other read-only media as well. Read
448 <file:Documentation/filesystems/romfs.txt> for details.
450 To compile this file system support as a module, choose M here: the
451 module will be called romfs. Note that the file system of your
452 root partition (the one containing the directory /) cannot be a
455 If you don't know whether you need it, then you don't need it:
460 tristate "System V/Xenix/V7/Coherent file system support"
463 SCO, Xenix and Coherent are commercial Unix systems for Intel
464 machines, and Version 7 was used on the DEC PDP-11. Saying Y
465 here would allow you to read from their floppies and hard disk
468 If you have floppies or hard disk partitions like that, it is likely
469 that they contain binaries from those other Unix systems; in order
470 to run these binaries, you will want to install linux-abi which is
471 a set of kernel modules that lets you run SCO, Xenix, Wyse,
472 UnixWare, Dell Unix and System V programs under Linux. It is
473 available via FTP (user: ftp) from
474 <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
475 NOTE: that will work only for binaries from Intel-based systems;
476 PDP ones will have to wait until somebody ports Linux to -11 ;-)
478 If you only intend to mount files from some other Unix over the
479 network using NFS, you don't need the System V file system support
480 (but you need NFS file system support obviously).
482 Note that this option is generally not needed for floppies, since a
483 good portable way to transport files and directories between unixes
484 (and even other operating systems) is given by the tar program ("man
485 tar" or preferably "info tar"). Note also that this option has
486 nothing whatsoever to do with the option "System V IPC". Read about
487 the System V file system in
488 <file:Documentation/filesystems/sysv-fs.txt>.
489 Saying Y here will enlarge your kernel by about 27 KB.
491 To compile this as a module, choose M here: the module will be called
494 If you haven't heard about all of this before, it's safe to say N.
498 tristate "UFS file system support (read only)"
501 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
502 OpenBSD and NeXTstep) use a file system called UFS. Some System V
503 Unixes can create and mount hard disk partitions and diskettes using
504 this file system as well. Saying Y here will allow you to read from
505 these partitions; if you also want to write to them, say Y to the
506 experimental "UFS file system write support", below. Please read the
507 file <file:Documentation/filesystems/ufs.txt> for more information.
509 The recently released UFS2 variant (used in FreeBSD 5.x) is
512 Note that this option is generally not needed for floppies, since a
513 good portable way to transport files and directories between unixes
514 (and even other operating systems) is given by the tar program ("man
515 tar" or preferably "info tar").
517 When accessing NeXTstep files, you may need to convert them from the
518 NeXT character set to the Latin1 character set; use the program
519 recode ("info recode") for this purpose.
521 To compile the UFS file system support as a module, choose M here: the
522 module will be called ufs.
524 If you haven't heard about all of this before, it's safe to say N.
527 bool "UFS file system write support (DANGEROUS)"
528 depends on UFS_FS && EXPERIMENTAL
530 Say Y here if you want to try writing to UFS partitions. This is
531 experimental, so you should back up your UFS partitions beforehand.
537 If you are experiencing any problems with the UFS filesystem, say
538 Y here. This will result in _many_ additional debugging messages to be
539 written to the system log.
541 endif # MISC_FILESYSTEMS
543 menuconfig NETWORK_FILESYSTEMS
544 bool "Network File Systems"
548 Say Y here to get to see options for network filesystems and
549 filesystem-related networking code, such as NFS daemon and
550 RPCSEC security modules.
552 This option alone does not add any kernel code.
554 If you say N, all options in this submenu will be skipped and
555 disabled; if unsure, say Y here.
557 if NETWORK_FILESYSTEMS
560 tristate "NFS client support"
564 select NFS_ACL_SUPPORT if NFS_V3_ACL
566 Choose Y here if you want to access files residing on other
567 computers using Sun's Network File System protocol. To compile
568 this file system support as a module, choose M here: the module
571 To mount file systems exported by NFS servers, you also need to
572 install the user space mount.nfs command which can be found in
573 the Linux nfs-utils package, available from http://linux-nfs.org/.
574 Information about using the mount command is available in the
575 mount(8) man page. More detail about the Linux NFS client
576 implementation is available via the nfs(5) man page.
578 Below you can choose which versions of the NFS protocol are
579 available in the kernel to mount NFS servers. Support for NFS
580 version 2 (RFC 1094) is always available when NFS_FS is selected.
582 To configure a system which mounts its root file system via NFS
583 at boot time, say Y here, select "Kernel level IP
584 autoconfiguration" in the NETWORK menu, and select "Root file
585 system on NFS" below. You cannot compile this file system as a
591 bool "NFS client support for NFS version 3"
594 This option enables support for version 3 of the NFS protocol
595 (RFC 1813) in the kernel's NFS client.
600 bool "NFS client support for the NFSv3 ACL protocol extension"
603 Some NFS servers support an auxiliary NFSv3 ACL protocol that
604 Sun added to Solaris but never became an official part of the
605 NFS version 3 protocol. This protocol extension allows
606 applications on NFS clients to manipulate POSIX Access Control
607 Lists on files residing on NFS servers. NFS servers enforce
608 ACLs on local files whether this protocol is available or not.
610 Choose Y here if your NFS server supports the Solaris NFSv3 ACL
611 protocol extension and you want your NFS client to allow
612 applications to access and modify ACLs on files on the server.
614 Most NFS servers don't support the Solaris NFSv3 ACL protocol
615 extension. You can choose N here or specify the "noacl" mount
616 option to prevent your NFS client from trying to use the NFSv3
622 bool "NFS client support for NFS version 4 (EXPERIMENTAL)"
623 depends on NFS_FS && EXPERIMENTAL
624 select RPCSEC_GSS_KRB5
626 This option enables support for version 4 of the NFS protocol
627 (RFC 3530) in the kernel's NFS client.
629 To mount NFS servers using NFSv4, you also need to install user
630 space programs which can be found in the Linux nfs-utils package,
631 available from http://linux-nfs.org/.
636 bool "Root file system on NFS"
637 depends on NFS_FS=y && IP_PNP
639 If you want your system to mount its root file system via NFS,
640 choose Y here. This is common practice for managing systems
641 without local permanent storage. For details, read
642 <file:Documentation/filesystems/nfsroot.txt>.
644 Most people say N here.
647 tristate "NFS server support"
652 select NFS_ACL_SUPPORT if NFSD_V2_ACL
654 Choose Y here if you want to allow other computers to access
655 files residing on this system using Sun's Network File System
656 protocol. To compile the NFS server support as a module,
657 choose M here: the module will be called nfsd.
659 You may choose to use a user-space NFS server instead, in which
660 case you can choose N here.
662 To export local file systems using NFS, you also need to install
663 user space programs which can be found in the Linux nfs-utils
664 package, available from http://linux-nfs.org/. More detail about
665 the Linux NFS server implementation is available via the
668 Below you can choose which versions of the NFS protocol are
669 available to clients mounting the NFS server on this system.
670 Support for NFS version 2 (RFC 1094) is always available when
671 CONFIG_NFSD is selected.
680 bool "NFS server support for NFS version 3"
683 This option enables support in your system's NFS server for
684 version 3 of the NFS protocol (RFC 1813).
689 bool "NFS server support for the NFSv3 ACL protocol extension"
693 Solaris NFS servers support an auxiliary NFSv3 ACL protocol that
694 never became an official part of the NFS version 3 protocol.
695 This protocol extension allows applications on NFS clients to
696 manipulate POSIX Access Control Lists on files residing on NFS
697 servers. NFS servers enforce POSIX ACLs on local files whether
698 this protocol is available or not.
700 This option enables support in your system's NFS server for the
701 NFSv3 ACL protocol extension allowing NFS clients to manipulate
702 POSIX ACLs on files exported by your system's NFS server. NFS
703 clients which support the Solaris NFSv3 ACL protocol can then
704 access and modify ACLs on your NFS server.
706 To store ACLs on your NFS server, you also need to enable ACL-
707 related CONFIG options for your local file systems of choice.
712 bool "NFS server support for NFS version 4 (EXPERIMENTAL)"
713 depends on NFSD && PROC_FS && EXPERIMENTAL
716 select RPCSEC_GSS_KRB5
718 This option enables support in your system's NFS server for
719 version 4 of the NFS protocol (RFC 3530).
721 To export files using NFSv4, you need to install additional user
722 space programs which can be found in the Linux nfs-utils package,
723 available from http://linux-nfs.org/.
732 depends on NFSD_V3 || NFS_V3
738 config NFS_ACL_SUPPORT
744 depends on NFSD || NFS_FS
753 config SUNRPC_XPRT_RDMA
755 depends on SUNRPC && INFINIBAND && EXPERIMENTAL
756 default SUNRPC && INFINIBAND
758 This option enables an RPC client transport capability that
759 allows the NFS client to mount servers via an RDMA-enabled
762 To compile RPC client RDMA transport support as a module,
763 choose M here: the module will be called xprtrdma.
767 config SUNRPC_REGISTER_V4
768 bool "Register local RPC services via rpcbind v4 (EXPERIMENTAL)"
769 depends on SUNRPC && EXPERIMENTAL
772 Sun added support for registering RPC services at an IPv6
773 address by creating two new versions of the rpcbind protocol
776 This option enables support in the kernel RPC server for
777 registering kernel RPC services via version 4 of the rpcbind
778 protocol. If you enable this option, you must run a portmapper
779 daemon that supports rpcbind protocol version 4.
781 Serving NFS over IPv6 from knfsd (the kernel's NFS server)
782 requires that you enable this option and use a portmapper that
783 supports rpcbind version 4.
785 If unsure, say N to get traditional behavior (register kernel
786 RPC services using only rpcbind version 2). Distributions
787 using the legacy Linux portmapper daemon must say N here.
789 config RPCSEC_GSS_KRB5
790 tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
791 depends on SUNRPC && EXPERIMENTAL
798 Choose Y here to enable Secure RPC using the Kerberos version 5
799 GSS-API mechanism (RFC 1964).
801 Secure RPC calls with Kerberos require an auxiliary user-space
802 daemon which may be found in the Linux nfs-utils package
803 available from http://linux-nfs.org/. In addition, user-space
804 Kerberos support should be installed.
808 config RPCSEC_GSS_SPKM3
809 tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
810 depends on SUNRPC && EXPERIMENTAL
818 Choose Y here to enable Secure RPC using the SPKM3 public key
819 GSS-API mechansim (RFC 2025).
821 Secure RPC calls with SPKM3 require an auxiliary userspace
822 daemon which may be found in the Linux nfs-utils package
823 available from http://linux-nfs.org/.
828 tristate "SMB file system support (OBSOLETE, please use CIFS)"
832 SMB (Server Message Block) is the protocol Windows for Workgroups
833 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
834 files and printers over local networks. Saying Y here allows you to
835 mount their file systems (often called "shares" in this context) and
836 access them just like any other Unix directory. Currently, this
837 works only if the Windows machines use TCP/IP as the underlying
838 transport protocol, and not NetBEUI. For details, read
839 <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
840 available from <http://www.tldp.org/docs.html#howto>.
842 Note: if you just want your box to act as an SMB *server* and make
843 files and printing services available to Windows clients (which need
844 to have a TCP/IP stack), you don't need to say Y here; you can use
845 the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
848 General information about how to connect Linux, Windows machines and
849 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
851 To compile the SMB support as a module, choose M here:
852 the module will be called smbfs. Most people say N, however.
854 config SMB_NLS_DEFAULT
855 bool "Use a default NLS"
858 Enabling this will make smbfs use nls translations by default. You
859 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
860 settings and you need to give the default nls for the SMB server as
861 CONFIG_SMB_NLS_REMOTE.
863 The nls settings can be changed at mount time, if your smbmount
864 supports that, using the codepage and iocharset parameters.
866 smbmount from samba 2.2.0 or later supports this.
868 config SMB_NLS_REMOTE
869 string "Default Remote NLS Option"
870 depends on SMB_NLS_DEFAULT
873 This setting allows you to specify a default value for which
874 codepage the server uses. If this field is left blank no
875 translations will be done by default. The local codepage/charset
876 default to CONFIG_NLS_DEFAULT.
878 The nls settings can be changed at mount time, if your smbmount
879 supports that, using the codepage and iocharset parameters.
881 smbmount from samba 2.2.0 or later supports this.
883 source "fs/cifs/Kconfig"
886 tristate "NCP file system support (to mount NetWare volumes)"
887 depends on IPX!=n || INET
889 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
890 used by Novell NetWare clients to talk to file servers. It is to
891 IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
892 to mount NetWare file server volumes and to access them just like
893 any other Unix directory. For details, please read the file
894 <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
895 the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
897 You do not have to say Y here if you want your Linux box to act as a
898 file *server* for Novell NetWare clients.
900 General information about how to connect Linux, Windows machines and
901 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
903 To compile this as a module, choose M here: the module will be called
904 ncpfs. Say N unless you are connected to a Novell network.
906 source "fs/ncpfs/Kconfig"
909 tristate "Coda file system support (advanced network fs)"
912 Coda is an advanced network file system, similar to NFS in that it
913 enables you to mount file systems of a remote server and access them
914 with regular Unix commands as if they were sitting on your hard
915 disk. Coda has several advantages over NFS: support for
916 disconnected operation (e.g. for laptops), read/write server
917 replication, security model for authentication and encryption,
918 persistent client caches and write back caching.
920 If you say Y here, your Linux box will be able to act as a Coda
921 *client*. You will need user level code as well, both for the
922 client and server. Servers are currently user level, i.e. they need
923 no kernel support. Please read
924 <file:Documentation/filesystems/coda.txt> and check out the Coda
925 home page <http://www.coda.cs.cmu.edu/>.
927 To compile the coda client support as a module, choose M here: the
928 module will be called coda.
931 tristate "Andrew File System support (AFS) (EXPERIMENTAL)"
932 depends on INET && EXPERIMENTAL
935 If you say Y here, you will get an experimental Andrew File System
936 driver. It currently only supports unsecured read-only AFS access.
938 See <file:Documentation/filesystems/afs.txt> for more information.
943 bool "AFS dynamic debugging"
946 Say Y here to make runtime controllable debugging messages appear.
948 See <file:Documentation/filesystems/afs.txt> for more information.
953 tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
954 depends on INET && NET_9P && EXPERIMENTAL
956 If you say Y here, you will get experimental support for
957 Plan 9 resource sharing via the 9P2000 protocol.
959 See <http://v9fs.sf.net> for more information.
963 endif # NETWORK_FILESYSTEMS
966 menu "Partition Types"
968 source "fs/partitions/Kconfig"
973 source "fs/nls/Kconfig"
974 source "fs/dlm/Kconfig"