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