Commit | Line | Data |
---|---|---|
1da177e4 LT |
1 | # |
2 | # File system configuration | |
3 | # | |
4 | ||
5 | menu "File systems" | |
6 | ||
9361401e DH |
7 | if BLOCK |
8 | ||
6da0b38f AD |
9 | source "fs/ext2/Kconfig" |
10 | source "fs/ext3/Kconfig" | |
11 | source "fs/ext4/Kconfig" | |
6d79125b CO |
12 | |
13 | config FS_XIP | |
14 | # execute in place | |
15 | bool | |
16 | depends on EXT2_FS_XIP | |
17 | default y | |
18 | ||
6da0b38f AD |
19 | source "fs/jbd/Kconfig" |
20 | source "fs/jbd2/Kconfig" | |
dab291af | 21 | |
1da177e4 | 22 | config FS_MBCACHE |
02ea2104 | 23 | # Meta block cache for Extended Attributes (ext2/ext3/ext4) |
1da177e4 | 24 | tristate |
2c512397 AB |
25 | default y if EXT2_FS=y && EXT2_FS_XATTR |
26 | default y if EXT3_FS=y && EXT3_FS_XATTR | |
27 | default y if EXT4_FS=y && EXT4_FS_XATTR | |
28 | default m if EXT2_FS_XATTR || EXT3_FS_XATTR || EXT4_FS_XATTR | |
1da177e4 | 29 | |
b16ecfe2 | 30 | source "fs/reiserfs/Kconfig" |
f5c77969 | 31 | source "fs/jfs/Kconfig" |
1da177e4 LT |
32 | |
33 | config FS_POSIX_ACL | |
89206955 | 34 | # Posix ACL utility routines (for now, only ext2/ext3/jfs/reiserfs/nfs4) |
1da177e4 LT |
35 | # |
36 | # NOTE: you can implement Posix ACLs without these helpers (XFS does). | |
37 | # Never use this symbol for ifdefs. | |
38 | # | |
39 | bool | |
b84c2157 | 40 | default n |
1da177e4 | 41 | |
bfcd17a6 TP |
42 | config FILE_LOCKING |
43 | bool "Enable POSIX file locking API" if EMBEDDED | |
44 | default y | |
45 | help | |
46 | This option enables standard file locking support, required | |
47 | for filesystems like NFS and for the flock() system | |
48 | call. Disabling this option saves about 11k. | |
49 | ||
1da177e4 | 50 | source "fs/xfs/Kconfig" |
f7825dcf | 51 | source "fs/gfs2/Kconfig" |
2fe4371d | 52 | source "fs/ocfs2/Kconfig" |
a68979b8 | 53 | |
60582d1e CM |
54 | config BTRFS_FS |
55 | tristate "Btrfs filesystem (EXPERIMENTAL) Unstable disk format" | |
56 | depends on EXPERIMENTAL | |
57 | select LIBCRC32C | |
c8b97818 CM |
58 | select ZLIB_INFLATE |
59 | select ZLIB_DEFLATE | |
60582d1e CM |
60 | help |
61 | Btrfs is a new filesystem with extents, writable snapshotting, | |
62 | support for multiple devices and many more features. | |
63 | ||
64 | Btrfs is highly experimental, and THE DISK FORMAT IS NOT YET | |
65 | FINALIZED. You should say N here unless you are interested in | |
66 | testing Btrfs with non-critical data. | |
67 | ||
68 | To compile this file system support as a module, choose M here. The | |
69 | module will be called btrfs. | |
70 | ||
71 | If unsure, say N. | |
72 | ||
25fad945 | 73 | endif # BLOCK |
1da177e4 | 74 | |
272eb014 | 75 | source "fs/notify/Kconfig" |
0eeca283 | 76 | |
1da177e4 LT |
77 | config QUOTA |
78 | bool "Quota support" | |
79 | help | |
80 | If you say Y here, you will be able to set per user limits for disk | |
81 | usage (also called disk quotas). Currently, it works for the | |
82 | ext2, ext3, and reiserfs file system. ext3 also supports journalled | |
83 | quotas for which you don't need to run quotacheck(8) after an unclean | |
919532a5 AB |
84 | shutdown. |
85 | For further details, read the Quota mini-HOWTO, available from | |
1da177e4 LT |
86 | <http://www.tldp.org/docs.html#howto>, or the documentation provided |
87 | with the quota tools. Probably the quota support is only useful for | |
88 | multi user systems. If unsure, say N. | |
89 | ||
8e893469 JK |
90 | config QUOTA_NETLINK_INTERFACE |
91 | bool "Report quota messages through netlink interface" | |
92 | depends on QUOTA && NET | |
93 | help | |
94 | If you say Y here, quota warnings (about exceeding softlimit, reaching | |
95 | hardlimit, etc.) will be reported through netlink interface. If unsure, | |
96 | say Y. | |
97 | ||
98 | config PRINT_QUOTA_WARNING | |
99 | bool "Print quota warnings to console (OBSOLETE)" | |
100 | depends on QUOTA | |
101 | default y | |
102 | help | |
103 | If you say Y here, quota warnings (about exceeding softlimit, reaching | |
104 | hardlimit, etc.) will be printed to the process' controlling terminal. | |
105 | Note that this behavior is currently deprecated and may go away in | |
106 | future. Please use notification via netlink socket instead. | |
107 | ||
1ccd14b9 JK |
108 | # Generic support for tree structured quota files. Seleted when needed. |
109 | config QUOTA_TREE | |
110 | tristate | |
111 | ||
1da177e4 LT |
112 | config QFMT_V1 |
113 | tristate "Old quota format support" | |
114 | depends on QUOTA | |
115 | help | |
116 | This quota format was (is) used by kernels earlier than 2.4.22. If | |
117 | you have quota working and you don't want to convert to new quota | |
118 | format say Y here. | |
119 | ||
120 | config QFMT_V2 | |
121 | tristate "Quota format v2 support" | |
122 | depends on QUOTA | |
1ccd14b9 | 123 | select QUOTA_TREE |
1da177e4 LT |
124 | help |
125 | This quota format allows using quotas with 32-bit UIDs/GIDs. If you | |
919532a5 | 126 | need this functionality say Y here. |
1da177e4 LT |
127 | |
128 | config QUOTACTL | |
129 | bool | |
130 | depends on XFS_QUOTA || QUOTA | |
131 | default y | |
132 | ||
1da177e4 LT |
133 | config AUTOFS_FS |
134 | tristate "Kernel automounter support" | |
135 | help | |
136 | The automounter is a tool to automatically mount remote file systems | |
137 | on demand. This implementation is partially kernel-based to reduce | |
138 | overhead in the already-mounted case; this is unlike the BSD | |
139 | automounter (amd), which is a pure user space daemon. | |
140 | ||
141 | To use the automounter you need the user-space tools from the autofs | |
142 | package; you can find the location in <file:Documentation/Changes>. | |
143 | You also want to answer Y to "NFS file system support", below. | |
144 | ||
145 | If you want to use the newer version of the automounter with more | |
146 | features, say N here and say Y to "Kernel automounter v4 support", | |
147 | below. | |
148 | ||
149 | To compile this support as a module, choose M here: the module will be | |
150 | called autofs. | |
151 | ||
152 | If you are not a part of a fairly large, distributed network, you | |
153 | probably do not need an automounter, and can say N here. | |
154 | ||
155 | config AUTOFS4_FS | |
156 | tristate "Kernel automounter version 4 support (also supports v3)" | |
157 | help | |
158 | The automounter is a tool to automatically mount remote file systems | |
159 | on demand. This implementation is partially kernel-based to reduce | |
160 | overhead in the already-mounted case; this is unlike the BSD | |
161 | automounter (amd), which is a pure user space daemon. | |
162 | ||
163 | To use the automounter you need the user-space tools from | |
164 | <ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4/>; you also | |
165 | want to answer Y to "NFS file system support", below. | |
166 | ||
167 | To compile this support as a module, choose M here: the module will be | |
168 | called autofs4. You will need to add "alias autofs autofs4" to your | |
169 | modules configuration file. | |
170 | ||
171 | If you are not a part of a fairly large, distributed network or | |
172 | don't have a laptop which needs to dynamically reconfigure to the | |
173 | local network, you probably do not need an automounter, and can say | |
174 | N here. | |
175 | ||
04578f17 | 176 | config FUSE_FS |
37194d07 | 177 | tristate "FUSE (Filesystem in Userspace) support" |
04578f17 MS |
178 | help |
179 | With FUSE it is possible to implement a fully functional filesystem | |
180 | in a userspace program. | |
181 | ||
182 | There's also companion library: libfuse. This library along with | |
183 | utilities is available from the FUSE homepage: | |
184 | <http://fuse.sourceforge.net/> | |
185 | ||
909021ea MS |
186 | See <file:Documentation/filesystems/fuse.txt> for more information. |
187 | See <file:Documentation/Changes> for needed library/utility version. | |
188 | ||
04578f17 MS |
189 | If you want to develop a userspace FS, or if you want to use |
190 | a filesystem based on FUSE, answer Y or M. | |
191 | ||
f2fbc6c2 RD |
192 | config GENERIC_ACL |
193 | bool | |
194 | select FS_POSIX_ACL | |
195 | ||
9361401e | 196 | if BLOCK |
1da177e4 LT |
197 | menu "CD-ROM/DVD Filesystems" |
198 | ||
199 | config ISO9660_FS | |
200 | tristate "ISO 9660 CDROM file system support" | |
201 | help | |
202 | This is the standard file system used on CD-ROMs. It was previously | |
203 | known as "High Sierra File System" and is called "hsfs" on other | |
204 | Unix systems. The so-called Rock-Ridge extensions which allow for | |
205 | long Unix filenames and symbolic links are also supported by this | |
206 | driver. If you have a CD-ROM drive and want to do more with it than | |
207 | just listen to audio CDs and watch its LEDs, say Y (and read | |
208 | <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO, | |
209 | available from <http://www.tldp.org/docs.html#howto>), thereby | |
210 | enlarging your kernel by about 27 KB; otherwise say N. | |
211 | ||
212 | To compile this file system support as a module, choose M here: the | |
213 | module will be called isofs. | |
214 | ||
215 | config JOLIET | |
216 | bool "Microsoft Joliet CDROM extensions" | |
217 | depends on ISO9660_FS | |
218 | select NLS | |
219 | help | |
220 | Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system | |
221 | which allows for long filenames in unicode format (unicode is the | |
222 | new 16 bit character code, successor to ASCII, which encodes the | |
223 | characters of almost all languages of the world; see | |
224 | <http://www.unicode.org/> for more information). Say Y here if you | |
225 | want to be able to read Joliet CD-ROMs under Linux. | |
226 | ||
227 | config ZISOFS | |
228 | bool "Transparent decompression extension" | |
229 | depends on ISO9660_FS | |
230 | select ZLIB_INFLATE | |
231 | help | |
232 | This is a Linux-specific extension to RockRidge which lets you store | |
233 | data in compressed form on a CD-ROM and have it transparently | |
234 | decompressed when the CD-ROM is accessed. See | |
235 | <http://www.kernel.org/pub/linux/utils/fs/zisofs/> for the tools | |
236 | necessary to create such a filesystem. Say Y here if you want to be | |
237 | able to read such compressed CD-ROMs. | |
238 | ||
1da177e4 LT |
239 | config UDF_FS |
240 | tristate "UDF file system support" | |
f845fced | 241 | select CRC_ITU_T |
1da177e4 LT |
242 | help |
243 | This is the new file system used on some CD-ROMs and DVDs. Say Y if | |
244 | you intend to mount DVD discs or CDRW's written in packet mode, or | |
245 | if written to by other UDF utilities, such as DirectCD. | |
246 | Please read <file:Documentation/filesystems/udf.txt>. | |
247 | ||
248 | To compile this file system support as a module, choose M here: the | |
249 | module will be called udf. | |
250 | ||
251 | If unsure, say N. | |
252 | ||
253 | config UDF_NLS | |
254 | bool | |
255 | default y | |
256 | depends on (UDF_FS=m && NLS) || (UDF_FS=y && NLS=y) | |
257 | ||
258 | endmenu | |
25fad945 | 259 | endif # BLOCK |
1da177e4 | 260 | |
9361401e | 261 | if BLOCK |
1da177e4 LT |
262 | menu "DOS/FAT/NT Filesystems" |
263 | ||
264 | config FAT_FS | |
265 | tristate | |
266 | select NLS | |
267 | help | |
268 | If you want to use one of the FAT-based file systems (the MS-DOS and | |
269 | VFAT (Windows 95) file systems), then you must say Y or M here | |
270 | to include FAT support. You will then be able to mount partitions or | |
271 | diskettes with FAT-based file systems and transparently access the | |
272 | files on them, i.e. MSDOS files will look and behave just like all | |
273 | other Unix files. | |
274 | ||
275 | This FAT support is not a file system in itself, it only provides | |
276 | the foundation for the other file systems. You will have to say Y or | |
277 | M to at least one of "MSDOS fs support" or "VFAT fs support" in | |
278 | order to make use of it. | |
279 | ||
280 | Another way to read and write MSDOS floppies and hard drive | |
281 | partitions from within Linux (but not transparently) is with the | |
282 | mtools ("man mtools") program suite. You don't need to say Y here in | |
283 | order to do that. | |
284 | ||
285 | If you need to move large files on floppies between a DOS and a | |
286 | Linux box, say Y here, mount the floppy under Linux with an MSDOS | |
287 | file system and use GNU tar's M option. GNU tar is a program | |
288 | available for Unix and DOS ("man tar" or "info tar"). | |
289 | ||
1da177e4 LT |
290 | The FAT support will enlarge your kernel by about 37 KB. If unsure, |
291 | say Y. | |
292 | ||
293 | To compile this as a module, choose M here: the module will be called | |
294 | fat. Note that if you compile the FAT support as a module, you | |
295 | cannot compile any of the FAT-based file systems into the kernel | |
296 | -- they will have to be modules as well. | |
297 | ||
298 | config MSDOS_FS | |
299 | tristate "MSDOS fs support" | |
300 | select FAT_FS | |
301 | help | |
302 | This allows you to mount MSDOS partitions of your hard drive (unless | |
303 | they are compressed; to access compressed MSDOS partitions under | |
304 | Linux, you can either use the DOS emulator DOSEMU, described in the | |
305 | DOSEMU-HOWTO, available from | |
306 | <http://www.tldp.org/docs.html#howto>, or try dmsdosfs in | |
307 | <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you | |
308 | intend to use dosemu with a non-compressed MSDOS partition, say Y | |
309 | here) and MSDOS floppies. This means that file access becomes | |
310 | transparent, i.e. the MSDOS files look and behave just like all | |
311 | other Unix files. | |
312 | ||
313 | If you have Windows 95 or Windows NT installed on your MSDOS | |
314 | partitions, you should use the VFAT file system (say Y to "VFAT fs | |
315 | support" below), or you will not be able to see the long filenames | |
316 | generated by Windows 95 / Windows NT. | |
317 | ||
318 | This option will enlarge your kernel by about 7 KB. If unsure, | |
319 | answer Y. This will only work if you said Y to "DOS FAT fs support" | |
320 | as well. To compile this as a module, choose M here: the module will | |
321 | be called msdos. | |
322 | ||
323 | config VFAT_FS | |
324 | tristate "VFAT (Windows-95) fs support" | |
325 | select FAT_FS | |
326 | help | |
327 | This option provides support for normal Windows file systems with | |
328 | long filenames. That includes non-compressed FAT-based file systems | |
329 | used by Windows 95, Windows 98, Windows NT 4.0, and the Unix | |
330 | programs from the mtools package. | |
331 | ||
332 | The VFAT support enlarges your kernel by about 10 KB and it only | |
333 | works if you said Y to the "DOS FAT fs support" above. Please read | |
334 | the file <file:Documentation/filesystems/vfat.txt> for details. If | |
335 | unsure, say Y. | |
336 | ||
337 | To compile this as a module, choose M here: the module will be called | |
338 | vfat. | |
339 | ||
340 | config FAT_DEFAULT_CODEPAGE | |
341 | int "Default codepage for FAT" | |
342 | depends on MSDOS_FS || VFAT_FS | |
343 | default 437 | |
344 | help | |
345 | This option should be set to the codepage of your FAT filesystems. | |
346 | It can be overridden with the "codepage" mount option. | |
347 | See <file:Documentation/filesystems/vfat.txt> for more information. | |
348 | ||
349 | config FAT_DEFAULT_IOCHARSET | |
350 | string "Default iocharset for FAT" | |
351 | depends on VFAT_FS | |
352 | default "iso8859-1" | |
353 | help | |
354 | Set this to the default input/output character set you'd | |
355 | like FAT to use. It should probably match the character set | |
356 | that most of your FAT filesystems use, and can be overridden | |
357 | with the "iocharset" mount option for FAT filesystems. | |
358 | Note that "utf8" is not recommended for FAT filesystems. | |
359 | If unsure, you shouldn't set "utf8" here. | |
360 | See <file:Documentation/filesystems/vfat.txt> for more information. | |
361 | ||
362 | config NTFS_FS | |
363 | tristate "NTFS file system support" | |
364 | select NLS | |
365 | help | |
366 | NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003. | |
367 | ||
368 | Saying Y or M here enables read support. There is partial, but | |
369 | safe, write support available. For write support you must also | |
370 | say Y to "NTFS write support" below. | |
371 | ||
372 | There are also a number of user-space tools available, called | |
373 | ntfsprogs. These include ntfsundelete and ntfsresize, that work | |
374 | without NTFS support enabled in the kernel. | |
375 | ||
376 | This is a rewrite from scratch of Linux NTFS support and replaced | |
377 | the old NTFS code starting with Linux 2.5.11. A backport to | |
378 | the Linux 2.4 kernel series is separately available as a patch | |
379 | from the project web site. | |
380 | ||
381 | For more information see <file:Documentation/filesystems/ntfs.txt> | |
337e2ab5 | 382 | and <http://www.linux-ntfs.org/>. |
1da177e4 LT |
383 | |
384 | To compile this file system support as a module, choose M here: the | |
385 | module will be called ntfs. | |
386 | ||
387 | If you are not using Windows NT, 2000, XP or 2003 in addition to | |
388 | Linux on your computer it is safe to say N. | |
389 | ||
390 | config NTFS_DEBUG | |
391 | bool "NTFS debugging support" | |
392 | depends on NTFS_FS | |
393 | help | |
394 | If you are experiencing any problems with the NTFS file system, say | |
395 | Y here. This will result in additional consistency checks to be | |
396 | performed by the driver as well as additional debugging messages to | |
397 | be written to the system log. Note that debugging messages are | |
398 | disabled by default. To enable them, supply the option debug_msgs=1 | |
399 | at the kernel command line when booting the kernel or as an option | |
400 | to insmod when loading the ntfs module. Once the driver is active, | |
401 | you can enable debugging messages by doing (as root): | |
402 | echo 1 > /proc/sys/fs/ntfs-debug | |
403 | Replacing the "1" with "0" would disable debug messages. | |
404 | ||
405 | If you leave debugging messages disabled, this results in little | |
406 | overhead, but enabling debug messages results in very significant | |
407 | slowdown of the system. | |
408 | ||
409 | When reporting bugs, please try to have available a full dump of | |
410 | debugging messages while the misbehaviour was occurring. | |
411 | ||
412 | config NTFS_RW | |
413 | bool "NTFS write support" | |
414 | depends on NTFS_FS | |
415 | help | |
416 | This enables the partial, but safe, write support in the NTFS driver. | |
417 | ||
418 | The only supported operation is overwriting existing files, without | |
419 | changing the file length. No file or directory creation, deletion or | |
420 | renaming is possible. Note only non-resident files can be written to | |
421 | so you may find that some very small files (<500 bytes or so) cannot | |
422 | be written to. | |
423 | ||
424 | While we cannot guarantee that it will not damage any data, we have | |
425 | so far not received a single report where the driver would have | |
426 | damaged someones data so we assume it is perfectly safe to use. | |
427 | ||
428 | Note: While write support is safe in this version (a rewrite from | |
429 | scratch of the NTFS support), it should be noted that the old NTFS | |
430 | write support, included in Linux 2.5.10 and before (since 1997), | |
431 | is not safe. | |
432 | ||
433 | This is currently useful with TopologiLinux. TopologiLinux is run | |
434 | on top of any DOS/Microsoft Windows system without partitioning your | |
435 | hard disk. Unlike other Linux distributions TopologiLinux does not | |
436 | need its own partition. For more information see | |
437 | <http://topologi-linux.sourceforge.net/> | |
438 | ||
439 | It is perfectly safe to say N here. | |
440 | ||
441 | endmenu | |
25fad945 | 442 | endif # BLOCK |
1da177e4 LT |
443 | |
444 | menu "Pseudo filesystems" | |
445 | ||
6eedf8d3 | 446 | source "fs/proc/Kconfig" |
b89a8171 | 447 | |
1da177e4 LT |
448 | config SYSFS |
449 | bool "sysfs file system support" if EMBEDDED | |
450 | default y | |
451 | help | |
452 | The sysfs filesystem is a virtual filesystem that the kernel uses to | |
453 | export internal kernel objects, their attributes, and their | |
454 | relationships to one another. | |
455 | ||
456 | Users can use sysfs to ascertain useful information about the running | |
457 | kernel, such as the devices the kernel has discovered on each bus and | |
458 | which driver each is bound to. sysfs can also be used to tune devices | |
459 | and other kernel subsystems. | |
460 | ||
461 | Some system agents rely on the information in sysfs to operate. | |
462 | /sbin/hotplug uses device and object attributes in sysfs to assist in | |
03a67a46 | 463 | delegating policy decisions, like persistently naming devices. |
1da177e4 LT |
464 | |
465 | sysfs is currently used by the block subsystem to mount the root | |
466 | partition. If sysfs is disabled you must specify the boot device on | |
467 | the kernel boot command line via its major and minor numbers. For | |
468 | example, "root=03:01" for /dev/hda1. | |
469 | ||
470 | Designers of embedded systems may wish to say N here to conserve space. | |
471 | ||
1da177e4 LT |
472 | config TMPFS |
473 | bool "Virtual memory file system support (former shm fs)" | |
474 | help | |
475 | Tmpfs is a file system which keeps all files in virtual memory. | |
476 | ||
477 | Everything in tmpfs is temporary in the sense that no files will be | |
478 | created on your hard drive. The files live in memory and swap | |
479 | space. If you unmount a tmpfs instance, everything stored therein is | |
480 | lost. | |
481 | ||
482 | See <file:Documentation/filesystems/tmpfs.txt> for details. | |
483 | ||
39f0247d AG |
484 | config TMPFS_POSIX_ACL |
485 | bool "Tmpfs POSIX Access Control Lists" | |
486 | depends on TMPFS | |
487 | select GENERIC_ACL | |
488 | help | |
489 | POSIX Access Control Lists (ACLs) support permissions for users and | |
490 | groups beyond the owner/group/world scheme. | |
491 | ||
492 | To learn more about Access Control Lists, visit the POSIX ACLs for | |
493 | Linux website <http://acl.bestbits.at/>. | |
494 | ||
495 | If you don't know what Access Control Lists are, say N. | |
496 | ||
1da177e4 LT |
497 | config HUGETLBFS |
498 | bool "HugeTLB file system support" | |
53492b1d GS |
499 | depends on X86 || IA64 || PPC64 || SPARC64 || (SUPERH && MMU) || \ |
500 | (S390 && 64BIT) || BROKEN | |
dda27d1a AO |
501 | help |
502 | hugetlbfs is a filesystem backing for HugeTLB pages, based on | |
503 | ramfs. For architectures that support it, say Y here and read | |
504 | <file:Documentation/vm/hugetlbpage.txt> for details. | |
505 | ||
506 | If unsure, say N. | |
1da177e4 LT |
507 | |
508 | config HUGETLB_PAGE | |
509 | def_bool HUGETLBFS | |
510 | ||
7063fbf2 | 511 | config CONFIGFS_FS |
02ac0499 JB |
512 | tristate "Userspace-driven configuration filesystem" |
513 | depends on SYSFS | |
7063fbf2 JB |
514 | help |
515 | configfs is a ram-based filesystem that provides the converse | |
516 | of sysfs's functionality. Where sysfs is a filesystem-based | |
517 | view of kernel objects, configfs is a filesystem-based manager | |
518 | of kernel objects, or config_items. | |
519 | ||
520 | Both sysfs and configfs can and should exist together on the | |
521 | same system. One is not a replacement for the other. | |
522 | ||
1da177e4 LT |
523 | endmenu |
524 | ||
67ec7d3a RD |
525 | menuconfig MISC_FILESYSTEMS |
526 | bool "Miscellaneous filesystems" | |
527 | default y | |
528 | ---help--- | |
529 | Say Y here to get to see options for various miscellaneous | |
530 | filesystems, such as filesystems that came from other | |
531 | operating systems. | |
532 | ||
533 | This option alone does not add any kernel code. | |
534 | ||
535 | If you say N, all options in this submenu will be skipped and | |
536 | disabled; if unsure, say Y here. | |
537 | ||
538 | if MISC_FILESYSTEMS | |
1da177e4 LT |
539 | |
540 | config ADFS_FS | |
541 | tristate "ADFS file system support (EXPERIMENTAL)" | |
9361401e | 542 | depends on BLOCK && EXPERIMENTAL |
1da177e4 LT |
543 | help |
544 | The Acorn Disc Filing System is the standard file system of the | |
545 | RiscOS operating system which runs on Acorn's ARM-based Risc PC | |
546 | systems and the Acorn Archimedes range of machines. If you say Y | |
547 | here, Linux will be able to read from ADFS partitions on hard drives | |
548 | and from ADFS-formatted floppy discs. If you also want to be able to | |
549 | write to those devices, say Y to "ADFS write support" below. | |
550 | ||
551 | The ADFS partition should be the first partition (i.e., | |
552 | /dev/[hs]d?1) on each of your drives. Please read the file | |
553 | <file:Documentation/filesystems/adfs.txt> for further details. | |
554 | ||
555 | To compile this code as a module, choose M here: the module will be | |
556 | called adfs. | |
557 | ||
558 | If unsure, say N. | |
559 | ||
560 | config ADFS_FS_RW | |
561 | bool "ADFS write support (DANGEROUS)" | |
562 | depends on ADFS_FS | |
563 | help | |
564 | If you say Y here, you will be able to write to ADFS partitions on | |
565 | hard drives and ADFS-formatted floppy disks. This is experimental | |
566 | codes, so if you're unsure, say N. | |
567 | ||
568 | config AFFS_FS | |
569 | tristate "Amiga FFS file system support (EXPERIMENTAL)" | |
9361401e | 570 | depends on BLOCK && EXPERIMENTAL |
1da177e4 LT |
571 | help |
572 | The Fast File System (FFS) is the common file system used on hard | |
573 | disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y | |
574 | if you want to be able to read and write files from and to an Amiga | |
575 | FFS partition on your hard drive. Amiga floppies however cannot be | |
576 | read with this driver due to an incompatibility of the floppy | |
577 | controller used in an Amiga and the standard floppy controller in | |
578 | PCs and workstations. Read <file:Documentation/filesystems/affs.txt> | |
579 | and <file:fs/affs/Changes>. | |
580 | ||
581 | With this driver you can also mount disk files used by Bernd | |
582 | Schmidt's Un*X Amiga Emulator | |
583 | (<http://www.freiburg.linux.de/~uae/>). | |
584 | If you want to do this, you will also need to say Y or M to "Loop | |
585 | device support", above. | |
586 | ||
587 | To compile this file system support as a module, choose M here: the | |
588 | module will be called affs. If unsure, say N. | |
589 | ||
237fead6 MH |
590 | config ECRYPT_FS |
591 | tristate "eCrypt filesystem layer support (EXPERIMENTAL)" | |
88b4a07e | 592 | depends on EXPERIMENTAL && KEYS && CRYPTO && NET |
237fead6 MH |
593 | help |
594 | Encrypted filesystem that operates on the VFS layer. See | |
e403149c | 595 | <file:Documentation/filesystems/ecryptfs.txt> to learn more about |
237fead6 MH |
596 | eCryptfs. Userspace components are required and can be |
597 | obtained from <http://ecryptfs.sf.net>. | |
598 | ||
599 | To compile this file system support as a module, choose M here: the | |
600 | module will be called ecryptfs. | |
601 | ||
1da177e4 LT |
602 | config HFS_FS |
603 | tristate "Apple Macintosh file system support (EXPERIMENTAL)" | |
9361401e | 604 | depends on BLOCK && EXPERIMENTAL |
878129a3 | 605 | select NLS |
1da177e4 LT |
606 | help |
607 | If you say Y here, you will be able to mount Macintosh-formatted | |
608 | floppy disks and hard drive partitions with full read-write access. | |
889c94a1 JFS |
609 | Please read <file:Documentation/filesystems/hfs.txt> to learn about |
610 | the available mount options. | |
1da177e4 LT |
611 | |
612 | To compile this file system support as a module, choose M here: the | |
613 | module will be called hfs. | |
614 | ||
615 | config HFSPLUS_FS | |
616 | tristate "Apple Extended HFS file system support" | |
9361401e | 617 | depends on BLOCK |
1da177e4 LT |
618 | select NLS |
619 | select NLS_UTF8 | |
620 | help | |
621 | If you say Y here, you will be able to mount extended format | |
622 | Macintosh-formatted hard drive partitions with full read-write access. | |
623 | ||
624 | This file system is often called HFS+ and was introduced with | |
625 | MacOS 8. It includes all Mac specific filesystem data such as | |
626 | data forks and creator codes, but it also has several UNIX | |
627 | style features such as file ownership and permissions. | |
628 | ||
629 | config BEFS_FS | |
630 | tristate "BeOS file system (BeFS) support (read only) (EXPERIMENTAL)" | |
9361401e | 631 | depends on BLOCK && EXPERIMENTAL |
1da177e4 LT |
632 | select NLS |
633 | help | |
634 | The BeOS File System (BeFS) is the native file system of Be, Inc's | |
635 | BeOS. Notable features include support for arbitrary attributes | |
3cb2fccc | 636 | on files and directories, and database-like indices on selected |
1da177e4 LT |
637 | attributes. (Also note that this driver doesn't make those features |
638 | available at this time). It is a 64 bit filesystem, so it supports | |
44c09201 | 639 | extremely large volumes and files. |
1da177e4 LT |
640 | |
641 | If you use this filesystem, you should also say Y to at least one | |
642 | of the NLS (native language support) options below. | |
643 | ||
644 | If you don't know what this is about, say N. | |
645 | ||
646 | To compile this as a module, choose M here: the module will be | |
647 | called befs. | |
648 | ||
649 | config BEFS_DEBUG | |
650 | bool "Debug BeFS" | |
651 | depends on BEFS_FS | |
652 | help | |
653 | If you say Y here, you can use the 'debug' mount option to enable | |
c7736339 | 654 | debugging output from the driver. |
1da177e4 LT |
655 | |
656 | config BFS_FS | |
657 | tristate "BFS file system support (EXPERIMENTAL)" | |
9361401e | 658 | depends on BLOCK && EXPERIMENTAL |
1da177e4 LT |
659 | help |
660 | Boot File System (BFS) is a file system used under SCO UnixWare to | |
661 | allow the bootloader access to the kernel image and other important | |
662 | files during the boot process. It is usually mounted under /stand | |
663 | and corresponds to the slice marked as "STAND" in the UnixWare | |
664 | partition. You should say Y if you want to read or write the files | |
665 | on your /stand slice from within Linux. You then also need to say Y | |
666 | to "UnixWare slices support", below. More information about the BFS | |
667 | file system is contained in the file | |
668 | <file:Documentation/filesystems/bfs.txt>. | |
669 | ||
670 | If you don't know what this is about, say N. | |
671 | ||
672 | To compile this as a module, choose M here: the module will be called | |
673 | bfs. Note that the file system of your root partition (the one | |
674 | containing the directory /) cannot be compiled as a module. | |
675 | ||
676 | ||
677 | ||
678 | config EFS_FS | |
679 | tristate "EFS file system support (read only) (EXPERIMENTAL)" | |
9361401e | 680 | depends on BLOCK && EXPERIMENTAL |
1da177e4 LT |
681 | help |
682 | EFS is an older file system used for non-ISO9660 CD-ROMs and hard | |
683 | disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer | |
684 | uses the XFS file system for hard disk partitions however). | |
685 | ||
686 | This implementation only offers read-only access. If you don't know | |
687 | what all this is about, it's safe to say N. For more information | |
688 | about EFS see its home page at <http://aeschi.ch.eu.org/efs/>. | |
689 | ||
690 | To compile the EFS file system support as a module, choose M here: the | |
691 | module will be called efs. | |
692 | ||
31db6e9e | 693 | source "fs/jffs2/Kconfig" |
0d7eff87 AB |
694 | # UBIFS File system configuration |
695 | source "fs/ubifs/Kconfig" | |
696 | ||
1da177e4 LT |
697 | config CRAMFS |
698 | tristate "Compressed ROM file system support (cramfs)" | |
9361401e | 699 | depends on BLOCK |
1da177e4 LT |
700 | select ZLIB_INFLATE |
701 | help | |
702 | Saying Y here includes support for CramFs (Compressed ROM File | |
703 | System). CramFs is designed to be a simple, small, and compressed | |
704 | file system for ROM based embedded systems. CramFs is read-only, | |
705 | limited to 256MB file systems (with 16MB files), and doesn't support | |
706 | 16/32 bits uid/gid, hard links and timestamps. | |
707 | ||
708 | See <file:Documentation/filesystems/cramfs.txt> and | |
709 | <file:fs/cramfs/README> for further information. | |
710 | ||
711 | To compile this as a module, choose M here: the module will be called | |
712 | cramfs. Note that the root file system (the one containing the | |
713 | directory /) cannot be compiled as a module. | |
714 | ||
715 | If unsure, say N. | |
716 | ||
6ab5c1ca PL |
717 | config SQUASHFS |
718 | tristate "SquashFS 4.0 - Squashed file system support" | |
719 | depends on BLOCK | |
720 | select ZLIB_INFLATE | |
721 | help | |
722 | Saying Y here includes support for SquashFS 4.0 (a Compressed | |
723 | Read-Only File System). Squashfs is a highly compressed read-only | |
724 | filesystem for Linux. It uses zlib compression to compress both | |
725 | files, inodes and directories. Inodes in the system are very small | |
726 | and all blocks are packed to minimise data overhead. Block sizes | |
727 | greater than 4K are supported up to a maximum of 1 Mbytes (default | |
728 | block size 128K). SquashFS 4.0 supports 64 bit filesystems and files | |
729 | (larger than 4GB), full uid/gid information, hard links and | |
730 | timestamps. | |
731 | ||
732 | Squashfs is intended for general read-only filesystem use, for | |
733 | archival use (i.e. in cases where a .tar.gz file may be used), and in | |
734 | embedded systems where low overhead is needed. Further information | |
735 | and tools are available from http://squashfs.sourceforge.net. | |
736 | ||
737 | If you want to compile this as a module ( = code which can be | |
738 | inserted in and removed from the running kernel whenever you want), | |
739 | say M here and read <file:Documentation/modules.txt>. The module | |
740 | will be called squashfs. Note that the root file system (the one | |
741 | containing the directory /) cannot be compiled as a module. | |
742 | ||
743 | If unsure, say N. | |
744 | ||
745 | config SQUASHFS_EMBEDDED | |
746 | ||
747 | bool "Additional option for memory-constrained systems" | |
748 | depends on SQUASHFS | |
749 | default n | |
750 | help | |
751 | Saying Y here allows you to specify cache size. | |
752 | ||
753 | If unsure, say N. | |
754 | ||
755 | config SQUASHFS_FRAGMENT_CACHE_SIZE | |
756 | int "Number of fragments cached" if SQUASHFS_EMBEDDED | |
757 | depends on SQUASHFS | |
758 | default "3" | |
759 | help | |
760 | By default SquashFS caches the last 3 fragments read from | |
761 | the filesystem. Increasing this amount may mean SquashFS | |
762 | has to re-read fragments less often from disk, at the expense | |
763 | of extra system memory. Decreasing this amount will mean | |
764 | SquashFS uses less memory at the expense of extra reads from disk. | |
765 | ||
766 | Note there must be at least one cached fragment. Anything | |
767 | much more than three will probably not make much difference. | |
768 | ||
1da177e4 LT |
769 | config VXFS_FS |
770 | tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)" | |
9361401e | 771 | depends on BLOCK |
1da177e4 LT |
772 | help |
773 | FreeVxFS is a file system driver that support the VERITAS VxFS(TM) | |
774 | file system format. VERITAS VxFS(TM) is the standard file system | |
775 | of SCO UnixWare (and possibly others) and optionally available | |
776 | for Sunsoft Solaris, HP-UX and many other operating systems. | |
777 | Currently only readonly access is supported. | |
778 | ||
779 | NOTE: the file system type as used by mount(1), mount(2) and | |
780 | fstab(5) is 'vxfs' as it describes the file system format, not | |
781 | the actual driver. | |
782 | ||
783 | To compile this as a module, choose M here: the module will be | |
784 | called freevxfs. If unsure, say N. | |
785 | ||
25fad945 RD |
786 | config MINIX_FS |
787 | tristate "Minix file system support" | |
788 | depends on BLOCK | |
789 | help | |
790 | Minix is a simple operating system used in many classes about OS's. | |
791 | The minix file system (method to organize files on a hard disk | |
792 | partition or a floppy disk) was the original file system for Linux, | |
793 | but has been superseded by the second extended file system ext2fs. | |
794 | You don't want to use the minix file system on your hard disk | |
795 | because of certain built-in restrictions, but it is sometimes found | |
796 | on older Linux floppy disks. This option will enlarge your kernel | |
797 | by about 28 KB. If unsure, say N. | |
798 | ||
799 | To compile this file system support as a module, choose M here: the | |
800 | module will be called minix. Note that the file system of your root | |
801 | partition (the one containing the directory /) cannot be compiled as | |
802 | a module. | |
803 | ||
63ca8ce2 BC |
804 | config OMFS_FS |
805 | tristate "SonicBlue Optimized MPEG File System support" | |
806 | depends on BLOCK | |
807 | select CRC_ITU_T | |
808 | help | |
809 | This is the proprietary file system used by the Rio Karma music | |
810 | player and ReplayTV DVR. Despite the name, this filesystem is not | |
811 | more efficient than a standard FS for MPEG files, in fact likely | |
812 | the opposite is true. Say Y if you have either of these devices | |
813 | and wish to mount its disk. | |
814 | ||
815 | To compile this file system support as a module, choose M here: the | |
816 | module will be called omfs. If unsure, say N. | |
1da177e4 LT |
817 | |
818 | config HPFS_FS | |
819 | tristate "OS/2 HPFS file system support" | |
9361401e | 820 | depends on BLOCK |
1da177e4 LT |
821 | help |
822 | OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS | |
823 | is the file system used for organizing files on OS/2 hard disk | |
824 | partitions. Say Y if you want to be able to read files from and | |
825 | write files to an OS/2 HPFS partition on your hard drive. OS/2 | |
826 | floppies however are in regular MSDOS format, so you don't need this | |
827 | option in order to be able to read them. Read | |
828 | <file:Documentation/filesystems/hpfs.txt>. | |
829 | ||
830 | To compile this file system support as a module, choose M here: the | |
831 | module will be called hpfs. If unsure, say N. | |
832 | ||
833 | ||
1da177e4 LT |
834 | config QNX4FS_FS |
835 | tristate "QNX4 file system support (read only)" | |
9361401e | 836 | depends on BLOCK |
1da177e4 LT |
837 | help |
838 | This is the file system used by the real-time operating systems | |
839 | QNX 4 and QNX 6 (the latter is also called QNX RTP). | |
840 | Further information is available at <http://www.qnx.com/>. | |
841 | Say Y if you intend to mount QNX hard disks or floppies. | |
842 | Unless you say Y to "QNX4FS read-write support" below, you will | |
843 | only be able to read these file systems. | |
844 | ||
845 | To compile this file system support as a module, choose M here: the | |
846 | module will be called qnx4. | |
847 | ||
848 | If you don't know whether you need it, then you don't need it: | |
849 | answer N. | |
850 | ||
851 | config QNX4FS_RW | |
852 | bool "QNX4FS write support (DANGEROUS)" | |
853 | depends on QNX4FS_FS && EXPERIMENTAL && BROKEN | |
854 | help | |
855 | Say Y if you want to test write support for QNX4 file systems. | |
856 | ||
857 | It's currently broken, so for now: | |
858 | answer N. | |
859 | ||
25fad945 RD |
860 | config ROMFS_FS |
861 | tristate "ROM file system support" | |
862 | depends on BLOCK | |
863 | ---help--- | |
864 | This is a very small read-only file system mainly intended for | |
865 | initial ram disks of installation disks, but it could be used for | |
866 | other read-only media as well. Read | |
867 | <file:Documentation/filesystems/romfs.txt> for details. | |
868 | ||
869 | To compile this file system support as a module, choose M here: the | |
870 | module will be called romfs. Note that the file system of your | |
871 | root partition (the one containing the directory /) cannot be a | |
872 | module. | |
873 | ||
874 | If you don't know whether you need it, then you don't need it: | |
875 | answer N. | |
1da177e4 LT |
876 | |
877 | ||
878 | config SYSV_FS | |
879 | tristate "System V/Xenix/V7/Coherent file system support" | |
9361401e | 880 | depends on BLOCK |
1da177e4 LT |
881 | help |
882 | SCO, Xenix and Coherent are commercial Unix systems for Intel | |
883 | machines, and Version 7 was used on the DEC PDP-11. Saying Y | |
884 | here would allow you to read from their floppies and hard disk | |
885 | partitions. | |
886 | ||
887 | If you have floppies or hard disk partitions like that, it is likely | |
888 | that they contain binaries from those other Unix systems; in order | |
cab00891 | 889 | to run these binaries, you will want to install linux-abi which is |
1da177e4 LT |
890 | a set of kernel modules that lets you run SCO, Xenix, Wyse, |
891 | UnixWare, Dell Unix and System V programs under Linux. It is | |
892 | available via FTP (user: ftp) from | |
893 | <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>). | |
894 | NOTE: that will work only for binaries from Intel-based systems; | |
895 | PDP ones will have to wait until somebody ports Linux to -11 ;-) | |
896 | ||
897 | If you only intend to mount files from some other Unix over the | |
898 | network using NFS, you don't need the System V file system support | |
899 | (but you need NFS file system support obviously). | |
900 | ||
901 | Note that this option is generally not needed for floppies, since a | |
902 | good portable way to transport files and directories between unixes | |
903 | (and even other operating systems) is given by the tar program ("man | |
904 | tar" or preferably "info tar"). Note also that this option has | |
905 | nothing whatsoever to do with the option "System V IPC". Read about | |
906 | the System V file system in | |
907 | <file:Documentation/filesystems/sysv-fs.txt>. | |
908 | Saying Y here will enlarge your kernel by about 27 KB. | |
909 | ||
910 | To compile this as a module, choose M here: the module will be called | |
911 | sysv. | |
912 | ||
913 | If you haven't heard about all of this before, it's safe to say N. | |
914 | ||
915 | ||
1da177e4 LT |
916 | config UFS_FS |
917 | tristate "UFS file system support (read only)" | |
9361401e | 918 | depends on BLOCK |
1da177e4 LT |
919 | help |
920 | BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD, | |
921 | OpenBSD and NeXTstep) use a file system called UFS. Some System V | |
922 | Unixes can create and mount hard disk partitions and diskettes using | |
923 | this file system as well. Saying Y here will allow you to read from | |
924 | these partitions; if you also want to write to them, say Y to the | |
925 | experimental "UFS file system write support", below. Please read the | |
926 | file <file:Documentation/filesystems/ufs.txt> for more information. | |
927 | ||
928 | The recently released UFS2 variant (used in FreeBSD 5.x) is | |
929 | READ-ONLY supported. | |
930 | ||
1da177e4 LT |
931 | Note that this option is generally not needed for floppies, since a |
932 | good portable way to transport files and directories between unixes | |
933 | (and even other operating systems) is given by the tar program ("man | |
934 | tar" or preferably "info tar"). | |
935 | ||
936 | When accessing NeXTstep files, you may need to convert them from the | |
937 | NeXT character set to the Latin1 character set; use the program | |
938 | recode ("info recode") for this purpose. | |
939 | ||
940 | To compile the UFS file system support as a module, choose M here: the | |
941 | module will be called ufs. | |
942 | ||
943 | If you haven't heard about all of this before, it's safe to say N. | |
944 | ||
945 | config UFS_FS_WRITE | |
946 | bool "UFS file system write support (DANGEROUS)" | |
5afb3145 | 947 | depends on UFS_FS && EXPERIMENTAL |
1da177e4 LT |
948 | help |
949 | Say Y here if you want to try writing to UFS partitions. This is | |
950 | experimental, so you should back up your UFS partitions beforehand. | |
951 | ||
abf5d15f ED |
952 | config UFS_DEBUG |
953 | bool "UFS debugging" | |
954 | depends on UFS_FS | |
955 | help | |
956 | If you are experiencing any problems with the UFS filesystem, say | |
957 | Y here. This will result in _many_ additional debugging messages to be | |
958 | written to the system log. | |
959 | ||
67ec7d3a | 960 | endif # MISC_FILESYSTEMS |
1da177e4 | 961 | |
ea0985ad JE |
962 | menuconfig NETWORK_FILESYSTEMS |
963 | bool "Network File Systems" | |
964 | default y | |
1da177e4 | 965 | depends on NET |
ea0985ad JE |
966 | ---help--- |
967 | Say Y here to get to see options for network filesystems and | |
968 | filesystem-related networking code, such as NFS daemon and | |
969 | RPCSEC security modules. | |
6fb1bc10 | 970 | |
ea0985ad JE |
971 | This option alone does not add any kernel code. |
972 | ||
973 | If you say N, all options in this submenu will be skipped and | |
974 | disabled; if unsure, say Y here. | |
975 | ||
976 | if NETWORK_FILESYSTEMS | |
1da177e4 LT |
977 | |
978 | config NFS_FS | |
6fb1bc10 | 979 | tristate "NFS client support" |
1da177e4 LT |
980 | depends on INET |
981 | select LOCKD | |
982 | select SUNRPC | |
b7fa0554 | 983 | select NFS_ACL_SUPPORT if NFS_V3_ACL |
1da177e4 | 984 | help |
6fb1bc10 CL |
985 | Choose Y here if you want to access files residing on other |
986 | computers using Sun's Network File System protocol. To compile | |
987 | this file system support as a module, choose M here: the module | |
988 | will be called nfs. | |
1da177e4 | 989 | |
6fb1bc10 CL |
990 | To mount file systems exported by NFS servers, you also need to |
991 | install the user space mount.nfs command which can be found in | |
992 | the Linux nfs-utils package, available from http://linux-nfs.org/. | |
993 | Information about using the mount command is available in the | |
994 | mount(8) man page. More detail about the Linux NFS client | |
995 | implementation is available via the nfs(5) man page. | |
1da177e4 | 996 | |
6fb1bc10 CL |
997 | Below you can choose which versions of the NFS protocol are |
998 | available in the kernel to mount NFS servers. Support for NFS | |
999 | version 2 (RFC 1094) is always available when NFS_FS is selected. | |
1da177e4 | 1000 | |
6fb1bc10 CL |
1001 | To configure a system which mounts its root file system via NFS |
1002 | at boot time, say Y here, select "Kernel level IP | |
1003 | autoconfiguration" in the NETWORK menu, and select "Root file | |
1004 | system on NFS" below. You cannot compile this file system as a | |
1005 | module in this case. | |
1da177e4 | 1006 | |
6fb1bc10 | 1007 | If unsure, say N. |
1da177e4 LT |
1008 | |
1009 | config NFS_V3 | |
6fb1bc10 | 1010 | bool "NFS client support for NFS version 3" |
1da177e4 LT |
1011 | depends on NFS_FS |
1012 | help | |
6fb1bc10 CL |
1013 | This option enables support for version 3 of the NFS protocol |
1014 | (RFC 1813) in the kernel's NFS client. | |
1da177e4 LT |
1015 | |
1016 | If unsure, say Y. | |
1017 | ||
b7fa0554 | 1018 | config NFS_V3_ACL |
6fb1bc10 | 1019 | bool "NFS client support for the NFSv3 ACL protocol extension" |
b7fa0554 AG |
1020 | depends on NFS_V3 |
1021 | help | |
6fb1bc10 CL |
1022 | Some NFS servers support an auxiliary NFSv3 ACL protocol that |
1023 | Sun added to Solaris but never became an official part of the | |
1024 | NFS version 3 protocol. This protocol extension allows | |
1025 | applications on NFS clients to manipulate POSIX Access Control | |
1026 | Lists on files residing on NFS servers. NFS servers enforce | |
1027 | ACLs on local files whether this protocol is available or not. | |
1028 | ||
1029 | Choose Y here if your NFS server supports the Solaris NFSv3 ACL | |
1030 | protocol extension and you want your NFS client to allow | |
1031 | applications to access and modify ACLs on files on the server. | |
1032 | ||
1033 | Most NFS servers don't support the Solaris NFSv3 ACL protocol | |
1034 | extension. You can choose N here or specify the "noacl" mount | |
1035 | option to prevent your NFS client from trying to use the NFSv3 | |
1036 | ACL protocol. | |
b7fa0554 AG |
1037 | |
1038 | If unsure, say N. | |
1039 | ||
1da177e4 | 1040 | config NFS_V4 |
6fb1bc10 | 1041 | bool "NFS client support for NFS version 4 (EXPERIMENTAL)" |
1da177e4 LT |
1042 | depends on NFS_FS && EXPERIMENTAL |
1043 | select RPCSEC_GSS_KRB5 | |
1044 | help | |
6fb1bc10 CL |
1045 | This option enables support for version 4 of the NFS protocol |
1046 | (RFC 3530) in the kernel's NFS client. | |
1da177e4 | 1047 | |
6fb1bc10 CL |
1048 | To mount NFS servers using NFSv4, you also need to install user |
1049 | space programs which can be found in the Linux nfs-utils package, | |
1050 | available from http://linux-nfs.org/. | |
1da177e4 LT |
1051 | |
1052 | If unsure, say N. | |
1053 | ||
6fb1bc10 CL |
1054 | config ROOT_NFS |
1055 | bool "Root file system on NFS" | |
1056 | depends on NFS_FS=y && IP_PNP | |
1057 | help | |
1058 | If you want your system to mount its root file system via NFS, | |
1059 | choose Y here. This is common practice for managing systems | |
1060 | without local permanent storage. For details, read | |
1061 | <file:Documentation/filesystems/nfsroot.txt>. | |
1062 | ||
1063 | Most people say N here. | |
1064 | ||
1da177e4 LT |
1065 | config NFSD |
1066 | tristate "NFS server support" | |
1067 | depends on INET | |
1068 | select LOCKD | |
1069 | select SUNRPC | |
1070 | select EXPORTFS | |
f05e15b5 | 1071 | select NFS_ACL_SUPPORT if NFSD_V2_ACL |
1da177e4 | 1072 | help |
d24455b5 CL |
1073 | Choose Y here if you want to allow other computers to access |
1074 | files residing on this system using Sun's Network File System | |
1075 | protocol. To compile the NFS server support as a module, | |
1076 | choose M here: the module will be called nfsd. | |
1da177e4 | 1077 | |
d24455b5 CL |
1078 | You may choose to use a user-space NFS server instead, in which |
1079 | case you can choose N here. | |
1da177e4 | 1080 | |
d24455b5 CL |
1081 | To export local file systems using NFS, you also need to install |
1082 | user space programs which can be found in the Linux nfs-utils | |
1083 | package, available from http://linux-nfs.org/. More detail about | |
1084 | the Linux NFS server implementation is available via the | |
1085 | exports(5) man page. | |
1da177e4 | 1086 | |
d24455b5 CL |
1087 | Below you can choose which versions of the NFS protocol are |
1088 | available to clients mounting the NFS server on this system. | |
1089 | Support for NFS version 2 (RFC 1094) is always available when | |
1090 | CONFIG_NFSD is selected. | |
1da177e4 | 1091 | |
d24455b5 | 1092 | If unsure, say N. |
1da177e4 | 1093 | |
a257cdd0 AG |
1094 | config NFSD_V2_ACL |
1095 | bool | |
1096 | depends on NFSD | |
1097 | ||
1da177e4 | 1098 | config NFSD_V3 |
d24455b5 | 1099 | bool "NFS server support for NFS version 3" |
1da177e4 LT |
1100 | depends on NFSD |
1101 | help | |
d24455b5 CL |
1102 | This option enables support in your system's NFS server for |
1103 | version 3 of the NFS protocol (RFC 1813). | |
1104 | ||
1105 | If unsure, say Y. | |
1da177e4 | 1106 | |
a257cdd0 | 1107 | config NFSD_V3_ACL |
d24455b5 | 1108 | bool "NFS server support for the NFSv3 ACL protocol extension" |
a257cdd0 | 1109 | depends on NFSD_V3 |
78dd0992 | 1110 | select NFSD_V2_ACL |
a257cdd0 | 1111 | help |
d24455b5 CL |
1112 | Solaris NFS servers support an auxiliary NFSv3 ACL protocol that |
1113 | never became an official part of the NFS version 3 protocol. | |
1114 | This protocol extension allows applications on NFS clients to | |
1115 | manipulate POSIX Access Control Lists on files residing on NFS | |
1116 | servers. NFS servers enforce POSIX ACLs on local files whether | |
1117 | this protocol is available or not. | |
1118 | ||
1119 | This option enables support in your system's NFS server for the | |
1120 | NFSv3 ACL protocol extension allowing NFS clients to manipulate | |
1121 | POSIX ACLs on files exported by your system's NFS server. NFS | |
1122 | clients which support the Solaris NFSv3 ACL protocol can then | |
1123 | access and modify ACLs on your NFS server. | |
1124 | ||
1125 | To store ACLs on your NFS server, you also need to enable ACL- | |
1126 | related CONFIG options for your local file systems of choice. | |
1127 | ||
1128 | If unsure, say N. | |
a257cdd0 | 1129 | |
1da177e4 | 1130 | config NFSD_V4 |
d24455b5 | 1131 | bool "NFS server support for NFS version 4 (EXPERIMENTAL)" |
1a448fdb CL |
1132 | depends on NFSD && PROC_FS && EXPERIMENTAL |
1133 | select NFSD_V3 | |
89206955 | 1134 | select FS_POSIX_ACL |
42ed95c4 | 1135 | select RPCSEC_GSS_KRB5 |
1da177e4 | 1136 | help |
d24455b5 CL |
1137 | This option enables support in your system's NFS server for |
1138 | version 4 of the NFS protocol (RFC 3530). | |
1139 | ||
1140 | To export files using NFSv4, you need to install additional user | |
1141 | space programs which can be found in the Linux nfs-utils package, | |
1142 | available from http://linux-nfs.org/. | |
1143 | ||
1da177e4 LT |
1144 | If unsure, say N. |
1145 | ||
1da177e4 LT |
1146 | config LOCKD |
1147 | tristate | |
1148 | ||
1149 | config LOCKD_V4 | |
1150 | bool | |
1151 | depends on NFSD_V3 || NFS_V3 | |
1152 | default y | |
1153 | ||
1154 | config EXPORTFS | |
1155 | tristate | |
1156 | ||
a257cdd0 AG |
1157 | config NFS_ACL_SUPPORT |
1158 | tristate | |
1159 | select FS_POSIX_ACL | |
1160 | ||
1161 | config NFS_COMMON | |
1162 | bool | |
1163 | depends on NFSD || NFS_FS | |
1164 | default y | |
1165 | ||
1da177e4 LT |
1166 | config SUNRPC |
1167 | tristate | |
1168 | ||
1169 | config SUNRPC_GSS | |
1170 | tristate | |
1171 | ||
c3a57ed7 | 1172 | config SUNRPC_XPRT_RDMA |
3211e4eb | 1173 | tristate |
113632d0 | 1174 | depends on SUNRPC && INFINIBAND && EXPERIMENTAL |
3211e4eb | 1175 | default SUNRPC && INFINIBAND |
327a299d CL |
1176 | help |
1177 | This option enables an RPC client transport capability that | |
1178 | allows the NFS client to mount servers via an RDMA-enabled | |
1179 | transport. | |
1180 | ||
1181 | To compile RPC client RDMA transport support as a module, | |
1182 | choose M here: the module will be called xprtrdma. | |
1183 | ||
1184 | If unsure, say N. | |
c3a57ed7 | 1185 | |
a26cfad6 CL |
1186 | config SUNRPC_REGISTER_V4 |
1187 | bool "Register local RPC services via rpcbind v4 (EXPERIMENTAL)" | |
1188 | depends on SUNRPC && EXPERIMENTAL | |
1189 | default n | |
1190 | help | |
1191 | Sun added support for registering RPC services at an IPv6 | |
1192 | address by creating two new versions of the rpcbind protocol | |
1193 | (RFC 1833). | |
1194 | ||
1195 | This option enables support in the kernel RPC server for | |
1196 | registering kernel RPC services via version 4 of the rpcbind | |
1197 | protocol. If you enable this option, you must run a portmapper | |
1198 | daemon that supports rpcbind protocol version 4. | |
1199 | ||
1200 | Serving NFS over IPv6 from knfsd (the kernel's NFS server) | |
1201 | requires that you enable this option and use a portmapper that | |
1202 | supports rpcbind version 4. | |
1203 | ||
1204 | If unsure, say N to get traditional behavior (register kernel | |
1205 | RPC services using only rpcbind version 2). Distributions | |
1206 | using the legacy Linux portmapper daemon must say N here. | |
1207 | ||
1da177e4 LT |
1208 | config RPCSEC_GSS_KRB5 |
1209 | tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)" | |
1210 | depends on SUNRPC && EXPERIMENTAL | |
1211 | select SUNRPC_GSS | |
1212 | select CRYPTO | |
1213 | select CRYPTO_MD5 | |
1214 | select CRYPTO_DES | |
bcbaecbb | 1215 | select CRYPTO_CBC |
1da177e4 | 1216 | help |
327a299d CL |
1217 | Choose Y here to enable Secure RPC using the Kerberos version 5 |
1218 | GSS-API mechanism (RFC 1964). | |
1da177e4 | 1219 | |
327a299d CL |
1220 | Secure RPC calls with Kerberos require an auxiliary user-space |
1221 | daemon which may be found in the Linux nfs-utils package | |
1222 | available from http://linux-nfs.org/. In addition, user-space | |
1223 | Kerberos support should be installed. | |
1da177e4 LT |
1224 | |
1225 | If unsure, say N. | |
1226 | ||
1227 | config RPCSEC_GSS_SPKM3 | |
1228 | tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)" | |
1229 | depends on SUNRPC && EXPERIMENTAL | |
1230 | select SUNRPC_GSS | |
1231 | select CRYPTO | |
1232 | select CRYPTO_MD5 | |
1233 | select CRYPTO_DES | |
df6db302 | 1234 | select CRYPTO_CAST5 |
bcbaecbb | 1235 | select CRYPTO_CBC |
1da177e4 | 1236 | help |
327a299d CL |
1237 | Choose Y here to enable Secure RPC using the SPKM3 public key |
1238 | GSS-API mechansim (RFC 2025). | |
1da177e4 | 1239 | |
327a299d CL |
1240 | Secure RPC calls with SPKM3 require an auxiliary userspace |
1241 | daemon which may be found in the Linux nfs-utils package | |
1242 | available from http://linux-nfs.org/. | |
1da177e4 LT |
1243 | |
1244 | If unsure, say N. | |
1245 | ||
1246 | config SMB_FS | |
c7736339 | 1247 | tristate "SMB file system support (OBSOLETE, please use CIFS)" |
1da177e4 LT |
1248 | depends on INET |
1249 | select NLS | |
1250 | help | |
1251 | SMB (Server Message Block) is the protocol Windows for Workgroups | |
1252 | (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share | |
1253 | files and printers over local networks. Saying Y here allows you to | |
1254 | mount their file systems (often called "shares" in this context) and | |
1255 | access them just like any other Unix directory. Currently, this | |
1256 | works only if the Windows machines use TCP/IP as the underlying | |
1257 | transport protocol, and not NetBEUI. For details, read | |
1258 | <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO, | |
1259 | available from <http://www.tldp.org/docs.html#howto>. | |
1260 | ||
1261 | Note: if you just want your box to act as an SMB *server* and make | |
1262 | files and printing services available to Windows clients (which need | |
1263 | to have a TCP/IP stack), you don't need to say Y here; you can use | |
1264 | the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>) | |
1265 | for that. | |
1266 | ||
1267 | General information about how to connect Linux, Windows machines and | |
1268 | Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>. | |
1269 | ||
c7736339 AM |
1270 | To compile the SMB support as a module, choose M here: |
1271 | the module will be called smbfs. Most people say N, however. | |
1da177e4 LT |
1272 | |
1273 | config SMB_NLS_DEFAULT | |
1274 | bool "Use a default NLS" | |
1275 | depends on SMB_FS | |
1276 | help | |
1277 | Enabling this will make smbfs use nls translations by default. You | |
1278 | need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls | |
1279 | settings and you need to give the default nls for the SMB server as | |
1280 | CONFIG_SMB_NLS_REMOTE. | |
1281 | ||
1282 | The nls settings can be changed at mount time, if your smbmount | |
1283 | supports that, using the codepage and iocharset parameters. | |
1284 | ||
1285 | smbmount from samba 2.2.0 or later supports this. | |
1286 | ||
1287 | config SMB_NLS_REMOTE | |
1288 | string "Default Remote NLS Option" | |
1289 | depends on SMB_NLS_DEFAULT | |
1290 | default "cp437" | |
1291 | help | |
1292 | This setting allows you to specify a default value for which | |
1293 | codepage the server uses. If this field is left blank no | |
1294 | translations will be done by default. The local codepage/charset | |
1295 | default to CONFIG_NLS_DEFAULT. | |
1296 | ||
1297 | The nls settings can be changed at mount time, if your smbmount | |
1298 | supports that, using the codepage and iocharset parameters. | |
1299 | ||
1300 | smbmount from samba 2.2.0 or later supports this. | |
1301 | ||
bb26b963 | 1302 | source "fs/cifs/Kconfig" |
6103335d | 1303 | |
1da177e4 LT |
1304 | config NCP_FS |
1305 | tristate "NCP file system support (to mount NetWare volumes)" | |
1306 | depends on IPX!=n || INET | |
1307 | help | |
1308 | NCP (NetWare Core Protocol) is a protocol that runs over IPX and is | |
1309 | used by Novell NetWare clients to talk to file servers. It is to | |
1310 | IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you | |
1311 | to mount NetWare file server volumes and to access them just like | |
1312 | any other Unix directory. For details, please read the file | |
1313 | <file:Documentation/filesystems/ncpfs.txt> in the kernel source and | |
1314 | the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>. | |
1315 | ||
1316 | You do not have to say Y here if you want your Linux box to act as a | |
1317 | file *server* for Novell NetWare clients. | |
1318 | ||
1319 | General information about how to connect Linux, Windows machines and | |
1320 | Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>. | |
1321 | ||
1322 | To compile this as a module, choose M here: the module will be called | |
1323 | ncpfs. Say N unless you are connected to a Novell network. | |
1324 | ||
1325 | source "fs/ncpfs/Kconfig" | |
1326 | ||
1327 | config CODA_FS | |
1328 | tristate "Coda file system support (advanced network fs)" | |
1329 | depends on INET | |
1330 | help | |
1331 | Coda is an advanced network file system, similar to NFS in that it | |
1332 | enables you to mount file systems of a remote server and access them | |
1333 | with regular Unix commands as if they were sitting on your hard | |
1334 | disk. Coda has several advantages over NFS: support for | |
1335 | disconnected operation (e.g. for laptops), read/write server | |
1336 | replication, security model for authentication and encryption, | |
1337 | persistent client caches and write back caching. | |
1338 | ||
1339 | If you say Y here, your Linux box will be able to act as a Coda | |
1340 | *client*. You will need user level code as well, both for the | |
1341 | client and server. Servers are currently user level, i.e. they need | |
1342 | no kernel support. Please read | |
1343 | <file:Documentation/filesystems/coda.txt> and check out the Coda | |
1344 | home page <http://www.coda.cs.cmu.edu/>. | |
1345 | ||
1346 | To compile the coda client support as a module, choose M here: the | |
1347 | module will be called coda. | |
1348 | ||
1da177e4 | 1349 | config AFS_FS |
64aaa4f8 | 1350 | tristate "Andrew File System support (AFS) (EXPERIMENTAL)" |
1da177e4 | 1351 | depends on INET && EXPERIMENTAL |
08e0e7c8 | 1352 | select AF_RXRPC |
1da177e4 LT |
1353 | help |
1354 | If you say Y here, you will get an experimental Andrew File System | |
1355 | driver. It currently only supports unsecured read-only AFS access. | |
1356 | ||
cc2e2767 | 1357 | See <file:Documentation/filesystems/afs.txt> for more information. |
1da177e4 LT |
1358 | |
1359 | If unsure, say N. | |
1360 | ||
08e0e7c8 DH |
1361 | config AFS_DEBUG |
1362 | bool "AFS dynamic debugging" | |
1363 | depends on AFS_FS | |
1364 | help | |
1365 | Say Y here to make runtime controllable debugging messages appear. | |
1366 | ||
1367 | See <file:Documentation/filesystems/afs.txt> for more information. | |
1368 | ||
1369 | If unsure, say N. | |
1370 | ||
93fa58cb EVH |
1371 | config 9P_FS |
1372 | tristate "Plan 9 Resource Sharing Support (9P2000) (Experimental)" | |
bd238fb4 | 1373 | depends on INET && NET_9P && EXPERIMENTAL |
93fa58cb EVH |
1374 | help |
1375 | If you say Y here, you will get experimental support for | |
1376 | Plan 9 resource sharing via the 9P2000 protocol. | |
1377 | ||
1378 | See <http://v9fs.sf.net> for more information. | |
1379 | ||
1380 | If unsure, say N. | |
1381 | ||
ea0985ad | 1382 | endif # NETWORK_FILESYSTEMS |
1da177e4 | 1383 | |
9361401e | 1384 | if BLOCK |
1da177e4 LT |
1385 | menu "Partition Types" |
1386 | ||
1387 | source "fs/partitions/Kconfig" | |
1388 | ||
1389 | endmenu | |
9361401e | 1390 | endif |
1da177e4 LT |
1391 | |
1392 | source "fs/nls/Kconfig" | |
e7fd4179 | 1393 | source "fs/dlm/Kconfig" |
1da177e4 LT |
1394 | |
1395 | endmenu |