xref: /openbmc/linux/fs/Kconfig (revision 4f3865fb)
1#
2# File system configuration
3#
4
5menu "File systems"
6
7config EXT2_FS
8	tristate "Second extended fs support"
9	help
10	  Ext2 is a standard Linux file system for hard disks.
11
12	  To compile this file system support as a module, choose M here: the
13	  module will be called ext2.  Be aware however that the file system
14	  of your root partition (the one containing the directory /) cannot
15	  be compiled as a module, and so this could be dangerous.
16
17	  If unsure, say Y.
18
19config EXT2_FS_XATTR
20	bool "Ext2 extended attributes"
21	depends on EXT2_FS
22	help
23	  Extended attributes are name:value pairs associated with inodes by
24	  the kernel or by users (see the attr(5) manual page, or visit
25	  <http://acl.bestbits.at/> for details).
26
27	  If unsure, say N.
28
29config EXT2_FS_POSIX_ACL
30	bool "Ext2 POSIX Access Control Lists"
31	depends on EXT2_FS_XATTR
32	select FS_POSIX_ACL
33	help
34	  Posix Access Control Lists (ACLs) support permissions for users and
35	  groups beyond the owner/group/world scheme.
36
37	  To learn more about Access Control Lists, visit the Posix ACLs for
38	  Linux website <http://acl.bestbits.at/>.
39
40	  If you don't know what Access Control Lists are, say N
41
42config EXT2_FS_SECURITY
43	bool "Ext2 Security Labels"
44	depends on EXT2_FS_XATTR
45	help
46	  Security labels support alternative access control models
47	  implemented by security modules like SELinux.  This option
48	  enables an extended attribute handler for file security
49	  labels in the ext2 filesystem.
50
51	  If you are not using a security module that requires using
52	  extended attributes for file security labels, say N.
53
54config EXT2_FS_XIP
55	bool "Ext2 execute in place support"
56	depends on EXT2_FS
57	help
58	  Execute in place can be used on memory-backed block devices. If you
59	  enable this option, you can select to mount block devices which are
60	  capable of this feature without using the page cache.
61
62	  If you do not use a block device that is capable of using this,
63	  or if unsure, say N.
64
65config FS_XIP
66# execute in place
67	bool
68	depends on EXT2_FS_XIP
69	default y
70
71config EXT3_FS
72	tristate "Ext3 journalling file system support"
73	select JBD
74	help
75	  This is the journaling version of the Second extended file system
76	  (often called ext3), the de facto standard Linux file system
77	  (method to organize files on a storage device) for hard disks.
78
79	  The journaling code included in this driver means you do not have
80	  to run e2fsck (file system checker) on your file systems after a
81	  crash.  The journal keeps track of any changes that were being made
82	  at the time the system crashed, and can ensure that your file system
83	  is consistent without the need for a lengthy check.
84
85	  Other than adding the journal to the file system, the on-disk format
86	  of ext3 is identical to ext2.  It is possible to freely switch
87	  between using the ext3 driver and the ext2 driver, as long as the
88	  file system has been cleanly unmounted, or e2fsck is run on the file
89	  system.
90
91	  To add a journal on an existing ext2 file system or change the
92	  behavior of ext3 file systems, you can use the tune2fs utility ("man
93	  tune2fs").  To modify attributes of files and directories on ext3
94	  file systems, use chattr ("man chattr").  You need to be using
95	  e2fsprogs version 1.20 or later in order to create ext3 journals
96	  (available at <http://sourceforge.net/projects/e2fsprogs/>).
97
98	  To compile this file system support as a module, choose M here: the
99	  module will be called ext3.  Be aware however that the file system
100	  of your root partition (the one containing the directory /) cannot
101	  be compiled as a module, and so this may be dangerous.
102
103config EXT3_FS_XATTR
104	bool "Ext3 extended attributes"
105	depends on EXT3_FS
106	default y
107	help
108	  Extended attributes are name:value pairs associated with inodes by
109	  the kernel or by users (see the attr(5) manual page, or visit
110	  <http://acl.bestbits.at/> for details).
111
112	  If unsure, say N.
113
114	  You need this for POSIX ACL support on ext3.
115
116config EXT3_FS_POSIX_ACL
117	bool "Ext3 POSIX Access Control Lists"
118	depends on EXT3_FS_XATTR
119	select FS_POSIX_ACL
120	help
121	  Posix Access Control Lists (ACLs) support permissions for users and
122	  groups beyond the owner/group/world scheme.
123
124	  To learn more about Access Control Lists, visit the Posix ACLs for
125	  Linux website <http://acl.bestbits.at/>.
126
127	  If you don't know what Access Control Lists are, say N
128
129config EXT3_FS_SECURITY
130	bool "Ext3 Security Labels"
131	depends on EXT3_FS_XATTR
132	help
133	  Security labels support alternative access control models
134	  implemented by security modules like SELinux.  This option
135	  enables an extended attribute handler for file security
136	  labels in the ext3 filesystem.
137
138	  If you are not using a security module that requires using
139	  extended attributes for file security labels, say N.
140
141config JBD
142	tristate
143	help
144	  This is a generic journaling layer for block devices.  It is
145	  currently used by the ext3 and OCFS2 file systems, but it could
146	  also be used to add journal support to other file systems or block
147	  devices such as RAID or LVM.
148
149	  If you are using the ext3 or OCFS2 file systems, you need to
150	  say Y here. If you are not using ext3 OCFS2 then you will probably
151	  want to say N.
152
153	  To compile this device as a module, choose M here: the module will be
154	  called jbd.  If you are compiling ext3 or OCFS2 into the kernel,
155	  you cannot compile this code as a module.
156
157config JBD_DEBUG
158	bool "JBD (ext3) debugging support"
159	depends on JBD
160	help
161	  If you are using the ext3 journaled file system (or potentially any
162	  other file system/device using JBD), this option allows you to
163	  enable debugging output while the system is running, in order to
164	  help track down any problems you are having.  By default the
165	  debugging output will be turned off.
166
167	  If you select Y here, then you will be able to turn on debugging
168	  with "echo N > /proc/sys/fs/jbd-debug", where N is a number between
169	  1 and 5, the higher the number, the more debugging output is
170	  generated.  To turn debugging off again, do
171	  "echo 0 > /proc/sys/fs/jbd-debug".
172
173config FS_MBCACHE
174# Meta block cache for Extended Attributes (ext2/ext3)
175	tristate
176	depends on EXT2_FS_XATTR || EXT3_FS_XATTR
177	default y if EXT2_FS=y || EXT3_FS=y
178	default m if EXT2_FS=m || EXT3_FS=m
179
180config REISERFS_FS
181	tristate "Reiserfs support"
182	help
183	  Stores not just filenames but the files themselves in a balanced
184	  tree.  Uses journaling.
185
186	  Balanced trees are more efficient than traditional file system
187	  architectural foundations.
188
189	  In general, ReiserFS is as fast as ext2, but is very efficient with
190	  large directories and small files.  Additional patches are needed
191	  for NFS and quotas, please see <http://www.namesys.com/> for links.
192
193	  It is more easily extended to have features currently found in
194	  database and keyword search systems than block allocation based file
195	  systems are.  The next version will be so extended, and will support
196	  plugins consistent with our motto ``It takes more than a license to
197	  make source code open.''
198
199	  Read <http://www.namesys.com/> to learn more about reiserfs.
200
201	  Sponsored by Threshold Networks, Emusic.com, and Bigstorage.com.
202
203	  If you like it, you can pay us to add new features to it that you
204	  need, buy a support contract, or pay us to port it to another OS.
205
206config REISERFS_CHECK
207	bool "Enable reiserfs debug mode"
208	depends on REISERFS_FS
209	help
210	  If you set this to Y, then ReiserFS will perform every check it can
211	  possibly imagine of its internal consistency throughout its
212	  operation.  It will also go substantially slower.  More than once we
213	  have forgotten that this was on, and then gone despondent over the
214	  latest benchmarks.:-) Use of this option allows our team to go all
215	  out in checking for consistency when debugging without fear of its
216	  effect on end users.  If you are on the verge of sending in a bug
217	  report, say Y and you might get a useful error message.  Almost
218	  everyone should say N.
219
220config REISERFS_PROC_INFO
221	bool "Stats in /proc/fs/reiserfs"
222	depends on REISERFS_FS
223	help
224	  Create under /proc/fs/reiserfs a hierarchy of files, displaying
225	  various ReiserFS statistics and internal data at the expense of
226	  making your kernel or module slightly larger (+8 KB). This also
227	  increases the amount of kernel memory required for each mount.
228	  Almost everyone but ReiserFS developers and people fine-tuning
229	  reiserfs or tracing problems should say N.
230
231config REISERFS_FS_XATTR
232	bool "ReiserFS extended attributes"
233	depends on REISERFS_FS
234	help
235	  Extended attributes are name:value pairs associated with inodes by
236	  the kernel or by users (see the attr(5) manual page, or visit
237	  <http://acl.bestbits.at/> for details).
238
239	  If unsure, say N.
240
241config REISERFS_FS_POSIX_ACL
242	bool "ReiserFS POSIX Access Control Lists"
243	depends on REISERFS_FS_XATTR
244	select FS_POSIX_ACL
245	help
246	  Posix Access Control Lists (ACLs) support permissions for users and
247	  groups beyond the owner/group/world scheme.
248
249	  To learn more about Access Control Lists, visit the Posix ACLs for
250	  Linux website <http://acl.bestbits.at/>.
251
252	  If you don't know what Access Control Lists are, say N
253
254config REISERFS_FS_SECURITY
255	bool "ReiserFS Security Labels"
256	depends on REISERFS_FS_XATTR
257	help
258	  Security labels support alternative access control models
259	  implemented by security modules like SELinux.  This option
260	  enables an extended attribute handler for file security
261	  labels in the ReiserFS filesystem.
262
263	  If you are not using a security module that requires using
264	  extended attributes for file security labels, say N.
265
266config JFS_FS
267	tristate "JFS filesystem support"
268	select NLS
269	help
270	  This is a port of IBM's Journaled Filesystem .  More information is
271	  available in the file <file:Documentation/filesystems/jfs.txt>.
272
273	  If you do not intend to use the JFS filesystem, say N.
274
275config JFS_POSIX_ACL
276	bool "JFS POSIX Access Control Lists"
277	depends on JFS_FS
278	select FS_POSIX_ACL
279	help
280	  Posix Access Control Lists (ACLs) support permissions for users and
281	  groups beyond the owner/group/world scheme.
282
283	  To learn more about Access Control Lists, visit the Posix ACLs for
284	  Linux website <http://acl.bestbits.at/>.
285
286	  If you don't know what Access Control Lists are, say N
287
288config JFS_SECURITY
289	bool "JFS Security Labels"
290	depends on JFS_FS
291	help
292	  Security labels support alternative access control models
293	  implemented by security modules like SELinux.  This option
294	  enables an extended attribute handler for file security
295	  labels in the jfs filesystem.
296
297	  If you are not using a security module that requires using
298	  extended attributes for file security labels, say N.
299
300config JFS_DEBUG
301	bool "JFS debugging"
302	depends on JFS_FS
303	help
304	  If you are experiencing any problems with the JFS filesystem, say
305	  Y here.  This will result in additional debugging messages to be
306	  written to the system log.  Under normal circumstances, this
307	  results in very little overhead.
308
309config JFS_STATISTICS
310	bool "JFS statistics"
311	depends on JFS_FS
312	help
313	  Enabling this option will cause statistics from the JFS file system
314	  to be made available to the user in the /proc/fs/jfs/ directory.
315
316config FS_POSIX_ACL
317# Posix ACL utility routines (for now, only ext2/ext3/jfs/reiserfs)
318#
319# NOTE: you can implement Posix ACLs without these helpers (XFS does).
320# 	Never use this symbol for ifdefs.
321#
322	bool
323	default n
324
325source "fs/xfs/Kconfig"
326
327config OCFS2_FS
328	tristate "OCFS2 file system support (EXPERIMENTAL)"
329	depends on NET && EXPERIMENTAL
330	select CONFIGFS_FS
331	select JBD
332	select CRC32
333	select INET
334	help
335	  OCFS2 is a general purpose extent based shared disk cluster file
336	  system with many similarities to ext3. It supports 64 bit inode
337	  numbers, and has automatically extending metadata groups which may
338	  also make it attractive for non-clustered use.
339
340	  You'll want to install the ocfs2-tools package in order to at least
341	  get "mount.ocfs2".
342
343	  Project web page:    http://oss.oracle.com/projects/ocfs2
344	  Tools web page:      http://oss.oracle.com/projects/ocfs2-tools
345	  OCFS2 mailing lists: http://oss.oracle.com/projects/ocfs2/mailman/
346
347	  Note: Features which OCFS2 does not support yet:
348	          - extended attributes
349		  - shared writeable mmap
350	          - loopback is supported, but data written will not
351	            be cluster coherent.
352	          - quotas
353	          - cluster aware flock
354	          - Directory change notification (F_NOTIFY)
355	          - Distributed Caching (F_SETLEASE/F_GETLEASE/break_lease)
356	          - POSIX ACLs
357	          - readpages / writepages (not user visible)
358
359config MINIX_FS
360	tristate "Minix fs support"
361	help
362	  Minix is a simple operating system used in many classes about OS's.
363	  The minix file system (method to organize files on a hard disk
364	  partition or a floppy disk) was the original file system for Linux,
365	  but has been superseded by the second extended file system ext2fs.
366	  You don't want to use the minix file system on your hard disk
367	  because of certain built-in restrictions, but it is sometimes found
368	  on older Linux floppy disks.  This option will enlarge your kernel
369	  by about 28 KB. If unsure, say N.
370
371	  To compile this file system support as a module, choose M here: the
372	  module will be called minix.  Note that the file system of your root
373	  partition (the one containing the directory /) cannot be compiled as
374	  a module.
375
376config ROMFS_FS
377	tristate "ROM file system support"
378	---help---
379	  This is a very small read-only file system mainly intended for
380	  initial ram disks of installation disks, but it could be used for
381	  other read-only media as well.  Read
382	  <file:Documentation/filesystems/romfs.txt> for details.
383
384	  To compile this file system support as a module, choose M here: the
385	  module will be called romfs.  Note that the file system of your
386	  root partition (the one containing the directory /) cannot be a
387	  module.
388
389	  If you don't know whether you need it, then you don't need it:
390	  answer N.
391
392config INOTIFY
393	bool "Inotify file change notification support"
394	default y
395	---help---
396	  Say Y here to enable inotify support.  Inotify is a file change
397	  notification system and a replacement for dnotify.  Inotify fixes
398	  numerous shortcomings in dnotify and introduces several new features
399	  including multiple file events, one-shot support, and unmount
400	  notification.
401
402	  For more information, see Documentation/filesystems/inotify.txt
403
404	  If unsure, say Y.
405
406config INOTIFY_USER
407	bool "Inotify support for userspace"
408	depends on INOTIFY
409	default y
410	---help---
411	  Say Y here to enable inotify support for userspace, including the
412	  associated system calls.  Inotify allows monitoring of both files and
413	  directories via a single open fd.  Events are read from the file
414	  descriptor, which is also select()- and poll()-able.
415
416	  For more information, see Documentation/filesystems/inotify.txt
417
418	  If unsure, say Y.
419
420config QUOTA
421	bool "Quota support"
422	help
423	  If you say Y here, you will be able to set per user limits for disk
424	  usage (also called disk quotas). Currently, it works for the
425	  ext2, ext3, and reiserfs file system. ext3 also supports journalled
426	  quotas for which you don't need to run quotacheck(8) after an unclean
427	  shutdown.
428	  For further details, read the Quota mini-HOWTO, available from
429	  <http://www.tldp.org/docs.html#howto>, or the documentation provided
430	  with the quota tools. Probably the quota support is only useful for
431	  multi user systems. If unsure, say N.
432
433config QFMT_V1
434	tristate "Old quota format support"
435	depends on QUOTA
436	help
437	  This quota format was (is) used by kernels earlier than 2.4.22. If
438	  you have quota working and you don't want to convert to new quota
439	  format say Y here.
440
441config QFMT_V2
442	tristate "Quota format v2 support"
443	depends on QUOTA
444	help
445	  This quota format allows using quotas with 32-bit UIDs/GIDs. If you
446	  need this functionality say Y here.
447
448config QUOTACTL
449	bool
450	depends on XFS_QUOTA || QUOTA
451	default y
452
453config DNOTIFY
454	bool "Dnotify support" if EMBEDDED
455	default y
456	help
457	  Dnotify is a directory-based per-fd file change notification system
458	  that uses signals to communicate events to user-space.  There exist
459	  superior alternatives, but some applications may still rely on
460	  dnotify.
461
462	  Because of this, if unsure, say Y.
463
464config AUTOFS_FS
465	tristate "Kernel automounter support"
466	help
467	  The automounter is a tool to automatically mount remote file systems
468	  on demand. This implementation is partially kernel-based to reduce
469	  overhead in the already-mounted case; this is unlike the BSD
470	  automounter (amd), which is a pure user space daemon.
471
472	  To use the automounter you need the user-space tools from the autofs
473	  package; you can find the location in <file:Documentation/Changes>.
474	  You also want to answer Y to "NFS file system support", below.
475
476	  If you want to use the newer version of the automounter with more
477	  features, say N here and say Y to "Kernel automounter v4 support",
478	  below.
479
480	  To compile this support as a module, choose M here: the module will be
481	  called autofs.
482
483	  If you are not a part of a fairly large, distributed network, you
484	  probably do not need an automounter, and can say N here.
485
486config AUTOFS4_FS
487	tristate "Kernel automounter version 4 support (also supports v3)"
488	help
489	  The automounter is a tool to automatically mount remote file systems
490	  on demand. This implementation is partially kernel-based to reduce
491	  overhead in the already-mounted case; this is unlike the BSD
492	  automounter (amd), which is a pure user space daemon.
493
494	  To use the automounter you need the user-space tools from
495	  <ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4/>; you also
496	  want to answer Y to "NFS file system support", below.
497
498	  To compile this support as a module, choose M here: the module will be
499	  called autofs4.  You will need to add "alias autofs autofs4" to your
500	  modules configuration file.
501
502	  If you are not a part of a fairly large, distributed network or
503	  don't have a laptop which needs to dynamically reconfigure to the
504	  local network, you probably do not need an automounter, and can say
505	  N here.
506
507config FUSE_FS
508	tristate "Filesystem in Userspace support"
509	help
510	  With FUSE it is possible to implement a fully functional filesystem
511	  in a userspace program.
512
513	  There's also companion library: libfuse.  This library along with
514	  utilities is available from the FUSE homepage:
515	  <http://fuse.sourceforge.net/>
516
517	  See <file:Documentation/filesystems/fuse.txt> for more information.
518	  See <file:Documentation/Changes> for needed library/utility version.
519
520	  If you want to develop a userspace FS, or if you want to use
521	  a filesystem based on FUSE, answer Y or M.
522
523menu "CD-ROM/DVD Filesystems"
524
525config ISO9660_FS
526	tristate "ISO 9660 CDROM file system support"
527	help
528	  This is the standard file system used on CD-ROMs.  It was previously
529	  known as "High Sierra File System" and is called "hsfs" on other
530	  Unix systems.  The so-called Rock-Ridge extensions which allow for
531	  long Unix filenames and symbolic links are also supported by this
532	  driver.  If you have a CD-ROM drive and want to do more with it than
533	  just listen to audio CDs and watch its LEDs, say Y (and read
534	  <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO,
535	  available from <http://www.tldp.org/docs.html#howto>), thereby
536	  enlarging your kernel by about 27 KB; otherwise say N.
537
538	  To compile this file system support as a module, choose M here: the
539	  module will be called isofs.
540
541config JOLIET
542	bool "Microsoft Joliet CDROM extensions"
543	depends on ISO9660_FS
544	select NLS
545	help
546	  Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system
547	  which allows for long filenames in unicode format (unicode is the
548	  new 16 bit character code, successor to ASCII, which encodes the
549	  characters of almost all languages of the world; see
550	  <http://www.unicode.org/> for more information).  Say Y here if you
551	  want to be able to read Joliet CD-ROMs under Linux.
552
553config ZISOFS
554	bool "Transparent decompression extension"
555	depends on ISO9660_FS
556	select ZLIB_INFLATE
557	help
558	  This is a Linux-specific extension to RockRidge which lets you store
559	  data in compressed form on a CD-ROM and have it transparently
560	  decompressed when the CD-ROM is accessed.  See
561	  <http://www.kernel.org/pub/linux/utils/fs/zisofs/> for the tools
562	  necessary to create such a filesystem.  Say Y here if you want to be
563	  able to read such compressed CD-ROMs.
564
565config ZISOFS_FS
566# for fs/nls/Config.in
567	tristate
568	depends on ZISOFS
569	default ISO9660_FS
570
571config UDF_FS
572	tristate "UDF file system support"
573	help
574	  This is the new file system used on some CD-ROMs and DVDs. Say Y if
575	  you intend to mount DVD discs or CDRW's written in packet mode, or
576	  if written to by other UDF utilities, such as DirectCD.
577	  Please read <file:Documentation/filesystems/udf.txt>.
578
579	  To compile this file system support as a module, choose M here: the
580	  module will be called udf.
581
582	  If unsure, say N.
583
584config UDF_NLS
585	bool
586	default y
587	depends on (UDF_FS=m && NLS) || (UDF_FS=y && NLS=y)
588
589endmenu
590
591menu "DOS/FAT/NT Filesystems"
592
593config FAT_FS
594	tristate
595	select NLS
596	help
597	  If you want to use one of the FAT-based file systems (the MS-DOS and
598	  VFAT (Windows 95) file systems), then you must say Y or M here
599	  to include FAT support. You will then be able to mount partitions or
600	  diskettes with FAT-based file systems and transparently access the
601	  files on them, i.e. MSDOS files will look and behave just like all
602	  other Unix files.
603
604	  This FAT support is not a file system in itself, it only provides
605	  the foundation for the other file systems. You will have to say Y or
606	  M to at least one of "MSDOS fs support" or "VFAT fs support" in
607	  order to make use of it.
608
609	  Another way to read and write MSDOS floppies and hard drive
610	  partitions from within Linux (but not transparently) is with the
611	  mtools ("man mtools") program suite. You don't need to say Y here in
612	  order to do that.
613
614	  If you need to move large files on floppies between a DOS and a
615	  Linux box, say Y here, mount the floppy under Linux with an MSDOS
616	  file system and use GNU tar's M option. GNU tar is a program
617	  available for Unix and DOS ("man tar" or "info tar").
618
619	  It is now also becoming possible to read and write compressed FAT
620	  file systems; read <file:Documentation/filesystems/fat_cvf.txt> for
621	  details.
622
623	  The FAT support will enlarge your kernel by about 37 KB. If unsure,
624	  say Y.
625
626	  To compile this as a module, choose M here: the module will be called
627	  fat.  Note that if you compile the FAT support as a module, you
628	  cannot compile any of the FAT-based file systems into the kernel
629	  -- they will have to be modules as well.
630
631config MSDOS_FS
632	tristate "MSDOS fs support"
633	select FAT_FS
634	help
635	  This allows you to mount MSDOS partitions of your hard drive (unless
636	  they are compressed; to access compressed MSDOS partitions under
637	  Linux, you can either use the DOS emulator DOSEMU, described in the
638	  DOSEMU-HOWTO, available from
639	  <http://www.tldp.org/docs.html#howto>, or try dmsdosfs in
640	  <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you
641	  intend to use dosemu with a non-compressed MSDOS partition, say Y
642	  here) and MSDOS floppies. This means that file access becomes
643	  transparent, i.e. the MSDOS files look and behave just like all
644	  other Unix files.
645
646	  If you have Windows 95 or Windows NT installed on your MSDOS
647	  partitions, you should use the VFAT file system (say Y to "VFAT fs
648	  support" below), or you will not be able to see the long filenames
649	  generated by Windows 95 / Windows NT.
650
651	  This option will enlarge your kernel by about 7 KB. If unsure,
652	  answer Y. This will only work if you said Y to "DOS FAT fs support"
653	  as well. To compile this as a module, choose M here: the module will
654	  be called msdos.
655
656config VFAT_FS
657	tristate "VFAT (Windows-95) fs support"
658	select FAT_FS
659	help
660	  This option provides support for normal Windows file systems with
661	  long filenames.  That includes non-compressed FAT-based file systems
662	  used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
663	  programs from the mtools package.
664
665	  The VFAT support enlarges your kernel by about 10 KB and it only
666	  works if you said Y to the "DOS FAT fs support" above.  Please read
667	  the file <file:Documentation/filesystems/vfat.txt> for details.  If
668	  unsure, say Y.
669
670	  To compile this as a module, choose M here: the module will be called
671	  vfat.
672
673config FAT_DEFAULT_CODEPAGE
674	int "Default codepage for FAT"
675	depends on MSDOS_FS || VFAT_FS
676	default 437
677	help
678	  This option should be set to the codepage of your FAT filesystems.
679	  It can be overridden with the "codepage" mount option.
680	  See <file:Documentation/filesystems/vfat.txt> for more information.
681
682config FAT_DEFAULT_IOCHARSET
683	string "Default iocharset for FAT"
684	depends on VFAT_FS
685	default "iso8859-1"
686	help
687	  Set this to the default input/output character set you'd
688	  like FAT to use. It should probably match the character set
689	  that most of your FAT filesystems use, and can be overridden
690	  with the "iocharset" mount option for FAT filesystems.
691	  Note that "utf8" is not recommended for FAT filesystems.
692	  If unsure, you shouldn't set "utf8" here.
693	  See <file:Documentation/filesystems/vfat.txt> for more information.
694
695config NTFS_FS
696	tristate "NTFS file system support"
697	select NLS
698	help
699	  NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003.
700
701	  Saying Y or M here enables read support.  There is partial, but
702	  safe, write support available.  For write support you must also
703	  say Y to "NTFS write support" below.
704
705	  There are also a number of user-space tools available, called
706	  ntfsprogs.  These include ntfsundelete and ntfsresize, that work
707	  without NTFS support enabled in the kernel.
708
709	  This is a rewrite from scratch of Linux NTFS support and replaced
710	  the old NTFS code starting with Linux 2.5.11.  A backport to
711	  the Linux 2.4 kernel series is separately available as a patch
712	  from the project web site.
713
714	  For more information see <file:Documentation/filesystems/ntfs.txt>
715	  and <http://linux-ntfs.sourceforge.net/>.
716
717	  To compile this file system support as a module, choose M here: the
718	  module will be called ntfs.
719
720	  If you are not using Windows NT, 2000, XP or 2003 in addition to
721	  Linux on your computer it is safe to say N.
722
723config NTFS_DEBUG
724	bool "NTFS debugging support"
725	depends on NTFS_FS
726	help
727	  If you are experiencing any problems with the NTFS file system, say
728	  Y here.  This will result in additional consistency checks to be
729	  performed by the driver as well as additional debugging messages to
730	  be written to the system log.  Note that debugging messages are
731	  disabled by default.  To enable them, supply the option debug_msgs=1
732	  at the kernel command line when booting the kernel or as an option
733	  to insmod when loading the ntfs module.  Once the driver is active,
734	  you can enable debugging messages by doing (as root):
735	  echo 1 > /proc/sys/fs/ntfs-debug
736	  Replacing the "1" with "0" would disable debug messages.
737
738	  If you leave debugging messages disabled, this results in little
739	  overhead, but enabling debug messages results in very significant
740	  slowdown of the system.
741
742	  When reporting bugs, please try to have available a full dump of
743	  debugging messages while the misbehaviour was occurring.
744
745config NTFS_RW
746	bool "NTFS write support"
747	depends on NTFS_FS
748	help
749	  This enables the partial, but safe, write support in the NTFS driver.
750
751	  The only supported operation is overwriting existing files, without
752	  changing the file length.  No file or directory creation, deletion or
753	  renaming is possible.  Note only non-resident files can be written to
754	  so you may find that some very small files (<500 bytes or so) cannot
755	  be written to.
756
757	  While we cannot guarantee that it will not damage any data, we have
758	  so far not received a single report where the driver would have
759	  damaged someones data so we assume it is perfectly safe to use.
760
761	  Note:  While write support is safe in this version (a rewrite from
762	  scratch of the NTFS support), it should be noted that the old NTFS
763	  write support, included in Linux 2.5.10 and before (since 1997),
764	  is not safe.
765
766	  This is currently useful with TopologiLinux.  TopologiLinux is run
767	  on top of any DOS/Microsoft Windows system without partitioning your
768	  hard disk.  Unlike other Linux distributions TopologiLinux does not
769	  need its own partition.  For more information see
770	  <http://topologi-linux.sourceforge.net/>
771
772	  It is perfectly safe to say N here.
773
774endmenu
775
776menu "Pseudo filesystems"
777
778config PROC_FS
779	bool "/proc file system support"
780	help
781	  This is a virtual file system providing information about the status
782	  of the system. "Virtual" means that it doesn't take up any space on
783	  your hard disk: the files are created on the fly by the kernel when
784	  you try to access them. Also, you cannot read the files with older
785	  version of the program less: you need to use more or cat.
786
787	  It's totally cool; for example, "cat /proc/interrupts" gives
788	  information about what the different IRQs are used for at the moment
789	  (there is a small number of Interrupt ReQuest lines in your computer
790	  that are used by the attached devices to gain the CPU's attention --
791	  often a source of trouble if two devices are mistakenly configured
792	  to use the same IRQ). The program procinfo to display some
793	  information about your system gathered from the /proc file system.
794
795	  Before you can use the /proc file system, it has to be mounted,
796	  meaning it has to be given a location in the directory hierarchy.
797	  That location should be /proc. A command such as "mount -t proc proc
798	  /proc" or the equivalent line in /etc/fstab does the job.
799
800	  The /proc file system is explained in the file
801	  <file:Documentation/filesystems/proc.txt> and on the proc(5) manpage
802	  ("man 5 proc").
803
804	  This option will enlarge your kernel by about 67 KB. Several
805	  programs depend on this, so everyone should say Y here.
806
807config PROC_KCORE
808	bool "/proc/kcore support" if !ARM
809	depends on PROC_FS && MMU
810
811config PROC_VMCORE
812        bool "/proc/vmcore support (EXPERIMENTAL)"
813        depends on PROC_FS && EXPERIMENTAL && CRASH_DUMP
814	default y
815        help
816        Exports the dump image of crashed kernel in ELF format.
817
818config SYSFS
819	bool "sysfs file system support" if EMBEDDED
820	default y
821	help
822	The sysfs filesystem is a virtual filesystem that the kernel uses to
823	export internal kernel objects, their attributes, and their
824	relationships to one another.
825
826	Users can use sysfs to ascertain useful information about the running
827	kernel, such as the devices the kernel has discovered on each bus and
828	which driver each is bound to. sysfs can also be used to tune devices
829	and other kernel subsystems.
830
831	Some system agents rely on the information in sysfs to operate.
832	/sbin/hotplug uses device and object attributes in sysfs to assist in
833	delegating policy decisions, like persistantly naming devices.
834
835	sysfs is currently used by the block subsystem to mount the root
836	partition.  If sysfs is disabled you must specify the boot device on
837	the kernel boot command line via its major and minor numbers.  For
838	example, "root=03:01" for /dev/hda1.
839
840	Designers of embedded systems may wish to say N here to conserve space.
841
842config TMPFS
843	bool "Virtual memory file system support (former shm fs)"
844	help
845	  Tmpfs is a file system which keeps all files in virtual memory.
846
847	  Everything in tmpfs is temporary in the sense that no files will be
848	  created on your hard drive. The files live in memory and swap
849	  space. If you unmount a tmpfs instance, everything stored therein is
850	  lost.
851
852	  See <file:Documentation/filesystems/tmpfs.txt> for details.
853
854config HUGETLBFS
855	bool "HugeTLB file system support"
856	depends X86 || IA64 || PPC64 || SPARC64 || SUPERH || BROKEN
857	help
858	  hugetlbfs is a filesystem backing for HugeTLB pages, based on
859	  ramfs. For architectures that support it, say Y here and read
860	  <file:Documentation/vm/hugetlbpage.txt> for details.
861
862	  If unsure, say N.
863
864config HUGETLB_PAGE
865	def_bool HUGETLBFS
866
867config RAMFS
868	bool
869	default y
870	---help---
871	  Ramfs is a file system which keeps all files in RAM. It allows
872	  read and write access.
873
874	  It is more of an programming example than a useable file system.  If
875	  you need a file system which lives in RAM with limit checking use
876	  tmpfs.
877
878	  To compile this as a module, choose M here: the module will be called
879	  ramfs.
880
881config CONFIGFS_FS
882	tristate "Userspace-driven configuration filesystem (EXPERIMENTAL)"
883	depends on SYSFS && EXPERIMENTAL
884	help
885	  configfs is a ram-based filesystem that provides the converse
886	  of sysfs's functionality. Where sysfs is a filesystem-based
887	  view of kernel objects, configfs is a filesystem-based manager
888	  of kernel objects, or config_items.
889
890	  Both sysfs and configfs can and should exist together on the
891	  same system. One is not a replacement for the other.
892
893endmenu
894
895menu "Miscellaneous filesystems"
896
897config ADFS_FS
898	tristate "ADFS file system support (EXPERIMENTAL)"
899	depends on EXPERIMENTAL
900	help
901	  The Acorn Disc Filing System is the standard file system of the
902	  RiscOS operating system which runs on Acorn's ARM-based Risc PC
903	  systems and the Acorn Archimedes range of machines. If you say Y
904	  here, Linux will be able to read from ADFS partitions on hard drives
905	  and from ADFS-formatted floppy discs. If you also want to be able to
906	  write to those devices, say Y to "ADFS write support" below.
907
908	  The ADFS partition should be the first partition (i.e.,
909	  /dev/[hs]d?1) on each of your drives. Please read the file
910	  <file:Documentation/filesystems/adfs.txt> for further details.
911
912	  To compile this code as a module, choose M here: the module will be
913	  called adfs.
914
915	  If unsure, say N.
916
917config ADFS_FS_RW
918	bool "ADFS write support (DANGEROUS)"
919	depends on ADFS_FS
920	help
921	  If you say Y here, you will be able to write to ADFS partitions on
922	  hard drives and ADFS-formatted floppy disks. This is experimental
923	  codes, so if you're unsure, say N.
924
925config AFFS_FS
926	tristate "Amiga FFS file system support (EXPERIMENTAL)"
927	depends on EXPERIMENTAL
928	help
929	  The Fast File System (FFS) is the common file system used on hard
930	  disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20).  Say Y
931	  if you want to be able to read and write files from and to an Amiga
932	  FFS partition on your hard drive.  Amiga floppies however cannot be
933	  read with this driver due to an incompatibility of the floppy
934	  controller used in an Amiga and the standard floppy controller in
935	  PCs and workstations. Read <file:Documentation/filesystems/affs.txt>
936	  and <file:fs/affs/Changes>.
937
938	  With this driver you can also mount disk files used by Bernd
939	  Schmidt's Un*X Amiga Emulator
940	  (<http://www.freiburg.linux.de/~uae/>).
941	  If you want to do this, you will also need to say Y or M to "Loop
942	  device support", above.
943
944	  To compile this file system support as a module, choose M here: the
945	  module will be called affs.  If unsure, say N.
946
947config HFS_FS
948	tristate "Apple Macintosh file system support (EXPERIMENTAL)"
949	depends on EXPERIMENTAL
950	select NLS
951	help
952	  If you say Y here, you will be able to mount Macintosh-formatted
953	  floppy disks and hard drive partitions with full read-write access.
954	  Please read <file:fs/hfs/HFS.txt> to learn about the available mount
955	  options.
956
957	  To compile this file system support as a module, choose M here: the
958	  module will be called hfs.
959
960config HFSPLUS_FS
961	tristate "Apple Extended HFS file system support"
962	select NLS
963	select NLS_UTF8
964	help
965	  If you say Y here, you will be able to mount extended format
966	  Macintosh-formatted hard drive partitions with full read-write access.
967
968	  This file system is often called HFS+ and was introduced with
969	  MacOS 8. It includes all Mac specific filesystem data such as
970	  data forks and creator codes, but it also has several UNIX
971	  style features such as file ownership and permissions.
972
973config BEFS_FS
974	tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)"
975	depends on EXPERIMENTAL
976	select NLS
977	help
978	  The BeOS File System (BeFS) is the native file system of Be, Inc's
979	  BeOS. Notable features include support for arbitrary attributes
980	  on files and directories, and database-like indeces on selected
981	  attributes. (Also note that this driver doesn't make those features
982	  available at this time). It is a 64 bit filesystem, so it supports
983	  extremly large volumes and files.
984
985	  If you use this filesystem, you should also say Y to at least one
986	  of the NLS (native language support) options below.
987
988	  If you don't know what this is about, say N.
989
990	  To compile this as a module, choose M here: the module will be
991	  called befs.
992
993config BEFS_DEBUG
994	bool "Debug BeFS"
995	depends on BEFS_FS
996	help
997	  If you say Y here, you can use the 'debug' mount option to enable
998	  debugging output from the driver.
999
1000config BFS_FS
1001	tristate "BFS file system support (EXPERIMENTAL)"
1002	depends on EXPERIMENTAL
1003	help
1004	  Boot File System (BFS) is a file system used under SCO UnixWare to
1005	  allow the bootloader access to the kernel image and other important
1006	  files during the boot process.  It is usually mounted under /stand
1007	  and corresponds to the slice marked as "STAND" in the UnixWare
1008	  partition.  You should say Y if you want to read or write the files
1009	  on your /stand slice from within Linux.  You then also need to say Y
1010	  to "UnixWare slices support", below.  More information about the BFS
1011	  file system is contained in the file
1012	  <file:Documentation/filesystems/bfs.txt>.
1013
1014	  If you don't know what this is about, say N.
1015
1016	  To compile this as a module, choose M here: the module will be called
1017	  bfs.  Note that the file system of your root partition (the one
1018	  containing the directory /) cannot be compiled as a module.
1019
1020
1021
1022config EFS_FS
1023	tristate "EFS file system support (read only) (EXPERIMENTAL)"
1024	depends on EXPERIMENTAL
1025	help
1026	  EFS is an older file system used for non-ISO9660 CD-ROMs and hard
1027	  disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
1028	  uses the XFS file system for hard disk partitions however).
1029
1030	  This implementation only offers read-only access. If you don't know
1031	  what all this is about, it's safe to say N. For more information
1032	  about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
1033
1034	  To compile the EFS file system support as a module, choose M here: the
1035	  module will be called efs.
1036
1037config JFFS_FS
1038	tristate "Journalling Flash File System (JFFS) support"
1039	depends on MTD
1040	help
1041	  JFFS is the Journaling Flash File System developed by Axis
1042	  Communications in Sweden, aimed at providing a crash/powerdown-safe
1043	  file system for disk-less embedded devices. Further information is
1044	  available at (<http://developer.axis.com/software/jffs/>).
1045
1046config JFFS_FS_VERBOSE
1047	int "JFFS debugging verbosity (0 = quiet, 3 = noisy)"
1048	depends on JFFS_FS
1049	default "0"
1050	help
1051	  Determines the verbosity level of the JFFS debugging messages.
1052
1053config JFFS_PROC_FS
1054	bool "JFFS stats available in /proc filesystem"
1055	depends on JFFS_FS && PROC_FS
1056	help
1057	  Enabling this option will cause statistics from mounted JFFS file systems
1058	  to be made available to the user in the /proc/fs/jffs/ directory.
1059
1060config JFFS2_FS
1061	tristate "Journalling Flash File System v2 (JFFS2) support"
1062	select CRC32
1063	depends on MTD
1064	help
1065	  JFFS2 is the second generation of the Journalling Flash File System
1066	  for use on diskless embedded devices. It provides improved wear
1067	  levelling, compression and support for hard links. You cannot use
1068	  this on normal block devices, only on 'MTD' devices.
1069
1070	  Further information on the design and implementation of JFFS2 is
1071	  available at <http://sources.redhat.com/jffs2/>.
1072
1073config JFFS2_FS_DEBUG
1074	int "JFFS2 debugging verbosity (0 = quiet, 2 = noisy)"
1075	depends on JFFS2_FS
1076	default "0"
1077	help
1078	  This controls the amount of debugging messages produced by the JFFS2
1079	  code. Set it to zero for use in production systems. For evaluation,
1080	  testing and debugging, it's advisable to set it to one. This will
1081	  enable a few assertions and will print debugging messages at the
1082	  KERN_DEBUG loglevel, where they won't normally be visible. Level 2
1083	  is unlikely to be useful - it enables extra debugging in certain
1084	  areas which at one point needed debugging, but when the bugs were
1085	  located and fixed, the detailed messages were relegated to level 2.
1086
1087	  If reporting bugs, please try to have available a full dump of the
1088	  messages at debug level 1 while the misbehaviour was occurring.
1089
1090config JFFS2_FS_WRITEBUFFER
1091	bool "JFFS2 write-buffering support"
1092	depends on JFFS2_FS
1093	default y
1094	help
1095	  This enables the write-buffering support in JFFS2.
1096
1097	  This functionality is required to support JFFS2 on the following
1098	  types of flash devices:
1099	    - NAND flash
1100	    - NOR flash with transparent ECC
1101	    - DataFlash
1102
1103config JFFS2_SUMMARY
1104	bool "JFFS2 summary support (EXPERIMENTAL)"
1105	depends on JFFS2_FS && EXPERIMENTAL
1106	default n
1107	help
1108	  This feature makes it possible to use summary information
1109	  for faster filesystem mount.
1110
1111	  The summary information can be inserted into a filesystem image
1112	  by the utility 'sumtool'.
1113
1114	  If unsure, say 'N'.
1115
1116config JFFS2_FS_XATTR
1117	bool "JFFS2 XATTR support (EXPERIMENTAL)"
1118	depends on JFFS2_FS && EXPERIMENTAL && !JFFS2_FS_WRITEBUFFER
1119	default n
1120	help
1121	  Extended attributes are name:value pairs associated with inodes by
1122	  the kernel or by users (see the attr(5) manual page, or visit
1123	  <http://acl.bestbits.at/> for details).
1124
1125	  If unsure, say N.
1126
1127config JFFS2_FS_POSIX_ACL
1128	bool "JFFS2 POSIX Access Control Lists"
1129	depends on JFFS2_FS_XATTR
1130	default y
1131	select FS_POSIX_ACL
1132	help
1133	  Posix Access Control Lists (ACLs) support permissions for users and
1134	  groups beyond the owner/group/world scheme.
1135
1136	  To learn more about Access Control Lists, visit the Posix ACLs for
1137	  Linux website <http://acl.bestbits.at/>.
1138
1139	  If you don't know what Access Control Lists are, say N
1140
1141config JFFS2_FS_SECURITY
1142	bool "JFFS2 Security Labels"
1143	depends on JFFS2_FS_XATTR
1144	default y
1145	help
1146	  Security labels support alternative access control models
1147	  implemented by security modules like SELinux.  This option
1148	  enables an extended attribute handler for file security
1149	  labels in the jffs2 filesystem.
1150
1151	  If you are not using a security module that requires using
1152	  extended attributes for file security labels, say N.
1153
1154config JFFS2_COMPRESSION_OPTIONS
1155	bool "Advanced compression options for JFFS2"
1156	depends on JFFS2_FS
1157	default n
1158	help
1159	  Enabling this option allows you to explicitly choose which
1160	  compression modules, if any, are enabled in JFFS2. Removing
1161	  compressors and mean you cannot read existing file systems,
1162	  and enabling experimental compressors can mean that you
1163	  write a file system which cannot be read by a standard kernel.
1164
1165	  If unsure, you should _definitely_ say 'N'.
1166
1167config JFFS2_ZLIB
1168	bool "JFFS2 ZLIB compression support" if JFFS2_COMPRESSION_OPTIONS
1169	select ZLIB_INFLATE
1170	select ZLIB_DEFLATE
1171	depends on JFFS2_FS
1172	default y
1173        help
1174          Zlib is designed to be a free, general-purpose, legally unencumbered,
1175          lossless data-compression library for use on virtually any computer
1176          hardware and operating system. See <http://www.gzip.org/zlib/> for
1177          further information.
1178
1179          Say 'Y' if unsure.
1180
1181config JFFS2_RTIME
1182	bool "JFFS2 RTIME compression support" if JFFS2_COMPRESSION_OPTIONS
1183	depends on JFFS2_FS
1184	default y
1185        help
1186          Rtime does manage to recompress already-compressed data. Say 'Y' if unsure.
1187
1188config JFFS2_RUBIN
1189	bool "JFFS2 RUBIN compression support" if JFFS2_COMPRESSION_OPTIONS
1190	depends on JFFS2_FS
1191	default n
1192        help
1193          RUBINMIPS and DYNRUBIN compressors. Say 'N' if unsure.
1194
1195choice
1196        prompt "JFFS2 default compression mode" if JFFS2_COMPRESSION_OPTIONS
1197        default JFFS2_CMODE_PRIORITY
1198        depends on JFFS2_FS
1199        help
1200          You can set here the default compression mode of JFFS2 from
1201          the available compression modes. Don't touch if unsure.
1202
1203config JFFS2_CMODE_NONE
1204        bool "no compression"
1205        help
1206          Uses no compression.
1207
1208config JFFS2_CMODE_PRIORITY
1209        bool "priority"
1210        help
1211          Tries the compressors in a predefinied order and chooses the first
1212          successful one.
1213
1214config JFFS2_CMODE_SIZE
1215        bool "size (EXPERIMENTAL)"
1216        help
1217          Tries all compressors and chooses the one which has the smallest
1218          result.
1219
1220endchoice
1221
1222config CRAMFS
1223	tristate "Compressed ROM file system support (cramfs)"
1224	select ZLIB_INFLATE
1225	help
1226	  Saying Y here includes support for CramFs (Compressed ROM File
1227	  System).  CramFs is designed to be a simple, small, and compressed
1228	  file system for ROM based embedded systems.  CramFs is read-only,
1229	  limited to 256MB file systems (with 16MB files), and doesn't support
1230	  16/32 bits uid/gid, hard links and timestamps.
1231
1232	  See <file:Documentation/filesystems/cramfs.txt> and
1233	  <file:fs/cramfs/README> for further information.
1234
1235	  To compile this as a module, choose M here: the module will be called
1236	  cramfs.  Note that the root file system (the one containing the
1237	  directory /) cannot be compiled as a module.
1238
1239	  If unsure, say N.
1240
1241config VXFS_FS
1242	tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
1243	help
1244	  FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
1245	  file system format.  VERITAS VxFS(TM) is the standard file system
1246	  of SCO UnixWare (and possibly others) and optionally available
1247	  for Sunsoft Solaris, HP-UX and many other operating systems.
1248	  Currently only readonly access is supported.
1249
1250	  NOTE: the file system type as used by mount(1), mount(2) and
1251	  fstab(5) is 'vxfs' as it describes the file system format, not
1252	  the actual driver.
1253
1254	  To compile this as a module, choose M here: the module will be
1255	  called freevxfs.  If unsure, say N.
1256
1257
1258config HPFS_FS
1259	tristate "OS/2 HPFS file system support"
1260	help
1261	  OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
1262	  is the file system used for organizing files on OS/2 hard disk
1263	  partitions. Say Y if you want to be able to read files from and
1264	  write files to an OS/2 HPFS partition on your hard drive. OS/2
1265	  floppies however are in regular MSDOS format, so you don't need this
1266	  option in order to be able to read them. Read
1267	  <file:Documentation/filesystems/hpfs.txt>.
1268
1269	  To compile this file system support as a module, choose M here: the
1270	  module will be called hpfs.  If unsure, say N.
1271
1272
1273
1274config QNX4FS_FS
1275	tristate "QNX4 file system support (read only)"
1276	help
1277	  This is the file system used by the real-time operating systems
1278	  QNX 4 and QNX 6 (the latter is also called QNX RTP).
1279	  Further information is available at <http://www.qnx.com/>.
1280	  Say Y if you intend to mount QNX hard disks or floppies.
1281	  Unless you say Y to "QNX4FS read-write support" below, you will
1282	  only be able to read these file systems.
1283
1284	  To compile this file system support as a module, choose M here: the
1285	  module will be called qnx4.
1286
1287	  If you don't know whether you need it, then you don't need it:
1288	  answer N.
1289
1290config QNX4FS_RW
1291	bool "QNX4FS write support (DANGEROUS)"
1292	depends on QNX4FS_FS && EXPERIMENTAL && BROKEN
1293	help
1294	  Say Y if you want to test write support for QNX4 file systems.
1295
1296	  It's currently broken, so for now:
1297	  answer N.
1298
1299
1300
1301config SYSV_FS
1302	tristate "System V/Xenix/V7/Coherent file system support"
1303	help
1304	  SCO, Xenix and Coherent are commercial Unix systems for Intel
1305	  machines, and Version 7 was used on the DEC PDP-11. Saying Y
1306	  here would allow you to read from their floppies and hard disk
1307	  partitions.
1308
1309	  If you have floppies or hard disk partitions like that, it is likely
1310	  that they contain binaries from those other Unix systems; in order
1311	  to run these binaries, you will want to install linux-abi which is a
1312	  a set of kernel modules that lets you run SCO, Xenix, Wyse,
1313	  UnixWare, Dell Unix and System V programs under Linux.  It is
1314	  available via FTP (user: ftp) from
1315	  <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
1316	  NOTE: that will work only for binaries from Intel-based systems;
1317	  PDP ones will have to wait until somebody ports Linux to -11 ;-)
1318
1319	  If you only intend to mount files from some other Unix over the
1320	  network using NFS, you don't need the System V file system support
1321	  (but you need NFS file system support obviously).
1322
1323	  Note that this option is generally not needed for floppies, since a
1324	  good portable way to transport files and directories between unixes
1325	  (and even other operating systems) is given by the tar program ("man
1326	  tar" or preferably "info tar").  Note also that this option has
1327	  nothing whatsoever to do with the option "System V IPC". Read about
1328	  the System V file system in
1329	  <file:Documentation/filesystems/sysv-fs.txt>.
1330	  Saying Y here will enlarge your kernel by about 27 KB.
1331
1332	  To compile this as a module, choose M here: the module will be called
1333	  sysv.
1334
1335	  If you haven't heard about all of this before, it's safe to say N.
1336
1337
1338
1339config UFS_FS
1340	tristate "UFS file system support (read only)"
1341	help
1342	  BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
1343	  OpenBSD and NeXTstep) use a file system called UFS. Some System V
1344	  Unixes can create and mount hard disk partitions and diskettes using
1345	  this file system as well. Saying Y here will allow you to read from
1346	  these partitions; if you also want to write to them, say Y to the
1347	  experimental "UFS file system write support", below. Please read the
1348	  file <file:Documentation/filesystems/ufs.txt> for more information.
1349
1350          The recently released UFS2 variant (used in FreeBSD 5.x) is
1351          READ-ONLY supported.
1352
1353	  If you only intend to mount files from some other Unix over the
1354	  network using NFS, you don't need the UFS file system support (but
1355	  you need NFS file system support obviously).
1356
1357	  Note that this option is generally not needed for floppies, since a
1358	  good portable way to transport files and directories between unixes
1359	  (and even other operating systems) is given by the tar program ("man
1360	  tar" or preferably "info tar").
1361
1362	  When accessing NeXTstep files, you may need to convert them from the
1363	  NeXT character set to the Latin1 character set; use the program
1364	  recode ("info recode") for this purpose.
1365
1366	  To compile the UFS file system support as a module, choose M here: the
1367	  module will be called ufs.
1368
1369	  If you haven't heard about all of this before, it's safe to say N.
1370
1371config UFS_FS_WRITE
1372	bool "UFS file system write support (DANGEROUS)"
1373	depends on UFS_FS && EXPERIMENTAL && BROKEN
1374	help
1375	  Say Y here if you want to try writing to UFS partitions. This is
1376	  experimental, so you should back up your UFS partitions beforehand.
1377
1378endmenu
1379
1380menu "Network File Systems"
1381	depends on NET
1382
1383config NFS_FS
1384	tristate "NFS file system support"
1385	depends on INET
1386	select LOCKD
1387	select SUNRPC
1388	select NFS_ACL_SUPPORT if NFS_V3_ACL
1389	help
1390	  If you are connected to some other (usually local) Unix computer
1391	  (using SLIP, PLIP, PPP or Ethernet) and want to mount files residing
1392	  on that computer (the NFS server) using the Network File Sharing
1393	  protocol, say Y. "Mounting files" means that the client can access
1394	  the files with usual UNIX commands as if they were sitting on the
1395	  client's hard disk. For this to work, the server must run the
1396	  programs nfsd and mountd (but does not need to have NFS file system
1397	  support enabled in its kernel). NFS is explained in the Network
1398	  Administrator's Guide, available from
1399	  <http://www.tldp.org/docs.html#guide>, on its man page: "man
1400	  nfs", and in the NFS-HOWTO.
1401
1402	  A superior but less widely used alternative to NFS is provided by
1403	  the Coda file system; see "Coda file system support" below.
1404
1405	  If you say Y here, you should have said Y to TCP/IP networking also.
1406	  This option would enlarge your kernel by about 27 KB.
1407
1408	  To compile this file system support as a module, choose M here: the
1409	  module will be called nfs.
1410
1411	  If you are configuring a diskless machine which will mount its root
1412	  file system over NFS at boot time, say Y here and to "Kernel
1413	  level IP autoconfiguration" above and to "Root file system on NFS"
1414	  below. You cannot compile this driver as a module in this case.
1415	  There are two packages designed for booting diskless machines over
1416	  the net: netboot, available from
1417	  <http://ftp1.sourceforge.net/netboot/>, and Etherboot,
1418	  available from <http://ftp1.sourceforge.net/etherboot/>.
1419
1420	  If you don't know what all this is about, say N.
1421
1422config NFS_V3
1423	bool "Provide NFSv3 client support"
1424	depends on NFS_FS
1425	help
1426	  Say Y here if you want your NFS client to be able to speak version
1427	  3 of the NFS protocol.
1428
1429	  If unsure, say Y.
1430
1431config NFS_V3_ACL
1432	bool "Provide client support for the NFSv3 ACL protocol extension"
1433	depends on NFS_V3
1434	help
1435	  Implement the NFSv3 ACL protocol extension for manipulating POSIX
1436	  Access Control Lists.  The server should also be compiled with
1437	  the NFSv3 ACL protocol extension; see the CONFIG_NFSD_V3_ACL option.
1438
1439	  If unsure, say N.
1440
1441config NFS_V4
1442	bool "Provide NFSv4 client support (EXPERIMENTAL)"
1443	depends on NFS_FS && EXPERIMENTAL
1444	select RPCSEC_GSS_KRB5
1445	help
1446	  Say Y here if you want your NFS client to be able to speak the newer
1447	  version 4 of the NFS protocol.
1448
1449	  Note: Requires auxiliary userspace daemons which may be found on
1450		http://www.citi.umich.edu/projects/nfsv4/
1451
1452	  If unsure, say N.
1453
1454config NFS_DIRECTIO
1455	bool "Allow direct I/O on NFS files (EXPERIMENTAL)"
1456	depends on NFS_FS && EXPERIMENTAL
1457	help
1458	  This option enables applications to perform uncached I/O on files
1459	  in NFS file systems using the O_DIRECT open() flag.  When O_DIRECT
1460	  is set for a file, its data is not cached in the system's page
1461	  cache.  Data is moved to and from user-level application buffers
1462	  directly.  Unlike local disk-based file systems, NFS O_DIRECT has
1463	  no alignment restrictions.
1464
1465	  Unless your program is designed to use O_DIRECT properly, you are
1466	  much better off allowing the NFS client to manage data caching for
1467	  you.  Misusing O_DIRECT can cause poor server performance or network
1468	  storms.  This kernel build option defaults OFF to avoid exposing
1469	  system administrators unwittingly to a potentially hazardous
1470	  feature.
1471
1472	  For more details on NFS O_DIRECT, see fs/nfs/direct.c.
1473
1474	  If unsure, say N.  This reduces the size of the NFS client, and
1475	  causes open() to return EINVAL if a file residing in NFS is
1476	  opened with the O_DIRECT flag.
1477
1478config NFSD
1479	tristate "NFS server support"
1480	depends on INET
1481	select LOCKD
1482	select SUNRPC
1483	select EXPORTFS
1484	select NFS_ACL_SUPPORT if NFSD_V3_ACL || NFSD_V2_ACL
1485	help
1486	  If you want your Linux box to act as an NFS *server*, so that other
1487	  computers on your local network which support NFS can access certain
1488	  directories on your box transparently, you have two options: you can
1489	  use the self-contained user space program nfsd, in which case you
1490	  should say N here, or you can say Y and use the kernel based NFS
1491	  server. The advantage of the kernel based solution is that it is
1492	  faster.
1493
1494	  In either case, you will need support software; the respective
1495	  locations are given in the file <file:Documentation/Changes> in the
1496	  NFS section.
1497
1498	  If you say Y here, you will get support for version 2 of the NFS
1499	  protocol (NFSv2). If you also want NFSv3, say Y to the next question
1500	  as well.
1501
1502	  Please read the NFS-HOWTO, available from
1503	  <http://www.tldp.org/docs.html#howto>.
1504
1505	  To compile the NFS server support as a module, choose M here: the
1506	  module will be called nfsd.  If unsure, say N.
1507
1508config NFSD_V2_ACL
1509	bool
1510	depends on NFSD
1511
1512config NFSD_V3
1513	bool "Provide NFSv3 server support"
1514	depends on NFSD
1515	help
1516	  If you would like to include the NFSv3 server as well as the NFSv2
1517	  server, say Y here.  If unsure, say Y.
1518
1519config NFSD_V3_ACL
1520	bool "Provide server support for the NFSv3 ACL protocol extension"
1521	depends on NFSD_V3
1522	select NFSD_V2_ACL
1523	help
1524	  Implement the NFSv3 ACL protocol extension for manipulating POSIX
1525	  Access Control Lists on exported file systems. NFS clients should
1526	  be compiled with the NFSv3 ACL protocol extension; see the
1527	  CONFIG_NFS_V3_ACL option.  If unsure, say N.
1528
1529config NFSD_V4
1530	bool "Provide NFSv4 server support (EXPERIMENTAL)"
1531	depends on NFSD_V3 && EXPERIMENTAL
1532	select NFSD_TCP
1533	select CRYPTO_MD5
1534	select CRYPTO
1535	select FS_POSIX_ACL
1536	help
1537	  If you would like to include the NFSv4 server as well as the NFSv2
1538	  and NFSv3 servers, say Y here.  This feature is experimental, and
1539	  should only be used if you are interested in helping to test NFSv4.
1540	  If unsure, say N.
1541
1542config NFSD_TCP
1543	bool "Provide NFS server over TCP support"
1544	depends on NFSD
1545	default y
1546	help
1547	  If you want your NFS server to support TCP connections, say Y here.
1548	  TCP connections usually perform better than the default UDP when
1549	  the network is lossy or congested.  If unsure, say Y.
1550
1551config ROOT_NFS
1552	bool "Root file system on NFS"
1553	depends on NFS_FS=y && IP_PNP
1554	help
1555	  If you want your Linux box to mount its whole root file system (the
1556	  one containing the directory /) from some other computer over the
1557	  net via NFS (presumably because your box doesn't have a hard disk),
1558	  say Y. Read <file:Documentation/nfsroot.txt> for details. It is
1559	  likely that in this case, you also want to say Y to "Kernel level IP
1560	  autoconfiguration" so that your box can discover its network address
1561	  at boot time.
1562
1563	  Most people say N here.
1564
1565config LOCKD
1566	tristate
1567
1568config LOCKD_V4
1569	bool
1570	depends on NFSD_V3 || NFS_V3
1571	default y
1572
1573config EXPORTFS
1574	tristate
1575
1576config NFS_ACL_SUPPORT
1577	tristate
1578	select FS_POSIX_ACL
1579
1580config NFS_COMMON
1581	bool
1582	depends on NFSD || NFS_FS
1583	default y
1584
1585config SUNRPC
1586	tristate
1587
1588config SUNRPC_GSS
1589	tristate
1590
1591config RPCSEC_GSS_KRB5
1592	tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
1593	depends on SUNRPC && EXPERIMENTAL
1594	select SUNRPC_GSS
1595	select CRYPTO
1596	select CRYPTO_MD5
1597	select CRYPTO_DES
1598	help
1599	  Provides for secure RPC calls by means of a gss-api
1600	  mechanism based on Kerberos V5. This is required for
1601	  NFSv4.
1602
1603	  Note: Requires an auxiliary userspace daemon which may be found on
1604		http://www.citi.umich.edu/projects/nfsv4/
1605
1606	  If unsure, say N.
1607
1608config RPCSEC_GSS_SPKM3
1609	tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
1610	depends on SUNRPC && EXPERIMENTAL
1611	select SUNRPC_GSS
1612	select CRYPTO
1613	select CRYPTO_MD5
1614	select CRYPTO_DES
1615	select CRYPTO_CAST5
1616	help
1617	  Provides for secure RPC calls by means of a gss-api
1618	  mechanism based on the SPKM3 public-key mechanism.
1619
1620	  Note: Requires an auxiliary userspace daemon which may be found on
1621	  	http://www.citi.umich.edu/projects/nfsv4/
1622
1623	  If unsure, say N.
1624
1625config SMB_FS
1626	tristate "SMB file system support (to mount Windows shares etc.)"
1627	depends on INET
1628	select NLS
1629	help
1630	  SMB (Server Message Block) is the protocol Windows for Workgroups
1631	  (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
1632	  files and printers over local networks.  Saying Y here allows you to
1633	  mount their file systems (often called "shares" in this context) and
1634	  access them just like any other Unix directory.  Currently, this
1635	  works only if the Windows machines use TCP/IP as the underlying
1636	  transport protocol, and not NetBEUI.  For details, read
1637	  <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
1638	  available from <http://www.tldp.org/docs.html#howto>.
1639
1640	  Note: if you just want your box to act as an SMB *server* and make
1641	  files and printing services available to Windows clients (which need
1642	  to have a TCP/IP stack), you don't need to say Y here; you can use
1643	  the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
1644	  for that.
1645
1646	  General information about how to connect Linux, Windows machines and
1647	  Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1648
1649	  To compile the SMB support as a module, choose M here: the module will
1650	  be called smbfs.  Most people say N, however.
1651
1652config SMB_NLS_DEFAULT
1653	bool "Use a default NLS"
1654	depends on SMB_FS
1655	help
1656	  Enabling this will make smbfs use nls translations by default. You
1657	  need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
1658	  settings and you need to give the default nls for the SMB server as
1659	  CONFIG_SMB_NLS_REMOTE.
1660
1661	  The nls settings can be changed at mount time, if your smbmount
1662	  supports that, using the codepage and iocharset parameters.
1663
1664	  smbmount from samba 2.2.0 or later supports this.
1665
1666config SMB_NLS_REMOTE
1667	string "Default Remote NLS Option"
1668	depends on SMB_NLS_DEFAULT
1669	default "cp437"
1670	help
1671	  This setting allows you to specify a default value for which
1672	  codepage the server uses. If this field is left blank no
1673	  translations will be done by default. The local codepage/charset
1674	  default to CONFIG_NLS_DEFAULT.
1675
1676	  The nls settings can be changed at mount time, if your smbmount
1677	  supports that, using the codepage and iocharset parameters.
1678
1679	  smbmount from samba 2.2.0 or later supports this.
1680
1681config CIFS
1682	tristate "CIFS support (advanced network filesystem for Samba, Window and other CIFS compliant servers)"
1683	depends on INET
1684	select NLS
1685	help
1686	  This is the client VFS module for the Common Internet File System
1687	  (CIFS) protocol which is the successor to the Server Message Block
1688	  (SMB) protocol, the native file sharing mechanism for most early
1689	  PC operating systems.  The CIFS protocol is fully supported by
1690	  file servers such as Windows 2000 (including Windows 2003, NT 4
1691	  and Windows XP) as well by Samba (which provides excellent CIFS
1692	  server support for Linux and many other operating systems). Limited
1693	  support for Windows ME and similar servers is provided as well.
1694	  You must use the smbfs client filesystem to access older SMB servers
1695	  such as OS/2 and DOS.
1696
1697	  The intent of the cifs module is to provide an advanced
1698	  network file system client for mounting to CIFS compliant servers,
1699	  including support for dfs (hierarchical name space), secure per-user
1700	  session establishment, safe distributed caching (oplock), optional
1701	  packet signing, Unicode and other internationalization improvements,
1702	  and optional Winbind (nsswitch) integration. You do not need to enable
1703	  cifs if running only a (Samba) server. It is possible to enable both
1704	  smbfs and cifs (e.g. if you are using CIFS for accessing Windows 2003
1705	  and Samba 3 servers, and smbfs for accessing old servers). If you need
1706	  to mount to Samba or Windows from this machine, say Y.
1707
1708config CIFS_STATS
1709        bool "CIFS statistics"
1710        depends on CIFS
1711        help
1712          Enabling this option will cause statistics for each server share
1713	  mounted by the cifs client to be displayed in /proc/fs/cifs/Stats
1714
1715config CIFS_STATS2
1716	bool "CIFS extended statistics"
1717	depends on CIFS_STATS
1718	help
1719	  Enabling this option will allow more detailed statistics on SMB
1720	  request timing to be displayed in /proc/fs/cifs/DebugData and also
1721	  allow optional logging of slow responses to dmesg (depending on the
1722	  value of /proc/fs/cifs/cifsFYI, see fs/cifs/README for more details).
1723	  These additional statistics may have a minor effect on performance
1724	  and memory utilization.
1725
1726	  Unless you are a developer or are doing network performance analysis
1727	  or tuning, say N.
1728
1729config CIFS_XATTR
1730        bool "CIFS extended attributes"
1731        depends on CIFS
1732        help
1733          Extended attributes are name:value pairs associated with inodes by
1734          the kernel or by users (see the attr(5) manual page, or visit
1735          <http://acl.bestbits.at/> for details).  CIFS maps the name of
1736          extended attributes beginning with the user namespace prefix
1737          to SMB/CIFS EAs. EAs are stored on Windows servers without the
1738          user namespace prefix, but their names are seen by Linux cifs clients
1739          prefaced by the user namespace prefix. The system namespace
1740          (used by some filesystems to store ACLs) is not supported at
1741          this time.
1742
1743          If unsure, say N.
1744
1745config CIFS_POSIX
1746        bool "CIFS POSIX Extensions"
1747        depends on CIFS_XATTR
1748        help
1749          Enabling this option will cause the cifs client to attempt to
1750	  negotiate a newer dialect with servers, such as Samba 3.0.5
1751	  or later, that optionally can handle more POSIX like (rather
1752	  than Windows like) file behavior.  It also enables
1753	  support for POSIX ACLs (getfacl and setfacl) to servers
1754	  (such as Samba 3.10 and later) which can negotiate
1755	  CIFS POSIX ACL support.  If unsure, say N.
1756
1757config CIFS_EXPERIMENTAL
1758	  bool "CIFS Experimental Features (EXPERIMENTAL)"
1759	  depends on CIFS && EXPERIMENTAL
1760	  help
1761	    Enables cifs features under testing. These features are
1762	    experimental and currently include support for writepages
1763	    (multipage writebehind performance improvements) and directory
1764	    change notification ie fcntl(F_DNOTIFY) as well as some security
1765	    improvements.  Some also depend on setting at runtime the
1766	    pseudo-file /proc/fs/cifs/Experimental (which is disabled by
1767	    default). See the file fs/cifs/README for more details.
1768
1769	    If unsure, say N.
1770
1771config CIFS_UPCALL
1772	  bool "CIFS Kerberos/SPNEGO advanced session setup (EXPERIMENTAL)"
1773	  depends on CIFS_EXPERIMENTAL
1774	  select CONNECTOR
1775	  help
1776	    Enables an upcall mechanism for CIFS which will be used to contact
1777	    userspace helper utilities to provide SPNEGO packaged Kerberos
1778	    tickets which are needed to mount to certain secure servers
1779	    (for which more secure Kerberos authentication is required). If
1780	    unsure, say N.
1781
1782config NCP_FS
1783	tristate "NCP file system support (to mount NetWare volumes)"
1784	depends on IPX!=n || INET
1785	help
1786	  NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
1787	  used by Novell NetWare clients to talk to file servers.  It is to
1788	  IPX what NFS is to TCP/IP, if that helps.  Saying Y here allows you
1789	  to mount NetWare file server volumes and to access them just like
1790	  any other Unix directory.  For details, please read the file
1791	  <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
1792	  the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
1793
1794	  You do not have to say Y here if you want your Linux box to act as a
1795	  file *server* for Novell NetWare clients.
1796
1797	  General information about how to connect Linux, Windows machines and
1798	  Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
1799
1800	  To compile this as a module, choose M here: the module will be called
1801	  ncpfs.  Say N unless you are connected to a Novell network.
1802
1803source "fs/ncpfs/Kconfig"
1804
1805config CODA_FS
1806	tristate "Coda file system support (advanced network fs)"
1807	depends on INET
1808	help
1809	  Coda is an advanced network file system, similar to NFS in that it
1810	  enables you to mount file systems of a remote server and access them
1811	  with regular Unix commands as if they were sitting on your hard
1812	  disk.  Coda has several advantages over NFS: support for
1813	  disconnected operation (e.g. for laptops), read/write server
1814	  replication, security model for authentication and encryption,
1815	  persistent client caches and write back caching.
1816
1817	  If you say Y here, your Linux box will be able to act as a Coda
1818	  *client*.  You will need user level code as well, both for the
1819	  client and server.  Servers are currently user level, i.e. they need
1820	  no kernel support.  Please read
1821	  <file:Documentation/filesystems/coda.txt> and check out the Coda
1822	  home page <http://www.coda.cs.cmu.edu/>.
1823
1824	  To compile the coda client support as a module, choose M here: the
1825	  module will be called coda.
1826
1827config CODA_FS_OLD_API
1828	bool "Use 96-bit Coda file identifiers"
1829	depends on CODA_FS
1830	help
1831	  A new kernel-userspace API had to be introduced for Coda v6.0
1832	  to support larger 128-bit file identifiers as needed by the
1833	  new realms implementation.
1834
1835	  However this new API is not backward compatible with older
1836	  clients. If you really need to run the old Coda userspace
1837	  cache manager then say Y.
1838
1839	  For most cases you probably want to say N.
1840
1841config AFS_FS
1842# for fs/nls/Config.in
1843	tristate "Andrew File System support (AFS) (Experimental)"
1844	depends on INET && EXPERIMENTAL
1845	select RXRPC
1846	help
1847	  If you say Y here, you will get an experimental Andrew File System
1848	  driver. It currently only supports unsecured read-only AFS access.
1849
1850	  See <file:Documentation/filesystems/afs.txt> for more intormation.
1851
1852	  If unsure, say N.
1853
1854config RXRPC
1855	tristate
1856
1857config 9P_FS
1858	tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)"
1859	depends on INET && EXPERIMENTAL
1860	help
1861	  If you say Y here, you will get experimental support for
1862	  Plan 9 resource sharing via the 9P2000 protocol.
1863
1864	  See <http://v9fs.sf.net> for more information.
1865
1866	  If unsure, say N.
1867
1868endmenu
1869
1870menu "Partition Types"
1871
1872source "fs/partitions/Kconfig"
1873
1874endmenu
1875
1876source "fs/nls/Kconfig"
1877
1878endmenu
1879
1880