2 # File system configuration
10 If you say Y here, you will be able to set per user limits for disk
11 usage (also called disk quotas). Currently, it works for the
12 ext2, ext3, and reiserfs file system. You need additional software
13 in order to use quota support (you can download sources from
14 <http://www.sf.net/projects/linuxquota/>). For further details, read
15 the Quota mini-HOWTO, available from
16 <http://www.linuxdoc.org/docs.html#howto>. Probably the quota
17 support is only useful for multi user systems. If unsure, say N.
20 tristate "Old quota format support"
23 This quota format was (is) used by kernels earlier than 2.4.??. If
24 you have quota working and you don't want to convert to new quota
28 tristate "Quota format v2 support"
31 This quota format allows using quotas with 32-bit UIDs/GIDs. If you
32 need this functionality say Y here. Note that you will need latest
33 quota utilities for new quota format with this kernel.
37 depends on XFS_QUOTA || QUOTA
41 tristate "Kernel automounter support"
43 The automounter is a tool to automatically mount remote file systems
44 on demand. This implementation is partially kernel-based to reduce
45 overhead in the already-mounted case; this is unlike the BSD
46 automounter (amd), which is a pure user space daemon.
48 To use the automounter you need the user-space tools from the autofs
49 package; you can find the location in <file:Documentation/Changes>.
50 You also want to answer Y to "NFS file system support", below.
52 If you want to use the newer version of the automounter with more
53 features, say N here and say Y to "Kernel automounter v4 support",
56 If you want to compile this as a module ( = code which can be
57 inserted in and removed from the running kernel whenever you want),
58 say M here and read <file:Documentation/modules.txt>. The module
59 will be called autofs.o.
61 If you are not a part of a fairly large, distributed network, you
62 probably do not need an automounter, and can say N here.
65 tristate "Kernel automounter version 4 support (also supports v3)"
67 The automounter is a tool to automatically mount remote file systems
68 on demand. This implementation is partially kernel-based to reduce
69 overhead in the already-mounted case; this is unlike the BSD
70 automounter (amd), which is a pure user space daemon.
72 To use the automounter you need the user-space tools from
73 <ftp://ftp.kernel.org/pub/linux/daemons/autofs/testing-v4/>; you also
74 want to answer Y to "NFS file system support", below.
76 If you want to compile this as a module ( = code which can be
77 inserted in and removed from the running kernel whenever you want),
78 say M here and read <file:Documentation/modules.txt>. The module
79 will be called autofs4.o. You will need to add "alias autofs
80 autofs4" to your modules configuration file.
82 If you are not a part of a fairly large, distributed network or
83 don't have a laptop which needs to dynamically reconfigure to the
84 local network, you probably do not need an automounter, and can say
88 tristate "Reiserfs support"
90 Stores not just filenames but the files themselves in a balanced
91 tree. Uses journaling.
93 Balanced trees are more efficient than traditional file system
94 architectural foundations.
96 In general, ReiserFS is as fast as ext2, but is very efficient with
97 large directories and small files. Additional patches are needed
98 for NFS and quotas, please see <http://www.reiserfs.org/> for links.
100 It is more easily extended to have features currently found in
101 database and keyword search systems than block allocation based file
102 systems are. The next version will be so extended, and will support
103 plugins consistent with our motto ``It takes more than a license to
104 make source code open.''
106 Read <http://www.reiserfs.org/> to learn more about reiserfs.
108 Sponsored by Threshold Networks, Emusic.com, and Bigstorage.com.
110 If you like it, you can pay us to add new features to it that you
111 need, buy a support contract, or pay us to port it to another OS.
113 config REISERFS_CHECK
114 bool "Enable reiserfs debug mode"
115 depends on REISERFS_FS
117 If you set this to Y, then ReiserFS will perform every check it can
118 possibly imagine of its internal consistency throughout its
119 operation. It will also go substantially slower. More than once we
120 have forgotten that this was on, and then gone despondent over the
121 latest benchmarks.:-) Use of this option allows our team to go all
122 out in checking for consistency when debugging without fear of its
123 effect on end users. If you are on the verge of sending in a bug
124 report, say Y and you might get a useful error message. Almost
125 everyone should say N.
127 config REISERFS_PROC_INFO
128 bool "Stats in /proc/fs/reiserfs"
129 depends on REISERFS_FS
131 Create under /proc/fs/reiserfs a hierarchy of files, displaying
132 various ReiserFS statistics and internal data at the expense of
133 making your kernel or module slightly larger (+8 KB). This also
134 increases the amount of kernel memory required for each mount.
135 Almost everyone but ReiserFS developers and people fine-tuning
136 reiserfs or tracing problems should say N.
139 tristate "ADFS file system support (EXPERIMENTAL)"
140 depends on EXPERIMENTAL
142 The Acorn Disc Filing System is the standard file system of the
143 RiscOS operating system which runs on Acorn's ARM-based Risc PC
144 systems and the Acorn Archimedes range of machines. If you say Y
145 here, Linux will be able to read from ADFS partitions on hard drives
146 and from ADFS-formatted floppy discs. If you also want to be able to
147 write to those devices, say Y to "ADFS write support" below.
149 The ADFS partition should be the first partition (i.e.,
150 /dev/[hs]d?1) on each of your drives. Please read the file
151 <file:Documentation/filesystems/adfs.txt> for further details.
153 This code is also available as a module called adfs.o ( = code which
154 can be inserted in and removed from the running kernel whenever you
155 want). If you want to compile it as a module, say M here and read
156 <file:Documentation/modules.txt>.
161 bool "ADFS write support (DANGEROUS)"
164 If you say Y here, you will be able to write to ADFS partitions on
165 hard drives and ADFS-formatted floppy disks. This is experimental
166 codes, so if you're unsure, say N.
169 tristate "Amiga FFS file system support (EXPERIMENTAL)"
170 depends on EXPERIMENTAL
172 The Fast File System (FFS) is the common file system used on hard
173 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
174 if you want to be able to read and write files from and to an Amiga
175 FFS partition on your hard drive. Amiga floppies however cannot be
176 read with this driver due to an incompatibility of the floppy
177 controller used in an Amiga and the standard floppy controller in
178 PCs and workstations. Read <file:Documentation/filesystems/affs.txt>
179 and <file:fs/affs/Changes>.
181 With this driver you can also mount disk files used by Bernd
182 Schmidt's Un*X Amiga Emulator
183 (<http://www.freiburg.linux.de/~uae/>).
184 If you want to do this, you will also need to say Y or M to "Loop
185 device support", above.
187 This file system is also available as a module ( = code which can be
188 inserted in and removed from the running kernel whenever you want).
189 The module is called affs.o. If you want to compile it as a module,
190 say M here and read <file:Documentation/modules.txt>. If unsure,
194 tristate "Apple Macintosh file system support (EXPERIMENTAL)"
195 depends on EXPERIMENTAL
197 If you say Y here, you will be able to mount Macintosh-formatted
198 floppy disks and hard drive partitions with full read-write access.
199 Please read <file:fs/hfs/HFS.txt> to learn about the available mount
202 This file system support is also available as a module ( = code
203 which can be inserted in and removed from the running kernel
204 whenever you want). The module is called hfs.o. If you want to
205 compile it as a module, say M here and read
206 <file:Documentation/modules.txt>.
209 tristate "BeOS file systemv(BeFS) support (read only) (EXPERIMENTAL)"
210 depends on EXPERIMENTAL
212 The BeOS File System (BeFS) is the native file system of Be, Inc's
213 BeOS. Notable features include support for arbitrary attributes
214 on files and directories, and database-like indices on selected
215 attributes. (Also note that this driver doesn't make those features
216 available at this time). It is a 64 bit filesystem, so it supports
217 extreemly large volumes and files.
219 If you use this filesystem, you should also say Y to at least one
220 of the NLS (native language support) options below.
222 If you don't know what this is about, say N.
224 If you want to compile this as a module ( = code which can be
225 inserted in and removed from the running kernel whenever you want),
226 say M here and read Documentation/modules.txt. The module will be
233 If you say Y here, you can use the 'debug' mount option to enable
234 debugging output from the driver.
237 tristate "BFS file system support (EXPERIMENTAL)"
238 depends on EXPERIMENTAL
240 Boot File System (BFS) is a file system used under SCO UnixWare to
241 allow the bootloader access to the kernel image and other important
242 files during the boot process. It is usually mounted under /stand
243 and corresponds to the slice marked as "STAND" in the UnixWare
244 partition. You should say Y if you want to read or write the files
245 on your /stand slice from within Linux. You then also need to say Y
246 to "UnixWare slices support", below. More information about the BFS
247 file system is contained in the file
248 <file:Documentation/filesystems/bfs.txt>.
250 If you don't know what this is about, say N.
252 If you want to compile this as a module ( = code which can be
253 inserted in and removed from the running kernel whenever you want),
254 say M here and read <file:Documentation/modules.txt>. The module
255 will be called bfs.o. Note that the file system of your root
256 partition (the one containing the directory /) cannot be compiled as
260 tristate "Ext3 journalling file system support"
262 This is the journaling version of the Second extended file system
263 (often called ext3), the de facto standard Linux file system
264 (method to organize files on a storage device) for hard disks.
266 The journaling code included in this driver means you do not have
267 to run e2fsck (file system checker) on your file systems after a
268 crash. The journal keeps track of any changes that were being made
269 at the time the system crashed, and can ensure that your file system
270 is consistent without the need for a lengthy check.
272 Other than adding the journal to the file system, the on-disk format
273 of ext3 is identical to ext2. It is possible to freely switch
274 between using the ext3 driver and the ext2 driver, as long as the
275 file system has been cleanly unmounted, or e2fsck is run on the file
278 To add a journal on an existing ext2 file system or change the
279 behavior of ext3 file systems, you can use the tune2fs utility ("man
280 tune2fs"). To modify attributes of files and directories on ext3
281 file systems, use chattr ("man chattr"). You need to be using
282 e2fsprogs version 1.20 or later in order to create ext3 journals
283 (available at <http://sourceforge.net/projects/e2fsprogs/>).
285 If you want to compile this file system as a module ( = code which
286 can be inserted in and removed from the running kernel whenever you
287 want), say M here and read <file:Documentation/modules.txt>. The
288 module will be called ext3.o. Be aware however that the file system
289 of your root partition (the one containing the directory /) cannot
290 be compiled as a module, and so this may be dangerous.
293 bool "Ext3 extended attributes"
297 Extended attributes are name:value pairs associated with inodes by
298 the kernel or by users (see the attr(5) manual page, or visit
299 <http://acl.bestbits.at/> for details).
303 You need this for POSIX ACL support on ext3.
305 config EXT3_FS_POSIX_ACL
306 bool "Ext3 POSIX Access Control Lists"
307 depends on EXT3_FS_XATTR
309 Posix Access Control Lists (ACLs) support permissions for users and
310 groups beyond the owner/group/world scheme.
312 To learn more about Access Control Lists, visit the Posix ACLs for
313 Linux website <http://acl.bestbits.at/>.
315 If you don't know what Access Control Lists are, say N
317 # CONFIG_JBD could be its own option (even modular), but until there are
318 # other users than ext3, we will simply make it be the same as CONFIG_EXT3_FS
319 # dep_tristate ' Journal Block Device support (JBD for ext3)' CONFIG_JBD $CONFIG_EXT3_FS
324 This is a generic journaling layer for block devices. It is
325 currently used by the ext3 file system, but it could also be used to
326 add journal support to other file systems or block devices such as
329 If you are using the ext3 file system, you need to say Y here. If
330 you are not using ext3 then you will probably want to say N.
332 If you want to compile this device as a module ( = code which can be
333 inserted in and removed from the running kernel whenever you want),
334 say M here and read <file:Documentation/modules.txt>. The module
335 will be called jbd.o. If you are compiling ext3 into the kernel,
336 you cannot compile this code as a module.
339 bool "JBD (ext3) debugging support"
342 If you are using the ext3 journaled file system (or potentially any
343 other file system/device using JBD), this option allows you to
344 enable debugging output while the system is running, in order to
345 help track down any problems you are having. By default the
346 debugging output will be turned off.
348 If you select Y here, then you will be able to turn on debugging
349 with "echo N > /proc/sys/fs/jbd-debug", where N is a number between
350 1 and 5, the higher the number, the more debugging output is
351 generated. To turn debugging off again, do
352 "echo 0 > /proc/sys/fs/jbd-debug".
356 tristate "DOS FAT fs support"
358 If you want to use one of the FAT-based file systems (the MS-DOS,
359 VFAT (Windows 95) and UMSDOS (used to run Linux on top of an
360 ordinary DOS partition) file systems), then you must say Y or M here
361 to include FAT support. You will then be able to mount partitions or
362 diskettes with FAT-based file systems and transparently access the
363 files on them, i.e. MSDOS files will look and behave just like all
366 This FAT support is not a file system in itself, it only provides
367 the foundation for the other file systems. You will have to say Y or
368 M to at least one of "MSDOS fs support" or "VFAT fs support" in
369 order to make use of it.
371 Another way to read and write MSDOS floppies and hard drive
372 partitions from within Linux (but not transparently) is with the
373 mtools ("man mtools") program suite. You don't need to say Y here in
376 If you need to move large files on floppies between a DOS and a
377 Linux box, say Y here, mount the floppy under Linux with an MSDOS
378 file system and use GNU tar's M option. GNU tar is a program
379 available for Unix and DOS ("man tar" or "info tar").
381 It is now also becoming possible to read and write compressed FAT
382 file systems; read <file:Documentation/filesystems/fat_cvf.txt> for
385 The FAT support will enlarge your kernel by about 37 KB. If unsure,
388 If you want to compile this as a module however ( = code which can
389 be inserted in and removed from the running kernel whenever you
390 want), say M here and read <file:Documentation/modules.txt>. The
391 module will be called fat.o. Note that if you compile the FAT
392 support as a module, you cannot compile any of the FAT-based file
393 systems into the kernel -- they will have to be modules as well.
394 The file system of your root partition (the one containing the
395 directory /) cannot be a module, so don't say M here if you intend
396 to use UMSDOS as your root file system.
399 tristate "MSDOS fs support"
402 This allows you to mount MSDOS partitions of your hard drive (unless
403 they are compressed; to access compressed MSDOS partitions under
404 Linux, you can either use the DOS emulator DOSEMU, described in the
405 DOSEMU-HOWTO, available from
406 <http://www.linuxdoc.org/docs.html#howto>, or try dmsdosfs in
407 <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you
408 intend to use dosemu with a non-compressed MSDOS partition, say Y
409 here) and MSDOS floppies. This means that file access becomes
410 transparent, i.e. the MSDOS files look and behave just like all
413 If you want to use UMSDOS, the Unix-like file system on top of a
414 DOS file system, which allows you to run Linux from within a DOS
415 partition without repartitioning, you'll have to say Y or M here.
417 If you have Windows 95 or Windows NT installed on your MSDOS
418 partitions, you should use the VFAT file system (say Y to "VFAT fs
419 support" below), or you will not be able to see the long filenames
420 generated by Windows 95 / Windows NT.
422 This option will enlarge your kernel by about 7 KB. If unsure,
423 answer Y. This will only work if you said Y to "DOS FAT fs support"
424 as well. If you want to compile this as a module however ( = code
425 which can be inserted in and removed from the running kernel
426 whenever you want), say M here and read
427 <file:Documentation/modules.txt>.
428 The module will be called msdos.o.
430 #dep_tristate ' UMSDOS: Unix-like file system on top of standard MSDOS fs' CONFIG_UMSDOS_FS $CONFIG_MSDOS_FS
431 # UMSDOS is temprory broken
435 Say Y here if you want to run Linux from within an existing DOS
436 partition of your hard drive. The advantage of this is that you can
437 get away without repartitioning your hard drive (which often implies
438 backing everything up and restoring afterwards) and hence you're
439 able to quickly try out Linux or show it to your friends; the
440 disadvantage is that Linux becomes susceptible to DOS viruses and
441 that UMSDOS is somewhat slower than ext2fs. Another use of UMSDOS
442 is to write files with long unix filenames to MSDOS floppies; it
443 also allows Unix-style soft-links and owner/permissions of files on
444 MSDOS floppies. You will need a program called umssync in order to
445 make use of UMSDOS; read
446 <file:Documentation/filesystems/umsdos.txt>.
448 To get utilities for initializing/checking UMSDOS file system, or
449 latest patches and/or information, visit the UMSDOS home page at
450 <http://www.voyager.hr/~mnalis/umsdos/>.
452 This option enlarges your kernel by about 28 KB and it only works if
453 you said Y to both "DOS FAT fs support" and "MSDOS fs support"
454 above. If you want to compile this as a module ( = code which can
455 be inserted in and removed from the running kernel whenever you
456 want), say M here and read <file:Documentation/modules.txt>. The
457 module will be called umsdos.o. Note that the file system of your
458 root partition (the one containing the directory /) cannot be a
459 module, so saying M could be dangerous. If unsure, say N.
462 tristate "VFAT (Windows-95) fs support"
465 This option provides support for normal Windows file systems with
466 long filenames. That includes non-compressed FAT-based file systems
467 used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
468 programs from the mtools package.
470 You cannot use the VFAT file system for your Linux root partition
471 (the one containing the directory /); use UMSDOS instead if you
472 want to run Linux from within a DOS partition (i.e. say Y to
473 "Unix like fs on top of std MSDOS fs", below).
475 The VFAT support enlarges your kernel by about 10 KB and it only
476 works if you said Y to the "DOS FAT fs support" above. Please read
477 the file <file:Documentation/filesystems/vfat.txt> for details. If
480 If you want to compile this as a module ( = code which can be
481 inserted in and removed from the running kernel whenever you want),
482 say M here and read <file:Documentation/modules.txt>. The module
483 will be called vfat.o.
486 tristate "EFS file system support (read only) (EXPERIMENTAL)"
487 depends on EXPERIMENTAL
489 EFS is an older file system used for non-ISO9660 CD-ROMs and hard
490 disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
491 uses the XFS file system for hard disk partitions however).
493 This implementation only offers read-only access. If you don't know
494 what all this is about, it's safe to say N. For more information
495 about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
497 If you want to compile the EFS file system support as a module ( =
498 code which can be inserted in and removed from the running kernel
499 whenever you want), say M here and read
500 <file:Documentation/modules.txt>. The module will be called efs.o.
503 tristate "Journalling Flash File System (JFFS) support"
506 JFFS is the Journaling Flash File System developed by Axis
507 Communications in Sweden, aimed at providing a crash/powerdown-safe
508 file system for disk-less embedded devices. Further information is
509 available at (<http://developer.axis.com/software/jffs/>).
511 config JFFS_FS_VERBOSE
512 int "JFFS debugging verbosity (0 = quiet, 3 = noisy)"
516 Determines the verbosity level of the JFFS debugging messages.
519 bool "JFFS stats available in /proc filesystem"
522 Enabling this option will cause statistics from mounted JFFS file systems
523 to be made available to the user in the /proc/fs/jffs/ directory.
526 tristate "Journalling Flash File System v2 (JFFS2) support"
529 JFFS2 is the second generation of the Journalling Flash File System
530 for use on diskless embedded devices. It provides improved wear
531 levelling, compression and support for hard links. You cannot use
532 this on normal block devices, only on 'MTD' devices.
534 Further information should be made available soon at
535 <http://sources.redhat.com/jffs2/>.
537 config JFFS2_FS_DEBUG
538 int "JFFS2 debugging verbosity (0 = quiet, 2 = noisy)"
542 This controls the amount of debugging messages produced by the JFFS2
543 code. Set it to zero for use in production systems. For evaluation,
544 testing and debugging, it's advisable to set it to one. This will
545 enable a few assertions and will print debugging messages at the
546 KERN_DEBUG loglevel, where they won't normally be visible. Level 2
547 is unlikely to be useful - it enables extra debugging in certain
548 areas which at one point needed debugging, but when the bugs were
549 located and fixed, the detailed messages were relegated to level 2.
551 If reporting bugs, please try to have available a full dump of the
552 messages at debug level 1 while the misbehaviour was occurring.
555 bool "JFFS2 support for NAND flash (EXPERIMENTAL)"
556 depends on JFFS2_FS && EXPERIMENTAL
559 tristate "Compressed ROM file system support"
561 Saying Y here includes support for CramFs (Compressed ROM File
562 System). CramFs is designed to be a simple, small, and compressed
563 file system for ROM based embedded systems. CramFs is read-only,
564 limited to 256MB file systems (with 16MB files), and doesn't support
565 16/32 bits uid/gid, hard links and timestamps.
567 See <file:Documentation/filesystems/cramfs.txt> and
568 <file:fs/cramfs/README> for further information.
570 If you want to compile this as a module ( = code which can be
571 inserted in and removed from the running kernel whenever you want),
572 say M here and read <file:Documentation/modules.txt>. The module
573 will be called cramfs.o. Note that the root file system (the one
574 containing the directory /) cannot be compiled as a module.
579 bool "Virtual memory file system support (former shm fs)"
581 Tmpfs is a file system which keeps all files in virtual memory.
583 Everything in tmpfs is temporary in the sense that no files will be
584 created on your hard drive. The files live in memory and swap
585 space. If you unmount a tmpfs instance, everything stored therein is
588 See <file:Documentation/filesystems/tmpfs.txt> for details.
594 Ramfs is a file system which keeps all files in RAM. It allows
595 read and write access.
597 It is more of an programming example than a useable file system. If
598 you need a file system which lives in RAM with limit checking use
601 If you want to compile this as a module ( = code which can be
602 inserted in and removed from the running kernel whenever you want),
603 say M here and read <file:Documentation/modules.txt>. The module
604 will be called ramfs.o.
607 bool "HugeTLB file system support"
608 depends on HUGETLB_PAGE
611 tristate "ISO 9660 CDROM file system support"
613 This is the standard file system used on CD-ROMs. It was previously
614 known as "High Sierra File System" and is called "hsfs" on other
615 Unix systems. The so-called Rock-Ridge extensions which allow for
616 long Unix filenames and symbolic links are also supported by this
617 driver. If you have a CD-ROM drive and want to do more with it than
618 just listen to audio CDs and watch its LEDs, say Y (and read
619 <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO,
620 available from <http://www.linuxdoc.org/docs.html#howto>), thereby
621 enlarging your kernel by about 27 KB; otherwise say N.
623 If you want to compile this as a module ( = code which can be
624 inserted in and removed from the running kernel whenever you want),
625 say M here and read <file:Documentation/modules.txt>. The module
626 will be called isofs.o.
629 bool "Microsoft Joliet CDROM extensions"
630 depends on ISO9660_FS
632 Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system
633 which allows for long filenames in unicode format (unicode is the
634 new 16 bit character code, successor to ASCII, which encodes the
635 characters of almost all languages of the world; see
636 <http://www.unicode.org/> for more information). Say Y here if you
637 want to be able to read Joliet CD-ROMs under Linux.
640 bool "Transparent decompression extension"
641 depends on ISO9660_FS
643 This is a Linux-specific extension to RockRidge which lets you store
644 data in compressed form on a CD-ROM and have it transparently
645 decompressed when the CD-ROM is accessed. See
646 <http://www.kernel.org/pub/linux/utils/fs/zisofs/> for the tools
647 necessary to create such a filesystem. Say Y here if you want to be
648 able to read such compressed CD-ROMs.
651 tristate "JFS filesystem support"
653 This is a port of IBM's Journaled Filesystem . More information is
654 available in the file Documentation/filesystems/jfs.txt.
656 If you do not intend to use the JFS filesystem, say N.
659 bool "JFS POSIX Access Control Lists"
662 Posix Access Control Lists (ACLs) support permissions for users and
663 groups beyond the owner/group/world scheme.
665 To learn more about Access Control Lists, visit the Posix ACLs for
666 Linux website <http://acl.bestbits.at/>.
668 If you don't know what Access Control Lists are, say N
674 If you are experiencing any problems with the JFS filesystem, say
675 Y here. This will result in additional debugging messages to be
676 written to the system log. Under normal circumstances, this
677 results in very little overhead.
679 config JFS_STATISTICS
680 bool "JFS statistics"
683 Enabling this option will cause statistics from the JFS file system
684 to be made available to the user in the /proc/fs/jfs/ directory.
687 tristate "Minix fs support"
689 Minix is a simple operating system used in many classes about OS's.
690 The minix file system (method to organize files on a hard disk
691 partition or a floppy disk) was the original file system for Linux,
692 but has been superseded by the second extended file system ext2fs.
693 You don't want to use the minix file system on your hard disk
694 because of certain built-in restrictions, but it is sometimes found
695 on older Linux floppy disks. This option will enlarge your kernel
696 by about 28 KB. If unsure, say N.
698 If you want to compile this as a module ( = code which can be
699 inserted in and removed from the running kernel whenever you want),
700 say M here and read <file:Documentation/modules.txt>. The module
701 will be called minix.o. Note that the file system of your root
702 partition (the one containing the directory /) cannot be compiled as
706 tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
708 FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
709 file system format. VERITAS VxFS(TM) is the standard file system
710 of SCO UnixWare (and possibly others) and optionally available
711 for Sunsoft Solaris, HP-UX and many other operating systems.
712 Currently only readonly access is supported.
714 NOTE: the file system type as used by mount(1), mount(2) and
715 fstab(5) is 'vxfs' as it describes the file system format, not
718 This file system is also available as a module ( = code which can be
719 inserted in and removed from the running kernel whenever you want).
720 The module is called freevxfs.o. If you want to compile it as a
721 module, say M here and read <file:Documentation/modules.txt>. If
725 tristate "NTFS file system support (read only)"
727 NTFS is the file system of Microsoft Windows NT/2000/XP. For more
728 information see <file:Documentation/filesystems/ntfs.txt>. Saying Y
729 here would allow you to read from NTFS partitions.
731 This file system is also available as a module ( = code which can be
732 inserted in and removed from the running kernel whenever you want).
733 The module will be called ntfs.o. If you want to compile it as a
734 module, say M here and read <file:Documentation/modules.txt>.
736 If you are not using Windows NT/2000/XP in addition to Linux on your
737 computer it is safe to say N.
740 bool "NTFS debugging support"
743 If you are experiencing any problems with the NTFS file system, say
744 Y here. This will result in additional consistency checks to be
745 performed by the driver as well as additional debugging messages to
746 be written to the system log. Note that debugging messages are
747 disabled by default. To enable them, supply the option debug_msgs=1
748 at the kernel command line when booting the kernel or as an option
749 to insmod when loading the ntfs module. Once the driver is active,
750 you can enable debugging messages by doing (as root):
751 echo 1 > /proc/sys/fs/ntfs-debug
752 Replacing the "1" with "0" would disable debug messages.
754 If you leave debugging messages disabled, this results in little
755 overhead, but enabling debug messages results in very significant
756 slowdown of the system.
758 When reporting bugs, please try to have available a full dump of
759 debugging messages while the misbehaviour was occurring.
762 bool "NTFS write support (DANGEROUS)"
763 depends on NTFS_FS && EXPERIMENTAL
765 This enables the experimental write support in the NTFS driver.
767 WARNING: Do not use this option unless you are actively developing
768 NTFS as it is currently guaranteed to be broken and you
769 may lose all your data!
771 It is strongly recommended and perfectly safe to say N here.
774 tristate "OS/2 HPFS file system support"
776 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
777 is the file system used for organizing files on OS/2 hard disk
778 partitions. Say Y if you want to be able to read files from and
779 write files to an OS/2 HPFS partition on your hard drive. OS/2
780 floppies however are in regular MSDOS format, so you don't need this
781 option in order to be able to read them. Read
782 <file:Documentation/filesystems/hpfs.txt>.
784 This file system is also available as a module ( = code which can be
785 inserted in and removed from the running kernel whenever you want).
786 The module is called hpfs.o. If you want to compile it as a module,
787 say M here and read <file:Documentation/modules.txt>. If unsure,
791 bool "/proc file system support"
793 This is a virtual file system providing information about the status
794 of the system. "Virtual" means that it doesn't take up any space on
795 your hard disk: the files are created on the fly by the kernel when
796 you try to access them. Also, you cannot read the files with older
797 version of the program less: you need to use more or cat.
799 It's totally cool; for example, "cat /proc/interrupts" gives
800 information about what the different IRQs are used for at the moment
801 (there is a small number of Interrupt ReQuest lines in your computer
802 that are used by the attached devices to gain the CPU's attention --
803 often a source of trouble if two devices are mistakenly configured
804 to use the same IRQ). The program procinfo to display some
805 information about your system gathered from the /proc file system.
807 Before you can use the /proc file system, it has to be mounted,
808 meaning it has to be given a location in the directory hierarchy.
809 That location should be /proc. A command such as "mount -t proc proc
810 /proc" or the equivalent line in /etc/fstab does the job.
812 The /proc file system is explained in the file
813 <file:Documentation/filesystems/proc.txt> and on the proc(5) manpage
816 This option will enlarge your kernel by about 67 KB. Several
817 programs depend on this, so everyone should say Y here.
820 bool "/dev file system support (EXPERIMENTAL)"
821 depends on EXPERIMENTAL
823 This is support for devfs, a virtual file system (like /proc) which
824 provides the file system interface to device drivers, normally found
825 in /dev. Devfs does not depend on major and minor number
826 allocations. Device drivers register entries in /dev which then
827 appear automatically, which means that the system administrator does
828 not have to create character and block special device files in the
829 /dev directory using the mknod command (or MAKEDEV script) anymore.
831 This is work in progress. If you want to use this, you *must* read
832 the material in <file:Documentation/filesystems/devfs/>, especially
833 the file README there.
838 bool "Automatically mount at boot"
841 This option appears if you have CONFIG_DEVFS_FS enabled. Setting
842 this to 'Y' will make the kernel automatically mount devfs onto /dev
843 when the system is booted, before the init thread is started.
844 You can override this with the "devfs=nomount" boot option.
852 If you say Y here, then the /dev file system code will generate
853 debugging messages. See the file
854 <file:Documentation/filesystems/devfs/boot-options> for more
859 # It compiles as a module for testing only. It should not be used
860 # as a module in general. If we make this "tristate", a bunch of people
861 # who don't know what they are doing turn it on and complain when it
864 bool "/dev/pts file system for Unix98 PTYs"
865 depends on UNIX98_PTYS
867 You should say Y here if you said Y to "Unix98 PTY support" above.
868 You'll then get a virtual file system which can be mounted on
869 /dev/pts with "mount -t devpts". This, together with the pseudo
870 terminal master multiplexer /dev/ptmx, is used for pseudo terminal
871 support as described in The Open Group's Unix98 standard: in order
872 to acquire a pseudo terminal, a process opens /dev/ptmx; the number
873 of the pseudo terminal is then made available to the process and the
874 pseudo terminal slave can be accessed as /dev/pts/<number>. What was
875 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
877 The GNU C library glibc 2.1 contains the requisite support for this
878 mode of operation; you also need client programs that use the Unix98
879 API. Please read <file:Documentation/Changes> for more information
880 about the Unix98 pty devices.
882 Note that the experimental "/dev file system support"
883 (CONFIG_DEVFS_FS) is a more general facility.
886 tristate "QNX4 file system support (read only)"
888 This is the file system used by the real-time operating systems
889 QNX 4 and QNX 6 (the latter is also called QNX RTP).
890 Further information is available at <http://www.qnx.com/>.
891 Say Y if you intend to mount QNX hard disks or floppies.
892 Unless you say Y to "QNX4FS read-write support" below, you will
893 only be able to read these file systems.
895 This file system support is also available as a module ( = code
896 which can be inserted in and removed from the running kernel
897 whenever you want). The module is called qnx4.o. If you want to
898 compile it as a module, say M here and read
899 <file:Documentation/modules.txt>.
901 If you don't know whether you need it, then you don't need it:
905 bool "QNX4FS write support (DANGEROUS)"
906 depends on QNX4FS_FS && EXPERIMENTAL
908 Say Y if you want to test write support for QNX4 file systems.
910 It's currently broken, so for now:
914 tristate "ROM file system support"
916 This is a very small read-only file system mainly intended for
917 initial ram disks of installation disks, but it could be used for
918 other read-only media as well. Read
919 <file:Documentation/filesystems/romfs.txt> for details.
921 This file system support is also available as a module ( = code
922 which can be inserted in and removed from the running kernel
923 whenever you want). The module is called romfs.o. If you want to
924 compile it as a module, say M here and read
925 <file:Documentation/modules.txt>. Note that the file system of your
926 root partition (the one containing the directory /) cannot be a
929 If you don't know whether you need it, then you don't need it:
933 tristate "Second extended fs support"
935 This is the de facto standard Linux file system (method to organize
936 files on a storage device) for hard disks.
938 You want to say Y here, unless you intend to use Linux exclusively
939 from inside a DOS partition using the UMSDOS file system. The
940 advantage of the latter is that you can get away without
941 repartitioning your hard drive (which often implies backing
942 everything up and restoring afterwards); the disadvantage is that
943 Linux becomes susceptible to DOS viruses and that UMSDOS is somewhat
944 slower than ext2fs. Even if you want to run Linux in this fashion,
945 it might be a good idea to have ext2fs around: it enables you to
946 read more floppy disks and facilitates the transition to a *real*
947 Linux partition later. Another (rare) case which doesn't require
948 ext2fs is a diskless Linux box which mounts all files over the
949 network using NFS (in this case it's sufficient to say Y to "NFS
950 file system support" below). Saying Y here will enlarge your kernel
953 The Ext2fs-Undeletion mini-HOWTO, available from
954 <http://www.linuxdoc.org/docs.html#howto>, gives information about
955 how to retrieve deleted files on ext2fs file systems.
957 To change the behavior of ext2 file systems, you can use the tune2fs
958 utility ("man tune2fs"). To modify attributes of files and
959 directories on ext2 file systems, use chattr ("man chattr").
961 Ext2fs partitions can be read from within DOS using the ext2tool
962 command line tool package (available from
963 <ftp://ibiblio.org/pub/Linux/system/filesystems/ext2/>) and from
964 within Windows NT using the ext2nt command line tool package from
965 <ftp://ibiblio.org/pub/Linux/utils/dos/>. Explore2fs is a
966 graphical explorer for ext2fs partitions which runs on Windows 95
967 and Windows NT and includes experimental write support; it is
969 <http://jnewbigin-pc.it.swin.edu.au/Linux/Explore2fs.htm>.
971 If you want to compile this file system as a module ( = code which
972 can be inserted in and removed from the running kernel whenever you
973 want), say M here and read <file:Documentation/modules.txt>. The
974 module will be called ext2.o. Be aware however that the file system
975 of your root partition (the one containing the directory /) cannot
976 be compiled as a module, and so this could be dangerous. Most
977 everyone wants to say Y here.
980 bool "Ext2 extended attributes"
983 Extended attributes are name:value pairs associated with inodes by
984 the kernel or by users (see the attr(5) manual page, or visit
985 <http://acl.bestbits.at/> for details).
989 config EXT2_FS_POSIX_ACL
990 bool "Ext2 POSIX Access Control Lists"
991 depends on EXT2_FS_XATTR
993 Posix Access Control Lists (ACLs) support permissions for users and
994 groups beyond the owner/group/world scheme.
996 To learn more about Access Control Lists, visit the Posix ACLs for
997 Linux website <http://acl.bestbits.at/>.
999 If you don't know what Access Control Lists are, say N
1002 tristate "System V/Xenix/V7/Coherent file system support"
1004 SCO, Xenix and Coherent are commercial Unix systems for Intel
1005 machines, and Version 7 was used on the DEC PDP-11. Saying Y
1006 here would allow you to read from their floppies and hard disk
1009 If you have floppies or hard disk partitions like that, it is likely
1010 that they contain binaries from those other Unix systems; in order
1011 to run these binaries, you will want to install linux-abi which is a
1012 a set of kernel modules that lets you run SCO, Xenix, Wyse,
1013 UnixWare, Dell Unix and System V programs under Linux. It is
1014 available via FTP (user: ftp) from
1015 <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
1016 NOTE: that will work only for binaries from Intel-based systems;
1017 PDP ones will have to wait until somebody ports Linux to -11 ;-)
1019 If you only intend to mount files from some other Unix over the
1020 network using NFS, you don't need the System V file system support
1021 (but you need NFS file system support obviously).
1023 Note that this option is generally not needed for floppies, since a
1024 good portable way to transport files and directories between unixes
1025 (and even other operating systems) is given by the tar program ("man
1026 tar" or preferably "info tar"). Note also that this option has
1027 nothing whatsoever to do with the option "System V IPC". Read about
1028 the System V file system in
1029 <file:Documentation/filesystems/sysv-fs.txt>.
1030 Saying Y here will enlarge your kernel by about 27 KB.
1032 If you want to compile this as a module ( = code which can be
1033 inserted in and removed from the running kernel whenever you want),
1034 say M here and read <file:Documentation/modules.txt>. The module
1035 will be called sysv.o.
1037 If you haven't heard about all of this before, it's safe to say N.
1040 tristate "UDF file system support"
1042 This is the new file system used on some CD-ROMs and DVDs. Say Y if
1043 you intend to mount DVD discs or CDRW's written in packet mode, or
1044 if written to by other UDF utilities, such as DirectCD.
1045 Please read <file:Documentation/filesystems/udf.txt>.
1047 This file system support is also available as a module ( = code
1048 which can be inserted in and removed from the running kernel
1049 whenever you want). The module is called udf.o. If you want to
1050 compile it as a module, say M here and read
1051 <file:Documentation/modules.txt>.
1056 tristate "UFS file system support (read only)"
1058 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
1059 OpenBSD and NeXTstep) use a file system called UFS. Some System V
1060 Unixes can create and mount hard disk partitions and diskettes using
1061 this file system as well. Saying Y here will allow you to read from
1062 these partitions; if you also want to write to them, say Y to the
1063 experimental "UFS file system write support", below. Please read the
1064 file <file:Documentation/filesystems/ufs.txt> for more information.
1066 If you only intend to mount files from some other Unix over the
1067 network using NFS, you don't need the UFS file system support (but
1068 you need NFS file system support obviously).
1070 Note that this option is generally not needed for floppies, since a
1071 good portable way to transport files and directories between unixes
1072 (and even other operating systems) is given by the tar program ("man
1073 tar" or preferably "info tar").
1075 When accessing NeXTstep files, you may need to convert them from the
1076 NeXT character set to the Latin1 character set; use the program
1077 recode ("info recode") for this purpose.
1079 If you want to compile the UFS file system support as a module ( =
1080 code which can be inserted in and removed from the running kernel
1081 whenever you want), say M here and read
1082 <file:Documentation/modules.txt>. The module will be called ufs.o.
1084 If you haven't heard about all of this before, it's safe to say N.
1087 bool "UFS file system write support (DANGEROUS)"
1088 depends on UFS_FS && EXPERIMENTAL
1090 Say Y here if you want to try writing to UFS partitions. This is
1091 experimental, so you should back up your UFS partitions beforehand.
1094 tristate "XFS filesystem support"
1096 XFS is a high performance journaling filesystem which originated
1097 on the SGI IRIX platform. It is completely multi-threaded, can
1098 support large files and large filesystems, extended attributes,
1099 variable block sizes, is extent based, and makes extensive use of
1100 Btrees (directories, extents, free space) to aid both performance
1103 Refer to the documentation at <http://oss.sgi.com/projects/xfs/>
1104 for complete details. This implementation is on-disk compatible
1105 with the IRIX version of XFS.
1107 If you want to compile this file system as a module ( = code which
1108 can be inserted in and removed from the running kernel whenever you
1109 want), say M here and read <file:Documentation/modules.txt>. The
1110 module will be called xfs.o. Be aware, however, that if the file
1111 system of your root partition is compiled as a module, you'll need
1112 to use an initial ramdisk (initrd) to boot.
1115 bool "Realtime support (EXPERIMENTAL)"
1116 depends on XFS_FS && EXPERIMENTAL
1118 If you say Y here you will be able to mount and use XFS filesystems
1119 which contain a realtime subvolume. The realtime subvolume is a
1120 separate area of disk space where only file data is stored. The
1121 realtime subvolume is designed to provide very deterministic
1122 data rates suitable for media streaming applications.
1124 See the xfs man page in section 5 for a bit more information.
1126 This feature is unsupported at this time, is not yet fully
1127 functional, and may cause serious problems.
1132 bool "Quota support"
1135 If you say Y here, you will be able to set limits for disk usage on
1136 a per user and/or a per group basis under XFS. XFS considers quota
1137 information as filesystem metadata and uses journaling to provide a
1138 higher level guarantee of consistency. The on-disk data format for
1139 quota is also compatible with the IRIX version of XFS, allowing a
1140 filesystem to be migrated between Linux and IRIX without any need
1143 If unsure, say N. More comprehensive documentation can be found in
1144 README.quota in the xfsprogs package. XFS quota can be used either
1145 with or without the generic quota support enabled (CONFIG_QUOTA) -
1146 they are completely independent subsystems.
1148 config XFS_POSIX_ACL
1152 Posix Access Control Lists (ACLs) support permissions for users and
1153 groups beyond the owner/group/world scheme.
1155 To learn more about Access Control Lists, visit the Posix ACLs for
1156 Linux website <http://acl.bestbits.at/>.
1158 If you don't know what Access Control Lists are, say N
1161 menu "Network File Systems"
1165 tristate "Coda file system support (advanced network fs)"
1168 Coda is an advanced network file system, similar to NFS in that it
1169 enables you to mount file systems of a remote server and access them
1170 with regular Unix commands as if they were sitting on your hard
1171 disk. Coda has several advantages over NFS: support for
1172 disconnected operation (e.g. for laptops), read/write server
1173 replication, security model for authentication and encryption,
1174 persistent client caches and write back caching.
1176 If you say Y here, your Linux box will be able to act as a Coda
1177 *client*. You will need user level code as well, both for the
1178 client and server. Servers are currently user level, i.e. they need
1179 no kernel support. Please read
1180 <file:Documentation/filesystems/coda.txt> and check out the Coda
1181 home page <http://www.coda.cs.cmu.edu/>.
1183 If you want to compile the coda client support as a module ( = code
1184 which can be inserted in and removed from the running kernel
1185 whenever you want), say M here and read
1186 <file:Documentation/modules.txt>. The module will be called coda.o.
1188 config INTERMEZZO_FS
1189 tristate "InterMezzo file system support (replicating fs) (EXPERIMENTAL)"
1190 depends on INET && EXPERIMENTAL
1192 InterMezzo is a networked file system with disconnected operation
1193 and kernel level write back caching. It is most often used for
1194 replicating potentially large trees or keeping laptop/desktop copies
1197 If you say Y or M your kernel or module will provide InterMezzo
1198 support. You will also need a file server daemon, which you can get
1199 from <http://www.inter-mezzo.org/>.
1202 tristate "NFS file system support"
1205 If you are connected to some other (usually local) Unix computer
1206 (using SLIP, PLIP, PPP or Ethernet) and want to mount files residing
1207 on that computer (the NFS server) using the Network File Sharing
1208 protocol, say Y. "Mounting files" means that the client can access
1209 the files with usual UNIX commands as if they were sitting on the
1210 client's hard disk. For this to work, the server must run the
1211 programs nfsd and mountd (but does not need to have NFS file system
1212 support enabled in its kernel). NFS is explained in the Network
1213 Administrator's Guide, available from
1214 <http://www.linuxdoc.org/docs.html#guide>, on its man page: "man
1215 nfs", and in the NFS-HOWTO.
1217 A superior but less widely used alternative to NFS is provided by
1218 the Coda file system; see "Coda file system support" below.
1220 If you say Y here, you should have said Y to TCP/IP networking also.
1221 This option would enlarge your kernel by about 27 KB.
1223 This file system is also available as a module ( = code which can be
1224 inserted in and removed from the running kernel whenever you want).
1225 The module is called nfs.o. If you want to compile it as a module,
1226 say M here and read <file:Documentation/modules.txt>.
1228 If you are configuring a diskless machine which will mount its root
1229 file system over NFS at boot time, say Y here and to "Kernel
1230 level IP autoconfiguration" above and to "Root file system on NFS"
1231 below. You cannot compile this driver as a module in this case.
1232 There are two packages designed for booting diskless machines over
1233 the net: netboot, available from
1234 <http://ftp1.sourceforge.net/netboot/>, and Etherboot,
1235 available from <http://ftp1.sourceforge.net/etherboot/>.
1237 If you don't know what all this is about, say N.
1240 bool "Provide NFSv3 client support"
1243 Say Y here if you want your NFS client to be able to speak the newer
1244 version 3 of the NFS protocol.
1249 bool "Provide NFSv4 client support (EXPERIMENTAL)"
1250 depends on NFS_FS && EXPERIMENTAL
1252 Say Y here if you want your NFS client to be able to speak the newer
1253 version 4 of the NFS protocol. This feature is experimental, and
1254 should only be used if you are interested in helping to test NFSv4.
1259 bool "Root file system on NFS"
1260 depends on NFS_FS=y && IP_PNP
1262 If you want your Linux box to mount its whole root file system (the
1263 one containing the directory /) from some other computer over the
1264 net via NFS (presumably because your box doesn't have a hard disk),
1265 say Y. Read <file:Documentation/nfsroot.txt> for details. It is
1266 likely that in this case, you also want to say Y to "Kernel level IP
1267 autoconfiguration" so that your box can discover its network address
1270 Most people say N here.
1273 tristate "NFS server support"
1276 If you want your Linux box to act as an NFS *server*, so that other
1277 computers on your local network which support NFS can access certain
1278 directories on your box transparently, you have two options: you can
1279 use the self-contained user space program nfsd, in which case you
1280 should say N here, or you can say Y and use the kernel based NFS
1281 server. The advantage of the kernel based solution is that it is
1284 In either case, you will need support software; the respective
1285 locations are given in the file <file:Documentation/Changes> in the
1288 If you say Y here, you will get support for version 2 of the NFS
1289 protocol (NFSv2). If you also want NFSv3, say Y to the next question
1292 Please read the NFS-HOWTO, available from
1293 <http://www.linuxdoc.org/docs.html#howto>.
1295 The NFS server is also available as a module ( = code which can be
1296 inserted in and removed from the running kernel whenever you want).
1297 The module is called nfsd.o. If you want to compile it as a module,
1298 say M here and read <file:Documentation/modules.txt>. If unsure,
1302 bool "Provide NFSv3 server support"
1305 If you would like to include the NFSv3 server as well as the NFSv2
1306 server, say Y here. If unsure, say Y.
1309 bool "Provide NFSv4 server support (EXPERIMENTAL)"
1310 depends on NFSD_V3 && EXPERIMENTAL
1312 If you would like to include the NFSv4 server as well as the NFSv2
1313 and NFSv3 servers, say Y here. This feature is experimental, and
1314 should only be used if you are interested in helping to test NFSv4.
1318 bool "Provide NFS server over TCP support (EXPERIMENTAL)"
1319 depends on NFSD && EXPERIMENTAL
1321 Enable NFS service over TCP connections. This the officially
1322 still experimental, but seems to work well.
1326 default m if NFS_FS!=y && NFSD!=y && (NFS_FS=m || NFSD=m)
1327 default y if NFS_FS=y || NFSD=y
1331 default m if NFS_FS!=y && NFSD!=y && (NFS_FS=m || NFSD=m)
1332 default y if NFS_FS=y || NFSD=y
1336 depends on NFSD_V3 || NFS_V3
1344 tristate "CIFS support (advanced network filesystem for Samba, Window and other CIFS compliant servers)(EXPERIMENTAL)"
1347 This is the client VFS module for the Common Internet File System
1348 (CIFS) protocol which is the successor to the Server Message Block
1349 (SMB) protocol, the native file sharing mechanism for most early
1350 PC operating systems. CIFS is fully supported by current network
1351 file servers such as Windows 2000 (including Windows NT version 4
1352 and Windows XP) as well by Samba (which provides excellent CIFS
1353 server support for Linux and many other operating systems). For
1354 production systems the smbfs module may be used instead of this
1355 cifs module since smbfs is currently more stable and provides
1356 support for older servers. The intent of this module is to provide the
1357 most advanced network file system function for CIFS compliant servers,
1358 including support for dfs (heirarchical name space), secure per-user
1359 session establishment, safe distributed caching (oplock), optional
1360 packet signing, Unicode and other internationalization improvements, and
1361 optional Winbind (nsswitch) integration. This module is in an early
1362 development stage, so unless you are specifically interested in this
1363 filesystem, just say N.
1366 tristate "SMB file system support (to mount Windows shares etc.)"
1369 SMB (Server Message Block) is the protocol Windows for Workgroups
1370 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
1371 files and printers over local networks. Saying Y here allows you to
1372 mount their file systems (often called "shares" in this context) and
1373 access them just like any other Unix directory. Currently, this
1374 works only if the Windows machines use TCP/IP as the underlying
1375 transport protocol, and not NetBEUI. For details, read
1376 <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
1377 available from <http://www.linuxdoc.org/docs.html#howto>.
1379 Note: if you just want your box to act as an SMB *server* and make
1380 files and printing services available to Windows clients (which need
1381 to have a TCP/IP stack), you don't need to say Y here; you can use
1382 the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
1385 General information about how to connect Linux, Windows machines and
1386 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1388 If you want to compile the SMB support as a module ( = code which
1389 can be inserted in and removed from the running kernel whenever you
1390 want), say M here and read <file:Documentation/modules.txt>. The
1391 module will be called smbfs.o. Most people say N, however.
1393 config SMB_NLS_DEFAULT
1394 bool "Use a default NLS"
1397 Enabling this will make smbfs use nls translations by default. You
1398 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
1399 settings and you need to give the default nls for the SMB server as
1400 CONFIG_SMB_NLS_REMOTE.
1402 The nls settings can be changed at mount time, if your smbmount
1403 supports that, using the codepage and iocharset parameters.
1405 smbmount from samba 2.2.0 or later supports this.
1407 config SMB_NLS_REMOTE
1408 string "Default Remote NLS Option"
1409 depends on SMB_NLS_DEFAULT
1412 This setting allows you to specify a default value for which
1413 codepage the server uses. If this field is left blank no
1414 translations will be done by default. The local codepage/charset
1415 default to CONFIG_NLS_DEFAULT.
1417 The nls settings can be changed at mount time, if your smbmount
1418 supports that, using the codepage and iocharset parameters.
1420 smbmount from samba 2.2.0 or later supports this.
1423 tristate "NCP file system support (to mount NetWare volumes)"
1424 depends on IPX!=n || INET
1426 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
1427 used by Novell NetWare clients to talk to file servers. It is to
1428 IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
1429 to mount NetWare file server volumes and to access them just like
1430 any other Unix directory. For details, please read the file
1431 <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
1432 the IPX-HOWTO from <http://www.linuxdoc.org/docs.html#howto>.
1434 You do not have to say Y here if you want your Linux box to act as a
1435 file *server* for Novell NetWare clients.
1437 General information about how to connect Linux, Windows machines and
1438 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1440 If you want to compile this as a module ( = code which can be
1441 inserted in and removed from the running kernel whenever you want),
1442 say M here and read <file:Documentation/modules.txt>. The module
1443 will be called ncpfs.o. Say N unless you are connected to a Novell
1446 source "fs/ncpfs/Kconfig"
1448 # for fs/nls/Config.in
1450 tristate "Andrew File System support (AFS) (Experimental)"
1451 depends on INET && EXPERIMENTAL
1453 If you say Y here, you will get an experimental Andrew File System
1454 driver. It currently only supports unsecured read-only AFS access.
1456 See Documentation/filesystems/afs.txt for more intormation.
1462 default m if AFS_FS=m
1463 default y if AFS_FS=y
1467 # for fs/nls/Config.in
1473 # Meta block cache for Extended Attributes (ext2/ext3)
1476 depends on EXT2_FS_XATTR || EXT3_FS_XATTR
1477 default y if EXT2_FS=y || EXT3_FS=y
1478 default m if EXT2_FS=m || EXT3_FS=m
1480 # Posix ACL utility routines (for now, only ext2/ext3/jfs)
1482 # NOTE: you can implement Posix ACLs without these helpers (XFS does).
1483 # Never use this symbol for ifdefs.
1487 depends on EXT2_FS_POSIX_ACL || EXT3_FS_POSIX_ACL || JFS_POSIX_ACL
1490 menu "Partition Types"
1492 source "fs/partitions/Kconfig"
1496 source "fs/nls/Kconfig"